[openstack-dev] [higgins] Continued discussion from the last team meeting

Hongbin Lu hongbin.lu at huawei.com
Tue May 24 20:55:28 UTC 2016

Hi all,

At the last team meeting, we tried to define the scope of the Higgins project. In general, we agreed to focus on the following features as an initial start:

*         Build a container abstraction and use docker as the first implementation.

*         Focus on basic container operations (i.e. CRUD), and leave advanced operations (i.e. keep container alive, rolling upgrade, etc.) to users or other projects/services.

*         Start with non-nested container use cases (e.g. containers on physical hosts), and revisit nested container use cases (e.g. containers on VMs) later.
The items below needs further discussion so I started this ML to discuss it.

1.       Container composition: implement a docker compose like feature

2.       Container host management: abstract container host
For #1, it seems we broadly agreed that this is a useful feature. The argument is where this feature belongs to. Some people think this feature belongs to other projects, such as Heat, and others think it belongs to Higgins so we should implement it. For #2, we were mainly debating two things: where the container hosts come from (provisioned by Nova or provided by operators); should we expose host management APIs to end-users? Thoughts?

Best regards,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160524/ddaae0b6/attachment.html>

More information about the OpenStack-dev mailing list