<div>Hi, Adrian, Jay and all,</div><div><br></div><div>There could be a much longer version of this, but let me try to explain in a minimalist way.</div><div><br></div><div>Bay currently has two modes: VM-based, BM-based. In both cases, Bay helps to isolate different tenants' containers. In other words, bay is single-tenancy. For BM-based bay, the single tenancy is a worthy tradeoff, given the performance merits of LXC vs VM. However, for a VM-based bay, there is no performance gain, but single tenancy seems a must, due to the lack of isolation in container. Hyper, as a hypervisor-based substitute for container, brings the much-needed isolation, and therefore enables multi-tenancy. In HyperStack, we don't really need Ironic to provision multiple Hyper bays. On the other hand,  the entire HyperStack cluster is a single big "bay". Pretty similar to how Nova works.</div><div><br></div><div>Also, HyperStack is able to leverage Cinder, Neutron for SDS/SDN functionality. So when someone submits a Docker Compose app, HyperStack would launch HyperVMs and call Cinder/Neutron to setup the volumes and network. The architecture is quite simple.</div><div><br></div><div>Here are a blog I'd like to recommend: <span style="line-height: 1.5;">https://hyper.sh/blog/post/2015/06/29/docker-hyper-and-the-end-of-guest-os.html</span></div><div><includetail><div> </div><div>Let me know your questions.</div><div><br></div><div>Thanks,</div><div>Peng</div><div><br></div><div style="font:Verdana normal 14px;color:#000;"><div style="FONT-SIZE: 12px;FONT-FAMILY: Arial Narrow;padding:2px 0 2px 0;">------------------ Original ------------------</div><div style="FONT-SIZE: 12px;background:#efefef;padding:8px;"><div id="menu_sender"><b>From: </b> "Adrian Otto"<adrian.otto@rackspace.com>;</div><div><b>Date: </b> Thu, Jul 16, 2015 11:02 PM</div><div><b>To: </b> "OpenStack Development Mailing List (not for usage questions)"<openstack-dev@lists.openstack.org>; <wbr></div><div></div><div><b>Subject: </b> Re: [openstack-dev] [magnum][bp] Power Magnum to run onmetalwith        Hyper</div></div><div> </div>




Jay,
<div class=""><br class="">
</div>
<div class="">Hyper is a substitute for a Docker host, so I expect it could work equally well for all of the current bay types. Hyper’s idea of a “pod” and a Kubernetes “pod” are similar, but different. I’m not yet convinced that integrating Hyper host creation
 direct with Magnum (and completely bypassing nova) is a good idea. It probably makes more sense to implement use nova with the ironic dirt driver to provision Hyper hosts so we can use those as substitutes for Bay nodes in our various Bay types. This would
 fit in the place were we use Fedora Atomic today. We could still rely on nova to do all of the machine instance management and accounting like we do today, but produce bays that use Hyper instead of a Docker host. Everywhere we currently offer CoreOS as an
 option we could also offer Hyper as an alternative, with some caveats. </div>
<div class=""><br class="">
</div>
<div class="">There may be some caveats/drawbacks to consider before committing to a Hyper integration. I’ll be asking those of Peng also on this thread, so keep an eye out.</div>
<div class=""><br class="">
</div>
<div class="">Thanks,</div>
<div class=""><br class="">
</div>
<div class="">Adrian</div>
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Jul 16, 2015, at 3:23 AM, Jay Lau <<a href="mailto:jay.lau.513@gmail.com" class="">jay.lau.513@gmail.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">
<div class="">
<div class="">
<div class="">Thanks Peng, then I can see two integration points for Magnum and Hyper:<br class="">
<br class="">
</div>
1) Once Hyper and k8s integration finished, we can deploy k8s in two mode: docker and hyper mode, the end user can select which mode they want to use. For such case, we do not need to create a new bay but may need some enhancement for current k8s bay<br class="">
<br class="">
</div>
2) After mesos and hyper integration,  we can treat mesos and hyper as a new bay to magnum. Just like what we are doing now for mesos+marathon.<br class="">
<br class="">
</div>
Thanks!<br class="">
</div>
<div class="gmail_extra"><br class="">
<div class="gmail_quote">2015-07-16 17:38 GMT+08:00 Peng Zhao <span dir="ltr" class="">
<<a href="mailto:peng@hyper.sh" target="_blank" class="">peng@hyper.sh</a>></span>:<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<u class=""></u>
<div style="word-wrap:normal;word-break:break-word" class="">
<table valign="top" style="width:100%;margin-top:6px" border="0" cellpadding="0" cellspacing="0" lang="container" class="">
<tbody class="">
<tr class="">
<td style="line-height:1.31;color:#222;font-family:arial,sans-serif" valign="top" class="">
<div style="max-width:590px" class="">Hi Jay,</div>
<div style="max-width:590px" class=""><br class="">
</div>
<div style="max-width:590px" class="">Yes, we are working with the community to integrate Hyper with Mesos and K8S. Since Hyper uses Pod as the default job unit, it is quite easy to integrate with K8S. Mesos takes a bit more efforts, but still straightforward.</div>
<div style="max-width:590px" class=""><br class="">
</div>
<div style="max-width:590px" class="">We expect to finish both integration in v0.4 early August.</div>
<div style="max-width:590px" class=""><br class="">
</div>
<div style="max-width:590px" class="">Best,</div>
<span class="">
<div style="max-width:590px" class="">Peng</div>
<div style="max-width:590px" class=""><br class="">
</div>
<div style="max-width:590px" class="">
<div style="font-size:13px;line-height:1.25;max-width:590px" class="">
<div style="font-size:14px;max-width:590px" class="">-----------------------------------------------------</div>
<div style="font-size:14px;max-width:590px" class="">Hyper - Make VM run like Container</div>
<div style="font-size:14px;max-width:590px" class=""><br class="">
</div>
</div>
</div>
<br class="">
</span>
<div class="gmail_extra"><br class="">
<div class="gmail_quote">
<div class="">
<div class="h5">On Thu, Jul 16, 2015 at 3:47 PM, Jay Lau <span dir="ltr" class="">
<<a href="mailto:jay.lau.513@gmail.com" target="_blank" class="">jay.lau.513@gmail.com</a>></span> wrote:<br class="">
</div>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">
<div class="h5">
<div dir="ltr" class="">
<div class="">Hi Peng,<br class="">
<br class="">
<br class="">
</div>
<div class="">Just want to get more for Hyper. If we create a hyper bay, then can I set up multiple hosts in a hyper bay? If so, who will do the scheduling, does mesos or some others integrate with hyper?
<br class="">
<br class="">
</div>
<div class="">I did not find much info for hyper cluster management.<br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Thanks.<br class="">
</div>
</div>
</div>
</div>
<div class="gmail_extra">
<div class="">
<div class=""><br class="">
<div class="gmail_quote">
<div class="">
<div class="h5">2015-07-16 9:54 GMT+08:00 Peng Zhao <span dir="ltr" class=""><<a href="mailto:peng@hyper.sh" target="_blank" class="">peng@hyper.sh</a>></span>:<br class="">
</div>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">
<div class="h5">
<div class="">
<div class="">
<div class=""><br class="">
</div>
<div class=""><u class=""></u>
<div class=""> </div>
<div class=""></div>
<div style="" class="">
<div dir="ltr" class="">
<div class="gmail_quote">
<div style="word-wrap:normal;word-break:break-word" class="">
<table valign="top" style="width:100%;margin-top:6px" border="0" cellpadding="0" cellspacing="0" lang="container" class="">
<tbody class="">
<tr class="">
<td style="line-height:1.31;color:#222;font-family:arial,sans-serif" valign="top" class="">
<div class="gmail_extra" style="max-width:590px">
<div class="gmail_quote" style="max-width:590px"><br class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=""><br class="">
</div>
<div class=""><u class=""></u>
<div class=""> <br class="">
</div>
<div class=""> <br class="">
</div>
<div style="" class="">
<div style="FONT-SIZE:12px;FONT-FAMILY:Arial Narrow;padding:2px 0 2px 0" class="">
------------------ Original ------------------</div>
<div style="FONT-SIZE:12px;background:#efefef;padding:8px" class="">
<div class=""><b class="">From: </b> “Adrian Otto”<<a href="mailto:adrian.otto@rackspace.com" target="_blank" class="">adrian.otto@rackspace.com</a>>;</div>
<div class=""><b class="">Date: </b> Wed, Jul 15, 2015 02:31 AM</div>
<div class=""><b class="">To: </b> “OpenStack Development Mailing List (not for usage questions)“<<a href="mailto:openstack-dev@lists.openstack.org" target="_blank" class="">openstack-dev@lists.openstack.org</a>>;
</div>
<div class=""><br class="">
</div>
<div class=""><b class="">Subject: </b> Re: [openstack-dev] [magnum][bp] Power Magnum to run onmetal withHyper</div>
</div>
<div class=""> <br class="">
</div>
Peng,
<div class=""><br class="">
<div class="">
<blockquote type="cite" class="">
<div class="">On Jul 13, 2015, at 8:37 PM, Peng Zhao <<a href="mailto:peng@hyper.sh" target="_blank" class="">peng@hyper.sh</a>> wrote:</div>
<br class="">
<div class="">
<div class="">Thanks Adrian!</div>
<div class=""><br class="">
</div>
<div class="">Hi, all,</div>
<div class=""><br class="">
</div>
<div class="">Let me recap what is hyper and the idea of hyperstack. </div>
<div class=""><br class="">
</div>
<div class=""><span style="line-height:1.5" class="">Hyper is a single-host runtime engine.</span><span style="line-height:1.5" class=""> </span>Technically,
</div>
<div class="">Docker = LXC + AUFS</div>
<div class="">Hyper = Hypervisor + AUFS</div>
<div class=""><span style="line-height:1.5" class="">where AUFS is the Docker image.</span></div>
</div>
</blockquote>
<div class=""><br class="">
</div>
I do not understand the last line above. My understanding is that AUFS == UnionFS, which is used to implement a storage driver for Docker. Others exist for btrfs, and devicemapper. You select which one you want by setting an option like this:</div>
<div class=""><br class="">
</div>
<div class="">DOCKEROPTS=<span class=""><span class="">”</span>-s devicemapper<span class="">”</span></span></div>
<div class=""><br class="">
</div>
<div style="max-width:590px" class="">Are you trying to say that with Hyper, AUFS is used to provide layered Docker image capability that are shared by multiple hypervisor guests?</div>
</div>
<div style="max-width:590px" class=""><br class="">
</div>
</div>
</div>
</blockquote>
<font class="">
<div class="gmail_quote" style="max-width:590px"><font class="">Peng >>> Yes, AUFS implies the Docker images here.</font></div>
<br class="">
</font>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">
<div style="" class="">
<div class="">
<div class="">My guess is that you are trying to articulate that a host running Hyper is a 1:1 substitute for a host running Docker, and will respond using the Docker remote API. This would result in containers running on the same host that have a superior
 security isolation than they would if LXC was used as the backend to Docker. Is this correct?</div>
</div>
<div class=""><br class="">
</div>
</div>
</div>
</blockquote>
<font class="">Peng>>> Exactly</font>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">
<div style="" class="">
<div class="">
<div style="max-width:590px" class=""><br class="">
<blockquote type="cite" class="">
<div class="">
<div class=""><span style="line-height:1.5" class="">Due to the shared-kernel nature of LXC, Docker lacks of the necessary isolation in a multi-tenant CaaS platform, and this is what Hyper/hypervisor is good at.</span></div>
<div class=""><br class="">
</div>
<div class="">And because of this, most CaaS today run on top of IaaS: <a href="https://trello-attachments.s3.amazonaws.com/55545e127c7cbe0ec5b82f2b/388x275/e286dea1266b46c1999d566b0f9e326b/iaas.png" target="_blank" class="">
https://trello-attachments.s3.amazonaws.com/55545e127c7cbe0ec5b82f2b/388x275/e286dea1266b46c1999d566b0f9e326b/iaas.png</a></div>
<div class="">Hyper enables the native, secure, bare-metal CaaS  <a href="https://trello-attachments.s3.amazonaws.com/55545e127c7cbe0ec5b82f2b/395x244/828ad577dafb3f357e95899e962651b2/caas.png" target="_blank" class="">https://trello-attachments.s3.amazonaws.com/55545e127c7cbe0ec5b82f2b/395x244/828ad577dafb3f357e95899e962651b2/caas.png</a></div>
<div class=""><br class="">
</div>
<div class="">From the tech stack perspective, Hyperstack turns Magnum o run in parallel with Nova, not running on atop.</div>
</div>
</blockquote>
<div class=""><br class="">
</div>
For this to work, we’d expect to get a compute host from Heat, so if the bay type were set to “hyper”, we’d need to use a template that can produce a compute host running Hyper. How would that host be produced, if we do not get it from nova? Might it make more
 sense to make a dirt driver for nova that could produce a Hyper guest on a host already running the nova-compute agent? That way Magnum would not need to re-create any of Nova’s functionality in order to produce nova instances of type “hyper”.</div>
</div>
</div>
</div>
</blockquote>
<font class="">
<div class="gmail_quote" style="max-width:590px"><font class=""><br class="">
</font></div>
<div class="gmail_quote" style="max-width:590px"><font class="">Peng >>> We don’t have to get the physical host from nova. Let’s say</font></div>
<div class="gmail_quote" style="max-width:590px"><font class="">   OpenStack = Nova+Cinder+Neutron+Bare-metal+KVM, so “AWS-like IaaS for everyone else”<br class="">
</font></div>
<div class="gmail_quote" style="max-width:590px"><font class="">   HyperStack= Magnum+Cinder+Neutron+Bare-metal+Hyper, then “Google-like CaaS for everyone else”</font></div>
<div class="gmail_quote" style="max-width:590px"><font class=""><br class="">
</font></div>
<div class="gmail_quote" style="max-width:590px">Ideally, customers should deploy a single OpenStack cluster, with both nova/kvm and magnum/hyper. I’m looking for a solution to make nova/magnum co-exist.</div>
<br class="">
</font>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">
<div style="" class="">
<div class="">
<div class="">Is Hyper compatible with libvirt?</div>
</div>
</div>
</div>
</blockquote>
<font class="">
<div class="gmail_quote" style="max-width:590px"><font class=""><br class="">
</font></div>
<div class="gmail_quote" style="max-width:590px"><font class="">Peng>>> We are working on the libvirt integration, expect in v0.5</font></div>
<br class="">
</font>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">
<div style="" class="">
<div class="">
<div class=""><br class="">
</div>
<div class="">Can Hyper support nested Docker containers within the Hyper guest?</div>
</div>
</div>
</div>
</blockquote>
<font class="">
<div class="gmail_quote" style="max-width:590px"><font class=""><br class="">
</font></div>
Peng>>> Docker in Docker? In a HyperVM instance, there is no docker daemon, cgroup and namespace (except MNT for pod). VM serves the purpose of isolation. We plan to support cgroup and namespace, so you can control whether multiple containers in a pod share
 the same namespace, or completely isolated. But in either case, no docker daemon is present.</font></div>
<div class="gmail_quote" style="max-width:590px"><font class=""><br class="">
</font>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">
<div style="" class="">
<div class="">
<div class=""><br class="">
</div>
<div class="">Thanks,</div>
<div class=""><br class="">
</div>
<div class="">Adrian Otto</div>
<div class=""><br class="">
</div>
<div class="">
<blockquote type="cite" class="">
<div class="">
<div class=""><br class="">
</div>
<div class="">
<div class="">Best,</div>
<div class="">Peng</div>
<div class=""> <br class="">
</div>
<div class="">
<div style="FONT-SIZE:12px;FONT-FAMILY:Arial Narrow;padding:2px 0 2px 0" class="">
------------------ Original ------------------</div>
<div style="FONT-SIZE:12px;background:#efefef;padding:8px" class="">
<div class=""><b class="">From: </b> “Adrian Otto”<<a href="mailto:adrian.otto@rackspace.com" target="_blank" class="">adrian.otto@rackspace.com</a>>;</div>
<div class=""><b class="">Date: </b> Tue, Jul 14, 2015 07:18 AM</div>
<div class=""><b class="">To: </b> “OpenStack Development Mailing List (not for usage questions)“<<a href="mailto:openstack-dev@lists.openstack.org" target="_blank" class="">openstack-dev@lists.openstack.org</a>>;
</div>
<div class=""><br class="">
</div>
<div class=""><b class="">Subject: </b> Re: [openstack-dev] [magnum][bp] Power Magnum to run on metal withHyper</div>
</div>
<div class=""> <br class="">
</div>
Team,
<div class=""><br class="">
</div>
<div class="">I woud like to ask for your input about adding support for Hyper in Magnum:</div>
<div class=""><br class="">
</div>
<div class=""><a href="https://blueprints.launchpad.net/magnum/+spec/hyperstack" target="_blank" class="">https://blueprints.launchpad.net/magnum/+spec/hyperstack</a></div>
<div class=""><br class="">
</div>
<div class="">We touched on this in our last team meeting, and it was apparent that achieving a higher level of understanding of the technology before weighing in about the directional approval of this blueprint. Peng Zhao and Xu Wang have graciously agreed
 to respond to this thread to address questions about how the technology works, and how it could be integrated with Magnum.</div>
<div class=""><br class="">
</div>
<div class="">Please take a moment to review the blueprint, and ask your questions here on this thread.</div>
<div class=""><br class="">
</div>
<div class="">Thanks,</div>
<div class=""><br class="">
</div>
<div class="">Adrian Otto</div>
<div class=""><br class="">
</div>
<div class="">
<blockquote type="cite" class="">
<div class="">On Jul 2, 2015, at 8:48 PM, Peng Zhao <<a href="mailto:peng@hyper.sh" target="_blank" class="">peng@hyper.sh</a>> wrote:</div>
<br class="">
<div class="">
<table valign="top" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;width:743px;margin-top:6px" border="0" cellpadding="0" cellspacing="0" lang="container" class="">
<tbody class="">
<tr class="">
<td style="padding-top:6px;line-height:1.31;color:rgb(34,34,34);font-family:arial,sans-serif" valign="top" class="">
<div class="">Here is the bp of Magnum+Hyper+Metal integration: <a href="https://blueprints.launchpad.net/magnum/+spec/hyperstack" style="word-wrap:normal;word-break:break-word" target="_blank" class="">
https://blueprints.launchpad.net/magnum/+spec/hyperstack</a></div>
<div class=""><br class="">
</div>
<div class="">Wanted to hear more thoughts and kickstart some brainstorming.</div>
<div class=""><br class="">
</div>
<div class="">Thanks,</div>
<div class="">Peng</div>
<div class=""><br class="">
</div>
<div class="">-----------------------------------------------------</div>
<div class="">Hyper - Make VM run like Container</div>
<div class=""><br class="">
</div>
<img style="border:0px;width:0px;min-height:0px" height="0" width="0" class=""></td>
</tr>
</tbody>
</table>
<span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important" class="">__________________________________________________________________________</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="">
<span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important" class="">OpenStack
 Development Mailing List (not for usage questions)</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="">
<span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important" class="">Unsubscribe:<span class=""> </span></span><a href="mailto:OpenStack-dev-request@lists.openstack.org" style="word-wrap:normal;word-break:break-word;font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank" class="">OpenStack-dev-request@lists.openstack.org</a><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important" class="">?subject:unsubscribe</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" style="word-wrap:normal;word-break:break-word;font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></div>
</blockquote>
</div>
<br class="">
</div>
</div>
__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank" class="">
OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
<u class=""></u></div>
</blockquote>
</div>
<br class="">
</div>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<br class="">
</div>
</div>
<u class=""></u></div>
</div>
</div>
<br class="">
</div>
</div>
<span class="">__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
<br class="">
</span></blockquote>
</div>
<br class="">
<br class="">
</div>
</div>
<span class=""><span class=""><font color="#888888" class="">-- <br class="">
<div class="">
<div dir="ltr" class="">
<div class="">
<div dir="ltr" class="">
<div class="">Thanks,<br class="">
<br class="">
</div>
Jay Lau (Guangya Liu)<br class="">
</div>
</div>
</div>
</div>
</font></span></span></div>
<span class=""><br class="">
__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
<br class="">
</span></blockquote>
</div>
<br class="">
</div>
<img style="border:0;width:0px;min-height:0px" src="https://app.mixmax.com/api/track/v2/DrWziYtTJofqeDgT1/ig2cuIXZwlHaAdmblBnI/IyZy9mLrNWY0NnblB3buMHdzlGbAZXZk1yajFGdz5WZw9mI/iQ3cpxEIn5WaslWYNBCduVWbw9GblZXZEByajFGdT5WZw9kI?sc=false" height="0" width="0" class="">
</td>
</tr>
</tbody>
</table>
</div>
<br class="">
__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
<br class="">
</blockquote>
</div>
<br class="">
<br clear="all" class="">
<br class="">
-- <br class="">
<div class="gmail_signature">
<div dir="ltr" class="">
<div class="">
<div dir="ltr" class="">
<div class="">Thanks,<br class="">
<br class="">
</div>
Jay Lau (Guangya Liu)<br class="">
</div>
</div>
</div>
</div>
</div>
__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">
OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
</div>
</blockquote>
</div>
<br class="">
</div>


</div><!--<![endif]--></includetail></div>