Re: FAD proposal
by Paul W. Frields
This post[1] to rel-eng@ will also be of interest to folks working on
infrastructure and applications in Fedora.
On Thu, Feb 19, 2015 at 04:22:48PM -0500, Paul W. Frields wrote:
> One of Matthew Miller's goals for Fedora is to diversify our release
> deliverables. This is one reason the Fedora Engineering team is
> bringing on a full-time person soon to work on release tools. We want
> to contribute to the Fedora release engineering effort too (as opposed
> to simply asking existing folks to do more). :-)
>
> I would expect over the first month or two in that role, our release
> tools person will likely be:
>
> * looking at the field of deliverables needed, across not just the
> products but also at containers and Project Atomic needs
>
> * getting familiar with any current release processes as needed
>
> * discussion with stakeholders in the project, including rel-eng,
> mattdm, infrastructure, and others, on this list and elsewhere about
> requirements
>
> During this time, I'd expect there will be some decisions on process,
> architecture, etc. To kickstart development, I'd like to set up a FAD
> where key community members, including developers and release
> engineers, can start (or continue) working on actual code and
> supporting infrastructure.
>
> I started a wiki page here for interested people to sign up:
> https://fedoraproject.org/wiki/FAD_Release_Tools_and_Infrastructure_2015
>
> There are some proposed dates listed on the wiki page. None have been
> fully decided yet. I have preliminary approval from the FPL, and I'm
> awaiting OSAS input on budget availability, and any time restrictions
> from their POV. There is a good chance we will do this at the Red Hat
> Tower (HQ) in Raleigh, NC USA. The event will not be restricted to
> USA people, although we'll have to select a roster of people to meet
> goals.
>
> There's a specific section in the page for you to write your name and
> any restrictions on dates. This will help us make the best
> date/location plan.
> https://fedoraproject.org/wiki/FAD_Release_Tools_and_Infrastructure_2015#...
* * *
[1] https://lists.fedoraproject.org/pipermail/rel-eng/2015-February/019355.html
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
9 years, 2 months
puppet to ansible migration status (2015-02-20)
by Kevin Fenzi
Greetings.
I thought I would send out a little status on where we are with
puppet->ansible migration currently.
We are currently down to 28 machines left in puppet:
"app01.stg.phx2.fedoraproject.org"
I think the only thing left here is the websites building stuff.
We could move that to sundries01.stg and nuke it.
"bapp02.phx2.fedoraproject.org"
This needs the mm2 deployment to finish as well as the websites
building stuff. We could move that to sundries01 now I guess, but the
rest will depend on mm2.
"backup02.fedoraproject.org"
I have been keeping this around until our backup storage in RDU2 is
live. I was hoping that to have already happened, so I might rebuild
this somewhere and make it use rdiff-backup.
"bastion-comm01.qa.fedoraproject.org"
Need to schedule a time to rebuild this with qa folks.
"bodhost01.fedoraproject.org"
"proxy07.fedoraproject.org"
This needs to be re-installed. We may be able to get an unattended ks
to work on it now that we know some of the pitfalls better.
"collab03.fedoraproject.org"
"collab04.fedoraproject.org"
"hosted-lists01.fedoraproject.org"
I was hoping for hyperkitty/mailman01/02 to be live so we wouldn't need
to migrate these, but again I am loosing hope and we might just look at
making a mailman 2 playbook and migrating them to get it done.
"darkserver01.phx2.fedoraproject.org"
Needs kushal to confirm it's all working on rhel7 and then we can
reinstall.
"db02.stg.phx2.fedoraproject.org"
This needs the rest of the postgresql db's migrated to db01.stg and/or
dumped/restored from production. Then, it also needs new mediawiki and
paste so we can get rid of mysql. However, I fear that also will not
happen anytime soon, so I might make a db03.stg that is mariadb.
"db05.phx2.fedoraproject.org"
This was waiting for mediawiki and paste to move to postgres, but I
guess I will look at making a playbook and moving it to ansible/mariadb
before then sometime. Probibly after alpha.
"hosted03.fedoraproject.org"
"hosted04.fedoraproject.org"
I need to build out the trac stack on epel7 for this. I am thinking I
might try and do so during freeze if anyone would like to help out.
Then, we can look at moving them after freeze. They also will need
playbooks.
"internetx01.fedoraproject.org"
"proxy02.fedoraproject.org"
These need reinstall (but hosted-lists01 is also there, so it needs
migrating first).
"osuosl02.fedoraproject.org"
This has collab03 and hosted03 on it. Need to ansiblize them and move
them to osuosl03 and then we can reinstall this one.
"people03.fedoraproject.org"
Needs playbook. We could also look at migrating it somewhere else to
get it off the ibiblio servers we need to reinstall.
"releng01.stg.phx2.fedoraproject.org"
"releng04.phx2.fedoraproject.org"
"relepel01.phx2.fedoraproject.org"
I am going to work on these today/this weekend. They need to stay rhel6
due to bodhi1, but shouldn't be too hard to bang out playbooks for
them. If I can get them in time I would love to finish them before
freeze.
"serverbeach09.fedoraproject.org"
Smooge was going to do this one soon...
"secondary01.phx2.fedoraproject.org"
This one needs a playbook. Should be pretty easy if someone would like
to whip one up.
"torrent02.fedoraproject.org"
Needs figuring our our torrent seed software and seeing if there's any
chance there's something better out there. Also needs playbook.
"virthost-comm01.qa.fedoraproject.org"
Need to migrate everything off this and retire it. Should be able to do
so soon as we have virthost-comm04 up and ready. Might try and work on
these during freeze as well.
"ibiblio02.fedoraproject.org"
"ibiblio03.fedoraproject.org"
These need reinstall and it's going to be a bit tricky as the reinstall
from 6->7 needs a full wipe. We should hopefully be able to migrate
things around to 04 enough to do this as well as moving things we don't
need.
"lockbox01.phx2.fedoraproject.org"
This will be the last machine to leave the building. ;)
So, I am hoping to work on legwork during freeze and push again after
freeze to get more done. Ideally we could get this done before Beta
freeze if all the stars align. ;)
kevin
9 years, 2 months
[release] pkgdb2 1.23.995
by Pierre-Yves Chibon
Hi all,
To keep up with the good habit, here is today's pkgdb2 release: 1.23.994 and
since I am not sure I'll be able to make another one tomorrow, I did a second
one just after to be sure: 1.23.995 :-)
Changelog:
* Fri Feb 20 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 1.23.995-1
- Update to 1.23.995 (pre-release of 1.24)
- Fix the link to `My Requests` on the API documentation page
* Fri Feb 20 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 1.23.994-1
- Update to 1.23.994 (pre-release of 1.24)
- Do not use insecure connection to pkgdb in set_monitoring_status (Till Maas)
- Add documentation for the API endpoint to set the monitoring status of a
package
- Replace the monitoring toggle button by one that might be clearer
- Fix actually setting the monitoring flag of new package to True (and adjust
the tests for this)
Enjoy and as usual, feel free to complain :)
Pierre
9 years, 2 months
Meeting Agenda Item: Introduction Taehwan Kim
by TAE HWAN KIM
Hello
I would like to become a Fedora Infrastructure Apprentice.
My name is Taehwan Kim aspiring a python developer that want to work and
contribute to open source community such as fedora.
First of all, I have looked up Fedora apps several times, but I can't
figure out where to start exactly.
I am interested in project that python developer can participate to
contribute and learn from.
what about bohdi or badge? (I found those project uses python and
pyramid web framework)
9 years, 2 months
Plan for tomorrow's Fedora Infrastructure meeting (2015-02-19)
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow,
2015-02-19 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.
http://ur1.ca/jr7j4
#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, 2 months
About fresque
by Pierre-Yves Chibon
Hi all,
The subject has popped-up on the devel list this week again and I thought it
might be an idea to discuss it further.
Fresque [1] is the Fedora Review Server. Its aim is to get the package review off
bugzilla into its own dedicated application that will integrate directly with
git and fedora-review.
Aurélien has been the main developer on this application in fall while Stanislav
and I presented the idea at flock last year [2].
However, Stanislav has changed team and both Aurélien and I have been working on
other projects.
So an idea is that we could have someone working on fresque this summer.
As far as I can see, there are two options for this:
a) we could get a GSoC student
b) as far as I understood, the fedora engineering team will have an engineering
intern this summer
Any thoughts on the idea of having someone working on it?
Any preferences on whether GSoC or RH intern?
One constraint is that, if we want/consider trying to get a GSoC student we need
to update the wiki [2] with the project before tomorrow.
Thoughts?
Pierre
[1] https://github.com/fedora-infra/fresque
[2] https://fedoraproject.org/wiki/Summer_coding_ideas_for_2015
9 years, 2 months
[release] pkgdb2 1.23.992
by Pierre-Yves Chibon
Hi everyone,
One release aways keeps the doctor away (and Vít busy :)), so here is the new
one: 1.23.993
Changelog:
* Thu Feb 19 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 1.23.993-1
- Update to 1.23.993 (pre-release of 1.24)
- Drop the package name from the URL to edit a request (fix few bugs in the
process)
- If requested is a package admin, request is set to Awaiting Review
- Use secure=True against prod pkgdb in set_monitoring_status.py (Ralph Bean)
Hopefully this fixes all/most of the bugs Vít faced.
Thanks,
Pierre
9 years, 2 months
[release] pkgdb2 1.23.992
by Pierre-Yves Chibon
Hi everyone,
I have just released and pushed to staging a new release of pkgdb2: 1.23.992,
the third pre-release of 1.24
Here is the changelog:
* Wed Feb 18 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 1.23.992-1
- Update to 1.23.992 (pre-release for 1.24)
- Add a `My Request` tab in the main menu
- Adjust copyright year in the master template
- Monitor package set as True by default (Ralph Bean)
- Drop the branch from field when requesting branch for a package
- Add the possibility to Edit one's request directly via the `My Requests` page
- Increase the width of the field in the form to request a new package
This should address some of the concerns raised by Vít (Thanks!) :)
Feedback much appreciated :)
Pierre
9 years, 2 months
Feb status update for Fedora Infrastructure Apprentices
by Kevin Fenzi
Greetings.
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. Whats your favorite work of art?
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, 2 months
