Re: [openstack-dev] [sahara][release] missing build artifacts

michael mccune wrote: On 04/01/2016 04:48 PM, Doug Hellmann wrote: Excerpts from Doug Hellmann's message of 2016-04-01 16:27:42 -0400: Sahara team, We noticed in our audit of the links on http://releases.openstack.org/mitaka/index.html that the links to the build artifacts for sahara-extras po

Re: [openstack-dev] [TripleO] FreeIPA integration

On Sat, Apr 02, 2016 at 05:28:57PM -0400, Adam Young wrote: > I finally have enough understanding of what is going on with Tripleo to > reasonably discuss how to implement solutions for some of the main security > needs of a deployment. > > > FreeIPA is an identity management solution that can pr

Re: [openstack-dev] [monasca][release] missing build artifacts

Davanum Srinivas wrote: Please see below: On Sat, Apr 2, 2016 at 8:41 AM, Doug Hellmann wrote: Excerpts from Hochmuth, Roland M's message of 2016-04-02 01:35:35 +: Hi Doug, You had mentioned issues with three repos: 1. monasca-ceilometer 2. monasca-log-api 3. monasca-thresh All the repo

Re: [openstack-dev] [Fuel][Bareon][Ironic] The future of integration module

Hello, At the beginning of the work, we've taken fuel-agent driver from Ironic team and customized it. Here is main features, which were created during development for Cray (all of them are now part of bareon-ironic): 1. deploy-config could be stored in multiple places (image meta, instance

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

Hi, We have a very good discussion about cross OpenStack L2 networking last week: https://etherpad.openstack.org/p/TricircleCrossPodL2Networking Let's continue the discussion and other topics in this weekly meeting. IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every

[openstack-dev] [cross-project] [all] Quotas and the need for reservation

Hi All, As part of the cross project Quota library effort [1] there has been a discussion around the need for reservations or getting rid of reservations altogether. It is believed that reservation help to to reserve a set of resources beforehand and hence eventually preventing any other upcoming

[openstack-dev] [Fuel] Help with reviews - modularisation.

Hi Fuelers! I kindly ask you to review my patches [0] and [1]. There is a "big thing" going on there. I'm trying to decouple Volume Manager from Nailgun. It's a first step towards Fuel modularisation, which will also be an example for other developers: "How to implement Nailgun extensions". Ther

[openstack-dev] FW: Regarding code debug information

Dear All, I am newbie for openstack development and trying to understand the flow using code base. As the code base is very huge need your support to understand it. Please let me know if there are any such way to debug the code or analyse it. Any kind of help will be appreciated. Thanks & Regar

[openstack-dev] [telemetry] Newton design summit planning

Hi folks, I've started to fill in the blank for our next design summit sessions. The schedule is at: https://www.openstack.org/summit/austin-2016/summit-schedule/global-search?t=Telemetry%3A We still have the 2 first work sessions empty, because I ran out of idea. I've used the Etherpad we pr

Re: [openstack-dev] FW: Regarding code debug information

There are developers doc which can help you to understand particular component framework and codes. http://docs.openstack.org/developer/openstack-projects.html Depends on project you want to deep dive you can check their doc. For example Nova nova one can be found here - http://docs.openstack.org

Re: [openstack-dev] [neutron][api] advanced search criteria

Armando M. wrote: On 4 April 2016 at 17:08, Jay Pipes wrote: On 04/04/2016 06:57 PM, Ihar Hrachyshka wrote: - why do we even need to control those features with configuration options? can we deprecate and remove them? This would be my choice. Configuration options that make the Neutron API

Re: [openstack-dev] [telemetry] Newton design summit planning

On Tue, 5 Apr 2016, Julien Danjou wrote: Any items/ideas we could discussion in this remaining sessions? Any project we could/should invite to discuss with us? Nova has started work on versioned notifications: http://specs.openstack.org/openstack/nova-specs/specs/mitaka/implemented/version

Re: [openstack-dev] [Fuel][library] Update of astute.yaml fixtures and noop tests

Hi folks, we've merged all the changes related to fixtures update [0] and bugfix to unblock noop tests [1]. So if you see -1 from fuel_noop_tests [2] in tests not related to your patch, then please rebase. Regards, Alex [0] https://review.openstack.org/#/q/topic:update-fixtures-to-9.0 [1] https:

[openstack-dev] [ironic] [inspector] Proposing Anton Arefiev (aarefiev) for ironic-inspector-core

Hi! I'd like to propose Anton to the ironic-inspector core reviewers team. His stats are pretty nice [1], he's making meaningful reviews and he's pushing important things (discovery, now tempest). Members of the current ironic-inspector-team and everyone interested, please respond with your

Re: [openstack-dev] 答复: [Heat] Re-evaluate conditions specification

On Fri, Apr 01, 2016 at 04:39:02PM +, Fox, Kevin M wrote: >Why is imperative programming always brought up when discussing >conditionals in the templates? We are not wanting anything imperative. The >heat engine still picks the final ordering of things. We just want to give >it

Re: [openstack-dev] [tricircle]weekly meeting of Apr. 6

Hi Chaoyi, Thank you for team mtg every week. One day, we may need to discuss about trust relationship considering secure connection and no-latency issue between top and bottoms over BGP across ASs, in short between DCs. Any thought would be appreciated as usual. Cheers, Shinobu On Tue, Apr 5, 2

Re: [openstack-dev] [TripleO] FreeIPA integration

On the certificate management side I had presented this blueprint* https://review.openstack.org/#/c/282307/ *which proposes FreeIPA as the reference solution. There the steps are described however, I did leave away where the FreeIPA instance will be instal

Re: [openstack-dev] [TripleO] FreeIPA integration

On Tue, Apr 5, 2016 at 11:36 AM, Steven Hardy wrote: > On Sat, Apr 02, 2016 at 05:28:57PM -0400, Adam Young wrote: > > I finally have enough understanding of what is going on with Tripleo to > > reasonably discuss how to implement solutions for some of the main > security > > needs of a deploymen

[openstack-dev] [nova] Nova API sub-team meeting

Hi, We have weekly Nova API meeting tomorrow. The meeting is being held Wednesday UTC1300 and irc channel is #openstack-meeting-4. The proposed agenda and meeting details are here: https://wiki.openstack.org/wiki/Meetings/NovaAPI Please feel free to add items to the agenda. Thanks

Re: [openstack-dev] [TripleO] FreeIPA integration

This sounds suspiciously like, "how do you get a secret to the instance to get a secret from the secret store" issue :) Nova instance user spec again? Thanks, Kevin From: Juan Antonio Osorio Sent: Tuesday, April 05, 2016 4:07:06 AM To: OpenStack Development

Re: [openstack-dev] [neutron] -2'ing all patches on every gate breakage

On 04/04/2016 23:20, Carl Baldwin wrote: > On Mon, Apr 4, 2016 at 3:22 PM, Doug Wiegley > wrote: >> I don’t know, -1 really means, “there is something wrong, the submitter >> should fix it and clear the slate.” Whereas -2 has two meanings. The first >> is “procedural block”, and the second is “f

[openstack-dev] [Heat] Design summit planning

Hi all, We've been allocated 12 sessions for Austin. I started an etherpad where you can put topics that you'd like to talk about: https://etherpad.openstack.org/p/newton-heat-sessions. Please fill it up, we'll discuss what we have at the meeting tomorrow. Maybe we'll wait until next week to final

Re: [openstack-dev] [TripleO] FreeIPA integration

On 02/04/2016 22:33, Adam Young wrote: > I finally have enough understanding of what is going on with Tripleo to > reasonably discuss how to implement solutions for some of the main > security needs of a deployment. > > > FreeIPA is an identity management solution that can provide support for: > >

[openstack-dev] [Smaug]- IRC Meeting today (04/05) - 1400 UTC SM

Hi All, We will hold our bi-weekly IRC meeting today (Tuesday, 04/05) at 1400 UTC in #openstack-meeting Please review the proposed meeting agenda here: https://wiki.openstack.org/wiki/Meetings/smaug Please feel free to add to the agenda any subject you would like to discuss. Thanks, Saggi -

Re: [openstack-dev] [TripleO] FreeIPA integration

On Tue, Apr 5, 2016 at 2:45 PM, Fox, Kevin M wrote: > This sounds suspiciously like, "how do you get a secret to the instance to > get a secret from the secret store" issue :) > Yeah, sounds pretty familiar. We were using the nova hooks mechanism for this means, but it was deprecated recently

Re: [openstack-dev] [ironic] [inspector] Proposing Anton Arefiev (aarefiev) for ironic-inspector-core

+1 from me. Thanks for your work Anton and congrats! ;-) Imre On 04/05/2016 12:24 PM, Dmitry Tantsur wrote: Hi! I'd like to propose Anton to the ironic-inspector core reviewers team. His stats are pretty nice [1], he's making meaningful reviews and he's pushing important things (discovery, no

[openstack-dev] [Nova] FPGA as a resource

Hey all, On yesterday's scheduler meeting I was raised the idea of bringing up the FPGA to the OpenStack as the resource, which than might be exposed to the VMs. The use cases for motivations, why one want do this, are pretty broad - having such chip ready on the computes might be beneficial ei

Re: [openstack-dev] [Designate] Tempest Tests - in-repo or separate

Agreed on a separate repo. I'm honestly a little unsure how in-service-repo would ever work long term, given that tempest's requirements will match master, and may not be compatible with N releases ago's $service requirements.. Thoughts on how that might work, or is it just that no service has ha

Re: [openstack-dev] [telemetry] Newton design summit planning

> -Original Message- > From: Chris Dent [mailto:cdent...@anticdent.org] > Sent: April 05, 2016 12:13 > > On Tue, 5 Apr 2016, Julien Danjou wrote: > > > Any items/ideas we could discussion in this remaining sessions? > > Any project we could/should invite to discuss with us? > > Nova has

Re: [openstack-dev] [ironic] [inspector] Proposing Anton Arefiev (aarefiev) for ironic-inspector-core

Not sure if I'm eligible to vote, but his reviews are insightful, so +1 from me. Congrats! :) On Tue, Apr 5, 2016 at 3:22 PM, Imre Farkas wrote: > +1 from me. Thanks for your work Anton and congrats! ;-) > > Imre > > > > On 04/05/2016 12:24 PM, Dmitry Tantsur wrote: > >> Hi! >> >> I'd like to pr

[openstack-dev] [release][stable][ironic] bifrost 1.0.1 release (mitaka)

We are satisfied to announce the release of: bifrost 1.0.1: Deployment of physical machines using OpenStack Ironic and Ansible This release is part of the mitaka stable release series. For more details, please see below. Changes in bifrost 1.0.0..1.0.1 --- 83f2232 U

Re: [openstack-dev] [TripleO] FreeIPA integration

On Tue, Apr 05, 2016 at 02:07:06PM +0300, Juan Antonio Osorio wrote: >On Tue, Apr 5, 2016 at 11:36 AM, Steven Hardy wrote: > > On Sat, Apr 02, 2016 at 05:28:57PM -0400, Adam Young wrote: > > I finally have enough understanding of what is going on with Tripleo > to > > reas

Re: [openstack-dev] [Nova] FPGA as a resource

On Tue, Apr 05, 2016 at 02:27:30PM +0200, Roman Dobosz wrote: > Hey all, > > On yesterday's scheduler meeting I was raised the idea of bringing up > the FPGA to the OpenStack as the resource, which than might be exposed > to the VMs. > > The use cases for motivations, why one want do this, are

Re: [openstack-dev] [telemetry] Newton design summit planning

seems fine to me. we still don't have a story around events. we just sort of store and dump it right now. i guess this could probably fit into ceilometer split session... or maybe everyone is cool with just pushing things to elasticsearch and letting users play with that + kibana. On 05/04/2016

Re: [openstack-dev] [neutron][api] advanced search criteria

Hirofumi Ichihara wrote: Hi Ihar, On 2016/04/05 7:57, Ihar Hrachyshka wrote: Hi all, in neutron, we have a bunch of configuration options to control advanced filtering features for API, f.e. allow_sorting, allow_pagination, allow_bulk, etc. Those options have default False values. I saw

Re: [openstack-dev] [cross-project] [all] Quotas and the need for reservation

>It is believed that reservation help to to reserve a set of resources >beforehand and hence eventually preventing any other upcoming request >(serial or parallel) to exceed quota if because of original request the >project might have reached the quota limits. > >Questions :- >1. Does reservation i

Re: [openstack-dev] [telemetry] Rescheduling IRC meetings

+1 to demand meetings and asynchronous way On Thu, Mar 31, 2016 at 9:33 PM, Ildikó Váncsa wrote: > Hi Gordon, > > > > > ie. the new PTL should checkpoint with subteam leads regularly to review > spec status or identify missing resources on high-priority > > items? > > I would say anything that w

Re: [openstack-dev] 答复: [Heat] Re-evaluate conditions specification

On 05/04/16 06:43, Steven Hardy wrote: On Fri, Apr 01, 2016 at 04:39:02PM +, Fox, Kevin M wrote: Why is imperative programming always brought up when discussing conditionals in the templates? We are not wanting anything imperative. The heat engine still picks the final ordering o

Re: [openstack-dev] [cinder][openstackclient] Required name option for volumes, snapshots and backups

All, Just to document the discussion we had during the OSC IRC meeting last week: I believe the consensus we reached was that it wasn't appropriate to pretend "volume" before all Cinder commands but that it would be appropriate to move in that direction to for any commands that may be ambiguous li

Re: [openstack-dev] [cinder][openstackclient] Required name option for volumes, snapshots and backups

What about commands the become ambiguous in the future? I doubt there are many operations or objects that are unique to Cinder - backup, snapshot, transfer, group, type - these are all very much generic, and even if they aren't ambiguous now, they might well become so in future... On 5 April 2016

Re: [openstack-dev] [Designate] Tempest Tests - in-repo or separate

On Tue, Apr 05, 2016 at 01:37:21PM +0100, Kiall Mac Innes wrote: > Agreed on a separate repo. > > I'm honestly a little unsure how in-service-repo would ever work long > term, given that tempest's requirements will match master, and may > not be compatible with N releases ago's $service requiremen

Re: [openstack-dev] [cinder][openstackclient] Required name option for volumes, snapshots and backups

Duncan, Agreed, but the OSC team is concerned about unnecessarily adding API names into commands as much as the Cinder team wishes to make it clearer which commands belong to our component. This is where we need to keep this discussion open with the OSC team to find a good common ground. I am hopi

Re: [openstack-dev] [tempest] Implementing tempest test for Keystone federation functional tests

Thank you all for your awesome feedbacks! On Sun, Apr 3, 2016 at 9:07 PM, Jamie Lennox wrote: > > > On 2 April 2016 at 09:21, Rodrigo Duarte wrote: > >> >> >> On Thu, Mar 31, 2016 at 1:11 PM, Matthew Treinish >> wrote: >> >>> On Thu, Mar 31, 2016 at 11:38:55AM -0400, Minying Lu wrote: >>> > Hi

Re: [openstack-dev] [cinder][openstackclient] Required name option for volumes, snapshots and backups

On Tuesday, April 5, 2016, Duncan Thomas wrote: > What about commands the become ambiguous in the future? I doubt there are > many operations or objects that are unique to Cinder - backup, snapshot, > transfer, group, type - these are all very much generic, and even if they > aren't ambiguous now

Re: [openstack-dev] [TripleO] FreeIPA integration

Having an extra node for FreeIPA spawn up by heat works for me. And it's not a hard-requirement that we have to wire this into the TripleO CI. But the most sustainable approach to having TLS everywhere (at least for the admin and internal endpoints of Openstack, the message broker server nodes and

Re: [openstack-dev] [tempest] Implementing tempest test for Keystone federation functional tests

Thank you for your awesome feedbacks! > Another option is to add those tests to keystone itself (if you are not >> including tests that triggers other components APIs). See >> https://blueprints.launchpad.net/keystone/+spec/keystone-tempest-plugin-tests >> >> > > knikolla and I are looking into t

Re: [openstack-dev] [congress][release] missing build artifacts

Looks like the congress job is working now. We have a tarball for our latest RC: http://tarballs.openstack.org/congress/congress-3.0.0.0rc3.tar.gz Thierry added the links back for the tarball. https://github.com/openstack/releases/commit/beee35379b3b52ed7d444d93d7afd8b6603f69b6 So it looks lik

Re: [openstack-dev] 答复: [Heat] Re-evaluate conditions specification

On 01/04/16 12:31, Steven Hardy wrote: On Fri, Apr 01, 2016 at 04:15:30PM +0200, Thomas Herve wrote: On Fri, Apr 1, 2016 at 3:21 AM, Zane Bitter wrote: On 31/03/16 18:10, Zane Bitter wrote: I'm in favour of some sort of variable-based implementation for a few reasons. One is that (5) seems

Re: [openstack-dev] [Fuel] branching Mitaka April 6, 2016

Hi Sergey, According to Matthew Mosesohn the plan is to delay branching of detach-* plugins. The only plugin scheduled for branching tomorrow seems to be a fuel-plugin-murano. -- Igor Belikov Fuel CI Engineer ibeli...@mirantis.com > On 04 Apr 2016, at 15:11, Sergii Golovatiuk wrote: > > What

[openstack-dev] [nova] FYI: Removing default flavors from nova

Just as a heads up, we are removing the default flavors from nova in this patch: https://review.openstack.org/#/c/300127/ Since long ago, Nova's default flavors were baked in at the database migration level. Now that we have moved them to another database entirely, this means we have to migrate

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

penstack-meeting4. > > https://wiki.openstack.org/wiki/Meetings/PuppetOpenStack > > As usual, free free to bring topics in this etherpad: > https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160405 > > We'll also have open discussion for bugs & reviews, so anyo

[openstack-dev] [all][trove] Trove bug scrub

If you are subscribed to bug notifications from Trove, you'd have received a lot of email from me over the past couple of days as I've gone through the LP bug list for the project and attempted to do some spring cleaning. Here's (roughly) what I've tried to do: -many bugs that have been in

[openstack-dev] [nova] post-copy live migration

Hi, We are working on the possibility of including post-copy live migration into Nova (https://review.openstack.org/#/c/301509/) At libvirt level, post-copy live migration works as follow: - Start live migration with a post-copy enabler flag (VIR_MIGRATE_POSTCOPY). Note this does not mean

Re: [openstack-dev] [nova] post-copy live migration

On Tue, Apr 05, 2016 at 05:17:41PM +0200, Luis Tomas wrote: > Hi, > > We are working on the possibility of including post-copy live migration into > Nova (https://review.openstack.org/#/c/301509/) > > At libvirt level, post-copy live migration works as follow: > - Start live migration with a

[openstack-dev] [osc] Meeting time preferences for OSC team

Here are my preferences: 1. even week: E.1 or E.4 2. odd week: O.3 Thanks, Richard > Dear All, > > This is regarding deciding meeting time for OSC team to facilitate > appropriate time for APAC guys. > We are planning to have meeting on alternate weeks for this purpose. > > Some of the suggest

Re: [openstack-dev] [TripleO] FreeIPA integration

Yeah, and they just deprecated vendor data plugins too, which eliminates my other workaround. :/ We need to really discuss this problem at the summit and get a viable path forward. Its just getting worse. :/ Thanks, Kevin From: Juan Antonio Osorio [jaosor...@gma

Re: [openstack-dev] [neutron][api] advanced search criteria

On Mon, Apr 4, 2016 at 7:36 PM, Armando M. wrote: > > > On 4 April 2016 at 17:08, Jay Pipes wrote: >> >> On 04/04/2016 06:57 PM, Ihar Hrachyshka wrote: >>> >>> - why do we even need to control those features with configuration >>> options? can we deprecate and remove them? >> >> >> This would be

Re: [openstack-dev] [osc] Meeting time preferences for OSC team

I am OK with any of the proposed times. stevemar From: Richard Theis To: Date: 2016/04/05 11:46 AM Subject:[openstack-dev] [osc] Meeting time preferences for OSC team Here are my preferences: 1. even week: E.1 or E.4 2. odd week: O.3 Thanks, Richard > Dear All, > > This

Re: [openstack-dev] [nova] post-copy live migration

On 05/04/16 16:33, Daniel P. Berrange wrote: On Tue, Apr 05, 2016 at 05:17:41PM +0200, Luis Tomas wrote: Hi, We are working on the possibility of including post-copy live migration into Nova (https://review.openstack.org/#/c/301509/) At libvirt level, post-copy live migration works as follow:

[openstack-dev] [TripleO] Austin summit sessions

All, As discussed briefly today in our weekly meeting, I've started this etherpad: https://etherpad.openstack.org/p/newton-tripleo-sessions We have two fishbowl sessions and 3 working sessions, plus a half-day contributor meetup. Please can everyone dump ideas of what topics you'd like to cover

Re: [openstack-dev] [TripleO] FreeIPA integration

I was planning to bring it up informally for TripleO. But it would be cool to have a slot to talk about this. BR On 5 Apr 2016 18:51, "Fox, Kevin M" wrote: > Yeah, and they just deprecated vendor data plugins too, which eliminates > my other workaround. :/ > > We need to really discuss this prob

Re: [openstack-dev] [neutron] OVSDB native interface as default in gate jobs

Russell Bryant wrote: > because they are related to two different command line utilities > (ovs-vsctl vs ovs-ofctl) that speak two different protocols (OVSDB vs > OpenFlow) that talk to two different daemons on the system (ovsdb-server vs > ovs-vswitchd) ? True, they influence two different daemon

Re: [openstack-dev] [ironic] [inspector] Proposing Anton Arefiev (aarefiev) for ironic-inspector-core

+1 from me :) // jim > On Apr 5, 2016, at 03:24, Dmitry Tantsur wrote: > > Hi! > > I'd like to propose Anton to the ironic-inspector core reviewers team. His > stats are pretty nice [1], he's making meaningful reviews and he's pushing > important things (discovery, now tempest). > > Member

Re: [openstack-dev] [bifrost][ironic][release] missing build artifacts

> On Apr 2, 2016, at 05:46, Doug Hellmann wrote: > > Excerpts from Julia Kreger's message of 2016-04-01 18:21:24 -0400: >>> On Fri, Apr 1, 2016 at 4:48 PM, Doug Hellmann wrote: >>> >>> Excerpts from Doug Hellmann's message of 2016-04-01 16:25:07 -0400: Ironic/Bifrost team, >> >>> I

Re: [openstack-dev] [kloudbuster] authorization failed problem

Akshay, Note that version 6 is now released so please use the official image from the OpenStack App Catalog and update your code to latest. The doc has also been updated, you might want to have a look at the new arch section and gallery - those should help you with the questions you had below

Re: [openstack-dev] [neutron] OVSDB native interface as default in gate jobs

On Tue, Apr 5, 2016 at 12:35 PM, Sean M. Collins wrote: > Russell Bryant wrote: >> because they are related to two different command line utilities >> (ovs-vsctl vs ovs-ofctl) that speak two different protocols (OVSDB vs >> OpenFlow) that talk to two different daemons on the system (ovsdb-server v

Re: [openstack-dev] [neutron] OVSDB native interface as default in gate jobs

On Tue, Apr 5, 2016 at 12:57 PM, Assaf Muller wrote: > On Tue, Apr 5, 2016 at 12:35 PM, Sean M. Collins > wrote: > > Russell Bryant wrote: > >> because they are related to two different command line utilities > >> (ovs-vsctl vs ovs-ofctl) that speak two different protocols (OVSDB vs > >> OpenFlo

Re: [openstack-dev] [all][trove] Trove bug scrub

On 05/04/16 15:15 +, Amrith Kumar wrote: If you are subscribed to bug notifications from Trove, you’d have received a lot of email from me over the past couple of days as I’ve gone through the LP bug list for the project and attempted to do some spring cleaning. Here’s (roughly) what I’ve

[openstack-dev] [oslo] oslo.context and name fields

I was trying to clean up the divergent logging definitions in devstack as part of scrubbing out 'tenant' references - https://review.openstack.org/#/c/301801/ and in doing so stumbled over the fact that the extremely useful project_name and user_name fields are not in base oslo.context. https://gi

Re: [openstack-dev] [sahara][release] missing build artifacts

On 04/05/2016 03:56 AM, Thierry Carrez wrote: We seem to have a sahara-extra build alright: http://tarballs.openstack.org/sahara-extra/ Please ignore the noise :) ah, excellent! thanks for the clarification Thierry regards, mike

Re: [openstack-dev] [oslo] oslo.context and name fields

Excerpts from Sean Dague's message of 2016-04-05 14:31:46 -0400: > I was trying to clean up the divergent logging definitions in devstack > as part of scrubbing out 'tenant' references - > https://review.openstack.org/#/c/301801/ and in doing so stumbled over > the fact that the extremely useful pr

[openstack-dev] [nova] Launchpad bug spring cleaning day Monday 4/18

We're going to have a day of just cleaning out the launchpad bugs for Nova on Monday 4/18. This isn't a bug squashing day where people are proposing patches and the core team is reviewing them. This is purely about cleaning the garbage out of launchpad. Markus Zoeller has a nice dashboard we

Re: [openstack-dev] [monasca][release] missing build artifacts

Thanks Doug, Thierry and Davanum. Sorry about the all the extra work that I've caused. It sounds like all Python projects/deliverables are in reasonable shape, but if not, please let me know. Not sure what we should do about the jars at this point. We had started to discuss a plan to manually

Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?

Hi all, Thanks for your inputs. We discussed this proposal in our team meeting [1], and we all agreed to support an option to remove the need of floating IPs. A blueprint was created for implementing this feature: https://blueprints.launchpad.net/magnum/+spec/bay-with-no-floating-ips . Please f

Re: [openstack-dev] [neutron] [ipam] Migration to pluggable IPAM

I think the only thing standing in our way is this bug [1]. Ryan Tidwell and I are working on this. Carl [1] https://bugs.launchpad.net/neutron/+bug/1543094 On Mon, Apr 4, 2016 at 3:48 PM, John Belamaric wrote: > I was on vacation last week so I am just seeing this now. I agree that now > tha

Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?

Egor, I agree with you. I think Magnum should support another option to connect a bay to an existing neutron private network instead of creating one. If you like, we can discuss it separately in our next team meeting or in the design summit. Best regards, Hongbin From: Guz Egor [mailto:guz_e...

Re: [openstack-dev] [monasca][release] missing build artifacts

On Tue, Apr 5, 2016, at 11:56 AM, Hochmuth, Roland M wrote: > Thanks Doug, Thierry and Davanum. Sorry about the all the extra work that > I've caused. > > It sounds like all Python projects/deliverables are in reasonable shape, > but if not, please let me know. > > Not sure what we should do abo

Re: [openstack-dev] [osc] Meeting time preferences for OSC team

On Tue, Apr 5, 2016 at 10:44 AM, Richard Theis wrote: > Here are my preferences: > > 1. even week: E.1 or E.4 > 2. odd week: O.3 > I really don't want to go against the API-WG but want to keep it on Thursday if possible: E.4 O.3 Thanks for doing this Sheel dt -- Dean Troyer dtro...@gmail.c

Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?

Hi Monty, Thanks for your guidance. I have appended your inputs to the blueprint [1]. [1] https://blueprints.launchpad.net/magnum/+spec/bay-with-no-floating-ips Best regards, Honbgin -Original Message- From: Monty Taylor [mailto:mord...@inaugust.com] Sent: March-31-16 1:18 PM To: opens

Re: [openstack-dev] [oslo] oslo.context and name fields

Sean, I cannot speak to historically why there were not there, but I am working through the app-agnostic-logging-parameters blueprint [1] right now and it's very related to this. As part of this work I would be reviewing attributes that are more commonly used in subclassed context objects for inc

[openstack-dev] [nova][glance] Proposal to remove `nova image-*` commands from novaclient

As we discuss the glance v2 spec for nova, questions are coming up around what to do about the nova images API which is a proxy for glance v1. I don't want to add glance v2 support to the nova API since that's just more proxy gorp. I don't think we can just make the nova images API fail if we

Re: [openstack-dev] [oslo] oslo.context and name fields

Cool. Great. In looking at this code a bit more I think we're missing out on some commonality by the fact that this nice bit of common parsing - https://github.com/openstack/oslo.context/blob/c63a359094907bc50cc5e1be716508ddee825dfa/oslo_context/context.py#L138-L161 is actually hidden behind a fac

Re: [openstack-dev] [nova][glance] Proposal to remove `nova image-*` commands from novaclient

On Apr 5, 2016 2:49 PM, "Matt Riedemann" wrote: > > As we discuss the glance v2 spec for nova, questions are coming up around what to do about the nova images API which is a proxy for glance v1. > > I don't want to add glance v2 support to the nova API since that's just more proxy gorp. > > I don'

Re: [openstack-dev] [all][trove] Trove bug scrub

Thanks Amrith. I'll follow your lead and do some triaging as well. We should organize bug triage days to make this process easier next time. 2016-04-05 14:44 GMT-03:00 Flavio Percoco : > On 05/04/16 15:15 +, Amrith Kumar wrote: > >> If you are subscribed to bug notifications from Trove, you

Re: [openstack-dev] [all][trove] Trove bug scrub

From: Victoria Martínez de la Cruz [mailto:victo...@vmartinezdelacruz.com] Sent: Tuesday, April 05, 2016 4:35 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [all][trove] Trove bug scrub Thanks Amrith. I'll follow your lead and do some triaging

Re: [openstack-dev] [nova][glance] Proposal to remove `nova image-*` commands from novaclient

As a recent newcomer to using our client libraries, my only real objection to this plan is that our client libraries as a mess [1][2]. The interfaces we expect users to use are quite different for basic things like initial auth between the various clients, and by introducing another library we insi

Re: [openstack-dev] [nova][glance] Proposal to remove `nova image-*` commands from novaclient

  -Original Message- From: Michael Still Reply: OpenStack Development Mailing List (not for usage questions) Date: April 5, 2016 at 16:11:05 To: OpenStack Development Mailing List (not for usage questions) Subject:  Re: [openstack-dev] [nova][glance] Proposal to remove `nova image-*`

Re: [openstack-dev] [nova][glance] Proposal to remove `nova image-*` commands from novaclient

On Wed, Apr 6, 2016 at 7:28 AM, Ian Cordasco wrote: > > > -Original Message- > From: Michael Still > Reply: OpenStack Development Mailing List (not for usage questions) < > openstack-dev@lists.openstack.org> > Date: April 5, 2016 at 16:11:05 > To: OpenStack Development Mailing List (not

Re: [openstack-dev] [nova][glance] Proposal to remove `nova image-*` commands from novaclient

  -Original Message- From: Michael Still Reply: Michael Still Date: April 5, 2016 at 16:30:36 To: Ian Cordasco CC: OpenStack Development Mailing List (not for usage questions) Subject:  Re: [openstack-dev] [nova][glance] Proposal to remove `nova image-*` commands from novaclient > S

Re: [openstack-dev] [all][trove] Trove bug scrub

++! 2016-04-05 17:54 GMT-03:00 Amrith Kumar : > > > *From:* Victoria Martínez de la Cruz [mailto: > victo...@vmartinezdelacruz.com] > *Sent:* Tuesday, April 05, 2016 4:35 PM > *To:* OpenStack Development Mailing List (not for usage questions) < > openstack-dev@lists.openstack.org> > *Subject:* Re

Re: [openstack-dev] [oslo] oslo.context and name fields

I have created a version that use constructor arguments. [5] I will review in more detail across projects the use of keystone middleware to see if we can utilize a constructor environment attribute to simply constructor usage. [5] https://review.openstack.org/301918 Ronald Bradford Web Site: htt

Re: [openstack-dev] [nova][glance] Proposal to remove `nova image-*` commands from novaclient

I think in the interest of supporting the OSC effort, I am with deprecating the CLI stuff (possibly glanceclient too -- BUT in a different thread). I believe removing the bindings/modules that support possibly OSC and other libs might be lot trickier. (nova proxy stuff for glance may be an except

Re: [openstack-dev] [monasca][release] missing build artifacts

Thanks for the pointer Clark. We will look into using that, although we were running out of time on the Mitaka release to get something like that implemented. Craig Bryant is in the process of manually updating the versions in the pom files to match the Mitaka tags. A couple of reviews are avai

[openstack-dev] [nova] Minimal secure identification of a new VM

We have a use case where we want to register a newly spawned Virtual machine with an identity provider. Heat also has a need to provide some form of Identity for a new VM. Looking at the set of utilities right now, there does not seem to be a secure way to do this. Injecting files does not p

Re: [openstack-dev] [tempest] Implementing tempest test for Keystone federation functional tests

On Tue, Apr 5, 2016 at 11:53 AM, Minying Lu wrote: > Thank you for your awesome feedbacks! > > >> Another option is to add those tests to keystone itself (if you are not >>> including tests that triggers other components APIs). See >>> https://blueprints.launchpad.net/keystone/+spec/keystone-temp

[openstack-dev] [magnum] Collaborating topics for Magnum design summit

Hi team, As mentioned in the team meeting, Magnum team is using an etherpad [1] to collaborate topics for design summit. If you interest to join us in the Newton design summit, I would request your inputs in the etherpad. In particular, you can do the followings: * Propose new topics that you wa

Re: [openstack-dev] [nova][glance] Proposal to remove `nova image-*` commands from novaclient

On Tue, Apr 5, 2016 at 4:35 PM, Ian Cordasco wrote: > The goal is to centralize the server expertise and have that be combined > with the folks who know how to better design a library for a good developer > experience (kind of like with osc). That said, I think the SDK would have > gained more tr

[openstack-dev] [openstack][release][keystone] Mitaka RC3 available

Hello everyone, Due to a release-critical issue spotted in Keystone during RC2 testing, a new release candidate was created for Mitaka. You can find the RC3 source code tarball at: https://tarballs.openstack.org/keystone/keystone-9.0.0.0rc3.tar.gz Unless new release-critical issues are found tha

Re: [openstack-dev] [Neutron] Newton blueprints call for action

Armando M. wrote: > I would like to understand if these need new owners (both assignees and > approvers). Code submitted [5,6] has not been touched in a while, and > whilst I appreciate people have been busy focussing on Mitaka (myself > included), the Newton master branch has been open for a while

Re: [openstack-dev] [nova] Minimal secure identification of a new VM

Adam Young wrote: We have a use case where we want to register a newly spawned Virtual machine with an identity provider. Heat also has a need to provide some form of Identity for a new VM. Looking at the set of utilities right now, there does not seem to be a secure way to do this. Injecting

  1   2   >