fuel-dev team mailing list archive

[Matthew Mosesohn <mmosesohn@xxxxxxxxxxxx>]

With moving to docker, the persistent data item really adds a
complexity level, but it just means we need to segregate our static
and user data for deployment.
The main volumes we would need to create would include the following:
* cobbler conf and generated profiles
* postgresql database
* log store

Ephemeral data that can be lost includes:
rabbitmq cache
local container logs (rsyslog for anything we want to keep)

Items not clear about persistent volumes:
* Fuel Puppet manifests (so a user can make persistent changes)
* RPM/DEB repos (same as above)

I understand that Fuel upgrades is meant to accommodate upgrades and
rollbacks, so we have to add in a versioning convention to persistent
volumes and a way to perform these migrations.


On Mon, Feb 10, 2014 at 4:26 PM, Evgeniy L <eli@xxxxxxxxxxxx> wrote:
> Hi,
>
>
> As many of you may already know we started design/implementation of master
> node upgrade feature. Here you can read the design document.
>
>
> So, it's just status update of this feature.
>
> We want to use docker as containers management tool.
>
>
> Here is Docker's pros and cons
>
> Pros
>
> +
> http://stackoverflow.com/questions/17989306/what-does-docker-add-to-just-plain-lxc
>
> + rest API (it will be very useful in case of plugins, when we'll be able to
> setup new container from inside another container)
>
> + lxc requires us to design our own build process and networking
>
> + docker has a standard dockerfile format and tools to build images and
> store them in git and do version management
>
> Cons
>
> - additional complexity
>
> - non-persistent containers, it can be solved with volumes
>
> http://www.tech-d.net/2013/12/16/persistent-volumes-with-docker-container-as-volume-pattern/
>
> http://www.offermann.us/2013/12/tiny-docker-pieces-loosely-joined.html
>
> http://crosbymichael.com/advanced-docker-volumes.html
>
> - regarding non-persistent containers will be a lot of questions like "I
> patched nailgun but when I rerun container all changes are gone" (can be
> solved with documentation)
>
>
> Let us know if you have any ideas or questions.
>
> Thanks
>
> --
> Mailing list: https://launchpad.net/~fuel-dev
> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~fuel-dev
> More help   : https://help.launchpad.net/ListHelp
>