-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, 29 Apr 2014 14:35:55 +0200
Jaroslav Reznik <jreznik(a)redhat.com> wrote:
= Proposed Self Contained Change: Docker Cloud Image =
https://fedoraproject.org/wiki/Changes/Docker_Cloud_Image
Change owner(s): Cloud SIG / Sandro Mathys <red(a)fedoraproject.org>
New Fedora product: Fedora Docker Cloud Image - Docker host ready to
go.
== Detailed Description ==
Fedora Cloud agreed to make a base image plus several tailored to
specific purposes. This is one of the tailored ones — Docker host
ready to go. While basically that simply means only just adding
docker-io to the base image, this is (also) intended to be our
response to CoreOS. Therefore, depending on further discussion and
user input, we might also add etcd [1] and fleet [2] to the mix.
Furthermore, the Cloud SIG considers this their most radical image,
riding the very front of the leading edge. (Yeehaw!) Several
approaches (read: bonus objectives) are under consideration but not
crucial to the product itself:
* Fedora Atomic Initiative [3] (aka rpm-ostree) to allow for atomic
updates. We might further choose to remove yum/dnf from the image in
favor of ostree.
* Replace cloud-init with min-metadata-service, CoreOS' cloud-init or
other alternatives. We'd like to find a leaner solution (read: less
Requires) and one that is better (or easier) tailored to Fedora.
* Remove Python from this image to reduce the footprint. Note, that
this can only be achieved if yum/dnf AND cloud-init are replaced by
other solutions as explained in the above points.
It should be noted that most of these tools are currently under heavy
construction but might be ready in time. If they are, it's still up
to discussion whether they will be included. If they aren't, we might
punt them to F22 or later. Either way, they won't impact the
completion of this change's main goals and are only listed for
completeness' sake.
== Scope ==
* Proposal owners: Regarding the core objective, it's just about
creating a new kickstart file (probably even %include-ing the base
one) add some minor stuff and make sure it gets built into a new
image. Also, for added security, we'd like to see Docker and SELinux
integrate better. There's already work going on about this.
** The bonus objectives (i.e. leading edge approaches) further
require: *** ostree to work with SELinux
*** Creating a filesystem tree for ostree that equals the filesystem
of the image as created by traditional means
*** min-metadata-service to gain the ability to execute scripts just
like cloud-init does
*** CoreOS' cloud-init or other alternatives to be packages (and
possibly tailored) for Fedora
* Other developers: N/A (not a System Wide Change)
* Release engineering: N/A (not a System Wide Change)
Releng will be needed to make the docker images, and upload them where
they need to go, so this is not true
* Policies and guidelines: N/A (not a System Wide Change)
[1]
https://github.com/coreos/etcd
[2]
https://github.com/coreos/fleet
[3]
http://rpm-ostree.cloud.fedoraproject.org/
_______________________________________________
devel-announce mailing list
devel-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBAgAGBQJTX8bXAAoJEH7ltONmPFDRRnEP/jBACfQcJFfszUZyhem7mMBT
Hn3LqAOToPr4UeNyjM/G3CRatWEJ7YImMl+caqgZ0DYECKDHVmQECcbfpR2SnHM6
1xqsvkEL4erFtL6x4i9EeNnxfJPiLoUGENtr/f7OQqTiwdTJG5022ztRFbNLLoag
6khAyx+cn9gJs+/aNPX3C6RO7FfJsFduVVRnhBDOTW6SrY0mzHnBflm9v2ZkewL1
gc66XIeKISbJiX46zNoslKOICR3M+SMwd1+1FrBMhMysvlQuxPbnVmQmY6ilyBbH
v2uiEo0VDJLTgeBDvsRllf5kdRN3PUIWBmbW9hlvQjN4CFDugy/kplc1kdDWUnrF
1FDYo6Dc32DEwkJMG9nFyYQ8CmvO3Lp8J54tS0hdlFnpPSf1H6LJTdArSd2mRttZ
ceEWzjw5XaCUeJZFn25tABVYnxaJ1asy7IBnaGngeu2uSBXNIaToD/b4FEC3eeuz
hhr1lSeAg5JDFFq/H18TtCYVLv4S2lWWv/+nP6md588bxIPcJdojIcY/sptR+EYu
DKIs7AZtr8Lk6S+AlHAP762ZkvuasekPOD/XFtDPMaK2KcP67ntRantNITTV9DkD
vORr0a56CxEx0fk06PftUGv+9P4VfANVm4g3Kgc7+UI1I9aumrxbdiDNMNwSajth
bUIYP6FA807evkV0mCz8
=gwXJ
-----END PGP SIGNATURE-----