Re: [openstack-dev] [Horizon][stable] Horizon kilo gate fails due to testrepository dependency

On Tue, Jan 05, 2016 at 12:26:24PM +1300, Robert Collins wrote: > On 5 January 2016 at 12:04, Robert Collins wrote: > ... > > Indeed - > > https://bitbucket.org/pypa/setuptools/commits/fb35fcade302fa828d34e6aff952ec2398f2c877?at=get_command_list > > - the failing bit

[openstack-dev] [watcher] Mid-cycle developer meetup (2016-02-2/3/4)

Dear all, Wish you all an happy 2016 ! Watcher team is planning a mid-cycle developer meetup in Austin, TX. IBM Austin will host the event. Please find more details on our dedicated wiki page [1]. RSVP is required on our eventbrite page [2] by EOD January 22nd. Any comments/suggestions are

[openstack-dev] [devstack] [neutron] Progress, and current problems

I have been trying to get http://docs.openstack.org/developer/devstack/guides/neutron.html#using-neutron-with-a-single-interface working on Ubuntu 14.04 (updated to the latest, which includes kernel 3.19). With the latest sources and a sufficiently recent OVS, the one-node install pretty

Re: [openstack-dev] [keystone] Addressing issue of keysone token expiry during long running operations

Jamie John Garbutt suggested I follow up this issue with you. I understand you may be leading the effort to address the issue of token expiry during a long running operation. Nova encounter this scenario during image snapshots and live migrations. Is there a keystone blueprint for this issue?

Re: [openstack-dev] [log] LOG.exception should contain an exception message or not?

Excerpts from Sean Dague's message of 2016-01-05 08:31:34 -0500: > On 01/05/2016 08:08 AM, Akihiro Motoki wrote: > > Hi, > > > > # cross-posting to -dev and -operators ML > > > > In the current most OpenStack implementation, > > when we use LOG.exception, we don't pass an exception message to >

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On 12/23/2015 07:40 PM, Steven Hardy wrote: On Wed, Dec 23, 2015 at 11:05:05AM -0600, Ben Nemec wrote: On 12/23/2015 10:26 AM, Steven Hardy wrote: On Wed, Dec 23, 2015 at 09:28:59AM -0600, Ben Nemec wrote: On 12/23/2015 03:19 AM, Dougal Matthews wrote: On 22 December 2015 at 17:59, Ben

Re: [openstack-dev] [Horizon][stable] Horizon kilo gate fails due to testrepository dependency

On Tue, Jan 5, 2016 at 9:16 AM, Matthias Runge wrote: > On Tue, Jan 05, 2016 at 12:26:24PM +1300, Robert Collins wrote: > > On 5 January 2016 at 12:04, Robert Collins > wrote: > > ... > > > Indeed - >

Re: [openstack-dev] [puppet] Puppet OpenStack Mid-Cycle (Mitaka)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/05/2016 11:49 AM, Emilien Macchi wrote: > > > On 12/24/2015 09:18 AM, Emilien Macchi wrote: >> Regarding the list of attendees and their schedule constraints, >> it seems that: 25-26-27 of January would work for everyone. > > Just for the

[openstack-dev] [Tacker] Mitaka midcycle meetup - Jan 28, 29

Greetings, Tacker mid-cycle meetup is scheduled for Jan 28th & 29th in San Jose @ Brocade site. Please update the etherpad [1] to signup and add topics of interest. thanks, Sridhar [1] https://etherpad.openstack.org/p/tacker-mitaka-midcycle

Re: [openstack-dev] [puppet] Puppet OpenStack Mid-Cycle (Mitaka)

On 12/24/2015 09:18 AM, Emilien Macchi wrote: > Regarding the list of attendees and their schedule constraints, it seems > that: > 25-26-27 of January would work for everyone. Just for the record, the final date is 25-26-27 of January. Agenda is here:

Re: [openstack-dev] [puppet] Puppet OpenStack Mid-Cycle (Mitaka)

On 01/05/2016 12:05 PM, Anita Kuno wrote: > On 01/05/2016 11:49 AM, Emilien Macchi wrote: > > >> On 12/24/2015 09:18 AM, Emilien Macchi wrote: >>> Regarding the list of attendees and their schedule constraints, >>> it seems that: 25-26-27 of January would work for everyone. > >> Just for the

Re: [openstack-dev] [log] LOG.exception should contain an exception message or not?

On 01/05/2016 08:08 AM, Akihiro Motoki wrote: > Hi, > > # cross-posting to -dev and -operators ML > > In the current most OpenStack implementation, > when we use LOG.exception, we don't pass an exception message to > LOG.exception: > > LOG.exception(_LE("Error while processing VIF ports")) >

Re: [openstack-dev] [doc] DocImpact vs. reno

On 01/04/2016 08:01 PM, Lana Brindley wrote: > I’m late to this party because holidays (Thanks Anne for bringing it to > my attention). > > First of all, sorry this came as a surprise. I tried hard to make sure > everyone who needed to know knew, but that’s naturally a difficult thing > to do. >

Re: [openstack-dev] [puppet] weekly meeting #65

On 01/04/2016 07:31 AM, Emilien Macchi wrote: > Hi and happy new year folks! > > Tomorrow we will have our weekly meeting at UTC 1500. > Here is our agenda: > https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160105 > > Feel free to add more topics, re

Re: [openstack-dev] [all] Austin Summit Panel on Generation of Sample Configuration Option Files

Excerpts from Ben Nemec's message of 2016-01-04 17:43:20 -0600: > On 01/04/2016 03:50 PM, Kendall J Nelson wrote: > > Hello, > > > > > > In brainstorming ideas for talks at the upcoming summit, I thought about > > some of the things I had worked on for Cinder and what could still be > >

Re: [openstack-dev] [kolla] Adding Ubuntu Liberty to Kolla-Mitaka

On 01/04/2016 06:48 PM, Steven Dake (stdake) wrote: > Thomas, > > Adding a distribution to the gating is a very complex activity and > requires IIRC a full-time engineer to commit to maintaining the images. > Kolla developers can't help here, because we don¹t know how to add Debian > images to

Re: [openstack-dev] [all] Austin Summit Panel on Generation of Sample Configuration Option Files

Excerpts from Kendall J Nelson's message of 2016-01-04 15:50:15 -0600: > > > Hello, > > > > In brainstorming ideas for talks at the upcoming summit, I thought > about some of the things I had worked on for Cinder and what could still be > improved. One of the things I have been looking

Re: [openstack-dev] [telemetry][aodh][vitrage] The purpose of notification about alarm updating

> -Original Message- > From: gord chung [mailto:g...@live.ca] > Sent: Friday, December 11, 2015 10:17 PM > > the original reason this was implemented i believe was to track alarm > state changes as an event in ceilometer events. i still see this as a > valid use case but it does duplicate

[openstack-dev] [puppet] proposing Alex Schultz part of core team

Hi, Alex Schultz (mwhahaha on IRC) has been a very active contributor over the last months in the Puppet OpenStack group: * He's doing a lot of reviews and they are very valuable. He's in my opinion fully aware of our conventions and has nice insights to improve our modules. * He's very helpful

Re: [openstack-dev] [puppet] proposing Alex Schultz part of core team

I'm not a core, but Alex has been very helpful to me in the past and I think he's definitely earned it, +1. Thanks, Nate -Original Message- From: Emilien Macchi [mailto:emil...@redhat.com] Sent: Tuesday, January 5, 2016 9:55 AM To: OpenStack Development Mailing List Subject:

Re: [openstack-dev] [puppet] proposing Alex Schultz part of core team

+1 On Tue, Jan 5, 2016 at 1:15 PM, Potter, Nathaniel < nathaniel.pot...@intel.com> wrote: > I'm not a core, but Alex has been very helpful to me in the past and I > think he's definitely earned it, +1. > > Thanks, > Nate > > -Original Message- > From: Emilien Macchi

Re: [openstack-dev] [puppet] proposing Alex Schultz part of core team

+1 from me! On Tue, Jan 5, 2016 at 10:55 AM, Emilien Macchi wrote: > Hi, > > Alex Schultz (mwhahaha on IRC) has been a very active contributor over > the last months in the Puppet OpenStack group: > * He's doing a lot of reviews and they are very valuable. He's in my >

Re: [openstack-dev] [cinder] Object backporting and the associated service

> On Jan 5, 2016, at 7:13 AM, Michał Dulko wrote: > > On 01/04/2016 11:41 PM, Ryan Rossiter wrote: >> My first question is: what will be handling the object backports that the >> different cinder services need? In Nova, we have the conductor service, >> which handles

Re: [openstack-dev] [all] Austin Summit Panel on Generation of Sample Configuration Option Files

Okay, to clarify, you are saying pip freeze to get the list of libraries for the oslo.config.opts section in entry points here https://github.com/openstack/cinder/blob/master/setup.cfg#L44 ? All the Best, Kendall J. Nelson

Re: [openstack-dev] [heat] Client checking of server version

On 04/01/16 15:53, Jay Dobies wrote: I ran into an issue in a review about moving environment resolution from client to server [1]. It revolves around clients being able to access older versions of servers (that's a pretty simplistic description; see [2] for the spec). Before the holiday, Steve

Re: [openstack-dev] [all] Austin Summit Panel on Generation of Sample Configuration Option Files

Ben, Please see my in-line responses ... On 01/04/2016 05:43 PM, Ben Nemec wrote: On 01/04/2016 03:50 PM, Kendall J Nelson wrote: Hello, In brainstorming ideas for talks at the upcoming summit, I thought about some of the things I had worked on for Cinder and what could still be improved.

[openstack-dev] [Openstack-dev][Manila] status=NONE when share is created

Hi All, https://bugs.launchpad.net/manila/+bug/1526284 stack@controller:~/devstack$ manila create NFS 1 --name share5 --share-type GENERAL_Storage +-+--+ | Property | Value |

Re: [openstack-dev] [keystone] Addressing issue of keysone token expiry during long running operations

On 01/05/2016 05:05 AM, Carlton, Paul (Cloud Services) wrote: Jamie John Garbutt suggested I follow up this issue with you. I understand you may be leading the effort to address the issue of token expiry during a long running operation. Nova encounter this scenario during image snapshots and

Re: [openstack-dev] [doc] DocImpact vs. reno

> On 6 Jan 2016, at 1:19 PM, Jeremy Stanley wrote: > > On 2016-01-06 11:43:34 +1100 (+1100), Lana Brindley wrote: > [...] >> I’m starting to think that DocImpact needs to simply be retired then > > Alternatively, let the remaining projects which currently auto-open > bugs

Re: [openstack-dev] [Openstack-operators] [log] LOG.exception should contain an exception message or not?

Perhaps the recommendation should be to not use line-oriented tools (and formatters) for logs? At least at yahoo we use the json formatter provided by oslo.log and then use the functionality of splunk to handle json records (which afaik is built-in). Likely other tools can also handle json

[openstack-dev] [cinder] oslo_config.PortOp is undefined

Hello, I have a devstack created on 12/22/15. Just seeing that (after a vacation) it stops working. Tried to restart the cinder services, getting the error: stack@openstack4:~/devstack$ /usr/local/bin/cinder-api --config-file /etc/cinder/cinder.conf & echo $!

[openstack-dev] [tempest][radosgw][devstack-ceph-plugin] tempest failure with radosgw as swift endpoint

Hi stackers, Facing some issue running tempest with ceph radosgw as the swift endpoint. I enabled radosgw as part of a test-only patch which configures it as the swift endpoint, the CI fails since tempest's verify-tempest-config fails Console logs are at [1], tempest logs @ [2]

Re: [openstack-dev] [cinder] oslo_config.PortOp is undefined

I did not do anything specific. Oslo Config has IntOpt, not PortOpt. Any clue how can I upgrade oslo.config? --pradip On Tue, Jan 5, 2016 at 4:43 PM, Julien Danjou wrote: > On Tue, Jan 05 2016, Pradip Mukhopadhyay wrote: > > Upgrade oslo.config? > > > Hello, > > > > >

Re: [openstack-dev] [cinder] oslo_config.PortOp is undefined

PortOpt definitely exists in oslo.config [1]. Try executing "pip install -U -r /opt/stack/cinder/requirements.txt". [1] https://github.com/openstack/oslo.config/blob/f5e2fab3ae5af5bd47fe3526a73f13fbaa27c1f0/oslo_config/cfg.py#L1180-L1216 On 01/05/2016 12:33 PM, Pradip Mukhopadhyay wrote: > I did

Re: [openstack-dev] [cinder] oslo_config.PortOp is undefined

On Tue, Jan 05 2016, Pradip Mukhopadhyay wrote: Upgrade oslo.config? > Hello, > > > I have a devstack created on 12/22/15. Just seeing that (after a vacation) > it stops working. > > Tried to restart the cinder services, getting the error: > > stack@openstack4:~/devstack$

Re: [openstack-dev] [tempest][radosgw][devstack-ceph-plugin] tempest failure with radosgw as swift endpoint

On Tue, Jan 5, 2016 at 5:02 PM, Deepak Shetty wrote: > Hi stackers, >Facing some issue running tempest with ceph radosgw as the swift > endpoint. > >I enabled radosgw as part of a test-only patch which configures it as > the >swift endpoint, the CI fails since

Re: [openstack-dev] [cinder] oslo_config.PortOp is undefined

After upgrading all the oslo.config, oslo.service and oslo.log, now c-sch and c-vol running well. Buit c-api is failing with this stack-trace: stack@openstack4:~/devstack$ screen -x 2016-01-05 06:44:18.544 TRACE cinder return self.object_type.invoke(self) 2016-01-05 06:44:18.544 TRACE cinder

Re: [openstack-dev] [log] LOG.exception should contain an exception message or not?

On Tue, Jan 05, 2016 at 10:08:42PM +0900, Akihiro Motoki wrote: > Hi, > > # cross-posting to -dev and -operators ML > > In the current most OpenStack implementation, > when we use LOG.exception, we don't pass an exception message to > LOG.exception: > > LOG.exception(_LE("Error while

Re: [openstack-dev] [infra] Nodepool and wiki.openstack.org downtime on 5 January 2016

On Mon, Jan 4, 2016 at 10:46 AM, Colleen Murphy wrote: > The site wiki.openstack.org as well as the nodepool service will be > offline for 30 minutes starting at 2100 UTC on 5 January 2016 while we > update infrastructure management of these services. The nodepool downtime >

Re: [openstack-dev] [heat] Client checking of server version

On Mon, Jan 04, 2016 at 03:53:07PM -0500, Jay Dobies wrote: > I ran into an issue in a review about moving environment resolution from > client to server [1]. It revolves around clients being able to access older > versions of servers (that's a pretty simplistic description; see [2] for the >

Re: [openstack-dev] [nova][cinder] Deprecating ConfKeyManager (fixed-key key manager)

>> Aiming toward tests that mirror real-world deployment is certainly a >> good thing, but I don't think we should remove ConfKeyManager. >> >> We will want to maintain the ability to test these Cinder/Nova code >> paths in development environments or in some automated environments >> without

[openstack-dev] [Neutron][Nova][nova-scheduler] Neutron's Routed Networks and Nova

I attended the Nova scheduler meeting yesterday morning in hopes to set the stage for a discussion about Neutron's routed networks work and how that affects Nova [1]. John suggested that I write up a backlog spec to start the discussion (as he has suggested to me before). I did so today and

[openstack-dev] [app-catalog] IRC Meeting Thursday January 7th at 17:00UTC

Please join us this Thursday for our first meeting of 2016, January 7th at 17:00UTC in #openstack-meeting-3. The agenda can be found here: https://wiki.openstack.org/wiki/Meetings/app-catalog Please add agenda items if there's anything specific you would like to discuss (or of course if the

[openstack-dev] [log] LOG.exception should contain an exception message or not?

Hi, # cross-posting to -dev and -operators ML In the current most OpenStack implementation, when we use LOG.exception, we don't pass an exception message to LOG.exception: LOG.exception(_LE("Error while processing VIF ports")) IIUC it is because the exception message will be logged at the

Re: [openstack-dev] [cinder] Object backporting and the associated service

On 01/04/2016 11:41 PM, Ryan Rossiter wrote: > My first question is: what will be handling the object backports that the > different cinder services need? In Nova, we have the conductor service, which > handles all of the messy RPC and DB work. When anyone needs something > backported, they ask

[openstack-dev] [tricircle] play Tricircle with devstack

As the phase 1 of stateless design finished, now Tricircle could be played with devstack. Very limited functions for phase 1 were offered. Please visit https://github.com/openstack/tricircle/tree/experiment for how to do that. Welcome for bug-report, please register bug at

[openstack-dev] [tricircle] weekly meeting of Jan.6

Hi, Let's have a weekly meeting for phase 2 of stateless design, meeting will be held at the UTC1300 at #openstack-meeting on Jan.6. Agenda: Progress of To-do list: https://etherpad.openstack.org/p/TricircleToDo Discussion of phase 2 of stateless design. Best Regards Chaoyi Huang (

Re: [openstack-dev] [CLI][os-client-config][neutron] CLI option questions

I had written a fix for the particular --timeout issue here that prevents the client from parsing options beyond the subcommand: https://review.openstack.org/#/c/114005/ At the time I abandoned it since we figured it would be safer to just rename our HTTP timeout option to --http-timeout, but

[openstack-dev] [tricircle] weekly meeting of Jan.6

Hi, Let's have a weekly meeting for phase 2 of stateless design, meeting will be held at the UTC1300 at #openstack-meeting on Jan.6. Agenda: Progress of To-do list: https://etherpad.openstack.org/p/TricircleToDo Discussion of phase 2 of stateless design. Best Regards Chaoyi Huang (

[openstack-dev] [tricircle] play Tricircle with devstack

As the phase 1 of stateless design finished, now Tricircle could be played with devstack. Very limited functions for phase 1 were offered. Please visit https://github.com/openstack/tricircle/tree/experiment for how to do that. Welcome for bug-report, please register bug at

Re: [openstack-dev] [neutron] neutron-lib meetings canceled 12/23, 12/30

Nothing on the agenda for tomorrow, and many of us will be local next week, so let’s cancel this week, and resume next. Thanks, doug > On Dec 22, 2015, at 12:07 PM, Doug Wiegley > wrote: > > Happy holidays, see you all on 1/6. > > Thanks, > doug >

Re: [openstack-dev] [doc] DocImpact vs. reno

> On 6 Jan 2016, at 12:35 AM, Sean Dague wrote: > > On 01/04/2016 08:01 PM, Lana Brindley wrote: >> I’m late to this party because holidays (Thanks Anne for bringing it to >> my attention). >> >> First of all, sorry this came as a surprise. I tried hard to make sure >> everyone

Re: [openstack-dev] [kolla] Adding Ubuntu Liberty to Kolla-Mitaka

On 2016-01-05 20:01:13 + (+), Steven Dake (stdake) wrote: > I wish I could help you, but I have no idea how to add a new base > image to the infrastructure system. I know when I worked at Red > Hat, we had have a full time engineer work on it for 9 months > before Fedora was added. [...]

Re: [openstack-dev] [nova][cinder] Deprecating ConfKeyManager (fixed-key key manager)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Why would we not want to include a fixed-key backend in Castellan? As long as we make it clear that the fixed-key implementation is insecure and should not be used in production systems I see no harm in including it as part of the Castellan

Re: [openstack-dev] [cinder] oslo_config.PortOp is undefined

Thanks. Tried this. Still getting the same error on c-api installation. The pip upgrade shown some issues as follows: Installing collected packages: lxml, oslo.middleware, pyparsing, requests, python-keystoneclient, SQLAlchemy, urllib3 Found existing installation: lxml 3.3.3 Uninstalling

Re: [openstack-dev] [cinder] oslo_config.PortOp is undefined

Oops. sorry. I was as stack user. It works now (with a sudo). All the three cinder services are running. Thanks a ton for the help, Pradip On Tue, Jan 5, 2016 at 5:51 PM, Pradip Mukhopadhyay < pradip.inte...@gmail.com> wrote: > Thanks. Tried this. Still getting the same error on c-api

[openstack-dev] [CLI][os-client-config][neutron] CLI option questions

A series of os-client-config integration for neutronclient are proposed. Several questions hit me during reviewing https://review.openstack.org/#/c/242096. It is a review of neutroncleint, but I think it is generic to all CLIs. (1) global option vs command-specific option Various python-*client

[openstack-dev] [Senlin]deletion policy for cross-zones/regions

Hi all, I wrote some use cases on etherpad to summarize the deletion policy for cross-zones/regions. Welcome to join the discussion. https://etherpad.openstack.org/p/deletion_policy_for_cross_zone_region Best regards, xuhaiwei

Re: [openstack-dev] [nova][cinder]Detach a encrypted volume won't cleanup the device patch

Hi, For ISCSIConnector, the path can be recovered by rescan before disconnect_volume: https://github.com/openstack/os-brick/blob/master/os_brick/initiator/connector.py#L835 And for NFS volumes, it leads to following bug: https://bugs.launchpad.net/nova/+bug/1511255 Best wishes Lisa From:

Re: [openstack-dev] [doc] DocImpact vs. reno

On 2016-01-06 11:43:34 +1100 (+1100), Lana Brindley wrote: [...] > I’m starting to think that DocImpact needs to simply be retired then Alternatively, let the remaining projects which currently auto-open bugs for openstack-manuals switch to opening bugs against themselves and allow their bug