January 2015 - cloud - Fedora mailing-lists

[cloud] #89: Add Dockerfile Section to Downloads Page?
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#89: Add Dockerfile Section to Downloads Page? --------------------+-------------------- Reporter: jzb | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: --------------------+-------------------- For discussion - should we add a Dockerfile section on the downloads site? -- Ticket URL: <https://fedorahosted.org/cloud/ticket/89> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 2

[cloud] #83: participation in OpenShift Commons
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#83: participation in OpenShift Commons --------------------+--------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: meeting --------------------+--------------------- Take a look at http://origin.openshift.com/commons I brought up joining this to the board, and got the reasonable response of "have you gotten the Cloud SIG committed to actually doing the participation asked for?" I've talked to a couple of people and I think there's sufficient interest, but it seemed reasonable to ask formally if this is something we're interested in. The actual formal requirements seem to be low: > OpenShift Commons is open to anyone. We have no Contributor License Agreement (CLA) or required donation to join. Instead we take each organization at their word to be active participants in forums, Special Interest Groups (SIGs), mailing lists and events. and I think it'd be _great_ to have Fedora officially involved in that way. What do you all think? -- Ticket URL: <https://fedorahosted.org/cloud/ticket/83> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 4

[cloud] #78: Draft charter change, new slate (Cloud WG members vote needed!)
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#78: Draft charter change, new slate (Cloud WG members vote needed!) --------------------+-------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: --------------------+-------------------- Joe has prepared a draft change to the charter https://lists.fedoraproject.org/pipermail/cloud/2014-October/004372.html making it easier to select new members. Additionally, I've proposed a new WG membership slate based on current activity: https://lists.fedoraproject.org/pipermail/cloud/2014-October/004372.html By the existing rules, both of these need 5 +1 votes from existing members of the WG to pass. That is, the people listed https://fedoraproject.org/w/index.php?title=Cloud/Governance&oldid=368062#C… — so, current members, please vote on each. If we can't reach quorum in a week, I'll take this to FESCo for "override approval", but I hope that won't be necessary. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/78> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 7

[cloud] #76: Explore possibility of shipping preconfigured KVM cloud image on live DVD
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#76: Explore possibility of shipping preconfigured KVM cloud image on live DVD --------------------+-------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: --------------------+-------------------- I suggested this for Fedora Server, and Josh mentioned to me that we could do it for the cloud. What about prepackaging the cloud image on-disk with a live Workstation- based image, with an existing KVM configuration including a preconfigured config-drive allowing SSH access to the local user. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/76> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 1

[cloud] #71: libmicrohttpd is back as a systemd dependency
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#71: libmicrohttpd is back as a systemd dependency --------------------+-------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: --------------------+-------------------- This was gone from F20 (https://bugzilla.redhat.com/show_bug.cgi?id=908081) but is back now. As noted in this bug, it is undesirable because libmicrohttpd pulls in gnutls (and nettle) , which is not otherwise on the base image. Reducing the number of crypto libraries there by default reduces the need to respin off-cycle security updates -- this is not an abstract concern. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/71> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 2

[cloud] #60: Enable serial console for bootloader
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#60: Enable serial console for bootloader ---------------------+-------------------- Reporter: fabiand | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: ---------------------+-------------------- The bootloader of the current cloud images is not attached to a serial console. Please change this, so we can also follow the bootloader part on the serial console, i.e. for test automation. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/60> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 5

[cloud] #53: anaconda doesn't allow installation of current fedora-cloud-base.ks
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#53: anaconda doesn't allow installation of current fedora-cloud-base.ks ---------------------+-------------------- Reporter: walters | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: ---------------------+-------------------- Cloud images are expected to come with: * root password locked * No user precreated; instead, an agent (cloud-init, min-metadata-service) pull config data from the hypervisor and inject ssh keys, create users, etc. The problem is Anaconda's user.py is a mandatory step. A suggested hack is to set a root password, then unset it in %post. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/53> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 2

[cloud] #44: hey we should have a vagrant base box
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#44: hey we should have a vagrant base box --------------------+-------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: --------------------+-------------------- This is a very long-standing request. Here is a ticket for it. :) -- Ticket URL: <https://fedorahosted.org/cloud/ticket/44> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 14

[cloud] #23: File F21 change: Re-factor cloud-init
by Nobody 13 Oct '16

13 Oct '16

#23: File F21 change: Re-factor cloud-init ------------------------------+------------------------------------------ Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Feature Deadline) Component: Cloud Base Image | Keywords: ------------------------------+------------------------------------------ '''Summary:''' Cloud Init was initially designed for a different distribution and is only loosely tailored for our needs. As it stands, it pulls in a rather large set of packages not used for other things. It is also written in Python, itself a large subsystem which it would eventually be nice to leave out of the base. Effort is moderate, with some low- hanging fruit which may be addressed easily. '''Importance:''' vital long term, but just moderate for F21 (We really need this, but if we don't get work it now, it's in acceptable shape for this release.) '''Timeframe:''' F21 alpha, or F22 / if we don't make alpha with changes, this can go in next release. '''Scope:''' Self-contained '''Cloud SIG owner:''' TBD -- Ticket URL: <https://fedorahosted.org/cloud/ticket/23> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

2 15

[cloud] #34: External need: batched updates
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#34: External need: batched updates --------------------+------------------------ Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Flock 2014 Component: --- | Keywords: --------------------+------------------------ '''Summary:''' We want to produce updated images on a monthly cadence. It would be nice if we could produce those from QA'd bunches of packages. '''Importance:''' moderate (it will be hard to implement image refresh without this, but we could do it) '''Timeframe:''' F21 release + 1 month / Obviously better if we get things lined up earlier '''Fedora Sub-Project/SIG:''' Primarily QA, but Rel Eng and Infrastructure too. This is pretty big. ''' Cloud SIG owner:''' TBD (this probably needs someone actively contributing to initial and ongoing work) See the related Change proposal "(A)Periodic Updates to the Images" http://flock2013.sched.org/event/8c4f702e42814598e0e4e31b188a0ae6 What's this ticket about? We need an owner for this — someone to drive it forward. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/34> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 2

[cloud] #81: Create cloud training materials for ambassadors
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#81: Create cloud training materials for ambassadors -------------------------------------------+----------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 22 Component: Collaboration & Communication | Keywords: -------------------------------------------+----------------------- Many Fedora Ambassadors come from a desktop or old-school sysadmin background. Cloudy concepts are new and foreign. In talking with some of them, it was suggested that it'd be really, really helpful to have some basic training materials for our own ambassadors -- what is cloud, why does it matter, what is Fedora Cloud, what is our strategy, why do _we_ matter, and so on. http://mattdm.org/fedora/cloud2013/#1 might be a starting point. Maybe some more interactive training would even be useful. Of course, it'd also be awesome to get some people from the new modern world interested in being ambassadors as well -- another direction to approach the same issue. (But even then, training on what _we_ are doing would be useful.) -- Ticket URL: <https://fedorahosted.org/cloud/ticket/81> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

2 3

[cloud] #38: Automatic Smoketests on Image Build
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#38: Automatic Smoketests on Image Build --------------------------+------------------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Alpha) Component: Testing & QA | Keywords: --------------------------+------------------------------- '''Summary:''' When a new image is built in Koji, automatically boot it and run a basic matrix of tests. '''Importance:''' moderate (worst case, we can keep doing this by hand) '''Timeframe:''' F21 alpha / Want to reduce manual test workload '''Fedora Sub-Project/SIG:''' QA and the Taskotran project '''Cloud SIG owner:''' Sandro Mathys https://fedoraproject.org/wiki/Taskotron -- Ticket URL: <https://fedorahosted.org/cloud/ticket/38> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 6

[cloud] #25: File F21 change: OpenShift Out-of-the-Box Image
by Nobody 13 Oct '16

13 Oct '16

#25: File F21 change: OpenShift Out-of-the-Box Image --------------------------------+------------------------------------------ Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Feature Deadline) Component: OpenShift Origin | Keywords: Image | --------------------------------+------------------------------------------ '''Summary:''' Fedora Cloud agreed to make a base image plus several tailored to specific purposes. This is one of the tailored ones — OpenShift ready to run. '''Importance:''' nice to have (if we fail to do it, we are not any worse- off than we are now, and OpenShift can still be installed on the base iamge.) '''Timeframe:''' F21 alpha / If it's not ready for alpha, we have missed this release '''Scope:''' self-contained (in collaboration with OpenShift developers) '''Cloud SIG owner:''' TBD https://fedoraproject.org/wiki/Changes/OpenShift_Out-of-the- Box_Cloud_Image -- Ticket URL: <https://fedorahosted.org/cloud/ticket/25> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

2 2

[cloud] #28: discuss modularized SELinux policy packaging
by Nobody 13 Oct '16

13 Oct '16

#28: discuss modularized SELinux policy packaging ------------------------------+----------------------- Reporter: mattdm | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Fedora 22 Component: Cloud Base Image | Keywords: ------------------------------+----------------------- Possible F22 feature? Summary: Monolith SELinux policy has rules for everything that could exist, not just that which is installed. Possible room for reduction here. '''Importance:''' nice-to-have '''Timeframe:''' F21 or F22 / This is not low-hanging fruit. '''Scope:''' self-contained (SELinux) ''' Cloud SIG owner:''' TBD (No Feature filed at this time -- discuss with SELinux policy maintainers) -- Ticket URL: <https://fedorahosted.org/cloud/ticket/28> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

2 1

[cloud] #73: test cases for cloud-init
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#73: test cases for cloud-init --------------------------+------------------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Final) Component: Testing & QA | Keywords: --------------------------+------------------------------- We have a number of bugs for #cloud-config syntax not working properly -- probably because it's mostly been tested with debian/ubuntu-universe tools. For example: * https://bugzilla.redhat.com/show_bug.cgi?id=1126857 * https://bugzilla.redhat.com/show_bug.cgi?id=1126365 We should fix these, obviously, but also, each time we fix one, we should make a test case -- ideally an automatic test case! -- to make sure it stays fixed. It would also be nice to have some other test cases for cloud-config syntax we expect to work. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/73> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 1

[cloud] #57: get official images uploaded into Rackspace
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#57: get official images uploaded into Rackspace -------------------------------------------------+------------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 Component: Infrastructure & Release | (Final) Engineering | Keywords: -------------------------------------------------+------------------------- Work with Rackspace engineers... they don't yet have public image sharing, but getting our official images uploaded to a fedora account as part of the release process would be a good start. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/57> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 1

[cloud] #42: policies for batched updates
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#42: policies for batched updates ------------------------------+------------------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Final) Component: Software Updates | Keywords: ------------------------------+------------------------------- See ticket #18 We want to putting out updated images periodically (or aperiodically as needed). What are the rules? What are the procedures? Where are they documented? -- Ticket URL: <https://fedorahosted.org/cloud/ticket/42> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 1

[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] #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] #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] #88: Social Media for Dockerfiles
by Fedora Cloud Trac Tickets 24 Feb '16

24 Feb '16

#88: Social Media for Dockerfiles -----------------------------------+--------------------- Reporter: jzb | Owner: jzb Type: task | Status: new Priority: normal | Milestone: Future Component: Docker Base Container | Keywords: meeting -----------------------------------+--------------------- We need to work with marketing to tweet about things regularly. I'd like to put out regular tweets to promote individual Dockerfiles. Thoughts? -- Ticket URL: <https://fedorahosted.org/cloud/ticket/88> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 7

[cloud] #94: Producing Updated Cloud/Atomic Images
by Fedora Cloud Trac Tickets 11 Nov '15

11 Nov '15

#94: Producing Updated Cloud/Atomic Images ------------------------------+--------------------- Reporter: dustymabe | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: Cloud Base Image | Keywords: meeting ------------------------------+--------------------- We need to finalize our policy around producing updated images and then start doing it. Right now we have loosely decided to release new images once a month or whenever security updates require it. Additionally, as part of this we should also decide on a policy that determines when we stop updating images for a particular release. I imagine that we don't want to be producing updated images for Fedora X, Y, and Z all at the same time. Ideally we would only be producing updated images for the current/latest major version. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/94> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 24

[cloud] #84: publicize fedora-dockerfiles
by Fedora Cloud Trac Tickets 23 Sep '15

23 Sep '15

#84: publicize fedora-dockerfiles -------------------------------------------+------------------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Final) Component: Collaboration & Communication | Keywords: meeting -------------------------------------------+------------------------------- https://github.com/fedora-cloud/Fedora-Dockerfiles is a) cool b) useful c) active d) a great place for new contributors We should popularize this. Articles, blog posts, wiki documentation, non- wiki documentation, etc. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/84> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 21

[cloud] #58: get vagrant-libvirt (and/pr vagrant-kvm) plugins into the distro
by Fedora Cloud Trac Tickets 08 May '15

08 May '15

#58: get vagrant-libvirt (and/pr vagrant-kvm) plugins into the distro --------------------+-------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: --------------------+-------------------- See http://ttboj.wordpress.com/2014/05/13/vagrant-on-fedora-with-libvirt- reprise/ and the call for help at the end. Also the discussion there, and also previous work at * https://bugzilla.redhat.com/show_bug.cgi?id=998503 * https://fedoraproject.org/wiki/Changes/Vagrant -- Ticket URL: <https://fedorahosted.org/cloud/ticket/58> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 1

[cloud] #92: Need rootfiles package in fedora:latest Docker base image
by Fedora Cloud Trac Tickets 08 May '15

08 May '15

#92: Need rootfiles package in fedora:latest Docker base image -----------------------------------+-------------------- Reporter: scollier | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: Docker Base Container | Keywords: -----------------------------------+-------------------- We need the .bashrc in order to properly change the bash prompt once changed into the image. For example, here's the fedora:20 image: -bash-4.2# docker run -it fedora:20 bash [root@845950cd95f1 /]# cat /etc/fedora-release Fedora release 20 (Heisenbug) [root@845950cd95f1 /]# rpm -qf /root/.bashrc rootfiles-8.1-16.fc20.noarch For example, here's the fedora:latest image: -bash-4.2# docker run -it fedora:latest bash bash-4.3# rpm -qf /root/.bashrc error: file /root/.bashrc: No such file or directory -- Ticket URL: <https://fedorahosted.org/cloud/ticket/92> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 4

[cloud] #86: qcow2 images text is a bit obscure / OpenStack-only
by Fedora Cloud Trac Tickets 22 Apr '15

22 Apr '15

#86: qcow2 images text is a bit obscure / OpenStack-only ----------------------------+-------------------- Reporter: jzb | Owner: jzb Type: task | Status: new Priority: normal | Milestone: Future Component: Website & Wiki | Keywords: ----------------------------+-------------------- Lars Kellogg-Stedman sent a note to the Fedora Cloud list today noting, rightly, that the libvirt audience might miss the qcow2 images because it's labeled "OpenStack" (only) rather than being more expansive. We need to correct this and add instructions for using cloud-init with the image in Virt-Manager, etc. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/86> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 1

[cloud] #87: Fedora Magazine Post: How to Use Dockerfiles
by Fedora Cloud Trac Tickets 04 Mar '15

04 Mar '15

#87: Fedora Magazine Post: How to Use Dockerfiles -----------------------------------+--------------------- Reporter: jzb | Owner: jzb Type: task | Status: new Priority: normal | Milestone: Future Component: Docker Base Container | Keywords: meeting -----------------------------------+--------------------- Need to do a post on how to use Dockerfiles and maybe how to contribute patches to Dockerfiles. Should this also live on the wiki? -- Ticket URL: <https://fedorahosted.org/cloud/ticket/87> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 1

[cloud] #68: support HVM instances in EC2
by Fedora Cloud Trac Tickets 11 Feb '15

11 Feb '15

#68: support HVM instances in EC2 ------------------------------+------------------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Alpha) Component: Cloud Base Image | Keywords: ------------------------------+------------------------------- We currently only support Xen paravirtualized images (PV) in EC2. We need to support HVM as well. (This will require changes to our EC2 image production and upload process, and may require changes to our bootloader code as well. Particularly, it probably takes away our clever hack for providing different kernel parameters in EC2.) -- Ticket URL: <https://fedorahosted.org/cloud/ticket/68> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 7

EC2 cloud image size
by Dmitry Makovey 30 Jan '15

30 Jan '15

I just tried to spin up "cloud" instance of F21 on EC2 only to discover it's requirements for 12G volume (???). Am I doing something wrong or did F21 jumped from moderate 2-3G (F20) over to 12G "overnight". I assumed "cloud image" would be a tiny set of packages with very little requirements to fit into all flavors offered by EC2 and alike. Was this done to accommodate Docker? -- Dmitry Makovey Web Systems Administrator Athabasca University (780) 675-6245 --- Confidence is what you have before you understand the problem Woody Allen When in trouble when in doubt run in circles scream and shout http://www.wordwizard.com/phpbb3/viewtopic.php?f=16&t=19330

5 15

2015-01-28 @ 1900 UTC ** Cloud SIG Meeting Minutes
by Mike Ruckman 28 Jan '15

28 Jan '15

============================ #fedora-meeting-1: cloud sig ============================ Meeting started by roshi at 19:00:42 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting-1/2015-01-28/fedora_cloud_s… . Meeting summary --------------- * Roll Call (roshi, 19:01:04) * Follow Up (roshi, 19:03:53) * LINK: https://fedorahosted.org/cloud/ticket/94 (dustymabe, 19:05:26) * LINK: https://fedorahosted.org/cloud/report/9 (roshi, 19:06:50) * HVM Instances (#68) (roshi, 19:07:16) * LINK: https://fedorahosted.org/cloud/ticket/68 (roshi, 19:07:24) * Open Floor (roshi, 19:23:21) * Meeting is going to end early due to not meeting quorum (roshi, 19:23:58) Meeting ended at 19:28:26 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * roshi (51) * dustymabe (28) * Corey84 (13) * zodbot (8) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- // Mike -- Fedora QA freenode: roshi http://roshi.fedorapeople.org

1 0

[cloud] #91: Update Timezone for the docker images
by Fedora Cloud Trac Tickets 28 Jan '15

28 Jan '15

#91: Update Timezone for the docker images -----------------------------------+----------------------- Reporter: kushal | Owner: kushal Type: task | Status: new Priority: normal | Milestone: Fedora 22 Component: Docker Base Container | Keywords: meeting -----------------------------------+----------------------- In the kickstart currently it is configured as New York, it should be UTC. This issue was first mentioned by lsm5. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/91> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 2

[Fedocal] Reminder meeting : Fedora Cloud Workgroup
by Dusty Mabe 26 Jan '15

26 Jan '15

Dear all, You are kindly invited to the meeting: Fedora Cloud Workgroup on 2015-01-28 from 19:00:00 to 20:00:00 UTC At fedora-meeting(a)irc.freenode.net The meeting will be about: Standing meeting for the Fedora Cloud Workgroup Source: https://apps.fedoraproject.org/calendar//meeting/1999/

1 0

2015-01-26 @ 1700 UTC ** F22 Blocker Review Meeting
by Mike Ruckman 25 Jan '15

25 Jan '15

# F22 Blocker Review meeting # Date: 2015-01-26 # Time: 1700 UTC # Location: #fedora-blocker-review on irc.freenode.net I seem to have forgotten how to use the "send" button on my mail client, so this annoucnement is getting out a bit late. Apologies for that! We've got another blocker review in a couple hours! We currently have several proposed blockers: 2 Alpha, 1 Beta and 2 Final. So if you're around after the QA meeting, come and join us for some blocker review goodness :) If you want to take a look at the proposed or accepted blockers, the full list can be found here: https://qa.fedoraproject.org/blockerbugs/ Make sure to click through the milestones to see how many we have before the meeting! We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F22 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting See you soon! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- // Mike -- Fedora QA freenode: roshi http://roshi.fedorapeople.org

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud January 2015