<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 22 June 2015 at 16:52, Peng Zhao <span dir="ltr"><<a href="mailto:peng@hyper.sh" target="_blank">peng@hyper.sh</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<u></u>
<div style="word-wrap:normal;word-break:break-word">
<table lang="container" border="0" cellpadding="0" cellspacing="0" valign="top" style="width:100%;margin-top:6px">
<tbody><tr>
<td valign="top" style="line-height:1.31;color:#222;font-family:'Segoe UI','Helvetica Neue',Helvetica,'Calibri',Arial,sans-serif">
<div>Thanks John.</div><div><br></div><div>I’m also not sure what the future would be, but I’d say that it would be nice to have a hybrid OpenStack cluster of both VM/App-Container flavor. And yes, it is more about a unified model between Nova and Magnum.</div></td></tr></tbody></table></div></blockquote><div><br></div><div>In my head, I always considered heat as a good place to model using both kinds of resources.</div><div><br></div><div>But I can't say I have thought through all the details as yet.</div><div><br></div><div>Thanks,</div><div>John</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:normal;word-break:break-word"><table lang="container" border="0" cellpadding="0" cellspacing="0" valign="top" style="width:100%;margin-top:6px"><tbody><tr><td valign="top" style="line-height:1.31;color:#222;font-family:'Segoe UI','Helvetica Neue',Helvetica,'Calibri',Arial,sans-serif"><div><br></div><div>Best,</div><span class=""><div>Peng</div><div><br></div><div><div style="font-size:13px;line-height:1.25"><div style="font-size:14px;max-width:590px">-----------------------------------------------------</div><div style="font-size:14px;max-width:590px">Hyper - Make VM run like Container</div><div style="font-size:14px;max-width:590px"><br></div></div></div><br></span><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Mon, Jun 22, 2015 at 5:10 PM, John Garbutt <span dir="ltr"><<a href="mailto:john@johngarbutt.com" target="_blank">john@johngarbutt.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">On 22 June 2015 at 09:18, Sahid Orentino Ferdjaoui<br>
<span><<a href="mailto:sahid.ferdjaoui@redhat.com" target="_blank">sahid.ferdjaoui@redhat.com</a>> wrote:<br>
> On Sun, Jun 21, 2015 at 07:18:10PM +0300, Joe Gordon wrote:<br>
>> On Fri, Jun 19, 2015 at 12:55 PM, Peng Zhao <peng@hyper.sh> wrote:<br>
>><br>
>> > Hi, all,<br>
>> ><br>
>> > I would like to propose nova-hyper driver:<br>
>> > <a href="https://blueprints.launchpad.net/nova/+spec/nova-hyper" rel="noreferrer" target="_blank">https://blueprints.launchpad.net/nova/+spec/nova-hyper</a>.<br>
>> ><br>
>> > - What is Hyper?<br>
>> > Put simply, Hyper is a hypervisor-agnostic Docker runtime. It is<br>
>> > similar to Intel’s ClearContainer, allowing to run a Docker image with any<br>
>> > hypervisor.<br>
>> ><br>
>> > - Why Hyper driver?<br>
>> > Given its hypervisor nature, Hyper makes it easy to integrate with<br>
>> > OpenStack ecosystem, e.g. Nova, Cinder, Neutron<br>
>> ><br>
>> > - How to implement?<br>
>> > Similar to nova-docker driver. Hyper has a daemon “hyperd” running on<br>
>> > each physical box. hyperd exposed a set of REST APIs. Integrating Nova with<br>
>> > the APIs would do the job.<br>
<br>
</span>For clarity, we are yet to accept the nova-docker driver into the Nova<br>
project, due to various concerns about its potential future direction.<br>
Hopefully we should get a more final answer on that soon.<br>
<span><br>
>> > - Roadmap<br>
>> > Integrate with Magnum & Ironic.<br>
>> ><br>
>> ><br>
>> This sounds like a better fit for something on top of Nova such as Magnum<br>
>> then as a Nova driver.<br>
<br>
</span>+1<br>
<br>
On the surface, it feels like a possible Magnum driver.<br>
Although I am far from certain that its an exact match.<br>
But I think that would be a better starting point than Nova.<br>
<span><br>
>> Nova only supports things that look like 'VMs'. That includes bare metal,<br>
>> and containers, but it only includes a subset of container features.<br>
<br>
</span>+1<br>
<br>
In your blueprint you mention:<br>
"The difference between LXC and VM makes the driver hard to maintain a<br>
unified model in Nova."<br>
<br>
To be clear Nova has no intention of providing a unified model, in<br>
part due to the truth behind your statement above. We provide things<br>
that look like "servers". Please see:<br>
<a href="http://docs.openstack.org/developer/nova/project_scope.html#containers" rel="noreferrer" target="_blank">http://docs.openstack.org/developer/nova/project_scope.html#containers</a><br>
<br>
I would recommending talking the container subgroup, in one of their<br>
meetings, about how best to integrate with OpenStack:<br>
<a href="https://wiki.openstack.org/wiki/Meetings/Containers" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/Meetings/Containers</a><br>
<span><br>
>> Looking at the hyper CLI [0], there are many commands that nova would not<br>
>> suppprt, such as:<br>
>><br>
>> * The pod notion<br>
>> * exec<br>
>> * pull<br>
><br>
> Then I guess you need to see if Hyper can implement mandatory features<br>
> for Nova [1], [2].<br>
><br>
> [1] <a href="http://docs.openstack.org/developer/nova/support-matrix.html" rel="noreferrer" target="_blank">http://docs.openstack.org/developer/nova/support-matrix.html</a><br>
> [2] <a href="https://wiki.openstack.org/wiki/HypervisorSupportMatrix" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/HypervisorSupportMatrix</a><br>
<br>
</span>We have no intention of expanding the scope of the Nova API to include<br>
container operation. And the reverse is also true, we would want to<br>
see an intention to support all the important existing APIs before<br>
inclusion, and proving that be having tempest tests reliably passing.<br>
<br>
Many thanks,<br>
John<br>
</div></div><div><div><br><span class="">
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</span></div></div></blockquote></div><br></div><img width="0" height="0" style="border:0;width:0px;min-height:0px" src="https://app.mixmax.com/api/track/v2/IcXcvq7LfnSm1P4S8/ig2cuIXZwlHaAdmblBnI/IyZy9mLrNWY0NnblB3buMHdzlGbAZXZk1yajFGdz5WZw9mI/iQ3cpxEIn5WaslWYNBCduVWbw9GblZXZEByajFGdT5WZw9kI?sc=false" alt="">
</td>
</tr>
</tbody></table>
</div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>