Re: [openstack-dev] [nova][glance][cinder][neutron]How to make use of x-openstack-request-id

At the Tokyo summit, there was a working session that addressed how to log the request-id chain. The etherpad for that is [0] A spec needs to be written and implementation details need some hashing out, but the approach should provide a way to track the originating request through each logged

Re: [openstack-dev] [Neutron][L3] Orphaned process cleanup

On Wed, Jan 27, 2016 at 05:06:03PM EST, Assaf Muller wrote: > >> RDO systemd init script for the L3 agent will send a signal 15 when > >> 'systemctl restart neutron-l3-agent' is executed. I assume > >> Debian/Ubuntu do the same. It is imperative that agent restarts do not > >> cause data plane

Re: [openstack-dev] [Neutron][L3] Orphaned process cleanup

On Wed, Jan 27, 2016 at 4:52 PM, Sean M. Collins wrote: > On Wed, Jan 27, 2016 at 04:24:00PM EST, Assaf Muller wrote: >> On Wed, Jan 27, 2016 at 4:10 PM, Sean M. Collins wrote: >> > Hi, >> > >> > I started poking a bit at

[openstack-dev] [keystone] changes to keystone-core!

Hello everyone! We've been talking about this for a long while, and I am very pleased to announce that at the midcycle we have made changes to keystone-core. The project has grown and our review queue grows ever longer. Effective immediately, we'd like to welcome the following new Guardians of

Re: [openstack-dev] Add TOSCA assets to the catalog

Our schema file is located here: http://git.openstack.org/cgit/openstack/app-catalog/tree/openstack_catalog/web/static/assets.schema.yaml We don't have a schema type defined for TOSCA assets yet. We should discuss the sorts of things that need to be listed so that the asset can be loaded into an

Re: [openstack-dev] [api] service type vs. project name for use in headers

What is the point of the guideline if we're not able to influence some of the biggest projects out there, that would keep growing with what they have.. Maybe we should add a note in each of those guidelines saying some examples exist where SERVICE_TYPE has been replaced by PROJECT_NAME for

Re: [openstack-dev] [app-catalog] Add TOSCA assets to the catalog

Great. Thank you so much Kevin and Steve!! I will try defining schema for TOSCA and update it for the review. Regards, Sahdev Zala From: "Fox, Kevin M" To: "OpenStack Development Mailing List (not for usage questions)" Date:

Re: [openstack-dev] Announcing Ekko -- Scalable block-based backup for OpenStack

On Wed, Jan 27, 2016 at 8:19 PM, Fausto Marzi wrote: > Hi Sam, > > After our conversation, I have few questions and consideration about Ekko, > mainly on how it works et similar. Also to make available to the community > our discussions: > > - In understand you

[openstack-dev] [app-catalog] App Catalog IRC Meeting CANCELLED this week

Due to scheduling conflicts and a very light agenda, there will be no Community App Catalog IRC meeting this week. Our next meeting is scheduled for February 4th, the agenda can be found here: https://wiki.openstack.org/wiki/Meetings/app-catalog One thing on the agenda for the 2/4/2016 meeting

[openstack-dev] [neutron] https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers

Is there any part of the cited wiki page that is still relevant?I've just been asked whether networking-calico (a backend project that I work on) should be listed there, and I think the answer is no because that page is out of date now. If that's right, could/should it be deleted? Thanks,

Re: [openstack-dev] [neutron] https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers

I'll kill it, as this should be superseded by the in-tree devref version. Thanks for pointing my attention to it. On 27 January 2016 at 23:40, Neil Jerram wrote: > Is there any part of the cited wiki page that is still relevant?I've just > been asked whether

Re: [openstack-dev] [Fuel][Plugins] Tasks ordering between plugins

Simon, you should use the deployment_tasks.yaml interface (which will likely eventually move to '*/tasks.yaml' (to mimic library) This uses the same task system as granular deploy. you can set task ordering between known tasks and roles names, in the case that they are not registered they will

Re: [openstack-dev] [Fuel][Plugins] Tasks ordering between plugins

On Jan 27, 2016 4:58 PM, "Andrew Woodward" wrote: > > Simon, you should use the deployment_tasks.yaml interface (which will likely eventually move to '*/tasks.yaml' (to mimic library) This uses the same task system as granular deploy. you can set task ordering between known

[openstack-dev] [Neutron][LBaaS][barbican]TLS container could not be found

Hi community, I was going through https://wiki.openstack.org/wiki/Network/LBaaS/docs/how-to-create-tls-loadbalancer with devstack. I was stuck at a point when I tried to create a listener within a loadbalancer with this command: neutron lbaas-listener-create --loadbalancer lb1 --protocol-port

[openstack-dev] [QA] Meeting Thursday January 28th at 9:00 UTC

Hello everyone, Please reminder that the weekly OpenStack QA team IRC meeting will be Thursday, Jan 28th at 9:00 UTC in the #openstack-meeting channel. The agenda for the meeting can be found here:

Re: [openstack-dev] [Neutron][L3] Orphaned process cleanup

On Wed, Jan 27, 2016 at 5:20 PM, Sean M. Collins wrote: > On Wed, Jan 27, 2016 at 05:06:03PM EST, Assaf Muller wrote: >> >> RDO systemd init script for the L3 agent will send a signal 15 when >> >> 'systemctl restart neutron-l3-agent' is executed. I assume >> >> Debian/Ubuntu

Re: [openstack-dev] [TripleO] spec-lite process for tripleo

On 01/27/2016 09:21 AM, Derek Higgins wrote: > Hi All, > > We briefly discussed feature tracking in this weeks tripleo meeting. I > would like to provide a way for downstream consumers (and ourselves) to > track new features as they get implemented. The main things that came > out of the

Re: [openstack-dev] [Neutron][LBaaS][Octavia] Should subnet be optional on member create?

I could see it being interesting, but that would have to be something vetted by other drivers and appliances because they may not support that. On Mon, 2016-01-25 at 21:37 +, Fox, Kevin M wrote: > We are using a neutron v1 lb that has external to the cloud members in a lb > used by a

[openstack-dev] [neutron][dvr]

Hi all, One basic question related to DVR topic '*dvr_update'*. In OVS Neutron agent, I see that the *dvr_update* topic is being added to the consumer list irrespective of DVR being enabled or not. Because of this, even though I have disabled DVR in my environment, I still see the agent subscribe

Re: [openstack-dev] [nova] Better tests for nova scheduler(esp. race conditions)?

Thank you Nikola! I'm very interested in this. According to my current understanding, a complete functional test for nova scheduler should include nova-api, the scheduler service, part of conductor service which forward scheduler decisions to compute services, and the part of compute service

Re: [openstack-dev] Announcing Ekko -- Scalable block-based backup for OpenStack

On 1/27/16, 12:06 PM, "Flavio Percoco" wrote: >On 27/01/16 12:16 -0500, Emilien Macchi wrote: >> >> >>On 01/27/2016 10:51 AM, Jay Pipes wrote: >>> On 01/27/2016 12:53 PM, gordon chung wrote: > It makes for a crappy user experience. Crappier than the crappy user >

Re: [openstack-dev] [keystone] changes to keystone-core!

Hi, Many thanks to everyone for your patient guidance and mentoring me in the past years! It's your help to make me grow up from a newbie! As a core project in OpenStack, keystone has grown to be several sub-projects, I strongly believe that we will continue to provide a stable/great

Re: [openstack-dev] [Neutron][LBaaS][Octavia] Should subnet be optional on member create?

If we take the approach do "download configuration for all v1 out of OpenStack, delete all v1 configuration and then, after lbaas v1 is removed and lbaas v2 is installed, use the data to recreate the items, this should be compatible to all drivers. No sure if such procedure will be accepted

Re: [openstack-dev] [keystone] changes to keystone-core!

Congratulations Samuel and Dave =) 2016-01-27 20:13 GMT-03:00 Steve Martinelli : > Hello everyone! > > We've been talking about this for a long while, and I am very pleased to > announce that at the midcycle we have made changes to keystone-core. The > project has grown and

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

> Okay, so I initially thought we weren't making much progress on this > discussion, but after some more thought and reading of the existing PoC, > we're (maybe?) less far apart than I initially thought. > > I think there are kind of three different designs being discussed. > > 1) Rewrite a

Re: [openstack-dev] [tricircle] Playing Tricircle with Devstack

Hi Jeo, This error occurred when installing devstack on node2. Best regards, Yipei On Wed, Jan 27, 2016 at 3:13 PM, Yipei Niu wrote: > > -- Forwarded message -- > From: Yipei Niu > Date: Tue, Jan 26, 2016 at 8:42 PM > Subject: Re:

Re: [openstack-dev] [Fuel][Bugs] Time sync problem when testing.

Yes, I have created custom iso with debug output. It didn't help, so another one with strace was created. On Jan 27, 2016 00:56, "Alex Schultz" wrote: > On Tue, Jan 26, 2016 at 2:16 PM, Stanislaw Bogatkin > wrote: > > When there is too high strata,

Re: [openstack-dev] [Nova] PCI CI is down

This bug and another related block bug: https://bugs.launchpad.net/nova/+bug/1536509 been merged recently, PCI-CI now is back online. Regards Yongli He -Original Message- From: Nikola Đipanov [mailto:ndipa...@redhat.com] Sent: Wednesday, January 20, 2016 10:41 PM To: OpenStack

Re: [openstack-dev] [kuryr] Does Kuryr support multi-tenant

Hi Vikas, > >The question is what you mean by multi-tenancy, if you mean that different > >tenants each control their own bare-metal > >server then Kuryr already support this. (by tenant credential configuration) > >I understand kuryr can configure with tenant credential, but we still need

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On Wed, 2016-01-27 at 09:36 -0500, Dan Prince wrote: > On Wed, 2016-01-27 at 14:32 +0100, Jiri Tomasek wrote: > > On 01/26/2016 09:05 PM, Ben Nemec wrote: > > > On 01/25/2016 04:36 PM, Dan Prince wrote: > > > > On Mon, 2016-01-25 at 15:31 -0600, Ben Nemec wrote: > > > > > On 01/22/2016 06:19 PM,

[openstack-dev] [neutron] no neutron lib meeting

Multiple cancels, and I'll be on a plane. Thanks, Doug __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

[openstack-dev] [TripleO] spec-lite process for tripleo

Hi All, We briefly discussed feature tracking in this weeks tripleo meeting. I would like to provide a way for downstream consumers (and ourselves) to track new features as they get implemented. The main things that came out of the discussion is that people liked the spec-lite process that

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

> On Wed, 2016-01-27 at 09:36 -0500, Dan Prince wrote: > > On Wed, 2016-01-27 at 14:32 +0100, Jiri Tomasek wrote: > > > On 01/26/2016 09:05 PM, Ben Nemec wrote: > > > > On 01/25/2016 04:36 PM, Dan Prince wrote: > > > > > On Mon, 2016-01-25 at 15:31 -0600, Ben Nemec wrote: > > > > > > On 01/22/2016

[openstack-dev] [release][neutron] networking-sfc release 1.0.0 (independent)

We are overjoyed to announce the release of: networking-sfc 1.0.0: API's and implementations to support Service Function Chaining in Neutron. This release is part of the independent release series. With source available at: http://git.openstack.org/cgit/openstack/networking-sfc With

[openstack-dev] [all] [Ironic] New project: Ironic Staging Drivers

Hi, I would like to quickly announce the creation of a new project called Ironic Staging Drivers. What the Ironic Staging Drivers project is? - As context, in the Tokyo design summit it was decided that drivers in the Ironic tree will

Re: [openstack-dev] [Fuel][library] Switching to external fixtures for integration Noop tests

On 26.01.2016 22:18, Kyrylo Galanov wrote: > Hello Bogdan, > > I hope I am not the one of the context. Why do we separate fixtures for > Noop tests from the repo? > I can understand if while noop test block was carried out to a separate > repo. > I believe fixtures normally are downloaded by

Re: [openstack-dev] Announcing Ekko -- Scalable block-based backup for OpenStack

On 01/27/2016 12:53 PM, gordon chung wrote: It makes for a crappy user experience. Crappier than the crappy user experience that OpenStack API users already have because we have done a crappy job shepherding projects in order to make sure there isn't overlap between their APIs (yes, Ceilometer

Re: [openstack-dev] [nova] do not account compute resource of instances in state SHELVED_OFFLOADED

Hi Andrew, Am 27.01.2016 um 10:38 schrieb Andrew Laski: > 1. This allows for a poor experience where a user would not be able to > turn on and use an instance that they already have due to overquota. > This is a change from the current behavior where they just can't create > resources, now

Re: [openstack-dev] [Fuel][Bugs] Time sync problem when testing.

I've got proposal from mos-linux team about switch to sntp instead of ntpdate due to ntpdate deprecation. It looks nice enough for me but we already had similar problems with sntp before switching to ntpdate. Does anyone vote against switching to sntp? On Wed, Jan 27, 2016 at 2:25 PM, Maksim

Re: [openstack-dev] [nova][neutron] Update on Neutron's rolling upgrade support?

Thanks very much for the update, Ihar, much appreciated! On 01/26/2016 01:19 PM, Ihar Hrachyshka wrote: Jay Pipes wrote: Hey Sean, Tomorrow morning UTC, we'll be discussing Neutron topics at the Nova mid-cycle. Wondering if you might give us a quick status update on

[openstack-dev] Fuel 9.0 (Mitaka) deployment with Ubuntu UCA packages

Hi Fuelers and Stackers, I am pleased to announce the first possibility to deploy Mitaka using Fuel as a deployment tool. I am taking advantage of Alex Schultz's plugin, fuel-plugin-upstream[0], along with a series of patches currently on review[1]. I have not had a chance to do destructive tests

Re: [openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

So, metrics are grouped by the type of resource they use, and each metric has to be listed. Grouping isn't a problem, but creating an exhaustive list might be, since there are 100+ plugins [1] in collectd which can provide statistics, although not all of these are useful, and some require

Re: [openstack-dev] [TaskFlow] TaskFlow persistence

Hi, Thanks for the responses. Putting it in a small example def flow_factory(tmp): return lf.Flow('resume from backend example').add( TestTask(name='first', test=tmp), InterruptTask(name='boom'), TestTask(name='second', test="second task")) class

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On 01/27/2016 03:36 PM, Dan Prince wrote: On Wed, 2016-01-27 at 14:32 +0100, Jiri Tomasek wrote: On 01/26/2016 09:05 PM, Ben Nemec wrote: On 01/25/2016 04:36 PM, Dan Prince wrote: On Mon, 2016-01-25 at 15:31 -0600, Ben Nemec wrote: On 01/22/2016 06:19 PM, Dan Prince wrote: On Fri,

Re: [openstack-dev] OpenStack installer

As someone that has upgraded rdo clouds on multiple occasions, I concur. Its way easier to upgrade a whole cloud, (or even pieces of a cloud are possible) with properly isolated containers instead of rpms. Thats the case where containers really shine, and you don't experience it until you try

Re: [openstack-dev] Announcing Ekko -- Scalable block-based backup for OpenStack

On 01/27/2016 10:51 AM, Jay Pipes wrote: > On 01/27/2016 12:53 PM, gordon chung wrote: >>> It makes for a crappy user experience. Crappier than the crappy user >>> experience that OpenStack API users already have because we have done a >>> crappy job shepherding projects in order to make sure

Re: [openstack-dev] [devstack][tempest] RuntimeError: no suitable implementation for this system thrown by monotonic.py

This appears to have gone away this morning. I ran clean.sh and removed monotonic. The next run of stack.sh installed version 0.6 of monotonic and I no longer see this exception. Bob Hansen z/VM OpenStack Enablement From: Bob Hansen/Endicott/IBM@IBMUS To: "openstack-dev"

Re: [openstack-dev] Announcing Ekko -- Scalable block-based backup for OpenStack

On 27/01/2016 10:51 AM, Jay Pipes wrote: > On 01/27/2016 12:53 PM, gordon chung wrote: >>> It makes for a crappy user experience. Crappier than the crappy user >>> experience that OpenStack API users already have because we have done a >>> crappy job shepherding projects in order to make sure

Re: [openstack-dev] [oslo] Allow YAML config

Vladislav Kuzmin said on Tue, Dec 15, 2015 at 04:26:32PM +0300: > I want to specify all my option in yaml file, because it is much more > readable. But I must use ini file, because oslo.log using > logging.config.fileConfig for reading the config file ( >

Re: [openstack-dev] [openstack-ansible] LBaaSv2 / Octavia support

+1 on sharing/outlining migration script form v1 to v2. It will help lot of teams. Thanks, Vivek On 1/26/16, 6:58 PM, "Kevin Carter" wrote: >I know that Neutron LBaaS V1 is still available in Liberty and functional, and >at this point I assume its in Mitaka

Re: [openstack-dev] glance community image visibility blue print

On 27/01/16 11:02 -0800, Su Zhang wrote: Hello everyone, I created another BP for Newton release regarding glance community image visibility based on Louis Taylor's original BP. I will continue working on feature. Before I upload our implementation, it will be wonderful if anyone in glance

Re: [openstack-dev] Announcing Ekko -- Scalable block-based backup for OpenStack

On 27/01/16 12:16 -0500, Emilien Macchi wrote: On 01/27/2016 10:51 AM, Jay Pipes wrote: On 01/27/2016 12:53 PM, gordon chung wrote: It makes for a crappy user experience. Crappier than the crappy user experience that OpenStack API users already have because we have done a crappy job

Re: [openstack-dev] [TaskFlow] TaskFlow persistence

pn kk wrote: Hi, Thanks for the responses. Putting it in a small example def flow_factory(tmp): return lf.Flow('resume from backend example').add( TestTask(name='first', test=tmp), InterruptTask(name='boom'), TestTask(name='second', test="second task")) class

[openstack-dev] glance community image visibility blue print

Hello everyone, I created another BP for Newton release regarding glance community image visibility based on Louis Taylor's original BP. I will continue working on feature. Before I upload our implementation, it will be wonderful if anyone in glance community can review and approve the BP. It

[openstack-dev] [all][infra] Impact of HPE Helion Public Cloud Sunset on OpenStack Infrastructure

The HPE Helion Public Cloud is one of several OpenStack public clouds that generously donate compute, network, and storage resources to power the OpenStack Developer Infrastructure. As you may know, HPE is sunsetting the HPE Helion Public Cloud on January 31st 2016[1]. Use of HPE Helion Public

[openstack-dev] [puppet] Stepping down from Puppet Core

Hi, I would like to ask to be removed from the core reviewers team on the Puppet for OpenStack project. My day to day tasks and focus no longer revolve solely around Puppet and I lack dedicated time to contribute to the project. In the past months, I stopped actively reviewing changes compared

Re: [openstack-dev] [api] service type vs. project name for use in headers

On Wed, Jan 27, 2016 at 1:47 PM, michael mccune wrote: > i am not convinced that we would ever need to have a standard on how these > names are chosen for the header values, or if we would even need to have > header names that could be deduced. for me, it would be much better

Re: [openstack-dev] [puppet] Stepping down from Puppet Core

On 01/27/2016 03:13 PM, Mathieu Gagné wrote: > Hi, > > I would like to ask to be removed from the core reviewers team on the > Puppet for OpenStack project. > > My day to day tasks and focus no longer revolve solely around Puppet and > I lack dedicated time to contribute to the project. > >

[openstack-dev] [neutron] documenting configuration option segregation between services and agents

We should expand services_and_agents devref to describe how and why configuration options should be segregated between services and agents. I stumbled into this recently while trying to remove a confusing duplicate configuration option [1][2][3]. The present separation appears to be 'tribal

Re: [openstack-dev] [all][infra] Impact of HPE Helion Public Cloud Sunset on OpenStack Infrastructure

On 27/01/16 14:26 -0500, Cody A.W. Somerville wrote: The HPE Helion Public Cloud is one of several OpenStack public clouds that generously donate compute, network, and storage resources to power the OpenStack Developer Infrastructure. As you may know, HPE is sunsetting the HPE Helion Public

[openstack-dev] [api] service type vs. project name for use in headers

hi all, there have been a few reviews recently where the issue of service type versus project name have come up for use in the headers. as usual this conversation can get quite murky as there are several good examples where service type alone is not sufficient (for example if a service

Re: [openstack-dev] Announcing Ekko -- Scalable block-based backup for OpenStack

On Wed, Jan 27, 2016 at 7:06 PM, Flavio Percoco wrote: > > FWIW, the current governance model does not prevent competition. That's > not to > be understood as we encourage it but rather than there could be services > with > some level of overlap that are still worth being

Re: [openstack-dev] Announcing Ekko -- Scalable block-based backup for OpenStack

Hi Sam, After our conversation, I have few questions and consideration about Ekko, mainly on how it works et similar. Also to make available to the community our discussions: - In understand you are placing a backup-agent on the compute node and execute actions interacting directly with

Re: [openstack-dev] [puppet] Stepping down from Puppet Core

Mathieu, Thank you for all the work you've done over the past few years in this community. You've done a lot and also done a lot to help answer questions and mentor new folks. On Wed, Jan 27, 2016 at 1:13 PM, Mathieu Gagné wrote: > Hi, > > I would like to ask to be removed

Re: [openstack-dev] [api] service type vs. project name for use in headers

On 01/27/2016 03:31 PM, Dean Troyer wrote: On Wed, Jan 27, 2016 at 1:47 PM, michael mccune > wrote: i am not convinced that we would ever need to have a standard on how these names are chosen for the header values, or if we would even need to

[openstack-dev] [puppet] enable voting for integration jobs

Hi, Puppet OpenStack Integration jobs [1] have been here for some months. It seems like they're pretty stable when rubygems or EPEL is not down ;-) I'm sure it will fail from time to time, like other jobs but 'recheck' will do the job if we need to kick-off another run. We might want to enable

[openstack-dev] [Neutron][L3] Orphaned process cleanup

Hi, I started poking a bit at https://bugs.launchpad.net/devstack/+bug/1535661 We have radvd processes that the l3 agent launches, and if the l3 agent is terminated these radvd processes continue to run. I think we should probably terminate them when the l3 agent is terminated, like if we are in

Re: [openstack-dev] [glance][ironic][cinder][nova] 'tar' as an image disk_format

Hi Flavio, On Wed, Jan 27, 2016 at 4:50 AM, Flavio Percoco wrote: > [snip] > However, as a community, I think we should send a clear message and protect > our users and, in this case, the best way > is to avoid adding this format as supported. > To address some of the

[openstack-dev] [app-catalog] Add TOSCA assets to the catalog

Hello, I am looking at this blueprint https://blueprints.launchpad.net/app-catalog/+spec/add-tosca-assets and confused about the first task, "define metadata for TOSCA assets"? Can someone please provide example of metadata for previous work on Heat and Murano? I tried to find some old patch

Re: [openstack-dev] [app-catalog] Add TOSCA assets to the catalog

- Original Message - > From: "Sahdev P Zala" > To: "OpenStack Development Mailing List (not for usage questions)" > > > Hello, > > I am looking at this blueprint > https://blueprints.launchpad.net/app-catalog/+spec/add-tosca-assets

Re: [openstack-dev] [puppet] Stepping down from Puppet Core

On Wed, Jan 27, 2016 at 12:35 PM, Emilien Macchi wrote: > > > On 01/27/2016 03:13 PM, Mathieu Gagné wrote: > > Hi, > > > > I would like to ask to be removed from the core reviewers team on the > > Puppet for OpenStack project. > > > > My day to day tasks and focus no longer

Re: [openstack-dev] [Neutron][L3] Orphaned process cleanup

On Wed, Jan 27, 2016 at 4:10 PM, Sean M. Collins wrote: > Hi, > > I started poking a bit at https://bugs.launchpad.net/devstack/+bug/1535661 > > We have radvd processes that the l3 agent launches, and if the l3 agent > is terminated these radvd processes continue to run. I

Re: [openstack-dev] [TripleO] spec-lite process for tripleo

On Wed, 2016-01-27 at 16:21 +, Derek Higgins wrote: > Hi All, > > We briefly discussed feature tracking in this weeks tripleo meeting. > I  > would like to provide a way for downstream consumers (and ourselves) > to  > track new features as they get implemented. The main things that > came  >

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

Jamie At the Nova mid-cycle and John Garbutt suggested I reach out to you again to progress this issue. Thanks On 05/01/16 10:05, 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

Re: [openstack-dev] [Neutron][L3] Orphaned process cleanup

On Wed, Jan 27, 2016 at 04:24:00PM EST, Assaf Muller wrote: > On Wed, Jan 27, 2016 at 4:10 PM, Sean M. Collins wrote: > > Hi, > > > > I started poking a bit at https://bugs.launchpad.net/devstack/+bug/1535661 > > > > We have radvd processes that the l3 agent launches, and if

Re: [openstack-dev] OpenStack installer

Hello Gyorgy, Few more responses inline: On 01/27/2016 02:51 AM, Gyorgy Szombathelyi wrote: >> >> Hi Gyorgy, >> > Hi Kevin, > >> I'll definitely give this a look and thanks for sharing. I would like to ask >> however why you found OpenStack-Anisble overly complex so much so that >> you've taken

Re: [openstack-dev] [TripleO] changes in irc alerts

On Tue, Jan 26, 2016 at 7:15 PM, Derek Higgins wrote: > Hi All, > > For the last few months we've been alerting the #tripleo irc channel when > a card is open on the tripleo trello org, in the urgent list. > > When used I think it served a good purpose to alert people to the

Re: [openstack-dev] [Nova][Cinder] Cleanly detaching volumes from failed nodes

On 1/26/2016 5:55 AM, Avishay Traeger wrote: OK great, thanks! I added a suggestion to the etherpad as well, and found this link helpful: https://review.openstack.org/#/c/266095/ On Tue, Jan 26, 2016 at 1:37 AM, D'Angelo, Scott > wrote:

Re: [openstack-dev] [Nova][Cinder] Cleanly detaching volumes from failed nodes

On Wed, Jan 27, 2016 at 1:01 PM, Matt Riedemann wrote: > I've replied on https://review.openstack.org/#/c/266095/ and the related > cinder change https://review.openstack.org/#/c/272899/ which are adding a > new key to the volume connector dict being passed around

Re: [openstack-dev] [Fuel][Bugs] Time sync problem when testing.

I think we shouldn't depend on the other services like Syslog and logger trying to catch the problem and it is better to create the logs ourselves. On Wed, Jan 27, 2016 at 1:49 PM, Stanislaw Bogatkin wrote: > >But you've used 'logger -t ntpdate' - this is can fail again

Re: [openstack-dev] [fuel][plugins] Detached components plugin update requirement

I see no follow-up to Swann's question so let me elaborate why this issue is important for the LMA plugins. First I need to explain what was our release schedule for the LMA plugins during the MOS 7.0 cycle: - New features were done on the master branch which was only compatible with MOS 7.0. -

Re: [openstack-dev] [oslo] Sachi King for oslo core

Thanks for the vote of confidence all, I look forward to expanding what I'm working on. Cheers, Sachi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [glance] Glance Core team additions/removals

I'm always happy to add new cores :) +1 for Kairat. He has been working really hard and the huge number of high-quality reviews and commits is a good proof of this. Welcome Kairat! +1 for Brian. He is one of the most experienced technical specialists and he's a well-known member in the

Re: [openstack-dev] [nova][glance][cinder][neutron]How to make use of x-openstack-request-id

On Wed, Jan 27, 2016, at 05:47 AM, Kuvaja, Erno wrote: > > -Original Message- > > From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] > > Sent: Wednesday, January 27, 2016 9:56 AM > > To: openstack-dev@lists.openstack.org > > Subject: Re: [openstack-dev]

Re: [openstack-dev] [Nova][Cinder] Cleanly detaching volumes from failed nodes

On 1/27/2016 11:22 AM, Avishay Traeger wrote: On Wed, Jan 27, 2016 at 1:01 PM, Matt Riedemann > wrote: I've replied on https://review.openstack.org/#/c/266095/ and the related cinder change

Re: [openstack-dev] [nova][glance][cinder][neutron]How to make use of x-openstack-request-id

> -Original Message- > From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] > Sent: Wednesday, January 27, 2016 9:56 AM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [nova][glance][cinder][neutron]How to make > use of x-openstack-request-id > > > > On

Re: [openstack-dev] OpenStack installer

> On 01/26/2016 11:32 AM, Gyorgy Szombathelyi wrote: > > Hello! > > > > I just want to announce a new installer for OpenStack: > > https://github.com/DoclerLabs/openstack > > It is GPLv3, uses Ansible (currently 1.9.x, 2.0.0.2 has some bugs which has > to be resolved), has lots of components

Re: [openstack-dev] [nova] Feature suggestion - API for creating VM without powering it up

Looks like we can use user_data and cloud-init to do this stuff. Adding the following content into user_data.txt and launch instance like this: nova boot --user-data user_data.txt ..., the instance will shutdown after boot is finished. power_state: mode: poweroff message: Bye Bye You can find

Re: [openstack-dev] [tricircle] Playing Tricircle with Devstack

Hi, Yipei, The issue is still caused by the change in DevStack. When the command "openstack volume type create --property volume_backend_name=lvmdriver-1 lvmdriver-1" is executed in DevStack, the exported region name (i.e, RegionOne) is used, so the request was sent to RegionOne, but the

Re: [openstack-dev] [ceilometer] :Regarding wild card configuration in pipeline.yaml

Hi Gord, Could you please kindly suggest how to proceed further on the below issue as we are somewhat blocked in our development activity due to the wildcard issue. With Best Regards Raghunath Dudyala Tata Consultancy Services Limited Mailto: raghunat...@tcs.com Website: http://www.tcs.com

Re: [openstack-dev] [nova] do not account compute resource of instances in state SHELVED_OFFLOADED

On Tue, Jan 26, 2016, at 07:46 AM, Christian Berendt wrote: > After offloading a shelved instance the freed compute resources are > still accounted. > > I think it makes sense to make this behavior configurable. We often have > the request to not account the freed compute resources after an

[openstack-dev] [midonet] Re: Classifiers for MN's Service Chaining API

> the API has L2Insertions that each have a position. The current API > therefore only expects a single list of L2Insertions on a single VM. It > seems wrong to attach classifiers to the L2Insertion object... on the other > hand, since the model assumes the Service Function leaves the traffic >

Re: [openstack-dev] [Fuel][Bugs] Time sync problem when testing.

But you've used 'logger -t ntpdate' - this is can fail again and logs can be empty again. My opinion we should use output redirection to the log-file directly. On Wed, Jan 27, 2016 at 11:21 AM, Stanislaw Bogatkin wrote: > Yes, I have created custom iso with debug

Re: [openstack-dev] [nova][glance][cinder][neutron]How to make use of x-openstack-request-id

On 1/27/2016 9:40 AM, Tan, Lin wrote: Thank you so much. Eron. This really helps me a lot!! Tan *From:*Kuvaja, Erno [mailto:kuv...@hpe.com] *Sent:* Tuesday, January 26, 2016 8:34 PM *To:* OpenStack Development Mailing List (not for usage questions) *Subject:* Re: [openstack-dev]

Re: [openstack-dev] [Fuel][Bugs] Time sync problem when testing.

>But you've used 'logger -t ntpdate' - this is can fail again and logs can be empty again. What do you mean by 'fall again'? Piping to logger uses standard blocking I/O - logger gets all the output it can reach, so it get all output strace will produce. If ntpdate will hang for some reason - we

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

> -Original Message- > From: Flavio Percoco [mailto:fla...@redhat.com] > Sent: Monday, January 25, 2016 3:07 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on > the > idea to move it forward > > On 20/01/16 13:23

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On Tue, 2016-01-26 at 14:05 -0600, Ben Nemec wrote: > On 01/25/2016 04:36 PM, Dan Prince wrote: > > On Mon, 2016-01-25 at 15:31 -0600, Ben Nemec wrote: > > > On 01/22/2016 06:19 PM, Dan Prince wrote: > > > > On Fri, 2016-01-22 at 11:24 -0600, Ben Nemec wrote: > > > > > So I haven't weighed in on

Re: [openstack-dev] [Nova][Cinder] Cleanly detaching volumes from failed nodes

On 27 January 2016 at 06:40, Matt Riedemann wrote: > On 1/27/2016 11:22 AM, Avishay Traeger wrote: > >> >> I agree with you. Actually, I think it would be more correct to have >> Cinder store it, and not pass it at all to terminate_connection(). >> >> > That would be

Re: [openstack-dev] [oslo] Sachi King for oslo core

Yay Sachi! On Jan 27, 2016 05:01, "Sachi King" wrote: > Thanks for the vote of confidence all, I look forward to expanding > what I'm working on. > > Cheers, > Sachi > > __ > OpenStack Development Mailing

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On 26 January 2016 at 16:01, Ben Nemec wrote: > On 01/26/2016 03:46 AM, Steven Hardy wrote: > > On Mon, Jan 25, 2016 at 05:45:30PM -0600, Ben Nemec wrote: > >> On 01/25/2016 03:56 PM, Steven Hardy wrote: > >>> On Fri, Jan 22, 2016 at 11:24:20AM -0600, Ben Nemec wrote: >

  1   2   >