Re: [openstack-dev] [Neutron] how to deprecate a plugin

> On Wed, Jul 30, 2014 at 12:17 PM, YAMAMOTO Takashi > wrote: >> hi, >> >> what's the right procedure to deprecate a plugin? we (ryu team) are >> considering deprecating ryu plugin, in favor of ofagent. probably in >> K-timeframe, if it's acceptable. >> > The typical way is to announce the depre

[openstack-dev] [Neutron][policy] Group-based Policy weekly meeting invite and agenda

Greetings! This is a reminder for the weekly IRC Sub-team meeting occurring on Thursdays at 1800 UTC on #openstack-meeting-3 [1]. Tomorrow's agenda is posted here: https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy#July_31st.2C_2014 In particular, we propose to focus on two items: * A

[openstack-dev] Cinder tempest api volume tests failed

I deployed a single node devstack on Ubuntu 14.04. This devstack belongs to Juno. When i am running tempest api volume test, i am getting some tests failed. *Below are steps for devstack deployment:* 1) git clone https://github.com/openstack-dev/devstack.git 2)cd devstack 3)vi local.conf [[loca

[openstack-dev] [Congress] Integration Demo

Hi All, I have been working on integrating developing a policy demo using Congress. I have done following activities in this direction - Integrated Congress as a service with keystone - Developed a trivial Python-Congressclient with support for basic commands through command line - Integrated cong

[openstack-dev] Openstack Icehouse: URL doesn't exists when install nova-compute

Hi Openstack guys, I'm using Centos 6.4 64bit to deploy OpenStack Icehouse. When installing compute node, I got this error: $ yum install openstack-nova-compute http://yum.theforeman.org/releases/1.5/el6/x86_64/repodata/5db82d54c101b04330bc59837bcb337e196fcb5b226457e44a5a7dcfc62f159d-filelists.sq

Re: [openstack-dev] Paul Luse added to Swift Core

Paul, congratulations! :-) John Dickinson

Re: [openstack-dev] [neutron] Spec exceptions are closed, FPF is August 21

Kyle, Let me know if I can help resolve the concerns around rootwrap. I think in this case, the return on investment could be high with a relatively low investment. Carl On Wed, Jul 30, 2014 at 11:52 AM, Kyle Mestery wrote: > I wanted to send an email to let everyone know where we're at in the

[openstack-dev] Local message bus to connect all neutron agents in a host

openstack is designed as decoupled between all modules, both nova and all neutron plugins: ml2, l3, advanced...however, their agents may need some sort of interaction. Here are two examples: 1) DVR. L2 population already push all portcontext for a subnet to CN, but L3 agent on it has to get once m

[openstack-dev] Paul Luse added to Swift Core

I'm happy to share that Paul Luse has join Swift's core reviewer team. Paul has provided a ton of leadership, insight, and code during the past year. He was instrumental in getting storage policies written, and he's actively involved in the current work around erasure code support. Welcome, Pau

Re: [openstack-dev] [Neutron][CI] VMware mine sweeper for Neutron temporarily disabled

I am still hitting this issue. Are the infrastructure related failures white-listed? Thanks, Paddu From: Joe Gordon mailto:joe.gord...@gmail.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Wednesday, July 30, 2014 4

Re: [openstack-dev] [Neutron][CI] VMware mine sweeper for Neutron temporarily disabled

On Jul 29, 2014 12:46 PM, "Salvatore Orlando" wrote: > > Minesweeper for Neutron is now running again. > We updated the image for our compute nodes to ensure it is compliant with commit [1]. Does this mean you had libvirt < 0.9.11 in minesweeper? I am wondering if others will hit the issue (and m

[openstack-dev] [NFV] Gerrit dashboard (updated, now working)

Hi, During our last meetings, we briefly discussed about the Gerrit dashboard which was previously working but was now generating an error (414 too long URI). I decided to directly create an HTML static file and generating directly the dashboard there instead of redirecting to Gerrit custom dashb

Re: [openstack-dev] [nova] so what do i do about libvirt-python if i'm on precise?

On Jul 30, 2014 3:36 PM, "Clark Boylan" wrote: > > On Wed, Jul 30, 2014, at 03:23 PM, Jeremy Stanley wrote: > > On 2014-07-30 13:21:10 -0700 (-0700), Joe Gordon wrote: > > > While forcing people to move to a newer version of libvirt is > > > doable on most environments, do we want to do that now?

Re: [openstack-dev] [Neutron][LBaaS] Weekly IRC Agenda

Additions: - Change to move handling of ACTIVE/ERROR/DEFERRED and db deletes out of drivers. - Don¹t let gerrit overwrite dependent commits. Thanks, Doug On 7/30/14, 3:30 PM, "Jorge Miramontes" wrote: >Hey LBaaS folks, > > >This is you friendly reminder to provide any agenda items for tomorro

Re: [openstack-dev] [neutron] Cross-server locking for neutron server

On Jul 30, 2014, at 3:27 PM, Jay Pipes wrote: > It's not about distributed locking. It's about allowing multiple threads to > make some sort of progress in the face of a contentious piece of code. Sure, multiple threads, multiple process, multiple remote/distributed/cooperating process (all p

Re: [openstack-dev] [nova] so what do i do about libvirt-python if i'm on precise?

On 07/30/2014 03:34 PM, Clark Boylan wrote: On Wed, Jul 30, 2014, at 03:23 PM, Jeremy Stanley wrote: On 2014-07-30 13:21:10 -0700 (-0700), Joe Gordon wrote: While forcing people to move to a newer version of libvirt is doable on most environments, do we want to do that now? What is the benefit

Re: [openstack-dev] [tc][rally][qa] Application for a new OpenStack Program: Performance and Scalability

Le 30/07/2014 22:13, Boris Pavlovic a écrit : > Hi all, > > This thread is very useful. We've detect issue related to the mission > statement and name of proposed program on early steps. Seems like > mission statement and name are totally unclear and don't present in > the right perspective goals

Re: [openstack-dev] [nova] so what do i do about libvirt-python if i'm on precise?

On Wed, Jul 30, 2014, at 03:23 PM, Jeremy Stanley wrote: > On 2014-07-30 13:21:10 -0700 (-0700), Joe Gordon wrote: > > While forcing people to move to a newer version of libvirt is > > doable on most environments, do we want to do that now? What is > > the benefit of doing so? > [...] > > The only

[openstack-dev] [Neutron][LBaaS] Weekly IRC Agenda

Hey LBaaS folks, This is you friendly reminder to provide any agenda items for tomorrow's weekly IRC meeting. The agenda currently has these items: * Review Updates * Octavia Work Cheers, --Jorge P.S. Please don't forget to update the weekly standup ==> https://etherpad.openstack.org/

Re: [openstack-dev] [neutron] Cross-server locking for neutron server

It's not about distributed locking. It's about allowing multiple threads to make some sort of progress in the face of a contentious piece of code. Obstruction and lock-free algorithms are preferred, IMO, over lock-based solutions that sit there and block while something else is doing something.

Re: [openstack-dev] [nova] so what do i do about libvirt-python if i'm on precise?

On 2014-07-30 13:21:10 -0700 (-0700), Joe Gordon wrote: > While forcing people to move to a newer version of libvirt is > doable on most environments, do we want to do that now? What is > the benefit of doing so? [...] The only dog I have in this fight is that using the split-out libvirt-python on

Re: [openstack-dev] [neutron] A request for sub-projects to post meeting summary emails to the ML

Can we just have meeting-bot post the minutes, if we want a summary of each meeting? Or perhaps send that to a different DL, so it doesn¹t hit -dev? Doug On 7/30/14, 2:13 PM, "Ryan Moats" wrote: >I had occasion to walk through all of the archives of the openstack-dev >mailing list and it dawn

Re: [openstack-dev] [neutron] Cross-server locking for neutron server

I'll just start by saying I'm not the expert in what should-be the solution for neutron here (this is their developers ultimate decision) but I just wanted to add my thoughts Jays solution looks/sounds like a spin lock with a test-and-set[1] (imho still a lock, no matter the makeup u put on

Re: [openstack-dev] [oslo.messaging][infra] Adding support for AMQP 1.0 Messaging to Oslo.Messaging and infra/config

On 2014-07-30 14:59:09 -0400 (-0400), Ken Giusti wrote: > Thanks Daniel. It was my understanding - which may be wrong - that > having devstack install the 'out of band' packages would only help in > the case of the devstack-based integration tests, not in the case of > CI running the unit tests.

Re: [openstack-dev] [Nova] Nominating Jay Pipes for nova-core

On 7/30/2014 2:10 PM, Russell Bryant wrote: On 07/30/2014 05:02 PM, Michael Still wrote: Greetings, I would like to nominate Jay Pipes for the nova-core team. Jay has been involved with nova for a long time now. He's previously been a nova core, as well as a glance core (and PTL). He's been

[openstack-dev] [Neutron][L3] Team Meeting Thursday at 1500 UTC

The Neutron L3 Subteam will meet tomorrow at the regular time in #openstack-meeting-3. The agenda [1] is posted, please update as needed. See you there! The initial DVR implementation has merged as of today. Please review the notes and log from the DVR meeting today [2]. I will be sure to allo

Re: [openstack-dev] [Nova] Nominating Jay Pipes for nova-core

+1 On Wed, Jul 30, 2014 at 4:08 PM, Dan Smith wrote: > > Please respond with +1s or any concerns. > > +1.4142135623 > > --Dan > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listi

Re: [openstack-dev] [Nova] Nominating Jay Pipes for nova-core

big +1 :-) 2014-07-30 14:56 GMT-07:00 Sean Dague : > +1 > > On 07/30/2014 02:19 PM, Chris Behrens wrote: >> +1 >> >> On Jul 30, 2014, at 2:02 PM, Michael Still wrote: >> >>> Greetings, >>> >>> I would like to nominate Jay Pipes for the nova-core team. >>> >>> Jay has been involved with nova for a

Re: [openstack-dev] [Nova] Nominating Jay Pipes for nova-core

On Wed, 2014-07-30 at 14:02 -0700, Michael Still wrote: > I would like to nominate Jay Pipes for the nova-core team. +1 -- Kevin L. Mitchell Rackspace ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin

Re: [openstack-dev] [Nova] Nominating Jay Pipes for nova-core

> Please respond with +1s or any concerns. +1.4142135623 --Dan signature.asc Description: OpenPGP digital signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron] Cross-server locking for neutron server

On 07/30/2014 02:29 PM, Kevin Benton wrote: Yes, we are talking about the same thing. I think the term 'optimistic locking' comes from what happens during the sql transaction. The sql engine converts a read (the WHERE clause) and update (the UPDATE clause) operations into an atomic operation. The

Re: [openstack-dev] [oslo.messaging][infra] Adding support for AMQP 1.0 Messaging to Oslo.Messaging and infra/config

On 7/30/2014 11:59 AM, Ken Giusti wrote: On Wed, 30 Jul 2014 14:25:46 +0100, Daniel P. Berrange wrote: On Wed, Jul 30, 2014 at 08:54:01AM -0400, Ken Giusti wrote: Greetings, Apologies for the cross-post: this should be of interest to both infra and olso.messaging developers. The blueprint [

Re: [openstack-dev] [Nova] Nominating Jay Pipes for nova-core

+1 On Jul 30, 2014, at 2:19 PM, Chris Behrens mailto:cbehr...@codestud.com>> wrote: +1 On Jul 30, 2014, at 2:02 PM, Michael Still mailto:mi...@stillhq.com>> wrote: Greetings, I would like to nominate Jay Pipes for the nova-core team. Jay has been involved with nova for a long time now. He'

Re: [openstack-dev] [Nova] Nominating Jay Pipes for nova-core

+1 On 07/30/2014 02:19 PM, Chris Behrens wrote: > +1 > > On Jul 30, 2014, at 2:02 PM, Michael Still wrote: > >> Greetings, >> >> I would like to nominate Jay Pipes for the nova-core team. >> >> Jay has been involved with nova for a long time now. He's previously >> been a nova core, as well as

Re: [openstack-dev] [Neutron][LBaaS] new common module for Barbican TLS containers interaction

This is not sufficient per our designs. For example the container Consumer registration was supposed to be atomic and not handled in separate calls and I don't like the inflexibility that we are just using tls_ids them selves for every call. (For example We are forcing calls to the slow bar

Re: [openstack-dev] [neutron] Cross-server locking for neutron server

Yes, we are talking about the same thing. I think the term 'optimistic locking' comes from what happens during the sql transaction. The sql engine converts a read (the WHERE clause) and update (the UPDATE clause) operations into an atomic operation. The atomic guarantee requires an internal lock in

[openstack-dev] [neutron] A request for sub-projects to post meeting summary emails to the ML

I had occasion to walk through all of the archives of the openstack-dev mailing list and it dawned on me that neutron sub-projects aren't as regular in posting summary messages of IRC meetings to the ML as they could be. I'd like to suggest that going forward, sub-projects post a summary email o

Re: [openstack-dev] [Nova] Nominating Jay Pipes for nova-core

+1 On Jul 30, 2014, at 2:02 PM, Michael Still wrote: > Greetings, > > I would like to nominate Jay Pipes for the nova-core team. > > Jay has been involved with nova for a long time now. He's previously > been a nova core, as well as a glance core (and PTL). He's been around > so long that the

Re: [openstack-dev] [heat] Uniform style of README file for contrib resources

On Wed, 2014-07-30 at 17:05 +0400, Sergey Kraynev wrote: > On 30 July 2014 16:21, Angus Salkeld > wrote: > On Wed, 2014-07-30 at 13:41 +0400, Sergey Kraynev wrote: > > Hello guys. > > > > > > In the last time I meet again change related with changing >

Re: [openstack-dev] [Nova] Nominating Jay Pipes for nova-core

On 07/30/2014 05:02 PM, Michael Still wrote: > Greetings, > > I would like to nominate Jay Pipes for the nova-core team. > > Jay has been involved with nova for a long time now. He's previously > been a nova core, as well as a glance core (and PTL). He's been around > so long that there are prob

Re: [openstack-dev] [neutron] Cross-server locking for neutron server

In fact there are more applications for distributed locking than just accessing data in database. One of such use cases is serializing access to devices. This is what is not yet hardly needed, but will be as we get more service drivers working with appliances. It would be great if some existing li

[openstack-dev] [Nova] Nominating Jay Pipes for nova-core

Greetings, I would like to nominate Jay Pipes for the nova-core team. Jay has been involved with nova for a long time now. He's previously been a nova core, as well as a glance core (and PTL). He's been around so long that there are probably other types of core status I have missed. Please resp

Re: [openstack-dev] [neutron] Cross-server locking for neutron server

Excerpts from Jay Pipes's message of 2014-07-30 13:53:38 -0700: > On 07/30/2014 12:21 PM, Kevin Benton wrote: > > Maybe I misunderstood your approach then. > > > > I though you were suggesting where a node performs an "UPDATE record > > WHERE record = last_state_node_saw" query and then checks the

Re: [openstack-dev] [nova] stable branches & failure to handle review backlog

> From: Gary Kotton [mailto:gkot...@vmware.com]> > > On 7/30/14, 8:22 PM, "Kevin L. Mitchell" > wrote: > > >On Wed, 2014-07-30 at 09:01 +0200, Flavio Percoco wrote: > >> As a stable-maint, I'm always hesitant to review patches I've no > >> understanding on, hence I end up just checking how big

Re: [openstack-dev] [neutron] Cross-server locking for neutron server

On 07/30/2014 12:21 PM, Kevin Benton wrote: Maybe I misunderstood your approach then. I though you were suggesting where a node performs an "UPDATE record WHERE record = last_state_node_saw" query and then checks the number of affected rows. That's optimistic locking by every definition I've hea

Re: [openstack-dev] [nova] so what do i do about libvirt-python if i'm on precise?

On Wed, Jul 30, 2014 at 12:11 PM, Matt Riedemann wrote: > > > On 7/30/2014 11:49 AM, Joe Gordon wrote: > >> >> >> >> On Wed, Jul 30, 2014 at 6:43 AM, Daniel P. Berrange > > wrote: >> >> On Wed, Jul 30, 2014 at 06:39:56AM -0700, Matt Riedemann wrote: >> > This

Re: [openstack-dev] [tc][rally][qa] Application for a new OpenStack Program: Performance and Scalability

Hi all, This thread is very useful. We've detect issue related to the mission statement and name of proposed program on early steps. Seems like mission statement and name are totally unclear and don't present in the right perspective goals of this program. I updated name and mission statement: n

Re: [openstack-dev] [nova] stable branches & failure to handle review backlog

On 07/30/2014 01:22 PM, Kevin L. Mitchell wrote: > On Wed, 2014-07-30 at 09:01 +0200, Flavio Percoco wrote: >> As a stable-maint, I'm always hesitant to review patches I've no >> understanding on, hence I end up just checking how big is the patch, >> whether it adds/removes new configuration option

Re: [openstack-dev] [neutron] Spec exceptions are closed, FPF is August 21

Also, can I recommend that to avoid last minute rush of all the code in Juno-3 (and then clogging up the gate at that time), we work as a team to re-review patches that have addressed all previously identified issues? For example, the for the GBP plugin, the first series of patches have been updat

Re: [openstack-dev] [nova] stable branches & failure to handle review backlog

On 7/30/14, 8:22 PM, "Kevin L. Mitchell" wrote: >On Wed, 2014-07-30 at 09:01 +0200, Flavio Percoco wrote: >> As a stable-maint, I'm always hesitant to review patches I've no >> understanding on, hence I end up just checking how big is the patch, >> whether it adds/removes new configuration opti

Re: [openstack-dev] [nova] objects notifications

On 7/30/14, 7:26 AM, "Dan Smith" wrote: >> When reviewing https://review.openstack.org/#/c/107954/ it occurred to >> me that maybe we should consider having some kind of generic object >> wrapper that could do notifications for objects. Any thoughts on this? > >I think it might be good to do th

Re: [openstack-dev] [neutron] Cross-server locking for neutron server

Maybe I misunderstood your approach then. I though you were suggesting where a node performs an "UPDATE record WHERE record = last_state_node_saw" query and then checks the number of affected rows. That's optimistic locking by every definition I've heard of it. It matches the following statement f

Re: [openstack-dev] [neutron][policy] Bridging the 2-group gap in group policy

Hi Ryan: As I stated in the patch review, the suggestion to use a "profiled API" like IETF/CCITT is indeed very interesting. As a "profiled API" has not been tried with any neutron model before, and as there is no existing design pattern/best practices for how best to structure that, my recommenda

Re: [openstack-dev] [Neutron] how to deprecate a plugin

In Nova we have done the following: - add a warning in the current version that this will be deprecated in K - start of K drop the code It is also important to have an upgrade path. What happens if I have my RYU plugin in production and I upgrade to the next version. That should be clearly document

Re: [openstack-dev] [NFV] Meeting summary 2014-07-30

Hi, There are a few other issues which may be related: - https://review.openstack.org/103091 - https://review.openstack.org/103094 They are both related to the attachment of new interfaces to a VM Thanks Gary On 7/30/14, 9:38 PM, "Steve Gordon" wrote: >Meeting summary > >https://etherpad

Re: [openstack-dev] [nova] so what do i do about libvirt-python if i'm on precise?

On 7/30/2014 11:49 AM, Joe Gordon wrote: On Wed, Jul 30, 2014 at 6:43 AM, Daniel P. Berrange mailto:berra...@redhat.com>> wrote: On Wed, Jul 30, 2014 at 06:39:56AM -0700, Matt Riedemann wrote: > This change: > > https://review.openstack.org/#/c/105501/ > > Tries

Re: [openstack-dev] [ceilometer][nova] extra Ceilometer Samples of the instance gauge

> In a normal DevStack install, each Compute instance causes one Ceilometer > Sample every 10 minutes. Except, there is an extra one every hour. And a > lot of extra ones at > the start. What's going on here? instance is one meter which is generated through both polling and notifications (se

Re: [openstack-dev] [nova] bp/pxe boot

- Original Message - > From: "Angelo Matarazzo" > To: openstack-dev@lists.openstack.org > > Hi folks, > I would add the pxe boot capability to Nova/libvirt and Horizon too. > Currently, compute instances must be booted from images (or snapshots) > stored in Glance or volumes stored in Cin

Re: [openstack-dev] [oslo.messaging][infra] Adding support for AMQP 1.0 Messaging to Oslo.Messaging and infra/config

On Wed, 30 Jul 2014 14:25:46 +0100, Daniel P. Berrange wrote: > On Wed, Jul 30, 2014 at 08:54:01AM -0400, Ken Giusti wrote: > > Greetings, > > > > Apologies for the cross-post: this should be of interest to both infra > > and olso.messaging developers. > > > > The blueprint [0] that adds support fo

Re: [openstack-dev] [neutron][policy] Bridging the 2-group gap in group policy

Hi all, I support this API proposal. It is simple and conveys clear semantics. Thanks Ryan! Cathy From: Hemanth Ravi [mailto:hemanthrav...@gmail.com] Sent: Wednesday, July 30, 2014 11:13 AM To: OpenStack Development Mailing List (not for usage questions) Cc: Subrahmanyam Ongole Subject: Re: [op

Re: [openstack-dev] [nova] so what do i do about libvirt-python if i'm on precise?

On Wed, Jul 30, 2014 at 6:43 AM, Daniel P. Berrange wrote: > On Wed, Jul 30, 2014 at 06:39:56AM -0700, Matt Riedemann wrote: > > This change: > > > > https://review.openstack.org/#/c/105501/ > > > > Tries to pull in libvirt-python >= 1.2.5 for testing. > > > > I'm on Ubuntu Precise for developmen

Re: [openstack-dev] [NFV] Ready to change the meeting time?

- Original Message - > From: "Isaku Yamahata" > To: "OpenStack Development Mailing List (not for usage questions)" > > > Hi Steve. > > The timeslot of 5:00AM UTC(Tuesday) 30min clashes with it. > https://wiki.openstack.org/wiki/Meetings/ServiceVM > Please disable this time slot. > > t

[openstack-dev] [NFV] Meeting summary 2014-07-30

Meeting summary https://etherpad.openstack.org/p/nfv-meeting-agenda (russellb, 14:00:32) review actions from last week (russellb, 14:00:48) ACTION: bauzas to update list with link to new dash (sgordon, 14:02:34) https://review.openstack.org/#/c/95805/2 (sgordon, 14:02:

[openstack-dev] [ceilometer][nova] extra Ceilometer Samples of the instance gauge

In a normal DevStack install, each Compute instance causes one Ceilometer Sample every 10 minutes. Except, there is an extra one every hour. And a lot of extra ones at the start. What's going on here? For example: $ ceilometer sample-list -m instance -q resource=9108b64e-0e30-45fa-9fdf-ccc2

Re: [openstack-dev] [neutron][policy] Bridging the 2-group gap in group policy

Hi, Adding this CLI command seems to be a good way to provide support for the second model. This can be submitted as a new review patch to work through the approaches to implement this. I suggest the current CLI patch [1] be reviewed for the existing spec and completed. Ryan, would it possible fo

Re: [openstack-dev] [neutron] Cross-server locking for neutron server

On 07/30/2014 10:53 AM, Kevin Benton wrote: Using the UPDATE WHERE statement you described is referred to as optimistic locking. [1] https://docs.jboss.org/jbossas/docs/Server_Configuration_Guide/4/html/The_CMP_Engine-Optimistic_Locking.html SQL != JBoss. It's not optimistic locking in the da

Re: [openstack-dev] [neutron] Cross-server locking for neutron server

Hello, I stop to improve vxlan population and remove SELECT FOR UPDATE[1] because i am not sure the current approach is the right approach to handle vxlan/gre tenant pools: 1- Do we really to populate vxlan/gre tenant pools? The neutron-server could also choose randomly an vxlan vni in vni_ran

Re: [openstack-dev] [neutron] Cross-server locking for neutron server

Using the UPDATE WHERE statement you described is referred to as optimistic locking. [1] https://docs.jboss.org/jbossas/docs/Server_Configuration_Guide/4/html/The_CMP_Engine-Optimistic_Locking.html On Wed, Jul 30, 2014 at 10:30 AM, Jay Pipes wrote: > On 07/30/2014 10:05 AM, Kevin Benton wrote:

Re: [openstack-dev] [heat] Stack update and raw_template backup

On 30/07/14 02:21, Anant Patil wrote: On 28-Jul-14 22:37, Clint Byrum wrote: Excerpts from Zane Bitter's message of 2014-07-28 07:25:24 -0700: On 26/07/14 00:04, Anant Patil wrote: When the stack is updated, a diff of updated template and current template can be stored to optimize database. A

[openstack-dev] [neutron] Spec exceptions are closed, FPF is August 21

I wanted to send an email to let everyone know where we're at in the Juno cycle. We're hitting our stride in Juno-3 development now, and we have a lot of BPs targeted [1]. Due to this, I'm not going to approve any more spec exceptions other than possibly flavors [2] and even less possibly rootwrap

Re: [openstack-dev] [ceilometer] [swift] Improving ceilometer.objectstore.swift_middleware

On 7/30/14, 8:06 AM, Chris Dent wrote: ceilometer/objectstore/swift_middleware.py[1] counts the size of web request and reponse bodies through the swift proxy server and publishes metrics of the size of the request and response and that a request happened at all. There are (at least) two bug re

Re: [openstack-dev] [Neutron] how to deprecate a plugin

On Wed, Jul 30, 2014 at 12:17 PM, YAMAMOTO Takashi wrote: > hi, > > what's the right procedure to deprecate a plugin? we (ryu team) are > considering deprecating ryu plugin, in favor of ofagent. probably in > K-timeframe, if it's acceptable. > The typical way is to announce the deprecation at le

Re: [openstack-dev] [neutron] Cross-server locking for neutron server

On 07/30/2014 10:05 AM, Kevin Benton wrote: i.e. 'optimistic locking' as opposed to the 'pessimistic locking' referenced in the 3rd link of the email starting the thread. No, there's no locking. On Wed, Jul 30, 2014 at 9:55 AM, Jay Pipes mailto:jaypi...@gmail.com>> wrote: On 07/30/2014 0

Re: [openstack-dev] [nova] stable branches & failure to handle review backlog

On Wed, 2014-07-30 at 09:01 +0200, Flavio Percoco wrote: > As a stable-maint, I'm always hesitant to review patches I've no > understanding on, hence I end up just checking how big is the patch, > whether it adds/removes new configuration options etc but, the real > review has to be done by someone

Re: [openstack-dev] [nova] so what do i do about libvirt-python if i'm on precise?

On 7/30/2014 9:57 AM, Matt Riedemann wrote: On 7/30/2014 9:20 AM, Matt Riedemann wrote: On 7/30/2014 6:43 AM, Daniel P. Berrange wrote: On Wed, Jul 30, 2014 at 06:39:56AM -0700, Matt Riedemann wrote: This change: https://review.openstack.org/#/c/105501/ Tries to pull in libvirt-python

Re: [openstack-dev] [heat] [Solum] Stack update and raw_template backup

Excerpts from Anant Patil's message of 2014-07-29 23:21:05 -0700: > On 28-Jul-14 22:37, Clint Byrum wrote: > > Excerpts from Zane Bitter's message of 2014-07-28 07:25:24 -0700: > >> On 26/07/14 00:04, Anant Patil wrote: > >>> When the stack is updated, a diff of updated template and current > >>> t

[openstack-dev] [Neutron] how to deprecate a plugin

hi, what's the right procedure to deprecate a plugin? we (ryu team) are considering deprecating ryu plugin, in favor of ofagent. probably in K-timeframe, if it's acceptable. YAMAMOTO Takashi ___ OpenStack-dev mailing list OpenStack-dev@lists.openstac

Re: [openstack-dev] [ALL] Removing the tox==1.6.1 pin

On 7/30/2014 2:27 AM, Michele Paolino wrote: On 30/07/2014 07:53, Matt Riedemann wrote: On 7/25/2014 2:38 PM, Clark Boylan wrote: Hello, The recent release of tox 1.7.2 has fixed the {posargs} interpolation issues we had with newer tox which forced us to be pinned to tox==1.6.1. Before we

Re: [openstack-dev] [neutron] Cross-server locking for neutron server

-Original Message- From: Jay Pipes Reply: OpenStack Development Mailing List (not for usage questions) > Date: July 30, 2014 at 09:59:15 To: openstack-dev@lists.openstack.org > Subject:  Re: [openstack-dev] [neutron] Cross-server locking for neutron server > On 07/30/2014 09:48 AM, Doug

Re: [openstack-dev] [nova] so what do i do about libvirt-python if i'm on precise?

On 7/30/2014 6:43 AM, Daniel P. Berrange wrote: On Wed, Jul 30, 2014 at 06:39:56AM -0700, Matt Riedemann wrote: This change: https://review.openstack.org/#/c/105501/ Tries to pull in libvirt-python >= 1.2.5 for testing. I'm on Ubuntu Precise for development which has libvirt 0.9.8. The lat

Re: [openstack-dev] [neutron] Cross-server locking for neutron server

i.e. 'optimistic locking' as opposed to the 'pessimistic locking' referenced in the 3rd link of the email starting the thread. On Wed, Jul 30, 2014 at 9:55 AM, Jay Pipes wrote: > On 07/30/2014 09:48 AM, Doug Wiegley wrote: > >> I'd have to look at the Neutron code, but I suspect that a simple >

Re: [openstack-dev] [nova] so what do i do about libvirt-python if i'm on precise?

On 7/30/2014 9:20 AM, Matt Riedemann wrote: On 7/30/2014 6:43 AM, Daniel P. Berrange wrote: On Wed, Jul 30, 2014 at 06:39:56AM -0700, Matt Riedemann wrote: This change: https://review.openstack.org/#/c/105501/ Tries to pull in libvirt-python >= 1.2.5 for testing. I'm on Ubuntu Precise fo

Re: [openstack-dev] [neutron] Cross-server locking for neutron server

Excerpts from Doug Wiegley's message of 2014-07-30 09:48:17 -0700: > > I'd have to look at the Neutron code, but I suspect that a simple > > strategy of issuing the UPDATE SQL statement with a WHERE condition that > > I¹m assuming the locking is for serializing code, whereas for what you > describ

Re: [openstack-dev] [neutron] Cross-server locking for neutron server

On 07/30/2014 09:48 AM, Doug Wiegley wrote: I'd have to look at the Neutron code, but I suspect that a simple strategy of issuing the UPDATE SQL statement with a WHERE condition that I¹m assuming the locking is for serializing code, whereas for what you describe above, is there some reason we w

Re: [openstack-dev] [neutron] Cross-server locking for neutron server

> I'd have to look at the Neutron code, but I suspect that a simple > strategy of issuing the UPDATE SQL statement with a WHERE condition that I¹m assuming the locking is for serializing code, whereas for what you describe above, is there some reason we wouldn¹t just use a transaction? Thanks, do

Re: [openstack-dev] [neutron] Cross-server locking for neutron server

There's also no need to use locks at all for this (distributed or otherwise). You can use a compare and update strategy with an exponential backoff similar to the approach taken here: https://review.openstack.org/#/c/109837/ I'd have to look at the Neutron code, but I suspect that a simple

[openstack-dev] [nova] bp/pxe boot

Hi folks, I would add the pxe boot capability to Nova/libvirt and Horizon too. Currently, compute instances must be booted from images (or snapshots) stored in Glance or volumes stored in Cinder. Our idea (as you can find below) is already described there [1] [2] and "aims to provide a design fo

[openstack-dev] [marconi] Juno / Graduation Planning Session Today

Hi everyone, sorry for the short notice, but we are going to hold a special roadmap planning meeting today. Everyone is welcome to attend, but I esp. need core reviewers to attend: When: 2100 UTC Where: #openstack-marconi Agenda: https://etherpad.openstack.org/p/marconi-scratch Hope to see you

Re: [openstack-dev] [neutron] Cross-server locking for neutron server

Please do not re-invent locking.. the way we reinvented locking in Heat. ;) There are well known distributed coordination services such as Zookeeper and etcd, and there is an abstraction for them already called tooz: https://git.openstack.org/cgit/stackforge/tooz/ Excerpts from Elena Ezhova's me

[openstack-dev] [marconi] New name for the project

Hi everyone, we have discussed a few new names for the project to avoid trademark issues. Previously, we had chosen “Naav” but several people weren’t feeling great about that name. So, we discussed this today in #openstack-marconi and got consensus to rename Marconi to Zaqar. If anyone has any

[openstack-dev] [neutron] Cross-server locking for neutron server

Hello everyone! Some recent change requests ([1], [2]) show that there is a number of issues with locking db resources in Neutron. One of them is initialization of drivers which can be performed simultaneously by several neutron servers. In this case locking is essential for avoiding conflicts wh

Re: [openstack-dev] [Neutron] Not support dnsmasq < 2.63?

The hard limit should be 2.63 since that is supported in all of the modern long term releases from the distros. I’d prefer we not exit processes because we’ve been removing active checks on process starts. mark On Jul 29, 2014, at 9:51 PM, Xuhan Peng mailto:pengxu...@gmail.com>> wrote: We

[openstack-dev] [Trove] Specs improvements. Review request.

Hello, Stackers. I’ve been working on several specs and i’d like to receive early feedbacks on updated specs for: - Database log manipulations. Describes initial feature description. - https://wiki.openstack.org/wiki/Trove/DBInstanceLogOperation - Events notificat

Re: [openstack-dev] [Oslo] [Oslo.messaging] RPC failover handling in rabbitmq driver

On 07/28/2014 11:20 AM, Bogdan Dobrelya wrote: > Hello. > I'd like to bring your attention to major RPC failover issue in > impl_rabbit.py [0]. There are several *related* patches and a number of > concerns should be considered as well: > - Passive exchanges fix [1] (looks like the problem is much

[openstack-dev] [Trove] Datastore/Versions API improvements

Hello, Stackers. I’d like to gather Trove team around question related to Datastores/Version API responses (request/response payloads and HTTP codes). Small INFO When deployer creates datastore and versions for it Troves` backend receives request to store DBDatastore and DBDatastoreVer

[openstack-dev] [ceilometer] [swift] Improving ceilometer.objectstore.swift_middleware

ceilometer/objectstore/swift_middleware.py[1] counts the size of web request and reponse bodies through the swift proxy server and publishes metrics of the size of the request and response and that a request happened at all. There are (at least) two bug reports associated with this bit of code:

Re: [openstack-dev] [Openstack] [Barbican] Keystone PKI token too much long

We recently merged an implementation for GET /v3/catalog which finally enables POST /v3/auth/tokens?nocatalog to be a reasonable default behavior, at the cost of an extra HTTP call from remote service back to keystone where necessary. Spec: https://github.com/openstack/keystone-specs/blob/master/s

[openstack-dev] What's Up Doc? July 30 2014

Hi all, We had the APAC docs team meeting and here are the minutes and logs: http://eavesdrop.openstack.org/meetings/docteam/2014/docteam.2014-07-30-03.01.html http://eavesdrop.openstack.org/meetings/docteam/2014/docteam.2014-07-30-03.01.log.html Lots going on in doclandia so let's get started.

Re: [openstack-dev] [Ceilometer] Generate Event or Notification in Ceilometer

If all you want to do is publish a notification you can use oslo.messaging directly. Or, for something lighter weight, we have Notabene, which is a small wrapper on Kombu. An example of how our notification simulator/generator uses it is available here: https://github.com/StackTach/notigen/blob

Re: [openstack-dev] [Ceilometer] Generate Event or Notification in Ceilometer

On 07/30/2014 12:12 AM, Duan, Li-Gong (Gary@HPServers-Core-OE-PSC) wrote: Hi Jay, Thanks for your comment. You suggestion is good but I am wondering why we cannot use or leverage Ceilometer to monitor infrastructure-related, as it can used to monitor tenant-related things. You *could* use Ceil

  1   2   >