#76: Explore possibility of shipping preconfigured KVM cloud image on live DVD
--------------------+--------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Keywords:
--------------------+--------------------
I suggested this for Fedora Server, and Josh mentioned to me that we could
do it for the cloud.
What about prepackaging the cloud image on-disk with a live Workstation-
based image, with an existing KVM configuration including a preconfigured
config-drive allowing SSH access to the local user.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/76>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#71: libmicrohttpd is back as a systemd dependency
--------------------+--------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Keywords:
--------------------+--------------------
This was gone from F20
(https://bugzilla.redhat.com/show_bug.cgi?id=908081) but is back now.
As noted in this bug, it is undesirable because libmicrohttpd pulls in
gnutls (and nettle) , which is not otherwise on the base image. Reducing
the number of crypto libraries there by default reduces the need to respin
off-cycle security updates -- this is not an abstract concern.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/71>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#60: Enable serial console for bootloader
---------------------+--------------------
Reporter: fabiand | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Keywords:
---------------------+--------------------
The bootloader of the current cloud images is not attached to a serial
console.
Please change this, so we can also follow the bootloader part on the
serial console, i.e. for test automation.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/60>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#53: anaconda doesn't allow installation of current fedora-cloud-base.ks
---------------------+--------------------
Reporter: walters | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Keywords:
---------------------+--------------------
Cloud images are expected to come with:
* root password locked
* No user precreated; instead, an agent (cloud-init, min-metadata-service)
pull config data from the hypervisor and inject ssh keys, create users,
etc.
The problem is Anaconda's user.py is a mandatory step.
A suggested hack is to set a root password, then unset it in %post.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/53>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#44: hey we should have a vagrant base box
--------------------+--------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Keywords:
--------------------+--------------------
This is a very long-standing request. Here is a ticket for it. :)
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/44>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#23: File F21 change: Re-factor cloud-init
------------------------------+------------------------------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 21 (Feature Deadline)
Component: Cloud Base Image | Keywords:
------------------------------+------------------------------------------
'''Summary:''' Cloud Init was initially designed for a different
distribution and is only loosely tailored for our needs. As it stands, it
pulls in a rather large set of packages not used for other things. It is
also written in Python, itself a large subsystem which it would eventually
be nice to leave out of the base. Effort is moderate, with some low-
hanging fruit which may be addressed easily.
'''Importance:''' vital long term, but just moderate for F21 (We really
need this, but if we don't get work it now, it's in acceptable shape for
this release.)
'''Timeframe:''' F21 alpha, or F22 / if we don't make alpha with changes,
this can go in next release.
'''Scope:''' Self-contained
'''Cloud SIG owner:''' TBD
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/23>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#34: External need: batched updates
--------------------+------------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Flock 2014
Component: --- | Keywords:
--------------------+------------------------
'''Summary:''' We want to produce updated images on a monthly cadence. It
would be nice if we could produce those from QA'd bunches of packages.
'''Importance:''' moderate (it will be hard to implement image refresh
without this, but we could do it)
'''Timeframe:''' F21 release + 1 month / Obviously better if we get things
lined up earlier
'''Fedora Sub-Project/SIG:''' Primarily QA, but Rel Eng and Infrastructure
too. This is pretty big.
'''
Cloud SIG owner:''' TBD (this probably needs someone actively contributing
to initial and ongoing work)
See the related Change proposal "(A)Periodic Updates to the Images"
http://flock2013.sched.org/event/8c4f702e42814598e0e4e31b188a0ae6
What's this ticket about? We need an owner for this ā someone to drive it
forward.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/34>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#81: Create cloud training materials for ambassadors
-------------------------------------------+-----------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 22
Component: Collaboration & Communication | Keywords:
-------------------------------------------+-----------------------
Many Fedora Ambassadors come from a desktop or old-school sysadmin
background. Cloudy concepts are new and foreign. In talking with some of
them, it was suggested that it'd be really, really helpful to have some
basic training materials for our own ambassadors -- what is cloud, why
does it matter, what is Fedora Cloud, what is our strategy, why do _we_
matter, and so on.
http://mattdm.org/fedora/cloud2013/#1 might be a starting point. Maybe
some more interactive training would even be useful.
Of course, it'd also be awesome to get some people from the new modern
world interested in being ambassadors as well -- another direction to
approach the same issue. (But even then, training on what _we_ are doing
would be useful.)
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/81>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#38: Automatic Smoketests on Image Build
--------------------------+-------------------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 21 (Alpha)
Component: Testing & QA | Keywords:
--------------------------+-------------------------------
'''Summary:''' When a new image is built in Koji, automatically boot it
and run a basic matrix of tests.
'''Importance:''' moderate (worst case, we can keep doing this by hand)
'''Timeframe:''' F21 alpha / Want to reduce manual test workload
'''Fedora Sub-Project/SIG:''' QA and the Taskotran project
'''Cloud SIG owner:''' Sandro Mathys
https://fedoraproject.org/wiki/Taskotron
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/38>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System