<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hi Salvatore, Pandora is our open source admin UI for openstack <a href="https://code.google.com/p/c2-pandora/" target="_blank">https://code.google.com/p/c2-pandora/</a><br><br><div><div dir="ltr"><div><br></div><br><div class="ecxgmail_extra"><div class="ecxgmail_quote">On 22 June 2013 12:23, Peter Cheung <span dir="ltr"><<a href="mailto:mcheung63@hotmail.com" target="_blank">mcheung63@hotmail.com</a>></span> wrote:<br>
<blockquote class="ecxgmail_quote" style="border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex;">
<div><div dir="ltr"><div>Thanks <span style="font-size:12pt;">Salvatore</span></div>I am thinking these:<div>1) openvswitch has more features than quantum, so i want to support it in pandora first, then later to support quantum</div>
</div></div></blockquote><div><br></div><div>I think this statement is a bit incorrect, or at least deserves clarification.</div><div>Open vSwitch is a multi-layer virtual switch, whereas Quantum is a management tool for cloud networks.</div>
<div>I don't know then what you mean by stating Open vSwitch has more features than Quantum; there are surely features of Open vSwitch which are not leveraged by Quantum - perhaps are you referring to this?</div><div><br></div><div>>> We are making the network management UI, we are thinking we should control the openvswitch directly, or control the quantum. In openvswitch, there are some features needed by our commercial users, such as Qos, netflow monitoring, vlan and vlan tag. I am not sure the quantum API can address these things.</div>
<div> </div><blockquote class="ecxgmail_quote" style="border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex;"><div><div dir="ltr"><div>2) openvswitch seems doesn't provide API, still don't know how to control it programatically. May be i send command in command-pipeline then parse the output. But this is not a good practice.</div>
</div></div></blockquote><div><br></div><div>Openvswitch exposes interfaces for managing the switch layout and switch forwarding. They're the OVSDB [1,2] and Openflow interfaces. On <a href="http://openvswitch.org" target="_blank">openvswitch.org</a> there's plenty of information about how to use them.</div>
<div>Again, if you're looking at API like 'create_network' or 'create_subnet' on Openvswitch you are probably not looking in the right place; in this case you might look at a controller or a management system.</div><div><br></div><div>>> thanks :D</div>
<div> </div><div> </div><blockquote class="ecxgmail_quote" style="border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex;"><div><div dir="ltr"><div>3) i want to do live-migration with auto network transfer in pandora. So i need to control a vswitch.<br>
</div></div></div></blockquote><div><br></div><div>It seems then you need to develop your own control plane. Frankly I have not idea of what you mean by "auto network transfer".</div><div>I assume you've already looked at Floodlight, Open Daylight, and perhaps even at the Quantum's OVS/ML2 plugins (which implement a control plane too), and you're positive that they cannot satisfy your requirements, so you need to write something new?</div>
<div><br></div><div>[1] <a href="http://networkheresy.com/tag/ovsdb/" target="_blank">http://networkheresy.com/tag/ovsdb/</a></div><div>[2] <a href="http://tools.ietf.org/html/draft-pfaff-ovsdb-proto-02" target="_blank">http://tools.ietf.org/html/draft-pfaff-ovsdb-proto-02</a></div><div><br></div><div>>> no, we are not going to develop a new virtual switch, we don't have enough man power and don't want to reinvent the wheel. We just want to embed a network control in Pandora, so people can use it to admin their network, same way as they use ESX server. In a basic VM environment, i think people need these thing:</div><div>1) QOS control</div><div>2) VLan</div><div>3) netflow monitoring</div><div>4) link up mulitple vswitch to form a bigger network</div><div><br></div><div>Really not sure the quantum API can do that or not.</div><div><br></div><div>Thanks for you reply, Peter !!!</div>
<div><br></div><blockquote class="ecxgmail_quote" style="border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex;"><div><div dir="ltr"><div><br>Thanks<div>
from Peter</div><br><div><br></div><div><div><hr>Date: Sat, 22 Jun 2013 11:14:38 +0100<br>Subject: Re: [Openstack] openvswitch instead of quantum<br>From: <a href="mailto:sorlando@nicira.com" target="_blank">sorlando@nicira.com</a><br>
To: <a href="mailto:mcheung63@hotmail.com" target="_blank">mcheung63@hotmail.com</a><br>CC: <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a></div><div><div class="h5"><br><br>
<div dir="ltr">Yes, it is a very common use case.<div>Nowadays, everybody who deploys Xen, KVM, or LXC without a Cloud Management System is actually using Open vSwitch.</div><div>In that case you can program Open vSwitch using its own interface to provide virtual networks.</div>
<div><br></div><div>When deploying Openstack, you can use Open vSwitch without Quantum by deploying nova-network instead.</div><div>As far as I know every nova-network manager works with Open vSwitch too.</div>
<div><br></div><div>Salvatore</div></div><div><br><br><div>On 22 June 2013 09:14, Peter Cheung <span dir="ltr"><<a href="mailto:mcheung63@hotmail.com" target="_blank">mcheung63@hotmail.com</a>></span> wrote:<br>
<blockquote style="border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex;">
<div><div dir="ltr">Hi<div> Any people is using open vswitch directly, instead of sing quantum?</div><div>Is it a common practice?<br><br>Thanks<div>from Peter</div></div> </div></div>
<br>_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
<br></blockquote></div><br></div></div></div></div></div> </div></div>
</blockquote></div><br></div></div></div> </div></body>
</html>