cloud October 2015

cloud@lists.fedoraproject.org

24 participants
89 discussions

[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

[cloud] #125: Fedora-Dockerfiles examples for Kubernetes
by Fedora Cloud Trac Tickets 31 Aug '16

31 Aug '16

#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

2 13

[cloud] #115: Fedora Cloud FAD (late 2015/early 2016)
by Fedora Cloud Trac Tickets 15 Jun '16

15 Jun '16

#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

1 9

[cloud] #93: Getting sha256sum published for the cloud images
by Fedora Cloud Trac Tickets 02 Jun '16

02 Jun '16

#93: Getting sha256sum published for the cloud images --------------------------------------------------+----------------------- Reporter: kushal | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 22 Component: Infrastructure & Release Engineering | Keywords: meeting --------------------------------------------------+----------------------- This will help things systemd to search the images provided by Fedora in a standard way using nspawn tool. Example of such file from ubuntu: https://cloud-images.ubuntu.com/trusty/current/SHA1SUMS https://cloud-images.ubuntu.com/trusty/current/SHA256SUMS.gpg -- Ticket URL: <https://fedorahosted.org/cloud/ticket/93> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 15

[cloud] #126: python3 only means ansible won't work
by Fedora Cloud Trac Tickets 17 May '16

17 May '16

#126: python3 only means ansible won't work ------------------------------+--------------------- Reporter: dustymabe | Owner: Type: task | Status: new Priority: major | Milestone: Future Component: Cloud Base Image | Keywords: meeting ------------------------------+--------------------- If we have only python3 in our cloud images then ansible won't work as it assumes /usr/bin/python is there. You end up with: ``` GATHERING FACTS *************************************************************** failed: [f23] => {"failed": true, "parsed": false} /bin/sh: /usr/bin/python: No such file or directory ``` We need to figure out a solution to this. For f23 cloud base image maybe we decide that adding it via cloud-init is enough.. For vagrant I think we should definitely include it in the image. There also could be some workaround that I don't know about for this. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/126> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 9

dnf in Dockerfiles
by Joe Brockmeier 15 May '16

15 May '16

Hey all, So dgilmore pointed out that f22 docker images will not have yum installed - which means we need to update the Dockerfiles for f22 to use dnf and not yum. We probably ought to go through and sanity-check them all to ensure they work with the f22 image as well before, say, beta. I'm CC'ing Scott b/c, if I'm not mistaken, he's done quite a lot of the work so far on the Dockerfiles - but also, I think he's looking for assistance there in keeping the effort going. Best, jzb -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

10 12

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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud October 2015