Re: [openstack-dev] [Neutron] LeastNetwork scheduling for DHCP

2014-11-14 Thread GRASSART Benjamin
Hi all, I would definitely be glad to work on the subject as well. However I am not sure to understand fully Armando last remark in our change. I will try to discuss it with him on IRC. Regards, Benjamin GRASSART [@@ THALES GROUP INTERNAL @@] De : S M, Praveen Kumar

Re: [openstack-dev] [Neutron] LeastNetwork scheduling for DHCP

2014-11-14 Thread Armando M.
Benjamin, Feel free to reach out. If you are referring to my -2, that was just provisional. Before we can go ahead and see an improved scheduling capability for DHCP, you guys need to resolve the conflict between the overlapping blueprints, working together or giving up one in favor on the

Re: [openstack-dev] [Neutron] LeastNetwork scheduling for DHCP

2014-11-07 Thread S M, Praveen Kumar
Hi Vivek, We are definitely interested in working on these blueprints collaboratively. We have a working implementation for our blueprint and received few important comments from Armando and addressing them currently. Regards Praveen. From: Narasimhan, Vivekanandan Sent: Thursday, November

Re: [openstack-dev] [Neutron] LeastNetwork scheduling for DHCP

2014-11-06 Thread IWAMOTO Toshihiro
At Thu, 6 Nov 2014 15:39:25 +, Narasimhan, Vivekanandan wrote: Hi Neutron Stackers, There is an interest among vendors to bring Least Networks scheduling for DHCP into Openstack Neutron. Currently there are the following blueprints lying there, all of them trying to

Re: [openstack-dev] [Neutron] LeastNetwork scheduling for DHCP

2014-11-06 Thread ZZelle
Hi, iiuc, It seems [1][3] share exactly the same objective and implementation intention: - define an common abstract dhcp scheduler class - define a dhcp LeastNetworkScheduler [2] proposes to - define a dhcp LeastVmScheduler (networks are scheduled on the dhcp agent supporting the least vms

Re: [openstack-dev] [Neutron] LeastNetwork scheduling for DHCP

2014-11-06 Thread Itsuro ODA
+1 IMHO, it is enough for [1][3] to fix by issuing a bug report. Thanks Itsuro Oda On Thu, 6 Nov 2014 17:20:57 +0100 ZZelle zze...@gmail.com wrote: Hi, iiuc, It seems [1][3] share exactly the same objective and implementation intention: - define an common abstract dhcp scheduler