[openstack-dev] [Nova] Port os-volume-attachments into os-extended-volumes v3

Hi, guys, When I try to port 'os-volume-attachments' into nova api v3, I found there is a patch for new extensions 'os-extended-volumes'(https://review.openstack.org/#/c/32530/5 ). That extension implements part of same function of os-volume-attachme

Re: [openstack-dev] [oslo.config] Config files overriding CLI: The path of most surprise.

Excerpts from Mark McLoughlin's message of 2013-07-01 15:12:51 -0700: > On Mon, 2013-07-01 at 14:52 -0700, Clint Byrum wrote: > > Last week I went to use oslo.config in a utility I am writing called > > os-collect-config[1]... > > > > While running unit tests on the main() method that is used for

Re: [openstack-dev] [oslo.config] Config files overriding CLI: The path of most surprise.

On Tue, 2013-07-02 at 00:24 -0700, Clint Byrum wrote: > Excerpts from Mark McLoughlin's message of 2013-07-01 15:12:51 -0700: > > On Mon, 2013-07-01 at 14:52 -0700, Clint Byrum wrote: > > > Last week I went to use oslo.config in a utility I am writing called > > > os-collect-config[1]... > > > > >

Re: [openstack-dev] [horizon] Removing the .mo files from Horizon git

Thomas Goirand wrote: > So, shouldn't the .mo files be generated at build time only, and be kept > out of the Git? +1 -- Thierry Carrez (ttx) ___ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/l

[openstack-dev] Reminder: Project & release status meeting - 21:00 UTC

Today in the Project & release status meeting we'll be looking into havana-2 milestone (2 weeks left!), Neutron renaming progress and the proposed change[0] in blueprint tracking. [0] http://lists.openstack.org/pipermail/openstack-dev/2013-June/011055.html Feel free to add extra topics to the age

Re: [openstack-dev] [horizon] Removing the .mo files from Horizon git

On Tue, 2013-07-02 at 09:58 +0200, Thierry Carrez wrote: > Thomas Goirand wrote: > > So, shouldn't the .mo files be generated at build time only, and be kept > > out of the Git? > > +1 Yep, agree too. Interestingly, last time I checked, devstack doesn't actually compile the message catalogs (pyt

Re: [openstack-dev] Question about locking

Hi Vish, >Were other commands working on the compute node? It seems much more >likely that the node had a hung connection to rabbit. If you are not using tcp >keepalives, a network hiccup (or failover) can cause half open connections >where the server thinks the connection is still active so it se

Re: [openstack-dev] RFC: Basic definition of OpenStack Programs and first batch

John Dickinson wrote: > I really like the Solution 2 proposal. There is also a "Solution 3" variant: Everything is a program. Some programs produce an integrated/server piece, then that specific project (not the program that produces it) needs to go through incubation. That variant preserves the

Re: [openstack-dev] RFC: Basic definition of OpenStack Programs and first batch

Thierry Carrez wrote: > """ > 'OpenStack Programs' are efforts which are essential to the completion > of our mission. Programs can create any code repository and produce any > deliverable they deem necessary to achieve their goals. > > Programs are placed under the oversight of the Technical Comm

[openstack-dev] [Nova] Question about fixed_ip_bulk_create() db.api function.

Hello All. I have a question about the patch `Add unique constraint to FixedIp` (see https://review.openstack.org/#/c/29364/), which is a part of blueprint `Complete db unique key enforcement on all tables dbs` ( https://blueprints.launchpad.net/nova/+spec/db-enforce-unique-keys). There is a disc

Re: [openstack-dev] RFC: Basic definition of OpenStack Programs and first batch

On 2 July 2013 21:32, Thierry Carrez wrote: > Thierry Carrez wrote: >> """ >> 'OpenStack Programs' are efforts which are essential to the completion >> of our mission. Programs can create any code repository and produce any >> deliverable they deem necessary to achieve their goals. >> >> Programs

Re: [openstack-dev] Move keypair management out of Nova and into Keystone?

> -Original Message- > From: Jay Pipes [mailto:[email protected]] > Sent: 02 July 2013 02:04 > To: [email protected] > Subject: Re: [openstack-dev] Move keypair management out of Nova and into > Keystone? > > On 07/01/2013 07:49 PM, Jamie Lennox wrote: > > On Mon, 2013-07-

Re: [openstack-dev] [Nova] Question about fixed_ip_bulk_create() db.api function.

On 07/02/2013 05:32 AM, Victor Sergeyev wrote: Hello All. I have a question about the patch `Add unique constraint to FixedIp` (see https://review.openstack.org/#/c/29364/), which is a part of blueprint `Complete db unique key enforcement on all tables dbs` (https://blueprints.launchpad.net/nova

[openstack-dev] [OSSN][OSSG] Nova Baremetal Exposes Previous Tenant Data

Nova Baremetal Exposes Previous Tenant Data - ### Summary ### Data of previous tenants may be exposed to new ones when using Nova Baremetal ### Affected Services / Software ### Keystone, Databases ### Discussion ### Nova Baremetal is intended for testing and development only, it is not inten

Re: [openstack-dev] [nova] Nova API extensions NOT to be ported to v3

On 1 July 2013 15:49, Andrew Laski wrote: > On 07/01/13 at 11:23am, Mauro S M Rodrigues wrote: >> One more though, about os-multiple-create: I was also thinking to remove >> it, I don't see any real advantage to use it since it doesn't offer any kind >> of flexibility like chose different flavors,

Re: [openstack-dev] [Nova]Discussion about resize and migrate status separation

The confirm will happen automatically, after a period of time. Maybe 0 is a valid option there, I can't remember. John On 1 July 2013 03:18, guohliu wrote: > On 06/28/2013 05:58 PM, John Garbutt wrote: >> >> I am not sure its worth the extra calls. >> >> Hopefully once we have live-migrate and c

[openstack-dev] [nova] Nova scheduler code refactoring

Hi everyone, it appears that in different parts of nova various redundant and ambiguously designed code pieces are laying hidden. I have started hunting them recently with proposing and implementing a blueprint for scheduler's host manager refactoring: https://blueprints.launchpad.net/nova/+spec/

Re: [openstack-dev] Move keypair management out of Nova and into Keystone?

On Mon, 2013-07-01 at 21:03 -0400, Jay Pipes wrote: > On 07/01/2013 07:49 PM, Jamie Lennox wrote: > > On Mon, 2013-07-01 at 14:09 -0700, Nachi Ueno wrote: > >> Hi folks > >> > >> I'm interested in it too. > >> I'm working on VPN support for Neutron. > >> Public key authentication is one of feature

Re: [openstack-dev] Move keypair management out of Nova and into Keystone?

On 07/02/2013 08:26 AM, Simo Sorce wrote: On Mon, 2013-07-01 at 21:03 -0400, Jay Pipes wrote: On 07/01/2013 07:49 PM, Jamie Lennox wrote: On Mon, 2013-07-01 at 14:09 -0700, Nachi Ueno wrote: Hi folks I'm interested in it too. I'm working on VPN support for Neutron. Public key authentication i

Re: [openstack-dev] RFC: Basic definition of OpenStack Programs and first batch

On Tue, Jul 2, 2013 at 5:52 AM, Robert Collins wrote: > On 2 July 2013 21:32, Thierry Carrez wrote: > > Thierry Carrez wrote: > >> """ > >> 'OpenStack Programs' are efforts which are essential to the completion > >> of our mission. Programs can create any code repository and produce any > >> deli

[openstack-dev] [Swift] Swift 1.9.0 released: global clusters and more

I'm pleased to announce that Swift 1.9.0 has been released. This has been a great release with major features added, thanks to the combined effort of 37 different contributors. Full release notes: https://github.com/openstack/swift/blob/master/CHANGELOG Download: https://launchpad.net/swift/havana

Re: [openstack-dev] Move keypair management out of Nova and into Keystone?

I've spent some time thinking about how Barbican (Key Management) can help in this workflow. We will have the ability to generate SSH keys (and a host of other key & certificate types). This is backed by cryptographically sound code and we've spent some time figuring out the entropy problem and HS

Re: [openstack-dev] [oslo.config] Config files overriding CLI: The path of most surprise.

On 07/01/2013 05:52 PM, Clint Byrum wrote: > Last week I went to use oslo.config in a utility I am writing called > os-collect-config[1]... > > While running unit tests on the main() method that is used for the CLI, > I was surprised to find that my unit tests were picking up values from > a confi

Re: [openstack-dev] Move keypair management out of Nova and into Keystone?

On 07/02/2013 09:49 AM, Jarret Raim wrote: I've spent some time thinking about how Barbican (Key Management) can help in this workflow. We will have the ability to generate SSH keys (and a host of other key & certificate types). This is backed by cryptographically sound code and we've spent some

Re: [openstack-dev] [OSLO] Current DB status

On Mon, 2013-07-01 at 17:35 +0100, Mark McLoughlin wrote: > On Mon, 2013-07-01 at 19:33 +0300, Gary Kotton wrote: > > On 07/01/2013 07:07 PM, Mark McLoughlin wrote: > > > On Mon, 2013-07-01 at 18:59 +0300, Gary Kotton wrote: > > >> On 07/01/2013 06:49 PM, Mark McLoughlin wrote: > > >>> On Mon, 2013

Re: [openstack-dev] [oslo.config] Config files overriding CLI: The path of most surprise.

tl;dr - this has been fixed on master for a while and the fix is included in oslo.config-1.2.0a3 http://docs.openstack.org/developer/oslo.config/#a3 Mark. ___ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cg

Re: [openstack-dev] [Openstack] Keystone store-quota-data blueprint

On Monday, July 1, 2013, Jamie Lennox wrote: > On Tue, 2013-07-02 at 02:03 +, Everett Toews wrote: > > This topic came up at the last summit in Portland at [1] and [2]. > > > > > > Yehia and another colleague of his from HP had a design that was > > discussed and it seemed like they were going

Re: [openstack-dev] Move keypair management out of Nova and into Keystone?

On Monday, July 1, 2013, Jamie Lennox wrote: > On Mon, 2013-07-01 at 14:09 -0700, Nachi Ueno wrote: > > Hi folks > > > > I'm interested in it too. > > I'm working on VPN support for Neutron. > > Public key authentication is one of feature milestone in the IPsec > > implementation. > > But I believ

Re: [openstack-dev] Email is not registered problem

On 2013-07-01 18:29, Qing He wrote: The emails from this list stopped coming to my email address, is this related? I don't see how it could be. To my knowledge there's no connection between Gerrit and openstack-dev. I actually use different addresses for both. -Ben __

Re: [openstack-dev] A patch review

On Monday, July 1, 2013, Wenhao Xu wrote: > Hi guys, > > The review of (https://review.openstack.org/#/c/34652/) has been idled > for a while. I am wondering anyone has a free time slot to review it? > Thanks. > Please tag the name of the relevant project in the subject line, especially when ema

Re: [openstack-dev] [nova] Nova API extensions NOT to be ported to v3

On 07/02/2013 07:24 AM, John Garbutt wrote: > On 1 July 2013 15:49, Andrew Laski wrote: >> On 07/01/13 at 11:23am, Mauro S M Rodrigues wrote: >>> One more though, about os-multiple-create: I was also thinking to remove >>> it, I don't see any real advantage to use it since it doesn't offer any kin

Re: [openstack-dev] Move keypair management out of Nova and into Keystone?

On Tue, 2013-07-02 at 10:07 -0400, Jay Pipes wrote: > On 07/02/2013 09:49 AM, Jarret Raim wrote: > > I've spent some time thinking about how Barbican (Key Management) can help > > in this workflow. > > > > We will have the ability to generate SSH keys (and a host of other key & > > certificate type

Re: [openstack-dev] Move keypair management out of Nova and into Keystone?

On 07/02/2013 10:56 AM, Simo Sorce wrote: If 'access credentials' remain buried (as in they cannot never be retrieved) in Keystone (or whatever IdM service it bridges to) then it is probably the right place as it performs authentication anyway and needs direct access to these credentials interna

Re: [openstack-dev] [nova] Nova API extensions NOT to be ported to v3

On 07/02/2013 10:49 AM, Russell Bryant wrote: On 07/02/2013 07:24 AM, John Garbutt wrote: On 1 July 2013 15:49, Andrew Laski wrote: On 07/01/13 at 11:23am, Mauro S M Rodrigues wrote: One more though, about os-multiple-create: I was also thinking to remove it, I don't see any real advantage to

Re: [openstack-dev] Move keypair management out of Nova and into Keystone?

> > I don't understand. Users already have custody of their own keys. The > > only thing that Keystone/Nova has is the public key fingerprint [1], not > > the private key... > > You acatually have the public key, not just the fingerprint, but indeed > I do not see why abrbican should be involved h

Re: [openstack-dev] [cinder] Propose to add copying the reference images when creating a volume

On Mon, Jul 1, 2013 at 11:14 AM, Vishvananda Ishaya wrote: > > On Jul 1, 2013, at 3:35 AM, Sheng Bo Hou wrote: > > Hi Mate, > > First, thanks for answering. > I was trying to find the way to prepare the bootable volume. > Take the default image downloaded by devstack, there are three images: > ci

Re: [openstack-dev] Move keypair management out of Nova and into Keystone?

On 07/02/2013 11:12 AM, Bryan D. Payne wrote: > I don't understand. Users already have custody of their own keys. The > only thing that Keystone/Nova has is the public key fingerprint [1], not > the private key... You acatually have the public key, not just the fingerprin

Re: [openstack-dev] [Openstack] Keystone store-quota-data blueprint

That's a relieve! As you said, we designed the Quota API using the Trust API as example, so it is not in the default pipeline, and we hope to commit it soon for being reviewed. But the design is open for reviewing and feedback https://wiki.openstack.org/wiki/DomainQuotaManagementAndEnforcement

[openstack-dev] [networking] Changes to the OVS agent tunneling

I've been spending a fair amount of time working with the OVS agent recently, and I've written up a small Google Document [1] detailing the end goal of all of this work. The short story is that I am introducing changes into the OVS agent to add support for multiple tunnel_types when the agent is

Re: [openstack-dev] Move keypair management out of Nova and into Keystone?

> +1 for using Barbican >> > > Simo just got finished saying Barbican was *not* the correct place to put > this information... Understood. I'm disagreeing with Simo. And I'm agreeing with Jarret Raim. -bryan ___ OpenStack-dev mailing list OpenStack-

Re: [openstack-dev] [cinder] Propose to add copying the reference images when creating a volume

Hi Sheng, You can use a raw(qemu-img recognised) type image to glance, and ask cinder to create a volume from that. This way you end up with a bootable volume. In the end of the day, your instance will just see a block device. The default cinder driver should also recognise other formats that are

[openstack-dev] Hyper-v meeting

Hi all, I'm canceling the meeting for today. Multiple key individuals are traveling and unable to attend. We will resume next week. P Sent from my Verizon Wireless 4G LTE Smartphone ___ OpenStack-dev mailing list [email protected] ht

Re: [openstack-dev] Proposal for including fake implementations in python-client packages

The idea has merit; my main concern is that we would be duplicating significant chunks of code/logic between the fakes and the real services. How can we do this in a DRY way? /kg ___ OpenStack-dev mailing list [email protected] http:/

Re: [openstack-dev] [networking] Changes to the OVS agent tunneling

Hi Kyle, It seems that the document is locked, could you provide the access code? Thanks, Edgar On 7/2/13 8:32 AM, "Kyle Mestery (kmestery)" wrote: >I've been spending a fair amount of time working with the OVS agent >recently, and I've written up a small Google Document [1] detailing the >en

Re: [openstack-dev] [networking] Changes to the OVS agent tunneling

Fixed, sorry about that! On Jul 2, 2013, at 11:14 AM, Edgar Magana wrote: > Hi Kyle, > > It seems that the document is locked, could you provide the access code? > > Thanks, > > Edgar > > On 7/2/13 8:32 AM, "Kyle Mestery (kmestery)" wrote: > >> I've been spending a fair amount of time wor

Re: [openstack-dev] Proposal for including fake implementations in python-client packages

On Tue, Jul 2, 2013 at 11:10 AM, Kurt Griffiths wrote: > The idea has merit; my main concern is that we would be duplicating > significant chunks of code/logic between the fakes and the real services. > > How can we do this in a DRY way? I've done it a few different ways for libraries I've worke

Re: [openstack-dev] [networking] Changes to the OVS agent tunneling

+1 eagerly awaiting, sounds good. Alan -Original Message- From: Edgar Magana [mailto:[email protected]] Sent: July-02-13 12:15 PM To: OpenStack List Subject: Re: [openstack-dev] [networking] Changes to the OVS agent tunneling Hi Kyle, It seems that the document is locked, could you

Re: [openstack-dev] Move keypair management out of Nova and into Keystone?

Hi Simo, I am lost. Does Barbican is product came out of https://wiki.openstack.org/wiki/KeyManager BP? If yes, then why it is deviating from the BP which says Key Manager will be separate service but not a part of Keystone. If no, then why we are thinking about new Key manager (which seems

Re: [openstack-dev] Question about locking

On Jul 2, 2013, at 1:49 AM, "Rosa, Andrea (HP Cloud Services)" wrote: > Hi Vish, > >> Were other commands working on the compute node? It seems much more >> likely that the node had a hung connection to rabbit. If you are not using >> tcp >> keepalives, a network hiccup (or failover) can caus

Re: [openstack-dev] Move keypair management out of Nova and into Keystone?

On Tue, 2013-07-02 at 08:12 -0700, Bryan D. Payne wrote: > > > I don't understand. Users already have custody of their own > keys. The > > only thing that Keystone/Nova has is the public key > fingerprint [1], not > > the private key... > >

Re: [openstack-dev] Move keypair management out of Nova and into Keystone?

On Tue, 2013-07-02 at 16:55 +, Tiwari, Arvind wrote: > Hi Simo, > > I am lost. > > Does Barbican is product came out of > https://wiki.openstack.org/wiki/KeyManager BP? Yes Barbican is an implementation of this Blueprint afaik. > If yes, then why it is deviating from the BP which says Key

Re: [openstack-dev] [oslo.config] Config files overriding CLI: The path of most surprise.

On 2013-07-01 15:10:26 -0700 (-0700), Mark Washenberger wrote: [...] > The talk about permanence confuses me, unless we mean that more > permanent values are overridden by less permanent ones. [...] I think the "permanence" counter argument (which I don't agree with, just recounting it for complet

Re: [openstack-dev] Email is not registered problem

On 2013-07-01 23:29:30 + (+), Qing He wrote: > The emails from this list stopped coming to my email address, is > this related? Changing contact information in Gerrit (and Launchpad for that matter) has no bearing on Mailman mailing list subscriptions on lists.openstack.org. Perhaps the li

[openstack-dev] Work around DB in OpenStack (Oslo, Nova, Cinder, Glance)

### Goal ### We should fix work with DB, unify it in all projects and use oslo cod

Re: [openstack-dev] Work around DB in OpenStack (Oslo, Nova, Cinder, Glance)

One small addition I would suggest is a step to remove the unused sqlalchemy-migrate code once this is all done. That's my main concern with moving it to Oslo right now. Also, is this a formal blueprint(s)? Seems like it should be. -Ben On 2013-07-02 12:50, Boris Pavlovic wrote:

[openstack-dev] [Nova] No meeting this week (2013-07-04)

Greetings, Let's skip the weekly nova meeting this week. It falls on a US holiday, so many people would not be able to make it. The biggest item of discussion right now is havana-2 status. Please check and make sure the status of your blueprints is accurate. Let's work hard on a final push tow

Re: [openstack-dev] [horizon] Removing the .mo files from Horizon git

On 07/02/2013 01:13 AM, Mark McLoughlin wrote: > On Tue, 2013-07-02 at 09:58 +0200, Thierry Carrez wrote: >> Thomas Goirand wrote: >>> So, shouldn't the .mo files be generated at build time only, and be kept >>> out of the Git? >> >> +1 > > Yep, agree too. > > Interestingly, last time I checked

Re: [openstack-dev] [Nova] No meeting this week (2013-07-04)

Hi, +1 Best regards, Boris Pavlovic On Tue, Jul 2, 2013 at 10:04 PM, Russell Bryant wrote: > Greetings, > > Let's skip the weekly nova meeting this week. It falls on a US holiday, > so many people would not be able to make it. > > The biggest item of discussion right now is havana-2 status.

Re: [openstack-dev] RFC: Basic definition of OpenStack Programs and first batch

On 07/02/2013 05:46 AM, Doug Hellmann wrote: > > > > On Tue, Jul 2, 2013 at 5:52 AM, Robert Collins > mailto:[email protected]>> wrote: > > On 2 July 2013 21:32, Thierry Carrez > wrote: > > Thierry Carrez wrote: > >> """ > >> 'OpenSta

[openstack-dev] [Nova] Criteria for compute drivers

Greetings, Nova includes various compute drivers today, but the test coverage they receive varies quite a bit. This is documented on the following wiki page. The drivers are broken up into groups A, B, and C. https://wiki.openstack.org/wiki/HypervisorSupportMatrix We have two new compute d

Re: [openstack-dev] [horizon] Removing the .mo files from Horizon git

On 07/03/2013 02:15 AM, Monty Taylor wrote: > > > On 07/02/2013 01:13 AM, Mark McLoughlin wrote: >> On Tue, 2013-07-02 at 09:58 +0200, Thierry Carrez wrote: >>> Thomas Goirand wrote: So, shouldn't the .mo files be generated at build time only, and be kept out of the Git? >>> >>> +1 >> >

Re: [openstack-dev] Move keypair management out of Nova and into Keystone?

Wrote this answer this morning, but Simo beat me to it. Answer below sent for posterity. TL;DR: Jay - it seems like we are on the same page. Barbican can be helpful for generation and storage (if needed) of various types of keying material. However, if your use case is better served by storing

Re: [openstack-dev] Move keypair management out of Nova and into Keystone?

On Tue, Jul 2, 2013 at 8:12 AM, Bryan D. Payne wrote: > > > I don't understand. Users already have custody of their own keys. The >> > only thing that Keystone/Nova has is the public key fingerprint [1], not >> > the private key... >> >> You acatually have the public key, not just the fingerprin

Re: [openstack-dev] [Nova] Criteria for compute drivers

> We have two new compute drivers in the queue for Havana: docker [1] > and z/vm [2]. I'd like to propose as a piece of criteria for > inclusion that new drivers go into groups A or B. I think this is a really good idea. As we continue to absorb new and more complex drivers into the tree, the amo

Re: [openstack-dev] Move key pair management out of Nova and into Keystone?

Greetings Simo, Jay, Bryan, Jarret, Dolph, Phil, Nachi, Jamie, Thierry, Arvind and others! 1) The key manager, barbican, under development supports the blueprint we developed and discussed on this mailing list. https://wiki.openstack.org/wiki/KeyManager#Key_Manager 2) Its full feat

[openstack-dev] [Neutron] does delete_network call delete_subnet automatically?

Folks, When I create a network and a subnet associated to that network, I am able to delete the network without deleting the subnet first from both CLI and Horizon. The difference is that in Horizon, both APIs are called: delete_subnet() and delete_network() When I tried by CLI, only delete_networ

Re: [openstack-dev] [Neutron] does delete_network call delete_subnet automatically?

delete_network() in the db_base class handles deleting the subnets associated with the networks. https://github.com/openstack/quantum/blob/master/quantum/db/db_base_plugin_v2.py#L1033 On Tue, Jul 2, 2013 at 12:31 PM, Edgar Magana wrote: > Folks, > > When I create a network and a subnet associa

Re: [openstack-dev] [Infra] Meeting Tuesday July 2nd at 19:00 UTC

On Mon, Jul 1, 2013 at 9:33 AM, Elizabeth Krumbach Joseph wrote: > The OpenStack Infrastructure (Infra) team is hosting our weekly > meeting tomorrow, Tuesday July 2nd, at 19:00 UTC in #openstack-meeting Meeting minutes and logs: http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-07-0

Re: [openstack-dev] [Infra] Meeting Tuesday July 2nd at 19:00 UTC

On Tue, Jul 2, 2013 at 12:41 PM, Elizabeth Krumbach Joseph wrote: > http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-07-02-19.03.log.htm Lost a letter there: http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-07-02-19.03.log.html -- Elizabeth Krumbach Joseph || Lyz || pl

[openstack-dev] Distro defaults [was Re: [oslo.config] Config files overriding CLI: The path of most surprise.]

On Tue, 2013-07-02 at 17:48 +, Jeremy Stanley wrote: > On 2013-07-01 15:10:26 -0700 (-0700), Mark Washenberger wrote: > [...] > > The talk about permanence confuses me, unless we mean that more > > permanent values are overridden by less permanent ones. > [...] > > I think the "permanence" cou

Re: [openstack-dev] Move keypair management out of Nova and into Keystone?

> If you do not trust keystone to give you the right information you have > already lost as keystone is used (afaik) to check for authorization > anyway. > This is true. > Can you be a little bit more explicit on the threat model you have in > mind and what guarantees Barbican would give you tha

Re: [openstack-dev] RFC: Basic definition of OpenStack Programs and first batch

On Tue, Jul 2, 2013 at 2:30 PM, Monty Taylor wrote: > > > On 07/02/2013 05:46 AM, Doug Hellmann wrote: > > > > > > > > On Tue, Jul 2, 2013 at 5:52 AM, Robert Collins > > mailto:[email protected]>> wrote: > > > > On 2 July 2013 21:32, Thierry Carrez >

[openstack-dev] Issues with "git review" for a dependent commit

I'm trying to submit a gerrit review for a commit which is dependent on another person's commit [1]. I've followed the instructions here [2], and had no problems doing the branch create and the cherry pick of both the dependent and my own commits. However, when I go to commit, I get a gerrit err

Re: [openstack-dev] Move keypair management out of Nova and into Keystone?

On 7/2/13 12:43 PM, "Simo Sorce" wrote: >On Tue, 2013-07-02 at 16:55 +, Tiwari, Arvind wrote: >> Hi Simo, >> >> I am lost. >> >> Does Barbican is product came out of >>https://wiki.openstack.org/wiki/KeyManager BP? > >Yes Barbican is an implementation of this Blueprint afaik. Barbican is

Re: [openstack-dev] [Neutron] does delete_network call delete_subnet automatically?

If the plugin performs operations when the subnet is created, how is possible to roll-back those operation if the plugin implementation of delete_subnet() is never called? I don¹t think we should let delete_network in debasepluginv2.py delete all subnets, we could just ask the tenant user to delete

Re: [openstack-dev] Issues with "git review" for a dependent commit

Hi Kyle, I wonder if it works if you drop the -R ? I've seen this error: ! [remote rejected] HEAD -> refs/publish/master/bp/ml2-vxlan (no changes made) if i try to push a change that has already been pushed and nothing has changed. Any chance that may have happened? Best, Aaron On Tue, Ju

Re: [openstack-dev] Issues with "git review" for a dependent commit

On 2013-07-02 20:14:35 + (+), Kyle Mestery (kmestery) wrote: > I'm trying to submit a gerrit review for a commit which is > dependent on another person's commit [1]. [...] > ! [remote rejected] HEAD -> refs/publish/master/bp/ml2-vxlan (no changes > made) [...] I want to say I've seen thi

Re: [openstack-dev] [Neutron] does delete_network call delete_subnet automatically?

Good point. We should be calling delete_subnet() from delete_network() in the db_base class rather than deleting it directly from the database. Aaron On Tue, Jul 2, 2013 at 1:39 PM, Edgar Magana wrote: > If the plugin performs operations when the subnet is created, how is > possible to roll-ba

[openstack-dev] [Glance] No meeting this week

Hi folks, Due to the number of core members on vacation, we will not be having a glance team meeting this week. We will pick up again for Thursday of next week (July 11 2013), at the 2000 UTC timeslot. Thanks, markwash ___ OpenStack-dev mailing list Op

Re: [openstack-dev] [Nova] Criteria for compute drivers

On 02.07.2013, at 20:43, "Russell Bryant" wrote: > Greetings, > > Nova includes various compute drivers today, but the test coverage they > receive varies quite a bit. This is documented on the following wiki > page. The drivers are broken up into groups A, B, and C. > >https://wiki.ope

Re: [openstack-dev] [Neutron] does delete_network call delete_subnet automatically?

Before filing a bug, do we really want this kind of functionality? Is it "correct" to delete a network without really checking if the owner really wants to delete all subnets associated with it? Edgar From: Aaron Rosen Reply-To: OpenStack List Date: Tuesday, July 2, 2013 1:55 PM To: OpenSta

Re: [openstack-dev] Issues with "git review" for a dependent commit

On Jul 2, 2013, at 3:52 PM, Jeremy Stanley wrote: > On 2013-07-02 20:14:35 + (+), Kyle Mestery (kmestery) wrote: >> I'm trying to submit a gerrit review for a commit which is >> dependent on another person's commit [1]. > [...] >> ! [remote rejected] HEAD -> refs/publish/master/bp/ml2-vxl

Re: [openstack-dev] Issues with "git review" for a dependent commit

Kyle, is this commit basically a rebase on top of 91e0850? In that case the diff with the previous patchset would be empty. I recall I had a similar issue; I just tweaked a comment line in my commit to let gerrit think it was a different patchset. Salvatore On 2 July 2013 23:05, Kyle Mestery (k

Re: [openstack-dev] [Neutron] does delete_network call delete_subnet automatically?

Yes, I think this is the desired behavior. If someone deletes a network we check to see if there are any ports on the network. If there are ports on the network we raise. If there are no ports on the network we allow it to be deleted. Since you cannot have a subnet without a network we should delet

Re: [openstack-dev] Issues with "git review" for a dependent commit

On Jul 2, 2013, at 4:18 PM, Salvatore Orlando wrote: > > Kyle, > > is this commit basically a rebase on top of 91e0850? > In that case the diff with the previous patchset would be empty. > I recall I had a similar issue; I just tweaked a comment line in my commit to > let gerrit think it was a

Re: [openstack-dev] Issues with "git review" for a dependent commit

Kyle, I actually meant that this problem might occur if patchset 2, that you're trying to push, is a rebase of patchset 1 on top of another patch in order to make the commit dependent on another one. If that is the case, gerrit won't see any difference between patchset2 and patchset1, as git diff

Re: [openstack-dev] VPNaaS

HI Tatiana Cool. Thanks!! 2013/7/2 Tatiana Mazur : > Hello Nachi, > > VPNaaS UI code is here: > https://review.openstack.org/#/c/34882/ > > I edited "HowToInstall" page: an instruction and link to user scenarios > (https://wiki.openstack.org/wiki/Neutron/VPNaaS/UI) are added. > > -- > Kind regar

[openstack-dev] trove and heat integration status

Howdy, one of the TC requests for integration of trove was to integrate heat. While this is a small task for single instance installations, when we get into clustering it seems a bit more painful. Id like to submit the following as a place to start the discussion for why we would/wouldnt integr

Re: [openstack-dev] [Neutron] does delete_network call delete_subnet automatically?

It makes sense totally. Then, instead of making the db_base class calling the delete_subnet at the plugin level, shouldn't be better call delete_subnet at the plugin level when the delete_network is called? Basically: def delete_network() subnets = get_subnets() for subnet in subnets: delete_subne

Re: [openstack-dev] [Neutron] does delete_network call delete_subnet automatically?

The call should be in the db_base class. If you call self.delete_subnet() from the db_base class then it will call the delete_subnet() method from the plugin if implement. Inheritance. On Tue, Jul 2, 2013 at 3:15 PM, Edgar Magana wrote: > It makes sense totally. Then, instead of making the db_

[openstack-dev] [Nova] Proposal to add Christopher Yeoh to nova-core

Greetings, I would like to propose Christopher Yoeh to be added to the nova-core team. Christopher has been prolific in his contributions to nova lately, both in code and his general leadership of the v3 API effort. He has also been regularly contributing to code reviews. It would be great to h

Re: [openstack-dev] [Neutron] does delete_network call delete_subnet automatically?

Got it! I will file a bug for it and I will submit the fix this week. Thanks, Edgar From: Aaron Rosen Reply-To: OpenStack List Date: Tuesday, July 2, 2013 3:33 PM To: OpenStack List Subject: Re: [openstack-dev] [Neutron] does delete_network call delete_subnet automatically? The call sho

Re: [openstack-dev] trove and heat integration status

Excerpts from Michael Basnight's message of 2013-07-02 15:17:09 -0700: > Howdy, > > one of the TC requests for integration of trove was to integrate heat. While > this is a small task for single instance installations, when we get into > clustering it seems a bit more painful. Id like to submit

[openstack-dev] Savanna version 0.3 - on demand Hadoop task execution

We want to initiate discussion about Elastic Data Processing (EDP) Savanna component. This functionality is planned to be implemented in the next development phase starting on July 15. The main questions to address: - what kind of functionality should be implemented for EDP? - what a

Re: [openstack-dev] Issues with "git review" for a dependent commit

On 2013-07-02 21:05:21 + (+), Kyle Mestery (kmestery) wrote: [...] > remote: New Changes: > remote: https://review.openstack.org/35384 > remote: > To ssh://[email protected]:29418/openstack/quantum.git > ! [remote rejected] HEAD -> refs/publish/master/bp/ml2-vxlan (no changes

Re: [openstack-dev] [Nova] Proposal to add Christopher Yeoh to nova-core

> Please respond with +1s or any concerns. My only concern is that now he and Mikal can collude on patches while the rest of us are asleep. Actually, maybe that's okay. +1 from me :) --Dan ___ OpenStack-dev mailing list [email protected]

Re: [openstack-dev] trove and heat integration status

On Jul 2, 2013, at 3:52 PM, Clint Byrum wrote: > Excerpts from Michael Basnight's message of 2013-07-02 15:17:09 -0700: >> Howdy, >> >> one of the TC requests for integration of trove was to integrate heat. While >> this is a small task for single instance installations, when we get into >> clu

[openstack-dev] [Neutron] Help with database migration error

I have not worked with databases much and this is my first attempt at a database migration. I am trying to follow this Howto: https://wiki.openstack.org/wiki/Neutron/DatabaseMigration I get the following error at step 3: /opt/stack/quantum[master] $ quantum-db-manage --config-file /etc/quantum/q

Re: [openstack-dev] A patch review

Got it. Thanks. Best, Wenhao On Tue, Jul 2, 2013 at 10:46 PM, Dolph Mathews wrote: > > On Monday, July 1, 2013, Wenhao Xu wrote: > >> Hi guys, >> >> The review of (https://review.openstack.org/#/c/34652/) has been idled >> for a while. I am wondering anyone has a free time slot to review it? >

Re: [openstack-dev] Issues with "git review" for a dependent commit

On Jul 2, 2013, at 6:23 PM, Jeremy Stanley wrote: > On 2013-07-02 21:05:21 + (+), Kyle Mestery (kmestery) wrote: > [...] >> remote: New Changes: >> remote: https://review.openstack.org/35384 >> remote: >> To ssh://[email protected]:29418/openstack/quantum.git >> ! [remote rej

  1   2   >