[openstack-dev] [vitrage] use case repository

Hi root causers, Use case repository is considered as one of the very important subject to work on in Pike release[1]. I wonder what kind of use cases we have deployed/validated in vitrage, no matter in production or experimental, and where can I find related information? [1]:

Re: [openstack-dev] [telemetry] [ceilometer] Difference between publishers and dispatchers?

Hi Andres, Ceilometer has deprecated collector from Pike, so dispatchers will be no longer used in the future. Data should be pushed from publisher to storage backend(e.g. Gnocchi) and/or other outer system. Some dispatchers were deprecated because there are corresponding developed publisher, for

[openstack-dev] [Blazar] Meeting time slots in Boston

Hi Blazar folks, I created doodle[1] to decide our meeting time slots in Boston summit. Please check slots you can join the meeting by Thursday. I'll decide the slots on this Friday. Additionally, I'd like to ask you to write down how many hours we have the meeting in comments of the

Re: [openstack-dev] [kolla] Tags, revisions, dockerhub

So, while I agree that everyone should use images built locally, I also see what is value of downloading dockerhub-hosted images (besides speed). Images at dockerhub passed our gates and are CI tested. Which means quality of these images is ensured by our CI. Not everyone can afford to have CI/CD

Re: [openstack-dev] [kolla] Tags, revisions, dockerhub

I think we have two topics and improvements here 1. images in https://hub.docker.com/r/kolla/ 2. tag in end-user env. # images in hub.docker.com we are building kolla tag image and push them into hub.docker.com. After this, we do nothing for these images. The issue is 1. any security update

Re: [openstack-dev] [all] blog post about being PTL in OpenStack

yeah, I read https://blog.flaper87.com/something-about-being-a-ptl.html before I take the role , that really helps me a lot . I aslo share the blog in some meetups. Thanks Flavio and Emilien. and I will attend https://www.openstack.org/summ it/boston-2017/summit-schedule/events/18518/ 2017-04-18

Re: [openstack-dev] [keystone][glance][ironic][octavia][nova]oslo.config 4.0 will break projects' unit test

Thanks Michael Johnson for your fix ! We plan to release oslo.config 4.0 when each project has a fix at least in review , Latest updates: Nova: https://review.openstack.org/457188 need review Keystone: https://review.openstack.org/455391 wait for oslo.config 4.0 Glance:

Re: [openstack-dev] [telemetry] [ceilometer] Difference between publishers and dispatchers?

Hi Julien Thanks for your response. So does this mean that dispatchers will also be deprecated (if not already deprecated) in favor of only using publishers? On Mon, Apr 17, 2017 at 5:49 PM, Julien Danjou wrote: > On Mon, Apr 17 2017, Andres Alvarez wrote: > > Hi Andres, >

Re: [openstack-dev] [api-wg] Question about 'OpenStack-API-Version' header

On Mon, Apr 17, 2017 at 10:22:16AM +0100, Chris Dent wrote: > On Fri, 14 Apr 2017, Qiming Teng wrote: > > >According to the microversion specification [1], the > >'OpenStack-API-Version' header is optional. When it is omitted, the > >server should act as if the minimum supported version was

Re: [openstack-dev] [Tacker][OSC] Command naming specs

Hi Jay, See inline ... On Fri, Apr 14, 2017 at 12:25 PM, Jay Pipes wrote: > On 04/12/2017 03:08 AM, Trinath Somanchi wrote: > >> Hi OSC team- >> >> While implementing tacker-cli commands as OSC plugins [1], We are >> struck in command naming specifications. >> >> Tacker

Re: [openstack-dev] [tc] [elections] Available time and top priority

On Mon, Apr 10, 2017 at 4:40 PM, Matt Riedemann wrote: > On 4/10/2017 2:55 PM, Dean Troyer wrote: >> >> >> The TC meetings are held in IRC and that may somewhat mitigate the >> issue for non-native English speakers, but I've had problems myself >> keeping up at times with the

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

On Mon, Apr 17, 2017 at 09:55:51AM -0400, Brian Rosmaita wrote: > On 4/12/17 2:47 AM, Tony Breeds wrote: > > Hi all, > > I'm late in sending this announement, but I'm glad to see several > > projects > > have already requested EOL releases to make it trivial and obvious where to > > apply the

[openstack-dev] [neutron] keeping on top of neutron reviews

Hello Neutron reviewers, Please keep an eye on the review links in https://docs.openstack.org/developer/neutron/dashboards/index.html as part of your review routine. I went through and reviewed a lot of old patches over the weekend so if we keep on top of that list it shouldn't get out of hand.

Re: [openstack-dev] [kolla] Tags, revisions, dockerhub

On Tue, Apr 18, 2017 at 9:57 AM, Doug Hellmann wrote: > Excerpts from Michał Jastrzębski's message of 2017-04-12 15:59:34 -0700: > > My dear Kollegues, > > > > Today we had discussion about how to properly name/tag images being > > pushed to dockerhub. That moved towards

[openstack-dev] [neutron] Release liaison needed

Hey folks, Unfortunately, I'm not able to fulfill release liaison role anymore. The same applies to being infra liaison. It means, that this very important role needs YOU! If you'll decide to join the army of release liaisons, you will be responsible for: * releases! * communication with release

Re: [openstack-dev] [qa][gate] tempest slow - where do we execute them in gate?

On Mon, Apr 17, 2017 at 7:58 PM Ihar Hrachyshka wrote: > On Mon, Apr 17, 2017 at 9:35 AM, Jordan Pittier > wrote: > > We don"t run slow tests because the QA team think that they don't bring > > enough value to be executed, every time and

Re: [openstack-dev] [kolla] Tags, revisions, dockerhub

Excerpts from Michał Jastrzębski's message of 2017-04-12 15:59:34 -0700: > My dear Kollegues, > > Today we had discussion about how to properly name/tag images being > pushed to dockerhub. That moved towards general discussion on revision > mgmt. > > Problem we're trying to solve is this: > If

Re: [openstack-dev] [gnocchi] new measures backlog scheduling

On 17/04/17 12:09 PM, gordon chung wrote: > i tried also to implement jump hash[2], which improved distribution and > is in theory, less memory intensive as it does not maintain a hash > table. while better at distribution, it still is not completely uniform > and similarly, the less sacks per

Re: [openstack-dev] [intel experimental ci] Is it actually checking anything?

On Mon, Apr 17, 2017 at 12:31 PM, Jay Pipes wrote: > Please see the below output from the Intel Experimental CI (from > https://review.openstack.org/414769): > > On 04/17/2017 01:28 PM, Intel Experimental CI (Code Review) wrote: >> >> Intel Experimental CI has posted comments

Re: [openstack-dev] [tc][elections]questions about one platform vision

> On 2017. Apr 16., at 3:03, Neil Jerram wrote: > > FWIW, I think the Lego analogy is not actually helpful for another reason: it > has vastly too many ways of combining, and (hence) no sense at all of > consistency / interoperability between the different things that you can

Re: [openstack-dev] [glance][ironic][octavia] oslo.config 4.0 will break projects' unit test

Thank you ChangBo, I have resolved the issues in octavia in this patch: https://review.openstack.org/457356 up for review. Michael From: ChangBo Guo [mailto:glongw...@gmail.com] Sent: Sunday, April 16, 2017 12:32 AM To: OpenStack Development Mailing List (not for usage questions)

[openstack-dev] [monasca][swift][storyboard] migration experience

Moasca-teers As the migration away from Launchpad and to Storyboard moves forward, the Swift team has been considering making the move. Monasca has already made the move, so I'd love to hear your thoughts on that process. 1) How did you do the change? All at once or gradually? If you did it over

Re: [openstack-dev] [all] blog post about being PTL in OpenStack

On 17/04/17 13:39 -0500, Matt Riedemann wrote: On 4/13/2017 7:22 PM, Emilien Macchi wrote: Exceptionally, I'll self-promote a blog post that I wrote about my personal experience of being PTL in OpenStack. http://my1.fr/blog/my-journey-as-an-openstack-ptl/ My hope is to engage some discussion

[openstack-dev] [TripleO][CI] Bridging the production/CI workflow gap with large periodic CI jobs

Because CI jobs tend to max out about 5 nodes there's a whole class of minor bugs that make it into releases. What happens is that they never show up in small clouds, then when they do show up in larger testing clouds the people deploying those simply work around the issue and get onto what they

Re: [openstack-dev] [nova] placement/resource providers update 19

On 4/14/2017 5:18 AM, Chris Dent wrote: Here's the 19th placement and resource providers update. As usual, if I've left anything out, please followup with that information. # What Matters Most Discussion continues on the spec for claims being done during scheduling. Getting this worked out

[openstack-dev] [os-upstream-institute] Meeting reminder

Hi Team, A quick reminder that our next meeting will take place in #openstack-meeting-3 in 15 minutes (2000 UTC). See you there! :) Thanks, Ildikó IRC: ildikov __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [ironic] [third-party-ci] pkvmci ironic job breakage details

On 04/17/2017 02:25 PM, Matt Riedemann wrote: On 4/14/2017 10:51 AM, Michael Turek wrote: Hey ironic-ers, So our third party CI job for ironic has been, and remains, broken. I was able to do some investigation today and here's a summary of what we're seeing. I'm hoping someone might know the

Re: [openstack-dev] [ironic] [third-party-ci] pkvmci ironic job breakage details

Dell - Internal Use - Confidential Hi Mike I do see this problem this week. See logs. https://stash.opencrowbar.org/logs/52/456952/2/check/dell-hw-tempest-dsvm-ironic-pxe_ipmitool/315bd85/ We were running 5 builds on a one node devstack-cloud and now made it 6 and started seeing this

Re: [openstack-dev] [qa][gate] tempest slow - where do we execute them in gate?

On Mon, Apr 17, 2017 at 11:55:28AM -0700, Ihar Hrachyshka wrote: > On Mon, Apr 17, 2017 at 9:35 AM, Jordan Pittier > wrote: > > We don"t run slow tests because the QA team think that they don't bring > > enough value to be executed, every time and everywhere. The idea

Re: [openstack-dev] [qa][gate] tempest slow - where do we execute them in gate?

On Mon, Apr 17, 2017 at 9:35 AM, Jordan Pittier wrote: > We don"t run slow tests because the QA team think that they don't bring > enough value to be executed, every time and everywhere. The idea is that if > some specific slow tests are of some interest to some

Re: [openstack-dev] [all] blog post about being PTL in OpenStack

On 4/13/2017 7:22 PM, Emilien Macchi wrote: Exceptionally, I'll self-promote a blog post that I wrote about my personal experience of being PTL in OpenStack. http://my1.fr/blog/my-journey-as-an-openstack-ptl/ My hope is to engage some discussion about what our community thinks about this role

Re: [openstack-dev] [ironic] [third-party-ci] pkvmci ironic job breakage details

On 4/14/2017 10:51 AM, Michael Turek wrote: Hey ironic-ers, So our third party CI job for ironic has been, and remains, broken. I was able to do some investigation today and here's a summary of what we're seeing. I'm hoping someone might know the root of the problem. For reference, please see

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

Hi, On Mon, Apr 17, 2017 at 7:32 PM, Carmine Annunziata < carmine.annunziat...@gmail.com> wrote: > Hi guys, > I'm trying to integrate designate in openstack by devstack, the standard > procedure uses rejoin-stack.sh after the stack.sh but in the last release > there isn't anymore. So what may i

[openstack-dev] [Openstack-dev] [Designate]

Hi guys, I'm trying to integrate designate in openstack by devstack, the standard procedure uses rejoin-stack.sh after the stack.sh but in the last release there isn't anymore. So what may i do alternatively? Carmine __

[openstack-dev] [intel experimental ci] Is it actually checking anything?

Please see the below output from the Intel Experimental CI (from https://review.openstack.org/414769): On 04/17/2017 01:28 PM, Intel Experimental CI (Code Review) wrote: Intel Experimental CI has posted comments on this change. Change subject: placement: SRIOV PF devices as child providers

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

On Wed, Apr 12, 2017 at 2:47 AM, Tony Breeds wrote: > Hi all, > I'm late in sending this announement, but I'm glad to see several projects > have already requested EOL releases to make it trivial and obvious where to > apply the tag. > > I'm proposing to EOL all

Re: [openstack-dev] [tripleo] pingtest vs tempest

On Mon, Apr 17, 2017 at 12:28 PM, Ben Nemec wrote: > Tempest isn't really either of those things. According to another message > in this thread it takes around 15 minutes to run just the smoke tests. > That's unacceptable for a lot of our CI jobs. Ben, is the issue

Re: [openstack-dev] [qa][gate] tempest slow - where do we execute them in gate?

On Mon, Apr 17, 2017 at 6:50 AM, Ihar Hrachyshka wrote: > Hi all, > > so I tried to inject a failure in a tempest test and was surprised > that no gate job failed because of that: > https://review.openstack.org/#/c/457102/1 > > It turned out that the test is not executed

Re: [openstack-dev] [tripleo] pingtest vs tempest

On 04/17/2017 10:51 AM, Emilien Macchi wrote: We haven't got much feedback from TripleO core reviewers, who are usually more involved on this topic. I'll give a chance to let them talk because we take some actions based on the feedback brought in this discussion. I started to write a

[openstack-dev] [Glare][Mistral][Murano] Glare client was added to global requirements

Hello! I'm happy to announce that recently glare client was added to openstack's global requirements. Current version (0.3) contains 'glareclient' library, plugin to openstack client - 'openstack artifact', and a standalone cli - 'glare'. Now I'm finishing writing the documentation about cli

Re: [openstack-dev] [cinder][stable] Deprecation notice: Cinder Driver for NetApp E-Series

On Sat, Apr 15, 2017 at 03:25:09AM +, Ravi, Goutham wrote: > > What is being deprecated: Cinder drivers for NetApp E-Series > > Period of deprecation: E-Series drivers will be around in stable/pike and > will be removed in the Queens release (All milestones of this release) > Thanks for

Re: [openstack-dev] [tripleo] pingtest vs tempest

We haven't got much feedback from TripleO core reviewers, who are usually more involved on this topic. I'll give a chance to let them talk because we take some actions based on the feedback brought in this discussion. Thanks, On Fri, Apr 7, 2017 at 4:26 AM, Ravi Sekhar Reddy Konda

Re: [openstack-dev] [nova][deployment] FYI: changes to cells v2 setup guide (pike only)

On 4/16/2017 10:35 PM, Alex Xu wrote: Is it strange that the 'nova service-list' and 'nova host-list' return the hosts which didn't have host mapping yet? It's kind of strange yes. We could probably make GET /os-hypervisors work without requiring the host mappings, but it just doesn't today

[openstack-dev] [mistral] New CI Job definitions

Hi y'all... In the midst of trying to track down some errors being seen with tempest tests whilst running under mod_wsgi/apache, I've made it so that the devstack plugin is capable of also running with mod_wsgi/apache.[1] In doing so, It's become the default devstack job. I've also now created

Re: [openstack-dev] [all] Switching gate testing to use Ubuntu Cloud Archive

Ihar Hrachyshka writes: > I just saw the plan merged in master: > https://review.openstack.org/#/c/451492/ That's cool! Can we also > backport the change to Ocata and maybe Newton so that we don't hit the > same bug there? The backport is already up: > https://review.openstack.org/#/c/456506/ For

Re: [openstack-dev] [nova] Usability question for the server migrations API

On 4/17/2017 12:27 AM, Alex Xu wrote: Also note that, we still have the API '/os-migrations', it will return all the migration records in any status for all the VMs, and it supports filters like 'instance_uuid', 'status', and 'migration_type' etc. I can't remember clearly whether we said we will

Re: [openstack-dev] [all] Switching gate testing to use Ubuntu Cloud Archive

I just saw the plan merged in master: https://review.openstack.org/#/c/451492/ That's cool! Can we also backport the change to Ocata and maybe Newton so that we don't hit the same bug there? The backport is already up: https://review.openstack.org/#/c/456506/ Thanks, Ihar On Mon, Apr 3, 2017 at

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

On 4/12/17 2:47 AM, Tony Breeds wrote: > Hi all, > I'm late in sending this announement, but I'm glad to see several projects > have already requested EOL releases to make it trivial and obvious where to > apply the tag. > > I'm proposing to EOL all projects ... Hi Tony, just wanted to give

Re: [openstack-dev] [keystone] Integrate Identity with LDAP

Yes, you are right, Кирилл! Thanks, Chason From: Кирилл Беспалов Date: 2017-04-17 20:01 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [keystone] Integrate Identity with LDAP Hi! Seems you are faced with the bug:

Re: [openstack-dev] [keystone] Integrate Identity with LDAP

Hi! Seems you are faced with the bug: https://bugs.launchpad.net/keystone/+bug/1662762 Please make sure that Keystone already has the fix - https://review.openstack.org/#/c/437402/ 2017-04-17 6:56 GMT+03:00 Chason Chan : > Hi team, > > I am trying to integrate Identity

Re: [openstack-dev] [ceilometer]

On Mon, Apr 17 2017, Andres Alvarez wrote: > Hello everyone > > I am trying to get acquainted with the Ceilometer code base. I was reading > through the Telemetry Admin Guide > > regarding publishers and noticed that there are

Re: [openstack-dev] [telemetry] [ceilometer] Difference between publishers and dispatchers?

On Mon, Apr 17 2017, Andres Alvarez wrote: Hi Andres, > I am a bit confused on what is the difference between dispatchers and > publishers in Ceilometer. The documentation explains a bit about publishers > in the pipeline, but it does not mention much (if anything) about > dispatchers.

Re: [openstack-dev] [api-wg] Question about 'OpenStack-API-Version' header

On Fri, 14 Apr 2017, Qiming Teng wrote: According to the microversion specification [1], the 'OpenStack-API-Version' header is optional. When it is omitted, the server should act as if the minimum supported version was specified. That's correct. Recently, we have received some complaints

Re: [openstack-dev] [libvirt] Whether kvm supports NVIDIA VGPU

2017-04-15 3:03 GMT+08:00 Jay Pipes : > On 04/12/2017 10:53 PM, 文峰sx-9149 wrote: > >> Will the openstack or libvirt (kvm) support NVIDIA VGPU? >> I am here >> >> to see a mail introduction libvirt kvm

[openstack-dev] [telemetry] [ceilometer] Difference between publishers and dispatchers?

Hi everyone I am a bit confused on what is the difference between dispatchers and publishers in Ceilometer. The documentation explains a bit about publishers in the pipeline, but it does not mention much (if anything) about dispatchers. Would appreciate if someone can shed some light on this.

Re: [openstack-dev] [Tacker][OSC] Command naming specs

Agree. Vnffg can be moved as 'vnf forwardinggraph'. Also, we are discussing to improve the command readability from an user perspective. Thanks, Trinath Somanchi. Digital Networking | NXP – Hyderabad – INDIA. Email: trinath.soman...@nxp.com Mobile: +91 9866235130 | Off: +91 4033504051

Re: [openstack-dev] [neutron][sfc][fwaas][taas][horizon] where would we like to have horizon dashboard for neutron stadium projects?

Hi TIm, I think no user-visible changes happen for users. Do you have any example in your mind? I understand horizon lacks supports of some hooks (such as adding a menu to an existing table). If there are missing things, 2017-04-12 2:24 GMT+09:00 Tim Bell : > Are there any

Re: [openstack-dev] [Tacker][OSC] Command naming specs

2017-04-15 12:44 GMT+09:00 Trinath Somanchi : > Hi Jay- > > Thanks for the suggestions, we have improved this to an extent [1]. > > For 'openstack vnf service function chain create' we agreed to go with, > 'openstack nfv chain create' or 'openstack vnf chain create' I