Open Stack

On 2/9/15, 3:02 AM, "Thierry Carrez" <thierry at openstack.org> wrote:

>Adrian Otto wrote:
>> [...]
>> We have multiple options for solving this challenge. Here are a few:
>> 
>> 1) Cherry pick scheduler code from Nova, which already has a working a
>>filter scheduler design.
>> 2) Integrate swarmd to leverage its scheduler[2].
>> 3) Wait for the Gantt, when Nova Scheduler to be moved out of Nova.
>>This is expected to happen about a year from now, possibly sooner.
>> 4) Write our own filter scheduler, inspired by Nova.
>
>I haven't looked enough into Swarm to answer that question myself, but
>how much would #2 tie Magnum to Docker containers ?
>
>There is value for Magnum to support other container engines / formats
>(think Rocket/Appc) in the long run, so we should avoid early design
>choices that would prevent such support in the future.

Thierry,
Magnum has an object type of a bay which represents the underlying cluster
architecture used.  This could be kubernetes, raw docker, swarmd, or some
future invention.  This way Magnum can grow independently of the
underlying technology and provide a satisfactory user experience dealing
with the chaos that is the container development world :)

We will absolutely support relevant container technology, likely through
new Bay formats (which are really just heat templates).

Regards
-steve

>
>-- 
>Thierry Carrez (ttx)
>
>__________________________________________________________________________
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev