January 2016 - cloud - Fedora mailing-lists

[cloud] #12: send list of packages on cloud images to spot for change from %doc to %license
by Nobody 13 Oct '16

13 Oct '16

#12: send list of packages on cloud images to spot for change from %doc to %license ------------------------------+----------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 Component: Cloud Base Image | Keywords: easyfix ------------------------------+----------------------- See https://fedorahosted.org/fpc/ticket/411 -- Ticket URL: <https://fedorahosted.org/cloud/ticket/12> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

2 5

[cloud] #37: External Need: software collections
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#37: External Need: software collections -------------------------------------+------------------------------------- Reporter: mattdm | Owner: mattdm Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Feature Component: Collaboration & | Deadline) Communication | Keywords: -------------------------------------+------------------------------------- External Need: Software Collections for Cloud Users Summary: Provides selection of language stacks of particular versions to users. '''Importance:''' vital (provides a meaningful reason to use Fedora cloud image, and helps insulate against rapid change) '''Timeframe:''' F21 release / This is a requirement of users in production. '''Fedora Sub-Project/SIG:''' Environments and Stacks '''Cloud SIG owner:''' mattdm -- more help wanted :) Draft feature proposal: https://fedoraproject.org/wiki/Cloud_Changelist#External_Need:_Software_Col… -- Ticket URL: <https://fedorahosted.org/cloud/ticket/37> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 2

[cloud] #63: list fedora accounts needed for releng to make official cloud images content
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#63: list fedora accounts needed for releng to make official cloud images content --------------------+-------------------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Branch) Component: --- | Keywords: --------------------+-------------------------------- What official accounts and agreements do we need to upload cloud images to our intended targets, including Amazon AWS, Google GCE, and etc? What do we need to a) upload docker base images and b) do docker trusted builds? -- Ticket URL: <https://fedorahosted.org/cloud/ticket/63> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 1

[cloud] #39: External Need: Scratch Builds on Change
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#39: External Need: Scratch Builds on Change --------------------+-------------------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Branch) Component: --- | Keywords: --------------------+-------------------------------- '''Summary:''' Whenever the kickstart changes, _or_ an RPM which is on the image hits the tree, a new scratch image is automatically built. '''Importance:''' nice to have (makes development much easier, and makes it quick to spot and fix problems before they affect anyone) '''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 We need an owner for this -- someone to drive it. And someone to help release engineering and infrastructure with the actual implementation work (not necessarily the same person, but also not necessarily different) -- Ticket URL: <https://fedorahosted.org/cloud/ticket/39> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 1

[cloud] #59: Process for determining when and why Docker trusted images need to be rebuilt
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#59: Process for determining when and why Docker trusted images need to be rebuilt ----------------------------+-------------------- Reporter: scollier | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: Docker (Other) | Keywords: ----------------------------+-------------------- We have several Docker trusted images hosted on the Docker index: https://index.docker.io/u/fedora/ These are built from the Fedora Cloud github account here: https://github.com/fedora-cloud/Fedora-Dockerfiles We need a clear process for deciding when these layered images need to be rebuilt. Is it when new RPMs are released? Security errata? Changes to config files? What are other criteria that could trigger the need for a rebuild? -- Ticket URL: <https://fedorahosted.org/cloud/ticket/59> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 8

[cloud] #72: go over f21 changes, make sure they're all in good shape
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#72: go over f21 changes, make sure they're all in good shape --------------------+------------------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Alpha) Component: --- | Keywords: meeting --------------------+------------------------------- https://fedorahosted.org/fesco/ticket/1322 This is a meeting agenda item. Make sure all of the cloud-related changes are in good shape: * have owner * are on track * are updated with relevant info And when not, find a way to fix them :) -- Ticket URL: <https://fedorahosted.org/cloud/ticket/72> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 3

[cloud] #62: notification of pending security updates in motd
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#62: notification of pending security updates in motd ------------------------------+------------------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Alpha) Component: Cloud Base Image | Keywords: ------------------------------+------------------------------- I think it would be nice if the /etc/motd (or some other mechanism) would inform users of pending security updates on login. And, a welcome side-effect is that having cloud images check with the update server network periodically gives us a better measure of whether we're actually being used. Right now, cloud images are probably being drastically undercounted, as many aren't updated ever. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/62> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 8

[cloud] #55: define shell command API available in Fedora Cloud Base Image
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#55: define shell command API available in Fedora Cloud Base Image ------------------------------+------------------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Alpha) Component: Cloud Base Image | Keywords: ------------------------------+------------------------------- This is a list of shell commands (or at least the packages which contain them) which are expected to work in a cloud metadata userscript at initial Fedora Cloud Base Image launch. We should maintain this list and note changes in the release notes, have a deprecation procedure, and so on. The initial goal for Fedora Cloud Base Image is to balance size and usefulness -- python and yum/dnf will be in the list, for example. For a more "edgy" image, see Fedora Atomic. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/55> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 1

[cloud] #54: define shell command API available in Fedora Atomic
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#54: define shell command API available in Fedora Atomic -------------------------------+------------------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Alpha) Component: Docker Host Image | Keywords: -------------------------------+------------------------------- This is a list of shell commands (or at least the packages which contain them) which are expected to work in a cloud metadata userscript at initial Fedora Atomic launch. We should maintain this list and note changes in the release notes, have a deprecation procedure, and so on. The initial goal for Fedora Atomic is to be as small as reasonably possible, including removing Python (and, not including python and yum/dnf on the list). -- Ticket URL: <https://fedorahosted.org/cloud/ticket/54> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 3

[cloud] #48: remove rsyslog from default image, configure journald options appropriately
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#48: remove rsyslog from default image, configure journald options appropriately ------------------------------+------------------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Alpha) Component: Cloud Base Image | Keywords: ------------------------------+------------------------------- Right now, we have two logging systems installed by default in the Fedora Cloud image. While obviously rsyslog needs to continue to be an option, I don't think we should be shipping it by default. (After dhclient, it's the second-largest memory consumer, for one thing.) This requires some rework to the cloud-init package -- that's what's pulling it in now. We should also consider the journal options we want by default; probably settings optimized for less memory consumption are better. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/48> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 5

[cloud] #35: External need: Automatic Image Upload
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#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

1 5

[cloud] #15: migrate to GPT instead of old-style partitions
by Nobody 13 Oct '16

13 Oct '16

#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

2 3

[cloud] #14: Investigate systemd-networkd
by Nobody 13 Oct '16

13 Oct '16

#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

2 53

[cloud] #56: tracking ticket for conversations around shipping ostree images
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#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

1 4

[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] #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

[cloud] #144: f23 atomic iso configures docker loopback storage
by Fedora Cloud Trac Tickets 05 Oct '16

05 Oct '16

#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

3 10

[cloud] #136: vagrant boxes fixups
by Fedora Cloud Trac Tickets 28 Sep '16

28 Sep '16

#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

1 5

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud January 2016