You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2014-11-19 from 19:00:00 to 20:00:00 UTC
The meeting will be about:
Standing meeting for the Fedora Cloud Workgroup
So - the good news is that we are tantalizingly close to a good build
for the Atomic image. (We're missing the docker-storage-setup package,
and I think it's missing the config to pull in updates using atomic update.)
The bad news is that it's also tantalizingly close to Wednesday, which
is just shy of Thursday, which doesn't give us sufficient time to
promote a test day for this week.
We have gotten far enough that I feel pretty confident that, barring the
apocalypse, we will be able to have a test day on Thursday the 20th.
(And, should the apocalypse come before then, we'll presumably be too
busy to really care about missing the test day.)
Have moved the test day page to reflect this:
Still need to update it, but that's on the to-do for this week. Part of
the fun of living life on the leading edge - we get to document it all,
Joe Brockmeier | Principal Cloud & Storage Analyst
jzb(a)redhat.com | http://community.redhat.com/
Twitter: @jzb | http://dissociatedpress.net/
I've attached a signed text file containing a list of AMIs for the recent Atomic-20141112-21.x86_64 build.
The Koji task for this build can be found here: http://koji.fedoraproject.org/koji/taskinfo?taskID=8118904
Please let me know if there are any issues, or further action I can take on these builds.
Back in late October we agreed that not having AMIs uploaded was something we
should block on , but I felt like the "must boot" criteria didn't really
fit. I proposed to the cloud WG  a new criteria: "Cloud images must be
available in the following supported service registries: Amazon EC2."
I wanted to get feedback from the QA team regarding this potential criterion and
where it might fit. I think at alpha so we can get as much testing as possible.
The discussion thus far can be found on the Cloud groups trac.
If you could post your comments, votes on adding this, etc on the trac ticket
I would appreciate it. Using the trac makes it so people from the Cloud WG can
answer any questions/issues QA might have since not everyone is subscribed to
Untested, but I think this will fix the Atomic compose.
CC'ing fedora-cloud as my patch also touches the invocations
for mainline cloud as well as the docker base image.
We need to specify --version to ensure the build host is
allowed to use kickstart syntax from the target version.
Remove the >& /dev/null as we'd like to be able to debug if it's
scripts/build-cloud-images | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Initial cut: https://fedoraproject.org/wiki/Changes/AtomicHost
Notably, adding bare metal (already working) and vagrant boxes (have prototype code), and I'd like to do a diskless Live PXE image (code exists, need to put it together and polish).
This is kept in the Cloud group, but I think the division between Cloud/Server here is going to become rather arbitrary and weird. Oh well.