[cloud] #130: Fedora Atomic Host installable tree needed
by Fedora Cloud Trac Tickets
#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
7 years, 2 months
[cloud] #111: Some F22 AMIs marked private
by Fedora Cloud Trac Tickets
#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
7 years, 2 months
[cloud] #13: Port Cloud Image Kickstart to anaconda/imagefactory
by Nobody
#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
7 years, 2 months
[cloud] #136: vagrant boxes fixups
by Fedora Cloud Trac Tickets
#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
7 years, 2 months
[cloud] #125: Fedora-Dockerfiles examples for Kubernetes
by Fedora Cloud Trac Tickets
#125: Fedora-Dockerfiles examples for Kubernetes
----------------------+--------------------
Reporter: scollier | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Keywords:
----------------------+--------------------
Would be nice to have a couple of services put together to create an
application that is managed by Kubernetes on Atomic. This would need to
be clearly documented. We would need the proper json kubernetes files to
launch the apps with. A few examples would be nice:
1. simple web server with a database
2. simple web server
3. others?
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/125>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
7 years, 3 months
[cloud] #115: Fedora Cloud FAD (late 2015/early 2016)
by Fedora Cloud Trac Tickets
#115: Fedora Cloud FAD (late 2015/early 2016)
-----------------------+-----------------------
Reporter: dustymabe | Owner: dustymabe
Type: task | Status: new
Priority: normal | Milestone: Future
Component: Planning | Keywords: meeting
-----------------------+-----------------------
At Flock we talked about having a Fedora Activity Day for the cloud
working group to get some work done. This ticket will serve as a stub for
planning and coordination of this event.
The first step is to write up a proposal and submit it for review.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/115>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
7 years, 5 months