[openstack-dev] [Solum] Working group on language packs
ccoleman at redhat.com
Sun Nov 24 00:30:44 UTC 2013
> On Nov 23, 2013, at 6:48 PM, Robert Collins <robertc at robertcollins.net> wrote:
> Ok, so no - diskimage-builder builds regular OpenStack full disk disk images.
> Translating that to a filesystem is easy; doing a diff against another
> filesystem version is also doable, and if the container service for
> Nova understands such partial container contents you could certainly
> glue it all in together, but we don't have any specific glue for that
> I think docker is great, and if the goal of solum is to deploy via
> docker, I'd suggest using docker - no need to make diskimage-builder
> into a docker clone.
> OTOH if you're deploying via heat, I think Diskimage-builder is
> targeted directly at your needs : we wrote it for deploying OpenStack
> after all.
I think we're targeting all possible deployment paths, rather than just one. Docker simply represents one emerging direction for deployments due to its speed and efficiency (which vms can't match).
The base concept (images and image like constructs that can be started by nova) provides a clean abstraction - how those images are created is specific to the ecosystem or organization. An organization that is heavily invested in a particular image creation technology already can still take advantage of Solum, because all that is necessary for Solum to know about is a thin shim around transforming that base image into a deployable image. The developer and administrative support roles can split responsibilities - one that maintains a baseline, and one that consumes that baseline.
>> On 24 November 2013 12:24, Adrian Otto <adrian.otto at rackspace.com> wrote:
>> On Nov 23, 2013, at 2:39 PM, Robert Collins <robertc at robertcollins.net>
>>> On 24 November 2013 05:42, Clayton Coleman <ccoleman at redhat.com> wrote:
>>>>> Containers will work fine in diskimage-builder. One only needs to hack
>>>>> in the ability to save in the container image format rather than qcow2.
>>>> That's good to know. Will diskimage-builder be able to break those down into multiple layers?
>>> What do you mean?
>> Docker images can be layered. You can have a base image on the bottom, and then an arbitrary number of deltas on top of that. It essentially works like incremental backups do. You can think of it as each "layer" has a parent image, and if they all collapse together, you get the current state. Keeping track of past layers gives you the potential for rolling back to a particular restore point, or only distributing incremental changes when you know that the previous layer is already on the host.
>>> Robert Collins <rbtcollins at hp.com>
>>> Distinguished Technologist
>>> HP Converged Cloud
>>> OpenStack-dev mailing list
>>> OpenStack-dev at lists.openstack.org
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
> Robert Collins <rbtcollins at hp.com>
> Distinguished Technologist
> HP Converged Cloud
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
More information about the OpenStack-dev