List membership
by Jim Campbell
Hi All,
tldr: I'm not sure how to unsubscribe. Please help me.
I had subscribed to this list some time ago, and then unsubscribed (or
least I think I unsubscribed) within the past few months. I think that
perhaps my email address still got pulled into the account setup under
the new HyperKitty platform, though, as I've started getting emails
again, and I don't know how to unsubscribe.
I hate to be the guy who sends a note to the list that says, "Please
unsubscribe me," but I guess that's what I'm doing. I know that I've
never set up a subscription to this mailing list using Google or Fedora
accounts, so I'm not sure how to proceed.
Can anyone help?
Jim
8 years, 8 months
Meeting Agenda Item: Introduction Javier Blanco
by Javier Blanco
Hi all,
I'm Javier Blanco from Madrid, Spain. Now I'm working as Infrastructure
engineer for a IT company and previously as Oracle/MySQL DBA and GNU/Linux
sysadmin. I haven't got too much free time but I would like to contribute
to fedora project with my knowledge and learning all I can.
Regards.
8 years, 8 months
Plan for tomorrow's Fedora Infrastructure meeting - 2015-08-20
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow,
2015-08-20 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-08-20)
#meetingname infrastructure
#topic aloha
#chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk pbrobinson
#topic New folks introductions / Apprentice feedback
#topic GSoC student update - kushal
= 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 Lots of discussion and such from flock, see list for items - kevin
#info Collapsed 16 lines in all our playbooks down to 1 include - kevin
#info Builders all updated and rebooted - kevin/dennis
#info new batcave01 instance setup, will take the place of lockbox01 sometime - kevin
#info lists.fedorahosted.org migration now friday - kevin/abompard
#info new apprentice 'quests' for new folks to get started easier - kevin
#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 new apprentice quests list - kevin
#topic fas3 plans - kevin/smootherfrogz
#topic TRAC tickets review - p_klos
#topic
= 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
8 years, 8 months
Re: July status update for Fedora Infrastructure Apprentices
by Kevin Fenzi
On Wed, 19 Aug 2015 16:49:09 -0400
Libert <katari(a)waynasolutions.com> wrote:
> Hi, me too
>
> On 17/08/15 02:04, Amitakhya Phukan wrote:
> > Hello all,
> >
> > <snipped>
> >
> > Not finding the August status update email. Have I missed it ?
> >
> > On Mon, Jul 13, 2015 at 8:16 PM, Ardian Haxha
> > <ardian.haxha(a)gmail.com <mailto:ardian.haxha@gmail.com>> wrote:
> >
> >
> > Amitakhya Phukan
> >
Perhaps I didn't send this to the list...
There was no email for Aug. ;)
We will resume with Sept 1st.
Thanks,
kevin
8 years, 8 months
Outage Report: ibiblio02.fedoraproject.org/proxy04.fedoraproject.org
by Stephen John Smoogen
1. What happened?
A new hardware server was put into our sponsor site Ibiblio
(ibiblio.org) and we were able to move servers around to a) take down
ibiblio01.fedoraproject.org and b) rebuild ibiblio02 to RHEL-7.
During this rebuild the proxy04.fedoraproject.org server was moved
according to the following steps:
a. take proxy04.fedoraproject.org out of dns
b. turn off old proxy04 on ibiblio01
c. build proxy04 on new server.
d. put proxy04 back into DNS.
Step c had multiple problems that needed to be debugged which extended
the outage time beyond the original 2 hours. Problem one was that the
host system had come up thinking it was inside of PHX2 and was trying
to reach iscsi server inside. Problem two was that the configuration
file referenced the wrong kickstart which caused additional downtime.
Problem three ended up with some ordering problems in the general
ansible playbook causing services to try to start before config files
were copied over. Problem four was a new python-fedora was pushed out
requiring a python-six which isn't in EL7 yet. These added up to going
over the timeframe originally allocated.
The final outage problem occurred after step D had been in place. Some
files on the system had the wrong permissions and were causing parts
of the website to be non-functional. This required taking the server
out of DNS, redoing permissions and rebooting. At this time additional
CPU and memory were added in case this was helpful.
2. What was affected?
Some users experienced bad websites while the http server said it was
up but was not able to serve pages.
3. How long was the outage?
Rebuild of server was 4 hours due to rebuild problems.
4. What was the root cause?
Multiple papercut problems extended the outage. A possible solution to
those would be to run a continual deployment mode of building a dev
proxy system, but that is outside the scope of this email.
A permissions problem on files caused them not to be readable. Running
a script to fix permissions fixed the problem.
--
Stephen J Smoogen.
8 years, 8 months
Flock discussions
by Kevin Fenzi
We talked about a number of things at our flock meeting, and a few
things we didn't get to.
Here's a summary. Please chime in if you think I summarized wrong or
you would like to add things or revist something. ;)
* Jenkins
- Finish migrating to the new cloud instance with the packaged jenkins
- Will will weaken the wording on the wiki page. We still don't want
people to depend on our jenkins for release critical stuff, but we
will want it to be more supported.
- Add nagios checks so we know when it's down/needing fixing.
* Finishing the puppet migration
- This week I will create the lockbox01 replacement (batcave01).
- Once we have that all ansiblized and ready, we will change it's
ip's to the current lockbox01 ips.
- Any machines still in puppet at that point will be marked "Don't
touch" and we will try and get them migrated. This will likely be
collab03 (mailing lists migrating off it to mailman01), and
hosted03 (until we finish rhel7 packaging work and migrate it).
- gobby (or something better if we can find it) will migrate to some
other host.
* bodhi2
- Deploy tomorrow.
- Once things are working we can retire releng04 and repele01
* Openstack plans:
- Move all instances to new cloud
- Add old cloud nodes to new cloud
- Install two old nodes with openstack Icehouse
- Upgrade the test instance to openstack Kilo(?)
- Upgrade main cluster to Kilo
* Continuous deployment
- May not have enough advantages to actually do continuous
deployment but the steps that enable it are useful
- work on those steps and then revisit in 6 months
- Automate ansible creation of new hosts
- Automate deployment of our apps
- Upgrade playbooks (Take service out
- Automate sign and import of packages
* Apprentice / on boarding discussion -
* make a set of quests to point people to:
* update CSI info
* Update docs templates
* others?
* Review in meetings easyfixes.
* Try and do a 'technical debt workdown' week after F23 is released.
Possibly also try 'docs update' or the like.
- Try one every 3 months or so.
* Docker/container prototype
* John Stanley containerized a sticky notes instance in the cloud for
us to look at.
Things we wanted to talk about, but did not get to:
* Released app process and repos. We actually did talk about this, but
didn't actually make any decisions. It sounded like we wanted apps to
have all their dependencies in EPEL, but they could be in the
infrastructure repo if they were fast moving?
* FAS3. Whats the timeline for migration?
* single-sign-on/single-sign out.
* Auth protocol
* Hubs development / prototyping
Anything else?
kevin
8 years, 8 months
[release] pkgdb2: 1.27
by Pierre-Yves Chibon
Good morning everyone,
I just made and push a new release of pkgdb2: 1.27
It's basically only bug fixes.
Here is the changelog:
* Tue Aug 18 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 1.27-1
- Update to 1.27
- Fix integration with anitya to not crash upon receiving invalid data
- Fix the upgrade_pkg_info script to rely on the configuration file
Running fine in stg and prod :)
Happy hacking,
Pierre
8 years, 8 months
July 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. Have you logged into our Gobby instance and read/seen/added to our
meeting agenda? https://fedoraproject.org/wiki/Gobby
9. What was the last game you played?
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
8 years, 8 months
Pagure for dist-git
by Pierre-Yves Chibon
Hi everyone,
Over the last couple of days, I created a test cloud instance, copied over a big
tarball containing all the git repos from dist-git and load them into pagure.
The results is there: http://209.132.184.205/
As you can see, it has a little less than 19k projects while we have more than
22k in dist-git the reasons being:
- I lost of git repos while adjusting the loading script
- The loading script ignored all the project not having a PoC in pkgdb (ie:
retired package)
There is still some work to be done to get pagure in a state that it can be used
for dist-git, but looking at it right now, it seems to be able to handle this
large number of projects.
If you are interested in working on adjusting pagure for dist-git, here are the
current tickets I filled for this:
https://pagure.io/pagure/issues?tags=pkgs.fp
Pierre
8 years, 8 months
Do Fedora apps follow some common UI design?
by Parag Nemade
Hi,
This email is with reference to bug
https://bugzilla.redhat.com/show_bug.cgi?id=1252806, I reported against
Copr UI.
First question is do we follow some common UI designs for Fedora
applications? What can be used for fas username links provided by some
Fedora apps at top right corner? Also, do all apps shows footer on main
page which also give information about which version that app is using?
e.g. møte app is not showing from which source version its
built/deployed.
Regards,
Parag Nemade.
8 years, 8 months
