Re: [openstack-dev] [Heat] Heat template example repository

On 15.05.17 18:10, Steven Hardy wrote: On Mon, May 15, 2017 at 04:46:28PM +0200, Lance Haig wrote: Hi Steve, I am happy to assist in any way to be honest. The backwards compatibility is not always correct as I have seen when developing our library of templates on Liberty and then trying to

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

On 16/05/17 09:45 -0400, Doug Hellmann wrote: Excerpts from Flavio Percoco's message of 2017-05-15 21:50:23 -0400: On 15/05/17 11:49 -0700, Michał Jastrzębski wrote: >On 15 May 2017 at 11:19, Davanum Srinivas wrote: >> Sorry for the top post, Michal, Can you please clarify a

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

I would like to bring up a subject that hasn't really been discussed in this thread yet, forgive me if I missed an email mentioning this. What I personally would like to see is a publishing infrastructure to allow pushing built images to an internal infra mirror/repo/registry for consumption of

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

On 16 May 2017 at 06:22, Doug Hellmann wrote: > Excerpts from Thierry Carrez's message of 2017-05-16 14:08:07 +0200: >> Flavio Percoco wrote: >> > From a release perspective, as Doug mentioned, we've avoided releasing >> > projects >> > in any kind of built form. This was

Re: [openstack-dev] [keystone] [Pile] Need Exemption On Submitted Spec for the Keystone

That sounds good - I'll review the spec before today's meeting [0]. Will someone be around to answer questions about the spec if there are any? [0] http://eavesdrop.openstack.org/#Keystone_Team_Meeting On Mon, May 15, 2017 at 11:24 PM, Mh Raies wrote: > Hi Lance, > > >

Re: [openstack-dev] [all][keystone][product] api keys/application specific passwords

On 05/16/2017 05:39 AM, Sean Dague wrote: On 05/15/2017 10:00 PM, Adrian Turjak wrote: On 16/05/17 13:29, Lance Bragstad wrote: On Mon, May 15, 2017 at 7:07 PM, Adrian Turjak > wrote: Based on the specs that are currently up

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

On 16 May 2017 at 06:22, Doug Hellmann wrote: > Excerpts from Thierry Carrez's message of 2017-05-16 14:08:07 +0200: >> Flavio Percoco wrote: >> > From a release perspective, as Doug mentioned, we've avoided releasing >> > projects >> > in any kind of built form. This was

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

On 16 May 2017 at 06:20, Flavio Percoco wrote: > On 16/05/17 14:08 +0200, Thierry Carrez wrote: >> >> Flavio Percoco wrote: >>> >>> From a release perspective, as Doug mentioned, we've avoided releasing >>> projects >>> in any kind of built form. This was also one of the

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

Excerpts from Flavio Percoco's message of 2017-05-15 21:50:23 -0400: > On 15/05/17 11:49 -0700, Michał Jastrzębski wrote: > >On 15 May 2017 at 11:19, Davanum Srinivas wrote: > >> Sorry for the top post, Michal, Can you please clarify a couple of things: > >> > >> 1) Can folks

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

This is one of those areas that was shared understanding for a long time, and seems less "shared" now that we've grown and added new projects to the community. I intended to prepare a governance resolution *after* having some public discussion, so that we can restore that common understanding

[openstack-dev] [tc][all] Do we need a #openstack-tc IRC channel

Folks, See $TITLE :) Thanks, Dims -- Davanum Srinivas :: https://twitter.com/dims __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [vitrage] [nova] VM Heartbeat / Healthcheck Monitoring

Sam, Two other more higher-level points I wanted to discuss with you about Masaraki. First, so I notice that you are doing both monitoring, auto-recovery and even host maintenance type functionality as part of the Masaraki architecture. are you open to some configurability

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

Steve, We should not always ask "if this is a ruling from the TC", the default is that it's a discussion/exploration. If it is a "ruling", it won't be on a ML thread. Thanks, Dims On Tue, May 16, 2017 at 9:22 AM, Steven Dake (stdake) wrote: > Dims, > > The [tc] was in the

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

On 05/16/2017 09:24 AM, Doug Hellmann wrote: > Excerpts from Luigi Toscano's message of 2017-05-16 11:50:53 +0200: >> On Monday, 15 May 2017 21:12:16 CEST Doug Hellmann wrote: >>> Excerpts from Michał Jastrzębski's message of 2017-05-15 10:52:12 -0700: >>> On 15 May 2017 at 10:34, Doug

Re: [openstack-dev] [tripleo] Validations before upgrades and updates

On Mon, May 15, 2017 at 6:27 PM, Steven Hardy wrote: > On Mon, May 08, 2017 at 02:45:08PM +0300, Marios Andreou wrote: >>Hi folks, after some discussion locally with colleagues about improving >>the upgrades experience, one of the items that came up was pre-upgrade and

Re: [openstack-dev] [tempest] Proposing Fanglei Zhu for Tempest core

On Tue, May 16, 2017 at 08:22:44AM +, Andrea Frittoli wrote: > Hello team, > > I'm very pleased to propose Fanglei Zhu (zhufl) for Tempest core. > > Over the past two cycle Fanglei has been steadily contributing to Tempest > and its community. > She's done a great deal of work in making

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

On 16/05/17 14:08 +0200, Thierry Carrez wrote: Flavio Percoco wrote: From a release perspective, as Doug mentioned, we've avoided releasing projects in any kind of built form. This was also one of the concerns I raised when working on the proposal to support other programming languages. The

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

Excerpts from Luigi Toscano's message of 2017-05-16 11:50:53 +0200: > On Monday, 15 May 2017 21:12:16 CEST Doug Hellmann wrote: > > Excerpts from Michał Jastrzębski's message of 2017-05-15 10:52:12 -0700: > > > > > On 15 May 2017 at 10:34, Doug Hellmann wrote: > > > > I'm

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

Excerpts from Thierry Carrez's message of 2017-05-16 14:08:07 +0200: > Flavio Percoco wrote: > > From a release perspective, as Doug mentioned, we've avoided releasing > > projects > > in any kind of built form. This was also one of the concerns I raised when > > working on the proposal to

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

Dims, The [tc] was in the subject tag, and the message was represented as indicating some TC directive and has had several tc members comment on the thread. I did nothing wrong. Regards -steve -Original Message- From: Davanum Srinivas Reply-To: "OpenStack

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

On 16/05/17 04:22 +, Steven Dake (stdake) wrote: Flavio, Forgive the top post – outlook ftw. I understand the concerns raised in this thread. It is unclear if this thread is the feeling of two TC members or enough TC members care deeply about this issue to permanently limit OpenStack

Re: [openstack-dev] [vitrage] [nova] VM Heartbeat / Healthcheck Monitoring

thanks for the pointers Sam. I took a quick look. I agree that the VM Heartbeat / Health-check looks like a good fit into Masakari. Currently your instance monitoring looks like it is strictly black-box type monitoring thru libvirt events. Is that correct ? i.e. you do not do any intrusive

Re: [openstack-dev] [oslo] Can we stop global requirements update?

On Tue, May 16 2017, Andreas Jaeger wrote: > It is needed to generate the translations, but can't we move it for > oslo-i18n into test-requirements? I've pushed this and it seems to work, pretty sure it's safe. https://review.openstack.org/#/c/465014/ If we can merge this today and then

Re: [openstack-dev] [vitrage] [nova] [HA] VM Heartbeat / Healthcheck Monitoring

Afek, Ifat (Nokia - IL/Kfar Sava) wrote: On 16/05/2017, 4:36, "Sam P" wrote: Hi Greg, In Masakari [0] for VMHA, we have already implemented some what similar function in masakri-monitors. Masakari-monitors runs on nova-compute node,

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

Flavio Percoco wrote: > From a release perspective, as Doug mentioned, we've avoided releasing > projects > in any kind of built form. This was also one of the concerns I raised when > working on the proposal to support other programming languages. The problem of > releasing built images goes

Re: [openstack-dev] [vitrage] [nova] VM Heartbeat / Healthcheck Monitoring

On 16/05/2017, 4:36, "Sam P" wrote: Hi Greg, In Masakari [0] for VMHA, we have already implemented some what similar function in masakri-monitors. Masakari-monitors runs on nova-compute node, and monitors the host, process or instance failures.

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

Why drag TC into this discussion Steven? If the TC has something to say, it will be in the form of a resolution with topic "formal-vote". So please Stop! Thanks, Dims On Tue, May 16, 2017 at 12:22 AM, Steven Dake (stdake) wrote: > Flavio, > > Forgive the top post – outlook

Re: [openstack-dev] [tripleo] Issue while applying customs configuration to overcloud.

On Tue, May 16, 2017 at 04:33:33AM +, Dnyaneshwar Pawar wrote: > Hi TripleO team, > > I am trying to apply custom configuration to an existing overcloud. (using > openstack overcloud deploy command) > Though there is no error, the configuration is in not applied to overcloud. > Am I missing

Re: [openstack-dev] [all][keystone][product] api keys/application specific passwords

On 05/15/2017 10:00 PM, Adrian Turjak wrote: > > > On 16/05/17 13:29, Lance Bragstad wrote: >> >> >> On Mon, May 15, 2017 at 7:07 PM, Adrian Turjak >> > wrote: >> Based on the specs that are currently up in Keystone-specs, I >>

Re: [openstack-dev] [oslo] Can we stop global requirements update?

On 2017-05-16 12:10, Julien Danjou wrote: > On Tue, May 16 2017, Andreas Jaeger wrote: > >> what exactly happened with Babel? >> >> I see in global-requirements the following: >> Babel>=2.3.4,!=2.4.0 # BSD >> >> that shouldn't case a problem - or does it? Or what's the problem? > > Damn, at the

Re: [openstack-dev] [infra][all] etcd tarballs for CI use

Jesse, Great question :) We need the version that has the grpc gateway v3alpha API: https://github.com/coreos/etcd/pull/5669 Since we want to standardize on the etcd v3 API (to avoid migration of data from /v2 to /v3). Unfortunately the v3 API is gRPC based and has trouble with eventlet based

Re: [openstack-dev] [oslo] Can we stop global requirements update?

On Tue, May 16 2017, Andreas Jaeger wrote: > what exactly happened with Babel? > > I see in global-requirements the following: > Babel>=2.3.4,!=2.4.0 # BSD > > that shouldn't case a problem - or does it? Or what's the problem? Damn, at the moment I pressed the `Sent' button I thought "You just

[openstack-dev] [networking-sfc] pep8 failing

Hi Team, pep8 is failing in master code. *translation hint helpers *are removed from LOG messages. Is this purposefully done ? Let me know if it is not, will change it. ./networking_sfc/db/flowclassifier_db.py:342:13: N531 Log messages require translation hints! LOG.info("Deleting

Re: [openstack-dev] [oslo] Can we stop global requirements update?

On 2017-05-16 11:42, Julien Danjou wrote: > On Wed, Apr 19 2017, Julien Danjou wrote: > >> So Gnocchi gate is all broken (agan) because it depends on "pbr" and >> some new release of oslo.* depends on pbr!=2.1.0. > > Same things happened today with Babel. As far as Gnocchi is concerned, >

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

On Monday, 15 May 2017 21:12:16 CEST Doug Hellmann wrote: > Excerpts from Michał Jastrzębski's message of 2017-05-15 10:52:12 -0700: > > > On 15 May 2017 at 10:34, Doug Hellmann wrote: > > > I'm raising the issue here to get some more input into how to > > > proceed. Do

Re: [openstack-dev] [oslo] Can we stop global requirements update?

On Wed, Apr 19 2017, Julien Danjou wrote: > So Gnocchi gate is all broken (agan) because it depends on "pbr" and > some new release of oslo.* depends on pbr!=2.1.0. Same things happened today with Babel. As far as Gnocchi is concerned, we're going to take the easiest route and remove all our

Re: [openstack-dev] [tripleo] Issue while applying customs configuration to overcloud.

Hi Marios, Thanks for your reply. Referred example mentioned at https://docs.openstack.org/developer/tripleo-docs/advanced_deployment/extra_config.html , it is failing with error mentioned at http://paste.openstack.org/show/609644/ Regards, Dnyaneshwar From: Marios Andreou

Re: [openstack-dev] [tempest] Proposing Fanglei Zhu for Tempest core

+1. Nice work done by Fanglei and good to have her in team. -gmann On Tue, May 16, 2017 at 5:22 PM, Andrea Frittoli wrote: > Hello team, > > I'm very pleased to propose Fanglei Zhu (zhufl) for Tempest core. > > Over the past two cycle Fanglei has been steadily

Re: [openstack-dev] [infra][all] etcd tarballs for CI use

On 5/15/17, 11:20 PM, "Davanum Srinivas" wrote: > At this moment, though Fedora has 3.1.7 [1], Xenial is way too old, So > we will need to pull down tar balls from either [2] or [3]. proposing > backports is a possibility, but then we need some flexibility if we > end up

[openstack-dev] [tricircle]cancellation of weekly meeting(May 17) due to bug smash

Hello, team, The bug smash will be held May.17~19, the weekly meeting of May. 17 will be cancelled. Best Regards Chaoyi Huang (joehuang) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [all] Consolidating web themes

This all sounds really great ☺ thanks for taking it on board, Anne! No questions at present ☺ looking forward to seeing the new design! From: Anne Gentle Reply-To: "OpenStack Development Mailing List (not for usage questions)"

[openstack-dev] [tempest] Proposing Fanglei Zhu for Tempest core

Hello team, I'm very pleased to propose Fanglei Zhu (zhufl) for Tempest core. Over the past two cycle Fanglei has been steadily contributing to Tempest and its community. She's done a great deal of work in making Tempest code cleaner, easier to read, maintain and debug, fixing bugs and removing

Re: [openstack-dev] [oslo][oslo.messaging] Call to deprecate the 'pika' driver in the oslo.messaging project

+1 too, I haven't seen its contributors since a while. On Mon, May 15, 2017 at 09:42:00PM -0400, Flavio Percoco wrote: On 15/05/17 15:29 -0500, Ben Nemec wrote: On 05/15/2017 01:55 PM, Doug Hellmann wrote: Excerpts from Davanum Srinivas (dims)'s message of 2017-05-15 14:27:36 -0400: On

Re: [openstack-dev] [POC] Introduce an auto-converge policy to speedup migration

Hi Chris, Sorry for no Cc to you, I remember I have added cc Thanks, Chao Fan On Mon, May 15, 2017 at 01:30:39PM +0800, Chao Fan wrote: >On Thu, May 11, 2017 at 02:34:16PM -0400, Chris Friesen wrote: >>On 05/11/2017 05:58 AM, Chao Fan wrote: >>> Hi all, >>> >>> We plan to develop a policy

[openstack-dev] [storlets] No team meeting today

Hi All, There will be no team meeting today. As usual, if you have something please ping at #openstack-storlets Thanks, Eran __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [tripleo] Issue while applying customs configuration to overcloud.

On Tue, May 16, 2017 at 7:33 AM, Dnyaneshwar Pawar < dnyaneshwar.pa...@veritas.com> wrote: > Hi TripleO team, > > I am trying to apply custom configuration to an existing overcloud. (using > openstack overcloud deploy command) > Though there is no error, the configuration is in not applied to

<    1   2