Open Stack

Same question here. I also wonder why a new service. Yes the capabilities
might be different (but then can't this be fixed this is nova by making
nova support different capabilities in different hypervisors better). The
api's also might be different (but then can't this be fixed by making the
api plugins more comprehensive, perhaps attached to the capabilities
somehow). 

I go back to an example (maybe a bad one) that if u think of nova as a
project similar to eclipse (not really, just a temporary analogy). If u
have used eclipse there exists have whole plugins into eclipse which
drastically alter how and what eclipse offers. If nova was more like
eclipse (at least in this aspect) then couldn't there be a set of plugins
that could be added that would add or remove container support, and nova
would provide the core foundation eclipse platform (maybe stretching the
analogy too far here).

Just a think to think about.

-Josh

On 11/18/13 2:28 PM, "Stuart Fox" <stuart at demonware.net> wrote:

>Hey all
>
>Not having been at the summit (maybe the next one), could somebody give a
>really short explanation as to why it needs to be a separate service?
>It sounds like it should fit within the Nova area. It is, after all, just
>another hypervisor type, or so it seems.
>
>(I can¹t find the justification on the OS site)
>
>-------------------------------------------
>BR,
>Stuart Fox
>Manager, Systems Engineering
>Demonware
>+17783753701
>
>On Nov 18, 2013, at 2:05 PM, Sam Alba <sam.alba at gmail.com> wrote:
>
>> Hello everyone,
>> 
>> As some of you already know - in Hong-Kong during the last OpenStack
>> Summit - we ran a design session in the Nova topic titled "Docker
>> support in OpenStack". The session concluded in developing a new
>> OpenStack service for supporting containers instead of modifying Nova
>> to support both VMs and containers.
>> 
>> As said earlier, I am proposing a first draft of the spec for the
>> service. I've explicitly CC'ed all people who signed up at the end of
>> the design session.
>> 
>> Here is it: https://etherpad.openstack.org/p/containers-service
>> 
>> Once we agree on the HTTP API and on the plugin API, the idea is to
>> implement a first simple version that would support mono-host. Then it
>> would evolve in multi-host really quickly by adding a scheduler and a
>> messaging layer (more details in the etherpad).
>> 
>> Please have a look if you're interested in using Containers (and
>> Docker) in OpenStack.
>> 
>> Thanks Russell for giving some early feedback.
>> 
>> Also, Krishna Raman from RedHat already gave a first shot at drafting
>> the Rest API:
>> 
>> https://etherpad.openstack.org/p/containers-service-api
>> 
>> 
>> Sam
>> 
>> -- 
>> @sam_alba
>> 
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>_______________________________________________
>OpenStack-dev mailing list
>OpenStack-dev at lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev