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

Ed Leafe wrote: > On Mar 9, 2017, at 9:30 PM, Everett Toews wrote: > >>> For those who don't know, Everett and I started the API-WG a few years ago, >> >> Umm...given this statement, I feel I _must_ provide some clarity. >> >> The API WG was started by myself,

Re: [openstack-dev] [api][qa][tc][nova][cinder] Testing of a microversioned world

On Sat, Mar 11, 2017 at 10:45 PM Matt Riedemann wrote: On 3/10/2017 3:02 PM, Andrea Frittoli wrote: > > We had a couple of sessions related to this topic at the PTG [0][1]. > > We agreed that we want to still maintain integration tests only in > Tempest, which means that API

[openstack-dev] [nova] [placement] experimenting with extracting placement

From the start we've been saying that it is probably right for the placement service to have its own repository. This is aligned with the long term goal of placement being useful to many services, not just nova, and also helps to keep placement contained and comprehensible and thus

Re: [openstack-dev] [nova] [placement] experimenting with extracting placement

Le 13/03/2017 14:21, Sean Dague a écrit : > On 03/13/2017 09:16 AM, Sylvain Bauza wrote: >> >> >> Le 13/03/2017 13:41, Chris Dent a écrit : >>> >>> From the start we've been saying that it is probably right for the >>> placement service to have its own repository. This is aligned with >>> the

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

On Mon, 13 Mar 2017, Thierry Carrez wrote: At the recent Board+TC+UC meeting, the User Committee presented the API workgroup as a User Committee workgroup, based on data from: https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee Yeah, that's been ongoing for a while and not

Re: [openstack-dev] [nova] [placement] experimenting with extracting placement

Le 13/03/2017 13:41, Chris Dent a écrit : > > From the start we've been saying that it is probably right for the > placement service to have its own repository. This is aligned with > the long term goal of placement being useful to many services, not > just nova, and also helps to keep

Re: [openstack-dev] [api][qa][tc][nova][cinder] Testing of a microversioned world

On Mon, Mar 13, 2017 at 6:52 AM Ghanshyam Mann wrote: > On Sun, Mar 12, 2017 at 7:40 AM, Matt Riedemann > wrote: > > On 3/10/2017 3:02 PM, Andrea Frittoli wrote: > > > We had a couple of sessions related to this topic at the PTG [0][1]. > > We

Re: [openstack-dev] [nova] [placement] experimenting with extracting placement

On 03/13/2017 09:16 AM, Sylvain Bauza wrote: > > > Le 13/03/2017 13:41, Chris Dent a écrit : >> >> From the start we've been saying that it is probably right for the >> placement service to have its own repository. This is aligned with >> the long term goal of placement being useful to many

[openstack-dev] [nova] notification update week 10

Hi, Here is the status update / focus setting mail about notification work for week 10. Bugs There are couple of important outstanding bugs: [High] https://bugs.launchpad.net/nova/+bug/1665263 The legacy instance.delete notification is missing for unscheduled instance. The Pike fix

Re: [openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help your team?

Hi all, Not that it matters one way or the other, Carlos's comment reminded me of some trivia regarding owl eye color that I had read recently: https://owlpedia.wordpress.com/2015/08/06/why-do-owls-have-different-colour-eyes/ On Mon, Mar 13, 2017 at 6:16 AM, Carlos Camacho Gonzalez <

[openstack-dev] [glance][keystone][requirements] Prioritizing reviews for requirements u-c/g-r

Dear Glance and Keystone folks, A few requirements reviews are stuck behind others, can you please take a look and help with these? Glance: Fixing HostName and adding support for HostAddress - https://review.openstack.org/#/c/439777/ (Needed for oslo.config min change -

Re: [openstack-dev] [Neutron][LBaaS] - Best release to upgrade from LBaaS v1 to v2

On 10/03/17 17:49, Michael Johnson wrote: > Yes, folks have recently deployed the dashboard with success. I think you > had that discussion on the IRC channel, so I won't repeat it here. > > Please note, the neutron-lbaas-dashboard does not support LBaaS v1, you must > have LBaaS v2 deployed for

Re: [openstack-dev] [nova] [placement] experimenting with extracting placement

On 03/13/2017 09:33 AM, Sylvain Bauza wrote: > > We are close to the first milestone in Pike, right ? We also have > priorities for Placement that we discussed at the PTG and we never > discussed about how to cut placement during the PTG. > > Also, we haven't discussed yet with operators about

Re: [openstack-dev] [all] Small steps for Go

Update: * We have a new git repo (EMPTY!) for the commons work - http://git.openstack.org/cgit/openstack/golang-commons/ * The golang-client has little code, but lot of potential - https://git.openstack.org/cgit/openstack/golang-client/ Anyone interested, please get cranking! Oh, let's use

[openstack-dev] [tripleo] propose Alex Schultz core on tripleo-heat-templates

Hi, Alex is already core on instack-undercloud and puppet-tripleo. His involvement and knowledge in TripleO Heat Templates has been very appreciated over the last months and I think we can give him +2 on this project. As usual, feel free to vote -1/+1 on this proposal. Thanks, -- Emilien

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

So for cloud apps, you must have a config management system to do secure secret transport? A cloud app developer must target which config management tool? How do you know what the end user sites are running? Do you have to support all of them? Config management tooling is very religious, so if

Re: [openstack-dev] [nova] [placement] experimenting with extracting placement

Interestingly, we just had a meeting about cells and the scheduler, which had quite a bit of overlap on this topic. > That said, as mentioned in the previous email, the priorities for Pike > (and likely Queens) will continue to be, in order: traits, ironic, > shared resource pools, and nested

Re: [openstack-dev] [tripleo] propose Alex Schultz core on tripleo-heat-templates

+1 On Mon, Mar 13, 2017 at 4:12 PM, Jiří Stránský wrote: > On 13.3.2017 15:30, Emilien Macchi wrote: > >> Hi, >> >> Alex is already core on instack-undercloud and puppet-tripleo. >> His involvement and knowledge in TripleO Heat Templates has been very >> appreciated over the

Re: [openstack-dev] [nova] [placement] experimenting with extracting placement

> > We are close to the first milestone in Pike, right ? We also have > > priorities for Placement that we discussed at the PTG and we never > > discussed about how to cut placement during the PTG. > > > > Also, we haven't discussed yet with operators about how they would like > > to see Placement

Re: [openstack-dev] [TripleO][release][deployment] Packaging problems due to branch/release ordering

Jeremy Stanley wrote: > On 2017-03-09 12:12:01 +0100 (+0100), Alan Pevec wrote: >> 2017-03-09 10:41 GMT+01:00 Alfredo Moralejo Alonso : >>> On Wed, Mar 8, 2017 at 12:44 PM, Steven Hardy wrote: https://bugs.launchpad.net/tripleo/+bug/1669462

Re: [openstack-dev] [puppet][tripleo][release] puppet module versioning

Excerpts from Thierry Carrez's message of 2017-03-13 15:19:40 +0100: > Doug Hellmann wrote: > > Excerpts from Alex Schultz's message of 2017-03-09 11:29:28 -0700: > >> On Thu, Mar 9, 2017 at 10:54 AM, Doug Hellmann > >> wrote: > >>> Excerpts from Alex Schultz's message of

Re: [openstack-dev] [nova] [placement] experimenting with extracting placement

Le 13/03/2017 14:59, Jay Pipes a écrit : > On 03/13/2017 08:41 AM, Chris Dent wrote: >> >> From the start we've been saying that it is probably right for the >> placement service to have its own repository. This is aligned with >> the long term goal of placement being useful to many services,

Re: [openstack-dev] [nova] [placement] experimenting with extracting placement

On 03/13/2017 09:16 AM, Sylvain Bauza wrote: Please don't. Having a separate repository would mean that deployers would need to implement a separate package for placement plus discussing about how/when to use it. Apparently, there already *are* separate packages for

Re: [openstack-dev] [tripleo] propose Alex Schultz core on tripleo-heat-templates

On Mon, Mar 13, 2017 at 12:00 PM, Emilien Macchi wrote: > Hi, > > Alex is already core on instack-undercloud and puppet-tripleo. > His involvement and knowledge in TripleO Heat Templates has been very > appreciated over the last months and I think we can give him +2 on > this

Re: [openstack-dev] [monasca] future of thresholder on Storm

Hello Joachim, all, I’m not aware of an upcoming or existing replacement for the thresholding engine, Roland may be able to speak on that, but the Monasca query language is currently expected to be implemented in the existing engine. Thanks, Ryan From: "Barheine, Joachim"

Re: [openstack-dev] [nova] [placement] experimenting with extracting placement

On 03/13/2017 08:41 AM, Chris Dent wrote: From the start we've been saying that it is probably right for the placement service to have its own repository. This is aligned with the long term goal of placement being useful to many services, not just nova, and also helps to keep placement

Re: [openstack-dev] [puppet][tripleo][release] puppet module versioning

Doug Hellmann wrote: > Excerpts from Alex Schultz's message of 2017-03-09 11:29:28 -0700: >> On Thu, Mar 9, 2017 at 10:54 AM, Doug Hellmann wrote: >>> Excerpts from Alex Schultz's message of 2017-03-07 12:56:17 -0700: So what I'm proposing is to use a "-dev"

Re: [openstack-dev] What do we want to be when we grow up?

Joshua Harlow wrote: > [...] > * Be opinionated; let's actually pick *specific* technologies based on > well thought out decisions about what we want out of those technologies > and integrate them deeply (and if we make a bad decision, that's ok, we > are all grown ups and we'll deal with it).

Re: [openstack-dev] [tripleo] propose Alex Schultz core on tripleo-heat-templates

On 13.3.2017 15:30, Emilien Macchi wrote: Hi, Alex is already core on instack-undercloud and puppet-tripleo. His involvement and knowledge in TripleO Heat Templates has been very appreciated over the last months and I think we can give him +2 on this project. As usual, feel free to vote -1/+1

Re: [openstack-dev] [nova] [placement] experimenting with extracting placement

Le 13/03/2017 15:17, Jay Pipes a écrit : > On 03/13/2017 09:16 AM, Sylvain Bauza wrote: >> Please don't. >> Having a separate repository would mean that deployers would need to >> implement a separate package for placement plus discussing about >> how/when to use it. > > Apparently, there

Re: [openstack-dev] [nova] [placement] experimenting with extracting placement

On Mon, 13 Mar 2017, Sylvain Bauza wrote: That way, we could do the necessary quirks in the client in case the split goes bad. I don't understand this statement. If the client is always using the service catalog (which it should be) and the client is always only aware of the HTTP interface

Re: [openstack-dev] [nova] [placement] experimenting with extracting placement

On 03/13/2017 11:13 AM, Dan Smith wrote: Interestingly, we just had a meeting about cells and the scheduler, which had quite a bit of overlap on this topic. That said, as mentioned in the previous email, the priorities for Pike (and likely Queens) will continue to be, in order: traits, ironic,

[openstack-dev] Neutron API and WSGI

Hi list, Not being sure if this is the right place to ask: could someone please give me some pointers on Neutron API and WSGI (it seems Pecan is used)? I'm currently running Neutron from Liberty (2:7.2.0-0ubuntu1~cloud1) and I'm try to start Neutron API using uWSGI, but unfortunately without any

Re: [openstack-dev] [tripleo] propose Alex Schultz core on tripleo-heat-templates

On Mon, Mar 13, 2017 at 4:30 PM, Emilien Macchi wrote: > Hi, > > Alex is already core on instack-undercloud and puppet-tripleo. > His involvement and knowledge in TripleO Heat Templates has been very > appreciated over the last months and I think we can give him +2 on > this

Re: [openstack-dev] [nova] [placement] experimenting with extracting placement

On 03/13/2017 10:02 AM, Eoghan Glynn wrote: We are close to the first milestone in Pike, right ? We also have priorities for Placement that we discussed at the PTG and we never discussed about how to cut placement during the PTG. Also, we haven't discussed yet with operators about how they

Re: [openstack-dev] [TripleO][release][deployment] Packaging problems due to branch/release ordering

Excerpts from Thierry Carrez's message of 2017-03-13 15:13:18 +0100: > Jeremy Stanley wrote: > > On 2017-03-09 12:12:01 +0100 (+0100), Alan Pevec wrote: > >> 2017-03-09 10:41 GMT+01:00 Alfredo Moralejo Alonso : > >>> On Wed, Mar 8, 2017 at 12:44 PM, Steven Hardy

[openstack-dev] [Ironic] FYI: Making changes required for Ironic multi-node grenade to work

In order for Ironic multi-node grenade testing work we have to correct a mistake we (well really I) made. We need to remove the enabling of the ironic plugin in our devstack/upgrade/settings file and move it to openstack-infra/project-config. As enabling the plugin in that file works for

[openstack-dev] [nova] [notification] BlockDeviceMapping in InstancePayload

Hi, As part of the Searchlight integration we need to extend our instance notifications with BDM data [1]. As far as I understand the main goal is to provide enough data about the instance to Searchlight so that Nova can use Searchlight to generate the response of the GET

Re: [openstack-dev] [TripleO][release][deployment] Packaging problems due to branch/release ordering

2017-03-13 15:49 GMT+01:00 Doug Hellmann : ... > We test this upgrade scenario in the upstream CI, too. The difference > is that grenade can tell pip "install exactly the version I am > pointing to in this directory on disk," rather than relying on > version numbers to

Re: [openstack-dev] [api][qa][tc][nova][cinder] Testing of a microversioned world

On 03/10/2017 01:37 PM, John Griffith wrote: Now that micro-versions are *the API versioning scheme to rule them all* one question I've not been able to find an answer for is what we're going to promise here for support and testing. My understanding thus far is that the "community" approach

Re: [openstack-dev] [TripleO][release][deployment] Packaging problems due to branch/release ordering

2017-03-09 14:58 GMT+01:00 Jeremy Stanley : > In the past we addressed this by automatically merging the release > tag back into master, but we stopped doing that a cycle ago because > it complicated release note generation. Also this was including RC >= 2 and final tags so as

Re: [openstack-dev] [QA] Meeting Thursday Mar 9th at 9:00 UTC (about bug: test_get_volume_absolute_limits fails with no admin credentials)

This should be moved to admin dir with clear note like - [0]. force_tenant_isolation is right thing in that tests to avoid the test fails due to other tenants volumes etc. We have similar case for quota tests too. ..0

Re: [openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help your team?

Hey! Yeahp I think most owls have yellow/orange eyes, this can be a good thing to try. Cheers, Carlos On Fri, Mar 10, 2017 at 8:53 PM, Dan Sneddon wrote: > On 03/10/2017 08:26 AM, Heidi Joy Tretheway wrote: > > Hi TripleO team, > > > > Here’s an update on your project

[openstack-dev] [monasca] future of thresholder on Storm

Hi all, What are your plans for the Monasca thresholder on Apache Storm, especially with respect to the upcoming Monasca query language? I saw that there is a component monasca-transform that is based on Apache Spark. Are there plans to build a new alarming engine on Spark that is for example

Re: [openstack-dev] A Summary of Atlanta PTG Summaries (!)

Hi Emilien, All, On 8/3/17 09:26, Emilien Macchi wrote: On Mon, Mar 6, 2017 at 10:45 PM, Hugh Blemings wrote: Hiya, As has been done for the last few Summits/PTGs in Lwood[1] I've pulled together a list of the various posts to openstack-dev that summarise things at the PTG

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

On Mon, Mar 13, 2017 at 9:34 AM, Thomas Herve wrote: > On Fri, Mar 10, 2017 at 9:52 PM, Ryan Brady wrote: > > > > One of the pain points for me as an action developer is the OpenStack > > actions[1]. Since they all use the same method name to retrieve the

Re: [openstack-dev] [QA] Meeting Thursday Mar 9th at 9:00 UTC (about bug: test_get_volume_absolute_limits fails with no admin credentials)

hello qa team, As to #1671256 test_get_volume_absolute_limits fails with no admin credentials This testcase will fail when admin credenticals are not present, because it uses force_tenant_isolation = True and is not in admin dirs(if it was, it would be skipped instead of fail) so,

Re: [openstack-dev] [api][qa][tc][nova][cinder] Testing of a microversioned world

On Sun, Mar 12, 2017 at 7:40 AM, Matt Riedemann wrote: > On 3/10/2017 3:02 PM, Andrea Frittoli wrote: > >> >> We had a couple of sessions related to this topic at the PTG [0][1]. >> >> We agreed that we want to still maintain integration tests only in >> Tempest, which means

Re: [openstack-dev] [api][qa][tc][glance][keystone][cinder] Testing of deprecated API versions

On Sat, Mar 11, 2017 at 12:10 AM, Andrea Frittoli wrote: > > > On Fri, Mar 10, 2017 at 2:49 PM Andrea Frittoli > wrote: > >> On Fri, Mar 10, 2017 at 2:24 PM Doug Hellmann >> wrote: >> >> Excerpts from Ghanshyam

[openstack-dev] [acceleration]Atlanta PTG Summary

Hi Team, Sorry for the long delay after our ptg session. Here are the main takeaways from the meeting (both f2f and virtual ): *1. Pike Development Goal* We will shoot for an basic functional Cyborg code base for the Pike release cycle. We will

Re: [openstack-dev] [QA] Meeting Thursday Mar 9th at 9:00 UTC (about bug: test_get_volume_absolute_limits fails with no admin credentials)

Thanks gmann, I've uploaded a patch to move it, and fortunetly the testcase is not used in defcore. Original Mail Sender: ＜ghanshyamm...@gmail.com＞ To: ＜openstack-dev@lists.openstack.org＞ Date: 2017/03/13 15:30 Subject: Re: [openstack-dev] [QA] Meeting Thursday Mar 9th at 9:00

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

On Fri, Mar 10, 2017 at 9:52 PM, Ryan Brady wrote: > > One of the pain points for me as an action developer is the OpenStack > actions[1]. Since they all use the same method name to retrieve the > underlying client, you cannot simply inherit from more than one so you are >

[openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

Folks, Currently devstack defaults to zookeeper and is opinionated about it. Talking to Josh, etcd seems to be a good option too. Does anyone have specific experience with etcd with tooz? Do we want to make DLM mandatory? (always run with tooz + backend)? Asking because lots of the container

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

On 10/03/17 21:34, Clint Byrum wrote: (BTW I proposed a workaround for Magnum/Kuryr at the PTG by using a pre-signed Zaqar URL with a subscription triggering a Mistral workflow, and I've started working on a POC.) What triggers the boot to kick over the bucket full of golf balls though? It's

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

On 13/03/17 18:16, Jay Pipes wrote: Who, specifically, are these gatekeepers of which you speak? In this case, the Nova & Keystone core teams. - ZB __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

On 03/13/2017 05:10 PM, Zane Bitter wrote: On 12/03/17 11:30, Clint Byrum wrote: Excerpts from Fox, Kevin M's message of 2017-03-11 21:31:40 +: No, they are treated as second class citizens. Take Trova again as an example. The underlying OpenStack infrastructure does not provide a good

Re: [openstack-dev] [Neutron][LBaaS] - Best release to upgrade from LBaaS v1 to v2

I can confirm that the 1.0.0 release of neutron-lbaas-dashboard is working on stable/newton. I included my installation steps in the below linked bug. As mentioned in the first e-mail. The instructions say to only install one of the two files in the enabled directory. I suspect that is the

[openstack-dev] [openstack-docs] [tripleo] Creating official Deployment guide for TripleO

Team, [adding Alexandra, OpenStack Docs PTL] It seems like there is a common interest in pushing deployment guides for different OpenStack Deployment projects: OSA, Kolla. The landing page is here: https://docs.openstack.org/project-deploy-guide/newton/ And one example:

Re: [openstack-dev] [Horizon][searchlight] Sharing resource type implementations

I'll definitely be looking at getting a searchlight-ui patch up for the mirror side of my Horizon patch. Double registration largely depends on which particular aspect of the resource type is being looked at. Most of the resource type registration will just be replaced (with identical

Re: [openstack-dev] [all] Small steps for Go

Clint, There's some discussion on the etherpad, don't want to move that here. -- Dims On Mon, Mar 13, 2017 at 1:44 PM, Clint Byrum wrote: > Excerpts from Davanum Srinivas's message of 2017-03-13 10:06:30 -0400: >> Update: >> >> * We have a new git repo (EMPTY!) for the

Re: [openstack-dev] [deployment][kolla][openstack-helm]k8s-sig-openstack meeting

Of course, US daylight savings bug bit. Please consider 18:30 UTC the official time. We will work out scheduling at the meeting. > On Mar 13, 2017, at 10:36 AM, Chris Hoge wrote: > > Tomorrow, March 14 at 18:30 UTC/10:30 PT, we will be holding the new > extension to the

Re: [openstack-dev] [tripleo] A sneak peek to TripleO + Containers

On Mon, 2017-02-13 at 11:46 +0100, Flavio Percoco wrote: > Hello, > > I've been playing with a self-installing container for the > containerized TripleO > undercloud and I thought I'd share some of the progress we've made so > far. > > This is definitely not at its final, ideal, state but I

Re: [openstack-dev] [TripleO][Containers] Containers work tracking, updates and schedule

On Tue, 2017-03-07 at 12:08 +0100, Flavio Percoco wrote: > Greetings, > > We've been organizing the containers work for TripleO in a more > consumable way > that will hopefully ease the engagement from different squads and > teams in > OpenStack. For reference as a lot of the initial services

Re: [openstack-dev] What do we want to be when we grow up?

On 03/10/2017 11:39 PM, Joshua Harlow wrote: > > * Interoperability - kept as is (though I can't really say how many > public clouds there are anymore to interoperate with). There are plenty. As Dan Smith will tell you, I'm fond of telling people just how many OpenStack Public Cloud accounts I

Re: [openstack-dev] [neutron][ml2] - driver capability/feature verification framework

Hi Kevin, I will file the RFE this week. -Bob On 3/13/17 2:05 PM, Kevin Benton wrote: Hi, At the PTG we briefly discussed a generic system for verifying that the appropriate drivers are enforcing a particular user-requested feature in ML2 (e.g. security groups, qos, etc). Is someone

Re: [openstack-dev] [all] Small steps for Go

Excerpts from Davanum Srinivas's message of 2017-03-13 14:32:16 -0400: > Clint, > > There's some discussion on the etherpad, don't want to move that here. > Ok. I don't see much that explains why. But either way, IMO this is why an etherpad is a really bad place to have a discussion. Great for

[openstack-dev] [neutron][ml2] - driver capability/feature verification framework

Hi, At the PTG we briefly discussed a generic system for verifying that the appropriate drivers are enforcing a particular user-requested feature in ML2 (e.g. security groups, qos, etc). Is someone planning on working on this for Pike? If so, can you please file an RFE so we can prioritize it

Re: [openstack-dev] [tripleo] propose Alex Schultz core on tripleo-heat-templates

On 03/13/2017 10:30 AM, Emilien Macchi wrote: > Hi, > > Alex is already core on instack-undercloud and puppet-tripleo. +1 it is actually a bit odd to be +2 on puppet-tripleo without being +2 on THT, since so many changes span the two repos.

[openstack-dev] [deployment][kolla][openstack-helm]k8s-sig-openstack meeting

Tomorrow, March 14 at 18:30 UTC/10:30 PT, we will be holding the new extension to the k8s-sig-openstack meeting. This bi-weekly meeting will focus on Kubernetes as an deployment platform for OpenStack. This includes using Helm for orchestration. For this meeting, use the zoom id:

Re: [openstack-dev] [all] Small steps for Go

Excerpts from Davanum Srinivas's message of 2017-03-13 10:06:30 -0400: > Update: > > * We have a new git repo (EMPTY!) for the commons work - > http://git.openstack.org/cgit/openstack/golang-commons/ > * The golang-client has little code, but lot of potential - >

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

I know it happened a few messages up in the thread, but you may have forgotten where I said that we should resurrect the idea of having automatic instance-users as a feature of Nova (and even to add this to Shade/Oaktree, so people could add it to existing OpenStack clouds before they roll out the

Re: [openstack-dev] [all] Small steps for Go

- Original Message - > From: "Steve Gordon" > To: "OpenStack Development Mailing List (not for usage questions)" > > Sent: Monday, March 13, 2017 8:11:34 PM > Subject: Re: [openstack-dev] [all] Small steps for Go > > - Original

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

With my operator hat on, I would like to use the etcd backend, as I'm already paying the cost of maintaining etcd clusters as part of Kubernetes. Adding Zookeeper is a lot more work. Thanks, Kevin From: Davanum Srinivas [dava...@gmail.com] Sent: Monday,

Re: [openstack-dev] [all] Small steps for Go

- Original Message - > From: "Clint Byrum" > To: "openstack-dev" > Sent: Monday, March 13, 2017 1:44:19 PM > Subject: Re: [openstack-dev] [all] Small steps for Go > > Excerpts from Davanum Srinivas's message of 2017-03-13 10:06:30

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

Excerpts from Fox, Kevin M's message of 2017-03-14 00:09:55 +: > With my operator hat on, I would like to use the etcd backend, as I'm already > paying the cost of maintaining etcd clusters as part of Kubernetes. Adding > Zookeeper is a lot more work. > It would probably be a good idea to

Re: [openstack-dev] [api][qa][tc][nova][cinder] Testing of a microversioned world

On Mon, Mar 13, 2017 at 7:37 PM, Andrea Frittoli wrote: > On Sat, Mar 11, 2017 at 10:45 PM Matt Riedemann > wrote: > > On 3/10/2017 3:02 PM, Andrea Frittoli wrote: > > > > We had a couple of sessions related to this topic at the PTG [0][1]. > > >

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

Clint Byrum wrote: Excerpts from Fox, Kevin M's message of 2017-03-14 00:09:55 +: With my operator hat on, I would like to use the etcd backend, as I'm already paying the cost of maintaining etcd clusters as part of Kubernetes. Adding Zookeeper is a lot more work. It would probably

[openstack-dev] [neutron][networking-l2gw] Unable to create release tag

Hi, I was asked to create a release tag for stable/ocata. This fails with: gkotton@ubuntu:~/networking-l2gw$ git push gerrit tag 10.0.0 Enter passphrase for key '/home/gkotton/.ssh/id_rsa': Counting objects: 1, done. Writing objects: 100% (1/1), 533 bytes | 0 bytes/s, done. Total 1 (delta 0),

Re: [openstack-dev] What do we want to be when we grow up?

Monty Taylor wrote: On 03/10/2017 11:39 PM, Joshua Harlow wrote: * Interoperability - kept as is (though I can't really say how many public clouds there are anymore to interoperate with). There are plenty. As Dan Smith will tell you, I'm fond of telling people just how many OpenStack Public

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

So again, I’m for simplicity but that kind of simplicity that also allows flexibility in the future. There’s one principle that I usually follow in programming that says: “Space around code (absence of code) has more potential than the code itself.” That means that it’s better to get rid of

[openstack-dev] [Keystone] Admin or certain roles should be able to list full project subtree

Hello Keystone Devs, I've been playing with subtrees in Keystone for the last while, and one thing that hit me recently is that as admin, I still can't actually do subtree_as_list unless I have a role in all projects in the subtree. This is kind of silly. I can understand why this limitation was

[openstack-dev] [neutron] bug deputy report (Mar 6- Mar 13)

Hi All, I was serving as bug deputy for the last week. There were 25 bugs and few RFE’s that were raised last week. Of the 25 bugs 2 are still uncategorized, so help with them will be highly appreciated. 1. https://bugs.launchpad.net/neutron/+bug/1672345 -- Loadbalancer V2 ports are

Re: [openstack-dev] What do we want to be when we grow up?

Thierry Carrez wrote: Joshua Harlow wrote: [...] * Be opinionated; let's actually pick *specific* technologies based on well thought out decisions about what we want out of those technologies and integrate them deeply (and if we make a bad decision, that's ok, we are all grown ups and we'll

Re: [openstack-dev] [oslo][barbican][castellan] Proposal to rename Castellan to oslo.keymanager

Kaitlin, On Mon, Mar 13, 2017 at 2:55 PM, Farr, Kaitlin M. wrote: > Proposed library name: Rename Castellan to oslo.keymanager > > > > Proposed library mission/motivation: Castellan’s goal is to provide a > > generic key manager interface that projects can use for their

Re: [openstack-dev] [api][qa][tc][nova][cinder] Testing of a microversioned world

On Mon, Mar 13, 2017 at 12:58 PM, Chris Friesen wrote: > On 03/10/2017 01:37 PM, John Griffith wrote: > > Now that micro-versions are *the API versioning scheme to rule them all* >> one >> question I've not been able to find an answer for is what we're going to >>

Re: [openstack-dev] [Neutron][LBaaS] - Best release to upgrade from LBaaS v1 to v2

Hi Saverio, I did a fresh install today with master versions of both OpenStack and the neutron-lbaas-dashboard just to make sure the panels are working as expected. It went fine. https://usercontent.irccloud-cdn.com/file/4Zgl9SB3/ To answer your version question: Stable/mitaka

[openstack-dev] [oslo][barbican][castellan] Proposal to rename Castellan to oslo.keymanager

Proposed library name: Rename Castellan to oslo.keymanager Proposed library mission/motivation: Castellan's goal is to provide a generic key manager interface that projects can use for their key manager needs, e.g., storing certificates or generating keys for encrypting data. The interface

[openstack-dev] [ironic] this week's priorities and subteam reports

Hi, We are meditative to present this week's priorities and subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. This Week's Priorities (as of the weekly ironic meeting) 1.

Re: [openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help your team?

Hi Heidi, I like this one a good bit better. He might looks a smidge cross-eyed to me... but I'd take this one any day over the previous version. Thanks for trying to capture the spirit of the original logos. Dan On Fri, 2017-03-10 at 08:26 -0800, Heidi Joy Tretheway wrote: > Hi TripleO team, 

Re: [openstack-dev] [Murano] Where to find list of Newton Murano bugs, and post-Newton commits

Hi Greg, You can obtain a list of post-Newton enhancements to Murano here: https://docs.openstack.org/releasenotes/murano/ However, Murano doesn’t actively maintain a list of Newton bugs upstream; this is a general upstream policy. Instead, bugs that are identified upstream are then

Re: [openstack-dev] [oslo][barbican][castellan] Proposal to rename Castellan to oslo.keymanager

Excerpts from Farr, Kaitlin M.'s message of 2017-03-13 18:55:18 +: > Proposed library name: Rename Castellan to oslo.keymanager > > Proposed library mission/motivation: Castellan's goal is to provide a > generic key manager interface that projects can use for their key > manager needs, e.g.,

Re: [openstack-dev] [ironic] New mascot design

On Fri, Mar 10, 2017 at 11:28 AM, Heidi Joy Tretheway < heidi...@openstack.org> wrote: > Hi Ironic team, > Here’s an update on your project logo. Our illustrator tried to be as true > as possible to your original, while ensuring it matched the line weight, > color palette and style of the rest.

Re: [openstack-dev] [oslo][barbican][castellan] Proposal to rename Castellan to oslo.keymanager

Excerpts from Doug Hellmann's message of 2017-03-13 15:12:42 -0400: > Excerpts from Farr, Kaitlin M.'s message of 2017-03-13 18:55:18 +: > > Proposed library name: Rename Castellan to oslo.keymanager > > > > Proposed library mission/motivation: Castellan's goal is to provide a > > generic key

Re: [openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help your team?

Hi, I agree that this new updated logo is great refinement to what we currently have. Love it. Thanks Heidi On Mon, Mar 13, 2017 at 8:24 PM, Dan Prince wrote: > Hi Heidi, > > I like this one a good bit better. He might looks a smidge cross-eyed > to me... but I'd take this

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

On 12/03/17 11:30, Clint Byrum wrote: Excerpts from Fox, Kevin M's message of 2017-03-11 21:31:40 +: No, they are treated as second class citizens. Take Trova again as an example. The underlying OpenStack infrastructure does not provide a good security solution for Trove's use case. As

Re: [openstack-dev] [api][qa][tc][nova][cinder] Testing of a microversioned world

2017-03-13 12:23 GMT-07:00 Jim Rollenhagen : > On Mon, Mar 13, 2017 at 12:58 PM, Chris Friesen > wrote: >> >> On 03/10/2017 01:37 PM, John Griffith wrote: >> >>> Now that micro-versions are *the API versioning scheme to rule them all* >>> one

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

Zane, Sorry for the top post, Can you please submit a TC resolution? I can help with it as well. Let's test the waters. Thanks, Dims On Mon, Mar 13, 2017 at 5:10 PM, Zane Bitter wrote: > On 12/03/17 11:30, Clint Byrum wrote: >> >> Excerpts from Fox, Kevin M's message of

Re: [openstack-dev] [tripleo] propose Alex Schultz core on tripleo-heat-templates

On Mon, Mar 13, 2017 at 10:30:08AM -0400, Emilien Macchi wrote: > Hi, > > Alex is already core on instack-undercloud and puppet-tripleo. > His involvement and knowledge in TripleO Heat Templates has been very > appreciated over the last months and I think we can give him +2 on > this project. >

Re: [openstack-dev] [ironic] New mascot design

+1. Reminds me a lot of our current logo. I like this version the best of the official stylized logos. Thanks. On Fri, Mar 10, 2017 at 8:28 AM, Heidi Joy Tretheway wrote: > Hi Ironic team, > Here’s an update on your project logo. Our illustrator tried to be as true > as

Re: [openstack-dev] [ironic] New mascot design

I love it! +1 Thank you! -Julia On Fri, Mar 10, 2017 at 11:28 AM, Heidi Joy Tretheway < heidi...@openstack.org> wrote: > Hi Ironic team, > Here’s an update on your project logo. Our illustrator tried to be as true > as possible to your original, while ensuring it matched the line weight, >

  1   2   >