I just completed a bit of a Docker POC at Flock, and put together a
bit of a wiki page on it. Not a whole ton there right now, but as we
look towards more nimble deployment mechanisms, Docker might be
something worth looking at.
I hacked together a container with pastebin (sticky-notes) in it, and
a database external to the container. It didn't take more than a few
hours of work going from an Ansible playbook to a working container.
Let me know if anyone has questions or comments on the work so far.
Currently it's just on a transient cloud instance, and there are a lot
of things to think about (some of which I noted on the wiki page)
before we think about moving stuff somewhere more permanent.
There's a mention of something on the wiki page called Custodia. This
is a mechanism for securely provisioning, storing, distributing, and
auditing access to secret data. I wasn't able to find much on the
Internet, but Simo gave a talk on it at Flock if you went there :)
Anyhow, the wiki page is
https://fedoraproject.org/wiki/Infrastructure_Docker_POC
-Jon
There was a incident last night where mailman01 locked up and the only
reason I noticed it was an alert on collab03 having emails waiting to
deliver to mailman01.
This patch adds mailman01 to our normal nagios monitoring.
+1s?
kevin
--
---
.../files/nagios/hostgroups/vpnclients.cfg | 2 +-
.../nagios_server/files/nagios/hosts/mailman01.cfg | 7 +++++++
2 files changed, 8 insertions(+), 1 deletions(-)
create mode 100644 roles/nagios_server/files/nagios/hosts/mailman01.cfg
diff --git a/roles/nagios_server/files/nagios/hostgroups/vpnclients.cfg b/roles/nagios_server/files/nagios/hostgroups/vpnclients.cfg
index 7b34d6d..196702c 100644
--- a/roles/nagios_server/files/nagios/hostgroups/vpnclients.cfg
+++ b/roles/nagios_server/files/nagios/hostgroups/vpnclients.cfg
@@ -5,5 +5,5 @@
define hostgroup {
hostgroup_name vpnclients
alias vpnclients
- members tummy01,unbound-tummy01,smtp-mm-tummy01,proxy03,unbound-osuosl01,bodhost01,proxy07,coloamer01,proxy08,download-ib02,noc02,unbound-ib01,ibiblio02,ns02,proxy04,smtp-mm-ib01,torrent01,ibiblio03,ibiblio04,people01,internetx01,hosted-lists01,ns05,proxy02,osuosl01,proxy06,osuosl02,osuosl03,hosted03,ibiblio02,serverbeach09,ns-sb01,collab03,smtp-mm-coloamer01,host1plus01,dedicatedsolutions01,proxy05,proxy11
+ members tummy01,unbound-tummy01,smtp-mm-tummy01,proxy03,unbound-osuosl01,bodhost01,proxy07,coloamer01,proxy08,download-ib02,noc02,unbound-ib01,ibiblio02,ns02,proxy04,smtp-mm-ib01,torrent01,ibiblio03,ibiblio04,people01,internetx01,hosted-lists01,ns05,proxy02,osuosl01,proxy06,osuosl02,osuosl03,hosted03,ibiblio02,serverbeach09,ns-sb01,collab03,smtp-mm-coloamer01,host1plus01,dedicatedsolutions01,proxy05,proxy11,mailman01
}
diff --git a/roles/nagios_server/files/nagios/hosts/mailman01.cfg b/roles/nagios_server/files/nagios/hosts/mailman01.cfg
new file mode 100644
index 0000000..f3614c1
--- /dev/null
+++ b/roles/nagios_server/files/nagios/hosts/mailman01.cfg
@@ -0,0 +1,7 @@
+define host {
+ host_name mailman01
+ alias mailman01.phx2.fedoraproject.org
+ use defaulttemplate
+ address mailman01.phx2.fedoraproject.org
+ parents virthost17
+}
--
1.7.2.1
_______________________________________________
infrastructure mailing list
infrastructure(a)lists.fedoraproject.org
http://lists.fedoraproject.org/postorius/infrastructure@lists.fedoraproject…
Hi Infrastructure team,
on September 17, 2015 we plan to organize Fedora 23 Beta Release
Readiness Meeting [1]. As we will need a status from the
Infrastructure team, I would like to ask for a volunteer who will join
the meeting and will be able to provide the status for F23 Beta
readiness in the name of the whole team. Please let me know who the
volunteer will be :-)
[1] https://apps.fedoraproject.org/calendar/Fedora%20release/2015/9/14/#m2676
Thanks and Best Regards,
Jan
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
_______________________________________________
infrastructure mailing list
infrastructure(a)lists.fedoraproject.org
http://lists.fedoraproject.org/postorius/infrastructure@lists.fedoraproject…
Can I get two +1s for this fix which renames the report_mirror files
to have a '.conf' at the end.
Fix the s3sync report_mirror file names
The s3sync has been running successfully for some time now.
Unfortunately the last step, which runs report_mirror to update the
status of the s3 mirrors, failed as the report_mirror configuration
files had wrong names (missing .conf).
diff --git a/roles/s3-mirror/tasks/main.yml b/roles/s3-mirror/tasks/main.yml
index 3da4b8d..e3cf8a4 100644
--- a/roles/s3-mirror/tasks/main.yml
+++ b/roles/s3-mirror/tasks/main.yml
@@ -14,7 +14,7 @@
- mirrormanager2-client
- name: Create report_mirror config files
- template: src=report_mirror.conf dest=/etc/mirrormanager-client/report_mirror_{{ item }} owner=s3-mirror group=s3-mirror mode=0400
+ template: src=report_mirror.conf dest=/etc/mirrormanager-client/report_mirror_{{ item }}.conf owner=s3-mirror group=s3-mirror mode=0400
with_items:
- s3-mirror-us-east-1
- s3-mirror-us-west-1
Adrian
_______________________________________________
infrastructure mailing list
infrastructure(a)lists.fedoraproject.org
http://lists.fedoraproject.org/postorius/infrastructure@lists.fedoraproject…
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi all,
A quick update on the Fedora Infra cloud situation:
as of yesterday, 2015-09-10, we no have just one cloud setup remaining.
The "old" cloud (nodes fed-cloud01 through fed-cloud08) have been deprecated
and uninstalled.
We now only have the Fedora Infra Cloud, available at https://fedorainfracloud.org/
remaining. If you had an account on the old setup and need an account on the new
setup, feel free to get in touch with me.
- --
With kind regards,
Patrick Uiterwijk
Fedora Infra
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCgAGBQJV8y6uAAoJEIZXmA2atR5QtXwP/1B5HRjdei/CKIWlNoh+GTPC
5Gv1cuEeAgOjueYUtTR8jhpf2GuGe9wgqzlLLs1+0sZOBAj+1NKJkgXU2gEdyfNj
H9UHnfcUbdVjsG1S/Jgzo4nCmvlZEkrBc1LQXCr3uvXweOFUI+8Xh2+yXEzFtbm8
ufJhr2eHkGElszMUdXlJ1A5F12rk85mui/VlOfOkv6UIpmZ0bjmyVdFxlXoZnFq4
ZxXW+Js2WbzMZZ14/DzjO5sFt0nNH+x5nt71u0Qrxg97S42+VzlMlAzd2FnMPMr9
wKg9+7jIqoujvDI7kcwa/ep/bS4G6Rg+e6CDPPxM4ALezvr8GYyBKgyO+KyYQEn9
MFEvKRW/7WCxknyjbfmnSxEJSpnHlR14Lf4IaUjeGPh9ejl74wvio05x0jZZdv/i
SmvCbAHlARgEL+Cw2HDA9qnNIwMV4TUnpWPWlGPLSbLjOvpKLcx4KUEA7g+KwyGo
M/t+RujACUsvj4nVmXTgSoyJWmThSfDTa6Def3OoXJRHc4hdwMXXVdIErAB2n6HQ
Dr1zqizw8kBAfc2myxQburKpCeaZUvognM2dN9QzJCQtiEhxG6E4B63SB9/T6Jxg
3cOxn2ngLKMbJjHLfCtl4ZYSN/8zBn6w2UPi91fzo+AxVBCkgOQ6o0n9A/Kbdq4j
bEgxZ8ROGq9KDt1my2hT
=Bo0E
-----END PGP SIGNATURE-----
_______________________________________________
infrastructure mailing list
infrastructure(a)lists.fedoraproject.org
http://lists.fedoraproject.org/postorius/infrastructure@lists.fedoraproject…
Dear Bugzilla User,
On September 20th we will be upgrading the hardware and database of the production Red Hat Bugzilla servers. The upgrade forms part of our Bugzilla Performance Improvement Project.
We expect the hardware upgrade will provide a modest improvement to overall performance and will enable us to make further improvements in the future; with the enhanced operational flexibility in the maintenance of the hardware and software platform. In addition to upgrading the hardware, we will also change the underlying database from MySQL to PostgreSQL, to further improve performance and handle the increasing workloads that Bugzilla imposes.
Both hardware and database upgrades are not intended to change the functionality offered by the Red Hat Bugzilla user-interface (except the new product widget and the component widget on such pages as the advanced search page) or the RPC APIs.
Outage Timing:
An outage, beginning on September 20, 2015, 0:00 UTC and lasting between 10 and 14 hours is needed to migrate the data from the current (old) system to the new production system and to verify that everything is working correctly before the new system goes online.
Stay Informed:
For more information please refer to the Bugzilla Hardware Upgrade FAQ [1]. If you are not already subscribed to Bugzilla Announcements list, please do so at [2] to receive any further announcements.
Thank you,
The Red Hat Bugzilla Team
[1] https://bugzilla.redhat.com/docs/bugzilla-upgrade-faq.html
[2] http://www.redhat.com/mailman/listinfo/bugzilla-announce-list
_______________________________________________
infrastructure mailing list
infrastructure(a)lists.fedoraproject.org
http://lists.fedoraproject.org/postorius/infrastructure@lists.fedoraproject…
Hi,
The idea of Fedora Search engine has came back with discussion about
https://fedorahosted.org/fedora-infrastructure/ticket/1055 ticket on the
meeting.
Many people was truly interested in participating in that project.
So, if somebody is still interested I propose to make some brainstorm
about that matter, so we could reach better results than years ago :)
First we can discuss in that mail thread and move then to irc or some
other place.
Regards,
Pawel Klos
_______________________________________________
infrastructure mailing list
infrastructure(a)lists.fedoraproject.org
http://lists.fedoraproject.org/postorius/infrastructure@lists.fedoraproject…
Here are a few possibilities I've found so far;
Apache Solr - http://lucene.apache.org/solr/
Features - "Solr is a standalone enterprise search server with a
REST-like API. You put documents in it (called "indexing") via JSON, XML,
CSV or binary over HTTP. You query it via HTTP GET and receive JSON, XML,
CSV or binary results."
It's a java servlet, which may be a mark against it. There are docker
images for it. To try out the Velocity Search engine, move the Velocity
.jar files into the server library, use the techproducts solrconfig.xml,
and start the server with bin/solr start -e techproducts. You can copy in
some html files to the exampledocs directory using wget to mirror a site,
then index the files with bin/post command.
Apache Spark - http://spark.apache.org/
"Apache Spark™ is a fast and general engine for large-scale data
processing."
Here is a use case for someone using it as a search engine;
http://www.maana.io/company/press-release/the-first-and-only-big-data-searc…
Just in scanning the docs, you can run it with java or python.
OpenSearchServer - http://www.opensearchserver.com/
Also runs on java - I haven't tried it out yet.
Sphinx - Free open-source SQL full-text search engine -
http://sphinxsearch.com/docs/current.html
(Haven't tried this either)
Here is a link to a recent tech blog with few other possibilities;
http://www.mytechlogy.com/IT-blogs/8685/tech-blogs-top-5-open-source-search…
--
irc #aikidouke
_______________________________________________
infrastructure mailing list
infrastructure(a)lists.fedoraproject.org
http://lists.fedoraproject.org/postorius/infrastructure@lists.fedoraproject…
The infrastructure team will be having it's weekly meeting tomorrow,
2015-09-10 at 18:00 UTC in #fedora-meeting on the freenode network.
We have a gobby document
(see: https://fedoraproject.org/wiki/Gobby )
fedora-infrastructure-meeting-next is the document.
Please try and review and edit that document before the meeting and we
will use it to have our agenda of things to discuss. A copy as of today
is included in this email.
If you have something to discuss, add the topic to the discussion area
with your name. If you would like to teach other folks about some
application or setup in our infrastructure, please add that topic and
your name to the learn about section.
kevin
--
= Introduction =
This shared document is for the next fedora infrastructure meeting.
We will use it over the week before the meeting to gather status and info and
discussion items and so forth, then use it in the irc meeting to transfer
information to the meetbot logs.
= Meeting start stuff =
#startmeeting Infrastructure (2015-09-10)
#meetingname infrastructure
#topic aloha
#chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk pbrobinson
#topic New folks introductions / Apprentice feedback
= Status / information / Trivia / Announcements =
(We put things here we want others on the team to know, but don't need to discuss)
(Please use #info <the thing> - your name)
#topic announcements and information
#info We are now in F23Beta FREEZE - no changes to frozen hosts without patch/ack - everyone
#info
= Things we should discuss =
We use this section to bring up discussion topics. Things we want to talk about
as a group and come up with some consensus or decision or just brainstorm a
problem or issue. If there are none of these we skip this section.
(Use #topic your discussion topic - your username)
#topic fas3 plans - kevin/smootherfrogz
#topic metalink timeouts/mirrormanager issues detection - kevin
#topic TRAC tickets review - p_klos
= Learn about some application or setup in infrastructure =
(This section, each week we get 1 person to talk about an application or setup
that we have. Just going over what it is, how to contribute, ideas for improvement,
etc. Whoever would like to do this, just add the info in this section. In the
event we don't find someone to teach about something, we skip this section
and just move on to open floor.)
#topic Learn about:
= Meeting end stuff =
#topic Open Floor
#endmeeting
_______________________________________________
infrastructure mailing list
infrastructure(a)lists.fedoraproject.org
http://lists.fedoraproject.org/postorius/infrastructure@lists.fedoraproject…