Re: [openstack-dev] what permission is required to create a Keystone trust

On Thu, Sep 1, 2016 at 5:54 AM, Matt Jia wrote: > Hi, > > I am experimenting the Keystone Trusts feature with a script which creates a > trust between two users. > > import keystoneclient.v3 as keystoneclient > #import swiftclient.client as swiftclient > > > auth_url_v3 = 'http:/xxxt.com:5000/v3/'

Re: [openstack-dev] Cloud Reliability and Resilience for OpenStack (Fault Injection, Chaos Engineering, and Google SRE)

Hi Jorge, Rally team is working on feature called "Hooks". "Hooks" are going to allow to use Rally to run workloads and inject any actions (including using existing Chaos frameworks) Here is the patch: https://review.openstack.org/#/c/352276/ Here is merged spec: https://github.com/openstack/rall

[openstack-dev] [kolla][documentation] Docimpact bugs

Hello, We have around 13 doc bugs [1] created for features which required documentation. Most of the bugs are not attended after the feature got merged. I have moved all the bugs to o-1. If you think any of this can be completed within rc1 timeframe, feel free to move it back to the current milest

Re: [openstack-dev] [tripleo] FFE request for Ceph RGW integration

On 09/01/2016 02:11 AM, Giulio Fidente wrote: On 08/30/2016 10:50 PM, Steven Hardy wrote: On Tue, Aug 30, 2016 at 03:25:30PM -0400, Emilien Macchi wrote: Here's my 2 cents: The patch in puppet-ceph has been here for long time now and it still doesn't work (recent update of today, puppet-ceph i

[openstack-dev] [Glance] Gerrit is blocking the workflow with -2 for reason

Hi all, As it seems by the "Improving help text for *" string of patches like [0][1] that the Glance core group is willing to get around -2s by abandoning, reproposing and merging just because not all of us are around in US office hours, I'd like to propose that we would just remove the -2 right f

[openstack-dev] [kolla] Barcelona Summit Friday Scheduling

Hey folks, Summit space is a bit more constrained compared to Austin and there are more teams to accommodate. Also there are no full day contributor meetups. As a result, unlike past summits Koalleans have participated in, Friday is being scheduled by the foundation for workroom sessions and

Re: [openstack-dev] Cloud Reliability and Resilience for OpenStack (Fault Injection, Chaos Engineering, and Google SRE)

Hi Jorge, Reliability testing automation is the thing that OpenStack Performance team [1] is working right now. The whole solution will consist of: * Fault injection library os-failures [2] that provides an API to do different kind of faults on different OpenStack clouds. The lib is currently und

[openstack-dev] [vitrage] blueprint proposal: graph log inspector

Dear all, I proposed a new blueprint about graph log inspector on gerrit [1] and would be happy to receive everyone's comments. [1] https://review.openstack.org/#/c/364140

Re: [openstack-dev] [keystone][nova][neutron][all] Rolling upgrades: database triggers and oslo.versionedobjects

On 31 August 2016 at 01:57, Clint Byrum wrote: > > > It's simple, these are the holy SQL schema commandments: > > Don't delete columns, ignore them. > Don't change columns, create new ones. > When you create a column, give it a default that makes sense. I'm sure you're aware of this but I think i

Re: [openstack-dev] [kuryr] Python 3 usage and kuryr-kubernetes

Hi, Le 30/08/2016 à 16:39, Antoni Segura Puimedon a écrit : a) Work with the OpenStack distributions to ensure python3.5 support is reached soon for Kuryr and its dependencies (some listed below): * babel * oslo.concurrency * oslo.config * oslo.log * oslo.utils * pbr * pyroute2

Re: [openstack-dev] [vitrage] inspecting external openstack environment

Thanks for explanation. I'll give it a try. Answer to BTW, it is Liberty on Ubuntu 14.04 deployed by Fuel 8.0. -- Yujun On Wed, Aug 31, 2016 at 2:42 PM Afek, Ifat (Nokia - IL) wrote: > Hi Yujun, > > Using Vitrage for an external openstack environment should be possible, > but it has never been

Re: [openstack-dev] [all][massively distributed][architecture]Coordination between actions/WGs

> What is the REST API for tricircle? > When looking at the github I see: > ''Documentation: TBD'' > Getting a feel for its REST API would really be helpful in determine how > much of a proxy/request router it is vs being an actual API. I don't > really want/like a proxy/request router (if that was

[openstack-dev] [TripleO] FFE: TLS everywhere in the overcloud

Hello, I've been working on TLS everywhere in the majority of this newton cycle. And proposed this blueprint https://review.openstack.org/#/c/282307/ (which has been approved in launchpad) somewhere around May. There has been a lot of work trying to tackle blockers and doing a lot of pre-work tha

Re: [openstack-dev] [kolla] Requirement for bug when reno is present

sdake kindly took the time to explain the release process. Logs are here: http://eavesdrop.openstack.org/irclogs/%23openstack-kolla/%23openstack-kolla.2016-09-01.log.html#t2016-09-01T09:06:49 On 30/08/16 20:31, Christian Berendt wrote: On 30 Aug 2016, at 12:42, Paul Bourke wrote: Do people f

Re: [openstack-dev] Upstream - Barcelona

yes...Even I have not seen any emails for upstream tasks @ BarcelonaI guess we might have missed it... Thanks Swami On Thu, Sep 1, 2016 at 9:23 AM, Adam Lawson wrote: > I seemed to have missed the thread where upstream opps we're being > announced and/or opened. Who do I contact to get in o

Re: [openstack-dev] [Fuel] Getting rid of ISO

This is so awesome! Thanks! On Tue, Aug 16, 2016 at 4:30 PM Jay Pipes wrote: > On 08/16/2016 04:58 AM, Vladimir Kozhukalov wrote: > > Dear colleagues, > > > > We finally have working custom deployment job that deploys Fuel admin > > node using online RPM repositories (not ISO) on vanilla Centos

Re: [openstack-dev] [all][massively distributed][architecture]Coordination between actions/WGs

Clint Byrum wrote: > [...] > I think it's about time we get some Architecture WG meetings started, > and put "Document RPC design" on the agenda. +1 Anything blocking you ? Let me know where/if I can help. -- Thierry Carrez (ttx) _

[openstack-dev] [openstack-infra][all] Status update of the InfraCloud

Hi there We would like to write an update about the status of the InfraCloud ( if you never heard of it, it's essentially a bunch of hardware donated by HPE to the project to run an OpenStack cloud for CI testing. More info at http://docs.openstack.org/infra/system-config/infra-cloud.html ). We d

Re: [openstack-dev] [Glance] Gerrit is blocking the workflow with -2 for reason

-Original Message- From: Erno Kuvaja Reply: OpenStack Development Mailing List (not for usage questions) Date: September 1, 2016 at 02:51:42 To: OpenStack Development Mailing List (not for usage questions) Subject:  [openstack-dev] [Glance] Gerrit is blocking the workflow with -2 for rea

Re: [openstack-dev] [Neutron][networking-sfc] need help on requesting release for networking-sfc

Armando M. wrote: On 31 August 2016 at 17:31, Cathy Zhang wrote: CC OpenStack alias. From: Cathy Zhang Sent: Wednesday, August 31, 2016 5:19 PM To: Armando Migliaccio; Ihar Hrachyshka; Cathy Zhang Subject: need help on requesting release for networking-sfc Hi Armando/Ihar, I would l

[openstack-dev] [Murano] Changes in Core Library interface

Hi folks, starting from the Newton release Murano supports multi-region applications deployment [1] and this feature required some changes in the Core Library design. Specifically after this patch references to all region-specific resources are held in the CloudRegion class instead of the Env

Re: [openstack-dev] [Glance] Gerrit is blocking the workflow with -2 for reason

On 01/09/16 08:50 +0100, Erno Kuvaja wrote: Hi all, As it seems by the "Improving help text for *" string of patches like [0][1] that the Glance core group is willing to get around -2s by abandoning, reproposing and merging just because not all of us are around in US office hours, I'd like to pr

[openstack-dev] [murano][app-catalog] FFE request for dashboard reorg

I would like to request an FFE for murano/appcatalog-dashboard-reorg  https://blueprints.launchpad.net/murano/+spec/catalog-dashboard-reorg A little back story: we’ve agreed to start merging murano-dashboard and app-catalog-ui under the same structure back in Austin. For app-catalog-ui the proces

[openstack-dev] [new][cinder] os-brick 1.6.1 release (newton)

We are exuberant to announce the release of: os-brick 1.6.1: OpenStack Cinder brick library for managing local volume attaches This release is part of the newton stable release series. With source available at: http://git.openstack.org/cgit/openstack/os-brick With package available at:

Re: [openstack-dev] [TripleO] FFE request for Ironic composable services

On 08/30/2016 10:20 AM, Dmitry Tantsur wrote: Hi all! Bare metal provisioning is a hot topic right now. These services are also required for Dan's heat-driven undercloud work. The majority of changes has landed already, but there a few changes waiting on puppet-ironic changes. The feature is lo

Re: [openstack-dev] Upstream - Barcelona

M Ranga Swami Reddy wrote: > yes...Even I have not seen any emails for upstream tasks @ > BarcelonaI guess we might have missed it... > > Thanks > Swami > > On Thu, Sep 1, 2016 at 9:23 AM, Adam Lawson > wrote: > > I seemed to have missed the thread where upstre

Re: [openstack-dev] [openstack-infra][all] Status update of the InfraCloud

This is awesome stuff. Thanks to all involved and to HPE for the hardware :-) On Thu, Sep 1, 2016 at 9:12 PM, Ricardo Carrillo Cruz < ricardo.carrillo.c...@gmail.com> wrote: > Hi there > > We would like to write an update about the status of the InfraCloud ( if > you never heard of it, it's essen

Re: [openstack-dev] [keystone][nova][neutron][all] Rolling upgrades: database triggers and oslo.versionedobjects

So as the person who drove the rolling upgrade requirements into keystone in this cycle (because we have real customers that need it), and having first written the keystone upgrade process to be “versioned object ready” (because I assumed we would do this the same as everyone else), and subseque

Re: [openstack-dev] [all][massively distributed][architecture]Coordination between actions/WGs

May I suggest to open one (or more) thread(s) with the correct subject(s)? There are at least three points discussed here: - one related to the proposal of the Massively distributed group - one related to the Architecture WG with the communication issue between services (RPC+Rabbit MQ, REST AP

Re: [openstack-dev] [all][massively distributed][architecture]Coordination between actions/WGs

+1000 for this proposal. On Thu, Sep 1, 2016 at 2:47 PM, wrote: > May I suggest to open one (or more) thread(s) with the correct subject(s)? > > There are at least three points discussed here: > > - one related to the proposal of the Massively distributed group > - one related to the Architectur

[openstack-dev] [Murano] FFE for dependency-driven multi-step resource deallocation

Hi all, I'd like to request a feature freeze exception for dependency-driven multi-step resource deallocation[0]. We've merged an initial commit for it [1] and a spec[2]. That's what we have on review [3]. The of patches on review is about bugs related to this feature, and only one add some new fun

Re: [openstack-dev] [all][massively distributed][architecture]Coordination between actions/WGs

On Wed, Aug 31, 2016 at 6:02 PM, Clint Byrum wrote: > Excerpts from Ian Wells's message of 2016-08-31 12:30:45 -0700: >> On 31 August 2016 at 10:12, Clint Byrum wrote: >> >> > Excerpts from Duncan Thomas's message of 2016-08-31 12:42:23 +0300: >> > > On 31 August 2016 at 11:57, Bogdan Dobrelya >

Re: [openstack-dev] [all][massively distributed][architecture]Coordination between actions/WGs

On 31 August 2016 at 22:30, Ian Wells wrote: > On 31 August 2016 at 10:12, Clint Byrum wrote: > >> Excerpts from Duncan Thomas's message of 2016-08-31 12:42:23 +0300: >> > Is there a writeup anywhere on what these issues are? I've heard this >> > sentiment expressed multiple times now, but witho

Re: [openstack-dev] [keystone][nova][neutron][all] Rolling upgrades: database triggers and oslo.versionedobjects

On Thu, Aug 25 at 13:13 -0400, Steve Martinelli wrote: > The keystone team is pursuing a trigger-based approach to support rolling, > zero-downtime upgrades. The proposed operator experience is documented here: > > http://docs.openstack.org/developer/keystone/upgrading.html > I wanted to menti

Re: [openstack-dev] [all][massively distributed][architecture]Coordination between actions/WGs

On Wed, Aug 31, 2016 at 3:30 PM, Ian Wells wrote: > On 31 August 2016 at 10:12, Clint Byrum wrote: >> >> Excerpts from Duncan Thomas's message of 2016-08-31 12:42:23 +0300: >> > On 31 August 2016 at 11:57, Bogdan Dobrelya >> > wrote: >> > >> > > I agree that RPC design pattern, as it is implemen

Re: [openstack-dev] [keystone][nova][neutron][all] Rolling upgrades: database triggers and oslo.versionedobjects

On Wed, Aug 31 at 17:18 -0500, Monty Taylor wrote: > > Nova and Neutron have an approach for this. It may or may not be ideal - > but it exists right now. While it can be satisfying to discount the > existing approach and write a new one, I do not believe that is in the > best interests of OpenSta

Re: [openstack-dev] [nova] cells v2 next steps

On 8/31/2016 8:33 PM, Matt Riedemann wrote: On 8/31/2016 1:44 PM, Matt Riedemann wrote: Just to recap a call with Laski, Sean and Dan, the goal for the next 24 hours with cells v2 is to get this nova change landed: https://review.openstack.org/#/c/356138/ That depends on a set of grenade chang

Re: [openstack-dev] what permission is required to create a Keystone trust

Hi, Matt! The issue is most probably in the absence of roles being trusted, which are required to create a trust. On 01.09.2016 06:54, Matt Jia wrote: Hi, I am experimenting the Keystone Trusts feature with a script which creates a trust between two users. import keystoneclient.v3 as ke

Re: [openstack-dev] [Glance] Gerrit is blocking the workflow with -2 for reason

On 9/1/16, 7:31 AM, "Flavio Percoco" wrote: >On 01/09/16 08:50 +0100, Erno Kuvaja wrote: >>Hi all, >> >>As it seems by the "Improving help text for *" string of patches like >>[0][1] that the Glance core group is willing to get around -2s by >>abandoning, reproposing and merging just because not

[openstack-dev] [keystone] new core reviewer (rderose)

I want to welcome Ron De Rose (rderose) to the Keystone core team. In a short time Ron has shown a very positive impact. Ron has contributed feature work for shadowing LDAP and federated users, as well as enhancing password support for SQL users. Implementing these features and picking up various b

Re: [openstack-dev] [keystone][nova][neutron][all] Rolling upgrades: database triggers and oslo.versionedobjects

On 08/31/2016 06:18 PM, Monty Taylor wrote: I said this the other day in the IRC channel, and I'm going to say it again here. I'm going to do it as bluntly as I can - please keeping in mind that I respect all of the humans involved. I think this is a monstrously terrible idea. There are MANY

Re: [openstack-dev] [keystone] new core reviewer (rderose)

On Thu, Sep 1, 2016 at 9:44 AM, Steve Martinelli wrote: > I want to welcome Ron De Rose (rderose) to the Keystone core team. In a > short time Ron has shown a very positive impact. Ron has contributed > feature work for shadowing LDAP and federated users, as well as enhancing > password support f

Re: [openstack-dev] [keystone] new core reviewer (rderose)

+1! He has been doing some great work. Welcome to the team, Ron! On Thu, Sep 1, 2016 at 9:44 AM, Steve Martinelli wrote: > I want to welcome Ron De Rose (rderose) to the Keystone core team. In a > short time Ron has shown a very positive impact. Ron has contributed > feature work for shadowing

Re: [openstack-dev] [keystone] new core reviewer (rderose)

Welcome, Ron! Henry > On 1 Sep 2016, at 15:44, Steve Martinelli wrote: > > I want to welcome Ron De Rose (rderose) to the Keystone core team. In a short > time Ron has shown a very positive impact. Ron has contributed feature work > for shadowing LDAP and federated users, as well as enhancing

Re: [openstack-dev] [keystone] new core reviewer (rderose)

On Thu, Sep 01 at 10:44 -0400, Steve Martinelli wrote: > > Thanks for all your hard work Ron, we sincerely appreciate it. > Contrats! Well deserved for sure! -- David Stanek web: http://dstanek.com blog: http://traceback.org

Re: [openstack-dev] [keystone][nova][neutron][all] Rolling upgrades: database triggers and oslo.versionedobjects

On 09/01/2016 08:29 AM, Henry Nash wrote: From a purely keystone perspective, my gut feeling is that actually the trigger approach is likely to lead to a more robust, not less, solution - due to the fact that we solve the very specific problems of a given migration (i.e. need to keep column A

Re: [openstack-dev] [keystone][nova][neutron][all] Rolling upgrades: database triggers and oslo.versionedobjects

On 09/01/2016 09:45 AM, David Stanek wrote: > On Thu, Aug 25 at 13:13 -0400, Steve Martinelli wrote: >> The keystone team is pursuing a trigger-based approach to support rolling, >> zero-downtime upgrades. The proposed operator experience is documented here: >> >> http://docs.openstack.org/develo

Re: [openstack-dev] [keystone] new core reviewer (rderose)

Ronald, congrats, well deserved! Welcome aboard! On Thu, Sep 1, 2016 at 11:56 AM, David Stanek wrote: > On Thu, Sep 01 at 10:44 -0400, Steve Martinelli wrote: > > > > Thanks for all your hard work Ron, we sincerely appreciate it. > > > > Contrats! Well deserved for sure! > > -- > David Stanek >

Re: [openstack-dev] [oslo] pymysql change in error formatting has broken exception handing in oslo.db

> upstream issue: > > https://github.com/PyMySQL/PyMySQL/issues/507 A fix for this was merged in pymysql 0.7.8. --diana __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists

Re: [openstack-dev] [keystone] new core reviewer (rderose)

On 09/01/2016 10:44 AM, Steve Martinelli wrote: I want to welcome Ron De Rose (rderose) to the Keystone core team. In a short time Ron has shown a very positive impact. Ron has contributed feature work for shadowing LDAP and federated users, as well as enhancing password support for SQL users.

Re: [openstack-dev] [manila] [security] [tc] Add the vulnerability:managed tag to Manila

Thanks fungi. I misunderstood the full scope of the requirements for vulnerability management and since we don't yet have volunteers willing to perform all the required duties, I'm going to withdraw the tag request. As soon as interested community members step up to take on the responsibilitie

Re: [openstack-dev] [tripleo] Testing optional composable services in the CI

On Thu, Aug 25, 2016 at 9:16 AM, Steven Hardy wrote: > On Wed, Aug 17, 2016 at 07:20:59AM -0400, James Slagle wrote: >> On Wed, Aug 17, 2016 at 4:04 AM, Dmitry Tantsur wrote: >> > However, the current gate system allows to run jobs based on files >> > affected. >> > So we can also run a scenario

Re: [openstack-dev] [keystone][nova][neutron][all] Rolling upgrades: database triggers and oslo.versionedobjects

> So that is fine. However, correct me if I'm wrong but you're > proposing just that these projects migrate to also use a new service > layer with oslo.versionedobjects, because IIUC Nova/Neutron's > approach is dependent on that area of indirection being present. > Otherwise, if you meant som

Re: [openstack-dev] [all][massively distributed][architecture]Coordination between actions/WGs

This topic of oslo messaging issues has been going on for a long time and the main issue is not the transport itself (each transport has its own limitations) but the code using oslo messaging (e.g. pieces of almost every openstack service). It is relatively easy to write code using oslo messagi

Re: [openstack-dev] Upstream - Barcelona

There are probably limited number of seats to participate in the session this cycle. opps = seats in my messed up way of thinking. //adam *Adam Lawson* AQORN, Inc. 427 North Tatnall Street Ste. 58461 Wilmington, Delaware 19801-2230 Toll-free: (844) 4-AQORN-NOW ext. 101 International: +1 302-387

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

Subject: [all][api] POST /api-wg/news Greetings OpenStack community, Today we were joined by Scott DAngelo (scottda) who has graciously taken over the liaison role for Cinder as Alex Meade steps down. Thanks for stepping up Scott and welcome to the API WG! We also cleaned house today and merge

[openstack-dev] [trove][release] Trove FFE's for Newton

Between some late breaking complications in the gate (on stable branches, now understood and fixes are on the way to being merged) and a desire to have more jobs running in our CI, there are some feature patches that have not landed in N-3. This email is to document that list of feature freez

Re: [openstack-dev] [Glance] Gerrit is blocking the workflow with -2 for reason

Erno, Totally with you on not circumventing the process. I regret the fact that I had to resort to "side-stepping" your -2. But, please let's not look at this incident in isolation. We had to do it considering the circumstances that 1. You were unavailable to remove the -2 2. N-3 milestone is rig

[openstack-dev] [kolla] Feature freeze until we tag rc1

Hello all, With the end of last development milestone newton-3, we will be having a procedural -2 on all features change requests to block merge until rc1 is tagged on September 15th. As a result of this, all changes related to blueprints not tagged for rc1 will have -2. The -2 here does not indi

Re: [openstack-dev] migrate_flavor_data doesn't flavor migrate meta data of VMs spawned during upgrade.

On 8/31/2016 4:17 PM, Dan Smith wrote: Thanks Dan for your response. While I do run that before I start my move to liberty, what I see is that it doesn't seem to flavor migrate meta data for the VMs that are spawned after controller upgrade from juno to kilo and before all computes upgraded from j

Re: [openstack-dev] [tripleo] Feature freeze exception for OVN

On Tue, Aug 30, 2016 at 11:51 AM, Steven Hardy wrote: > On Tue, Aug 30, 2016 at 07:53:07PM +0530, Babu Shanmugam wrote: > > Hi, > > > > The THT patch for OVN [1] has no more dependencies with the recent > merging > > of [2]. The changes in heat templates does not have any impact on the > > existi

Re: [openstack-dev] [keystone] new core reviewer (rderose)

Thanks for the good work. Congrats, Ron! On Thu, Sep 1, 2016 at 12:21 PM, Adam Young wrote: > On 09/01/2016 10:44 AM, Steve Martinelli wrote: > > I want to welcome Ron De Rose (rderose) to the Keystone core team. In a > short time Ron has shown a very positive impact. Ron has contributed > featu

Re: [openstack-dev] migrate_flavor_data doesn't flavor migrate meta data of VMs spawned during upgrade.

On 9/1/2016 12:05 PM, Suresh Vinapamula wrote: On 8/31/2016 4:17 PM, Dan Smith wrote: Thanks Dan for your response. While I do run that before I start my move to liberty, what I see is that it doesn't seem to flavor migrate meta data for the VMs that are spawned after con

Re: [openstack-dev] [keystone][nova][neutron][all] Rolling upgrades: database triggers and oslo.versionedobjects

On 09/01/2016 11:52 AM, Dan Smith wrote: The indirection service is really unrelated to this discussion, IMHO. If you take RPC out of the picture, all you have left is a direct-to-the-database facade to handle the fact that schema has expanded underneath you. As Clint (et al) have said -- desi

[openstack-dev] [Tacker] Abstract interface for VNFC

Hi Tackers, As per this week meeting logs, regarding VNFC BP, I came to know that we need to add abstract interface which is invoked by infra_driver. But as we decided to go with SoftwareDeployment option in this cycle, most of the heat template changes are done by heat translator [1]. I could

[openstack-dev] [Fuel] Newton Feature Freeze

Dear colleagues, I'd like to announce FF for Newton cycle. All features must be merged before 09/02/2016 12:00 AM PST. From this point all patches must refer to medium and higher bugs. If some feature patches are still in progress, please request FF exception for a respective feature. First such

Re: [openstack-dev] [keystone][nova][neutron][all] Rolling upgrades: database triggers and oslo.versionedobjects

On 2016-09-01 10:39:09 -0400 (-0400), Mike Bayer wrote: > On 08/31/2016 06:18 PM, Monty Taylor wrote: [...] > >OpenStack is One Project > > > > > > Nova and Neutron have an approach for this. It may or may not be > > ideal - but it exists right now. While it can be satisfyin

Re: [openstack-dev] [keystone][nova][neutron][all] Rolling upgrades: database triggers and oslo.versionedobjects

Excerpts from Robert Collins's message of 2016-09-01 20:45:22 +1200: > On 31 August 2016 at 01:57, Clint Byrum wrote: > > > > > > It's simple, these are the holy SQL schema commandments: > > > > Don't delete columns, ignore them. > > Don't change columns, create new ones. > > When you create a col

[openstack-dev] [new][congress] python-congressclient 1.5.0 release (newton)

We are frolicsome to announce the release of: python-congressclient 1.5.0: Client for Congress This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/python-congressclient With package available at: https://pypi.python.org/

Re: [openstack-dev] [vitrage] relationship_type in static_datasources

I think you have a point. We can indeed use the templates definitions for the static datasources as well. BTW, I noticed we already have a blueprint for this issue: https://blueprints.launchpad.net/vitrage/+spec/add-direction-to-physical-topology-relationships, but nobody has handled it so far.

Re: [openstack-dev] [keystone][nova][neutron][all] Rolling upgrades: database triggers and oslo.versionedobjects

On Thursday, September 1, 2016, Jeremy Stanley wrote: > > I don't read that at all as suggesting "the problem is solved, go > away" but rather "help us make it better for everyone, don't just > take one project off in a new direction and leave the others > behind." I can clarify. I don't work

[openstack-dev] [neutron][networking-sfc] Unable to create openstack SFC

Hi all, Thanks Vincent for this confimation. I've noticed that error to the team here [1]. I think it could be interesting to update the wiki in order to signal new comer the network requirements for building a chain. @ Cathy: I can create port chain but it just works once for me. After analysing

[openstack-dev] [Congress] Enabling Remote Debugging

HI all - I've been trying to configure remote debugging with PyCharm and DevStack. It looks like some tiny modifications need to be made to the Congress code (3-4 files) to support remote debugging via pydevd. As far as I can tell, support has been added to Keystone, Glance, Nova, and Manilla (and

[openstack-dev] [Neutron] Cutting milestone 3 deliverables

Neutrinos, We are in the process of releasing the deliverables for Newton 3. This means we are in feature freeze and nothing should be approved for merging unless it is release critical, gate blocker, targeted for RC1[1] or has been granted a feature freeze exception [2] on the postmortem. For an

Re: [openstack-dev] [neutron][networking-sfc] Unable to create openstack SFC

Hi Vincent, Yes, there have been some code optimization and bug fixes going into the master branch. I am going to request the Mitaka release today after the patch for fixing the tempest version mismatch issue is merged. I would suggest that you use the Mitaka release. Thanks, Cathy From: Vinc

[openstack-dev] [puppet] Creating a Cloudkitty Puppet module

Hi! At the moment, I don't think theres a Puppet module for the Cloudkitty rating service. I'd like to start the development of this project. What are you thoughts on the matter? -- Guillaume Espanel Objectif Libre www.objectif-libre.com Infrastructure et Formations Linux _

Re: [openstack-dev] [Neutron][networking-sfc] need help on requesting release for networking-sfc

Thanks for all your response. We would like to have the stable branch pulled from a git commit. Shall we use the git hash of that commit for the intended git hash in the release request? I am confused about the following statement in the release guide. "You need to be careful when picking a

Re: [openstack-dev] [puppet] Creating a Cloudkitty Puppet module

On Thu, Sep 1, 2016 at 12:51 PM, Guillaume Espanel wrote: > Hi! > > At the moment, I don't think theres a Puppet module for > the Cloudkitty rating service. I'd like to start the development > of this project. > > What are you thoughts on the matter? > Sounds good. We've put together some documen

Re: [openstack-dev] [puppet] Creating a Cloudkitty Puppet module

Hi Guillaume, You can find all information about how to start a new puppet-module in http://docs.openstack.org/developer/puppet-openstack-guide/new-module.html If you have any question please join us in #puppet-openstack on freenode. 2016-09-01 15:51 GMT-03:00 Guillaume Espanel < guillaume.espa..

Re: [openstack-dev] [puppet] Creating a Cloudkitty Puppet module

Hi Guillaume, This is a great idea! We have a documentation for this process: http://docs.openstack.org/developer/puppet-openstack-guide/new-module.html You'll notice that we have a cookiecutter that will deploy the basic module for you and you'll be able to add the manifests to do deploy Cloudki

[openstack-dev] [new][neutron] python-neutronclient 6.0.0 release (newton)

We are chuffed to announce the release of: python-neutronclient 6.0.0: CLI and Client Library for OpenStack Networking This release is part of the newton release series. With source available at: https://git.openstack.org/cgit/openstack/python-neutronclient With package available at:

[openstack-dev] [new][openstackclient] os-client-config 1.21.1 release (newton)

We are pleased to announce the release of: os-client-config 1.21.1: OpenStack Client Configuation Library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/os-client-config With package available at: https://pypi.pytho

Re: [openstack-dev] [Neutron][networking-sfc] need help on requesting release for networking-sfc

> -Original Message- > From: Cathy Zhang [mailto:cathy.h.zh...@huawei.com] > Sent: Thursday, September 1, 2016 8:03 PM > To: Ihar Hrachyshka ; Armando M. > ; Cathy Zhang > Cc: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [Neutron][network

Re: [openstack-dev] [puppet] Creating a Cloudkitty Puppet module

Jinx! On Thu, Sep 1, 2016 at 12:09 PM Alex Schultz wrote: > On Thu, Sep 1, 2016 at 12:51 PM, Guillaume Espanel > wrote: > > Hi! > > > > At the moment, I don't think theres a Puppet module for > > the Cloudkitty rating service. I'd like to start the development > > of this project. > > > > What

Re: [openstack-dev] [Murano] FFE for dependency-driven multi-step resource deallocation

Garbage collection bp addresses a very important piece of tech debt and is required for app framework to work correctly. Therefore I’m granting this one. ETA for code to be merged is next week. I've also updated topic link to  https://review.openstack.org/#/q/topic:bp/dependency-driven-resource-d

[openstack-dev] [new][oslo] oslo.db 4.13.1 release (newton)

We are tickled pink to announce the release of: oslo.db 4.13.1: Oslo Database library This release is part of the newton stable release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.db With package available at: https://pypi.python.org/pypi/oslo.db Pl

[openstack-dev] [Zun][Higgins] About container image

Hi all, This is a continued discussion about the container image solution in Zun. Currently, when a user request to create a container (i.e. zun create --image ), the Zun compute agent will pull the image from docker hub or a private docker registry (depends on the image prefix). We are investi

Re: [openstack-dev] [all][massively distributed][architecture]Coordination between actions/WGs

On 1 September 2016 at 06:52, Ken Giusti wrote: > On Wed, Aug 31, 2016 at 3:30 PM, Ian Wells wrote: > > > I have opinions about other patterns we could use, but I don't want to push > > my solutions here, I want to see if this is really as much of a problem > as > > it looks and if people concu

Re: [openstack-dev] [Neutron][networking-sfc] need help on requesting release for networking-sfc

Hi Cathy, I haven't done this in openstack before, but what I believe the statement is referring to is that you need to make sure you tag a merged commit, if the topic branch had diverged from master and had to be merged into your master trunk. For example: commit f01595f801e1d78f84b43c111f29

[openstack-dev] [cinder] [nova] API interaction changes overview

Hi All, As we skipped a few meetings and we also reached the N-3 milestone this week I would like to summarise where we are currently with our plans. At the beginning of the Newton cycle we decided to refactor the Cinder API around attach and detach to make Cinder more a standalone module and

Re: [openstack-dev] [Neutron] Cutting milestone 3 deliverables

Neutrinos, Milestone 3 deliverables have been published [1]. Please, help us check the release notes to make sure everything in order and post patches to tidy up the release notes if needed. Some of these reminders are captured in [2], therefore please feel free to help. [3] captures a list of do

[openstack-dev] [nova] Move remove-mox-newton changes to remove-mox-ocata

I've closed the remove-mox-newton blueprint since today is feature freeze and we have two weeks to RC1 for newton. I've created a 'remove-mox-ocata' blueprint to continue this work, so if you have open changes for remove-mox-newton please re-targed those changes to the new blueprint. -- Tha

[openstack-dev] [nova] Move nova-python3-newton changes to goal-python35

We're at feature freeze so this blueprint is closed for newton: https://blueprints.launchpad.net/nova/+spec/nova-python3-newton I've created a blueprint for working on this in ocata: https://blueprints.launchpad.net/nova/+spec/goal-python35 So if you have open changes please start moving them

Re: [openstack-dev] [Neutron][networking-sfc] need help on requesting release for networking-sfc

Hi Mooney, Thank you for your response! I am still not quite sure about this. Anyway we will upload a patch for the release request and put down the git hash of the last commit which should be included in this Mitaka release. The Neutron release team will review it and let us know if there is

Re: [openstack-dev] [Neutron][networking-sfc] need help on requesting release for networking-sfc

Hi Tim, Thank you for your response! From the statement, it does not seem to refer to a merged commit, which does not apply to our case. But you could be right. Anyway we will upload a patch for the release request and put down the git hash of the last commit which should be included in this M

[openstack-dev] [nova] Newton b3 tag is pushed up for review

Booya! https://review.openstack.org/#/c/364600/ It's been a hectic week but a lot got done in the last few days of this release. Especially the focused effort on resource providers and cells v2 these last few days was awesome. 19 blueprints wrapped up in n-3: https://launchpad.net/nova/+mil

Re: [openstack-dev] [nova][keystone] auth for new metadata plugins

On Thu, Sep 1, 2016 at 11:58 AM, Adam Young wrote: > On 08/31/2016 07:56 AM, Michael Still wrote: > > There is a quick sketch of what a service account might look like at > https://review.openstack.org/#/c/363606/ -- I need to do some more > fiddling to get the new option group working, but I cou

Re: [openstack-dev] [Congress] Enabling Remote Debugging

Hi Aimee, Thanks for digging into it! Here¹s my understanding of our conventions (and I¹m happy to hear from others). a. If you think it¹s just a straightforward change with zero to minimal impact on architecture, users, and devs, then it makes sense to file a bug or just submit a patch. b. If y

Re: [openstack-dev] [keystone] new core reviewer (rderose)

Well deserved! Congrats! Best Regards, Dave Chen From: Steve Martinelli [mailto:s.martine...@gmail.com] Sent: Thursday, September 01, 2016 10:44 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [keystone] new core reviewer (rderose) I want to

Re: [openstack-dev] [all][massively distributed][architecture]Coordination between actions/WGs

Hi, Adrien, +1, and the comment in the https://etherpad.openstack.org/p/massively-distributed_WG_description has been updated. - Security management over the WAN: how manage the inter-site communications and edge cloud securely. - Fault tolerant issues (each edge cloud should be able to run

  1   2   >