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