[openstack-dev] [requirements][ffe] FFE for python-designateclient 2.10.0

Hi all, I would like to ask for a FFE to release python-designateclient 2.10.0 [1] We did not do a release at all during the rocky cycle, and this allows us to create a stable/rocky branch It just requires a U-C bump, and contains a few bug fixes from 2.9.0. Thanks, Graham 1 -

Re: [openstack-dev] [nova][searchlight][designate][telemetry][mistral][blazar][watcher][masakari]Possible deprecation of Nova's legacy notification interface

On 09/08/2018 15:27, Matt Riedemann wrote: > On 8/9/2018 8:44 AM, Graham Hayes wrote: >> Designate has no plans to swap or add support for the new interface in >> the near or medium term - we are more than willing to take patches, but >> we do not have the people pow

Re: [openstack-dev] [nova][searchlight][designate][telemetry][mistral][blazar][watcher][masakari]Possible deprecation of Nova's legacy notification interface

Designate has no plans to swap or add support for the new interface in the near or medium term - we are more than willing to take patches, but we do not have the people power to do it ourselves. Some of our users do use the old interface a lot - designate-sink is quite heavily embeded in some

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

On 01/08/2018 13:21, Andrey Kurilin wrote: > > > The second link from google search gives an opensource client written in > python https://github.com/raelgc/scudcloud . Also, there is something > which is written in golang. >   > > complete lack of any console clients (ditto), > > >

[openstack-dev] [designate][stable] Stable Core Team Updates

repositories (like DevStack) already). Thanks, Graham Hayes 1 - https://review.openstack.org/#/q/(project:openstack/designate+OR+project:openstack/python-designateclient+OR+project:openstack/designate-specs+OR+project:openstack/designate-dashboard+OR+project:openstack/designate-tempest-plugin

Re: [openstack-dev] [qa] [tempest] [patrole] Service client duplication between Tempest and Tempest plugins

On 23/07/2018 20:22, MONTEIRO, FELIPE C wrote: Hi, ** Intention ** Intention is to expand Patrole testing to some service clients that already exist in some Tempest plugins, for core services only. What exact projects does Patrole consider "core", and how are you making that decision? Is it

[openstack-dev] [designate] Meeting tomorrow

Unfortunately something has come up and I have an appointment I have to be at for our scheduled slot (11:00 UTC). Can someone else chair, or we can post pone the meeting for 1 week. Does anyone have any preferences? Thanks, - Graham

[openstack-dev] [designate] Meeting Times update

Hi All, We had talked about moving to a bi-weekly meeting, with alternating times, and I have updated the meetings repo [0] with some suggested times. Please speak up if these do not suit! - Graham 0 - https://review.openstack.org/#/c/573204/ signature.asc Description: OpenPGP digital

Re: [openstack-dev] [tc] StarlingX project status update

On 30/05/18 21:23, Mohammed Naser wrote: > Hi everyone: > > Over the past week in the summit, there was a lot of discussion > regarding StarlingX > and members of the technical commitee had a few productive discussions > regarding > the best approach to deal with a proposed new pilot project

Re: [openstack-dev] [tc] summary of joint leadership meeting from 20 May

On 05/06/18 16:22, Jay S Bryant wrote: > > > On 6/5/2018 7:31 AM, Sean McGinnis wrote: >> On Tue, Jun 05, 2018 at 11:21:16AM +0200, Thierry Carrez wrote: >>> Jay Pipes wrote: On 06/04/2018 05:02 PM, Doug Hellmann wrote: > [...]> Personally, I've very much enjoyed the separate PTGs

Re: [openstack-dev] [tc] [all] TC Report 18-20

-04-26T15:03:54 > -Original Message----- > From: Graham Hayes <g...@ham.ie> > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > <openstack-dev@lists.openstack.org> > Date: Tuesday, 15 May 2018 at 18:22 > To: "openstack-dev@lists.open

Re: [openstack-dev] [tc] [all] TC Report 18-20

her gap in reports. > > # Elections > > The elections were for seven positions. Of those, three are new to > the TC: Graham Hayes, Mohammed Naser, Zane Bitter. Having new people > is _great_. There's a growing sense that the TC needs to take a more > active role in helping adapt the

Re: [openstack-dev] [all][tc][ptls] final stages of python 3 transition

On 08/05/18 16:53, Doug Hellmann wrote: > Excerpts from Graham Hayes's message of 2018-05-08 16:28:46 +0100: >> On 08/05/18 16:09, Zane Bitter wrote: >>> On 30/04/18 17:16, Ben Nemec wrote: > Excerpts from Doug Hellmann's message of 2018-04-25 16:54:46 -0400: >> 1. Fix oslo.service

Re: [openstack-dev] [all][tc][ptls] final stages of python 3 transition

On 08/05/18 16:09, Zane Bitter wrote: > On 30/04/18 17:16, Ben Nemec wrote: >>> Excerpts from Doug Hellmann's message of 2018-04-25 16:54:46 -0400: 1. Fix oslo.service functional tests -- the Oslo team needs help     maintaining this library. Alternatively, we could move all    

Re: [openstack-dev] [tc][docs] documenting openstack "constellations"

On 02/05/18 20:11, Doug Hellmann wrote: > Excerpts from Zane Bitter's message of 2018-05-02 11:38:55 -0400: >> On 01/05/18 16:21, Doug Hellmann wrote: >>> Excerpts from Andreas Jaeger's message of 2018-05-01 21:51:19 +0200: On 05/01/2018 04:08 PM, Doug Hellmann wrote: > The TC has had an

Re: [openstack-dev] [designate] Meeting Times - change to office hours?

ment Mailing List (not for usage questions) >> *Subject:* Re: [openstack-dev] [designate] Meeting Times - change to >> office hours? >> 2018-04-23 13:11 GMT+02:00 Graham Hayes <g...@ham.ie>: >>> Hi All, >>> >>> We moved our meeting time to 14:00UTC

Re: [openstack-dev] [tc] campaign question: How "active" should the TC be?

On 23/04/18 14:27, Doug Hellmann wrote: > [This is meant to be one of (I hope) several conversation-provoking > questions directed at prospective TC members to help the community > understand their positions before considering how to vote in the > ongoing election.] > > We frequently have

Re: [openstack-dev] [tc] campaign question related to new projects

On 23/04/18 18:14, Doug Hellmann wrote: > Excerpts from Graham Hayes's message of 2018-04-23 17:23:20 +0100: >> On 23/04/18 17:14, Doug Hellmann wrote: >>> Excerpts from Graham Hayes's message of 2018-04-23 16:27:04 +0100: On 23/04/18 16:04, Doug Hellmann wrote: > Excerpts from Graham

Re: [openstack-dev] [tc] campaign question related to new projects

On 23/04/18 17:14, Doug Hellmann wrote: > Excerpts from Graham Hayes's message of 2018-04-23 16:27:04 +0100: >> On 23/04/18 16:04, Doug Hellmann wrote: >>> Excerpts from Graham Hayes's message of 2018-04-23 12:15:24 +0100: 7On 20/04/18 22:26, Doug Hellmann wrote: > Without letting

Re: [openstack-dev] [tc] campaign question: How should we handle projects with overlapping feature sets?

On 23/04/18 14:50, Doug Hellmann wrote: > [This is meant to be one of (I hope) several conversation-provoking > questions directed at prospective TC members to help the community > understand their positions before considering how to vote in the > ongoing election.] > > In the course of

Re: [openstack-dev] [tc] campaign question related to new projects

On 23/04/18 16:04, Doug Hellmann wrote: > Excerpts from Graham Hayes's message of 2018-04-23 12:15:24 +0100: >> 7On 20/04/18 22:26, Doug Hellmann wrote: >> >>> Without letting the conversation devolve too much into a discussion >>> of Adjutant's case, please talk a little about how you would

Re: [openstack-dev] [tc] campaign question: How can we make contributing to OpenStack easier?

On 23/04/18 15:06, Doug Hellmann wrote: > [This is meant to be one of (I hope) several conversation-provoking > questions directed at prospective TC members to help the community > understand their positions before considering how to vote in the > ongoing election.] > > Over the last year we have

Re: [openstack-dev] [all] Topics for the Board+TC+UC meeting in Vancouver

On 18/04/18 11:38, Chris Dent wrote: > On Tue, 17 Apr 2018, Thierry Carrez wrote: > >> So... Is there any specific topic you think we should cover in that >> meeting ? > > The topics: > > 1. What are we to do, as a community, when external pressures for > results are not matched by contribution

Re: [openstack-dev] [tc] campaign question related to new projects

7On 20/04/18 22:26, Doug Hellmann wrote: > Without letting the conversation devolve too much into a discussion > of Adjutant's case, please talk a little about how you would evaluate > a project's application in general. What sorts of things do you > consider when deciding whether a project

[openstack-dev] [designate] Meeting Times - change to office hours?

Hi All, We moved our meeting time to 14:00UTC on Wednesdays, but attendance has been low, and it is also the middle of the night for one of our cores. I would like to suggest we have an office hours style meeting, with one in the UTC evening and one in the UTC morning. If this seems reasonable

Re: [openstack-dev] [all] How to handle python3 only projects

On 17/04/18 07:10, Adrian Turjak wrote: > Hello devs, > > The python27 clock of doom ticks closer to zero > (https://pythonclock.org/) and officially dropping python27 support is > going to have to happen eventually, that though is a bigger topic. > > Before we get there outright what we should

[openstack-dev] [election][tc] TC Candidacy for Graham Hayes

e the go to software for Infrastructure as a Service. Thanks again, - Graham 1 - http://stackalytics.com/?release=all=commits_id=grahamhayes 2 - https://www.openstack.org/community/members/profile/12766/graham-hayes 3 - https://review.openstack.org/#/q/project:openstack/governance+(commentby:%22Graham+Haye

Re: [openstack-dev] [all][requirements] uncapping eventlet

On 05/04/18 16:47, Matthew Thode wrote: > eventlet-0.22.1 has been out for a while now, we should try and use it. > Going to be fun times. > > I have a review projects can depend upon if they wish to test. > https://review.openstack.org/533021 It looks like we may have an issue with oslo.service

Re: [openstack-dev] [stable][release] Remove complex ACL changes around releases

On 26/03/2018 14:33, Thierry Carrez wrote: > Hi! > > TL;DR: > We used to do complex things with ACLs for stable/* branches around > releases. Let's stop doing that as it's not really useful anyway, and > just trust the $project-stable-maint teams to do the right thing. > > > Current

Re: [openstack-dev] Pros and Cons of face-to-face meetings

On 08/03/18 18:06, Jeremy Stanley wrote: > On 2018-03-08 17:49:35 + (+), Flint WALRUS wrote: >> Pretty easy, put the PTG online with a livestream on >> YouTube/Hangout/whatever platform that will then be saved and could even be >> watched later on! >> >> It’s just a matter of some hardware

Re: [openstack-dev] [tc] [all] TC Report 18-10

On 07/03/18 20:24, Lance Bragstad wrote: > > > On 03/07/2018 06:12 AM, Chris Dent wrote: >> >> HTML: https://anticdent.org/tc-report-18-10.html >> >> This is a TC Report, but since everything that happened in its window >> of observation is preparing for the >>

[openstack-dev] [designate] V1 API is now fully removed

I saw [1] and realised that we should be more explicit about the upcoming release. As highlighted in [2], this email is a reminder that the long awaited removal of the DNS V1 API is now complete with [3]. This means from Queens onwards it will not be possible to re-enable the V1 API (we have had

Re: [openstack-dev] [osc][python-openstackclient] Consistency of option name

moving it to "availability-zone" would be better than "zone". I think that point has been made, so lets leave it at that. - Graham > > Dean Troyer <dtro...@gmail.com> wrote on 02/12/2018 10:24:05 AM: >> >> On Mon, Feb 12, 2018 at 9:13 AM, Graham Hayes <g.

Re: [openstack-dev] [osc][python-openstackclient] Consistency of option name

On 12/02/18 14:51, Dean Troyer wrote: > On Mon, Feb 12, 2018 at 7:50 AM, Graham Hayes <g...@ham.ie> wrote: >> Please please move to `availability-zone` - zone is a DNS zone (seen as >> Keystone took Domain :) ) within OSC. > > As stated in another message, changing

Re: [openstack-dev] [osc][python-openstackclient] Consistency of option name

On 12/02/18 04:18, Hongbin Lu wrote: > Hi all, > > I was working on the OSC plugin of my project and trying to choose a CLI > option to represent the availability zone of the container. When I came > across the existing commands, I saw some inconsistencies on the naming. > Some commands use the

Re: [openstack-dev] [keystone][nova][ironic][heat] Do we want a BM/VM room at the PTG?

On 31/01/18 17:22, Dmitry Tantsur wrote: > On 01/31/2018 06:15 PM, Matt Riedemann wrote: >> On 1/30/2018 9:33 AM, Colleen Murphy wrote: >>> At the last PTG we had some time on Monday and Tuesday for >>> cross-project discussions related to baremetal and VM management. We >>> don't currently have

Re: [openstack-dev] [tc] [all] TC Report 18-05

On 30/01/18 18:34, Chris Dent wrote: > > Linkified: https://anticdent.org/tc-report-18-05.html > > Your author has been rather ill, so this week's TC Report will be a > bit abridged and mostly links. I'll try to return with more robust > commentary next week. > > ## RDO Test Days > > dmsimard

Re: [openstack-dev] [tc] [all] TC Report 18-05

On 30/01/18 18:34, Chris Dent wrote: > > ## Today's Board Meeting > > I attended [today's Board > Meeting](https://wiki.openstack.org/wiki/Governance/Foundation/30Jan2018BoardMeeting) > > but it seems that according to the [transparency >

[openstack-dev] [designate] designate-core updates

Another update to the designate-core team: + eandersson - timsim - kiall eandersson has been a long term reviewer and end user of designate who has consistently performed good, and detail orientated reviews. Unfortunately both Kiall and Tim have moved on to other areas, and as such have not had

Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

On 19/01/18 16:27, Andrea Frittoli wrote: > > Thanks for the summary! > > To be honest I don't see why this decision has to be difficult to take. I think the confusion comes from one thing being decided already, and now conflicting direction is being given to teams, without anyone updating

Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

On 19/01/18 00:52, Ken'ichi Ohmichi wrote: > 2018-01-18 12:36 GMT-08:00 Doug Hellmann : >> Excerpts from Doug Hellmann's message of 2018-01-18 15:21:12 -0500: >>> Excerpts from Graham Hayes's message of 2018-01-18 19:25:02 +: On 18/01/18 18:52, Doug Hellmann

Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

On 19/01/18 03:28, Ghanshyam Mann wrote: > On Thu, Jan 11, 2018 at 10:06 PM, Colleen Murphy wrote: >> Hi everyone, >> >> We have governance review under debate[1] that we need the community's help >> on. >> The debate is over what recommendation the TC should make to the

Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

On 19/01/18 04:10, Ghanshyam Mann wrote: > On Thu, Jan 18, 2018 at 11:22 PM, Graham Hayes <g...@ham.ie> wrote: >> On 18/01/18 16:25, Doug Hellmann wrote: >>> Excerpts from Graham Hayes's message of 2018-01-18 15:33:12 +: >> >> >> >>> >

Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

On 18/01/18 18:52, Doug Hellmann wrote: > Excerpts from Graham Hayes's message of 2018-01-18 17:52:39 +: >> On 18/01/18 16:25, Doug Hellmann wrote: >>> Excerpts from Graham Hayes's message of 2018-01-18 15:33:12 +: >> >> >> >>> >>> In the past the QA team agreed to accept

Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

On 18/01/18 16:25, Doug Hellmann wrote: > Excerpts from Graham Hayes's message of 2018-01-18 15:33:12 +: > > In the past the QA team agreed to accept trademark-related tests from > all projects in the tempest repo. Has that changed? > There has not been an explict rejection but in all

Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

On 11/01/18 16:36, Colleen Murphy wrote: > Hi everyone, > > We have governance review under debate[1] that we need the community's help > on. > The debate is over what recommendation the TC should make to the Interop team > on where the tests it uses for the OpenStack trademark program should

Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

On 12/01/18 09:49, Luigi Toscano wrote: > On Thursday, 11 January 2018 23:52:00 CET Matt Riedemann wrote: >> On 1/11/2018 10:36 AM, Colleen Murphy wrote: >>> 1) All trademark-related tests should go in the tempest repo, in >>> accordance >>> >>> with the original resolution. This would mean

[openstack-dev] [designate] Meeting Next Week + Other Highlights

Hi All, I am going to be on vacation next week, and will not be able to run the weekly IRC meeting. We can either skip, or if someone steps up to run it we can go ahead. I will be around enough to do the q3 release. Also a reminder that the etherpad for planning the PTG in Dublin is available

Re: [openstack-dev] [designate] state of pdns4 backend

Hi Ritesh, see in line: On 08/01/18 23:02, Ritesh Anand wrote: > Hi Stackers, > > I see that we moved from PowerDNS Backend to PDNS4 backend, I have a few > questions in that regard: > > 1. Should powerdns 3.4 (with PowerDNS backend) continue to work fine on > Pike OpenStack? Yes - as long as

Re: [openstack-dev] [api] APIs schema consumption discussion

On 22/11/17 20:04, Graham Hayes wrote: > When I was talking to Gil about it, I suggested writing a new sphinx / > docutils formatter. I am not sure how feasible it would be, but it could > be possible (as sphinx has the whole page tree in memory when writing it > out, we may be ab

Re: [openstack-dev] [os-api-ref][doc] Adding openstack-doc-core to os-api-ref

On 04/01/18 15:39, Stephen Finucane wrote: > I'm not sure what the procedure for this is but here goes. > > I've noticed that the 'os-api-ref' project seems to have its own group > of cores [1], many of whom are no longer working on OpenStack (at > least, not full-time), and has a handful of open

Re: [openstack-dev] [designate] need help with managed resource tenant ID

On 03/01/18 17:50, Ritesh Anand wrote: > Hi Stackers, > > Happy new year!! > > I am working around Designate service and have been seeing this warning > in designate-central.log: > 2017-12-12 06:25:47.022 31171 WARNING designate.central.service [-] > Managed Resource Tenant ID is not properly

Re: [openstack-dev] [tc] [all] TC Report 49

On 06/12/17 23:33, James E. Blair wrote: > Chris Dent writes: > >> The expansion of the Foundation was talked about at the summit in >> Sydney, but having something happen this quickly was a bit of a >> surprise, leading to some [questions in >>

Re: [openstack-dev] [qa] [patrole] Question regarding Patrole API coverage

On 29/11/17 15:11, Andrea Frittoli wrote: > > > On Wed, Nov 29, 2017 at 2:28 PM Peng Liu > wrote: > > Hi Team, > > Hi Peng >   > > I have a question regarding to the API coverage of Patrole. > Currently, Patrole as a Tempest plugin

Re: [openstack-dev] [designate] Meeting Time

On 22/11/17 17:16, Graham Hayes wrote: > So, after looking at the responses, we have a winning > meeting time. > > 14:00 UTC (I propose staying on Wednesday) [1]. > > If there is no objections by the end of the week, I will > update the meeting time on eavesdrop.open

Re: [openstack-dev] [api] APIs schema consumption discussion

On 16/11/17 01:56, Gilles Dubreuil wrote: > > On 15/11/17 03:07, Doug Hellmann wrote: >> Excerpts from Gilles Dubreuil's message of 2017-11-14 10:15:02 +1100: >>> Hi, >>> >>> Follow-up conversation from our last "API SIG feedback and discussion >>> session" at Sydney Summit [1], about APIs

[openstack-dev] [designate] Core Reviewers

I have decided to start cycling out old core reviewers who are not as active with new, more active reviewers. The first change is - Eric Larson (elarson) + Jens Harbott (frickler) Unfortunately elarson has moved companies, and frickler has been consistently providing good, regular reviews.

[openstack-dev] [designate] Meeting Time

So, after looking at the responses, we have a winning meeting time. 14:00 UTC (I propose staying on Wednesday) [1]. If there is no objections by the end of the week, I will update the meeting time on eavesdrop.openstack.org Thanks, Graham 1 -

[openstack-dev] [all] ujson "drop in" replacement

Hey all, There seems to be a lot of "replace oslo.serization / native python json with UltraJSON (otherwise known as ujson) patches over the last few weeks. We should be careful - it is not a drop in replacement. e.g. - Normal python JSON: >>> import json >>>

[openstack-dev] [designate] Skipping this weeks meeting

Hi, I have a conflict this week with a different meeting. I would suggest we skip this week unless there is someone who can chair it in my absence? Thanks, Graham signature.asc Description: OpenPGP digital signature __

Re: [openstack-dev] [tc][election] Question for candidates: How do you think we can make our community more inclusive?

On 13/10/17 13:45, Flavio Percoco wrote: > Greetings, > > Some of you, TC candidates, expressed concerns about diversity and > inclusiveness > (or inclusivity, depending on your taste) in your candidacy. I believe > this is a > broad, and some times ill-used, topic so, I'd like to know, from

Re: [openstack-dev] [all][tc] TC Candidates: what does an OpenStack user look like?

On 12/10/17 17:51, Zane Bitter wrote: > (Reminder: we are in the TC election campaigning period, and we all have > the opportunity to question the candidates. The campaigning period ends > on Saturday, so make with the questions.) > > > In my head, I have a mental picture of who I'm building

Re: [openstack-dev] [tc][election] Question for the candidates

There is one topic I have been pretty vocal about wanting the TC to deal with - encouraging cross project teams (Docs / QA etc) to start migrating to providing tooling, rather than direct services to projects. I am aware I am (re)opening a can of worms, but I think as a community we have started

Re: [openstack-dev] [tc][election] Question for the candidates

For me "Write down OpenStack principles" [1] signaled the start of an more open TC. It was writing down principles that I had been told about verbally when I started working on OpenStack, and had been part of a "shared understanding" for some people who had been in the community for a while. This

Re: [openstack-dev] [ptls] Sydney Forum Project Onboarding Rooms

Can I add designate? I will be there to look after the room. Thanks, Graham On Tue, 10 Oct 2017, at 20:20, Kendall Nelson wrote: > Added :) > -Kendall (diablo_rojo) > > On Tue, Oct 10, 2017 at 2:11 AM Spyros Trigazis > wrote:>> Magnum - Spyros Trigazis -

[openstack-dev] [tc][election] TC Candidacy

for taking the time to read this, Graham Hayes (mugsie) 1 - http://stackalytics.com/?release=all=commits_id=grahamhayes 2 - http://lists.openstack.org/pipermail/openstack-dev/2016-July/099285.html 3 - http://graham.hayes.ie/posts/openstack-designate-where-we-are/ 4 - https://review.openstack.org/#/c

[openstack-dev] [Designate] Meeting time

Hi All, With a change of contributors, we now have a meeting at a time that is inconvenient for most people. I have a new survey for us to try and find a more suitable time here: https://docs.google.com/forms/d/e/1FAIpQLSeF3P4545zBIxL_PnQnm8GshG2kjgRUylNTNjJCxLUhlDKCDA/viewform If you are

Re: [openstack-dev] [Oslo][Designate][Congress] Problem with from_dict overrides and new oslo.context release

On 09/10/17 18:03, Ben Nemec wrote: > Hi, > > I brought up the fix[1] I proposed for [2] in the Oslo meeting today, > and it led to some good discussion that we wanted to take to a broader > audience.  In particular, the projects that are affected by the bug. > > The oslo.context change I

Re: [openstack-dev] [ptl][tc] Accessible upgrade support

On Thu, 5 Oct 2017, at 09:50, Thierry Carrez wrote: > Matt Riedemann wrote: > > What's the difference between this tag and the zero-impact-upgrades tag? > > I guess the accessible one is, can a user still ssh into their VM while > > the nova compute service is being upgraded. The

Re: [openstack-dev] [designate] multi domain usage for handlers

s.de > > https://www.noris.de - Mehr Leistung als Standard > Vorstand: Ingo Kraupa (Vorsitzender), Joachim Astel > Vorsitzender des Aufsichtsrats: Stefan Schnabel - AG Nürnberg HRB 17689 > >   > >   > >   > >   > > Am 28.09.2017 um 18:54 schrie

Re: [openstack-dev] [designate] multi domain usage for handlers

On 28/09/17 17:06, Kim-Norman Sahm wrote: > Hi, > > i'm currently testing designate and i have a question about the > architecture. > We're using openstack newton with keystone v3 and thus the keystone > domain/project structure. > > I've tried the global nova_fixed and neutron_floating_ip

[openstack-dev] [designate] Skip meeting this week

Hi All, I have just realised I am double booked for the meeting time this week. We are in a quiet persiod, so I suggest skipping this weeks meeting. Thanks, Graham 0x23BA8E2E.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature

[openstack-dev] [Designate] PTL Nomination

to add clear install / configuration documentation per driver. Finally, I want to ensure that the optional OpenStack DNS InterOp program is implemented, and complete for the next InterOp version. Thank you for taking the time to read this, and your interest in the project. - Graham Hayes

Re: [openstack-dev] [release][monasca][designate][requirements] late library release for monasca-statsd

On 25/07/17 12:12, Doug Hellmann wrote: > The monasca team has requested a late release of monasca-statsd. > As far as I can tell, only other team using the library is designate: > > $ whatuses monasca-statsd > deb-designate requirements.txt monasca-statsd>=1.1.0 # > Apache-2.0

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

On 24/07/17 20:37, Octave J. Orgeron wrote: >> >> Rather than having all the projects make use of >> oslo_db.sqlalchemy.ndb.AutoStringTinyText / AutoStringSize, we add new >> generic types to oslo.db : >> >> oslo_db.sqlalchemy.types.SmallString >> oslo_db.sqlalchemy.types.String >> >> (or

Re: [openstack-dev] [all] Cleaning up inactive meetbot channels

On 19/07/17 20:24, Jeremy Stanley wrote: > For those who are unaware, Freenode doesn't allow any one user to > /join more than 120 channels concurrently. This has become a > challenge for some of the community's IRC bots in the past year, > most recently the "openstack" meetbot (which not only

Re: [openstack-dev] [openstack-ansible][neutron][designate][dns] dns plugin suppressed in neutron.conf.j2 template

On 30/06/17 13:29, Lawrence J. Albinson wrote: > Good Afternoon Colleagues, > > I've been working to incorporate dynamic dns/designate updating from > neutron and nova within an OpenStack-Ansible built environment. > > I note that the dns plugin is explicitly suppressed in the >

Re: [openstack-dev] [openstack-ansible][neutron][designate] Failure trying to set dns_domain from command line

ate] > url = etc > > Kind regards, Lawrence Yes, that is the right section. - Graham > > On 27/06/17 16:57, Graham Hayes wrote: >> On 27/06/17 16:36, Lawrence J. Albinson wrote: >>> Hi Graham, >>> >>> Many thanks for the pointer. I ha

Re: [openstack-dev] [openstack-ansible][neutron][designate] Failure trying to set dns_domain from command line

the two together will fix things. I shall know by the > morning. > > Again, many thanks. > > Kind regards, Lawrence > > From: Graham Hayes > Sent: 27 June 2017 16:14 > To: openstack-dev@lists.openstack.org > Subject: Re: [o

Re: [openstack-dev] [openstack-ansible][neutron][designate] Failure trying to set dns_domain from command line

On 27/06/17 15:01, Lawrence J. Albinson wrote: > Hello Colleagues, > > I am trying to enable dynamic updating of DNSaaS when a port or VM is > created/deleted. > > I have DNSaaS working with Bind9 as the back-end and I am able to > manually create/update/delete entries with the openstack client

Re: [openstack-dev] [openstack-ansible][designate][bind9] Looking for ways to limit users to adding hosts within fixed personal domain

cloud|internal).example.com. Thanks, - Graham > Kind regards, Lawrence > > Lawrence J Albinson > > From: Graham Hayes > Sent: 20 June 2017 13:01 > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [openstack-an

Re: [openstack-dev] [openstack-ansible][designate][bind9] Looking for ways to limit users to adding hosts within fixed personal domain

On 20/06/17 12:37, Lawrence J. Albinson wrote: > I am trying to find pointers to how I might limit non-privileged users > to a single domain when adding hosts to Designate. > > It is a private OpenStack cloud and each user will have a personal > sub-domain of a common organisational domain, like

Re: [openstack-dev] [all][tc] Moving away from "big tent" terminology

On 19/06/17 16:11, Jay Pipes wrote: > On 06/16/2017 05:18 AM, Graham Hayes wrote: >> On 15/06/17 22:35, Ed Leafe wrote: >>> On Jun 15, 2017, at 3:35 PM, Jeremy Stanley <fu...@yuggoth.org> wrote: >>> >>>> For me it's one of the most annoying yet challe

Re: [openstack-dev] [all][tc] Moving away from "big tent" terminology

On 15/06/17 22:35, Ed Leafe wrote: > On Jun 15, 2017, at 3:35 PM, Jeremy Stanley wrote: > >> For me it's one of the most annoying yet challenging/interesting >> aspects: free software development is as much about community and >> politics as it is actual software development

Re: [openstack-dev] [qa][tc][all] Tempest to reject trademark tests

On 01/06/17 01:30, Matthew Treinish wrote: > On Wed, May 31, 2017 at 03:45:52PM +, Jeremy Stanley wrote: >> On 2017-05-31 15:22:59 + (+), Jeremy Stanley wrote: >>> On 2017-05-31 09:43:11 -0400 (-0400), Doug Hellmann wrote: >>> [...] it's news to me that they're considering

Re: [openstack-dev] [qa][tc][all] Tempest to reject trademark tests

On 31/05/17 16:45, Jeremy Stanley wrote: > On 2017-05-31 15:22:59 + (+), Jeremy Stanley wrote: >> On 2017-05-31 09:43:11 -0400 (-0400), Doug Hellmann wrote: >> [...] >>> it's news to me that they're considering reversing course. If the >>> QA team isn't going to continue, we'll need to

Re: [openstack-dev] [qa] [tc] [all] more tempest plugins (was Re: [tc] [all] TC Report 22)

On 31/05/17 11:22, Chris Dent wrote: > On Wed, 31 May 2017, Graham Hayes wrote: >> On 30/05/17 19:09, Doug Hellmann wrote: >>> Excerpts from Chris Dent's message of 2017-05-30 18:16:25 +0100: >>>> Note that this goal only applies to tempest _plugins_. Projec

Re: [openstack-dev] [tc] [all] TC Report 22

On 30/05/17 19:09, Doug Hellmann wrote: > Excerpts from Chris Dent's message of 2017-05-30 18:16:25 +0100: >> >> There's no TC meeting this week. Thierry did a second weekly status >> report[^1]. There will be a TC meeting next week (Tuesday, 6th June >> at 20:00 UTC) with the intention of

Re: [openstack-dev] [tc] [all] TC Report 22

On 30/05/17 18:16, Chris Dent wrote: > > There's no TC meeting this week. Thierry did a second weekly status > report[^1]. There will be a TC meeting next week (Tuesday, 6th June > at 20:00 UTC) with the intention of discussing the proposals about > postgreSQL (of which more below). Here are my

Re: [openstack-dev] [Openstack-dev] [Designate]

On 26/05/17 13:35, Andrea Frittoli wrote: > On Thu, May 25, 2017 at 5:27 PM Carmine Annunziata > > > wrote: > > Hi everyone, > I integrated Designate in Openstack by devstack, now i'm using the > new default

Re: [openstack-dev] [oslo][requirements][designate][cinder] Reverting eventlet version bump

On 04/04/17 11:11 -0700, Clint Byrum wrote: Excerpts from Monty Taylor's message of 2017-04-04 12:19:36 -0500: On 04/04/2017 09:19 AM, Jay S Bryant wrote: > Monty, > > I agree with your approach. Think we should not break other projects > with a change like this and the answer thus far has

Re: [openstack-dev] [kubernetes][go] External OpenStack Cloud Provider for Kubernetes

On 24/03/17 08:46 -0700, Antoni Segura Puimedon wrote: On Friday, March 24, 2017 at 3:59:18 PM UTC+1, Graham Hayes wrote: On 24/03/17 10:27 -0400, Davanum Srinivas wrote: >Folks, > >As discussed in the etherpad: >https://etherpad.openstack.org/p/go-an

Re: [openstack-dev] [kubernetes][go] External OpenStack Cloud Provider for Kubernetes

On 24/03/17 10:27 -0400, Davanum Srinivas wrote: Folks, As discussed in the etherpad: https://etherpad.openstack.org/p/go-and-containers Here's a request for a repo in OpenStack: https://review.openstack.org/#/c/449641/ This request pulls in the existing code from kubernetes/kubernetes repo