#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
#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
#41: Write Initial QA Documents
--------------------------+--------------------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 21 (Branch)
Component: Testing & QA | Keywords:
--------------------------+--------------------------------
* '''What:''' Work out and write down structured test plans and test cases
and, if additional are necessary, release criteria / requirements.
* '''Where:''' Fedora Wiki
* '''Why:''' So testers know how to test, and QA overlords and rel-eng
know when the images are actually ready for release. Or maybe rather, when
they're not.
* '''When:''' Before the very first alpha release candidate (RC) of Fedora
21 is due.
* '''Who:''' Someone in cloud working group in collaboration with QA.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/41>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#36: Coordinate F21 / fedora next website
----------------------------+-------------------------------
Reporter: mattdm | Owner: jzb
Type: task | Status: new
Priority: normal | Milestone: Fedora 21 (Final)
Component: Website & Wiki | Keywords:
----------------------------+-------------------------------
'''Summary:''' Since we are now one of the three top level artifacts
Fedora produces, we want to emphasize our unique niche. Updated website
with new flashier branding, plus tools for selecting different images for
different use cases
'''Importance:''' vital (it's basically part of the whole exercise)
'''Timeframe:''' F21 release / arguably, having the web site up ''is'' the
release. And it'd be nice to have earlier, like at the alpha and beta
'''Fedora Sub-Project/SIG:''' Websites
'''Cloud SIG owner:''' Joe Brockmeier
https://fedorahosted.org/fedora-websites/ticket/248
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/36>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#65: crucial questions on Docker image deliverable
-----------------------------------+--------------------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 21 (Branch)
Component: Docker Base Container | Keywords: meeting
-----------------------------------+--------------------------------
Adam W asks some excellent questions here:
https://lists.fedoraproject.org/pipermail/devel/2014-June/199579.html
> What "Fedora" exactly is the image going to contain? Fedora Server?
> Fedora Cloud? Will it be a part of either of those products? If not,
> what is its status, exactly? Who's responsible for it? Is it considered
> a primary or frontline or whatever Fedora deliverable? Who's going to
> test it? How's it going to be promoted in relation to all our other
> deliverables?
I gave some tentative answers, but let's get them answered definitively.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/65>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System