#56: tracking ticket for conversations around shipping ostree images
-------------------------------------------+-------------------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: blocker | Milestone: Fedora 21
Component: Collaboration & Communication | (Branch)
| Keywords:
-------------------------------------------+-------------------------------
We've decided to base the Fedora Docker host image on Project Atomic, and
therefore rpm-ostree. This means several big conversations, including with
QA, Rel Eng, and the mirror network. It will mean some new development and
possibly extra resources. But first we need to figure out the questions to
ask, and then we need to ask them, and then we need to find answers, or
provide them where they don't already exist.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/56>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#13: Port Cloud Image Kickstart to anaconda/imagefactory
------------------------------+-----------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 21
Component: Cloud Base Image | Keywords:
------------------------------+-----------------------
Rel-Eng is updating to Koji 1.9, which will allow us to use Anaconda and
ImageFactory for image creation instead of appliance-creator.
* What: The current kickstart file is full of kludges for appliance-
creator. Port to anaconda/imagefactory kludges
* Where: same as ongoing maintenance of kickstart
* Why: appliance-creator is being retired; anaconda-based installs are the
way forward
* When: As soon as this is available in Koji. Need a new ImageFactory
release, then patches into Koji for support, then a new Koji release, then
Koji needs to be updated in Fedora production
* Who: Ian McLeod is working on ImageFactory; Jay Greguske on the Koji
patches, Mike McLean is Koji maintainer, Dennis Gilmore in release
engineering will do the Koji update. Need to work with them to get this in
place, and then someone from cloud wg needs to do the updating.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/13>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#69: Fedora Cloud image boot: Y U SO SLOW?
------------------------------+-------------------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 21 (Alpha)
Component: Cloud Base Image | Keywords:
------------------------------+-------------------------------
In openstack using June 26th rawhide
(http://koji.fedoraproject.org/koji/taskinfo?taskID=7078357) boot is
really slow. It's about 25 seconds (as per the boot log) to a command
prompt, but another 20 seconds until the root resize is done, and another
20 before cloud-init completes.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/69>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#70: cloud-init output not going to the openstack log
---------------------+------------------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: blocker | Milestone: Fedora 21 (Beta)
Component: --- | Keywords:
---------------------+------------------------------
Some combination of "got something wrong in the kernel parameters or where
cloud-init is sending its output".
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/70>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#43: procedures and process for getting updated images onto mirrors
------------------------------+------------------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: blocker | Milestone: Fedora 21 (Beta)
Component: Software Updates | Keywords:
------------------------------+------------------------------
Right now, cloud images only get mirrored at GA release time. We need to
figure out how to ship updates.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/43>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#93: Getting sha256sum published for the cloud images
--------------------------------------------------+-----------------------
Reporter: kushal | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 22
Component: Infrastructure & Release Engineering | Keywords: meeting
--------------------------------------------------+-----------------------
This will help things systemd to search the images provided by Fedora in a
standard way using nspawn tool.
Example of such file from ubuntu:
https://cloud-images.ubuntu.com/trusty/current/SHA1SUMShttps://cloud-images.ubuntu.com/trusty/current/SHA256SUMS.gpg
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/93>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#88: Social Media for Dockerfiles
-----------------------------------+---------------------
Reporter: jzb | Owner: jzb
Type: task | Status: new
Priority: normal | Milestone: Future
Component: Docker Base Container | Keywords: meeting
-----------------------------------+---------------------
We need to work with marketing to tweet about things regularly. I'd like
to put out regular tweets to promote individual Dockerfiles. Thoughts?
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/88>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#94: Producing Updated Cloud/Atomic Images
------------------------------+---------------------
Reporter: dustymabe | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: Cloud Base Image | Keywords: meeting
------------------------------+---------------------
We need to finalize our policy around producing updated images and then
start doing it.
Right now we have loosely decided to release new images once a month or
whenever security updates require it.
Additionally, as part of this we should also decide on a policy that
determines when we stop updating images for a particular release. I
imagine that we don't want to be producing updated images for Fedora X, Y,
and Z all at the same time. Ideally we would only be producing updated
images for the current/latest major version.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/94>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#84: publicize fedora-dockerfiles
-------------------------------------------+-------------------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 21 (Final)
Component: Collaboration & Communication | Keywords: meeting
-------------------------------------------+-------------------------------
https://github.com/fedora-cloud/Fedora-Dockerfiles is
a) cool
b) useful
c) active
d) a great place for new contributors
We should popularize this. Articles, blog posts, wiki documentation, non-
wiki documentation, etc.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/84>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System