cloud April 2016

cloud@lists.fedoraproject.org

26 participants
100 discussions

[cloud] #134: Clarify the status and process of https://github.com/fedora-cloud/docker-brew-fedora
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#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

1 2

[cloud] #157: Review of release blocking deliverables for F24
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#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

1 1

[cloud] #142: disable deltarpms in cloud images
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#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

1 3

[cloud] #130: Fedora Atomic Host installable tree needed
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#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

1 1

[cloud] #111: Some F22 AMIs marked private
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#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

1 4

[cloud] #13: Port Cloud Image Kickstart to anaconda/imagefactory
by Nobody 13 Oct '16

13 Oct '16

#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

2 5

[cloud] #69: Fedora Cloud image boot: Y U SO SLOW?
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#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

1 1

[cloud] #40: rel-eng/image upload changes for f21
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#40: rel-eng/image upload changes for f21 -------------------------------------------------+------------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 21 Component: Infrastructure & Release | (Alpha) Engineering | Keywords: -------------------------------------------------+------------------------- Some small updates to the cloud image upload process: * https://fedorahosted.org/rel-eng/ticket/5880 * https://fedorahosted.org/rel-eng/ticket/5881 -- Ticket URL: <https://fedorahosted.org/cloud/ticket/40> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 1

[cloud] #70: cloud-init output not going to the openstack log
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#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

1 1

[cloud] #43: procedures and process for getting updated images onto mirrors
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#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

1 6

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud April 2016