Open Stack

Yes you are right. The statuses call is correctly changing the operating
status to DISABLED, but not showing operating status as DISABLED when doing
POST/PUT/GET on loadbalancer upon specifying admin_state_up as 'False'
explicitly. Thanks for confirming though.

Madhu

On Tue, Apr 28, 2015 at 6:59 PM, Brandon Logan <brandon.logan at rackspace.com>
wrote:

>  ​So that is the right URL for the statuses call.  As I understand the
> issue the statuses call is correctly changing the operating status to
> DISABLED correct?
>
>
>  The problem is when you do an operationg on a loadbalancer and
> admin_state_up = False.  In that case the body returned for those
> operationgs (POST, PUT, GET) should show operating status as DISABLED, and
> it is not.  This is a bug, and I believe it would be quite simple to fix.
> You won't need to call the statuses method as that is just the method that
> is called when the /statuses resource is called.  The create_loadbalancer,
> get_loadbalancer, get_loadbalancers, and update_loadbalancer methods will
> just need to change the operating_status to DISABLED if admin_state_up is
> False.  Should be a very simple change actually.
>
>
>  Let me know if I am articulating the problem correctly.
>
>
>  Thanks,
>
> Brandon
>  ------------------------------
> *From:* Madhusudhan Kandadai <madhusudhan.openstack at gmail.com>
> *Sent:* Tuesday, April 28, 2015 3:23 PM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] Neutron Lbaas v2 not showing
> operating_status as inactive
>
>    Hi Anand,
>
>  There is an api which calls 'statuses' method.. I could see the status
> 'DISABLED' in: GET /lbaas/loadbalancers/loadbalancer_id/statuses.
>
> Maybe we need to correct the doc to reflect the right URL to avoid
> confusion. If that is the right API call, I shall update the bug and mark
> it as fixed.
>
>  Regards,
>  Madhu
>
>
>
> On Tue, Apr 28, 2015 at 12:28 PM, Anand shanmugam <anand1712 at outlook.com>
> wrote:
>
>>  Hi ,
>>
>>  I am working on the bug https://bugs.launchpad.net/neutron/+bug/1449286
>>
>>  In this bug the admin_state_up is made to false when creating a lbaas
>> v2 loadbalancer.The operating_state should become DISABLED for the created
>> loadbalancer but it is showing as online.
>>
>>  I can see that there is a method "statuses" which takes care of
>> disabling the opensrting_status (
>> https://github.com/openstack/neutron-lbaas/blob/master/neutron_lbaas/services/loadbalancer/plugin.py#L971)
>> but I cannot find the method which will call this 'satuses' method.
>>
>>  I feel this statuses method is not called at all when creating or
>> updating a loadbalancer.Could someone please help me if there is any other
>> api to call this method?
>>
>>  Regards,
>> Anand S
>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> 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/20150428/ab3a7f06/attachment.html>