[openstack-dev] [nova] nova boot from image created volume

Hello, If we use nova boot from image and created volume, i think the nova will use volume/cinder.py:create to create volume. But after insert pdb, i do not find the specific code of line to call the create. Can someone help me to point out the code of the line? Thanks a lot.

Re: [openstack-dev] [Openstack] How to get all detail RPC message and detail context in neutron docs?

Thank you, use debug option will also help us to get detail of RPC message, good luck~ 2017-04-06 14:20 GMT+08:00 김기석 [Kiseok Kim] : > Sam, > > > > I have no idea whether or not the document exists. (I want to read too) > > > > about L3 RPC messages(L3_AGENT topic), its client-side is implemented

Re: [openstack-dev] [tripleo] pingtest vs tempest

HI, I think Rally or Browbeat and other performance oriented solutions won't serve our needs, because we run TripleO CI on virtualized environment with very limited resources. Actually we are pretty close to full utilizing these resources when deploying openstack, so very little is available for t

Re: [openstack-dev] [nova] Risk prediction model for OpenStack

林泽燕 wrote: > Dear everyone, > > My name is Zoey Lin, majored in Computer Science, Peking University, > China. I’m a candidate of Master Degree. Recently I'm making a research > on OpenStack about the contribution composition of a code file, to > predict the potential amount of defect that the file

Re: [openstack-dev] [tripleo] pingtest vs tempest

On 04/05/2017 10:49 PM, Emilien Macchi wrote: Greetings dear owls, I would like to bring back an old topic: running tempest in the gate. == Context Right now, TripleO gate is running something called pingtest to validate that the OpenStack cloud is working. It's an Heat stack, that deploys a N

[openstack-dev] [tripleo] Proposing Florian Fuchs for tripleo-validations core

Hellooo, I'd like to propose we extend Florian Fuchs +2 powers to the tripleo-validations project. Florian is already core on tripleo-ui (well, tripleo technically so this means there is no changes to make to gerrit groups). Florian took over many of the stalled patches in tripleo-validations and

Re: [openstack-dev] [tripleo] pingtest vs tempest

Sagi, I think Rally or Browbeat and other performance oriented solutions won't > serve our needs, because we run TripleO CI on virtualized environment with > very limited resources. Actually we are pretty close to full utilizing > these resources when deploying openstack, so very little is availab

Re: [openstack-dev] [tripleo] Roadmap for Container CI work

On 4.4.2017 22:01, Emilien Macchi wrote: After our weekly meeting of today, I found useful to share and discuss our roadmap for Container CI jobs in TripleO. They are ordered by priority from the highest to lowest: 1. Swap ovb-nonha job with ovb-containers, enable introspection on the container

Re: [openstack-dev] [tripleo] pingtest vs tempest

On Thu, Apr 6, 2017 at 5:32 AM, Sagi Shnaidman wrote: > HI, > > I think Rally or Browbeat and other performance oriented solutions won't > serve our needs, because we run TripleO CI on virtualized environment with > very limited resources. Actually we are pretty close to full utilizing these > res

Re: [openstack-dev] [tripleo] Proposing Florian Fuchs for tripleo-validations core

On 6.4.2017 11:53, Martin André wrote: Hellooo, I'd like to propose we extend Florian Fuchs +2 powers to the tripleo-validations project. Florian is already core on tripleo-ui (well, tripleo technically so this means there is no changes to make to gerrit groups). Florian took over many of the s

Re: [openstack-dev] [tripleo] Proposing Florian Fuchs for tripleo-validations core

On 6 April 2017 at 10:53, Martin André wrote: > Hellooo, > > I'd like to propose we extend Florian Fuchs +2 powers to the > tripleo-validations project. Florian is already core on tripleo-ui > (well, tripleo technically so this means there is no changes to make > to gerrit groups). > > Florian too

[openstack-dev] [openstack-doc] Docs team meeting

Hey everyone, The docs meeting will continue today in #openstack-meeting-alt as scheduled (Thursday at 21:00 UTC). For more details, and the agenda, see the meeting page: - https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_meeting The meeting with be hosted by Joseph Robi

Re: [openstack-dev] [tripleo] pingtest vs tempest

On Thu, 6 Apr 2017, Sagi Shnaidman wrote: It may be useful to run a "limited edition" of API tests that maximize coverage and don't duplicate, for example just to check service working basically, without covering all its functionality. It will take very little time (i.e. 5 tests for each service

[openstack-dev] [tripleo] Consistent way of integrating services with different backends

Hi owls! This is something that I've been discussing in the IRC channel but still I think we should define a consistent way of integrating services which support different backends. In this case, I'm refering to BGPVPN and L2GW Neutron services, but it could be applied to any other type of service

Re: [openstack-dev] [tripleo] pingtest vs tempest

Maybe I'm getting a little off topic with this question, but why was Tempest removed last time? I'm not well versed in the history of this discussion, but from what I understand Tempest in the gate has been an off and on again thing for a while but I've never heard the story of why it got removed.

Re: [openstack-dev] [QA][intel-nfv-ci-tests][octavia][tap-as-a-service][vmware-nsx][networking-sfc] Refactor of Tempest scenario base classes

One final status update on this. We will proceed now with refactoring the tempest scenario base class. - 17 patches merged - 3 patches ready (on master) - 3 patches ready (on stable branches) - 3 extra patches for data_utils Details: https://etherpad.openstack.org/p/tempest-manager-plugins andre

Re: [openstack-dev] [tripleo] pingtest vs tempest

Having tempest running will allow these jobs to appear in openstack-health system as well. On Thu, Apr 6, 2017 at 1:29 PM, Justin Kilpatrick wrote: > Maybe I'm getting a little off topic with this question, but why was > Tempest removed last time? > > I'm not well versed in the history of this d

Re: [openstack-dev] [tripleo] pingtest vs tempest

On Thursday, 6 April 2017 13:29:32 CEST Justin Kilpatrick wrote: > Maybe I'm getting a little off topic with this question, but why was > Tempest removed last time? > > I'm not well versed in the history of this discussion, but from what I > understand Tempest in the gate has > been an off and on

Re: [openstack-dev] [tripleo] Roadmap for Container CI work

On 6.4.2017 12:46, Jiří Stránský wrote: On 4.4.2017 22:01, Emilien Macchi wrote: After our weekly meeting of today, I found useful to share and discuss our roadmap for Container CI jobs in TripleO. They are ordered by priority from the highest to lowest: 1. Swap ovb-nonha job with ovb-container

[openstack-dev] Emails for OpenStack R Release Name voting going out - please be patient

Hey all! I've started the R Release Name poll and currently am submitting everyone's email address to the system. In order to not make our fine friends at Carnegie Mellon (the folks who run the CIVS voting service) upset, I have a script that submits the emails one at a time with a half-secon

Re: [openstack-dev] [tripleo] pingtest vs tempest

I don't really have much context in what the decision is going to be based on here, so I'll just add some random comments here and there. On Thu, Apr 6, 2017 at 12:48 PM Arx Cruz wrote: > Having tempest running will allow these jobs to appear in openstack-health > system as well. > I agree that

Re: [openstack-dev] [tripleo] Consistent way of integrating services with different backends

I think the answer here should be if we want to define environment files as a whole “With all the information required to deploy something functional” or composing them like a LEGO (which might not work separately). I don't have a strong opinion about it, but I'm inclined to use them as functiona

Re: [openstack-dev] [tripleo] pingtest vs tempest

I would say smoke tests, and at least the minimum scenario tests. Smoke tests takes 14 minutes (113 tests) to run, and I can check how long it takes the minimum scenario tests later. So it won't take a long time running. Kind regards, Arx Cruz On Thu, Apr 6, 2017 at 2:44 PM, Andrea Frittoli wrot

Re: [openstack-dev] [tripleo] Proposing Florian Fuchs for tripleo-validations core

+1 On Thu, Apr 6, 2017 at 12:56 PM, Julie Pichon wrote: > On 6 April 2017 at 10:53, Martin André wrote: > > Hellooo, > > > > I'd like to propose we extend Florian Fuchs +2 powers to the > > tripleo-validations project. Florian is already core on tripleo-ui > > (well, tripleo technically so this

Re: [openstack-dev] [tripleo] Consistent way of integrating services with different backends

On Thu, 2017-04-06 at 13:07 +0200, Ricardo Noriega De Soto wrote: > Hi owls! > > This is something that I've been discussing in the IRC channel but > still I > think we should define a consistent way of integrating services which > support different backends. In this case, I'm refering to BGPVPN a

Re: [openstack-dev] [tripleo] pingtest vs tempest

On Wed, Apr 5, 2017 at 4:49 PM, Emilien Macchi wrote: > Greetings dear owls, > > I would like to bring back an old topic: running tempest in the gate. > > == Context > > Right now, TripleO gate is running something called pingtest to > validate that the OpenStack cloud is working. It's an Heat st

Re: [openstack-dev] [tripleo] Proposing Florian Fuchs for tripleo-validations core

On 04/06/2017 07:00 AM, Jiri Tomasek wrote: > +1 > > On Thu, Apr 6, 2017 at 12:56 PM, Julie Pichon wrote: > > > On 6 April 2017 at 10:53, Martin André wrote: > >> Hellooo, > >> > >> I'd like to propose we extend Florian Fuchs +2 powers to the > >> tripleo-validations project. Florian is already c

[openstack-dev] [cinder][nova] Cinder-Nova API meeting time slot change

Hi All, As of __today__ the Cinder-Nova API interactions meeting has a new time slot, __1600 UTC__. The meeting channel is the same: __#openstack-meeting-cp__. The patch [1] to change the slot officially is still under review with no conflicts. See you soon! Thanks and Best Regards, Ildikó

Re: [openstack-dev] [tripleo] Proposing Florian Fuchs for tripleo-validations core

I tripleo-validate that! OK the joke was poor. +1 otherwise :-) Nice contributions from Florian, fully deserved. On Thu, Apr 6, 2017 at 10:18 AM, Jason E. Rist wrote: > On 04/06/2017 07:00 AM, Jiri Tomasek wrote: >> +1 >> >> On Thu, Apr 6, 2017 at 12:56 PM, Julie Pichon wrote: >> >> > On 6 Apr

Re: [openstack-dev] [tripleo] pingtest vs tempest

On 06/04/17 12:32 +0300, Sagi Shnaidman wrote: HI, I think Rally or Browbeat and other performance oriented solutions won't serve our needs, because we run TripleO CI on virtualized environment with very limited resources. Actually we are pretty close to full utilizing these resources when deplo

Re: [openstack-dev] [tripleo] Proposing Florian Fuchs for tripleo-validations core

+1 On Thu, Apr 06, 2017 at 11:53:04AM +0200, Martin André wrote: > Hellooo, > > I'd like to propose we extend Florian Fuchs +2 powers to the > tripleo-validations project. Florian is already core on tripleo-ui > (well, tripleo technically so this means there is no changes to make > to gerrit grou

Re: [openstack-dev] [tripleo] Consistent way of integrating services with different backends

I think the option 1) is a better choice. Since: 1. The api and agent talk through RPC. So it is unnecessarily to have both the api and agent service on the same node. Separate composable service is more appropriate here. 2. In the l2gw_plugin.ini file, it suggests that the service_provider could h

Re: [openstack-dev] [nova] nova boot from image created volume

jaypipes@serialcoder:~/src/git.openstack.org/openstack/nova/nova$ ack-grep --ignore-dir tests --ignore-dir locale "volume_api.create" compute/api.py 2982:snapshot = self.volume_api.create_snapshot_force( api/openstack/compute/volumes.py 185:new_volume = self.volume_ap

Re: [openstack-dev] [oslo][requirements][designate][cinder] Reverting eventlet version bump

On 04/04/17 11:11 -0700, Clint Byrum wrote: Excerpts from Monty Taylor's message of 2017-04-04 12:19:36 -0500: On 04/04/2017 09:19 AM, Jay S Bryant wrote: > Monty, > > I agree with your approach. Think we should not break other projects > with a change like this and the answer thus far has been

[openstack-dev] [fuel] Weekly meeting April 6th is cancelled

Fuelers Agenda is empty for today, so the meeting is cancelled. -- Yours Faithfully, Vladimir Kuklin, Fuel Library Tech Lead, Mirantis, Inc. +7 (495) 640-49-04 +7 (926) 702-39-68 Skype kuklinvv 35bk3, Vorontsovskaya Str. Moscow, Russia, www.mirantis.com www.mirantis.ru

Re: [openstack-dev] [nova] nova boot from image created volume

On 4/6/2017 10:05 AM, Jay Pipes wrote: jaypipes@serialcoder:~/src/git.openstack.org/openstack/nova/nova$ ack-grep --ignore-dir tests --ignore-dir locale "volume_api.create" compute/api.py 2982:snapshot = self.volume_api.create_snapshot_force( api/openstack/compute/volumes.py 185:

Re: [openstack-dev] [tripleo] Proposing Florian Fuchs for tripleo-validations core

On 04/06/2017 11:53 AM, Martin André wrote: Hellooo, I'd like to propose we extend Florian Fuchs +2 powers to the tripleo-validations project. Florian is already core on tripleo-ui (well, tripleo technically so this means there is no changes to make to gerrit groups). Florian took over many of

Re: [openstack-dev] [tripleo] Proposing Florian Fuchs for tripleo-validations core

+1 On 2017-04-06 11:53, Martin André wrote: > Hellooo, > > I'd like to propose we extend Florian Fuchs +2 powers to the > tripleo-validations project. Florian is already core on tripleo-ui > (well, tripleo technically so this means there is no changes to make > to gerrit groups). > > Florian too

Re: [openstack-dev] [tc] version document for project navigator

Assuming this format is accepted, do you all have any sense of when this data will be complete for all projects? Jimmy McArthur April 5, 2017 at 8:59 AM FWIW, from my perspective on the Project Navigator side, this format works great. We can actually derive the age

[openstack-dev] [all][api] POST /api-wg/news

Greetings OpenStack community, In today's API-WG meeting we renamed the group twice. First to the "microversion support group". This is because any conversation that is even tangentially related to microversions becomes rather involved, leaking into metaphysics. Today involved some discussion

[openstack-dev] [architecture] Arch-WG, we hardly knew ye..

I'm going to be blunt. I'm folding the Architecture Working Group immediately following our meeting today at 2000 UTC. We'll be using the time to discuss continuity of the base-services proposal, and any other draw-down necessary. After that our meetings will cease. I had high hopes for the arch-w

Re: [openstack-dev] [Zun]Use 'uuid' instead of 'id' as object ident in data model

On 04/05/2017 11:00 AM, Monty Taylor wrote: On 04/05/2017 09:39 AM, Akihiro Motoki wrote: I noticed this thread by Monty's reply. Sorry for my late :( I think we need to think 'id' separately for API modeling and DB modeling. In the API perspective, one of the important things is that 'id' i

Re: [openstack-dev] [Zun]Use 'uuid' instead of 'id' as object ident in data model

On 04/05/2017 11:02 AM, gordon chung wrote: On 05/04/17 09:00 AM, Monty Taylor wrote: Please do NOT use uuid as a primary key in MySQL: * UUID has 36 characters which makes it bulky. you can store it as a binary if space is a concern. this is highly inconvenient from a datadump / MySQL

Re: [openstack-dev] [tripleo] container jobs are unstable

On Thu, Mar 30, 2017 at 11:01:08AM -0400, Paul Belanger wrote: > On Thu, Mar 30, 2017 at 03:08:57PM +0100, Steven Hardy wrote: > > To be fair, we discussed this on IRC yesterday, everyone agreed infra > > supported docker cache/registry was a great idea, but you said there was no > > known timeline

Re: [openstack-dev] [tc] version document for project navigator

On 04/06/2017 11:58 AM, Jimmy McArthur wrote: Assuming this format is accepted, do you all have any sense of when this data will be complete for all projects? Hopefully "soon" :) Honestly, it's not terribly difficult data to produce, so once we're happy with it and where it goes, crowdsourcin

Re: [openstack-dev] [tc] version document for project navigator

Cool. Thanks Monty! Monty Taylor April 6, 2017 at 3:21 PM On 04/06/2017 11:58 AM, Jimmy McArthur wrote: Assuming this format is accepted, do you all have any sense of when this data will be complete for all projects? Hopefully "soon" :) Honestly, it's not terrib

[openstack-dev] [freezer] Freezer Hangout Discussion tomorrow

Hello everyone, There will be a freezer hangout meeting tomorrow if you want to discuss anything about freezer. We gonna review the project and what has been done so far and where should we direct the project. The hangout will start tomorrow at 2:00 pm GMT till 3:00 pm GMT and you can join from h

[openstack-dev] [keystone] rejoining our IRC channel

If you chill in #openstack-keystone, we had a little mishap today that resulted in people getting accidentally kicked from the channel. Everything is back to normal and if you haven't already done so, feel free to hop back in. Thanks! __

Re: [openstack-dev] [freezer] Freezer Hangout Discussion tomorrow

You can join the call directly tomorrow using this link [0]. [0] https://plus.google.com/hangouts/_/calendar/ZW5nLnN6YWhlckBnbWFpbC5jb20.u6remok1ujohdvh9hgl3u3h294?authuser=0 On Thu, Apr 6, 2017 at 10:03 PM, Saad Zaher wrote: > Hello everyone, > > There will be a freezer hangout meeting tomor

Re: [openstack-dev] [tripleo] container jobs are unstable

On Thu, Mar 30, 2017 at 10:08 AM, Steven Hardy wrote: > On Wed, Mar 29, 2017 at 10:07:24PM -0400, Paul Belanger wrote: > > On Thu, Mar 30, 2017 at 09:56:59AM +1300, Steve Baker wrote: > > > On Thu, Mar 30, 2017 at 9:39 AM, Emilien Macchi > wrote: > > > > > > > On Mon, Mar 27, 2017 at 8:00 AM, Fl

Re: [openstack-dev] [keystone] rejoining our IRC channel

On 2017-04-06 16:04:14 -0500 (-0500), Lance Bragstad wrote: > If you chill in #openstack-keystone, we had a little mishap today that > resulted in people getting accidentally kicked from the channel. Everything > is back to normal and if you haven't already done so, feel free to hop back > in. Sad

Re: [openstack-dev] [oslo][kolla][openstack-helm][tripleo][all] Storing configuration options in etcd(?)

On Wed, Mar 22, 2017 at 11:23 AM, Flavio Percoco wrote: > On 15/03/17 15:40 -0400, Doug Hellmann wrote: >> >> Excerpts from Monty Taylor's message of 2017-03-15 04:36:24 +0100: >>> >>> On 03/14/2017 06:04 PM, Davanum Srinivas wrote: >>> > Team, >>> > >>> > So one more thing popped up again on IRC:

Re: [openstack-dev] [keystone] rejoining our IRC channel

2017-04-06 17:16 GMT-05:00 Jeremy Stanley : > On 2017-04-06 16:04:14 -0500 (-0500), Lance Bragstad wrote: >> If you chill in #openstack-keystone, we had a little mishap today that >> resulted in people getting accidentally kicked from the channel. Everything >> is back to normal and if you haven't

Re: [openstack-dev] [policy][nova][keystone] policy meeting next week

For those looking for a little background information on RBAC, I've included a link to the NIST RBAC model [0]. It doesn't drill down to the nitty-gritty implementation details, but it does give a good idea of RBAC standardization complete with examples. If anyone has any additional references the

Re: [openstack-dev] [oslo][kolla][openstack-helm][tripleo][all] Storing configuration options in etcd(?)

Excerpts from Emilien Macchi's message of 2017-04-06 18:17:59 -0400: > On Wed, Mar 22, 2017 at 11:23 AM, Flavio Percoco wrote: > > On 15/03/17 15:40 -0400, Doug Hellmann wrote: > >> > >> Excerpts from Monty Taylor's message of 2017-03-15 04:36:24 +0100: > >>> > >>> On 03/14/2017 06:04 PM, Davanum

Re: [openstack-dev] [kubernetes][go] External OpenStack Cloud Provider for Kubernetes

- Original Message - > From: "Monty Taylor" > To: openstack-dev@lists.openstack.org > Sent: Sunday, April 2, 2017 4:16:44 PM > Subject: Re: [openstack-dev] [kubernetes][go] External OpenStack Cloud > Provider for Kubernetes > > On 04/02/2017 02:53 PM, Chris Hoge wrote: > > Now that the p

Re: [openstack-dev] [nova] nova boot from image created volume

Thanks Matt. -- Original -- From: "Matt Riedemann"; Date: Fri, Apr 7, 2017 00:18 AM To: "openstack-dev"; Subject: Re: [openstack-dev] [nova] nova boot from image created volume On 4/6/2017 10:05 AM, Jay Pipes wrote: >> jaypipes@serialcoder:~/src/gi