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

On 07/29/2014 09:01 PM, Russell Bryant wrote: > On 07/29/2014 12:12 PM, Daniel P. Berrange wrote: >> Sure there was some debate about what criteria were desired acceptance >> when stable trees were started. Once the criteria are defined I don't >> think it is credible to say that people are incapab

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

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. Regards, Gary On 07/29/2014 02:05 AM, Duan, Li-Gong (Gary at HPServers-Core-OE-PSC

Re: [openstack-dev] [glance] HTTPS client breaks nova

On 07/23/2014 06:05 PM, Rob Crittenden wrote: > Rob Crittenden wrote: >> It looks like the switch to requests in python-glanceclient >> (https://review.openstack.org/#/c/78269/) has broken nova when SSL is >> enabled. >> >> I think it is related to the custom object that the glanceclient uses. >> I

Re: [openstack-dev] [Nova] Boot from ISO feature status

Hi Daniel, For now (IceHouse), it's not possible to boot from iso and attach volume after boot. Libvirt present ISO disk via an IDE controller (/dev/hda) and new volume try to be added as IDE too (/dev/hdb). Do you mean that with the new block device mapping code, we will be able to boot from ISO

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 30/07/14 04:00, Kyle Mestery wrote: > I'm personally ok with this hard limit, but I'd really like to > hear from distribution people here to understand their thoughts, > including what versions of dnsmasq ship with their products and how > this wo

Re: [openstack-dev] [nova] bug discussion at mid cycle meet up

On Tue, Jul 29, 2014 at 02:48:12PM -0400, Russell Bryant wrote: > On 07/29/2014 11:43 AM, Tracy Jones wrote: > > 3. We have bugs that are really not bugs but features, or performance > > issues. They really should be a BP not a bug, but we don’t want these > > things to fall off the radar so they

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 29/07/14 18:12, Daniel P. Berrange wrote: > On Tue, Jul 29, 2014 at 08:30:09AM -0700, Jay Pipes wrote: >> On 07/29/2014 06:13 AM, Daniel P. Berrange wrote: >>> On Tue, Jul 29, 2014 at 02:04:42PM +0200, Thierry Carrez >>> wrote: Ihar Hrachyshk

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

On Wed, Jul 30, 2014 at 11:16:00AM +0200, Ihar Hrachyshka wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 29/07/14 18:12, Daniel P. Berrange wrote: > > On Tue, Jul 29, 2014 at 08:30:09AM -0700, Jay Pipes wrote: > >> On 07/29/2014 06:13 AM, Daniel P. Berrange wrote: > >>> On Tue,

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

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 can remove the pin and start telling people to u

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

On Fri, Jul 25, 2014 at 02:38:49PM -0700, 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 can remove the pin and start telling people to use latest tox > we

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

Hello guys. In the last time I meet again change related with changing content of README for Docker resource. https://review.openstack.org/#/c/110541/ https://review.openstack.org/#/c/101144/ Both changes try to improve current description. I looked on other README files in contrib directories a

[openstack-dev] [Trove] Configuration Groups CLI improvements

Hello, Stackers. Since Trove gives an ability to create post-deployment configuration for instances, it would be nice to have an ability to pass database configuration file location through configuration file location. I’d like to propose feature that would improve usability of CLI for config

Re: [openstack-dev] [PKG-Openstack-devel] Bug#755315: [Trove] Should we stop using wsgi-intercept, now that it imports from mechanize? this is really bad!

On Tue, 29 Jul 2014, Chris Dent wrote: Let me know whenever you have a new release, without mechanize as new dependency, or with it being optional. It will be soon (a day or so). https://pypi.python.org/pypi/wsgi_intercept is now at 0.8.0 All traces of mechanize removed. Have at. Enjoy. If

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

On Fri, Jul 25, 2014 at 02:38:49PM -0700, Clark Boylan wrote: > New tox sets a random PYTHONHASHSEED value by default. Arguably this is > a good thing as it forces you to write code that handles unknown hash > seeds, but unfortunately many projects' unittests don't currently deal > with this very w

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

Hi Kyle, SUSE Cloud ships dnsmasq 2.71 . For us it's fine to bump the minimum version supported to 2.63 . cheers, Rossella On 07/30/2014 04:00 AM, Kyle Mestery wrote: > On Tue, Jul 29, 2014 at 8:51 PM, Xuhan Peng wrote: >> We bumped the minimum version of dnsmasq to 2.63 a while ago by this co

Re: [openstack-dev] [TripleO] Spec process

James Slagle wrote: > Finally, the juno-2 milestone has passed. Many (if not all?) > integrated projects have already -2'd specs that have not been > approved, indicating they are not going to make Juno. There are many > valid reasons to do this: focus, stabilization, workload, etc. > > Personally

Re: [openstack-dev] [Keystone] Survey on Token Provider Usage

Morgan Fainberg wrote: > The Keystone team is looking for feedback from the community on what type of > Keystone Token is being used in your OpenStack deployments. This is to help > us understand the use of the different providers and get information on the > reasoning (if possible) that that to

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

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 content of > README for Docker resource. > > > > https://review.openstack.org/#/c/110541/ I can ditch mine, just making a change after helping someone on IRC

Re: [openstack-dev] [Manila] Incubation request

Swartzlander, Ben wrote: > On Tue, 2014-07-29 at 13:38 +0200, Thierry Carrez wrote: >> Swartzlander, Ben a écrit : >>> Manila has come a long way since we proposed it for incubation last autumn. >>> Below are the formal requests. >>> >>> https://wiki.openstack.org/wiki/Manila/Incubation_Applicatio

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

Russell Bryant wrote: > On 07/29/2014 12:12 PM, Daniel P. Berrange wrote: >> Sure there was some debate about what criteria were desired acceptance >> when stable trees were started. Once the criteria are defined I don't >> think it is credible to say that people are incapable of following the >> r

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

Greetings, Apologies for the cross-post: this should be of interest to both infra and olso.messaging developers. The blueprint [0] that adds support for version 1.0 of the AMQP messaging protocol is blocked due to CI test failures [1]. These failures are due to a new package dependency this bluep

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

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 content of > > README for Docker resource. > > > > > > > > https://review.openstack.org/#/c/110541/ > > I c

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

So we need to create a decorator method for create(), save(), destroy() etc as following? NOTIFICATION_FIELDS = ['host', 'metadata', ...] @notify_on_save(NOTIFICATION_FIELDS) @base.remotable def save(context): @notify_on_create(NOTIFICATION_FIELDS) @base.remotable def create(context):

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

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 for version 1.0 of the AMQP messaging > protocol is blocked due to CI test f

Re: [openstack-dev] [Neutron] Managing change in gerrit which depends on multiple other changes in review

Hi Brandon, Doug Thanks for your explanations and feedback I think I understand now what should be done. I made a commit today to my TLS change https://review.openstack.org/#/c/109035 And my barbican module change https://review.openstack.org/#/c/109849 It caused: 1. patch commit to "New extensi

[openstack-dev] [oslo][nova] can't rebuild local tox due to oslo alpha packages

I noticed yesterday that trying to rebuild tox in nova fails because it won't pull down the oslo alpha packages (config, messaging, rootwrap). It looks like you need the --pre option with pip install to get these normally. Also sounds like tox should already be doing --pre, but it doesn't ap

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

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 latest libvirt-python appears to require libvirt >= 0.9.11. So do I have to move to Trusty? -- Thanks, Matt Riedeman

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

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 latest libvirt-python appears to requi

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

On 07/30/2014 02:21 AM, Daniel P. Berrange wrote: > On Wed, Jul 30, 2014 at 11:16:00AM +0200, Ihar Hrachyshka wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA512 >> >> On 29/07/14 18:12, Daniel P. Berrange wrote: >>> On Tue, Jul 29, 2014 at 08:30:09AM -0700, Jay Pipes wrote: On 07/29/

[openstack-dev] tempest api volume test 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 [[local|l

Re: [openstack-dev] [oslo][nova] can't rebuild local tox due to oslo alpha packages

> I noticed yesterday that trying to rebuild tox in nova fails because it > won't pull down the oslo alpha packages (config, messaging, rootwrap). i ran into this yesterday as well. Doug suggested i update my virtualenv and that worked. i went from 1.10.1 to 1.11.x cheers, gord

Re: [openstack-dev] tempest api volume test failed

On 07/30/2014 06:51 AM, Nikesh Kumar Mahalka wrote: > 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/o

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

On Wed, Jul 30, 2014 at 7:52 AM, Thierry Carrez wrote: > Russell Bryant wrote: >> On 07/29/2014 12:12 PM, Daniel P. Berrange wrote: >>> Sure there was some debate about what criteria were desired acceptance >>> when stable trees were started. Once the criteria are defined I don't >>> think it is c

Re: [openstack-dev] [Neutron] nova-network as ML2 mechanism?

On Tue, Jul 29, 2014 at 10:12 AM, Jonathan Proulx wrote: > Hi All, > > Would making an nova-network mechanism driver for the ml2 plugin be possible? > This has been discussed a bit, and yes, in theory this is possible. Nachi has started looking into this as far as I know. I also think this may hav

[openstack-dev] [neutron] [nova] Parity meeting cancelled this week

Given the fact most of the key players are at the nova mid-cycle this week, lets cancel the parity meeting [1] for today. Next week, lets focus on what came out of the nova mid-cycle and a plan for the final weeks of Juno. Thanks! Kyle [1] https://wiki.openstack.org/wiki/Meetings/NeutronNovaNetwo

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

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

[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] [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] [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:

[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

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] 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] [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:[email protected]>> wrote: We

[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

[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

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] [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

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

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

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] [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

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] [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: [email protected] > 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] [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

[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 [email protected]

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

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] [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] [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:[email protected]>> wrote: On 07/30/2014 0

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] [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

[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] [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

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] [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][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

[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

[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:

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

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] [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:[email protected]] 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] [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] [nova] bp/pxe boot

- Original Message - > From: "Angelo Matarazzo" > To: [email protected] > > 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] [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] 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:[email protected]>> 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] [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] [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] [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] 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] [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] [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] [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 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] [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] 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] [nova] stable branches & failure to handle review backlog

> From: Gary Kotton [mailto:[email protected]]> > > 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] [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

[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

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

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] [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

+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

[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] [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

  1   2   >