<html><body>
<p><font size="2" face="sans-serif">Hi Hong Bin,</font><br>
<br>
<font size="2" face="sans-serif">Thanks for your reply.</font><br>
<br>
<br>
<font size="2" face="sans-serif">I think it is better to discuss the 'platform' Vs instance_type Vs others case first.</font><br>
<font size="2" face="sans-serif">Attach: initial patch (about the discussion): </font><a href="https://review.openstack.org/#/c/200401/" target="_blank"><font size="2" color="#0000FF" face="Arial"><u>https://review.openstack.org/#/c/200401/</u></font></a><br>
<br>
<font size="2" face="sans-serif">My other patches all depend on above patch, if above patch can not reach a meaningful agreement.</font><br>
<br>
<font size="2" face="sans-serif">My following patches would be blocked by that.</font><br>
<br>
<br>
<br>
<font size="2" face="sans-serif">Thanks</font><br>
<br>
<br>
<font size="2" face="sans-serif">Best Wishes,</font><br>
<font size="2" face="sans-serif">--------------------------------------------------------------------------------</font><br>
<font size="2" face="sans-serif">Kai Qiang Wu (吴开强 Kennan）<br>
IBM China System and Technology Lab, Beijing<br>
<br>
E-mail: wkqwu@cn.ibm.com<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 size="2" face="sans-serif">--------------------------------------------------------------------------------</font><br>
<font size="2" face="sans-serif">Follow your heart. You are miracle! </font><br>
<br>
<img width="16" height="16" src="cid:1__=C7BBF417DF8610768f9e8a93df938@cn.ibm.com" border="0" 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"><font size="2" color="#424282" face="sans-serif">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><br>
<br>
<font size="1" color="#5F5F5F" face="sans-serif">From: </font><font size="1" face="sans-serif">Hongbin Lu <hongbin.lu@huawei.com></font><br>
<font size="1" color="#5F5F5F" face="sans-serif">To: </font><font size="1" face="sans-serif">"OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org></font><br>
<font size="1" color="#5F5F5F" face="sans-serif">Date: </font><font size="1" face="sans-serif">07/16/2015 11:47 AM</font><br>
<font size="1" color="#5F5F5F" face="sans-serif">Subject: </font><font size="1" face="sans-serif">Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?</font><br>
<hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br>
<br>
<br>
<font size="2" color="#1F497D" face="Calibri">Kai,</font><br>
<font size="2" color="#1F497D" face="Calibri"> </font><br>
<font size="2" color="#1F497D" face="Calibri">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 size="2" color="#1F497D" face="Calibri"> </font><br>
<font size="2" color="#1F497D" face="Calibri">[1] </font><a href="https://review.openstack.org/#/c/198984/6"><font size="2" color="#0000FF" face="Calibri"><u>https://review.openstack.org/#/c/198984/6</u></font></a><br>
<font size="2" color="#1F497D" face="Calibri"> </font><br>
<font size="2" face="Tahoma"><b>From:</b></font><font size="2" face="Tahoma"> Kai Qiang Wu [</font><font size="2" face="Tahoma"><a href="mailto:wkqwu@cn.ibm.com">mailto:wkqwu@cn.ibm.com</a></font><font size="2" face="Tahoma">] </font><font size="2" face="Tahoma"><b><br>
Sent:</b></font><font size="2" face="Tahoma"> July-15-15 10:36 PM</font><font size="2" face="Tahoma"><b><br>
To:</b></font><font size="2" face="Tahoma"> OpenStack Development Mailing List (not for usage questions)</font><font size="2" face="Tahoma"><b><br>
Subject:</b></font><font size="2" face="Tahoma"> Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?</font><br>
<font size="3" face="sans-serif"> </font>
<p><font size="2" face="Arial">Hi HongBin,</font><font size="3" face="sans-serif"><br>
</font><font size="2" face="Arial"><br>
I think flavors introduces more confusion than nova_instance_type or instance_type.</font><font size="3" face="sans-serif"><br>
<br>
</font><font size="2" face="Arial"><br>
As flavors not have binding with 'vm' or 'baremetal',</font><font size="3" face="sans-serif"><br>
</font><font size="2" face="Arial"><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 size="3" face="sans-serif"><br>
<br>
</font><font size="2" face="Arial"><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 size="3" face="sans-serif"><br>
<br>
</font><font size="2" face="Arial"><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 size="3" face="sans-serif"><br>
<br>
</font><font size="2" face="Arial"><br>
3> Finally, I think instance_type is better. instance_type can be used as heat templates identification parameter.</font><font size="3" face="sans-serif"><br>
</font><font size="2" face="Arial"><br>
instance_type = 'vm', it means such templates fit for normal 'VM' heat stack deploy</font><font size="3" face="sans-serif"><br>
</font><font size="2" face="Arial"><br>
instance_type = 'baremetal', it means such templates fit for ironic baremetal heat stack deploy.</font><font size="3" face="sans-serif"><br>
<br>
<br>
<br>
<br>
</font><font size="2" face="Arial"><br>
Thanks!</font><font size="3" face="sans-serif"><br>
</font><font size="2" face="Arial"><br>
<br>
Best Wishes,<br>
--------------------------------------------------------------------------------<br>
Kai Qiang Wu (</font><font size="2" face="sans-serif">吴开强</font><font size="2" face="Arial"> Kennan</font><font size="2" face="sans-serif">）</font><font size="2" face="Arial"><br>
IBM China System and Technology Lab, Beijing<br>
<br>
E-mail: </font><a href="mailto:wkqwu@cn.ibm.com"><font size="2" color="#0000FF" face="Arial"><u>wkqwu@cn.ibm.com</u></font></a><font size="2" face="Arial"><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 size="3" face="sans-serif"><br>
<br>
</font><img src="cid:1__=C7BBF417DF8610768f9e8a93df938@cn.ibm.com" width="16" height="16" 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"><font size="2" color="#424282" face="Arial">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 size="3" face="sans-serif"><br>
</font><font size="1" color="#5F5F5F" face="Arial"><br>
From: </font><font size="1" face="Arial">Hongbin Lu <</font><a href="mailto:hongbin.lu@huawei.com"><font size="1" color="#0000FF" face="Arial"><u>hongbin.lu@huawei.com</u></font></a><font size="1" face="Arial">></font><font size="1" color="#5F5F5F" face="Arial"><br>
To: </font><font size="1" face="Arial">"OpenStack Development Mailing List (not for usage questions)" <</font><a href="mailto:openstack-dev@lists.openstack.org"><font size="1" color="#0000FF" face="Arial"><u>openstack-dev@lists.openstack.org</u></font></a><font size="1" face="Arial">></font><font size="1" color="#5F5F5F" face="Arial"><br>
Date: </font><font size="1" face="Arial">07/16/2015 04:44 AM</font><font size="1" color="#5F5F5F" face="Arial"><br>
Subject: </font><font size="1" face="Arial">Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?</font><br>
<hr width="100%" size="2" align="left" noshade><br>
<font size="3" face="sans-serif"><br>
<br>
</font><font size="2" color="#1F497D" face="Calibri"><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 size="3" face="sans-serif"> </font>
<ul style="padding-left: 36pt"><font size="2" color="#1F497D" face="Symbol">· </font><font size="2" color="#1F497D" face="sans-serif"> </font><font size="2" color="#1F497D" face="Symbol"> </font><font size="2" color="#1F497D" face="sans-serif"> </font><font size="2" color="#1F497D" face="Symbol"> </font><font size="2" color="#1F497D" face="sans-serif"> </font><font size="2" color="#1F497D" face="Symbol"> </font><font size="2" color="#1F497D" face="sans-serif"> </font><font size="2" color="#1F497D" face="Symbol"> </font><font size="2" color="#1F497D" face="Calibri">platform: vm or baremetal</font><font size="2" color="#1F497D" face="Symbol"><br>
· </font><font size="2" color="#1F497D" face="sans-serif"> </font><font size="2" color="#1F497D" face="Symbol"> </font><font size="2" color="#1F497D" face="sans-serif"> </font><font size="2" color="#1F497D" face="Symbol"> </font><font size="2" color="#1F497D" face="sans-serif"> </font><font size="2" color="#1F497D" face="Symbol"> </font><font size="2" color="#1F497D" face="sans-serif"> </font><font size="2" color="#1F497D" face="Symbol"> </font><font size="2" color="#1F497D" face="Calibri">os: atomic, coreos, …</font><font size="2" color="#1F497D" face="Symbol"><br>
· </font><font size="2" color="#1F497D" face="sans-serif"> </font><font size="2" color="#1F497D" face="Symbol"> </font><font size="2" color="#1F497D" face="sans-serif"> </font><font size="2" color="#1F497D" face="Symbol"> </font><font size="2" color="#1F497D" face="sans-serif"> </font><font size="2" color="#1F497D" face="Symbol"> </font><font size="2" color="#1F497D" face="sans-serif"> </font><font size="2" color="#1F497D" face="Symbol"> </font><font size="2" color="#1F497D" face="Calibri">coe: kubernetes, swarm or mesos</font></ul>
<font size="2" color="#1F497D" face="Calibri"> <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 size="3" face="sans-serif"> </font>
<ul style="padding-left: 36pt"><font size="2" color="#1F497D" face="Symbol">· </font><font size="2" color="#1F497D" face="sans-serif"> </font><font size="2" color="#1F497D" face="Symbol"> </font><font size="2" color="#1F497D" face="sans-serif"> </font><font size="2" color="#1F497D" face="Symbol"> </font><font size="2" color="#1F497D" face="sans-serif"> </font><font size="2" color="#1F497D" face="Symbol"> </font><font size="2" color="#1F497D" face="sans-serif"> </font><font size="2" color="#1F497D" face="Symbol"> </font><font size="2" color="#1F497D" face="Calibri">flavor: baremetal, m1.small, m1.medium, …</font><font size="2" color="#1F497D" face="Symbol"><br>
· </font><font size="2" color="#1F497D" face="sans-serif"> </font><font size="2" color="#1F497D" face="Symbol"> </font><font size="2" color="#1F497D" face="sans-serif"> </font><font size="2" color="#1F497D" face="Symbol"> </font><font size="2" color="#1F497D" face="sans-serif"> </font><font size="2" color="#1F497D" face="Symbol"> </font><font size="2" color="#1F497D" face="sans-serif"> </font><font size="2" color="#1F497D" face="Symbol"> </font><font size="2" color="#1F497D" face="Calibri">os: atomic, coreos, ...</font><font size="2" color="#1F497D" face="Symbol"><br>
· </font><font size="2" color="#1F497D" face="sans-serif"> </font><font size="2" color="#1F497D" face="Symbol"> </font><font size="2" color="#1F497D" face="sans-serif"> </font><font size="2" color="#1F497D" face="Symbol"> </font><font size="2" color="#1F497D" face="sans-serif"> </font><font size="2" color="#1F497D" face="Symbol"> </font><font size="2" color="#1F497D" face="sans-serif"> </font><font size="2" color="#1F497D" face="Symbol"> </font><font size="2" color="#1F497D" face="Calibri">coe: kubernetes, swarm or mesos</font></ul>
<font size="2" color="#1F497D" face="Calibri"> <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 size="2" face="Tahoma"><b><br>
From:</b></font><font size="2" face="Tahoma"> Fox, Kevin M [</font><a href="mailto:Kevin.Fox@pnnl.gov"><font size="2" color="#0000FF" face="Tahoma"><u>mailto:Kevin.Fox@pnnl.gov</u></font></a><font size="2" face="Tahoma">] </font><font size="2" face="Tahoma"><b><br>
Sent:</b></font><font size="2" face="Tahoma"> July-15-15 12:37 PM</font><font size="2" face="Tahoma"><b><br>
To:</b></font><font size="2" face="Tahoma"> OpenStack Development Mailing List (not for usage questions)</font><font size="2" face="Tahoma"><b><br>
Subject:</b></font><font size="2" face="Tahoma"> Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?</font><font size="3" face="Arial"><br>
</font><font size="2" face="Tahoma"><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 width="100%" size="2" align="center"></div><font size="2" face="Tahoma"><b>From:</b></font><font size="2" face="Tahoma"> Daneyon Hansen (danehans) [danehans@cisco.com]</font><font size="2" face="Tahoma"><b><br>
Sent:</b></font><font size="2" face="Tahoma"> Wednesday, July 15, 2015 9:20 AM</font><font size="2" face="Tahoma"><b><br>
To:</b></font><font size="2" face="Tahoma"> OpenStack Development Mailing List (not for usage questions)</font><font size="2" face="Tahoma"><b><br>
Subject:</b></font><font size="2" face="Tahoma"> Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?</font><font size="2" face="Courier"><br>
All,</font><font size="2" face="Times New Roman"><br>
</font><font size="2" face="Courier"><br>
IMO virt_type does not properly describe bare metal deployments. What about using the compute_driver parameter?</font><font size="3" face="Times New Roman"><br>
</font><font size="3" face="Arial"><br>
compute_driver</font><font size="2" face="Times New Roman"> = </font><font size="3" face="Arial">None<br>
</font><font size="3" face="sans-serif"><br>
</font><font size="3" face="Arial"><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 size="3" face="sans-serif"><br>
</font><font size="3" color="#0000FF" face="sans-serif"><u><br>
</u></font><a href="http://docs.openstack.org/kilo/config-reference/content/list-of-compute-config-options.html" target="_blank"><font size="3" color="#0000FF" face="Arial"><u>http://docs.openstack.org/kilo/config-reference/content/list-of-compute-config-options.html</u></font></a><font size="3" color="#0000FF" face="sans-serif"><u><br>
</u></font><a href="http://docs.openstack.org/developer/ironic/deploy/install-guide.html" target="_blank"><font size="3" color="#0000FF" face="Times New Roman"><u>http://docs.openstack.org/developer/ironic/deploy/install-guide.html</u></font></a><font size="2" face="Calibri"><br>
</font><font size="2" face="Calibri"><b><br>
From: </b></font><font size="2" face="Calibri">Adrian Otto <</font><a href="mailto:adrian.otto@rackspace.com" target="_blank"><font size="2" color="#0000FF" face="Calibri"><u>adrian.otto@rackspace.com</u></font></a><font size="2" face="Calibri">></font><font size="2" face="Calibri"><b><br>
Reply-To: </b></font><font size="2" face="Calibri">"OpenStack Development Mailing List (not for usage questions)" <</font><a href="mailto:openstack-dev@lists.openstack.org" target="_blank"><font size="2" color="#0000FF" face="Calibri"><u>openstack-dev@lists.openstack.org</u></font></a><font size="2" face="Calibri">></font><font size="2" face="Calibri"><b><br>
Date: </b></font><font size="2" face="Calibri">Tuesday, July 14, 2015 at 7:44 PM</font><font size="2" face="Calibri"><b><br>
To: </b></font><font size="2" face="Calibri">"OpenStack Development Mailing List (not for usage questions)" <</font><a href="mailto:openstack-dev@lists.openstack.org" target="_blank"><font size="2" color="#0000FF" face="Calibri"><u>openstack-dev@lists.openstack.org</u></font></a><font size="2" face="Calibri">></font><font size="2" face="Calibri"><b><br>
Subject: </b></font><font size="2" face="Calibri">Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?<br>
</font><font size="3" face="sans-serif"> </font>
<ul style="padding-left: 36pt"><font size="2" face="Calibri">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 size="2" color="#0000FF" face="Calibri"><u>hongbin.lu@huawei.com</u></font></a><font size="2" face="Calibri">> <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 size="2" color="#0000FF" face="Calibri"><u>openstack-dev@lists.openstack.org</u></font></a><font size="2" face="Calibri">> <br>
Subject: Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type? </font><font size="2" color="#1F497D" face="Calibri"><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 size="2" color="#0000FF" face="Calibri"><u>https://blueprints.launchpad.net/nova/+spec/flavor-instance-type-dedup</u></font></a><font size="2" color="#1F497D" face="Calibri"><br>
<br>
Best regards,<br>
Hongbin<br>
</font><font size="2" face="Tahoma"><b><br>
From:</b></font><font size="2" face="Tahoma"> Kai Qiang Wu [</font><a href="mailto:wkqwu@cn.ibm.com" target="_blank"><font size="2" color="#0000FF" face="Tahoma"><u>mailto:wkqwu@cn.ibm.com</u></font></a><font size="2" face="Tahoma">] </font><font size="2" face="Tahoma"><b><br>
Sent:</b></font><font size="2" face="Tahoma"> July-14-15 9:35 PM</font><font size="2" face="Tahoma"><b><br>
To:</b></font><font size="2" face="Tahoma"> </font><a href="mailto:openstack-dev@lists.openstack.org" target="_blank"><font size="2" color="#0000FF" face="Tahoma"><u>openstack-dev@lists.openstack.org</u></font></a><font size="2" face="Tahoma"><b><br>
Subject:</b></font><font size="2" face="Tahoma"> [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?</font><font size="3" face="Arial"><br>
</font><font size="2" face="Arial"><br>
Hi Magnum Guys,</font><font size="3" face="Arial"><br>
</font><font size="2" face="Arial"><br>
<br>
I want to raise this question through ML.</font><font size="3" face="Arial"><br>
</font><font size="2" face="Arial"><br>
<br>
In this patch </font><a href="https://review.openstack.org/#/c/200401/" target="_blank"><font size="2" color="#0000FF" face="Arial"><u>https://review.openstack.org/#/c/200401/</u></font></a><font size="3" face="Arial"><br>
</font><font size="2" face="Arial"><br>
<br>
For some old history reason, we use </font><font size="2" face="Arial"><b>platform </b></font><font size="2" face="Arial">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 size="3" face="Arial"><br>
</font><font size="2" face="Arial"><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 size="3" face="Arial"><br>
</font><font size="2" face="Arial"><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 size="3" face="Arial"><br>
</font><font size="2" face="Arial"><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 size="3" face="Arial"><br>
</font><font size="2" face="Arial"><br>
<br>
Please help to vote for that name. </font><font size="3" face="Arial"><br>
</font><font size="2" face="Arial"><br>
<br>
Thanks</font><font size="3" face="Arial"><br>
<br>
<br>
</font><font size="2" face="Arial"><br>
<br>
Best Wishes,<br>
--------------------------------------------------------------------------------<br>
Kai Qiang Wu (</font><font size="2" face="sans-serif">吴开强</font><font size="2" face="Arial"> Kennan</font><font size="2" face="sans-serif">）</font><font size="2" face="Arial"><br>
IBM China System and Technology Lab, Beijing<br>
<br>
E-mail: </font><a href="mailto:wkqwu@cn.ibm.com" target="_blank"><font size="2" color="#0000FF" face="Arial"><u>wkqwu@cn.ibm.com</u></font></a><font size="2" face="Arial"><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 size="2" face="sans-serif">__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: </font><a href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"><font size="2" color="#0000FF" face="sans-serif"><u>OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</u></font></a><font size="2" color="#0000FF" face="sans-serif"><u><br>
</u></font><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><font size="2" color="#0000FF" face="sans-serif"><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></a><tt><font size="2">__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>
</font></tt><tt><font size="2"><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></font></tt><tt><font size="2"><br>
</font></tt><br>
</ul>
</body></html>