Re: [openstack-dev] [requirements][masakari] FFE for adding python-masakariclient in global-requirements

Hi Tony, Correction: >> You can take that or: >> https://review.openstack.org/#/c/457491/ > Thanks for the update and I will try to merge #/c/457491 asap. > Otherwise I will resolve the merge conflicts. I did not realize that you add [1] depends on [2]. I will wait for [2] to get merged. [1]

Re: [openstack-dev] [all][infra]Plan to support Python 3.6 ?

On 08/09/2017 11:25 PM, ChangBo Guo wrote: We received Python 3.6 related Bug recently [1][2]. That let me think what's the plan to support Python 3.6 for OpenStack in the future. Python 3.6 was released on December 23, 2016, has some different behaviors from Python 3.5[3]. talked with cdent

Re: [openstack-dev] [requirements][masakari] FFE for adding python-masakariclient in global-requirements

Hi Tony, As you suggested, I would like go with option 1. > Once that merges the bot will suggest a review to update your > requirements files. > > You can take that or: > https://review.openstack.org/#/c/457491/ Thanks for the update and I will try to merge #/c/457491 asap. Otherwise I

Re: [openstack-dev] [tripleo][puppet] Hold off on approving patches until further notice

On Thu, Aug 10, 2017 at 11:12 AM, Paul Belanger wrote: > On Thu, Aug 10, 2017 at 07:03:32AM -0600, Alex Schultz wrote: >> FYI, >> >> The gates are hosed for a variety of reasons[0][1] and we can't get >> critical patches merged. Please hold off on rechecking or approving >>

[openstack-dev] [keystone] keystone 12.0.0.0rc1 (pike)

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

[openstack-dev] [cinder] cinder 11.0.0.0rc1 (pike)

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

[openstack-dev] [ironic]Is there document about drac driver?

Hi, I make a test about dell server,but I can find few docs about drac driver, anybody can give me a suggestion? 保密：本函仅供收件人使用，如阁下并非抬头标明的收件人，请您即刻删除本函，勿以任何方式使用及传播，并请您能将此误发情形通知发件人，谢谢！ __ OpenStack Development Mailing

Re: [openstack-dev] [neutron][vpnaas] pike rc

done http://git.openstack.org/cgit/openstack/neutron-vpnaas/tag/?h=11.0.0.0rc1 https://review.openstack.org/#/q/status:open+project:openstack/neutron-vpnaas+branch:stable/pike+topic:create-pike On Tue, Aug 8, 2017 at 10:46 AM, Takashi Yamamoto wrote: > hi, > > can anyone

[openstack-dev] [glance] glance 15.0.0.0rc1 (pike)

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

[openstack-dev] [senlin] senlin 4.0.0.0rc1 (pike)

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

[openstack-dev] neutron-vpnaas 11.0.0.0rc1 (pike)

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

[openstack-dev] [congress] congress 6.0.0.0rc1 (pike)

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

[openstack-dev] [sahara] sahara-dashboard 7.0.0.0rc1 (pike)

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

[openstack-dev] [sahara] sahara-image-elements 7.0.0.0rc1 (pike)

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

[openstack-dev] [sahara] sahara-extra 7.0.0.0rc1 (pike)

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

[openstack-dev] [sahara] sahara 7.0.0.0rc1 (pike)

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

Re: [openstack-dev] [neutron][tap-as-a-service] pike branch/release

done. http://git.openstack.org/cgit/openstack/tap-as-a-service/tag/?h=2.0.0 https://review.openstack.org/#/q/status:open+project:openstack/tap-as-a-service+branch:stable/pike+topic:create-pike On Tue, Aug 8, 2017 at 10:07 PM, Takashi Yamamoto wrote: > hi, > > On Tue, Aug

Re: [openstack-dev] [requirements][masakari] FFE for adding python-masakariclient in global-requirements

On Thu, Aug 10, 2017 at 12:58:21PM -0500, Sam P wrote: > Hi Tony, > > For maskari-monitors, earliest we can cut stable/pike is 8/11. > You was mentioned about masakari and related projects in [1]. > For python-masakariclient, stable/pike can be cut on 8/11. > However, for maskari I would like to

Re: [openstack-dev] [requirements][I18n][OpenStackClient][Quality Assurance][Security][Telemetry][ec2-api][heat][horizon][ironic][kuryr][magnum][manila][monasca][murano][neutron][octavia][senlin][solu

On Thu, Aug 10, 2017 at 11:01:23PM +, Jeremy Stanley wrote: > Yes, it comes up often enough and as far as I'm aware reviewers > haven't previously rejected unofficial projects who want to receive > requirements updates. There are definitely projects who don't want > to (or for license reasons

Re: [openstack-dev] [requirements][I18n][OpenStackClient][Quality Assurance][Security][Telemetry][ec2-api][heat][horizon][ironic][kuryr][magnum][manila][monasca][murano][neutron][octavia][senlin][solu

On 2017-08-11 08:49:18 +1000 (+1000), Tony Breeds wrote: > On Thu, Aug 10, 2017 at 07:22:56PM +0900, Akihiro Motoki wrote: [...] > > I am not sure that projects not under the TC governance can use > > openstack/releases repo. Is the openstack/release repo for > > projects under the governance? >

Re: [openstack-dev] [requirements][I18n][OpenStackClient][Quality Assurance][Security][Telemetry][ec2-api][heat][horizon][ironic][kuryr][magnum][manila][monasca][murano][neutron][octavia][senlin][solu

On Fri, Aug 11, 2017 at 12:46:20AM +0900, Ian Y. Choi wrote: > Akihiro Motoki wrote on 8/10/2017 7:22 PM: > > Tony, > > > > Thanks for taking care. > > > > > > > i18n I18n > > At now, i18n repo is a part of governance but this is a project which >

Re: [openstack-dev] [requirements][I18n][OpenStackClient][Quality Assurance][Security][Telemetry][ec2-api][heat][horizon][ironic][kuryr][magnum][manila][monasca][murano][neutron][octavia][senlin][solu

On Thu, Aug 10, 2017 at 07:22:56PM +0900, Akihiro Motoki wrote: > Tony, > > Thanks for taking care. > > > The following repos don't seem to use the openstack/releases repo so I > > have less information there. > > Most of them are projects not under the governance (so-called "hosted" > or

Re: [openstack-dev] [requirements][I18n][OpenStackClient][Quality Assurance][Security][Telemetry][ec2-api][heat][horizon][ironic][kuryr][magnum][manila][monasca][murano][neutron][octavia][senlin][solu

On Thu, Aug 10, 2017 at 10:17:23AM -0400, Matthew Treinish wrote: > On Thu, Aug 10, 2017 at 03:46:32PM +1000, Tony Breeds wrote: > > > > Hi All, > > In an effort to qualify which projects are likley to be affected if > > when we open the requirements repo I generated a list of all repos that:

Re: [openstack-dev] [requirements][I18n][OpenStackClient][Quality Assurance][Security][Telemetry][ec2-api][heat][horizon][ironic][kuryr][magnum][manila][monasca][murano][neutron][octavia][senlin][solu

On Thu, Aug 10, 2017 at 12:38:43PM +0200, Dmitry Tantsur wrote: > Hi Tony! > > I hope to finish releasing Ironic stuff next week. We still have a few > critical things to land. Cool > On 08/10/2017 07:46 AM, Tony Breeds wrote: > > > > Hi All, > > In an effort to qualify which projects

Re: [openstack-dev] [all][interop][heat][designate] Proposed updates to OpenStack Powered trademarks: extensions and verticals

> On Aug 10, 2017, at 2:47 PM, Chris Hoge wrote: > > At the upcoming board meeting in September, the Interop Working Group > will be proposing a new trademark program to supplement the OpenStack > Powered mark. This update formally defines two distinct types of programs. >

[openstack-dev] [all][interop][heat][designate] Proposed updates to OpenStack Powered trademarks: extensions and verticals

At the upcoming board meeting in September, the Interop Working Group will be proposing a new trademark program to supplement the OpenStack Powered mark. This update formally defines two distinct types of programs. 1) Platforms. This captures the three existing trademarks, OpenStack Powered

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

I proposed a patch to remove the deprecation [0]. [0] https://review.openstack.org/492694 On 06/28/2017 09:33 PM, Lance Bragstad wrote: > Cool - I'm glad this is generating discussion. I personally don't see > a whole lot of maintenance costs with `keystone-manage > domain_config_upload`. I was

[openstack-dev] [horizon] horizon 12.0.0.0rc1 (pike)

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

Re: [openstack-dev] [masakari]Remove ERROR instances from recovery targets

Hi Rikimaru, Currently, [1] does not skip error instances from evacuating. However, it does make it back to error after evacuating the instance. If your requirement does not satisfied with that, then the next option will be create a option for not to evacuate error VMs first place. Because,

Re: [openstack-dev] [neutron] Call for help with in-tree tempest scenario test failures

Hello, I’m still checking this QoS scenario test and I found something strange IMHO. For example, almost all failed tests from last 2 days were executed on nodes with names like: * ubuntu-xenial-2-node-citycloud-YYY- - on those nodes almost (or even all) all scenario tests was failed due to

[openstack-dev] [barbican] barbican 5.0.0.0rc1 (pike)

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

[openstack-dev] nova_powervm 5.0.0.0rc1 (pike)

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

[openstack-dev] networking-powervm 5.0.0.0rc1 (pike)

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

[openstack-dev] [telemetry] ceilometer-powervm 5.0.0.0rc1 (pike)

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

Re: [openstack-dev] [neutron][infra] Functional job failure rate at 100%

On 2017-08-10 17:13:58 + (+), Mooney, Sean K wrote: [...] > so on that it would bre quite trivial to have disk image builder > install The linux-image-virtual-hwe-16.04 > linux-image-virtual-hwe-16.04-edge to pull in a 4.10 or 4.11 > kernel respctivly if the default 4.4 is broken. We just

Re: [openstack-dev] [nova] Thanks gibi!

On 08/10/2017 01:57 PM, Matt Riedemann wrote: Apparently we don't have community contributor awards at the PTG, only the summit, and seeing as that's several months away now, which is kind of an eternity, I wanted to take the time now to thank gibi (Balazs Gibizer to his parents) for all the

Re: [openstack-dev] [all][barbican][freezer][horizon][karbor][keystone][mistral][nova][pack-deb][refstack][solum][storlets][swift][tacker][telemetry][watcher][zaqar] Last days for PTL candidate announ

On 2017-08-07 03:50 PM, Kendall Nelson wrote: Hello Everyone :) A quick reminder that we are in the last days for PTL candidate announcements. If you want to stand for PTL, don't delay, follow the instructions at [1] to make sure the community knows your intentions. Make sure your candidacy

[openstack-dev] [nova] Thanks gibi!

Apparently we don't have community contributor awards at the PTG, only the summit, and seeing as that's several months away now, which is kind of an eternity, I wanted to take the time now to thank gibi (Balazs Gibizer to his parents) for all the work he's been doing in Nova. Not only does

Re: [openstack-dev] [requirements][masakari] FFE for adding python-masakariclient in global-requirements

Hi Tony, For maskari-monitors, earliest we can cut stable/pike is 8/11. You was mentioned about masakari and related projects in [1]. For python-masakariclient, stable/pike can be cut on 8/11. However, for maskari I would like to land few changes before cut stable/pike and hopefully we can cut

Re: [openstack-dev] [heat][infra] Help needed! high gate failure rate

On Thu, Aug 10, 2017 at 12:04 PM, Paul Belanger wrote: > On Thu, Aug 10, 2017 at 07:22:42PM +0530, Rabi Mishra wrote: >> On Thu, Aug 10, 2017 at 4:34 PM, Rabi Mishra wrote: >> >> > On Thu, Aug 10, 2017 at 2:51 PM, Ian Wienand

[openstack-dev] [all][api] POST /api-wg/news

308 Permanent Redirect Location: /api-sig/news Greetings OpenStack community, As with last week, today's meeting started off with continued discussion about the Guided Review process that we are trying to create ahead of the Denver PTG. elmiko continues to shape the proposal in a review [0].

Re: [openstack-dev] [neutron][infra] Functional job failure rate at 100%

From: Miguel Angel Ajo Pelayo [mailto:majop...@redhat.com] Sent: Thursday, August 10, 2017 8:55 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron][infra] Functional job failure rate at 100% Good

Re: [openstack-dev] [tripleo][puppet] Hold off on approving patches until further notice

On Thu, Aug 10, 2017 at 07:03:32AM -0600, Alex Schultz wrote: > FYI, > > The gates are hosed for a variety of reasons[0][1] and we can't get > critical patches merged. Please hold off on rechecking or approving > anything new until further notice. We're hoping to get some of the > fixes for

[openstack-dev] [murano] murano-dashboard 4.0.0.0rc1 (pike)

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

[openstack-dev] [murano] murano 4.0.0.0rc1 (pike)

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

Re: [openstack-dev] [heat][infra] Help needed! high gate failure rate

On Thu, Aug 10, 2017 at 07:22:42PM +0530, Rabi Mishra wrote: > On Thu, Aug 10, 2017 at 4:34 PM, Rabi Mishra wrote: > > > On Thu, Aug 10, 2017 at 2:51 PM, Ian Wienand wrote: > > > >> On 08/10/2017 06:18 PM, Rico Lin wrote: > >> > We're facing a high

[openstack-dev] [freezer] freezer-dr 5.0.0.0rc1 (pike)

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

[openstack-dev] [freezer] freezer 5.0.0.0rc1 (pike)

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

[openstack-dev] [freezer] freezer-api 5.0.0.0rc1 (pike)

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

Re: [openstack-dev] [mistral][core] Proposing Andras Kovi to the Mistral core team

+1 from me. Andras will be a great addition to the core team. Original Message From: Lingxian Kong Sent: Thursday, August 10, 2017 02:59 PM To: "OpenStack Development Mailing List (not for usage questions)" Subject:

Re: [openstack-dev] [requirements][I18n][OpenStackClient][Quality Assurance][Security][Telemetry][ec2-api][heat][horizon][ironic][kuryr][magnum][manila][monasca][murano][neutron][octavia][senlin][solu

Akihiro Motoki wrote on 8/10/2017 7:22 PM: Tony, Thanks for taking care. i18n I18n At now, i18n repo is a part of governance but this is a project which has no need to cut a release, so it always follows the master branch of the requirements

Re: [openstack-dev] [neutron] possible race condition with nova instance and neutron ports

Thank you. It worked with the new settings. Now the instances are correctly in ERROR state of network is not functional. To solve the performance problem and have 0 instances in ERROR state I had to enable the neutron-rootwrap-daemon. Without it the dhcp agents were not fast enough to consume the

[openstack-dev] [monasca] Mid-cycle project team meeting

Hello everyone, as discussed yesterday in the Team Meeting there will be no Monasca planning session during the PTG. Instead we will hold a video conference one week later. The goal is to discuss the priorities and coordinate the work in the next release cycle. Please mark the dates which

Re: [openstack-dev] [docs] Doc meeting Thursday

Reminder: Docs meeting as normally scheduled in #openstack-meeting today at 16:00UTC. Agenda: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting Thanks, Alex From: Alexandra Settle Date: Tuesday, August 8, 2017 at 11:13 AM To: openstack-docs

Re: [openstack-dev] [openstack][oslo.policy] A new Keystone-Oslo hook for external PDP

Ruan, The hook is the easy part, having the data you need for making the decision is harder. -- Dims On Thu, Aug 10, 2017 at 10:51 AM, wrote: > Dims, > There is a similar prototype https://review.openstack.org/#/c/237521/. > Our idea is to provide a more generic one

Re: [openstack-dev] [openstack][oslo.policy] A new Keystone-Oslo hook for external PDP

Dims, There is a similar prototype https://review.openstack.org/#/c/237521/. Our idea is to provide a more generic one instead of Fortress. Ruan -Original Message- From: Davanum Srinivas [mailto:dava...@gmail.com] Sent: jeudi 10 août 2017 16:32 To: OpenStack Development Mailing List

Re: [openstack-dev] [openstack][oslo.policy] A new Keystone-Oslo hook for external PDP

Ruan, Have you prototyped to see if you have all the information you need is available in the context (or can be gathered from Nova)? ( quickly check what the existing HttpCheck mechanism sends over the wire ) Thanks, Dims On Thu, Aug 10, 2017 at 10:17 AM, wrote: > Hello,

[openstack-dev] [Tripleo] FFE to add Dell EMC Cinder and Manila Drivers to Triple-o

I would like to request a feature freeze exception to Dell EMC storage products support for Triple-o. This work is done and pending verification Jenkins, there seems to be some gate issues that is delaying the process. The puppet-cinder and puppet-manila work is already merged. Pending

[openstack-dev] [openstack][oslo.policy] A new Keystone-Oslo hook for external PDP

Hello, We would like to have an external and centralized security policy engine (PDP) that can pilot both OpenStack and SDN controllers. For this reason, we have developed and upstreamed a hook for the new OpenDaylight release Carbon (https://git.opendaylight.org/gerrit/#/c/46146/), and we'd

Re: [openstack-dev] [requirements][I18n][OpenStackClient][Quality Assurance][Security][Telemetry][ec2-api][heat][horizon][ironic][kuryr][magnum][manila][monasca][murano][neutron][octavia][senlin][solu

On Thu, Aug 10, 2017 at 03:46:32PM +1000, Tony Breeds wrote: > > Hi All, > In an effort to qualify which projects are likley to be affected if > when we open the requirements repo I generated a list of all repos that: > > 1. Subscribe to requirements management > 2. Do not already have a

Re: [openstack-dev] [heat][infra] Help needed! high gate failure rate

On Thu, Aug 10, 2017 at 4:34 PM, Rabi Mishra wrote: > On Thu, Aug 10, 2017 at 2:51 PM, Ian Wienand wrote: > >> On 08/10/2017 06:18 PM, Rico Lin wrote: >> > We're facing a high failure rate in Heat's gates [1], four of our gate >> > suffering with fail

[openstack-dev] [sahara] No meeting today

Sorry for the last minute notice, but we are not having Sahara team meeting today. Thanks -- TELLES NOBREGA SOFTWARE ENGINEER Red Hat I tenob...@redhat.com TRIED. TESTED. TRUSTED.

Re: [openstack-dev] package gluster-swift with Openstack swift repository

2017-08-10 9:52 GMT+02:00 Venkata R Edara : > Hello All, > > we are from Red Hat and we have product called Gluster which is distributed > file system. we have integrated Gluster with openstack-swift , the product > is called > > gluster-swift . gluster-swift allows users to

Re: [openstack-dev] [requirements][I18n][OpenStackClient][Quality Assurance][Security][Telemetry][ec2-api][heat][horizon][ironic][kuryr][magnum][manila][monasca][murano][neutron][octavia][senlin][solu

Features for tricircle pike has been freezed, and no exception was asked until now, as you proposed, If neutron can have branch this week, we can cut branch earlier. Thank you, TTX. From: Thierry Carrez [thie...@openstack.org] Sent: 10 August 2017 20:39

Re: [openstack-dev] [heat][infra] Help needed! high gate failure rate

> The reality is you're just going to have to triage this and be a *lot* > more specific with issues. I find opening an etherpad and going > through the failures one-by-one helpful (e.g. I keep [2] for centos > jobs I'm interested in). > > Looking at the top of the console.html log you'll have

[openstack-dev] [tripleo][puppet] Hold off on approving patches until further notice

FYI, The gates are hosed for a variety of reasons[0][1] and we can't get critical patches merged. Please hold off on rechecking or approving anything new until further notice. We're hoping to get some of the fixes for this merged today. I will send a note when it's OK to merge again. [0]

Re: [openstack-dev] [python-openstackclient][python-openstacksdk][neutron] supporting resource extensions with our CLI

I think this discussion has several aspects from general direction to implementation details. TL;DR My suggestion as a main maintainer of python-neutronclient is to upstream all out-of-tree APIs, support all features in OSC and push away 'neutron' CLI. The long version; In my basic

Re: [openstack-dev] [requirements][I18n][OpenStackClient][Quality Assurance][Security][Telemetry][ec2-api][heat][horizon][ironic][kuryr][magnum][manila][monasca][murano][neutron][octavia][senlin][solu

joehuang wrote: > Tricircle plans to cut stable/pike branch on August 22nd, it has dependency > on Neutron stable/pike creation. That sounds a bit late to create your release branch. It doesn't give you a lot of time to react to critical issues discovered in that release, as August 24 is the

[openstack-dev] [charms] PTL cover for the next two weeks

Hi All As I'm off in the backwaters of Scotland with zero chance of any internet access for the next two weeks, I'm delegating my PTL responsibilities to the capable Ryan Beisner until my return. I'll be back just after the charms final freeze in the leadup to the charms release at the start of

Re: [openstack-dev] [ceilometer][networking-sfc] Meters/Statistics for Networking-SFC

Hi Rajeev, No , We haven't started any design . Let me know If I can help you anywhere . We can collaborate on this :) Thanks., Mohankumar.N On Tue, Aug 8, 2017 at 12:15 PM, rajeev.satyanaray...@wipro.com < rajeev.satyanaray...@wipro.com> wrote: > Hi MohanKumar, > > > > Thanks for the

Re: [openstack-dev] [mistral][core] Proposing Andras Kovi to the Mistral core team

+1, It will be great to have him! Cheers, Lingxian Kong (Larry) On Thu, Aug 10, 2017 at 5:34 PM, Renat Akhmerov wrote: > Hi, > > I’d like to propose Andras Kovi to the Mistral core team. > > The current statistics of Andras can be seen at [1]. > Andras has been

Re: [openstack-dev] [heat][infra] Help needed! high gate failure rate

On Thu, Aug 10, 2017 at 2:51 PM, Ian Wienand wrote: > On 08/10/2017 06:18 PM, Rico Lin wrote: > > We're facing a high failure rate in Heat's gates [1], four of our gate > > suffering with fail rate from 6 to near 20% in 14 days. which makes most > of > > our patch stuck with

[openstack-dev] [ironic] Countdown to Pike final

Hi team! I would like to finish our releases, or at least the most of them, by the middle of next week to leave some time for stabilization and to avoid problems with the requirements repo branching. We have released ironic-lib, ironic-ui, sushy and the clients already. Now we need to figure

Re: [openstack-dev] [requirements][I18n][OpenStackClient][Quality Assurance][Security][Telemetry][ec2-api][heat][horizon][ironic][kuryr][magnum][manila][monasca][murano][neutron][octavia][senlin][solu

Hi Tony! I hope to finish releasing Ironic stuff next week. We still have a few critical things to land. On 08/10/2017 07:46 AM, Tony Breeds wrote: Hi All, In an effort to qualify which projects are likley to be affected if when we open the requirements repo I generated a list of all

Re: [openstack-dev] [requirements][I18n][OpenStackClient][Quality Assurance][Security][Telemetry][ec2-api][heat][horizon][ironic][kuryr][magnum][manila][monasca][murano][neutron][octavia][senlin][solu

Tony, Thanks for taking care. > The following repos don't seem to use the openstack/releases repo so I > have less information there. Most of them are projects not under the governance (so-called "hosted" or "unofficial" projects), so I am not sure there is a good way to handle them. I can

Re: [openstack-dev] [requirements][I18n][OpenStackClient][Quality Assurance][Security][Telemetry][ec2-api][heat][horizon][ironic][kuryr][magnum][manila][monasca][murano][neutron][octavia][senlin][solu

On Thu, Aug 10, 2017 at 08:41:40AM +, joehuang wrote: > Hello, > > Tricircle plans to cut stable/pike branch on August 22nd, it has > dependency on Neutron stable/pike creation. Okay in that case can you block any reviews from the proposal-bot until you do branch. Yours Tony.

Re: [openstack-dev] [requirements][I18n][OpenStackClient][Quality Assurance][Security][Telemetry][ec2-api][heat][horizon][ironic][kuryr][magnum][manila][monasca][murano][neutron][octavia][senlin][solu

On Thu, Aug 10, 2017 at 07:29:22AM +, witold.be...@est.fujitsu.com wrote: > Hi Tony, > > stable/pike branches for Monasca repos are on the way > > https://review.openstack.org/492101 Great! next cycle we'll have to try and match against open reviews to reduce the noise. Yours Tony.

Re: [openstack-dev] [all][elections] PTL Voting is now open

On Thu, Aug 10, 2017 at 1:57 PM, Dmitry Tantsur wrote: > On 08/10/2017 02:01 AM, Kendall Nelson wrote: >> >> Hello Again! >> >> Elections are underway and will remain open for you to cast your vote >> until Aug 16th, 2017 23:45 UTC. >> >> We are having elections for Ironic

Re: [openstack-dev] [heat][infra] Help needed! high gate failure rate

On 08/10/2017 06:18 PM, Rico Lin wrote: > We're facing a high failure rate in Heat's gates [1], four of our gate > suffering with fail rate from 6 to near 20% in 14 days. which makes most of > our patch stuck with the gate. There have been a confluence of things causing some problems recently.

Re: [openstack-dev] [requirements][I18n][OpenStackClient][Quality Assurance][Security][Telemetry][ec2-api][heat][horizon][ironic][kuryr][magnum][manila][monasca][murano][neutron][octavia][senlin][solu

Hello, Tricircle plans to cut stable/pike branch on August 22nd, it has dependency on Neutron stable/pike creation. Best Regards Chaoyi Huang (joehuang) From: Tony Breeds [t...@bakeyournoodle.com] Sent: 10 August 2017 13:46 To: OpenStack Development

Re: [openstack-dev] [all][elections] PTL Voting is now open

On 08/10/2017 02:01 AM, Kendall Nelson wrote: Hello Again! Elections are underway and will remain open for you to cast your vote until Aug 16th, 2017 23:45 UTC. We are having elections for Ironic and Documentation. By the way, why do I receive a poll, given that I'm one of candidates? :)

Re: [openstack-dev] [mistral][core] Proposing Andras Kovi to the Mistral core team

Hi, +1 (from an other Nokia guy, who knows Andras personally and agrees, that he is a good guy ☺) Br, Gerg0 From: Dougal Matthews [mailto:dou...@redhat.com] Sent: Thursday, August 10, 2017 9:54 AM To: OpenStack Development Mailing List (not for usage questions)

[openstack-dev] [heat][infra] Help needed! high gate failure rate

Hi all We're facing a high failure rate in Heat's gates [1], four of our gate suffering with fail rate from 6 to near 20% in 14 days. which makes most of our patch stuck with the gate. gate-heat-dsvm-functional-convg-mysql-lbaasv2-ubuntu-xenial(19.67%)

Re: [openstack-dev] [mistral][core] Proposing Andras Kovi to the Mistral core team

On 10 August 2017 at 06:34, Renat Akhmerov wrote: > Hi, > > I’d like to propose Andras Kovi to the Mistral core team. > > The current statistics of Andras can be seen at [1]. > Andras has been contributing for about 1.5 years and in Pike he increased > his activity

Re: [openstack-dev] [neutron][infra] Functional job failure rate at 100%

Good (amazing) job folks. :) El 10 ago. 2017 9:43, "Thierry Carrez" escribió: > Oh, that's good for us. Should still be fixed, if only so that we can > test properly :) > > Kevin Benton wrote: > > This is just the code simulating the conntrack entries that would be > >

[openstack-dev] package gluster-swift with Openstack swift repository

Hello All, we are from Red Hat and we have product called Gluster which is distributed file system. we have integrated Gluster with openstack-swift , the product is called gluster-swift . gluster-swift

Re: [openstack-dev] [neutron][infra] Functional job failure rate at 100%

Oh, that's good for us. Should still be fixed, if only so that we can test properly :) Kevin Benton wrote: > This is just the code simulating the conntrack entries that would be > created by real traffic in a production system, right? > > On Wed, Aug 9, 2017 at 11:46 AM, Jakub Libosvar

Re: [openstack-dev] [all][infra]Plan to support Python 3.6 ?

2017-08-10 0:46 GMT+08:00 Jeremy Stanley : > On 2017-08-09 09:31:37 -0400 (-0400), Doug Hellmann wrote: > [...] > > One of the reasons we were able to move ahead with 3.5 was that it > > would be available on the platforms for which we test deployments, > > as defined in the

Re: [openstack-dev] [requirements][I18n][OpenStackClient][Quality Assurance][Security][Telemetry][ec2-api][heat][horizon][ironic][kuryr][magnum][manila][monasca][murano][neutron][octavia][senlin][solu

Hi Tony, stable/pike branches for Monasca repos are on the way https://review.openstack.org/492101 Cheers Witek > -Original Message- > From: Tony Breeds [mailto:t...@bakeyournoodle.com] > Sent: Donnerstag, 10. August 2017 07:47 > To: OpenStack Development Mailing List

Re: [openstack-dev] [ironic] support for various glance image reference formats - do we need them all?

HI Dmitry, On Tue, Aug 8, 2017 at 7:13 PM, Dmitry Tantsur wrote: > Hi! > > Thanks for raising this. > > On 08/07/2017 02:47 PM, Pavlo Shchelokovskyy wrote: > >> Hi all, >> >> currently our GlanceImageService seems to support several ways of >> defining a reference to glance

Re: [openstack-dev] [requirements][masakari] FFE for adding python-masakariclient in global-requirements

Hi Tony and all, Sorry for the delay to reply. We are planning to create the stable/pike branch soon. I am contacting the PTL Sampath Priyankara(samP) for the exact date. Thanks and Regards, Dinesh Bhor | App. Software Dev. Cnslt. dinesh.b...@nttdata.com | nttdata.com/americas -Original