Hi folks
> Gary
Thank you for your comment. I wanna discuss your point on the mailing list.
Yusuke pushed Multi-host implementation for review.
https://review.openstack.org/#/c/10766/2
This patch changes only quantum-dhcp-agent side.
Gary's point is we should have host attribute on the port for scheduling.
I agree with Gary.
In the nova, vm has available_zone for scheduling.
So Instead of using host properties.
How about use available_zone for port?
Format of availability_zone is something like this
available_zone="zone_name:host".
We can also add availability_zone attribute for the network as a
default value of port.
We can write this until next Monday.
However I'm not sure quantum community will accept this or not, so I'm
asking here.
If there are no objections, we will push zone version for review.
Thanks
Nachi
--
Mailing list: https://launchpad.net/~netstack
Post to : netstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~netstack
More help : https://help.launchpad.net/ListHelp
> Gary
Thank you for your comment. I wanna discuss your point on the mailing list.
Yusuke pushed Multi-host implementation for review.
https://review.openstack.org/#/c/10766/2
This patch changes only quantum-dhcp-agent side.
Gary's point is we should have host attribute on the port for scheduling.
I agree with Gary.
In the nova, vm has available_zone for scheduling.
So Instead of using host properties.
How about use available_zone for port?
Format of availability_zone is something like this
available_zone="zone_name:host".
We can also add availability_zone attribute for the network as a
default value of port.
We can write this until next Monday.
However I'm not sure quantum community will accept this or not, so I'm
asking here.
If there are no objections, we will push zone version for review.
Thanks
Nachi
--
Mailing list: https://launchpad.net/~netstack
Post to : netstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~netstack
More help : https://help.launchpad.net/ListHelp