cloud September 2016

cloud@lists.fedoraproject.org

25 participants
97 discussions

[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

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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud September 2016