cloud October 2015

cloud@lists.fedoraproject.org

24 participants
89 discussions

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

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud October 2015