#155: Decide on post-GA update cadence for various deliverables
-------------------------+---------------------
Reporter: maxamillion | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Keywords: meeting
-------------------------+---------------------
Currently there are plans to update release deliverables more formally
post Fedora 24 GA. These aren't all going to happen immediately following
the release but work will be done to enable them ASAP.
Some of these we've already decided on in the past but a couple still need
decisions. The goal here is to simply determine what we would like to see
as an ideal release cadence of updated deliverables. Technical
implementation and details will be outside this scope.
https://fedoraproject.org/wiki/Fedora_Program_Management/Updating_deliverab…
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/155>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#144: f23 atomic iso configures docker loopback storage
-------------------------+--------------------
Reporter: jasonbrooks | Owner:
Type: defect | Status: new
Priority: major | Milestone: Future
Component: --- | Keywords:
-------------------------+--------------------
ISO installs of f23 atomic get configured w/ loopback storage, which is a
bad thing: http://www.projectatomic.io/blog/2015/06/notes-on-fedora-
centos-and-docker-storage-drivers/.
F22 Atomic had the correct config.
Running "docker info" on a VM installed from Fedora-Cloud_Atomic-
x86_64-22.iso yields:
{{{
...
Storage Driver: devicemapper
Pool Name: fedora-docker--pool
Pool Blocksize: 65.54 kB
Backing Filesystem: extfs
Data file:
Metadata file:
...
}}}
Running "docker info" on a VM installed from Fedora-Cloud_Atomic-
x86_64-23.iso yields:
{{{
...
Storage Driver: devicemapper
Pool Name: docker-253:0-153054-pool
Pool Blocksize: 65.54 kB
Backing Filesystem: extfs
Data file: /dev/loop0
Metadata file: /dev/loop1
...
}}}
I looked over the kickstarts, but I'm not clear on what might be causing
this.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/144>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
Hi all,
As discussed over the list, I have a stage setup for our trac tickets
moved into Pagure [1]. Please have a look.
When we will move into the production pagure, all of us (who ever
commented on a trac ticket ever) will get a flood of fedmsg(s) :)
I will require a permission to do that amount of flooding :)
[1] https://stg.pagure.io/atomic-wg/issues
Kushal
--
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.inhttps://dgplug.org
#167: Decide a process about failed tests for Autocloud
--------------------+---------------------
Reporter: kushal | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Keywords: meeting
--------------------+---------------------
If we have a test failing the compose (right test, catching a real bug),
should we stop the release till the time the bug gets resolved?
My personal opinion is yes, first fix, and then only go ahead.
For example [https://apps.fedoraproject.org/autocloud/jobs/353/output#283
this test] fails time to time on the vagrant virtualbox image.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/167>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
I see Fedora Rawhide, just Fedora (cloud base, I assume) 25, and Fedora
Atomic 24 in https://apps.fedoraproject.org/autocloud/compose?limit=20.
Shouldn't there also be an Atomic 25 branch by now? (Shouldn't there be
one starting with branching, for that matter?) Or am I just missing it?
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
Hi Cloud/Atomic WG,
I would like to request review of the WG deliverables for Fedora 25
release. The list of deliverables is available on wiki:
https://fedoraproject.org/wiki/Fedora_Program_Management/ReleaseBlocking/Fe…
Please let me know, or edit the wiki page, in case there are missing
deliverables or the current ones have wrong blocking status.
There is going to be overall review done by FESCo, probably on
2016-Sep-30 for all the blocking deliverables.
Thanks and Best Regards,
Jan
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
Dear all,
You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2016-10-05 from 17:00:00 to 18:00:00 UTC
At fedora-meeting-1(a)irc.freenode.net
The meeting will be about:
Standing meeting for the Fedora Cloud Workgroup
Source: https://apps.fedoraproject.org/calendar/meeting/1999/