Re: [Openstack] [openstack][nova] Changes-Since parameter in Nova API not working as expected

[Jay Pipes]

Awesome, thanks Jose!

On 06/26/2017 11:12 PM, Jose Renato Santos wrote:

Jay

I created a bug report as you suggested:
https://bugs.launchpad.net/nova/+bug/1700684

Thanks for your help
Best
Renato

-Original Message-
From: Jay Pipes [mailto:jaypi...@gmail.com]
Sent: Monday, June 26, 2017 2:32 PM
To: Jose Renato Santos ; 
openstack@lists.openstack.org
Subject: Re: [Openstack] [openstack][nova] Changes-Since parameter in Nova API 
not working as expected

On 06/26/2017 02:27 PM, Jose Renato Santos wrote:

Jay,
Thanks for your response

Let me clarify my point.
I am not expecting to see a change in the updated_at column of a server when 
the rules of its security group changes.
I agree that would be a change to be handled by the Neutron Api, and
would be too much to ask for Nova to keep track of that But I would expect to 
see a change in updated_at column of a server instance when I 
associated(attach) a new security group to that server.
For me that is a change in the server and not on the security group.
The security group was not changed, but the server was, as it is now associated 
with a different set of security groups I hope that clarifies my question.


I think that's a pretty reasonable request actually. Care to create a bug on 
Launchpad for it?

Best,
-jay



___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [openstack][nova] Changes-Since parameter in Nova API not working as expected

[Jose Renato Santos]

Jay

I created a bug report as you suggested:
https://bugs.launchpad.net/nova/+bug/1700684

Thanks for your help
Best
Renato

-Original Message-
From: Jay Pipes [mailto:jaypi...@gmail.com] 
Sent: Monday, June 26, 2017 2:32 PM
To: Jose Renato Santos ; 
openstack@lists.openstack.org
Subject: Re: [Openstack] [openstack][nova] Changes-Since parameter in Nova API 
not working as expected

On 06/26/2017 02:27 PM, Jose Renato Santos wrote:
> Jay,
> Thanks for your response
> 
> Let me clarify my point.
> I am not expecting to see a change in the updated_at column of a server when 
> the rules of its security group changes.
> I agree that would be a change to be handled by the Neutron Api, and 
> would be too much to ask for Nova to keep track of that But I would expect to 
> see a change in updated_at column of a server instance when I 
> associated(attach) a new security group to that server.
> For me that is a change in the server and not on the security group. 
> The security group was not changed, but the server was, as it is now 
> associated with a different set of security groups I hope that clarifies my 
> question.

I think that's a pretty reasonable request actually. Care to create a bug on 
Launchpad for it?

Best,
-jay


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [openstack][nova] Changes-Since parameter in Nova API not working as expected

[Kevin Benton]

Keep in mind that security groups are still a property of the port, so you
have to decide what to do when a server has two ports in the same security
group and one of the ports is removed from that group. In that scenario the
security groups of the instance haven't changed even though one of the
ports was removed. Do you adjust the updated_at timestamp then?

On Mon, Jun 26, 2017 at 12:32 PM, Jay Pipes  wrote:

> On 06/26/2017 02:27 PM, Jose Renato Santos wrote:
>
>> Jay,
>> Thanks for your response
>>
>> Let me clarify my point.
>> I am not expecting to see a change in the updated_at column of a server
>> when the rules of its security group changes.
>> I agree that would be a change to be handled by the Neutron Api, and
>> would be too much to ask for Nova to keep track of that
>> But I would expect to see a change in updated_at column of a server
>> instance when I associated(attach) a new security group to that server.
>> For me that is a change in the server and not on the security group. The
>> security group was not changed, but the server was, as it is now associated
>> with a different set of security groups
>> I hope that clarifies my question.
>>
>
> I think that's a pretty reasonable request actually. Care to create a bug
> on Launchpad for it?
>
>
> Best,
> -jay
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac
> k
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac
> k
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [openstack][nova] Changes-Since parameter in Nova API not working as expected

[Jay Pipes]

On 06/26/2017 02:27 PM, Jose Renato Santos wrote:

Jay,
Thanks for your response

Let me clarify my point.
I am not expecting to see a change in the updated_at column of a server when 
the rules of its security group changes.
I agree that would be a change to be handled by the Neutron Api, and would be 
too much to ask for Nova to keep track of that
But I would expect to see a change in updated_at column of a server instance 
when I associated(attach) a new security group to that server.
For me that is a change in the server and not on the security group. The 
security group was not changed, but the server was, as it is now associated 
with a different set of security groups
I hope that clarifies my question.


I think that's a pretty reasonable request actually. Care to create a 
bug on Launchpad for it?


Best,
-jay

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [openstack][nova] Changes-Since parameter in Nova API not working as expected

[Jose Renato Santos]

Jay,
Thanks for your response

Let me clarify my point.
I am not expecting to see a change in the updated_at column of a server when 
the rules of its security group changes.
I agree that would be a change to be handled by the Neutron Api, and would be 
too much to ask for Nova to keep track of that
But I would expect to see a change in updated_at column of a server instance 
when I associated(attach) a new security group to that server.
For me that is a change in the server and not on the security group. The 
security group was not changed, but the server was, as it is now associated 
with a different set of security groups
I hope that clarifies my question.

Thanks
Renato


-Original Message-
From: Jay Pipes [mailto:jaypi...@gmail.com] 
Sent: Monday, June 26, 2017 12:25 PM
To: openstack@lists.openstack.org
Subject: Re: [Openstack] [openstack][nova] Changes-Since parameter in Nova API 
not working as expected

On 06/26/2017 12:58 PM, Jose Renato Santos wrote:
> Hi
> 
> I am accessing the nova api using the gophercloud SDK 
> https://github.com/rackspace/gophercloud
> 
> I am running Openstack Newton installed with Openstack Ansible
> 
> I am accessing the “List Servers” call of the nova Api with the 
> Changes-Since parameters for efficient polling
> 
> https://developer.openstack.org/api-guide/compute/polling_changes-sinc
> e_parameter.html
> 
> However, the API is not working as I expected.
> 
> When I stop or start a server instance, the API successfully detects 
> the change in the server state and returns the server in the next call 
> to ListServers with the Changes-Since parameter, as expected.
> 
> But when I attach a new security group to the server, the API does not 
> detect any change in the state of the server and does not return the 
> server in the next call  to ListServers with the Changes-Since parameter.
> 
> I would expect that changing the list of security groups attached to a 
> server would be considered a change in the server state and reported 
> when using the Changes-Since parameter, but that is not the behavior 
> that I am seeing.
> 
> Can someone please let me know if this is a known bug?

Changes to an instance's security group rules are not considered when listing 
servers by updated_at field value. This is mostly because the security group 
[rules] are Neutron objects and are not one-to-one associated with a Nova 
instance.

I'm not sure it's a bug per-se, but I suppose we could entertain a feature 
request to set the updated_at timestamp column for all instances associated 
with a security group when that security group's rules are changed.

But that would probably open up a can of worms that Nova developers may not be 
willing to deal with. For instance, should we update the instances.update_at 
table every time a volume is changed? a network port that an instance is 
associated with? A heat stack that launched the volume? etc etc.

Best,
-jay

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [openstack][nova] Changes-Since parameter in Nova API not working as expected

[Jay Pipes]

On 06/26/2017 12:58 PM, Jose Renato Santos wrote:

Hi

I am accessing the nova api using the gophercloud SDK 
https://github.com/rackspace/gophercloud


I am running Openstack Newton installed with Openstack Ansible

I am accessing the “List Servers” call of the nova Api with the 
Changes-Since parameters for efficient polling


https://developer.openstack.org/api-guide/compute/polling_changes-since_parameter.html

However, the API is not working as I expected.

When I stop or start a server instance, the API successfully detects the 
change in the server state and returns the server in the next call to 
ListServers with the Changes-Since parameter, as expected.


But when I attach a new security group to the server, the API does not 
detect any change in the state of the server and does not return the 
server in the next call  to ListServers with the Changes-Since parameter.


I would expect that changing the list of security groups attached to a 
server would be considered a change in the server state and reported 
when using the Changes-Since parameter, but that is not the behavior 
that I am seeing.


Can someone please let me know if this is a known bug?


Changes to an instance's security group rules are not considered when 
listing servers by updated_at field value. This is mostly because the 
security group [rules] are Neutron objects and are not one-to-one 
associated with a Nova instance.


I'm not sure it's a bug per-se, but I suppose we could entertain a 
feature request to set the updated_at timestamp column for all instances 
associated with a security group when that security group's rules are 
changed.


But that would probably open up a can of worms that Nova developers may 
not be willing to deal with. For instance, should we update the 
instances.update_at table every time a volume is changed? a network port 
that an instance is associated with? A heat stack that launched the 
volume? etc etc.


Best,
-jay

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [openstack][nova] Changes-Since parameter in Nova API not working as expected

[Jose Renato Santos]

Hi

 

I am accessing the nova api using the gophercloud SDK

https://github.com/rackspace/gophercloud

I am running Openstack Newton installed with Openstack Ansible

 

I am accessing the "List Servers" call of the nova Api with the
Changes-Since parameters for efficient polling 

 

https://developer.openstack.org/api-guide/compute/polling_changes-since_para
meter.html

 

However, the API is not working as I expected.

When I stop or start a server instance, the API successfully detects the
change in the server state and returns the server in the next call to
ListServers with the Changes-Since parameter, as expected.

But when I attach a new security group to the server, the API does not
detect any change in the state of the server and does not return the server
in the next call  to ListServers with the Changes-Since parameter.

I would expect that changing the list of security groups attached to a
server would be considered a change in the server state and reported when
using the Changes-Since parameter, but that is not the behavior that I am
seeing.

 

Can someone please let me know if this is a known bug?


Thanks

Renato

 

 

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack