You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2017-11-08 from 17:00:00 to 18:00:00 UTC
The meeting will be about:
Standing meeting for the Fedora Cloud Workgroup
# F27 Blocker Review meeting
# Date: 2017-11-06
# Time: ** 17:00 ** UTC
# Location: #fedora-blocker-review on irc.freenode.net
Hi folks! We currently have only one proposed freeze exception for
Fedora 27. However, in case more blockers show up over the weekend,
I'm scheduling a review meeting for Monday; if there aren't any,
I'll just run a very quick meeting where we don't do anything.
Note that daylight savings time ends in most of North America this
weekend, so we'll be changing the meeting time to 17:00 UTC. If
daylight savings ends (clocks go back) for you this weekend, the
meeting should be at the same local time as always. If you don't
observe daylight savings or it ends at a different time, the meeting
will be one hour later in your local time than it was last week.
If you have time this weekend, you can take a look at the proposed or
accepted blockers before the meeting - the full lists can be found
here: https://qa.fedoraproject.org/blockerbugs/ .
We'll be evaluating these bugs to see if they violate any of the
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F27 can be found on the
For more information about the Blocker and Freeze exception process,
check out these links:
And for those of you who are curious how a Blocker Review Meeting
works - or how it's supposed to go and you want to run one - check out
the SOP on the wiki:
Note that for the special case of the Server release being split from
the main release stream for Fedora 27, we have created separate Server
blocker tracking bugs and will be following the same basic process for
the Server release dates using those trackers.
Have a good weekend and see you on Monday!
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
You can grab the image download links and fill out the results here:
Unfortunately only half the AMIs uploaded:
Fedora-Cloud-Base-27-1.2.x86_64 EC2 (us-east-1) ami-acaa02d6 paravirtual gp2
Fedora-Cloud-Base-27-1.2.x86_64 EC2 (us-east-1) ami-00ac047a paravirtual standard
Fedora-Cloud-Base-27-1.2.x86_64 EC2 (us-west-2) ami-38b07b40 hvm standard
Fedora-Cloud-Base-27-1.2.x86_64 EC2 (us-west-1) ami-69586709 hvm standard
Fedora-Cloud-Base-27-1.2.x86_64 EC2 (sa-east-1) ami-68cfb704 hvm standard
Fedora-Cloud-Base-27-1.2.x86_64 EC2 (eu-west-1) ami-f564c58c hvm standard
Fedora-Cloud-Base-27-1.2.x86_64 EC2 (eu-central-1) ami-a067e2cf hvm standard
Fedora-Cloud-Base-27-1.2.x86_64 EC2 (ap-southeast-2) ami-6df41a0f hvm standard
Fedora-Cloud-Base-27-1.2.x86_64 EC2 (ap-southeast-1) ami-04612c67 hvm standard
Fedora-Cloud-Base-27-1.2.x86_64 EC2 (ap-northeast-1) ami-da963abc hvm standard
Fedora-Cloud-Base-27-1.2.x86_64 EC2 (us-east-1) ami-a9a800d3 hvm standard
I've opened a ticket to get this resolved: https://pagure.io/releng/issue/7126
NOTE: if you respond to this message please 'reply-all'.
I'd like to discuss firewalld on atomic host. Recently I was trying to
figure out the best way to explain to other users how to set firewall rules
on atomic host.
Usually I would say add your rules and then iptables-save, but on Atomic
Host docker has added it's firewall rules in there dynamically so if you iptables-save
you'll get a bunch of stuff that you don't want in your static configuration.
There are ways around this; manually create your config file, or use iptables-save
and then rip the docker stuff out. Either way it's a bit of a pain. I think
firewalld would make this easier on the user. Not sure of the pro/con ratio though.