#142: disable deltarpms in cloud images
------------------------------+--------------------
Reporter: praiskup | Owner:
Type: task | Status: new
Priority: major | Milestone: Future
Component: Cloud Base Image | Keywords:
------------------------------+--------------------
IOW: What cloud environment has with internet connection?
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/142>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#130: Fedora Atomic Host installable tree needed
---------------------+--------------------
Reporter: adelton | Owner:
Type: task | Status: new
Priority: major | Milestone: Future
Component: --- | Keywords:
---------------------+--------------------
Since beaker currently has no support for provisioning bare disk images,
Fedora Atomic Host cannot be used / tested in that environment.
We'd need installer trees for Fedora Atomic to be generated besides the
images.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/130>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#111: Some F22 AMIs marked private
--------------------------------------------------+--------------------
Reporter: pfrields | Owner:
Type: task | Status: new
Priority: major | Milestone: Future
Component: Infrastructure & Release Engineering | Keywords:
--------------------------------------------------+--------------------
URL: https://getfedora.org/en/cloud/download/
The GP2 Base Cloud HVM AMI list includes the AMI for us-west-2 (Oregon),
ID ami-bbc6fb8b. This AMI appears to be marked private, although some
other AMIs do not exhibit the same issue. I haven't checked the entire
list.
Can someone check these results against our process to see what's causing
the issue?
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/111>
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
#144: f23 atomic iso configures docker loopback storage
-------------------------+--------------------
Reporter: jasonbrooks | Owner:
Type: defect | Status: new
Priority: major | Milestone: Future
Component: --- | Keywords:
-------------------------+--------------------
ISO installs of f23 atomic get configured w/ loopback storage, which is a
bad thing: http://www.projectatomic.io/blog/2015/06/notes-on-fedora-
centos-and-docker-storage-drivers/.
F22 Atomic had the correct config.
Running "docker info" on a VM installed from Fedora-Cloud_Atomic-
x86_64-22.iso yields:
{{{
...
Storage Driver: devicemapper
Pool Name: fedora-docker--pool
Pool Blocksize: 65.54 kB
Backing Filesystem: extfs
Data file:
Metadata file:
...
}}}
Running "docker info" on a VM installed from Fedora-Cloud_Atomic-
x86_64-23.iso yields:
{{{
...
Storage Driver: devicemapper
Pool Name: docker-253:0-153054-pool
Pool Blocksize: 65.54 kB
Backing Filesystem: extfs
Data file: /dev/loop0
Metadata file: /dev/loop1
...
}}}
I looked over the kickstarts, but I'm not clear on what might be causing
this.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/144>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#136: vagrant boxes fixups
-----------------------+---------------------
Reporter: dustymabe | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Keywords: meeting
-----------------------+---------------------
There are few suggestions we are getting for our vagrant boxes here are
some of them:
Add a cdrom device to the boxes (makes installing vbox guest additions
from ISO easier)
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/136>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System