Re: [openstack-dev] [heat][mistral][deployment] how to add deployment roles

Hi, Just a small addition. “mistral action-update” applies only to so-called ad-hoc actions which are essentially wrappers written in YAML. You can’t update a regular action written in Python and plugged in Mistral with stevedore using this command. Renat Akhmerov @Nokia On 28 Jun 2017,

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

On Wed, Jun 28, 2017 at 6:59 AM, Jeremy Stanley wrote: > On 2017-06-17 01:20:28 +1000 (+1000), Joshua Hesketh wrote: > [...] > > I'm happy to help do this if you'd like. Otherwise the script I've > > used for the last few retirements is here: > >

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

On Tue, Jun 27, 2017 at 08:59:27PM +, Jeremy Stanley wrote: > Fingers crossed that we'll be able to switch to Gerrit 2.13 soon and > resume that much needed development effort. This looks to have landed in 2.14[1] :( I don't know how hard it'd be to backport to 2.13 or even if that's a

Re: [openstack-dev] [kolla][kolla-ansible] Proposing Surya (spsurya) for core

+1 >> -Original Message- >> From: Michał Jastrzębski [mailto:inc...@gmail.com] >> Sent: Wednesday, June 14, 2017 10:46 PM >> To: OpenStack Development Mailing List (not for usage questions) >> >> Subject: [openstack-dev] [kolla][kolla-ansible]

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

Hello, Silvia, Thank you for your interest in Tricircle and Trio2o. See inline comments. Best Regards Chaoyi Huang (joehuang) From: Silvia Fichera [fichera@gmail.com] Sent: 28 June 2017 5:16 To: OpenStack Development Mailing List (not for usage questions);

Re: [openstack-dev]   [watcher] Nominate Yumeng Bao to the core    team

+1 李灿伟 licanwei__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [kolla][kolla-ansible] Proposing Surya (spsurya) for core

+1 >> -Original Message- >> From: Michał Jastrzębski [mailto:inc...@gmail.com] >> Sent: Wednesday, June 14, 2017 10:46 PM >> To: OpenStack Development Mailing List (not for usage questions) >> >> Subject: [openstack-dev] [kolla][kolla-ansible]

Re: [openstack-dev] [heat][mistral][deployment] how to add deployment roles

HI, Steve - > I think perhaps the confusion is because this was implemented in > tripleoclient, and porting it to tripleo-common is not yet completed? > (Alex can confirm the status of this but it was planned I think). > > Related ML discussion which includes links to the patches: > >

[openstack-dev] [keystone] removing domain configuration upload via keystone-manage

Hi all, Keystone has deprecated the domain configuration upload capability provided through `keystone-manage`. We discussed it's removal in today's meeting [0] and wanted to send a quick note to the operator list. The ability to upload a domain config into keystone was done as a stop-gap until

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

Hi Graham, As ever, many thanks for clarifying that. And I shall put in a feature request as you suggest. In the meantime, presumably the missing pieces that I need are those described in: https://docs.openstack.org/ocata/networking-guide/config-dns-int.html under 'Configuring

Re: [openstack-dev] [docs][all][ptl] Contributor Portal and Better New Contributor On-boarding

On 22:18 Jun 27, Jeremy Stanley wrote: > On 2017-06-27 14:34:46 -0700 (-0700), Mike Perez wrote: > [...] > > ## PTG > > > > New contributors should be participating in the sessions for a > > project and get to know who are the people leading those efforts. > > People leading efforts want help.

Re: [openstack-dev] [docs][all][ptl] Contributor Portal and Better New Contributor On-boarding

On 00:07 Jun 28, Ildiko Vancsa wrote: > > On 2017. Jun 27., at 23:34, Mike Perez wrote: > > > > On 13:52 Jun 23, Michał Jastrzębski wrote: > >> Great idea! > >> > >> I would also throw another issue new people often have (I had it too). > >> Namely what to contribute.

Re: [openstack-dev] [tripleo] OpenStack manuals project migration - Progress for TripleO

I would like to help with some part. Dong 2017-06-28 4:54 GMT+08:00 Emilien Macchi : > Full background, context and details can be read here: > http://specs.openstack.org/openstack/docs-specs/specs/ > pike/os-manuals-migration.html > > TL;DR: there is a massive cross-project

Re: [openstack-dev] [docs][all][ptl] Contributor Portal and Better New Contributor On-boarding

On 2017-06-27 14:34:46 -0700 (-0700), Mike Perez wrote: [...] > ## PTG > > New contributors should be participating in the sessions for a > project and get to know who are the people leading those efforts. > People leading efforts want help. Whether it be documentation for > the thing,

Re: [openstack-dev] [docs][all][ptl] Contributor Portal and Better New Contributor On-boarding

Storyboard can definitely help with this! Each task in a story has an owner and a project while the larger story's description could list who is in charge of the larger implementation overall. On Tue, Jun 27, 2017 at 4:34 PM Mike Perez wrote: > On 13:52 Jun 23, Michał

Re: [openstack-dev] [docs][all][ptl] Contributor Portal and Better New Contributor On-boarding

On 13:52 Jun 23, Michał Jastrzębski wrote: > Great idea! > > I would also throw another issue new people often have (I had it too). > Namely what to contribute. Lot's of people wants to do something but > not quite know where to start. > So few ideas for start: > * List of triaged bugs > * List

Re: [openstack-dev] [docs][all][ptl] Contributor Portal and Better New Contributor On-boarding

On 09:45 Jun 26, Alexandra Settle wrote: > I think this is a good idea :) thanks Mike. We get a lot of people coming to > the docs chan or ML asking for help/where to start and sometimes it’s > difficult to point them in the right direction. > > Just from experience working with contributor

[openstack-dev] [tricircle] Tricircle vs Trio2o

Hi all, I would like to build up a multi-region openstack and I read that both tricircle and trio2o are the most suitable solutions. I have few questions: - from the wikis I couldn't deeply understand the differences between the two: ad far as I understood tricircle deploys a shared neutron

Re: [openstack-dev] [all][tc] Turning TC/UC workgroups into OpenStack SIGs

On Wed, Jun 21, 2017 at 8:59 AM, Thierry Carrez wrote: > Hi everyone, > > One of the areas identified as a priority by the Board + TC + UC > workshop in March was the need to better close the feedback loop and > make unanswered requirements emerge. Part of the solution is

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

On 2017-06-17 01:20:28 +1000 (+1000), Joshua Hesketh wrote: [...] > I'm happy to help do this if you'd like. Otherwise the script I've > used for the last few retirements is here: > http://git.openstack.org/cgit/openstack-infra/release-tools/tree/eol_branch.sh That would be really appreciated if

Re: [openstack-dev] [all][tc] Turning TC/UC workgroups into OpenStack SIGs

On 2017-06-27 15:42:05 +0200 (+0200), Thierry Carrez wrote: > Sean Dague wrote: [...] > > I wonder if we're going down this path, if some kind of tooling like > > standard tags for issues/patches should be added to the mix to help gain > > the effectiveness that the k8s team seems to have here. >

[openstack-dev] [tripleo] OpenStack manuals project migration - Progress for TripleO

Full background, context and details can be read here: http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html TL;DR: there is a massive cross-project effort which aims to migrate documentations out of a central repository and into project trees, managed by project

[openstack-dev] EXT: [octavia] scheduling webex to discuss flavor spec (https://review.openstack.org/#/c/392485/)

BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:Central Standard Time BEGIN:STANDARD DTSTART:16010101T02 TZOFFSETFROM:-0500 TZOFFSETTO:-0600 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11 END:STANDARD BEGIN:DAYLIGHT

Re: [openstack-dev] [heat][mistral][deployment] how to add deployment roles

Hi Dan, On Tue, Jun 27, 2017 at 9:19 PM, Dan Trainor wrote: > Hi - > > I'm looking for the glue that populates the overcloud role list. > > I can get a list of roles via 'openstack overcloud role list', however I'm > looking to create new roles to incorporate in to this

[openstack-dev] [heat][mistral][deployment] how to add deployment roles

Hi - I'm looking for the glue that populates the overcloud role list. I can get a list of roles via 'openstack overcloud role list', however I'm looking to create new roles to incorporate in to this list. I got as far as using 'mistral action-update' against what I beleive to be the proper

Re: [openstack-dev] [qa] New upgrade test tool proposal.

On 06/27/2017 03:19 PM, Dean Troyer wrote: > On Tue, Jun 27, 2017 at 1:37 PM, Jay Pipes wrote: >> Hi Castulo, sorry for the delayed response on this. Has your team moved >> forward on any of this? > > IIRC this work was impacted by the OSIC shutdown, I believe it is not >

Re: [openstack-dev] [qa] New upgrade test tool proposal.

On Tue, Jun 27, 2017 at 1:37 PM, Jay Pipes wrote: > Hi Castulo, sorry for the delayed response on this. Has your team moved > forward on any of this? IIRC this work was impacted by the OSIC shutdown, I believe it is not currently on anyone's radar. > What about the Grenade

Re: [openstack-dev] [stable][release] Last release date vs End of Life date

Excerpts from Tony Breeds's message of 2017-06-27 16:51:37 +1000: > Hi all, > Up 'til now we haven't set a last release date for a stable branch > approaching end of life. It seems like formalizing that would be a good > thing. > > This comes up as we need time to verify that said release

Re: [openstack-dev] [qa] New upgrade test tool proposal.

On 04/05/2017 04:22 PM, Martinez, Castulo wrote: Hi, As you might know, the TC introduced new tags [1] for upgrade processes quite some time ago, which reflect the level of maturity of an upgrade. Therefore there is the growing need of test tools which help to exercise and validate the upgrade

Re: [openstack-dev] [docs][all][ptl] Contributor Portal and Better New Contributor On-boarding

Boris Pavlovic wrote: Overall it would take 1-2 days for people not familiar with OpenStack. What about if one make "Sing-Up" page: 1) Few steps: provide Username, Contact info, Agreement, SSH key (and it will do all work for you set Gerrit, OpenStack,...) 2) After one finished form it gets

Re: [openstack-dev] [watcher] Nominate Yumeng Bao to the core team

+1. Keep it up Yumeng!! - Pru From: "Чадин Александр (Alexander Chadin)" Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Tuesday, June 27, 2017 at 6:43 AM To: OpenStack Development Mailing List

Re: [openstack-dev] [tc][all] Move away from meeting channels

On 2017-06-26 15:27:21 +0200 (+0200), Thierry Carrez wrote: > Flavio Percoco wrote: > > [...] > > Not being able to easily ping someone during a meeting is kind > > of a bummer but I'd argue that assuming someone is in the > > meeting channel and available at all times is a mistake to begin > >

Re: [openstack-dev] [ptls][all][tc][docs] Documentation migration spec

Excerpts from Jeremy Stanley's message of 2017-06-27 17:55:57 +: > On 2017-06-22 16:27:34 -0400 (-0400), Doug Hellmann wrote: > [...] > > The new job is configured to update the docs for all repos every > > time a patch is merged, not just when we tag releases. The server > > projects have

Re: [openstack-dev] [docs][all][ptl] Contributor Portal and Better New Contributor On-boarding

On 2017-06-26 10:51:08 -0700 (-0700), Clark Boylan wrote: > On Mon, Jun 26, 2017, at 10:31 AM, Boris Pavlovic wrote: [...] > > - When you try to contribute your first commit (if you already > > created it, you won't be able unit you do git commit --ament, so > > git review will add change-id) > >

Re: [openstack-dev] [ptls][all][tc][docs] Documentation migration spec

On 2017-06-22 16:27:34 -0400 (-0400), Doug Hellmann wrote: [...] > The new job is configured to update the docs for all repos every > time a patch is merged, not just when we tag releases. The server > projects have been working that way, but this is different for some > of the libraries,

Re: [openstack-dev] realtime kvm cpu affinities

On 06/27/2017 09:36 AM, Henning Schild wrote: Am Tue, 27 Jun 2017 09:28:34 -0600 schrieb Chris Friesen : Once you use "isolcpus" on the host, the host scheduler won't "float" threads between the CPUs based on load. To get the float behaviour you'd have to not

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

On 27/06/17 16:36, Lawrence J. Albinson wrote: > Hi Graham, > > Many thanks for the pointer. I hadn't added dns to the plugin list. > > I did, however, set the following: > > neutron_designate_enabled: True Ah - unfortunately there is two ways of integrating Neutron + Designate The

Re: [openstack-dev] [tc][all] Move away from meeting channels

On Mon, Jun 26, 2017 at 9:58 AM, Chris Dent wrote: > On Mon, 26 Jun 2017, Flavio Percoco wrote: > >> So, should we let teams to host IRC meetings in their own channels? > > > Yes. ++ >> Thoughts? > > > I think the silo-ing concern is, at least recently, not relevant on >

[openstack-dev] [Openstack-operators][dev][doc] Operations Guide future

Thanks everyone for your feedback regarding the proposal below. Going forwards we are going to implement Option 3. If anyone is able to help out with this migration, please let me know :) Looking forward to getting started! From: Alexandra Settle Date: Thursday, June 1,

Re: [openstack-dev] [Glare][TC][All] Past, Present and Future of Glare project

On Tue, Jun 27, 2017 at 10:19 AM, Flavio Percoco wrote: > On 26/06/17 17:35 +0300, Mikhail Fedosin wrote: > >> 2. We would like to become an official OpenStack project, and in general >> we >> follow all the necessary rules and recommendations, starting from weekly >> IRC

Re: [openstack-dev] [Glare][TC][All] Past, Present and Future of Glare project

On Tue, Jun 27, 2017 at 3:33 PM, Jay Pipes wrote: > From what I can tell, Keycloak is an Identity provider, not a secret store? > > Yes! I should explain more detailed. CloudBand is a big enterprise system for SDN and OpenStack is a part of it. The default Identity provider

Re: [openstack-dev] realtime kvm cpu affinities

Am Tue, 27 Jun 2017 09:25:14 -0600 schrieb Chris Friesen : > On 06/27/2017 01:44 AM, Sahid Orentino Ferdjaoui wrote: > > On Mon, Jun 26, 2017 at 10:19:12AM +0200, Henning Schild wrote: > >> Am Sun, 25 Jun 2017 10:09:10 +0200 > >> schrieb Sahid Orentino Ferdjaoui

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

Hi Graham, Many thanks for the pointer. I hadn't added dns to the plugin list. I did, however, set the following: neutron_designate_enabled: True I'm wondering if the two together will fix things. I shall know by the morning. Again, many thanks. Kind regards, Lawrence

Re: [openstack-dev] realtime kvm cpu affinities

Am Tue, 27 Jun 2017 09:28:34 -0600 schrieb Chris Friesen : > On 06/27/2017 01:45 AM, Sahid Orentino Ferdjaoui wrote: > > On Mon, Jun 26, 2017 at 12:12:49PM -0600, Chris Friesen wrote: > >> On 06/25/2017 02:09 AM, Sahid Orentino Ferdjaoui wrote: > >>> On Fri, Jun

Re: [openstack-dev] [tc][fuel] Making Fuel a hosted project

On Wed, Jun 21, 2017 at 4:34 PM, Vladimir Kuklin wrote: > Folks, I sent a reply a couple of days ago, but somehow it got lost. The > original message goes below > > Folks > > It is essentially true that Fuel is no longer being developed as almost 99% > of people have left

Re: [openstack-dev] realtime kvm cpu affinities

On 06/27/2017 01:45 AM, Sahid Orentino Ferdjaoui wrote: On Mon, Jun 26, 2017 at 12:12:49PM -0600, Chris Friesen wrote: On 06/25/2017 02:09 AM, Sahid Orentino Ferdjaoui wrote: On Fri, Jun 23, 2017 at 10:34:26AM -0600, Chris Friesen wrote: On 06/23/2017 09:35 AM, Henning Schild wrote: Am Fri,

Re: [openstack-dev] realtime kvm cpu affinities

On 06/27/2017 01:44 AM, Sahid Orentino Ferdjaoui wrote: On Mon, Jun 26, 2017 at 10:19:12AM +0200, Henning Schild wrote: Am Sun, 25 Jun 2017 10:09:10 +0200 schrieb Sahid Orentino Ferdjaoui : On Fri, Jun 23, 2017 at 10:34:26AM -0600, Chris Friesen wrote: On 06/23/2017

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

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

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 and/or the designate client and see Bind9 reflect those

Re: [openstack-dev] realtime kvm cpu affinities

Am Tue, 27 Jun 2017 09:44:22 +0200 schrieb Sahid Orentino Ferdjaoui : > On Mon, Jun 26, 2017 at 10:19:12AM +0200, Henning Schild wrote: > > Am Sun, 25 Jun 2017 10:09:10 +0200 > > schrieb Sahid Orentino Ferdjaoui : > > > > > On Fri, Jun 23, 2017 at

[openstack-dev] [hacking] Propose removal of cores

I am proposing that the following people be removed as core reviewers from the hacking project: https://review.openstack.org/#/admin/groups/153,members Joe Gordon James Carey Joe Gordon: Has not done a review in OpenStack since 16-Feb-2017 http://stackalytics.com/?release=all_id=jogo Has not

Re: [openstack-dev] [all][tc] Turning TC/UC workgroups into OpenStack SIGs

On 06/27/2017 09:42 AM, Thierry Carrez wrote: > Sean Dague wrote: >> I also think it's fine to rebrand WG to SIG, but we should also be >> honest that it's mostly a rebrand to consolidate on terminology that k8s >> and cncf have used that people find easier to understand so it's a way >> in which

Re: [openstack-dev] [User-committee] [all][tc] Turning TC/UC workgroups into OpenStack SIGs

Blair Bethwaite wrote: > There is a not insignificant degree of irony in the fact that this > conversation has splintered so that anyone only reading > openstack-operators and/or user-committee is missing 90% of the > picture Maybe I just need a new ML management strategy. That irony is not

[openstack-dev] [watcher] Nominate Yumeng Bao to the core team

Hi watcher folks, I’d like to nominate Yumeng Bao to the core team. She has made a lot of contributions including specifications, features and bug fixes. Yumeng has attended PTG and Summit with her presentation related to the Watcher. Yumeng is active on IRC channels and take a part on weekly

Re: [openstack-dev] [all][tc] Turning TC/UC workgroups into OpenStack SIGs

Sean Dague wrote: > On 06/21/2017 01:10 PM, Michał Jastrzębski wrote: >> One of key components which, imho, made SIGs successful in k8s is >> infrastructure behind it. >> >> When someone proposes an issue, they can tag SIG to it. Everyone in >> this SIG will be notified that there is an issue they

[openstack-dev] Fwd: [scientific] IRC Meeting (Tues 2100 UTC): Science app catalogues, network security of research computing on OpenStack

Resend for openstack-dev with proper list perms... -- Forwarded message -- From: Blair Bethwaite Date: 27 June 2017 at 23:24 Subject: [scientific] IRC Meeting (Tues 2100 UTC): Science app catalogues, network security of research computing on OpenStack

[openstack-dev] [ceilometer] deprecating pollster-list option

hi, i'm proposing to deprecate/remove pollster-list config option. if you're like me and wondering what this is, we apparently support ability to filter pollsters loaded by polling agent[1]. the reason i'd like to deprecate is because we already have this functionality in the

Re: [openstack-dev] [oslo][oslo-service] Multi main processes are started by using oslo_service

On 27/06/17 05:56 AM, zhi wrote: > Everything goes well when the "api_workers " equals 0 or 1. But two main > processes were started when the " api_workers " equals 2. The log shows > below: > > 2017-06-27 17:42:18.864 1958058 INFO abc.common.wsgi [-] (1958058) wsgi > starting up on

Re: [openstack-dev] [User-committee] [all][tc] Turning TC/UC workgroups into OpenStack SIGs

There is a not insignificant degree of irony in the fact that this conversation has splintered so that anyone only reading openstack-operators and/or user-committee is missing 90% of the picture Maybe I just need a new ML management strategy. I'd like to add a +1 to Sean's suggestion about

Re: [openstack-dev] [Glare][TC][All] Past, Present and Future of Glare project

From what I can tell, Keycloak is an Identity provider, not a secret store? -jay On 06/27/2017 05:35 AM, Adam Heczko wrote: Barbican already supports multiple secret storage backends [1] and most likely adding Keycloak's one [2] should be possible. [1]

Re: [openstack-dev] [QA][ALL] What tempest tests will go under tempest plugin for a Project?

++ openstack-dev On Tue, Jun 27, 2017 at 3:57 PM, Ghanshyam Mann wrote: > On Tue, Jun 27, 2017 at 3:52 PM, Chandan kumar wrote: >> Hello Ghanshyam, >> >> On Sat, Jun 24, 2017 at 3:48 PM, Ghanshyam Mann >> wrote: >>> On

Re: [openstack-dev] [all][tc] Turning TC/UC workgroups into OpenStack SIGs

On 06/21/2017 01:10 PM, Michał Jastrzębski wrote: > One of key components which, imho, made SIGs successful in k8s is > infrastructure behind it. > > When someone proposes an issue, they can tag SIG to it. Everyone in > this SIG will be notified that there is an issue they might be > interested

Re: [openstack-dev] [tc][all][ptl] Most Supported Queens Goals and Improving Goal Completion

On 06/27/2017 04:50 AM, Thierry Carrez wrote: > gordon chung wrote: >> do we know why they're not being completed? indifference? lack of resources? > > I would say it's a mix of reasons. Sometimes it's a resource issue, but > most of the time it's a prioritization issue (everyone waiting for >

Re: [openstack-dev] [all][qa][glance] some recent tempest problems

On Mon, Jun 26, 2017 at 11:58 PM, Eric Harney wrote: > On 06/19/2017 09:22 AM, Matt Riedemann wrote: >> On 6/16/2017 8:58 AM, Eric Harney wrote: >>> I'm not convinced yet that this failure is purely Ceph-specific, at a >>> quick look. >>> >>> I think what happens here is,

[openstack-dev] [oslo][oslo-service] Multi main processes are started by using oslo_service

Hi, all. Here, I want to start a main process and multi subprocess by using oslo_service. So I launch a service like this: from oslo_service import service as common_service def serve_wsgi(cls): try: service = cls.create() except Exception:

Re: [openstack-dev] [Glare][TC][All] Past, Present and Future of Glare project

Barbican already supports multiple secret storage backends [1] and most likely adding Keycloak's one [2] should be possible. [1] https://docs.openstack.org/project-install-guide/key-manager/draft/barbican-backend.html [2] https://github.com/jpkrohling/secret-store On Tue, Jun 27, 2017 at 10:42

[openstack-dev] [tricircle]weekly meeting of Jun.28

Hello, team, Agenda of Jun.28 weekly meeting: 1. feature implementation review 2. Community wide goals, PTG and Sydney summit topics 3. Open Discussion How to join: # IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every Wednesday starting from UTC 1:00.

Re: [openstack-dev] [tc][all][ptl] Most Supported Queens Goals and Improving Goal Completion

gordon chung wrote: > do we know why they're not being completed? indifference? lack of resources? I would say it's a mix of reasons. Sometimes it's a resource issue, but most of the time it's a prioritization issue (everyone waiting for someone else to pick it up), and in remaining cases it's

Re: [openstack-dev] [Glare][TC][All] Past, Present and Future of Glare project

Mikhail Fedosin wrote: > Does the above mean you are implementing a share secret storage > solution or that you are going to use an existing solution like > Barbican that does that? > > Sectets is a plugin for Glare we developed for Nokia CloudBand >

[openstack-dev] [os-upstream-institute] Meeting on the top of the hour

Hi Training Team, It is a friendly reminder that we’re having our Europe and Asia TZ friendly meeting slot at 0900 UTC today, on #openstack-meeting-3. You can find the meeting agenda here: https://etherpad.openstack.org/p/openstack-upstream-institute-meetings Thanks, Ildikó (IRC: ildikov)

Re: [openstack-dev] realtime kvm cpu affinities

On Mon, Jun 26, 2017 at 12:12:49PM -0600, Chris Friesen wrote: > On 06/25/2017 02:09 AM, Sahid Orentino Ferdjaoui wrote: > > On Fri, Jun 23, 2017 at 10:34:26AM -0600, Chris Friesen wrote: > > > On 06/23/2017 09:35 AM, Henning Schild wrote: > > > > Am Fri, 23 Jun 2017 11:11:10 +0200 > > > > schrieb

Re: [openstack-dev] realtime kvm cpu affinities

On Mon, Jun 26, 2017 at 10:19:12AM +0200, Henning Schild wrote: > Am Sun, 25 Jun 2017 10:09:10 +0200 > schrieb Sahid Orentino Ferdjaoui : > > > On Fri, Jun 23, 2017 at 10:34:26AM -0600, Chris Friesen wrote: > > > On 06/23/2017 09:35 AM, Henning Schild wrote: > > > > Am Fri,

Re: [openstack-dev] [Glare][TC][All] Past, Present and Future of Glare project

On 26/06/17 17:35 +0300, Mikhail Fedosin wrote: 2. We would like to become an official OpenStack project, and in general we follow all the necessary rules and recommendations, starting from weekly IRC meetings and our own channel, to Apache license and Keystone support. For this reason, I want

Re: [openstack-dev] [QA][ALL] What tempest tests will go under tempest plugin for a Project?

Hello Ghanshyam, On Sat, Jun 24, 2017 at 3:48 PM, Ghanshyam Mann wrote: > On Fri, Jun 23, 2017 at 4:51 PM, Chandan kumar wrote: >> Hello, >> >> In Queen OpenStack release, We have a community goal to split In-Tree >> tempest plugin to a separate

[openstack-dev] [stable][release] Last release date vs End of Life date

Hi all, Up 'til now we haven't set a last release date for a stable branch approaching end of life. It seems like formalizing that would be a good thing. This comes up as we need time to verify that said release integrates well (at least doesn't break) said branch. So should we define a

Re: [openstack-dev] [octavia] fail to plug vip to amphora

Hi, Micheal, Thanks a lot for your help, but I still have one question. In Octavia, once the controller worker fails plugging VIP to the amphora, the amphora is deleted immediately, making it impossible to trace the error. How to prevent Octavia from stopping and deleting the amphora? Best