Re: [openstack-dev] better name for placement

On Tue, Sep 4, 2018 at 7:01 PM, Jay Pipes wrote: On 09/04/2018 12:59 PM, Balázs Gibizer wrote: On Tue, Sep 4, 2018 at 6:25 PM, Jay Pipes wrote: On 09/04/2018 12:17 PM, Doug Hellmann wrote: Excerpts from Jay Pipes's message of 2018-09-04 12:08:41 -0400: On 09/04/2018 11:44 AM, Doug

Re: [openstack-dev] better name for placement

On 09/04/2018 12:59 PM, Balázs Gibizer wrote: On Tue, Sep 4, 2018 at 6:25 PM, Jay Pipes wrote: On 09/04/2018 12:17 PM, Doug Hellmann wrote: Excerpts from Jay Pipes's message of 2018-09-04 12:08:41 -0400: On 09/04/2018 11:44 AM, Doug Hellmann wrote: Excerpts from Chris Dent's message of

[openstack-dev] Retiring openstack-infra/odsreg and openstack-infra/puppet-odsreg

Puppet-odsreg is unused nowadays and it seems that odsreg is unused as well. I'll propose changes to retire them with topic "retire-odsreg", Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix

[openstack-dev] [neutron] PTG agenda

Dear Neutron Team, I have scheduled all the topics that were proposed for the PTG in Denver here: https://etherpad.openstack.org/p/neutron-stein-ptg. Please go to line 128 and onwards to see the detailed schedule. Please reach out to me should we need to make any changes or adjustments Best

Re: [openstack-dev] better name for placement

On Tue, 4 Sep 2018, Jay Pipes wrote: I wasn't in YVR, which explains why I's never heard of it. There's a number of misconceptions in the above document about the placement service that don't seem to have been addressed. I'm wondering if its worth revisiting the topic in Denver with the

Re: [openstack-dev] better name for placement

On Sep 4, 2018, at 12:44 PM, Chris Dent wrote: > > Changing the name, again, is painful. Please, let's not do it. I was in favor of coming up with a project name for placement. It was discussed, and the decision was made not to do so. We have since moved forward with the outcome of that

Re: [openstack-dev] [openstack-ansible][kolla-ansible][tripleo] ansible roles: where they live and what do they do

On Thu, Aug 9, 2018 at 2:43 PM, Mohammed Naser wrote: > Hi Alex, > > I am very much in favour of what you're bringing up. We do have > multiple projects that leverage Ansible in different ways and we all > end up doing the same thing at the end. The duplication of work is > not really

[openstack-dev] [election][tc] announcing candidacy

Greetings Stackers! I hereby announce my candidacy for a position on the OpenStack Technical Committee. In many respects I consider myself a maverick, except reality is sometimes entirely different than my own self perception, upon reflection. I find self reflection and introspection to be

Re: [openstack-dev] better name for placement

On Tue, 4 Sep 2018, Jay Pipes wrote: Either one works for me. Though I'm pretty sure that it isn't necessary. The reason it isn't necessary is because the stuff in the top-level placement package isn't meant to be imported by anything at all. It's the placement server code. Yes. If some

Re: [openstack-dev] better name for placement

On Tue, Sep 4, 2018 at 6:25 PM, Jay Pipes wrote: On 09/04/2018 12:17 PM, Doug Hellmann wrote: Excerpts from Jay Pipes's message of 2018-09-04 12:08:41 -0400: On 09/04/2018 11:44 AM, Doug Hellmann wrote: Excerpts from Chris Dent's message of 2018-09-04 15:32:12 +0100: On Tue, 4 Sep 2018,

[openstack-dev] [goals][python3] week 4 update

Subject: [goal][python3] week 4 update This is the 4th week of the "Run under Python 3 by default" goal (https://governance.openstack.org/tc/goals/stein/python3-first.html). == What we learned last week == We have discovered a few repositories with tests defined in project-config so that they

[openstack-dev] kolla-ansible 7.0.0.0rc1 (rocky)

Hello everyone, A new release candidate for kolla-ansible for the end of the Rocky cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/kolla-ansible/ Unless release-critical issues are found that warrant a release candidate respin, this candidate

Re: [openstack-dev] better name for placement

On 09/04/2018 01:17 PM, Balázs Gibizer wrote: On Tue, Sep 4, 2018 at 7:01 PM, Jay Pipes wrote: On 09/04/2018 12:59 PM, Balázs Gibizer wrote: On Tue, Sep 4, 2018 at 6:25 PM, Jay Pipes wrote: On 09/04/2018 12:17 PM, Doug Hellmann wrote: Excerpts from Jay Pipes's message of 2018-09-04

[openstack-dev] [neutron] Weekly meeting canceled on Tuesday 11th

Dear Neutron Team, Due to the PTG in Denver, the Neutron weekly team on Tuesday 11th at 1400 UTC is canceled. We will resume our meeting on Monday September 17th at 2100 UTC Best regards Miguel __ OpenStack Development

Re: [openstack-dev] [tripleo-ansible] Future plans

Hi Martin,On Mon, 2018-09-03 at 21:16 +0200, Martin Magr wrote: > Gretings, > >   since I did not find any blueprint regarding proper usage of > tripleo-ansible, I would like to ask how exactly we plan to use > tripleo-ansible project, what should be the proper structure of > roles/playbooks,

[openstack-dev] [horizon][stable] Removing Inactive Cores

Hi team, Since we're at the beginning of Stein release cycle, I think it's a good time to do some cleanup in our core teams. First of all, I would like to say a big Thank you to everybody who contributed as Core Reviewer to Horizon. Unfortunately, some people became inactive as reviewers during

Re: [openstack-dev] [tripleo] using multiple roles

Is it possible to have the roles_data.yaml file generated when running "openstack overcloud deploy"?? On Tue, Sep 4, 2018 at 4:52 PM Alex Schultz wrote: > On Tue, Sep 4, 2018 at 2:31 AM, Samuel Monderer > wrote: > > Hi, > > > > Due to many different HW in our environment we have multiple

[openstack-dev] [tripleo] Posibilities to aggregate/merge configs across templates

Hi all, I want to start discussion on: how to solve issue with merging environment values in TripleO. Description: In TripleO we experience some issues related to setting parameters in heat templates. First, it isn't possible to set some params as ultimate source of truth (disallow to overwrite

Re: [openstack-dev] [nova] [placement] extraction (technical) update

On 9/4/2018 4:27 PM, melanie witt wrote: Yes, we should definitely trim the placement DB migrations to only things relevant to placement. And we can use this opportunity to get rid of cruft too and squash all of the placement migrations together to start at migration 1 for the placement repo.

Re: [openstack-dev] [tricircle] Tricircle or Trio2o

HI ! we have made the tri020 work with the master version openstack as the below pr。 https://review.openstack.org/#/c/596258/ in our plan in the next step we will make tri020 work with the tricircle。see below plan. https://etherpad.openstack.org/p/tricircle-stein-plan At

[openstack-dev] [Neutron][SONA][networking-onos] Releasing stable/rocky branch for networking-onos

Hello, all stable/rocky branch for networking-onos project (https://github.com/openstack/networking-onos ) has been released. If you want to test it, please follow all-in-one install instruction,

[openstack-dev] check-requirements and you

With the move to per-project requirements (aka divergent requirements) we started allowing projects to have differing exclusions and minimums. As long as projects still tested against upper-constraints we were good. Part of the reason why we use upper-constraints is to ensure that project A and

Re: [openstack-dev] non-candidacy for TC

On 2018-09-04 19:46:30 -0400 (-0400), Paul Belanger wrote: > After a year on the TC, I've decided not to run for another term. [...] Thank you for your service (past and future)! -- Jeremy Stanley signature.asc Description: PGP signature

[openstack-dev] [election] [tc] thank you

After 2 years at the TC, I feel lucky enough to have been part of this group where I hope that my modest contributions helped to make OpenStack a bit better. I've learnt so many things and worked with a talented group where it's not easy every day, but we have made and will continue to progress in

Re: [openstack-dev] [goals][upgrade-checkers] Week R-31 update

Would it be helpful to factor some of the common code out into an Oslo library so projects basically just have to subclass, implement check functions, and add them to the _upgrade_checks dict? It's not a huge amount of code, but a bunch of it seems like it would need to be copy-pasted into

[openstack-dev] non-candidacy for TC

Greetings, After a year on the TC, I've decided not to run for another term. I'd like to thank the other TC members for helping bring me up to speed over the last year and community for originally voting. There is always work to do, and I'd like to use this email to encourage everybody to

Re: [openstack-dev] [goals][upgrade-checkers] Week R-31 update

Excerpts from Ben Nemec's message of 2018-09-04 18:39:35 -0500: > Would it be helpful to factor some of the common code out into an Oslo > library so projects basically just have to subclass, implement check > functions, and add them to the _upgrade_checks dict? It's not a huge > amount of

Re: [openstack-dev] non-candidacy for TC

Excerpts from Paul Belanger's message of 2018-09-04 19:46:30 -0400: > Greetings, > > After a year on the TC, I've decided not to run for another term. I'd > like to thank the other TC members for helping bring me up to speed over > the last year and community for originally voting. There is

Re: [openstack-dev] non-candidacy for TC

Thanks for all your contributions while on the TC Paul! Amy (spotz) On Tue, Sep 4, 2018 at 4:46 PM, Paul Belanger wrote: > Greetings, > > After a year on the TC, I've decided not to run for another term. I'd > like to thank the other TC members for helping bring me up to speed over > the last

Re: [openstack-dev] [nova] No weekly meeting on Thursday September 13

On 9/4/2018 4:13 PM, melanie witt wrote: The next meeting will be on Thursday September 20 at 1400 UTC [1]. I'm assuming we're going to have a meeting *this* week though, right? -- Thanks, Matt __ OpenStack Development

Re: [openstack-dev] Dose anyone have use Vitrage to build a mature project for RCA or any other purpose?

Thanks for your reply!So how do you analyse the RCA?Do you ever use any statistics methods like time series or mathine learning methods?Or just use the method that Vitrage provides? zhangwenqing >Date: Tue, 4 Sep 2018 12:29:43 +0300 >From: Ifat Afek >To: "OpenStack Development Mailing

[openstack-dev] [chef] State of the Kitchen: 7th Edition

HTML: https://samuel.cassi.ba/state-of-the-kitchen-7th-edition This is the seventh installment of what is going on with Chef OpenStack. The goal is to give a quick overview to see our progress and what is on the menu. Feedback is always welcome on the content and of what you would like to see

[openstack-dev] [oslo] PTG Schedule

Hi, I've added some tentative times to the planning etherpad[1]. This is all subject to change but I wanted to get something out there for people to look at. If you have other project responsibilities that day please let me know if anything conflicts. As you can see we have a fair amount of

Re: [openstack-dev] [election][tc] announcing candidacy

That is an excellent question John! The most specific thing that is weighing on my mind is elevating and supporting contributors. While this is not new, I think we as a community need to refocus on it because they are very fibers that make up the fabric of our community and ultimately the

Re: [openstack-dev] [Neutron] Tungsten Fabric (formally OpenContrail) at Denver PTG

Folks, This is a reminder of this event at OpenStack PTG in Denver. If you have not already RSVP'd please use the link below to do so. Couple of changes - this event is from 9-5 (not 9-6), and lunch is from 12:30-1:30pm (not 1:00-2:00). Look forward to seeing you there. regards -Sukhdev On

Re: [openstack-dev] [goals][upgrade-checkers] Week R-31 update

On 9/4/2018 6:39 PM, Ben Nemec wrote: Would it be helpful to factor some of the common code out into an Oslo library so projects basically just have to subclass, implement check functions, and add them to the _upgrade_checks dict? It's not a huge amount of code, but a bunch of it seems like it

Re: [openstack-dev] [nova] [placement] extraction (technical) update

On Tue, 4 Sep 2018 16:16:31 -0500, Eric Fried wrote: 030 is okay as long as nothing goes wrong. If something does it raises exceptions which would currently fail as the exceptions are not there. See below for more about exceptions. Maybe I'm misunderstanding what these migration thingies are

Re: [openstack-dev] [nova] [placement] extraction (technical) update

On Tue, 4 Sep 2018, Eric Fried wrote: 030 is okay as long as nothing goes wrong. If something does it raises exceptions which would currently fail as the exceptions are not there. See below for more about exceptions. Maybe I'm misunderstanding what these migration thingies are supposed to be

Re: [openstack-dev] [election][tc] announcing candidacy

On 4 Sep 2018, at 12:16, Julia Kreger wrote: Greetings Stackers! I hereby announce my candidacy for a position on the OpenStack Technical Committee. In many respects I consider myself a maverick, except reality is sometimes entirely different than my own self perception, upon

[openstack-dev] Run for a seat on the TC (I am, and you can too!)

I'm standing for reelection to a third term on the OpenStack Technical Committee. Rather than the usual platform where I drone on and on about myself, I'm going to take this opportunity to run a public service announcement instead. Going into my second term I stated, "my personal vision for

[openstack-dev] [nova] No weekly meeting on Thursday September 13

Hi everyone, This is just a reminder we won't have a weekly Nova meeting on Thursday September 13 because of PTG week. The next meeting will be on Thursday September 20 at 1400 UTC [1]. Cheers, -melanie [1] https://wiki.openstack.org/wiki/Meetings/Nova

Re: [openstack-dev] [nova] [placement] extraction (technical) update

> 030 is okay as long as nothing goes wrong. If something does it > raises exceptions which would currently fail as the exceptions are > not there. See below for more about exceptions. Maybe I'm misunderstanding what these migration thingies are supposed to be doing, but 030 [1] seems like it's

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

Hi all, I'd like to submit my candidacy to be a member of the OpenStack Technical Committee. My involvement with OpenStack began during the Diablo release. Since then I've participated in various parts of the community, in both upstream and downstream roles. Today I mainly focus on

Re: [openstack-dev] [goals][python3] week 4 update

> > +-+--+---+-++ > | Team| Open | Total | Status > | Champion | >

[openstack-dev] [tc] [all] TC Report 18-36

HTML: https://anticdent.org/tc-report-18-36.html It's been a rather busy day, so this TC Report will be a quick update of some discussions that have happened in the past week. # PEP 8002 With Guido van Rossum stepping back from his role as the BDFL of Python, there's work in progress to

[openstack-dev] [goals][upgrade-checkers] Week R-31 update

Just a few updates this week. 1. The story is now populated with a task per project that may have something to complete for this goal [1]. PTLs, or their liaison(s), should assign the task for their project to whomever is going to work on the goal. The goal document in governance is being

Re: [openstack-dev] check-requirements and you

On 18-09-05 07:04:12, Andreas Jaeger wrote: > On 2018-09-05 05:20, Matthew Thode wrote: > > With the move to per-project requirements (aka divergent requirements) > > we started allowing projects to have differing exclusions and minimums. > > As long as projects still tested against

[openstack-dev] [Neutron] [Cyborg] Cyborg-Neutron interaction for programmable NICs

Hello Neutron folks, There is emerging interest in programmable NICs that combine FPGAs and networking in different ways. I wrote up about one category of them here: https://etherpad.openstack.org/p/fpga-networking This was discussed at the Neutron meeting on Sep 3 [1]. This approach

[openstack-dev] [tripleo] VFs not configured in SR-IOV role

Hi, Attached is the used to deploy an overcloud with SR-IOV role. The deployment completed successfully but the VFs aren't configured on the host. Can anyone have a look at what I missed. Thanks Samuel <> __ OpenStack

[openstack-dev] [heat] Heat PTG

Dear all As PTG is near. It's time to settle down the PTG format for Heat. Here is the *PTG etherpad*: https://etherpad.openstack.org/p/2018-Denver-PTG-Heat This time we will run with *physical + online for all sessions*. The online link for sessions will post on etherpad before the session

Re: [openstack-dev] [goals][python3][adjutant][barbican][chef][cinder][cloudkitty][i18n][infra][loci][nova][charms][rpm][puppet][qa][telemetry][trove] join the bandwagon!

Excerpts from Ade Lee's message of 2018-09-04 08:21:51 -0400: > Barbican is ready. > > Thanks, > Ade Here you go: +---+---+-+---+ | Subject

Re: [openstack-dev] better name for placement

Excerpts from Jay Pipes's message of 2018-09-04 12:08:41 -0400: > On 09/04/2018 11:44 AM, Doug Hellmann wrote: > > Excerpts from Chris Dent's message of 2018-09-04 15:32:12 +0100: > >> On Tue, 4 Sep 2018, Jay Pipes wrote: > >> > >>> Is there a reason we couldn't have openstack-placement be the

Re: [openstack-dev] better name for placement

On Tue, 4 Sep 2018, Jay Pipes wrote: Is there a reason we couldn't have openstack-placement be the package name? I would hope we'd be able to do that, and probably should do that. 'openstack-placement' seems a find pypi package name for a think from which you do 'import placement' to do some

Re: [openstack-dev] [goals][python3][adjutant][barbican][chef][cinder][cloudkitty][i18n][infra][loci][nova][charms][rpm][puppet][qa][telemetry][trove] join the bandwagon!

All changes on cloudkitty projects have been merged, so we're ready for https://review.openstack.org/#/c/598929. Thank you again! -- Luka Peschke Développeur +33 (0) 5 82 95 65 36 5 rue du Moulin Bayard - 31000 Toulouse www.objectif-libre.com Le 2018-08-31 15:04, Doug Hellmann a écrit :

Re: [openstack-dev] better name for placement (was:Nominating Chris Dent for placement-core)

On 2018-09-04 09:32:20 +0100 (+0100), Chris Dent wrote: [...] > it allowed for the possibility that there could be another project > which provided the same service-type. That hasn't really come to > pass [...] It still might make sense to attempt to look at this issue from outside the limited

Re: [openstack-dev] [tripleo] using multiple roles

On Tue, Sep 4, 2018 at 8:15 AM, Samuel Monderer wrote: > Is it possible to have the roles_data.yaml file generated when running > "openstack overcloud deploy"?? > Not at this time. That is something we'd like to get to, but is not currently prioritized. Thanks, -Alex > On Tue, Sep 4, 2018 at

[openstack-dev] [publiccloud-wg] Meeting tomorrow for Public Cloud WG

Hi folks, Time for a new meeting for the Public Cloud WG. Agenda draft can be found at https://etherpad.openstack.org/p/publiccloud-wg, feel free to add items to that list. See you all tomorrow at 0700 UTC - IRC channel #openstack-publiccloud Cheers, Tobias -- Tobias Rydberg Senior

Re: [openstack-dev] better name for placement

On 2018-09-04 11:44:41 -0400 (-0400), Doug Hellmann wrote: > Excerpts from Chris Dent's message of 2018-09-04 15:32:12 +0100: [...] > > I would hope we'd be able to do that, and probably should do that. > > 'openstack-placement' seems a find pypi package name for a think > > from which you do

Re: [openstack-dev] [tripleo] using multiple roles

On Tue, Sep 4, 2018 at 2:31 AM, Samuel Monderer wrote: > Hi, > > Due to many different HW in our environment we have multiple roles. > I would like to place each role definition if a different file. > Is it possible to refer to all the roles from roles_data.yaml to all the > different files

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

On Tue, Sep 4, 2018 at 3:04 PM, Ifat Afek wrote: Hi, Vitrage also uses the Nova legacy notifications. Unfortunately I will not attend the PTG, but I added the relevant information in the etherpad. Thanks for the pad update. Cheers, gibi Thanks, Ifat On Tue, Aug 28, 2018 at 5:31 PM

Re: [openstack-dev] better name for placement

Excerpts from Jay Pipes's message of 2018-09-04 10:05:28 -0400: > On 09/04/2018 09:37 AM, Jeremy Stanley wrote: > > On 2018-09-04 09:32:20 +0100 (+0100), Chris Dent wrote: > > [...] > >> it allowed for the possibility that there could be another project > >> which provided the same service-type.

Re: [openstack-dev] better name for placement

On 09/04/2018 09:37 AM, Jeremy Stanley wrote: On 2018-09-04 09:32:20 +0100 (+0100), Chris Dent wrote: [...] it allowed for the possibility that there could be another project which provided the same service-type. That hasn't really come to pass [...] It still might make sense to attempt to

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

Hi, Vitrage also uses the Nova legacy notifications. Unfortunately I will not attend the PTG, but I added the relevant information in the etherpad. Thanks, Ifat On Tue, Aug 28, 2018 at 5:31 PM Balázs Gibizer wrote: > Thanks for all the responses. I collected them on the nova ptg > discussion

Re: [openstack-dev] better name for placement

On 09/04/2018 11:44 AM, Doug Hellmann wrote: Excerpts from Chris Dent's message of 2018-09-04 15:32:12 +0100: On Tue, 4 Sep 2018, Jay Pipes wrote: Is there a reason we couldn't have openstack-placement be the package name? I would hope we'd be able to do that, and probably should do that.

[openstack-dev] [tempest][CI][nova compute] Skipping non-compute-driver tests

Folks- The other day, I posted an experimental patch [1] with an effectively empty ComputeDriver (just enough to make n-cpu actually start) to see how much of our CI would pass. The theory being that any tests that still pass are tests that don't touch our compute driver, and are

Re: [openstack-dev] better name for placement

Excerpts from Chris Dent's message of 2018-09-04 15:32:12 +0100: > On Tue, 4 Sep 2018, Jay Pipes wrote: > > > Is there a reason we couldn't have openstack-placement be the package name? > > I would hope we'd be able to do that, and probably should do that. > 'openstack-placement' seems a find

Re: [openstack-dev] better name for placement

On 09/04/2018 12:17 PM, Doug Hellmann wrote: Excerpts from Jay Pipes's message of 2018-09-04 12:08:41 -0400: On 09/04/2018 11:44 AM, Doug Hellmann wrote: Excerpts from Chris Dent's message of 2018-09-04 15:32:12 +0100: On Tue, 4 Sep 2018, Jay Pipes wrote: Is there a reason we couldn't have

Re: [openstack-dev] [goals][python3][adjutant][barbican][chef][cinder][cloudkitty][i18n][infra][loci][nova][charms][rpm][puppet][qa][telemetry][trove] join the bandwagon!

Barbican is ready. Thanks, Ade On Thu, 2018-08-30 at 19:24 -0400, Doug Hellmann wrote: > Below is the list of project teams that have not yet started > migrating > their zuul configuration. If you're ready to go, please respond to > this > email to let us know so we can start proposing patches.

[openstack-dev] [election][tc] announcing candidacy

I am announcing my candidacy for a position on the OpenStack Technical Committee. I started contributing to OpenStack in 2012, not long after joining Dreamhost, and I am currently employed by Red Hat to work on OpenStack with a focus on long-term project concerns. I have served on the Technical

Re: [openstack-dev] check-requirements and you

On 2018-09-05 05:20, Matthew Thode wrote: With the move to per-project requirements (aka divergent requirements) we started allowing projects to have differing exclusions and minimums. As long as projects still tested against upper-constraints we were good. Part of the reason why we use

Re: [openstack-dev] [api] Open API 3.0 for OpenStack API

Hi, On 08/29/2018 08:36 AM, Edison Xiang wrote: Hi team, As we know, Open API 3.0 was released on July, 2017, it is about one year ago. Open API 3.0 support some new features like anyof, oneof and allof than Open API 2.0(Swagger 2.0). Now OpenStack projects do not support Open API. Also I

[openstack-dev] [TC][Searchlight] Searchlight project missing from the OpenStack website

Dear TC, I'm not sure if I missed something but Searchlight is not listed in the Software section of the OpenStack website [1]. Is it because Searchlight has missed the Rocky cycle? Bests, [1] https://www.openstack.org/software/project-navigator/openstack-components#operations-services *Trinh

[openstack-dev] [ptg] ptgbot HOWTO

Hi everyone, In a few days some of us will meet in Denver for the 4th OpenStack PTG. The event is made of several 'tracks' (organized around a specific team/group or a specific theme). Topics of discussions are loosely scheduled in those tracks, based on the needs of the attendance. This

Re: [openstack-dev] better name for placement (was:Nominating Chris Dent for placement-core)

On Tue, 4 Sep 2018, Thomas Goirand wrote: Just a nit-pick... It's a shame we call it just placement. It could have been something like: foo: OpenStack placement Just like we have: nova: OpenStack compute No? Is it too late? There was some discussion about this on one of the

[openstack-dev] [tripleo] using multiple roles

Hi, Due to many different HW in our environment we have multiple roles. I would like to place each role definition if a different file. Is it possible to refer to all the roles from roles_data.yaml to all the different files instead of having a long roles_data.yaml file? Regards, Samuel

[openstack-dev] [Tripleo] Automating role generation

Hi I am looking to automate role file generation in TripleO. The idea is basically for an operator to create a simple yaml file (operator.yaml, say) listing services that are needed and then TripleO to generate Controller.yaml enabling only those services that are mentioned. For example:

Re: [openstack-dev] better name for placement (was:Nominating Chris Dent for placement-core)

On 08/31/2018 05:45 PM, Eric Fried wrote: > The openstack/placement project [1] and its core team [2] have been > established in gerrit. > > I hereby nominate Chris Dent for membership in the placement-core team. > He has been instrumental in the design, implementation, and stewardship > of the

Re: [openstack-dev] Nominating Chris Dent for placement-core

+1 Eric Fried 于2018年8月31日周五 下午11:45写道： > The openstack/placement project [1] and its core team [2] have been > established in gerrit. > > I hereby nominate Chris Dent for membership in the placement-core team. > He has been instrumental in the design, implementation, and stewardship > of the

Re: [openstack-dev] [Tripleo] Automating role generation

On 4.9.2018 08:13, Janki Chhatbar wrote: Hi I am looking to automate role file generation in TripleO. The idea is basically for an operator to create a simple yaml file (operator.yaml, say) listing services that are needed and then TripleO to generate Controller.yaml enabling only those

[openstack-dev] [nova]Notification subteam meeting cancelled

Hi, This week's and next week's notification subteam meeting has been cancelled. See you in Denver. Cheers, gibi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [Tripleo] Automating role generation

On Tue, Sep 4, 2018 at 9:48 AM, Jiří Stránský wrote: > On 4.9.2018 08:13, Janki Chhatbar wrote: >> >> Hi >> >> I am looking to automate role file generation in TripleO. The idea is >> basically for an operator to create a simple yaml file (operator.yaml, >> say) >> listing services that are

[openstack-dev] Dose anyone have use Vitrage to build a mature project for RCA or any other purpose?

I want to use Vitrage for my AIOps project, but i can't get any relative information, and I think this is not a mature project.Does anyone have relative experience?Would you please give me some advice?__ OpenStack

Re: [openstack-dev] Dose anyone have use Vitrage to build a mature project for RCA or any other purpose?

On Tue, Sep 4, 2018 at 11:41 AM zhangwenqing <18800173...@163.com> wrote: > I want to use Vitrage for my AIOps project, but i can't get any relative > information, and I think this is not a mature project.Does anyone have > relative experience?Would you please give me some advice? > Hi, Vitrage

Re: [openstack-dev] [tripleo] quickstart for humans

Hi On 08/30/2018 04:28 PM, Honza Pokorny wrote: > Hello! > > Over the last few months, it seems that tripleo-quickstart has evolved > into a CI tool. It's primarily used by computers, and not humans. > tripleo-quickstart is a helpful set of ansible playbooks, and a > collection of feature sets.