[openstack-dev] Nova PTL Candidacy
Ahn Jaesuk
bluejay.ahn at gmail.com
Wed Mar 13 07:11:46 UTC 2013
I will be happy to talk with you regarding this feature at any time. :)
--
Jaesuk Ahn, Ph.D.
Team Leader | Cloud OS Dev. Team
Cloud Infrastructure Department
KT (Korea Telecom)
T. +82-10-9888-0328 | F. +82-303-0993-5340
Active member on OpenStack Korea Community
Mar 12, 2013, 4:08 PM, gong yong sheng <gongysh at linux.vnet.ibm.com> 작성:
> I think I will keep working on this multi-host feature basing on quantum scheduler.
> when it is going on, I need hear voices from you guys who are interested in multi-host feature.
>
> On 03/12/2013 01:21 PM, Ahn Jaesuk wrote:
>>
>> Mar 12, 2013, 12:55 PM, Nathanael Burton <nathanael.i.burton at gmail.com> 작성:
>>
>>> On Mar 11, 2013 1:27 PM, "Russell Bryant" <rbryant at redhat.com> wrote:
>>> >
>>> > It was in the "Nova Parity in Grizzly" list, though.
>>> >
>>> > From some other threads, it sounds like it was implemented in:
>>> >
>>> > https://blueprints.launchpad.net/quantum/+spec/quantum-scheduler
>>> >
>>>
>>> Was that completely implemented? This review was abandoned, https://review.openstack.org/18216
>>>
>>>
>>
>> Yes, I found the same thing. (Please correct me if I am wrong here.)
>>
>> This was an original patch for the quantum-scheduler, which is abandoned.
>> -> https://review.openstack.org/#/c/18216/
>> One of the objectives was "Router to l3 agent is a many to many relationship."
>> One more important one was "One L3 agent hosting a router plays default role, other L3 agents hosting the same router are in colocated mode."
>>
>> These are merged patches for the quantum-scheduler.
>> -> https://review.openstack.org/#/c/21049/
>> -> https://review.openstack.org/#/c/21069/
>> -> https://review.openstack.org/#/c/21175/
>> Some objectives has been changed from the original one to "Router to l3 agent is a many to one relationship"
>>
>> In my understanding, with these changes in new quantum-scheduler, it is impossible to simulate nova-network's multi-host mode with quantum.
>> In other words, https://blueprints.launchpad.net/quantum/+spec/quantum-multihost is still not fully implemented yet.
>>
>> I would like to know if this "multi-host mode in quantum" is being postponed or being abandoned.
>>
>>
>>> > and if that's the case, should this blueprint be closed to avoid confusion?
>>> >
>>> > https://blueprints.launchpad.net/quantum/+spec/quantum-multihost
>>>
>>> I agree.
>>>
>>> > Also, are there any docs on this new stuff?
>>> >
>>> > --
>>> > Russell Bryant
>>> >
>>> > _______________________________________________
>>> > OpenStack-dev mailing list
>>> > OpenStack-dev at lists.openstack.org
>>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>> _______________________________________________
>>> OpenStack-dev mailing list
>>> OpenStack-dev at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>> Cheers,
>>
>>
>>
>> --
>> Jaesuk Ahn, Ph.D.
>> Team Leader | Cloud OS Dev. Team
>> Cloud Infrastructure Department
>> KT (Korea Telecom)
>> T. +82-10-9888-0328 | F. +82-303-0993-5340
>> Active member on OpenStack Korea Community
>>
>>
>>
>>
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130313/a1f61407/attachment.html>
More information about the OpenStack-dev
mailing list