cloud November 2015

cloud@lists.stg.fedoraproject.org

22 participants
96 discussions

[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

← 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 November 2015