Re: [openstack-dev] [neutron][stable] metadata agent performance

2014-10-22 Thread Jakub Libosvar
On 10/22/2014 02:26 AM, Maru Newby wrote: We merged caching support for the metadata agent in juno, and backported to icehouse. It was enabled by default in juno, but disabled by default in icehouse to satisfy the stable maint requirement of not changing functional behavior. While

Re: [openstack-dev] [neutron][stable] metadata agent performance

2014-10-22 Thread Ihar Hrachyshka
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 22/10/14 02:26, Maru Newby wrote: We merged caching support for the metadata agent in juno, and backported to icehouse. It was enabled by default in juno, but disabled by default in icehouse to satisfy the stable maint requirement of not

Re: [openstack-dev] [neutron][stable] metadata agent performance

2014-10-22 Thread Akihiro Motoki
My understanding is same as from Ihar, and we no longer have the degradation in the latest Icehouse update. There was a degradation in 2014.1.2 [2] but the fix was backported in 2014.1.3 [1]. We don't need to take care of backporting when considering metadata RPC patch. [1]

Re: [openstack-dev] [neutron][stable] metadata agent performance

2014-10-22 Thread Maru Newby
On Oct 22, 2014, at 12:53 AM, Jakub Libosvar libos...@redhat.com wrote: On 10/22/2014 02:26 AM, Maru Newby wrote: We merged caching support for the metadata agent in juno, and backported to icehouse. It was enabled by default in juno, but disabled by default in icehouse to satisfy the

[openstack-dev] [neutron][stable] metadata agent performance

2014-10-21 Thread Maru Newby
We merged caching support for the metadata agent in juno, and backported to icehouse. It was enabled by default in juno, but disabled by default in icehouse to satisfy the stable maint requirement of not changing functional behavior. While performance of the agent was improved with caching

Re: [openstack-dev] [neutron][stable] metadata agent performance

2014-10-21 Thread Armando M.
It sounds like the only reasonable option we are left with right now is to document. Even if we enabled/removed the backport, it would take time until users can get their hands on a new cut of the stable branch. We would need to be more diligent in the future and limit backports to just bug