<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office">

  <head>
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    
    
    <!--[if gte mso 9]>
    <xml>
      <o:OfficeDocumentSettings>
        <o:AllowPNG/>
        <o:PixelsPerInch>96</o:PixelsPerInch>
     </o:OfficeDocumentSettings>
    </xml>
    <![endif]-->
    
    
    <style type="text/css">* a:hover{cursor:pointer;}</style>
    
  </head>

  <body yahoo="fix" style="word-wrap:normal;  word-break:break-word;">

    
    <!--[if (gte mso 9)|(IE)]>
      <style>a,body {font-family:'Calibri',Arial,sans-serif;}img {border:none !important;-ms-interpolation-mode:bicubic;}td {mso-line-height-rule:exactly !important;}table.border-outer {margin-bottom:15px !important;}.border-middle,.border-inner {width:100%;}td.mso-card-inner table {border-collapse:collapse !important;mso-table-lspace:0pt;mso-table-rspace:0pt;vertical-align:top;}.border-outer,.border-middle,.border-inner {border:none !important;}.mso-border-outer,.mso-border-middle,.mso-border-inner {padding:1px;}.mso-border-outer {background-color:rgb(245,255,255);}.mso-border-middle {background-color:rgb(223,246,255);}.mso-border-inner {background-color:rgb(153,176,225);}.preview-card {margin-bottom:0 !important;padding:0 !important;}.outlook-only {display:block !important;max-height:none !important;overflow:visible !important;}.outlook-com-only {display:none !important;font-size:0 !important;}#mso-one-whole {width:100% !important;}</style>
    <![endif]-->
    
    
    <style>a {word-wrap:normal;word-break:break-word;}@media only screen and (max-width:600px) {.container[not-yahoo] {-webkit-text-size-adjust:none !important;}.container[not-yahoo],.container[not-yahoo] .palm-one-whole {width:100% !important;min-width:100% !important;}.container[not-yahoo] .palm-one-half {width:50% !important;min-width:50% !important;box-sizing:border-box;}img {max-width:100%;}[class="border-outer"],[class="border-middle"],[class="border-inner"],[title="separator"],[class="inner"] {width:100% !important;}[class="innercell"] {padding:8px !important;}.palm-block {display:block !important;}.container[not-yahoo] td.palm-one-whole {display:inline-block !important;padding:0;}.container[not-yahoo] td.palm-one-whole:first-child:not(:only-child) {margin-bottom:16px;}td.hostname {padding-top:3px !important;}}@media only screen and (min-width:601px) {.preview-card {max-width:600px !important;}}@media only screen and (min-device-width :320px) and (max-device-width :568px),only screen and (min-device-width :768px) and (max-device-width :1024px),only screen and (max-device-width:640px),only screen and (max-device-width:667px),only screen and (max-width:480px){table[class="container"] {width:100% !important;min-width:100% !important;}.p,.small,li,font[size="2"],font[size="3"] {font-size:17px !important;line-height:1.5 !important;}audio {margin-bottom:10px;}.background-contain {background-size:contain;}}@media only screen and (min-device-width :320px) and (max-device-width :568px),only screen and (min-device-width :768px) and (max-device-width :1024px),only screen and (min-device-width :1224px)  {.container[not-yahoo] .message-wrapper {padding-top:6px;}.container[not-yahoo] .apple-only[style] {display:block !important;max-height:none !important;line-height:normal !important;overflow:visible !important;height:auto !important;width:100% !important;position:relative !important;}.ExternalClass .ecxapple-only {display:none !important;}.container[not-yahoo] .no-apple {display:none !important;}.container[not-yahoo] .no-apple {display:block;}.container[not-yahoo] form {font-size:inherit;}.container[not-yahoo] form input[type="text"] {height:43px;padding-left:4px !important;}.container[not-yahoo] form button:hover {cursor:pointer;}@media only screen and (min-device-width :1224px)  {.apple-mail-form {display:block !important;background-color:white !important;}}}</style>
    
    
    <style>.ExternalClass {width:100%;}.ExternalClass .outlook-com-button {display:block;}.ExternalClass button {height:auto;}.ExternalClass .outlook-com-hidden {display:none !important;}.ExternalClass .outlook-com-only {display:block !important;max-height:none !important;line-height:normal !important;overflow:visible !important;height:auto !important;width:100% !important;position:relative !important;}</style>
    

    <table class="container" lang="container" not-yahoo="fix" border="0" cellpadding="0" cellspacing="0" valign="top" style="width:100%;  margin-top:6px;">
      <tr>
        <td valign="top" class="message-wrapper" style="line-height: 1.31;  color: #222;  font-family: arial, sans-serif;">

          <!--[if mso]><table width="590" 
border="0" cellpadding="0" cellspacing="0" valign="top" style="border-collapse:separate; "
><tr><td valign="top"><![endif]-->
            <div>Echo with Monty:<br></div><div><br></div><div>> <span style="line-height: 1.31;">I believe that the real win is if Magnum's control plan can integrate the network and storage fabrics > that exist in an OpenStack with kube/mesos/swarm. </span></div><div><span style="line-height: 1.31;"><br></span></div><div>We are working on the Cinder (ceph), Neutron, Keystone integration in HyperStack [1] and love to contribute. Another TODO is the multi-tenancy support in k8s/swarm/mesos. A global scheduler/orchestrator for all tenants yields higher utilization rate than separate schedulers for each.</div><div><br></div><div>[1] https://launchpad.net/hyperstack</div><div><br></div><div class="mixmax_signature"><div style="font-size:13px; line-height: 1.25;"><div style="font-size: 14px; max-width: 590px;" class="p">-----------------------------------------------------</div><div style="font-size: 14px; max-width: 590px;" class="p">Hyper - Make VM run like Container</div><div style="font-size: 14px; max-width: 590px;" class="p"><br></div></div></div><div><font face="Arial, sans-serif" size="2" color="#222222" style="font-size: 13px;"><br></font></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 30, 2015 at 12:00 PM, Monty Taylor <span dir="ltr"><<a href="mailto:mordred@inaugust.com" target="_blank">mordred@inaugust.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">*waving hands wildly at details* ...<br>
<br>
I believe that the real win is if Magnum's control plan can integrate the network and storage fabrics that exist in an OpenStack with kube/mesos/swarm. Just deploying is VERY meh. I do not care - it's not interesting ... an ansible playbook can do that in 5 minutes. OTOH - deploying some kube into a cloud in such a way that it shares a tenant network with some VMs that are there - that's good stuff and I think actually provides significant value.<span class=""><br>
<br>
On 09/29/2015 10:57 PM, Jay Lau wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
+1 to Egor, I think that the final goal of Magnum is container as a<br>
service but not coe deployment as a service. ;-)<br>
<br>
Especially we are also working on Magnum UI, the Magnum UI should export<br>
some interfaces to enable end user can create container applications but<br>
not only coe deployment.<br>
<br>
I hope that the Magnum can be treated as another “Nova” which is<br>
focusing on container service. I know it is difficult to unify all of<br>
the concepts in different coe (k8s has pod, service, rc, swarm only has<br>
container, nova only has VM, PM with different hypervisors), but this<br>
deserve some deep dive and thinking to see how can move forward.....<br>
<br>
On Wed, Sep 30, 2015 at 1:11 AM, Egor Guz <<a href="mailto:EGuz@walmartlabs.com" target="_blank">EGuz@walmartlabs.com</a><br></span><span class="">
<mailto:<a href="mailto:EGuz@walmartlabs.com" target="_blank">EGuz@walmartlabs.com</a>>> wrote:<br>
<br>
    definitely ;), but the are some thoughts to Tom’s email.<br>
<br>
    I agree that we shouldn't reinvent apis, but I don’t think Magnum<br>
    should only focus at deployment (I feel we will become another<br>
    Puppet/Chef/Ansible module if we do it ):)<br>
    I belive our goal should be seamlessly integrate Kub/Mesos/Swarm to<br>
    OpenStack ecosystem (Neutron/Cinder/Barbican/etc) even if we need to<br>
    step in to Kub/Mesos/Swarm communities for that.<br>
<br>
    —<br>
    Egor<br>
<br>
    From: Adrian Otto <<a href="mailto:adrian.otto@rackspace.com" target="_blank">adrian.otto@rackspace.com</a><br></span>
    <mailto:<a href="mailto:adrian.otto@rackspace.com" target="_blank">adrian.otto@rackspace.<wbr>com</a>><mailto:<a href="mailto:adrian.otto@rackspace.com" target="_blank">adrian.otto@racksp<wbr>ace.com</a><span class=""><br>
    <mailto:<a href="mailto:adrian.otto@rackspace.com" target="_blank">adrian.otto@rackspace.<wbr>com</a>>>><br>
    Reply-To: “OpenStack Development Mailing List (not for usage<br>
    questions)“ <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack<wbr>.org</a><br>
    <mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.op<wbr>enstack.org</a>><mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-<wbr>dev@lists.openstack.org</a><br></span><span class="">
    <mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.op<wbr>enstack.org</a>>>><br>
    Date: Tuesday, September 29, 2015 at 08:44<br>
    To: “OpenStack Development Mailing List (not for usage questions)“<br>
    <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack<wbr>.org</a><br></span>
    <mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.op<wbr>enstack.org</a>><mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-<wbr>dev@lists.openstack.org</a><span class=""><br>
    <mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.op<wbr>enstack.org</a>>>><br>
    Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s?<br>
<br></span><span class="">
    This is definitely a topic we should cover in Tokyo.<br>
<br>
    On Sep 29, 2015, at 8:28 AM, Daneyon Hansen (danehans)<br>
    <<a href="mailto:danehans@cisco.com" target="_blank">danehans@cisco.com</a><br></span>
    <mailto:<a href="mailto:danehans@cisco.com" target="_blank">danehans@cisco.com</a>><ma<wbr>ilto:<a href="mailto:danehans@cisco.com" target="_blank">danehans@cisco.com</a><span class=""><br>
    <mailto:<a href="mailto:danehans@cisco.com" target="_blank">danehans@cisco.com</a>>>> wrote:<br>
<br>
<br>
    +1<br>
<br>
    From: Tom Cammann <<a href="mailto:tom.cammann@hpe.com" target="_blank">tom.cammann@hpe.com</a><br></span>
    <mailto:<a href="mailto:tom.cammann@hpe.com" target="_blank">tom.cammann@hpe.com</a>><m<wbr>ailto:<a href="mailto:tom.cammann@hpe.com" target="_blank">tom.cammann@hpe.com</a><br>
    <mailto:<a href="mailto:tom.cammann@hpe.com" target="_blank">tom.cammann@hpe.com</a>>>><br>
    Reply-To: “<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack<wbr>.org</a><br>
    <mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.op<wbr>enstack.org</a>><mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-<wbr>dev@lists.openstack.org</a><br>
    <mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.op<wbr>enstack.org</a>>>”<br>
    <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack<wbr>.org</a><br>
    <mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.op<wbr>enstack.org</a>><mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-<wbr>dev@lists.openstack.org</a><br>
    <mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.op<wbr>enstack.org</a>>>><span class=""><br>
    Date: Tuesday, September 29, 2015 at 2:22 AM<br>
    To: “<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack<wbr>.org</a><br></span>
    <mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.op<wbr>enstack.org</a>><mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-<wbr>dev@lists.openstack.org</a><br>
    <mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.op<wbr>enstack.org</a>>>”<br>
    <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack<wbr>.org</a><br>
    <mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.op<wbr>enstack.org</a>><mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-<wbr>dev@lists.openstack.org</a><span class=""><br>
    <mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.op<wbr>enstack.org</a>>>><br>
    Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s?<br>
<br></span><span class="">
    This has been my thinking in the last couple of months to completely<br>
    deprecate the COE specific APIs such as pod/service/rc and container.<br>
<br>
    As we now support Mesos, Kubernetes and Docker Swarm its going to be<br>
    very difficult and probably a wasted effort trying to consolidate<br>
    their separate APIs under a single Magnum API.<br>
<br>
    I'm starting to see Magnum as COEDaaS - Container Orchestration<br>
    Engine Deployment as a Service.<br>
<br>
    On 29/09/15 06:30, Ton Ngo wrote:<br>
    Would it make sense to ask the opposite of Wanghua's question:<br>
    should pod/service/rc be deprecated if the user can easily get to<br>
    the k8s api?<br>
    Even if we want to orchestrate these in a Heat template, the<br>
    corresponding heat resources can just interface with k8s instead of<br>
    Magnum.<br>
    Ton Ngo,<br>
<br>
    <ATT00001.gif>Egor Guz ---09/28/2015 10:20:02 PM---Also I belive<br>
    docker compose is just command line tool which doesn’t have any api<br>
    or scheduling feat<br>
<br>
    From: Egor Guz <<a href="mailto:EGuz@walmartlabs.com" target="_blank">EGuz@walmartlabs.com</a><br></span>
    <mailto:<a href="mailto:EGuz@walmartlabs.com" target="_blank">EGuz@walmartlabs.com</a>>><wbr><mailto:<a href="mailto:EGuz@walmartlabs.com" target="_blank">EGuz@walmartlabs.com</a><br>
    <mailto:<a href="mailto:EGuz@walmartlabs.com" target="_blank">EGuz@walmartlabs.com</a>>><br>
    To: “<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack<wbr>.org</a><br>
    <mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.op<wbr>enstack.org</a>>“<mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack<wbr>-dev@lists.openstack.org</a><br>
    <mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.op<wbr>enstack.org</a>>><br>
    <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack<wbr>.org</a><br>
    <mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.op<wbr>enstack.org</a>>><mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack<wbr>-dev@lists.openstack.org</a><br>
    <mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.op<wbr>enstack.org</a>>><span class=""><br>
    Date: 09/28/2015 10:20 PM<br>
    Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s?<br>
    ______________________________<wbr>__<br>
<br>
<br>
<br>
    Also I belive docker compose is just command line tool which doesn’t<br>
    have any api or scheduling features.<br>
    But during last Docker Conf hackathon PayPal folks implemented<br>
    docker compose executor for Mesos<br>
    (<a href="https://github.com/mohitsoni/compose-executor" rel="noreferrer" target="_blank">https://github.com/mohitsoni/<wbr>compose-executor</a>)<br>
    which can give you pod like experience.<br>
<br>
    —<br>
    Egor<br>
<br>
    From: Adrian Otto <<a href="mailto:adrian.otto@rackspace.com" target="_blank">adrian.otto@rackspace.com</a><br>
    <mailto:<a href="mailto:adrian.otto@rackspace.com" target="_blank">adrian.otto@rackspace.<wbr>com</a>><mailto:<a href="mailto:adrian.otto@rackspace.com" target="_blank">adrian.otto@racksp<wbr>ace.com</a><br></span>
    <mailto:<a href="mailto:adrian.otto@rackspace.com" target="_blank">adrian.otto@rackspace.<wbr>com</a>>><mailto:<a href="mailto:adrian.otto@rackspace.com" target="_blank">adrian.otto@racks<wbr>pace.com</a><span class=""><br>
    <mailto:<a href="mailto:adrian.otto@rackspace.com" target="_blank">adrian.otto@rackspace.<wbr>com</a>>>><br>
    Reply-To: “OpenStack Development Mailing List (not for usage<br>
    questions)“ <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack<wbr>.org</a><br>
    <mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.op<wbr>enstack.org</a>><mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-<wbr>dev@lists.openstack.org</a><br></span>
    <mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.op<wbr>enstack.org</a>>><mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack<wbr>-dev@lists.openstack.org</a><span class=""><br>
    <mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.op<wbr>enstack.org</a>>>><br>
    Date: Monday, September 28, 2015 at 22:03<br>
    To: “OpenStack Development Mailing List (not for usage questions)“<br>
    <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack<wbr>.org</a><br>
    <mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.op<wbr>enstack.org</a>><mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-<wbr>dev@lists.openstack.org</a><br></span>
    <mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.op<wbr>enstack.org</a>>><mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack<wbr>-dev@lists.openstack.org</a><span class=""><br>
    <mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.op<wbr>enstack.org</a>>>><br>
    Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s?<br>
<br>
    Wanghua,<br>
<br>
    I do follow your logic, but docker-compose only needs the docker API<br>
    to operate. We are intentionally avoiding re-inventing the wheel.<br>
    Our goal is not to replace docker swarm (or other existing systems),<br>
    but to compliment it/them. We want to offer users of Docker the<br>
    richness of native APIs and supporting tools. This way they will not<br>
    need to compromise features or wait longer for us to implement each<br>
    new feature as it is added. Keep in mind that our pod, service, and<br>
    replication controller resources pre-date this philosophy. If we<br>
    started out with the current approach, those would not exist in Magnum.<br>
<br>
    Thanks,<br>
<br>
    Adrian<br>
<br>
    On Sep 28, 2015, at 8:32 PM, 王华 <<a href="mailto:wanghua.humble@gmail.com" target="_blank">wanghua.humble@gmail.com</a><br>
    <mailto:<a href="mailto:wanghua.humble@gmail.com" target="_blank">wanghua.humble@gmail.c<wbr>om</a>><mailto:<a href="mailto:wanghua.humble@gmail.com" target="_blank">wanghua.humble@gmai<wbr>l.com</a><br></span>
    <mailto:<a href="mailto:wanghua.humble@gmail.com" target="_blank">wanghua.humble@gmail.c<wbr>om</a>>><mailto:<a href="mailto:wanghua.humble@gmail.com" target="_blank">wanghua.humble@gma<wbr>il.com</a><span class=""><br>
    <mailto:<a href="mailto:wanghua.humble@gmail.com" target="_blank">wanghua.humble@gmail.c<wbr>om</a>>>> wrote:<br>
<br>
    Hi folks,<br>
<br>
    Magnum now exposes service, pod, etc to users in kubernetes coe, but<br>
    exposes container in swarm coe. As I know, swarm is only a scheduler<br>
    of container, which is like nova in openstack. Docker compose is a<br>
    orchestration program which is like heat in openstack. k8s is the<br>
    combination of scheduler and orchestration. So I think it is better<br>
    to expose the apis in compose to users which are at the same level<br>
    as k8s.<br>
<br>
<br>
    Regards<br>
    Wanghua<br>
    ______________________________<wbr>______________________________<wbr>______________<br>
    OpenStack Development Mailing List (not for usage questions)<br>
    Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org</a><br>
    <mailto:<a href="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank">OpenStack-dev-request@<wbr>lists.openstack.org</a>><mailto:<a href="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank">Op<wbr>enStack-dev-request@lists.open<wbr>stack.org</a><br></span>
    <mailto:<a href="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank">OpenStack-dev-request@<wbr>lists.openstack.org</a>>><mailto:<a href="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank">O<wbr>penStack-dev-request@lists.ope<wbr>nstack.org</a><span class=""><br>
    <mailto:<a href="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank">OpenStack-dev-request@<wbr>lists.openstack.org</a>>>?subject:<wbr>unsubscribe<br>
    <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
    ______________________________<wbr>______________________________<wbr>______________<br>
    OpenStack Development Mailing List (not for usage questions)<br>
    Unsubscribe:<br>
    <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br></span>
    <<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@<wbr>lists.openstack.org?subject:un<wbr>subscribe</a>><mailto:<a href="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank">OpenStack-de<wbr>v-request@lists.openstack.org</a><span class=""><br>
    <mailto:<a href="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank">OpenStack-dev-request@<wbr>lists.openstack.org</a>>?subject:u<wbr>nsubscribe><br>
    <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br>
<br>
<br>
<br>
<br>
    ______________________________<wbr>______________________________<wbr>______________<br>
    OpenStack Development Mailing List (not for usage questions)<br>
    Unsubscribe:<br>
    <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br></span>
    <<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@<wbr>lists.openstack.org?subject:un<wbr>subscribe</a>><mailto:<a href="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank">OpenStack-de<wbr>v-request@lists.openstack.org</a><span class=""><br>
    <mailto:<a href="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank">OpenStack-dev-request@<wbr>lists.openstack.org</a>>?subject:u<wbr>nsubscribe><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openst<wbr>ack.org/cgi-bin/mailman/listin<wbr>fo/openstack-dev</a><br>
<br></span><span class="">
    <ATT00001.gif>________________<wbr>______________________________<wbr>____________________________<br>
    OpenStack Development Mailing List (not for usage questions)<br>
    Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org</a><br></span>
    <mailto:<a href="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank">OpenStack-dev-request@<wbr>lists.openstack.org</a>><mailto:<a href="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank">Op<wbr>enStack-dev-request@lists.open<wbr>stack.org</a><span class=""><br>
    <mailto:<a href="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank">OpenStack-dev-request@<wbr>lists.openstack.org</a>>>?subject:<wbr>unsubscribe<br>
    <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br>
    ______________________________<wbr>______________________________<wbr>______________<br>
    OpenStack Development Mailing List (not for usage questions)<br>
    Unsubscribe:<br>
    <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br></span>
    <<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@<wbr>lists.openstack.org?subject:un<wbr>subscribe</a>><span class=""><br>
    <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br>
<br>
<br>
<br>
--<br>
Thanks,<br>
<br>
Jay Lau (Guangya Liu)<br>
<br>
<br>
______________________________<wbr>______________________________<wbr>______________<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.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br>
</span></blockquote><div class="HOEnZb"><div class="h5">
<br>
<br>
______________________________<wbr>______________________________<wbr>______________<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.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</div></div></blockquote></div><br></div><img width="0" height="0" style="border:0; width:0px; height:0px;" src="https://app.mixmax.com/api/track/v2/l0iaJVhXWp68hsU4C/ig2cuIXZwlHaAdmblBnI/IyZy9mLrNWY0NnblB3buMHdzlGbAZXZk1yajFGdz5WZw9mI/iQ3cpxEIn5WaslWYNBCduVWbw9GblZXZEByajFGdT5WZw9kI?sc=false" alt="">
          <!--[if mso]></td></tr></table><![endif]-->
        </td>
      </tr>
    </table>
  </body>
</html>