Re: [openstack-dev] [cross-project][nova][cinder][designate][neutron] Common support-matrix.py

On 01/03/2017 23:53, Mike Perez wrote: > Hey all, > > I kicked off a thread [1] to start talking about approaches with improving > vendor discoveribility by improving our Market Place [2]. In order to improve > our market place, having the projects be more part of the process would allow > the

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

On 07/03/2017 13:22, Davanum Srinivas wrote: > Folks, > > Anyone interested? https://etherpad.openstack.org/p/go-and-containers > > Thanks, > Dims > The first thing that is required (according to the new guidelines) is for there to be a technical reason we need to use go, and cannot use python.

[openstack-dev] [designate] Re:add new features in designate-dashboard

> From: *Saju M* > > Date: Tue, Feb 28, 2017 at 11:43 PM > Subject: add new features in designate-dashboard > To: gra...@hayes.ie , gra...@managedit.ie > , graham.ha...@hp.com >

Re: [openstack-dev] [all] PBR 2.0.0 release *may* cause gate failures

On 01/03/2017 13:00, Sean Dague wrote: > On 03/01/2017 12:26 AM, Tony Breeds wrote: >> Hi All, >> Earlier today the release team tagged PBR 2.0.0. The reason for the >> major >> version bump is because warnerrors has been removed in favor of >> warning-is-error from sphinx >= 1.5.0. >> >> It

Re: [openstack-dev] [qa] Tempest Stable plugin interface change broke gate

On 21/02/2017 15:25, Andrea Frittoli wrote: > Hi Graham, > > sorry about that, and good catch. > You are right, that's a stable interface so that change should not have > landed. > > andrea > > On Tue, Feb 21, 2017 at 2:51 PM Hayes, Graham <graham.ha...@hpe.com

[openstack-dev] [tc][all][designate] The way forward for Designate

For those that are interested, we will have an hour discussion about how designate can move forward tomorrow (wed 22nd) at the PTG. We will be in Savannah 3 @ 11:00 for an hour. Thanks, Graham On 09/02/2017 14:22, Hayes, Graham wrote: > The HTML version of this is here: >

[openstack-dev] [qa] Tempest Stable plugin interface change broke gate

Hi. https://review.openstack.org/#/c/434304/ landed yesterday, which was a change to the stable interface for tempest plugins. It also took out the designate gate. Is this interface stable? - If so, there should have been at least some deprecation cycle, notification, or something. Revert has

Re: [openstack-dev] [octavia][sdk] service name for octavia

On 15/02/2017 15:00, Monty Taylor wrote: > On 02/14/2017 07:08 PM, Qiming Teng wrote: >> When reviewing a recent patch that adds openstacksdk support to octavia, >> I found that octavia is using 'octavia' as its service name instead of >> 'loadbalancing' or 'loadbalancingv2' or something similar.

[openstack-dev] [all][logos] License for new project mascots

Hi, I did a bit of digging through email, and I *thought* someone had asked about the license that these logos were being released under. Turns out it was me, and I don't seem to have gotten a response about it. So - what license are the new logos / mascots under? Is the same as the wiki? [1]

Re: [openstack-dev] [designate] Status of the project

On 11/02/17 15:12, Andrea Frittoli wrote: > > > On Thu, Feb 9, 2017 at 7:22 PM Hayes, Graham <graham.ha...@hpe.com > <mailto:graham.ha...@hpe.com>> wrote: > > The HTML version of this is here: > http://graham.hayes.ie/posts/openstack-designate-where-w

Re: [openstack-dev] [governance][tc][rally] Rally (Re: [rally][release] How rally release version)

On 13/02/2017 14:02, Davanum Srinivas wrote: > Andrey, Rally team, > > Do you want Rally to be dropped from Governance and Releases repository? > > Thanks, > Dims > While I think the info should be removed from releases if there is no useful data there, why the removal from governance? Rally has

Re: [openstack-dev] [Designate] In what sense is it multi-tenant?

On 10/02/17 21:51, Mike Spreitzer wrote: > In what sense is Designate multi-tenant? Can it be programmed to give > different views to different DNS clients? (If so, how?) > > Thanks, > Mike It is multi-tenant as it allows multiple users to use the same DNS infra, while keeping control of DNS

Re: [openstack-dev] [designate] Status of the project

r a huge amount we can offer others. >> Thanks, >> Kevin >> >> From: Jay Pipes [jaypi...@gmail.com] >> Sent: Friday, February 10, 2017 9:50 AM >> To: openstack-dev@lists.openstack.org >> Subject: Re: [openstack-d

Re: [openstack-dev] [designate] Status of the project

On 10/02/17 18:10, Joshua Harlow wrote: > Jay Pipes wrote: >> On 02/10/2017 12:21 PM, Joshua Harlow wrote: >>> Hayes, Graham wrote: >>>> The HTML version of this is here: >>>> http://graham.hayes.ie/posts/openstack-designate-where-we-are/ >>>

Re: [openstack-dev] [designate] Status of the project

but > if we can help, please shout out :) Thanks for reaching out, I will definitely shout if need it. - Graham > On 2/10/17, 3:53 PM, "Hayes, Graham" <graham.ha...@hpe.com> wrote: > > On 10/02/17 02:40, Jay Pipes

Re: [openstack-dev] [designate] Status of the project

On 10/02/17 17:24, Joshua Harlow wrote: > Hayes, Graham wrote: >> The HTML version of this is here: >> http://graham.hayes.ie/posts/openstack-designate-where-we-are/ >> >> I have been asked a few times recently "What is the state of the Designate >>

Re: [openstack-dev] [designate] Status of the project

On 10/02/17 15:48, Doug Hellmann wrote: > Excerpts from Jay Pipes's message of 2017-02-09 21:33:03 -0500: >> On 02/09/2017 02:19 PM, Hayes, Graham wrote: >> >> >>> Where too now then? >>> === >>> >>> Well, this is where I ca

Re: [openstack-dev] [designate] Status of the project

On 10/02/17 02:40, Jay Pipes wrote: > On 02/09/2017 02:19 PM, Hayes, Graham wrote: > > >> Where too now then? >> === >> >> Well, this is where I call out to people who actually use the project - >> don't >> jump ship and use somethi

[openstack-dev] [designate] Status of the project

The HTML version of this is here: http://graham.hayes.ie/posts/openstack-designate-where-we-are/ I have been asked a few times recently "What is the state of the Designate project?", "How is Designate getting on?", and by people who know what is happening "What are you going to do about

Re: [Openstack-operators] [LCOO] Intro to Large Contributing

On 09/02/2017 16:37, Jeremy Stanley wrote: > On 2017-02-09 00:59:52 + (+), UKASICK, ANDREW wrote: > [...] >> I'm the mysterious "AndyU" who was chatting with you about a year >> ago in IRC with questions about how to go about donating hosted >> cloud resources for use by the Infra team.

Re: [openstack-dev] [All] IRC Mishaps

On 09/02/2017 14:42, Jim Rollenhagen wrote: > On Thu, Feb 9, 2017 at 8:38 AM, Hayes, Graham <graham.ha...@hpe.com > <mailto:graham.ha...@hpe.com>> wrote: > > On 08/02/2017 20:39, Kendall Nelson wrote: > > Hello All! > > > > So I am sure

Re: [openstack-dev] [All] IRC Mishaps

On 09/02/2017 13:41, Hayes, Graham wrote: > On 08/02/2017 20:39, Kendall Nelson wrote: >> Hello All! >> >> So I am sure we've all seen it: people writing terminal commands into >> our project channels, misusing '/' commands, etc. But have any of you >> actually d

Re: [openstack-dev] [All] IRC Mishaps

On 08/02/2017 20:39, Kendall Nelson wrote: > Hello All! > > So I am sure we've all seen it: people writing terminal commands into > our project channels, misusing '/' commands, etc. But have any of you > actually done it? > > If any of you cores, ptls or other upstanding members of our wonderful >

Re: [openstack-dev] [all][tc][swift][designate] New language addition process has been approved

On 08/02/2017 14:56, Flavio Percoco wrote: > On 19/01/17 11:59 +0100, Flavio Percoco wrote: >> Greetings, >> >> The Technical Committe recently approved a new reference document which >> describes how new programming languages can be proposed for inclusion as >> supported languages by OpenStack.

Re: [openstack-dev] Large Contributing OpenStack Operators working group?

On 02/02/2017 20:17, Jay Pipes wrote: > Hi, > > I was told about this group today. I have a few questions. Hopefully > someone from this team can illuminate me with some answers. > > 1) What is the purpose of this group? The wiki states that the team > "aims to define the use cases and identify

Re: [openstack-dev] [Neutron][Oslo] Huge number of deprecation warnings in functional tests

openstack.org/#/c/275914/3/oslo_versionedobjects/fields.py L311. > On Sun, Jan 29, 2017 at 7:56 AM, Hayes, Graham <graham.ha...@hpe.com> wrote: >> On 29/01/17 00:53, Davanum Srinivas wrote: >>> Graham, Sławek, >>> >>> Have you seen this? >>&g

Re: [openstack-dev] [Neutron][Oslo] Huge number of deprecation warnings in functional tests

t;sla...@kaplonski.pl> wrote: >> Hello, >> >> Thanks. I just filled bug report to oslo project: >> https://bugs.launchpad.net/oslo.context/+bug/1660088 >> >> -- >> Best regards / Pozdrawiam >> Sławek Kapłoński >> sla...@kaplonski.pl >>

Re: [openstack-dev] [Neutron][Oslo] Huge number of deprecation warnings in functional tests

On 28/01/17 20:54, Sławek Kapłoński wrote: > Hello, > > I pushed today patch in Neutron to gerrit [1] and I noticed that functional > tests are failing. In logs there is huge number of deprecation warnings > displayed [2]. Tests are failing because of global timeout is reached and IMO > reason

Re: [openstack-dev] [neutron] PTL candidacy

On 25/01/2017 01:08, Kevin Benton wrote: >>I would really like us to discuss this issue head-on and see what is > missing in Neutron APIs and what would take to make them extensible so > that vendors do not run around trying to figure out alternative > solutions > > The Neutron API is already

Re: [openstack-dev] [all] Improving Vendor Driver Discoverability

On 20/01/17 01:40, Mike Perez wrote: > On 17:38 Jan 18, Morales, Victor wrote: >> Just a FYI, Ankur have been working on have a Feature Classification Matrix >> in Neutron[1] which collects some of this information >> >> [1] https://review.openstack.org/#/c/318192/ > > I actually didn't know Nova

Re: [openstack-dev] [all] [barbican] [security] Why are projects trying to avoid Barbican, still?

On 16/01/2017 13:38, Ian Cordasco wrote: > Hi everyone, > > I've seen a few nascent projects wanting to implement their own secret > storage to either replace Barbican or avoid adding a dependency on it. > When I've pressed the developers on this point, the only answer I've > received is to make

Re: [openstack-dev] [barbican] Project Navigator Out of Date?

On 16/01/2017 14:33, Julien Danjou wrote: > On Mon, Jan 16 2017, Ian Cordasco wrote: > >> Related to the other thread I just started, I was looking at the >> project navigator [1] for Barbican and found some things that look >> wrong (to an outsider) and was hoping could be cleared up. > > Don't

[openstack-dev] [designate] Non Candidacy for PTL - Pike

Happy new year! As you may have guessed from the subject, I have decided that the time has come to step aside as PTL for the upcoming cycle. It is unfortunate, but my work has pivoted in a different direction over the last year (containers all the way down man - but hey, I got part of my wish to

[openstack-dev] [designate] Next IRC meeting in 2017

Hi All, As a lot of people are now going on vacation for the holiday season, we decided to pick up IRC meetings in 2017. So, our first meeting will be 4th Jan 2017 @ 17:00 UTC See everyone after the break Graham __

Re: [openstack-dev] [neutron] Changes to DNS integration behavior?

On 12/12/2016 19:52, Kimball, Conrad wrote: > We are in the early phases of a project to deploy OpenStack and we face > the question of DNS integration when launching a VM instance. > > > > We have found the DNS Integration documentation at >

[openstack-dev] [designate] Meeting this week

Hi All, There is an unexpected internal meeting today that conflicts with the IRC meeting. As a result, I will not be available to chair, and I think that the other HPE team members will also be unavailable. I suggest that we postpone for this week? Thanks, Graham

Re: [openstack-dev] [all] Embracing new languages in OpenStack

On 08/11/2016 16:39, Flavio Percoco wrote: > On 08/11/16 16:20 +0000, Hayes, Graham wrote: >> On 08/11/2016 15:55, Doug Hellmann wrote: >>> Excerpts from Hayes, Graham's message of 2016-11-08 13:04:08 +: >>>> On 08/11/2016 10:30, Thierry

Re: [openstack-dev] [all] Embracing new languages in OpenStack

On 08/11/2016 15:55, Doug Hellmann wrote: > Excerpts from Hayes, Graham's message of 2016-11-08 13:04:08 +: >> On 08/11/2016 10:30, Thierry Carrez wrote: >>> Ash wrote: [...] Here's another take on the situation. If there are people who genuinely wish to see a CI pipeline that

Re: [openstack-dev] [all] Embracing new languages in OpenStack

On 08/11/2016 10:30, Thierry Carrez wrote: > Ash wrote: >> [...] >> Here's another take on the situation. If there are people who genuinely >> wish to see a CI pipeline that can support something like Go, perhaps >> you can establish a prerequisite of working with the Infra team on >> establishing

Re: [openstack-dev] [all] Embracing new languages in OpenStack

On 07/11/2016 17:14, Flavio Percoco wrote: > Greetings, > > I literally just posted a thing on my blog with some thoughts of what I'd > expect > any new language being proposed for OpenStack to cover before it can be > accepted. > > The goal is to set the expectations right for what's needed for

Re: [openstack-dev] [all] Global changes to CI jobs using neutron

On 02/11/16 19:53, Matt Riedemann wrote: > nova-network was deprecated in newton. Nova is working on moving the CI > jobs that run against it to use Neutron only in Ocata. I'm tracking that > work here: > > https://etherpad.openstack.org/p/removing-nova-network > > In an effort to make this more

Re: [openstack-dev] [Horizon] Rework Access & Security panel

On 27/10/2016 04:15, Adrian Turjak wrote: > Hello OpenstackDevs, > > In our deployment we keep running into a problem where customers forget > about the existence of floating ips once disassociated from an instance, > and when they then need to release them they often can't find where > because

Re: [openstack-dev] [trove][octavia][tacker][designate][manila][sahara][magnum][infra] servicevm working group meetup

On 24/10/2016 20:35, Adam Harwell wrote: > I'll be there. I will be there as well. - Graham > > > On Mon, Oct 24, 2016, 20:29 Doug Wiegley > wrote: > > >> On Oct 24, 2016, at 8:23 PM, Doug Wiegley >>

[openstack-dev] [designate] Draft Logo - Please have a look, and give feedback

Hi team, I just received a draft version of our project logo, using the mascot we selected together. A final version (and some cool swag) will be ready for us before the Project Team Gathering in February. Before they make our logo final, they want to be sure we're happy with our mascot. We

[openstack-dev] [designate] IRC Meetings - Canceled for the next 2 weeks

Hi All, With the Design Summit a week away, and having no agenda items, I suggest we skip the meeting this week, and as we will be in Spain next week, we will also be skipping that meeting. See you all in Barcelona, or at the meeting on the 2nd of November. Thanks, Graham

Re: [openstack-dev] [requirements][lbaas] gunicorn to g-r

On 18/10/2016 19:57, Doug Wiegley wrote: > >> On Oct 18, 2016, at 12:42 PM, Doug Hellmann wrote: >> >> Excerpts from Doug Wiegley's message of 2016-10-18 12:21:20 -0600: >>> On Oct 18, 2016, at 12:10 PM, Doug Hellmann wrote: Excerpts

Re: [openstack-dev] [tripleo] PTG space request

On 12/10/2016 10:31, Thierry Carrez wrote: > Emilien Macchi wrote: >> I would like to request for some space dedicated to TripleO project >> for the first OpenStack PTG. >> >> https://www.openstack.org/ptg/ >> >> The event will happen in February 2017 during the next PTG in Atlanta. >> Any

Re: [openstack-dev] [all][tc] Exposing project team's metadata in README files

On 12/10/2016 16:08, Doug Hellmann wrote: > Excerpts from Flavio Percoco's message of 2016-10-12 14:50:03 +0200: >> Greetings, >> >> One of the common complains about the existing project organization in the >> big >> tent is that it's difficult to wrap our heads around the many projects there >>

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On 03/10/2016 17:49, Edward Leafe wrote: > So the period of self-nominations for the Technical Committee seats has > ended, and the voting has begun. I've been a very close observer of this > process for several cycles, and I have some ideas I'd like to share. Full > disclosure: I am a current

Re: [openstack-dev] FYI - gate completely borked on master and newton dsvm/grenade jobs

Added a test commit for Designate - https://review.openstack.org/#/c/381084/ On 03/10/2016 13:31, Amrith Kumar wrote: > FWIW, this does not appear to work for Trove. To confirm I've pushed up a > trial balloon (https://review.openstack.org/#/c/381075/2). > > At least on a local sandbox it does

Re: [openstack-dev] FYI - gate completely borked on master and newton dsvm/grenade jobs

Also impacts designate, our dashboard, and our tempest plugin. It will probably hit our client library as well. -- Graham On 03/10/2016 12:49, Amrith Kumar wrote: > Also impacts Trove, see (for example) > > > >

Re: [openstack-dev] Pecan Version 1.2

On 27/09/2016 01:36, Ryan Petrello wrote: > Apologies for the trouble this caused. As Dave mentioned, this change > warranted a new major version of pecan, and I missed it. I've reverted the > offending commit and re-released a new version of pecan (1.2.1) to PyPI: > >

Re: [openstack-dev] [openstack-de] [DNSaaS] [designate] jenkins is failing for all latest patches

On 27/09/2016 08:42, Kelam, Koteswara Rao wrote: > Jenkins for openstack/designate is failing for latest patches. Py27, > py34 and py35 are failing continuously. > > gate-designate-python27-db-ubuntu-xenial >

[openstack-dev] [designate] PTL Candidacy

Hi Everyone, I would like to my intention to continue as PTL of the Designate project for another cycle. We have made great steps forward in Designate over the last few cycles, not just with features, but integrating with the community as a whole. For Ocata, I have previously proposed, and now

Re: [openstack-dev] [cue][qa] Status of OpenStack CI jobs

On 15/09/2016 00:12, Ken'ichi Ohmichi wrote: > Hi Cue-team, > > As http://status.openstack.org/openstack-health/#/ , the cue gate jobs > continues failing 100%. > What is current status of the development? > Hopefully the job will become stable for smooth development. > > Thanks > Ken Ohmichi I

Re: [openstack-dev] venting -- OpenStack wiki reCAPTCHA

On 09/09/2016 08:44, Tom Fifield wrote: > > > On 廿十六年九月八日 暮 08:36, Jeremy Stanley wrote: >> On 2016-09-09 01:10:15 + (+), Bhandaru, Malini K wrote: >>> Is it just me who likes to hit the save button often? >>> It gets tedious proving often that you are not a robot. Wiki >>> reCAPTCHA likes

Re: [openstack-dev] [all] governance proposal worth a visit: Write down OpenStack principles

On 08/09/2016 06:17, Chris Dent wrote: > On Thu, 8 Sep 2016, Flavio Percoco wrote: > >> To be honest, I think you're expressing in a negative way something >> that was thought in a positive way. The motivation to write the >> principles down is to help the community with the help from the >>

Re: [openstack-dev] [OpenStack-docs] [api-ref][ceilometer][nova][senlin][swift][zaqar] OpenStack Docs theme migration

d projects are using it, I will submit a new round of reviews to remove the temp code. Thanks! Graham On 19/08/2016 17:16, Hayes, Graham wrote: > Hi All, > > I have just pushed reviews to all the repos using os-api-ref, to allow > us to migrate to the new sphinx theme gracefully. >

[openstack-dev] [designate] Meeting Canceled this week

Hi All, As we are in the middle of our midcycle, we are going to skip the meeting this week. Thanks, Graham __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [api-ref][networking-sfc][ceilometer][glance][heat][ironic][keystone][manila][designate][trove][neutron][nova][sahara][searchlight][senlin][swift][zaqar] OpenStack Docs theme migration

Hi All, I have just pushed reviews to all the repos using os-api-ref, to allow us to migrate to the new sphinx theme gracefully. I have pushed reviews to the following repos: openstack/networking-sfc openstack/ceilometer openstack/glance openstack/heat openstack/ironic openstack/keystone

Re: [openstack-dev] [tc][cinder] tag:follows-standard-deprecation should be removed

On 11/08/2016 15:35, John Griffith wrote: > > > On Thu, Aug 11, 2016 at 7:14 AM, Erno Kuvaja > wrote: > > On Thu, Aug 11, 2016 at 2:47 PM, Sean McGinnis > > wrote: > >> >> > >> >>

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On 10/08/2016 16:04, Ihar Hrachyshka wrote: > Luigi Toscano wrote: > >> On Wednesday, 10 August 2016 10:42:41 CEST Ben Swartzlander wrote: >>> On 08/10/2016 04:33 AM, Duncan Thomas wrote: So I tried to get into helping with the cinder stable tree for a while, and

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On 09/08/2016 19:58, Ihar Hrachyshka wrote: > Walter A. Boring IV wrote: > >> On 08/08/2016 02:28 PM, Ihar Hrachyshka wrote: >>> Duncan Thomas wrote: >>> On 8 August 2016 at 21:12, Matthew Treinish wrote: Ignoring

Re: [openstack-dev] [requirements] History lesson please

On 09/08/2016 19:41, John Dickinson wrote: > > > On 9 Aug 2016, at 11:33, Ian Cordasco wrote: > >> >> >> -Original Message- >> From: John Dickinson >> Reply: OpenStack Development Mailing List (not for usage questions) >> >> Date: August

Re: [openstack-dev] [api][os-api-ref] openstackdocstheme integration

On 08/08/2016 13:47, Doug Hellmann wrote: > Excerpts from Hayes, Graham's message of 2016-08-08 11:28:35 +: >> On 05/08/2016 19:15, Doug Hellmann wrote: >>> Excerpts from Hayes, Graham's message of 2016-08-05 17:04:35 +: Hey, We look like we are getting close to merging the

Re: [openstack-dev] [api][os-api-ref] openstackdocstheme integration

On 05/08/2016 19:15, Doug Hellmann wrote: > Excerpts from Hayes, Graham's message of 2016-08-05 17:04:35 +: >> Hey, >> >> We look like we are getting close to merging the os-api-ref integration >> with openstackdocstheme. >> >> Unfortunately, there is no "phased" approach available - the

[openstack-dev] [api][os-api-ref] openstackdocstheme integration

Hey, We look like we are getting close to merging the os-api-ref integration with openstackdocstheme. Unfortunately, there is no "phased" approach available - the version released with compatibility for openstackdocstheme will not work with oslo.sphinx. So, we need a way to use oslosphinx until

Re: [openstack-dev] Project mascots update

On 05/08/2016 16:04, James Bottomley wrote: > On Thu, 2016-08-04 at 17:09 +1000, Mike Carden wrote: >> On Thu, Aug 4, 2016 at 4:26 PM, Antoni Segura Puimedon < >> toni+openstac...@midokura.com> wrote: >> >>> >>> It would be really awesome if, in true OSt and OSS spirit this work >>> happened in an

Re: [openstack-dev] [all][tc] establishing project-wide goals

On 02/08/2016 16:37, Doug Hellmann wrote: > Excerpts from Hayes, Graham's message of 2016-08-02 13:49:06 +: >> On 02/08/2016 14:37, Doug Hellmann wrote: >>> Excerpts from Hayes, Graham's message of 2016-08-02 11:53:37 +: On 29/07/2016 21:59, Doug Hellmann wrote: > One of the

Re: [openstack-dev] [tc] persistently single-vendor projects

On 02/08/2016 16:48, Steven Dake (stdake) wrote: > Responses inline: > > On 8/2/16, 8:13 AM, "Hayes, Graham" <graham.ha...@hpe.com> wrote: > >> On 02/08/2016 15:42, Flavio Percoco wrote: >>> On 01/08/16 10:19 -0400, Sean Dague wrote: >>

Re: [openstack-dev] [tc] persistently single-vendor projects

On 02/08/2016 15:42, Flavio Percoco wrote: > On 01/08/16 10:19 -0400, Sean Dague wrote: >> On 08/01/2016 09:58 AM, Davanum Srinivas wrote: >>> Thierry, Ben, Doug, >>> >>> How can we distinguish between. "Project is doing the right thing, but >>> others are not joining" vs "Project is actively

Re: [openstack-dev] [all][tc] establishing project-wide goals

On 02/08/2016 14:37, Doug Hellmann wrote: > Excerpts from Hayes, Graham's message of 2016-08-02 11:53:37 +: >> On 29/07/2016 21:59, Doug Hellmann wrote: >>> One of the outcomes of the discussion at the leadership training >>> session earlier this year was the idea that the TC should set some

Re: [openstack-dev] [all][tc] establishing project-wide goals

On 29/07/2016 21:59, Doug Hellmann wrote: > One of the outcomes of the discussion at the leadership training > session earlier this year was the idea that the TC should set some > community-wide goals for accomplishing specific technical tasks to > get the projects synced up and moving in the same

Re: [openstack-dev] [oslo][nova][requirements] Getting oslo.context 2.6.0 into the gate

On 28/07/2016 01:14, Tony Breeds wrote: > On Mon, Jul 18, 2016 at 04:09:54PM +0200, Markus Zoeller wrote: >> Since yesterday, Nova uses "oslo.context" 2.6.0 [1] but the needed >> change [2] is not yet in place, which broke "gate-nova-python27-db"[3]. >> Logstash counts 70 hits/h [4]. Most folks

Re: [openstack-dev] [all][tc] Equal Chances for all projects (was Plugins for all)

On 26/07/2016 18:47, Doug Hellmann wrote: > Excerpts from Hayes, Graham's message of 2016-07-26 13:48:35 +: >> On 26/07/2016 14:15, Sean Dague wrote: >>> On 07/26/2016 08:51 AM, Doug Hellmann wrote: >>> Given the amount of in-progress work to address the issue you've raised,

Re: [openstack-dev] [all][tc] Equal Chances for all projects (was Plugins for all)

On 26/07/2016 14:15, Sean Dague wrote: > On 07/26/2016 08:51 AM, Doug Hellmann wrote: > >> >> Given the amount of in-progress work to address the issue you've >> raised, I'm not convinced we need a global rule or policy. All of >> the teams mentioned are working toward the goal of providing

Re: [openstack-dev] [all][tc] Equal Chances for all projects (was Plugins for all)

On 26/07/2016 14:18, Doug Hellmann wrote: > Excerpts from Luigi Toscano's message of 2016-07-26 15:02:28 +0200: >> On Tuesday, 26 July 2016 08:34:27 CEST Doug Hellmann wrote: >>> Excerpts from Andrea Frittoli's message of 2016-07-26 10:24:07 +: What still requires work in Tempest is

[openstack-dev] [all][tc] Equal Chances for all projects (was Plugins for all)

hook into the API Reference, and API guides. This is great - and I am really happy about it. We still have issues trying to integrate with other areas in docs, and most non docs privileged projects end up with massive amounts of users docs in docs.openstack.org/developer/ , which is not ideal.

Re: [openstack-dev] [tc][all] Plugins for all

On 21/07/2016 16:49, Doug Hellmann wrote: > Excerpts from Hayes, Graham's message of 2016-07-19 16:59:20 +: >> On 19/07/2016 16:39, Doug Hellmann wrote: >>> Excerpts from Hayes, Graham's message of 2016-07-18 17:13:09 +: >>>> On 18/07/2016 17:57, Thierry Car

Re: [openstack-dev] [horizon] Plugin stability, failing tests etc.

We can still do multiple patches to fix any changes in the horizon library, and in the tip of the chain update the version in requirements. The risk has just been moved to the plugins, which is not ideal. It also makes downstream consumption *a lot* easier. > > > On 20 July 2016 at 13

Re: [openstack-dev] [horizon] Plugin stability, failing tests etc.

On 20/07/2016 10:16, Rob Cresswell wrote: > Hey all, > > So we've had a few issues with plugin stability recently, and its > apparent that many plugins are building off Horizon master as a > dependency. I would really advise against this. A more manageable > development process may be to: > > -

Re: [openstack-dev] [tc][all] Plugins for all

On 19/07/2016 16:39, Doug Hellmann wrote: > Excerpts from Hayes, Graham's message of 2016-07-18 17:13:09 +: >> On 18/07/2016 17:57, Thierry Carrez wrote: >>> Hayes, Graham wrote: >>>> [...] >>>> The point is that we were supposed to be a level field a

Re: [openstack-dev] [nova] gate "gate-nova-python27-db" is broken due to oslo.context 2.6.0

On 19/07/2016 15:11, Joshua Harlow wrote: > Hayes, Graham wrote: >> On 18/07/16 22:27, Ronald Bradford wrote: >>> Hi All, >>> >>> For Oslo libraries we ensure that API's are backward compatible for 1+ >>> releases. >>> When an O

Re: [openstack-dev] [nova] gate "gate-nova-python27-db" is broken due to oslo.context 2.6.0

On 18/07/16 22:27, Ronald Bradford wrote: > Hi All, > > For Oslo libraries we ensure that API's are backward compatible for 1+ > releases. > When an Oslo API adds a new class attribute (as in this example of > is_admin_project and 4 other attributes) added to Oslo Context in > 2.6.0, these are

Re: [openstack-dev] [tc][all] Plugins for all

On 18/07/2016 17:57, Thierry Carrez wrote: > Hayes, Graham wrote: >> [...] >> The point is that we were supposed to be a level field as a community >> but if we have examples like this, there is not a level playing field. > > While I generally agree on your goals here

Re: [openstack-dev] [tc][all] Plugins for all

On 17/07/2016 22:08, Jay Pipes wrote: > On 07/14/2016 12:21 PM, Hayes, Graham wrote: >> A lot of the effects are hard to see, and are not insurmountable, but >> do cause projects to re-invent the wheel. >> >> For example, quotas - there is no way for a project that is n

Re: [openstack-dev] [api] testing openstackdocstheme and os-api-ref for API reference info

On 15/07/2016 22:58, Anne Gentle wrote: > Hi -dev and -doc lists, and awesome devs Karen and Graham specifically - > > I want to figure out the best way to coordinate a release of both the > theme and the sphinx extension so that we can test and publish and > iterate on the new API reference

Re: [openstack-dev] [tc][all] Plugins for all

On 18/07/2016 01:59, Matt Riedemann wrote: > On 7/17/2016 4:13 PM, Jay Pipes wrote: >> On 07/15/2016 08:36 AM, Hayes, Graham wrote: >>> On 14/07/2016 21:20, Matt Riedemann wrote: >>>> And does this also include plugins within projects, like storage >>>>

Re: [openstack-dev] [tc][all] Plugins for all

On 15/07/2016 18:24, Luigi Toscano wrote: > On Friday, 15 July 2016 17:05:41 CEST Hayes, Graham wrote: >> On 15/07/2016 17:52, Luigi Toscano wrote: >>> On Friday, 15 July 2016 16:42:22 CEST Hayes, Graham wrote: >>>> On 15/07/2016 17:10, Andrew Laski wrote: >

Re: [openstack-dev] [tc][all] Plugins for all

On 15/07/2016 17:52, Luigi Toscano wrote: > On Friday, 15 July 2016 16:42:22 CEST Hayes, Graham wrote: >> On 15/07/2016 17:10, Andrew Laski wrote: > >>>> Tempest plugins are another example. Approximately 30 of the 36 >>>> current plugins are using resources t

Re: [openstack-dev] [tc][all] Plugins for all

On 15/07/2016 17:10, Andrew Laski wrote: > > > On Thu, Jul 14, 2016, at 03:21 PM, Hayes, Graham wrote: >> I just proposed a review to openstack/governance repo [0] that aims >> to have everything across OpenStack be plugin based for all cross >> project interaction, o

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

id, there is serious issues - with cross project fairness being one of the big ones (from my perspective anyway). I think getting concrete examples of problems and tackling them is a good road forward. - Graham > > From: Hayes, Graham [graham.ha..

Re: [openstack-dev] [tc][all] Plugins for all

On 14/07/2016 21:20, Matt Riedemann wrote: > On 7/14/2016 2:21 PM, Hayes, Graham wrote: >> I just proposed a review to openstack/governance repo [0] that aims >> to have everything across OpenStack be plugin based for all cross >> project interaction, or allow all projec

[openstack-dev] [tc][all] Plugins for all

I just proposed a review to openstack/governance repo [0] that aims to have everything across OpenStack be plugin based for all cross project interaction, or allow all projects access to the same internal APIs and I wanted to give a bit of background on my motivation, and how it came about.

[openstack-dev] [designate] Designate News Round Up

Hi All, Just a quick update on a few things! Mid Cycle = The Mid Cycle is confirmed for 22-26th of August. It will be in Dublin, in the city center. The address is 64 Mount Street Lower, Dublin 2. D02 TH77 Ireland I will be updating the page on the wiki with local hotels over the

[openstack-dev] [designate] Mid Cycle Dates - 22-26th August in Dublin, Ireland

At the IRC meeting yesterday we (finally) got some dates in place for the Mid Cycle. 22-26th August in Dublin, Ireland. Final location to be confirmed - this mid cycle is not being sponsored by anyone, so I need rough numbers before I go beg, borrow and / or steal a room, but it will be the city

[openstack-dev] [designate] Doc Smash - 13th July 2016 @ 14:30 UTC

Hi All, As we have seen over the last cycle or so, our docs need a bit of a refresh. We decided at the last IRC meeting that we should have a Doc Smash on the 13th July 2016 @ 14:30 UTC. The place holder bug is here - https://bugs.launchpad.net/designate/+bug/1590937 and I will break it out

Re: [openstack-dev] [designate][charms] Synchronising domains with new bind9 server

On 01/07/2016 18:04, Liam Young wrote: > Hi, > > I'm trying to add a new bind9 pool_target to an existing pool. The > problem is that the new bind server has no knowledge of the existing > zones as it missed the addzone commands when the domains where created. > It seems to me I have 3 options: >

Re: [openstack-dev] Designate issue

On 27/06/2016 12:24, sonali.pra...@accenture.com wrote: > Hi team, > > > > I have a doubt ..can we have designate and mysql in two different nodes?? > > And even the rabbitmq > > Will they communicate with each other like the normal openstack components. Hi Sonali, Yes, Designate can talk to

[openstack-dev] [designate] IRC Meeting today

Hi, Myself, Kiall and Federico are going to be caught up in some meetings today during the IRC meeting. Can someone chair the meeting? Thanks! - Graham __ OpenStack Development Mailing List (not for usage questions)

  1   2   3   >