<div dir="ltr"><div><div>After more thinking, I agree with Hongbin that instance_type might make customer confused with flavor, what about using server_type?<br><br></div>Actually, nova has concept of server group, the "servers" in this group can be vm. pm or container.<br><br></div>Thanks!<br></div><div class="gmail_extra"><br><div class="gmail_quote">2015-07-16 11:58 GMT+08:00 Kai Qiang Wu <span dir="ltr"><<a href="mailto:wkqwu@cn.ibm.com" target="_blank">wkqwu@cn.ibm.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
<p><font face="sans-serif" size="2">Hi Hong Bin,</font><br>
<br>
<font face="sans-serif" size="2">Thanks for your reply.</font><br>
<br>
<br>
<font face="sans-serif" size="2">I think it is better to discuss the 'platform' Vs instance_type Vs others case first.</font><br>
<font face="sans-serif" size="2">Attach: initial patch (about the discussion): </font><a href="https://review.openstack.org/#/c/200401/" target="_blank"><font color="#0000FF" face="Arial" size="2"><u>https://review.openstack.org/#/c/200401/</u></font></a><br>
<br>
<font face="sans-serif" size="2">My other patches all depend on above patch, if above patch can not reach a meaningful agreement.</font><br>
<br>
<font face="sans-serif" size="2">My following patches would be blocked by that.</font><span class=""><br>
<br>
<br>
<br>
<font face="sans-serif" size="2">Thanks</font><br>
<br>
<br>
<font face="sans-serif" size="2">Best Wishes,</font><br>
<font face="sans-serif" size="2">--------------------------------------------------------------------------------</font><br>
<font face="sans-serif" size="2">Kai Qiang Wu (吴开强 Kennan）<br>
IBM China System and Technology Lab, Beijing<br>
<br>
E-mail: <a href="mailto:wkqwu@cn.ibm.com" target="_blank">wkqwu@cn.ibm.com</a><br>
Tel: 86-10-82451647<br>
Address: Building 28(Ring Building), ZhongGuanCun Software Park, <br>
No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193</font><br>
<font face="sans-serif" size="2">--------------------------------------------------------------------------------</font><br>
<font face="sans-serif" size="2">Follow your heart. You are miracle! </font><br>
<br>
</span><img src="cid:1__=C7BBF417DF8610768f9e8a93df938@cn.ibm.com" alt="Inactive hide details for Hongbin Lu ---07/16/2015 11:47:30 AM---Kai, Sorry for the confusion. To clarify, I was thinking how t" border="0" height="16" width="16"><font color="#424282" face="sans-serif" size="2">Hongbin Lu ---07/16/2015 11:47:30 AM---Kai, Sorry for the confusion. To clarify, I was thinking how to name the field you proposed in baymo</font><span class=""><br>
<br>
<font color="#5F5F5F" face="sans-serif" size="1">From: </font><font face="sans-serif" size="1">Hongbin Lu <<a href="mailto:hongbin.lu@huawei.com" target="_blank">hongbin.lu@huawei.com</a>></font><br>
<font color="#5F5F5F" face="sans-serif" size="1">To: </font><font face="sans-serif" size="1">"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>></font><br>
</span><font color="#5F5F5F" face="sans-serif" size="1">Date: </font><font face="sans-serif" size="1">07/16/2015 11:47 AM</font></p><div><div class="h5"><br>
<font color="#5F5F5F" face="sans-serif" size="1">Subject: </font><font face="sans-serif" size="1">Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?</font><br>
<hr style="color:#8091a5" align="left" noshade size="2" width="100%"><br>
<br>
<br>
<font color="#1F497D" face="Calibri" size="2">Kai,</font><br>
<font color="#1F497D" face="Calibri" size="2"> </font><br>
<font color="#1F497D" face="Calibri" size="2">Sorry for the confusion. To clarify, I was thinking how to name the field you proposed in baymodel [1]. I prefer to drop it and use the existing field ‘flavor’ to map the Heat template.</font><br>
<font color="#1F497D" face="Calibri" size="2"> </font><br>
<font color="#1F497D" face="Calibri" size="2">[1] </font><a href="https://review.openstack.org/#/c/198984/6" target="_blank"><font color="#0000FF" face="Calibri" size="2"><u>https://review.openstack.org/#/c/198984/6</u></font></a><br>
<font color="#1F497D" face="Calibri" size="2"> </font><br>
<font face="Tahoma" size="2"><b>From:</b></font><font face="Tahoma" size="2"> Kai Qiang Wu [</font><font face="Tahoma" size="2"><a href="mailto:wkqwu@cn.ibm.com" target="_blank">mailto:wkqwu@cn.ibm.com</a></font><font face="Tahoma" size="2">] </font><font face="Tahoma" size="2"><b><br>
Sent:</b></font><font face="Tahoma" size="2"> July-15-15 10:36 PM</font><font face="Tahoma" size="2"><b><br>
To:</b></font><font face="Tahoma" size="2"> OpenStack Development Mailing List (not for usage questions)</font><font face="Tahoma" size="2"><b><br>
Subject:</b></font><font face="Tahoma" size="2"> Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?</font><br>
<font face="sans-serif" size="3"> </font>
</div></div><p></p><div><div class="h5"><font face="Arial" size="2">Hi HongBin,</font><font face="sans-serif" size="3"><br>
</font><font face="Arial" size="2"><br>
I think flavors introduces more confusion than nova_instance_type or instance_type.</font><font face="sans-serif" size="3"><br>
<br>
</font><font face="Arial" size="2"><br>
As flavors not have binding with 'vm' or 'baremetal',</font><font face="sans-serif" size="3"><br>
</font><font face="Arial" size="2"><br>
Let me summary the initial question: <br>
We have two kinds of templates for kubernetes now, <br>
(as templates in heat not flexible like programming language, if else etc. And separate templates are easy to maintain)<br>
The two kinds of kubernets templates, One for boot VM, another boot Baremetal. 'VM' or Baremetal here is just used for heat template selection.</font><font face="sans-serif" size="3"><br>
<br>
</font><font face="Arial" size="2"><br>
1> If used flavor, it is nova specific concept: take two as example, <br>
m1.small, or m1.middle. <br>
m1.small < 'VM' m1.middle < 'VM' <br>
Both m1.small and m1.middle can be used in 'VM' environment.<br>
So we should not use m1.small as a template identification. That's why I think flavor not good to be used.</font><font face="sans-serif" size="3"><br>
<br>
</font><font face="Arial" size="2"><br>
2> @Adrian, we have --flavor-id field for baymodel now, it would picked up by heat-templates, and boot instances with such flavor.</font><font face="sans-serif" size="3"><br>
<br>
</font><font face="Arial" size="2"><br>
3> Finally, I think instance_type is better. instance_type can be used as heat templates identification parameter.</font><font face="sans-serif" size="3"><br>
</font><font face="Arial" size="2"><br>
instance_type = 'vm', it means such templates fit for normal 'VM' heat stack deploy</font><font face="sans-serif" size="3"><br>
</font><font face="Arial" size="2"><br>
instance_type = 'baremetal', it means such templates fit for ironic baremetal heat stack deploy.</font><font face="sans-serif" size="3"><br>
<br>
<br>
<br>
<br>
</font><font face="Arial" size="2"><br>
Thanks!</font><font face="sans-serif" size="3"><br>
</font><font face="Arial" size="2"><br>
<br>
Best Wishes,<br>
--------------------------------------------------------------------------------<br>
Kai Qiang Wu (</font><font face="sans-serif" size="2">吴开强</font><font face="Arial" size="2"> Kennan</font><font face="sans-serif" size="2">）</font><font face="Arial" size="2"><br>
IBM China System and Technology Lab, Beijing<br>
<br>
E-mail: </font><a href="mailto:wkqwu@cn.ibm.com" target="_blank"><font color="#0000FF" face="Arial" size="2"><u>wkqwu@cn.ibm.com</u></font></a><font face="Arial" size="2"><br>
Tel: 86-10-82451647<br>
Address: Building 28(Ring Building), ZhongGuanCun Software Park, <br>
No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193<br>
--------------------------------------------------------------------------------<br>
Follow your heart. You are miracle! </font><font face="sans-serif" size="3"><br>
<br>
</font><img src="cid:1__=C7BBF417DF8610768f9e8a93df938@cn.ibm.com" alt="Inactive hide details for Hongbin Lu ---07/16/2015 04:44:14 AM---+1 for the idea of using Nova flavor directly. Why we introduc" height="16" width="16"><font color="#424282" face="Arial" size="2">Hongbin Lu ---07/16/2015 04:44:14 AM---+1 for the idea of using Nova flavor directly. Why we introduced the “platform” field to indicate “v</font><font face="sans-serif" size="3"><br>
</font><font color="#5F5F5F" face="Arial" size="1"><br>
From: </font><font face="Arial" size="1">Hongbin Lu <</font><a href="mailto:hongbin.lu@huawei.com" target="_blank"><font color="#0000FF" face="Arial" size="1"><u>hongbin.lu@huawei.com</u></font></a><font face="Arial" size="1">></font><font color="#5F5F5F" face="Arial" size="1"><br>
To: </font><font face="Arial" size="1">"OpenStack Development Mailing List (not for usage questions)" <</font><a href="mailto:openstack-dev@lists.openstack.org" target="_blank"><font color="#0000FF" face="Arial" size="1"><u>openstack-dev@lists.openstack.org</u></font></a><font face="Arial" size="1">></font><font color="#5F5F5F" face="Arial" size="1"><br>
Date: </font><font face="Arial" size="1">07/16/2015 04:44 AM</font><font color="#5F5F5F" face="Arial" size="1"><br>
Subject: </font><font face="Arial" size="1">Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?</font><br>
<hr align="left" noshade size="2" width="100%"><br>
<font face="sans-serif" size="3"><br>
<br>
</font><font color="#1F497D" face="Calibri" size="2"><br>
+1 for the idea of using Nova flavor directly.<br>
<br>
Why we introduced the “platform” field to indicate “vm” or “baremetel” is that magnum need to map a bay to a Heat template (which will be used to provision the bay). Currently, Magnum has three layers of mapping:</font><font face="sans-serif" size="3"> </font>
<ul style="padding-left:36pt"><font color="#1F497D" face="Symbol" size="2">· </font><font color="#1F497D" face="sans-serif" size="2"> </font><font color="#1F497D" face="Symbol" size="2"> </font><font color="#1F497D" face="sans-serif" size="2"> </font><font color="#1F497D" face="Symbol" size="2"> </font><font color="#1F497D" face="sans-serif" size="2"> </font><font color="#1F497D" face="Symbol" size="2"> </font><font color="#1F497D" face="sans-serif" size="2"> </font><font color="#1F497D" face="Symbol" size="2"> </font><font color="#1F497D" face="Calibri" size="2">platform: vm or baremetal</font><font color="#1F497D" face="Symbol" size="2"><br>
· </font><font color="#1F497D" face="sans-serif" size="2"> </font><font color="#1F497D" face="Symbol" size="2"> </font><font color="#1F497D" face="sans-serif" size="2"> </font><font color="#1F497D" face="Symbol" size="2"> </font><font color="#1F497D" face="sans-serif" size="2"> </font><font color="#1F497D" face="Symbol" size="2"> </font><font color="#1F497D" face="sans-serif" size="2"> </font><font color="#1F497D" face="Symbol" size="2"> </font><font color="#1F497D" face="Calibri" size="2">os: atomic, coreos, …</font><font color="#1F497D" face="Symbol" size="2"><br>
· </font><font color="#1F497D" face="sans-serif" size="2"> </font><font color="#1F497D" face="Symbol" size="2"> </font><font color="#1F497D" face="sans-serif" size="2"> </font><font color="#1F497D" face="Symbol" size="2"> </font><font color="#1F497D" face="sans-serif" size="2"> </font><font color="#1F497D" face="Symbol" size="2"> </font><font color="#1F497D" face="sans-serif" size="2"> </font><font color="#1F497D" face="Symbol" size="2"> </font><font color="#1F497D" face="Calibri" size="2">coe: kubernetes, swarm or mesos</font></ul>
<font color="#1F497D" face="Calibri" size="2"> <br>
I think we could just replace “platform” with “flavor”, if we can populate a list of flovars for VM and another list of flavors for baremetal (We may need an additional list of flavors for container in the future for the nested container use case). Then, the new three layers would be:</font><font face="sans-serif" size="3"> </font>
<ul style="padding-left:36pt"><font color="#1F497D" face="Symbol" size="2">· </font><font color="#1F497D" face="sans-serif" size="2"> </font><font color="#1F497D" face="Symbol" size="2"> </font><font color="#1F497D" face="sans-serif" size="2"> </font><font color="#1F497D" face="Symbol" size="2"> </font><font color="#1F497D" face="sans-serif" size="2"> </font><font color="#1F497D" face="Symbol" size="2"> </font><font color="#1F497D" face="sans-serif" size="2"> </font><font color="#1F497D" face="Symbol" size="2"> </font><font color="#1F497D" face="Calibri" size="2">flavor: baremetal, m1.small, m1.medium, …</font><font color="#1F497D" face="Symbol" size="2"><br>
· </font><font color="#1F497D" face="sans-serif" size="2"> </font><font color="#1F497D" face="Symbol" size="2"> </font><font color="#1F497D" face="sans-serif" size="2"> </font><font color="#1F497D" face="Symbol" size="2"> </font><font color="#1F497D" face="sans-serif" size="2"> </font><font color="#1F497D" face="Symbol" size="2"> </font><font color="#1F497D" face="sans-serif" size="2"> </font><font color="#1F497D" face="Symbol" size="2"> </font><font color="#1F497D" face="Calibri" size="2">os: atomic, coreos, ...</font><font color="#1F497D" face="Symbol" size="2"><br>
· </font><font color="#1F497D" face="sans-serif" size="2"> </font><font color="#1F497D" face="Symbol" size="2"> </font><font color="#1F497D" face="sans-serif" size="2"> </font><font color="#1F497D" face="Symbol" size="2"> </font><font color="#1F497D" face="sans-serif" size="2"> </font><font color="#1F497D" face="Symbol" size="2"> </font><font color="#1F497D" face="sans-serif" size="2"> </font><font color="#1F497D" face="Symbol" size="2"> </font><font color="#1F497D" face="Calibri" size="2">coe: kubernetes, swarm or mesos</font></ul>
<font color="#1F497D" face="Calibri" size="2"> <br>
This approach can avoid introducing a new field in baymodel to indicate what Nova flavor already indicates.<br>
<br>
Best regards,<br>
Hongbin<br>
</font><font face="Tahoma" size="2"><b><br>
From:</b></font><font face="Tahoma" size="2"> Fox, Kevin M [</font><a href="mailto:Kevin.Fox@pnnl.gov" target="_blank"><font color="#0000FF" face="Tahoma" size="2"><u>mailto:Kevin.Fox@pnnl.gov</u></font></a><font face="Tahoma" size="2">] </font><font face="Tahoma" size="2"><b><br>
Sent:</b></font><font face="Tahoma" size="2"> July-15-15 12:37 PM</font><font face="Tahoma" size="2"><b><br>
To:</b></font><font face="Tahoma" size="2"> OpenStack Development Mailing List (not for usage questions)</font><font face="Tahoma" size="2"><b><br>
Subject:</b></font><font face="Tahoma" size="2"> Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?</font><font face="Arial" size="3"><br>
</font><font face="Tahoma" size="2"><br>
Maybe somehow I missed the point, but why not just use raw Nova flavors? They already abstract away irconic vs kvm vs hyperv/etc.<br>
<br>
Thanks,<br>
Kevin</font><div align="center"><hr align="center" size="2" width="100%"></div><font face="Tahoma" size="2"><b>From:</b></font><font face="Tahoma" size="2"> Daneyon Hansen (danehans) [<a href="mailto:danehans@cisco.com" target="_blank">danehans@cisco.com</a>]</font><font face="Tahoma" size="2"><b><br>
Sent:</b></font><font face="Tahoma" size="2"> Wednesday, July 15, 2015 9:20 AM</font><font face="Tahoma" size="2"><b><br>
To:</b></font><font face="Tahoma" size="2"> OpenStack Development Mailing List (not for usage questions)</font><font face="Tahoma" size="2"><b><br>
Subject:</b></font><font face="Tahoma" size="2"> Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?</font><font face="Courier" size="2"><br>
All,</font><font face="Times New Roman" size="2"><br>
</font><font face="Courier" size="2"><br>
IMO virt_type does not properly describe bare metal deployments. What about using the compute_driver parameter?</font><font face="Times New Roman" size="3"><br>
</font><font face="Arial" size="3"><br>
compute_driver</font><font face="Times New Roman" size="2"> = </font><font face="Arial" size="3">None<br>
</font><font face="sans-serif" size="3"><br>
</font><font face="Arial" size="3"><br>
(StrOpt) Driver to use for controlling virtualization. Options include: libvirt.LibvirtDriver, xenapi.XenAPIDriver, fake.FakeDriver, baremetal.BareMetalDriver, vmwareapi.VMwareVCDriver, hyperv.HyperVDriver<br>
</font><font face="sans-serif" size="3"><br>
</font><font color="#0000FF" face="sans-serif" size="3"><u><br>
</u></font><a href="http://docs.openstack.org/kilo/config-reference/content/list-of-compute-config-options.html" target="_blank"><font color="#0000FF" face="Arial" size="3"><u>http://docs.openstack.org/kilo/config-reference/content/list-of-compute-config-options.html</u></font></a><font color="#0000FF" face="sans-serif" size="3"><u><br>
</u></font><a href="http://docs.openstack.org/developer/ironic/deploy/install-guide.html" target="_blank"><font color="#0000FF" face="Times New Roman" size="3"><u>http://docs.openstack.org/developer/ironic/deploy/install-guide.html</u></font></a><font face="Calibri" size="2"><br>
</font><font face="Calibri" size="2"><b><br>
From: </b></font><font face="Calibri" size="2">Adrian Otto <</font><a href="mailto:adrian.otto@rackspace.com" target="_blank"><font color="#0000FF" face="Calibri" size="2"><u>adrian.otto@rackspace.com</u></font></a><font face="Calibri" size="2">></font><font face="Calibri" size="2"><b><br>
Reply-To: </b></font><font face="Calibri" size="2">"OpenStack Development Mailing List (not for usage questions)" <</font><a href="mailto:openstack-dev@lists.openstack.org" target="_blank"><font color="#0000FF" face="Calibri" size="2"><u>openstack-dev@lists.openstack.org</u></font></a><font face="Calibri" size="2">></font><font face="Calibri" size="2"><b><br>
Date: </b></font><font face="Calibri" size="2">Tuesday, July 14, 2015 at 7:44 PM</font><font face="Calibri" size="2"><b><br>
To: </b></font><font face="Calibri" size="2">"OpenStack Development Mailing List (not for usage questions)" <</font><a href="mailto:openstack-dev@lists.openstack.org" target="_blank"><font color="#0000FF" face="Calibri" size="2"><u>openstack-dev@lists.openstack.org</u></font></a><font face="Calibri" size="2">></font><font face="Calibri" size="2"><b><br>
Subject: </b></font><font face="Calibri" size="2">Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?<br>
</font><font face="sans-serif" size="3"> </font>
</div></div><ul style="padding-left:36pt"><div><div class="h5"><font face="Calibri" size="2">One drawback to virt_type if not seen in the context of the acceptable values, is that it should be set to values like libvirt, xen, ironic, etc. That might actually be good. Instead of using the values 'vm' or 'baremetal', we use the name of the nova virt driver, and interpret those to be vm or baremetal types. So if I set the value to 'xen', I know the nova instance type is a vm, and 'ironic' means a baremetal nova instance. <br>
<br>
Adrian<br>
<br>
<br>
-------- Original message --------<br>
From: Hongbin Lu <</font><a href="mailto:hongbin.lu@huawei.com" target="_blank"><font color="#0000FF" face="Calibri" size="2"><u>hongbin.lu@huawei.com</u></font></a><font face="Calibri" size="2">> <br>
Date: 07/14/2015 7:20 PM (GMT-08:00) <br>
To: "OpenStack Development Mailing List (not for usage questions)" <</font><a href="mailto:openstack-dev@lists.openstack.org" target="_blank"><font color="#0000FF" face="Calibri" size="2"><u>openstack-dev@lists.openstack.org</u></font></a><font face="Calibri" size="2">> <br>
Subject: Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type? </font><font color="#1F497D" face="Calibri" size="2"><br>
I am going to propose a third option:<br>
<br>
3. virt_type<br>
<br>
I have concerns about option 1 and 2, because “instance_type” and flavor was used interchangeably before [1]. If we use “instance_type” to indicate “vm” or “baremetal”, it may cause confusions.<br>
<br>
[1] </font><a href="https://blueprints.launchpad.net/nova/+spec/flavor-instance-type-dedup" target="_blank"><font color="#0000FF" face="Calibri" size="2"><u>https://blueprints.launchpad.net/nova/+spec/flavor-instance-type-dedup</u></font></a><font color="#1F497D" face="Calibri" size="2"><br>
<br>
Best regards,<br>
Hongbin<br>
</font><font face="Tahoma" size="2"><b><br>
From:</b></font><font face="Tahoma" size="2"> Kai Qiang Wu [</font><a href="mailto:wkqwu@cn.ibm.com" target="_blank"><font color="#0000FF" face="Tahoma" size="2"><u>mailto:wkqwu@cn.ibm.com</u></font></a><font face="Tahoma" size="2">] </font><font face="Tahoma" size="2"><b><br>
Sent:</b></font><font face="Tahoma" size="2"> July-14-15 9:35 PM</font><font face="Tahoma" size="2"><b><br>
To:</b></font><font face="Tahoma" size="2"> </font><a href="mailto:openstack-dev@lists.openstack.org" target="_blank"><font color="#0000FF" face="Tahoma" size="2"><u>openstack-dev@lists.openstack.org</u></font></a><font face="Tahoma" size="2"><b><br>
Subject:</b></font><font face="Tahoma" size="2"> [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?</font><font face="Arial" size="3"><br>
</font><font face="Arial" size="2"><br>
Hi Magnum Guys,</font><font face="Arial" size="3"><br>
</font><font face="Arial" size="2"><br>
<br>
I want to raise this question through ML.</font><font face="Arial" size="3"><br>
</font><font face="Arial" size="2"><br>
<br>
In this patch </font><a href="https://review.openstack.org/#/c/200401/" target="_blank"><font color="#0000FF" face="Arial" size="2"><u>https://review.openstack.org/#/c/200401/</u></font></a><font face="Arial" size="3"><br>
</font><font face="Arial" size="2"><br>
<br>
For some old history reason, we use </font><font face="Arial" size="2"><b>platform </b></font><font face="Arial" size="2">to indicate 'vm' or 'baremetal'.<br>
This seems not proper for that, @Adrian proposed nova_instance_type, and someone prefer other names, let me summarize as below:</font><font face="Arial" size="3"><br>
</font><font face="Arial" size="2"><br>
<br>
1. nova_instance_type 2 votes<br>
<br>
2. instance_type 2 votes<br>
<br>
3. others (1 vote, but not proposed any name)</font><font face="Arial" size="3"><br>
</font><font face="Arial" size="2"><br>
<br>
Let's try to reach the agreement ASAP. I think count the final votes winner as the proper name is the best solution(considering community diversity).</font><font face="Arial" size="3"><br>
</font><font face="Arial" size="2"><br>
<br>
BTW, If you not proposed any better name, just vote to disagree all, I think that vote is not valid and not helpful to solve the issue.</font><font face="Arial" size="3"><br>
</font><font face="Arial" size="2"><br>
<br>
Please help to vote for that name. </font><font face="Arial" size="3"><br>
</font><font face="Arial" size="2"><br>
<br>
Thanks</font><font face="Arial" size="3"><br>
<br>
<br>
</font><font face="Arial" size="2"><br>
<br>
Best Wishes,<br>
--------------------------------------------------------------------------------<br>
Kai Qiang Wu (</font><font face="sans-serif" size="2">吴开强</font><font face="Arial" size="2"> Kennan</font><font face="sans-serif" size="2">）</font><font face="Arial" size="2"><br>
IBM China System and Technology Lab, Beijing<br>
<br>
E-mail: </font><a href="mailto:wkqwu@cn.ibm.com" target="_blank"><font color="#0000FF" face="Arial" size="2"><u>wkqwu@cn.ibm.com</u></font></a><font face="Arial" size="2"><br>
Tel: 86-10-82451647<br>
Address: Building 28(Ring Building), ZhongGuanCun Software Park, <br>
No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193<br>
--------------------------------------------------------------------------------<br>
Follow your heart. You are miracle! </font><font face="sans-serif" size="2">__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: </font><a href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank"><font color="#0000FF" face="sans-serif" size="2"><u>OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</u></font></a><font color="#0000FF" face="sans-serif" size="2"><u><br>
</u></font></div></div><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><font color="#0000FF" face="sans-serif" size="2"><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></a><tt><font size="2">__________________________________________________________________________<span class=""><br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
</span></font></tt><tt><font size="2"><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></font></tt><tt><font size="2"><br>
</font></tt><br>
</ul>
<p></p><p></p></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><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Thanks,<br><br></div>Jay Lau (Guangya Liu)<br></div></div></div></div>
</div>