#35: External need: Automatic Image Upload
--------------------+-------------------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 21 (Alpha)
Component: --- | Keywords:
--------------------+-------------------------------
'''Summary:''' Whenever an image is built, it is automatically uploaded to
our cloud provider targets (EC2, etc.) and to the fedora ftp site (and
possibly mirrors if we can convince mirror admins to drink from that
firehose)
'''Importance:''' vital (current process where rel eng does it by hand
will not scale)
'''Timeframe:''' whenever we can get it / this adds value whenever it
happens
'''Fedora Sub-Project/SIG:''' Release Engineering, possibly Infrastructure
for resources
'''Cloud SIG owner:''' TBD (note summer intern may help with that, if it
is not too late)
Possibly we file this as a change. Also see previous intern's initial
work: https://git.fedorahosted.org/cgit/cloud-image-service.git/
We need someone to help drive this, and to assist rel-eng and
infrastructure in whatever they need.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/35>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#15: migrate to GPT instead of old-style partitions
------------------------------+-------------------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 21 (Alpha)
Component: Cloud Base Image | Keywords:
------------------------------+-------------------------------
* What: use gpt with this spec
http://www.freedesktop.org/wiki/Specifications/DiscoverablePartitionsSpec/
* Where: in the kickstart, and with support needed from build tools (which
should be ticket #13)
* Why: images could be launched as containers using new systemd hotness
* When: nice for F21 alpha
* Who: ???
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/15>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#14: Investigate systemd-networkd
------------------------------+-------------------------------
Reporter: mattdm | Owner: janeznemanic
Type: task | Status: new
Priority: normal | Milestone: Fedora 21 (Alpha)
Component: Cloud Base Image | Keywords:
------------------------------+-------------------------------
* What: new service to do very basic network config
* Where: remove the sysv network scripts, add config for this
* Why: remove very kludgey shell scripts; try the new hotness
* When: Before F21 alpha
* Who: Janez Nemanic
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/14>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#56: tracking ticket for conversations around shipping ostree images
-------------------------------------------+-------------------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: blocker | Milestone: Fedora 21
Component: Collaboration & Communication | (Branch)
| Keywords:
-------------------------------------------+-------------------------------
We've decided to base the Fedora Docker host image on Project Atomic, and
therefore rpm-ostree. This means several big conversations, including with
QA, Rel Eng, and the mirror network. It will mean some new development and
possibly extra resources. But first we need to figure out the questions to
ask, and then we need to ask them, and then we need to find answers, or
provide them where they don't already exist.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/56>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#134: Clarify the status and process of https://github.com/fedora-cloud/docker-
brew-fedora
---------------------+-----------------------
Reporter: adelton | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 22
Component: --- | Keywords:
---------------------+-----------------------
Hello,
there is https://github.com/fedora-cloud/docker-brew-fedora with Issues
enabled.
People file issues with Fedora docker images but they don't seem to be
actively acknowledged or fixed.
Its README.md describes workflow for commits but not for reporting and
fixing issues.
It looks like https://git.fedorahosted.org/cgit/spin-kickstarts.git/ might
actually be the primary source of data that lands in https://github.com
/fedora-cloud/docker-brew-fedora and eventually in the registry.
But when I asked in https://fedorahosted.org/spin-kickstarts/ticket/51 for
the path to reporting and fixing issues to be clarified, it was rejected.
So I try here -- could the issues at https://github.com/fedora-cloud
/docker-brew-fedora/issues either be acted upon, or the Issues
functionality disabled? Also updating either the description or README.md
with clear instruction about reporting issues with Fedora docker images
would be helpful.
Thank you,
Jan
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/134>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#157: Review of release blocking deliverables for F24
--------------------+--------------------
Reporter: jkurik | Owner:
Type: task | Status: new
Priority: major | Milestone: Future
Component: --- | Keywords:
--------------------+--------------------
I would like to ask Cloud WG to review Release blocking deliverables for
Fedora 24 release. The current list is located at
[https://fedoraproject.org/wiki/Fedora_Program_Management/ReleaseBlocking/Fe…
this link].
Please let me know any discrepancies (missing images, wrong assignment,
blocking/non-blocking status, etc.) you might find there.
Thanks,
Jan
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/157>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#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