Meeting Agenda Item: Introduction Nelson
by nelson
Hello everyone,
My name is Nelson and I am a systems administrator. I have approximately
13 years of general IT experience with the last 5 focusing mostly on
Cisco networking and Windows\Linux server technology.
I have roughly 1 year of hands on experience administering RHEL and
CentOS servers. I am also big fan of GNU\Linux desktop distributions and
actively use the Fedora and Ubuntu distros as my daily drivers.
I would love an opportunity to contribute to the Infrastructure team at
the Fedora Project. While I don't have much development experience I can
create good quality documentation, perform monitoring or any other
systems related maintenance tasks that are needed.
Looking forward to working with you.
My IRC handle is Neldogz
Thank you
-Nelson
9 years, 8 months
[Fedora] Plan Stage 0: Move to Zanata
by Noriko Mizumoto
(This mail is cc'd to Infra and websites teams as this activity may
impact Infra and websites teams.)
Hi all translators,
With all suggestions/ideas/info posted by all of you, I had first meetup
with zanata team to draft a plan to start with. I like to share the news
I got from zanata team here. I will update the plan page with the
following information later tomorrow. The move will occur in parallel as
suggested. The communication channels with zanata team are zanata-users
ML [1] and #zanata channel on freenode. Due to the limited
capacity/resource of zanata team, posting to ML would be appreciated
than pinging on irc.
I thank you so much to Zanata team!
Stage 0 - Establish Test Instance on Openshift
Available at: localized-zanatatest.itos.redhat.com
Period: 4 weeks
* This is trial run. Log in with FAS account and create new zanata
account, and play. It is important to be loud and file a bug for any
request [1]. Please make sure to append "[Fedora]" at the beginning of
the subject. This will give a bug priority ;p
E.g. [Fedora] Organization feature is needed.
Stage 1 - Establish fedora.zanata.org (FAS only instance)
Available at: TBA
Period: n/a
* This will contain only essential items, no history is imported. First
every language coordinator needs to create new account and become your
team coordinator. And then the coordinators will help and approve other
translators to join. Note, there is no auto or transparent migration.
Stage 2 - Import history and Add features requested
Available at: TBA
Period: n/a
* History (such as reviewed marks, notification, translator credit per
msg) and any additional feature requested (and approved) will be
migrated. It is essential to evaluate and decide what level of history
to be imported (or may be given up).
[1]:https://bugzilla.redhat.com/enter_bug.cgi?product=Zanata
cheers
noriko
9 years, 8 months
MirrorManager/FAS FAD in December
by Pierre-Yves Chibon
Hi all,
At Flock while discussing on how to proceed with the MirrorManager2 port we
thought that having a FAD to which we could get Matt Domsch (MirrorManager 1
author), seat all down and see what is done and what remains and what we can
change would be a good thing.
We also thought that combining it with a FAS hackfest might be good, with the
idea to make FAS3 a drop-in replacement for FAS2 from a feature point of view.
That would give us a good basis upon which to improve FAS the way we want.
Kevin asked Matt if he would have time to join for a FAD and Matt Domsch replied
that early December would work for him.
That's also a good period for me.
So using the Bodhi2/Taskotron FAD page as a template I created on for a
MirrorManager2/FAS3 FAD in Denver in early December:
https://fedoraproject.org/wiki/FAD_MirrorManager2_FAS3_2014
Feedbacks welcome and feel free to have a look, add yourself and adjust the page
as needed :)
Cheers,
Pierre
9 years, 8 months
Creds needed for Rackspace, GCE, and HP cloud image uploading, etc.
by David Gay
Hi,
As per our cloud meeting today, here are the credentials I need in order to work with Rackspace, GCE, and HP, as far as I know:
Rackspace: user, API key
GCE: email, key, and project ID
HP: user, password, tenant name
I also need credentials for our internal Openstack, which is my first priority.
If anyone knows of other services that we use along with these (excepting EC2, which is already done), please let me know.
In the case that a service does not provide a good way to programmatically register images so that they are available to others, we'll have to work that out, as well.
-- oddshocks
9 years, 8 months
mailman0{1,2} are not on the VPN
by Aurelien Bompard
Hey people!
Apparently the two newly-rebuilt-on-RHEL7 mailman servers are not on the
VPN, so collab03 can't forward web requests to them. Could someone fix that
please (or show me how to do it)?
Thanks!
Aurélien
9 years, 8 months
Aug status update for Fedora Infrastructure Apprentices
by Kevin Fenzi
Greetings.
Sorry for the delay in sending this month. :(
You are getting this email because you are in the 'fi-apprentice' group
in the fedora account system (or are reading this on the
infrastructure list).
Feel free to reply just directly to me, or cc the infrastructure list
for everyone to see and comment on.
https://fedoraproject.org/wiki/Infrastructure_Apprentice
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
you.
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
to more?
3. Have you looked at or been able to work on any of the fi-apprentice
'easyfix' tickets?
https://fedorahosted.org/fedora-infrastructure/report/14
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. What is your favorite bread?
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!
kevin
9 years, 8 months
Plan for tomorrow's Fedora Infrastructure meeting (2014-08-14)
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow,
2014-08-14 at 18:00 UTC in #fedora-meeting on the freenode network.
Suggested topics:
#topic New folks introductions and Apprentice tasks.
If any new folks want to give a quick one line bio or any apprentices
would like to ask general questions, they can do so in this part of the
meeting. Don't be shy!
#topic Applications status / discussion
Check in on status of our applications: pkgdb, fas, bodhi, koji,
community, voting, tagger, packager, dpsearch, etc.
If there's new releases, bugs we need to work around or things to note.
#topic Sysadmin status / discussion
Here we talk about sysadmin related happenings from the previous week,
or things that are upcoming.
#topic nagios/alerts recap
Here we go over the last weeks alerts and see if we can find ways to
make it so they don't happen again.
#topic Upcoming Tasks/Items
https://apps.fedoraproject.org/calendar/list/infrastructure/
#topic Open Floor
Submit your agenda items, as tickets in the trac instance and send a
note replying to this thread.
More info here:
https://fedoraproject.org/wiki/Infrastructure/Meetings#Meetings
Thanks
kevin
9 years, 8 months