I would like to hear from others about this idea. First for those unfamiliar with one or both of these projects they are a new approach to a server OS based on nothing but containers....
URL - CoreOS <https://coreos.com/> *The main building block of CoreOS is Docker, a Linux container engine, where your applications and code run. Docker is installed on each CoreOS machine. You should construct a container for each of your services (web server, caching, database) start them with fleet and connect them together by reading and writing to etcd.* *CoreOS doesn't ship a package manager — any software you would like to use must run within a container. You can quickly try out a Ubuntu container in the step by step tutorial <https://coreos.com/docs/guides/docker/>. The end goal is to have your build system output a container as the final artifact. CoreOS uses systemd <https://coreos.com/using-coreos/systemd> and fleet <https://coreos.com/using-coreos/clustering> to manage the containers that need to be started based on the resulting build artifact.* URL - Redhat's Project Atomic<http://www.redhat.com/about/news/press-archive/2014/4/linux-container-innovations> *An Atomic Host is a lean operating system designed to run Docker containers, built from upstream CentOS, Fedora, or Red Hat Enterprise Linux RPMs. It provides all the benefits of the upstream distribution, plus the ability to perform atomic upgrades and rollbacks — giving the best of both worlds: A modern update model from a Linux distribution you know and trust. * *Ubuntu's Core OS, Juju, Juju-Gui and local provider integration* note; don't confuse Ubuntu's Core OS with the above CoreOS project I am thinking that a combination/integration of Ubuntu's Core OS with juju, juju-gui installed in a Local Provider (re LXC) environment would be more than a match for the above. Although Docker is central to the CoreOS project and Project Atomic, *Docker at least as I understand it*, *does not approach "Services" deployment anywhere near the degree that Juju does*. Ubuntu's Core OS <https://wiki.ubuntu.com/Core> What is Ubuntu Core - Ubuntu Core is a minimal rootfs (only 32 Mbytes) for use in the creation of custom images for specific needs. Ubuntu Core strives to create a suitable minimal environment for use in Board Support Packages, constrained or integrated environments, or as the basis for application demonstration images. It is available for the i386, amd64, and arm architectures. In my vision, you could deploy an Ubuntu Core OS image that has both juju and juju-gui already installed in local provider mode. An enterprise or service provider could then simply point a browser to the IP address of the deployed Ubuntu Core OS instance access juju-gui and from there deploy any of the 140+ Juju Charm's or the new Bundles all into LXC containers on the Core OS ubuntu. Seems to me that offers everything the two projects above would offer and more because at least with Juju Charm's the philosophy of "Service" deployment is at the heart of Juju. I'd be interested in comments from some of the juju guru-type folks...? thanks Brian
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
