firewall blocking atomic01.qa access to RHN/registry.access.redhat.com
by Colin Walters
Hi,
I'm trying to set up a Docker/Kubernetes/Atomic cluster in VMs on atomic01.qa to prototype out some alt.fp.org rel-eng work - using RHEL7 Atomic, but not being able to access subscription.rhn.redhat.com or registry.access.redhat.com is a pain.
Is there a reason this is being blocked?
In the more medium term I'd like to use some of the resources from the new OpenStack cloud, potentially returning this machine to the pool for other work.
In general for Fedora infra machines, it looks like the RHEL installations are configured to use a local mirror, and aren't subscribed, right? If we go down that path, can we set up a mirror of the Docker registry and the Atomic Host ostree repo? The former is a bit tricky, the latter is a two line shell script that would need to be cron job'd somewhere.
7 years, 11 months
[release] MirrorManager2: 0.0.8
by Pierre-Yves Chibon
Hi everyone,
I just tag and build a new MirrorManager2 release: 0.0.8.
Here is the changelog:
* Thu Apr 23 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.0.8-1
- Update to 0.0.8
- Make MM2 a little prettier on high-res display
- Add a Location tag for static (Patrick Uiterwijk)
- Fix the DB session issue on the crawler (Adrian Reber)
- Add some documentation on how MirrorManager works
- Decrease time required for set_not_up2date() (Adrien Reber)
- Add support to auto disable mirrors (Adrien Reber)
- Auto disable hosts which have a URL configured but which does not exist
(Adrian Reber)
- crawl_duration is a host specific property (Adrian Reber)
- Handle lighttpd returing a content length for directories (Adrian Reber)
- Scan the directories which are supposed to be on each mirror (Adrian Reber)
- Use Yesterday's date on mm2_get_internet2_netblocks to avoid TZ issue (Adrian
Reber)
- Fix logging in the UMDL script (Adrian Reber)
- Allow the UMDL to crawl only a specified category (Adrian Reber)
- Fix example fedmsg config (Ralph Bean)
I will rebuild all the mm-*.stg hosts which will therefore get this new release.
Pierre
7 years, 11 months
Plan for tomorrow's Fedora Infrastructure meeting (2015-04-23)
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow,
2015-04-23 at 18:00 UTC in #fedora-meeting on the freenode network.
This week we are continuing to try something new.
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 this
morning 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-04-23)
#meetingname infrastructure
#topic aloha
#chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk
#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 22 Beta is out! - kevin
#info Another re-install cycle of new cloud, hopefully last one - msuchy, smooge
#info Mediawiki 123 hopefully going to staging soon - patrick
#info Moved kojipkgs squid to use 8 threads instead of 1 - kevin
#info Updated squid on kojipkgs to fix ssl cert chain issue - kevin
#info Disabled lvmetad on all virthosts, it causes caching issues - 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
= 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 skip to open floor.)
#topic Learn about:
= Meeting end stuff =
#topic Open Floor
#endmeeting
7 years, 11 months
Bugzilla components of retired packages
by Michael Cronenworth
Can we get retired packages out of the active Bugzilla component list?
I just created a bug for a retired package and had to fix it...
Bugzilla allows components to be disabled rather than deleted in case the bugs need
to be searched for or a package comes out of retirement.
Unfortunately the only way I see to automate this process is the REST API in 5.0.
Thanks,
Michael
7 years, 11 months
Fedora 22 Beta Freeze now in effect
by Kevin Fenzi
Greetings.
we are now in the infrastructure freeze leading up to the Fedora 22
Beta release. This is a pre-release freeze.
This means that hosts that are marked as freezing should not have any
changes made to them except as part of a freeze break request
(see below)
We do this to make sure that our infrastructure is stable to allow for
building/composing/testing and distributing Fedora 22 Beta. This
freeze will end 1 day after Fedora 22 Beta is released.
(Currently scheduled for 2015-04-14)
Freeze breaks should be sent to this list, clearly describing the
planned change and include patches (if applicable). Freeze breaks
should not be applied until they have gotten at least 2 +1's from
members of sysadmin-main and/or releng groups.
You can see a list of hosts that do not freeze by checking out the
ansible repo and running the freezelist script:
git clone http://infrastructure.fedoraproject.org/infra/ansible.git
scripts/freezelist -i inventory
Thanks,
kevin
7 years, 11 months
Reprovision of nodes of new Fedora-cloud
by Miroslav Suchý
Stephan,
can you please reprovision fed-cloud09-15? I.e. both controller and all
compute nodes.
I'm ccing mailing list so if you experimenting with FC, you know why
your VM are gone. There should be none production VM.
It may be final version, but I'm not sure, because I made some changes
to packstack, which I could not test right now. So it may be final or I
may request one more reprovision.
Once declared final, I plan to do Fedora classroom for everybody who
want to learn how it is set up, what you can do and what you should not do.
Mirek
7 years, 11 months
MM2 status
by Pierre-Yves Chibon
Hi everyone,
So it seems the last update of MM2 has fixed the issue I was seeing from time to
time of the application becoming unresponsive due to DB hanging.
So here is the current status as far as I see it:
* Mirrorlist -> In prod and apparently fine
* MM2 UI -> Running in stg and seems all good to me
* Crawler -> Adrian Reber has put some great work on this, afaics he seems to
have fixed the biggest issues but I'll let him confirm if everything works now
or not
(@Adrian, I know there are features you want to make to the crawler but let's
get it working as it is for 1.0 and improve it afterward ;-))
* Pickle generation -> code wise I believe it works the question is: does it
generate the same pickle as MM1
! Crons: iirc there are still a couple of crons that are not running properly
and returning errors
So what I would like to do at one point is:
* Freeze the DB on MM1
* Generate a pickle -> save it
* Sync the DB over to stg (covert it as needed)
* Unfreeze the DB on MM1
* Have MM2 generate a pickle with this new data
* Compare the two pickle files
This sounds to me like the easiest way of comparing if both applications behave
in the same way.
Thoughts?
Pierre
7 years, 11 months
Flock 2015 taskotron/infra workshop idea
by Martin Krizek
Hi,
with deadline for submitting talk proposals for Flock 2015
approaching, we, Fedora QA, thought of an idea of doing
a workshop/hackathon with Fedora Infra.
Some ideas to discuss including (but certainly not limited to):
- taskotron fedmsg emission
- rawhide testing (no bodhi updates)
- figuring out logic (and its place) of deciding what updates
to push based on (which) test results
- *your idea*
This is something we've been brainstorming and figured
we'd ask here before going further with it. Is
something like this useful/interesting for you guys
in Infra to do? Are enough of you going to be at Flock?
Any other thoughts?
Thanks!
Martin
7 years, 11 months
