Hi,
I also think that this should also be on the openstack development list.
There are certainly developers and users who can certainly help contribute
Thanks
Gary
On 11/25/2012 01:48 PM, Gary Kotton wrote:
Hi,
I have been over the design and have added in some comments. I have a
number of concerns regarding the proposed implementation. For the l3
agent I have yet to understand why we are not looking into VRRP for a
solution for high availability. I am not sure if any of you are aware
of how VRRP works but it is good to understand. This means that the
l3-agents can all have the same configurations and if one fails then
another will take over. The other problem with the l3-agents is if the
load from the VM's exceeds the capabilities of the l3 agents. I do not
see how the proposed solution deals with this. It may mean different
routes. I think that this may complicate things further for users. One
thing that can be done on the agents is to manipulate the destination
MAC address of the traffic leaving the agents. This will ensure that
it will arrive at the designated L3 agent which in turn will be able
to provide the relevant floating IP support. With OVS this solution is
prety simple as it is just building the relevant flow entries. With
linux bridge it may require ip table rules (I have yet to understand
how one can update a destination MAC address but I guess that this is
possible). The "load balancing" of the destination traffic should be
done locally on each agent - they will know if the l3 agents are up
and done by checking with arp/icmp requests. (Just and idea).
I have yet to understand how you are going to be treating the failure
of a host and how the l3 information and dhcp information will be
moved from one to another.
Thanks
Gary
On 11/23/2012 02:56 PM, Salvatore Orlando wrote:
Hi Yong,
I did a review of the specification documents.
I left comments in the google doc.
Salvatore
On 21 November 2012 13:24, Salvatore Orlando <[email protected]
<mailto:[email protected]>> wrote:
Thanks Yong,
I will review this specification at some point between today and
tomorrow.
Salvatore
On 21 November 2012 13:20, gong yong sheng
<[email protected] <mailto:[email protected]>>
wrote:
Hi Nachi and other members,
I have drafted a version about quantum scheduler for BP
https://blueprints.launchpad.net/quantum/+spec/quantum-scheduler
the Google doc is at:
https://docs.google.com/document/d/1TJlW0_tMpeENA_ia38fvRu7ioKRt9fsWXBjivwd1mMw/edit
Thanks
Yong Sheng Gong
--
Mailing list: https://launchpad.net/~quantum-core
<https://launchpad.net/%7Equantum-core>
Post to : [email protected]
<mailto:[email protected]>
Unsubscribe : https://launchpad.net/~quantum-core
<https://launchpad.net/%7Equantum-core>
More help : https://help.launchpad.net/ListHelp
--
Mailing list: https://launchpad.net/~quantum-core
Post to : [email protected]
Unsubscribe : https://launchpad.net/~quantum-core
More help : https://help.launchpad.net/ListHelp
