On 03/19/2015 07:50 PM, Scott Collier wrote:
On 03/11/2015 09:40 AM, Major Hayden wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/11/2015 09:23 AM, Joe Brockmeier wrote:
I'm CC'ing Scott b/c, if I'm not mistaken, he's done quite a lot of
the work so far on the Dockerfiles - but also, I think he's looking
for assistance there in keeping the effort going.
I'll be glad to help maintain/update those Dockerfiles if needed, Scott.
Thanks Major. Here's a summary of things I think we should be looking
at in general, not just Dockerfile maintenance:
1. Ensuring dnf support on Fedora 22 images. This means figuring out
how to manage dockerfiles in a manner that both dnf or yum can work.
For example, the FROM line will determine what package installation
method we will use. If it's FROM fedora:rawhide, should use dnf, if
it's FROM fedora:21, should use yum. Just need to think that through
and how we want to handle. I haven't played around with dnf yet.
2. Need READMEs for the libvirt images:
https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/libvirt
https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/systemd/libvirt
3. Need some extra eyes on all PRs and images that come in. Might be
good to require a +1 from two maintainers before merging a request?
Thoughts?
4. I'd like to set up some CI on these where and if it makes sense.
Some triggers: docker package updates, Dockerfile updates, etc...
Something simple: build the image, run the image, test for an expected
result.
5. Does it make sense to add some kubernetes support / examples to
these? I know not all of these apps are "scalable" or usable in a
production k8s cluster, per se, but dropping in a yaml file for a few
select images, so people can explore and learn wouldn't hurt. It could
sit right by the Dockerfile. People could build the image, and deploy
in a k8s environment.
+1. Having k8 config files would help others. As of now I am trying to
understand k8s. I am interested to contribute towards the k8s files.
-Lala
6. Now that the LABEL patch has been (or will be merged) into Docker,
we'll want people to start testing the LABEL functionality in
fedora-dockerfiles and take advantage of that with the new atomic
package. We'll want to abstract away any complex docker install /
docker run commands moving forward. This will take some effort. This
will be very helpful on an any host with the atomic tool.
Anything else? Thoughts?
- --
Major Hayden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJVAFPcAAoJEONAdDQ9I/mwSKEH/2axXPtLKik7QII+/e6XzrJQ
LY8jeSXHMyFqaa86bhTI8pcp7fC05oXWCxkmg23SMhgAG7Ls+n39YXERzvnXx2FO
kGX59Kb9wcZ5YhbDZw53yRQeqDniRc9mb16qJvnuQ901gNcUWD9xKQ+P98HfAKT5
UY9WaSWETiT6oZwATlrMROM/2zUHUaEyBK8WvWTgVZATc4fijE9h3jutrZ1/BCYB
r038olR/kC0UHrGrY7EQB2TP5ECp1+ygbFzN0I6R63OivM//1yZy83BGP07p81QV
QlR/wsiJFWPOQPzBzeJ2ZYNGjdt8luDjBLV3nG2p4V4w0ikItilkZTiHp337ih8=
=MmjD
-----END PGP SIGNATURE-----
_______________________________________________
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
_______________________________________________
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
_______________________________________________
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
