#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
#68: support HVM instances in EC2
------------------------------+-------------------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 21 (Alpha)
Component: Cloud Base Image | Keywords:
------------------------------+-------------------------------
We currently only support Xen paravirtualized images (PV) in EC2. We need
to support HVM as well.
(This will require changes to our EC2 image production and upload process,
and may require changes to our bootloader code as well. Particularly, it
probably takes away our clever hack for providing different kernel
parameters in EC2.)
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/68>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#66: Create kickstart file
-------------------------------+------------------------------
Reporter: pfrields | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 21 (Beta)
Component: Docker Host Image | Keywords:
-------------------------------+------------------------------
What: Based on the Base Image's kickstart file, write an extended
kickstart file with the image-specifics.
Where: kickstart file is at https://fedorahosted.org/spin-kickstarts/
Why: No kickstart file, no image.
When: Before Fedora 21's first release candidates are built.
Who: Someone in cloud working group in collaboration with the Spins SIG
''(ported from task list at
https://fedoraproject.org/wiki/Cloud/Cloud_ToDo)''
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/66>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#74: Plan test days for Atomic image
--------------------+------------------------------
Reporter: jzb | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 21 (Beta)
Component: --- | Keywords: meeting
--------------------+------------------------------
Once we have a viable image we need to go ahead and plan a test day around
the image (or more). We're still delayed on alpha, but all signs are
looking good for next week's go/no-go meeting.
Will set a date or dates and start working on promoting that. Setting
milestone as "beta" for this as it's something that should happen before
the beta, but after alpha...
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/74>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#75: Article for Fedora Magazine on "state of cloud SIG/product" for alpha
release
----------------------------+-------------------------------
Reporter: jzb | Owner: jzb
Type: task | Status: new
Priority: normal | Milestone: Fedora 21 (Alpha)
Component: Website & Wiki | Keywords: meeting
----------------------------+-------------------------------
What it says on the tin - putting in a tracker ticket to work on this and
get it ready for the alpha release. Should go out simultaneously with the
alpha or maybe staggered by a day or two to keep interest high.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/75>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#51: start communication/collaboration on cloud image updates
--------------------+---------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Keywords: meeting
--------------------+---------------------
At today's FESCo meeting, FESCo approved
https://fedoraproject.org/wiki/Changes/%28A%29Periodic_Updates_to_Cloud_Ima…
but wants us to get started actually changing the hand-waving parts about
* policies (when exactly we will do off-cycle updates)
* QA expectations (the exact testing requirements)
* QA contribution (commitments to help with the automation and possible
manual testing)
* release engineering help (contributing scripts/code/effort as needed)
We really need people to sign up for each of these -- not necessarily to
do all the work, but to take ownership of the communication and
coordination for each.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/51>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#67: Notification of pending security updates on login
------------------------------+-------------------------------
Reporter: pfrields | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 21 (Final)
Component: Software Updates | Keywords:
------------------------------+-------------------------------
What: A system to display a count (or list?) of updates waiting to be
applied
Where: New code needs to be written.
https://bugzilla.redhat.com/show_bug.cgi?id=995537 could help.
Why: Helpful to users. Side-effect: we can count checkins.
When: nice by F21 release.
Who: (TBD)
''(ported from task list at
https://fedoraproject.org/wiki/Cloud/Cloud_ToDo#Docker_Host_Image)''
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/67>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#64: meeting agenda item/tracker for Project Atomic
--------------------+---------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Keywords: meeting
--------------------+---------------------
Weekly report on status/blockers/todos for Project Atomic in Fedora --
starting with image generation and ostree repos and building up from
there.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/64>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System