#104: Atomic PXE tree does not work for interactive installs
---------------------+--------------------
Reporter: walters | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Keywords:
---------------------+--------------------
Due to the change to *not* embed the content in squashfs (so that you can
use kickstart to download newer trees via HTTP), the simple:
virt-install --name f22-atomic-test --ram 2048 --disk size=8 -l
https://dl.fedoraproject.org/pub/alt/stage/22_TC2/Cloud_Atomic/x86_64/os/
breaks unless you use e.g. initrd-inject to add a kickstart.
This is hard to fix without actually having a Software UI in anaconda for
rpmostreepayload.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/104>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#103: bugzilla components for base image and Atomic Host
---------------------+--------------------
Reporter: walters | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Keywords:
---------------------+--------------------
https://git.fedorahosted.org/cgit/spin-
kickstarts.git/commit/?id=6ba647a663f09da4ba740eb99733a39cba58d204
shows that we really need a Bugzilla entries in Fedora for both the Docker
base image and the Atomic Host.
And to define the maintainers of them.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/103>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#89: Add Dockerfile Section to Downloads Page?
--------------------+--------------------
Reporter: jzb | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Keywords:
--------------------+--------------------
For discussion - should we add a Dockerfile section on the downloads site?
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/89>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#83: participation in OpenShift Commons
--------------------+---------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Keywords: meeting
--------------------+---------------------
Take a look at http://origin.openshift.com/commons
I brought up joining this to the board, and got the reasonable response of
"have you gotten the Cloud SIG committed to actually doing the
participation asked for?"
I've talked to a couple of people and I think there's sufficient interest,
but it seemed reasonable to ask formally if this is something we're
interested in. The actual formal requirements seem to be low:
> OpenShift Commons is open to anyone. We have no Contributor License
Agreement (CLA) or required donation to join. Instead we take each
organization at their word to be active participants in forums, Special
Interest Groups (SIGs), mailing lists and events.
and I think it'd be _great_ to have Fedora officially involved in that
way. What do you all think?
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/83>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#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