The infrastructure team will be having it's weekly meeting tomorrow,
2016-04-07 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.
= 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 (2016-04-07)
#chair smooge relrod nirik abadger1999 lmacken dgilmore 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 Production to staging FAS has been synced - kevin
#info retrace and faf staging hosts are live - kevin
#info postgresql tuning on non dedicated db hosts done - kevin
#info bunch of ansible cleanup patches from misc. Thanks misc!
#info kojira/koji db issues continuing, needs more investigation - kevin
#info epel5 repodata issue, hopefully solved now - kevin
#info Outages next week likely tue/wed for updates/reboot cycle - kevin
#info outage friday for openstack cloud - patrick
= 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 new rsync setup soon - smooge / kevin
#topic <yourtopic> - yourname
= 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.)
unknown. Sign up now?
#topic Learn about:
= Meeting end stuff =
#topic Open Floor
From: Michael Scherer <misc(a)zarb.org>
CONVENTIONS | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/CONVENTIONS b/CONVENTIONS
index f6c2eec..f6b37fe 100644
@@ -9,7 +9,7 @@ Playbook naming
The top level playbooks directory should contain:
-* Playbooks that are generic and used by serveral groups/hosts playbooks
+* Playbooks that are generic and used by several groups/hosts playbooks
* Playbooks used for utility purposes from command line
* Groups and Hosts subdirs.
@@ -95,7 +95,7 @@ We would like to get ansible running over hosts in an automated way.
A git hook could do this.
* On commit:
- If we have a way to detemine exactly what hosts are affected by a
+ If we have a way to determine exactly what hosts are affected by a
change we could simply run only on those hosts.
We might want a short delay (10m) to allow someone to see a problem