<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
On 08/01/2012 06:34 PM, Fabian Deutsch wrote:
<blockquote
cite="mid:1343835248.2211.26.camel@fdeutsch-laptop.local"
type="cite">
<pre wrap="">Am Mittwoch, den 01.08.2012, 09:56 -0400 schrieb Andrew Cathrow:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">From: "Mark Wu" <a class="moz-txt-link-rfc2396E" href="mailto:wudxw@linux.vnet.ibm.com"><wudxw@linux.vnet.ibm.com></a>
Sent: Wednesday, August 1, 2012 8:59:14 AM
Subject: Host network management roadmap inquiry
</pre>
</blockquote>
</blockquote>
<pre wrap="">
<snip/>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">quantum
</pre>
</blockquote>
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">Both the plugins openvswitch and linuxbridge stores abstract network
entities (network, port) in database and create bridge/vlan via the
tool ip/brctl or ovs-vsctl on demand. Only one bridge is created on
one server and one vlan is created for each virtual network. That
means that only one nic can be configured for vm network. It doesn't
configure nic or bond even if openvswitch also supports bond. Both
of traditional network stack configuration and quantum will be
supported oVirt for different purpose, right?
</pre>
</blockquote>
</blockquote>
</blockquote>
<br>
More than one virtual NIC can be assigned to a VM. The Quantum
agents are tune to assign the virtual NIC to the correct network.
The NIC bonding is something that is not addressed by Quantum. Each
agent hsa its own configuration file that indicates the physical
network connectivity. <br>
<blockquote
cite="mid:1343835248.2211.26.camel@fdeutsch-laptop.local"
type="cite">
<blockquote type="cite">
<pre wrap="">
good place to start :
<a class="moz-txt-link-freetext" href="https://fedoraproject.org/wiki/Quantum_and_oVirt">https://fedoraproject.org/wiki/Quantum_and_oVirt</a>
</pre>
</blockquote>
<pre wrap="">
Hey,
besides these Quantum specific informations I'd also like to discuss
where oVirt is going wrt to networking.
Quantum is sure a nice solution for a project wide solution, but how can
or should this be integrated into the underlying components like vdsm or
node?
</pre>
</blockquote>
<br>
If Quantum was integrated into oVirt then oVirt would receive all of
the support from Quantum. For example in Folsom there has been a lot
of activity in Quantum to provide address management. In the wiki it
is written that forman supports tis. I am not exactly sure in what
context. In Folsom-3 of Quantum one or more IP addresses can be
assigned in a network (from a predefined subnet). A DHCP agent
ensures that the VM's will receive the assigned IP address. <br>
<br>
<blockquote
cite="mid:1343835248.2211.26.camel@fdeutsch-laptop.local"
type="cite">
<pre wrap="">From a Node pov (feature as well as implementation wise) it is quite
interesting if we should switch to openvswitch (which can then in turn
used by quantum [via vdsm?]) or keep the linux bridge stuff.
There are also efforts on it's way (like teaming, the F17 feature) which
we should keep an eye on, as this seems to land in network manager as an
alternative(?) to the default bonding. It's also interesting how this
performs with openvswitch.
Many changes on many sides and we should lay out the path a bit to find
a direction where to go.
There is already
<a class="moz-txt-link-freetext" href="http://wiki.ovirt.org/wiki/Networking">http://wiki.ovirt.org/wiki/Networking</a>
</pre>
</blockquote>
<br>
Can you please clarify what you mean by network permissions. Quantum
has permissions for the management of networks.<br>
<blockquote
cite="mid:1343835248.2211.26.camel@fdeutsch-laptop.local"
type="cite">
<pre wrap="">
</pre>
</blockquote>
<br>
<blockquote
cite="mid:1343835248.2211.26.camel@fdeutsch-laptop.local"
type="cite">
<pre wrap="">
which we could use to summarize the needed features, potential
techniques and an over all plan.
Greetings
fabian
</pre>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Arch mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Arch@ovirt.org">Arch@ovirt.org</a>
<a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/arch">http://lists.ovirt.org/mailman/listinfo/arch</a>
</pre>
</blockquote>
<br>
</body>
</html>