You are getting this email because you are in the 'fi-apprentice' group
in the fedora account system (or are reading this on the
Feel free to reply just directly to me, or cc the infrastructure list
for everyone to see and comment on.
At the first of every month(or so), I am going to be sending out an
email like this one. I would like feedback on how things are going for
I'd like to ask for everyone to send me a quick reply with the
following data or anything related you can think of that might help us
make the apprentice program more useful.
0. Whats your fedora account system login?
1. Have you logged in and used your fi-apprentice membership to look at
our machines/setup in the last month? Do you plan to?
2. Has it helped you decide any area you wish to focus on or contribute
3. Have you looked at or been able to work on any of the fi-apprentice
4. Do you still wish to be a member of the group? If not (for whatever
reason) could you provide any hints to help others down the road?
5. Is there any help or communication or ideas you have that would help
you do any of the above?
6. What do you find to be the hardest part of getting involved?
Finding things to work on? Getting attention from others to help you?
Finding tickets in your interest area?
7. Have you been able to make any weekly irc meetings? Do you find them
helpful or interesting?
8. Have you logged into our Gobby instance and read/seen/added to our
meeting agenda? https://fedoraproject.org/wiki/Gobby
9. Do you have any pets? If so, what, if not is there one you want?
Any other general feedback is also quite welcome, including
improvements to this email, the wiki page, etc.
Any folks I do not hear from in the next week will be removed from the
group. (Note that it's easy to be readded when you have time or
whatever and it's nothing at all personal, we just want to keep the
group up to date with active folks).
Thanks, and looking forward to your feedback!
The infrastructure team will be having it's weekly meeting tomorrow,
2016-05-05 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-05-05)
#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 fedora-atomic-sig and qa-tools-sig created - kevin
#info fullfiletimelist is live on mirrors - kevin
#info https://fedoraproject.org/wiki/Infrastructure/fas_freeipa FAQ written up - 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)
= Apprentice office hours =
Here we will discuss any apprentice questions, try and match up people looking
for things to do with things to do, progress, testing anything like that.
#topic Apprentice office hours
= 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
Over the years, a number of times, people have asked us about migrating
from our own custom Fedora Account System (FAS) to FreeIPA.
We would love to, but right now as things stand it's just not a great
fit for us. In the past we have had trouble articulating what the
issues are, but now Patrick has written up a wiki page with all the
items we know of:
Hopefully we can keep open a dialog with FreeIPA folks and keep the
above wiki page synced up so perhaps someday we can migrate when
blockers are no longer in our way. :)
so I found a bit of time to look again to the testbed of openshift
in the cloud (https://fedoraproject.org/wiki/Cloud/OpenShift_Origin_Testbed), and now there
is 2 atomic VM running, I realize that we didn't define exactly the details.
Since one of the goal is to use fedora atomic, the vm run fedora atomic. So far, so good.
On what is needed to deploy, we have:
- the master (so openshift itself)
- a docker registry (may requires some storage)
- a router (so haproxy managed by openshift)
- and various nodes to run conatiners (so kubernetes and/or etcd and docker)
Atomic come with kubernetes, etcd and docker pre installed. AFAIK, there isn't yet
So the first question is about the layout.
When the first idea were discussed, people did propose
to have 2 nodes for the master, 2 node for infra and all others as worker nodes, and maybe
add one storage node. That's likely a fair production setup, but we are not yet doing production
And discussing around in the office, my co-workers suggest that we merge the master and the router on
one single node. I would also suggest to skip HA for now, and keep for later. So the
proposed layout would be:
- 1 node, with a public IP, running the master, the router and the registry
- a few nodes behind running container
Then once that's working, start to make regitry be replicated (not too hard to do on openstack,
since it can use the block storage), make the router replicated and the master/openshift too.
Then come the question that currently kinda block me, about where does the binaries
need to come from.
As people might know, all stuff on atomic is either preinstalled,
or come from a docker container.
Openshift can bundle kubernetes and etcd, or can likely use external ones.
So we have to decide:
- does etcd come from atomic (ie preinstalled), or do we use the one bundled in openshift
- do we use a external registry (using the rpm), or a external registry using a container, or using the
one deployed by openshift ?
- do we want to use openshift coming from F24 in a container, or directly consume the one from
openshift upstream on docker hub ?
I am not sure what is the answer for all of this, because in the end, the policy of fedora infra are maybe
not suitable to decide for that, and I am not sure if the tooling is ready. For example, if we take openshift from
the rpm in a container, someone need to build that container.
Any toughts ?
(I will likely decide by fiat anyway, but without the illusion of having got feedback if people do not give it)
My name is Justin, IRC / FAS username jflory7. Some of you might have
seen me around other parts of Fedora. I am looking at becoming more
involved with the Infrastructure team.
Over the summer, I am planning on contributing to the Ansible playbooks
as part of Google Summer of Code. My primary objectives are to (1) merge
the Community Blog and Fedora Magazine into a shared core, and (2)
automate the deployment with Ansible, one of the very few things in
Fedora that is not powered by Ansible yet. Patrick (puiterwijk) is
mentoring me for my proposal.
The full details of my project proposal can be found on the wiki.
In terms of my current experience, I am a Networking & Systems
Administration student at the Rochester Institute of Technology. I have
about three years experience administrating CentOS/RHEL machines that I
have used for personal work. I am familiar with Java and am in the
process of picking up Python.
More information about me can also be found on my wiki page.
I'm planning on making it to the meeting today and have already added
some info to the Gobby meeting agenda pad. Looking forward to getting
more involved with the Infrastructure team!
Justin W. Flory
From: Michael Scherer <misc(a)fedoraproject.org>
sshaccess.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/sshaccess.rst b/sshaccess.rst
index 6bfcebe..b73043b 100644
@@ -50,7 +50,7 @@ First of all: (on your local machine)::
This file, and any keys, need to be chmod 600, or you will get a "Bad owner or
- permissions" error. The .ssh directorymust be mode 700.
+ permissions" error. The .ssh directory must be mode 700.
then, add the following::
@@ -109,7 +109,7 @@ Troubleshooting
IP could be added to denyhosts.
* If you are running an OpenSSH version less than 5.4, then the -W
- option is not avaliable. In that case, use the following ProxyCommand
+ option is not available. In that case, use the following ProxyCommand
ProxyCommand ssh -q bastion.fedoraproject.org exec nc %h %p
Basset's rabbit-mq is very chatty in logs, so I would like to apply the
following and run the logserver playbook:
diff --git a/roles/epylog/files/merged/weed_local.cf
b/roles/epylog/files/merged/weed_local.cf index db8ed07..7720ad5 100644
@@ -213,6 +213,7 @@ python2.*: mail from:.*
restorecond: Reset file context /etc/aliases.*
restorecond: Reset file context /var/db/shadow.db.*