[openstack-dev] [QA] Meeting Thursday July 13th at 8:00 UTC

Hello everyone, Please reminder that the weekly OpenStack QA team IRC meeting will be Thursday, July 13th at 8:00 UTC in the #openstack-meeting channel. The agenda for the meeting can be found here: https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_July_13th_2017_.280800_UTC.29

Re: [openstack-dev] [watcher] migration to storyboard

Hello :) I wanted to resurrect this thread and see how the discussion about the migration was going? I haven't seen much activity on the etherpad lately and we are eager to decide on a migration date for moving you to Storyboard! Let us know if you have any questions here or in #storyboard.

Re: [openstack-dev] [trove][all][tc] A proposal to rearchitect Trove

There is a use case where some sites have folks buy whole bricks of compute nodes that get added to the overarching cloud, but using AZ's or HostAggregates/Flavors to dedicate the hardware to the users. You might want to land the db vm on the hardware for that project and one would expect the

Re: [openstack-dev] [Shaker] Shaker Image Builder fails in Ocata due to OS::Glance::Image deprecation

Awesome Ilya. Thanks a lot. Let me look at bringing CentOS to parity. On Fri, Mar 3, 2017 at 8:36 AM, Ilya Shakhat wrote: > Hi Sai, > > As we discussed at PTG, I've added an option to build image using > diskimage-builder tool. The code is not merged yet, please see >

Re: [openstack-dev] [nova] bug triage experimentation

On 2017-07-12 15:50:26 -0500 (-0500), Jay S Bryant wrote: [...] > Looking for the, 'here is what everyone needs to know to start > using StoryBoard' documentation so I can get that linked in our > devref. [...] An excellent point, and as always a bit of a challenge when designing software for use

Re: [openstack-dev] [tripleo] scenario006 conflict

On Wed, Jul 12, 2017 at 2:23 PM, Emilien Macchi wrote: [...] > Derek, it seems like you want to deploy Ironic on scenario006 > (https://review.openstack.org/#/c/474802). I was wondering how it > would work with multinode jobs. Derek, I also would like to point out that

[openstack-dev] [tripleo] scenario006 conflict

Hey folks, Derek, it seems like you want to deploy Ironic on scenario006 (https://review.openstack.org/#/c/474802). I was wondering how it would work with multinode jobs. Also, Flavio would like to test k8s on scenario006: https://review.openstack.org/#/c/471759/ . To avoid having too much

Re: [openstack-dev] [nova] bug triage experimentation

On 2017-07-12 14:36:21 -0600 (-0600), Sean Dague wrote: [...] > It would be really nice if we could this as first class support > and not bolt on later, because I fear we're going to get pretty > complicated adhoc schema definitions here that have to be done > client side. It's still not entirely

Re: [openstack-dev] [nova] bug triage experimentation

On 7/12/2017 3:44 PM, Kendall Nelson wrote: @Jay: I would definitely urge projects to update the places they have any info about bug tracking since different projects use tags differently. I suppose we could add to the SB documentation what the common practices are, but I imagine there will

Re: [openstack-dev] [nova] bug triage experimentation

@Jay: I would definitely urge projects to update the places they have any info about bug tracking since different projects use tags differently. I suppose we could add to the SB documentation what the common practices are, but I imagine there will be a lot of project specific details about how the

Re: [openstack-dev] [nova] bug triage experimentation

On 07/12/2017 02:19 PM, Kendall Nelson wrote: Hey Sean :) So we discussed the issue of tag collisions in the SB meeting we had today. Basically, we came to the conclusion that projects should append their project to the start of the tag, thereby avoiding collision i.e. ironic-compute,

Re: [openstack-dev] [nova] bug triage experimentation

Kendall, It looks like our current bug tracking documentation is quite minimal: https://docs.openstack.org/cinder/latest/devref/launchpad.html#bug-tracking Is there going to be a place where SB is going to be documented with some of these details that we can link to under our bug-tracking

Re: [openstack-dev] [nova] bug triage experimentation

Hey Sean :) So we discussed the issue of tag collisions in the SB meeting we had today. Basically, we came to the conclusion that projects should append their project to the start of the tag, thereby avoiding collision i.e. ironic-compute, nova-compute, manila-storage, swift-storage,

Re: [openstack-dev] Queens Project Teams Gathering- Denver September 11-15th

We are less than two months out from the upcoming Project Teams Gathering in Denver, Colorado! Registration is live , and a limited discounted block of hotel rooms

Re: [openstack-dev] [zun] "--image-driver glance" doesn't seem to work @ master

k, thanks. I changed the name of the image in Glance because I wanted to prove to myself that zun/docker was pulling the image from Glance and not Docker Hub. Greg. From: Hongbin Lu Reply-To: "openstack-dev@lists.openstack.org" Date:

Re: [openstack-dev] [zun] "--nets network=..." usage question

Hi Greg, This parameter has just been added to the CLI and it hasn’t been fully implemented yet. Sorry for the confusion. Here is how I expect this parameter to work: 1. Create from neutron network name: $ zun run --name ctn-ping --nets network=private … 2. Create from neutron network uuid: $

Re: [openstack-dev] [zun] "--image-driver glance" doesn't seem to work @ master

Hi Greg, Would be great if you log the issues at, https://bugs.launchpad.net/zun/. Thanks, Pradeep On Wed, Jul 12, 2017 at 10:31 PM, Waines, Greg wrote: > Just tried this, this morning. > > I can not launch a container when I specify to pull the container image >

Re: [openstack-dev] [zun] "--image-driver glance" doesn't seem to work @ master

Hi Greg, I created a bug to record the issue: https://bugs.launchpad.net/zun/+bug/1703955 . Due to this bug, Zun couldn’t find the docker image if the image was uploaded to glance under a different name. I think it will work if you can upload the image to glance with name “cirros”. For

[openstack-dev] [tripleo] CI Squad Meeting Summary (week 27)

Greetings, Apologies for the delayed notes with regards to the last tripleo-ci-squad meeting. Highlights: * Tempest * master/pike is down to 2 tempest failures [1] out of 1,337 tests executed. * stable/ocata is a full pass on tempest * proposed tempest test to replace the tripleo ping

[openstack-dev] [zun] "--nets network=..." usage question

What is expected for the “--nets network=...” parameter on zun run or create ? Is it the network name, the subnet name, the network uuid, the subnet uuid, ... I think I’ve tried them all and none work. Full logs: stack@devstack-zun:~/devstack$ neutron net-list neutron CLI is deprecated and

[openstack-dev] [zun] "--image-driver glance" doesn't seem to work @ master

Just tried this, this morning. I can not launch a container when I specify to pull the container image from glance (instead of docker hub). I get an error back from docker saying the “:latest” can not be found. I tried renaming the glance image to “:latest” ... but that didn’t work either.

[openstack-dev] Identification Needed for Themes of Automatically Extracted Topics

Dear OpenStack developer community member, We have designed a research project to explore trends in code review as reviewers and the OpenStack developer community age. To do so, we apply Latent Dirichlet Allocation (LDA)—a popular Natural Language Processing (NLP) technique—to 506,590

[openstack-dev] [glance][nova] Examples of how to set --block-device for disk passthrough to guest

Dear Colleagues, I am trying to pass through a raw local disk from the hypervisor to one of its guests under openstack. I have read https://wiki.openstack.org/wiki/Raw-device-mapping-support which seems to address my requirement. I have done the first step, namely: glance image-update

Re: [openstack-dev] [heat] Online video meet up this week (topic:review)

On 2017-07-12 21:28:28 +0800 (+0800), Rico Lin wrote: > First, please don't worry about that replacing issue, because we > never want to replace IRC meeting in anyway. And to make this > clear, this is not even a experiment to do so. [...] Great, that's a relief. > And thanks for correct my

Re: [openstack-dev] [keystone] office hours report 2017-7-7

On 07/12/2017 09:17 AM, Akihiro Motoki wrote: > 2017-07-12 10:35 GMT+09:00 Lance Bragstad : >> Hey all, >> >> This is a summary of what was worked on today during office hours. Full logs >> of the meeting can be found below: >> >>

Re: [openstack-dev] [tripleo][ci] decreased coverage for telemetry

On Wed, Jul 12, 2017 at 10:33 AM, Pradeep Kilambi wrote: > On Tue, Jul 11, 2017 at 10:06 PM, Wesley Hayutin > wrote: > > > > > > On Tue, Jul 11, 2017 at 9:04 PM, Emilien Macchi > wrote: > >> > >> On Tue, Jul 11, 2017 at 12:41 PM,

Re: [openstack-dev] [nova] Should PUT /os-services be idempotent?

Please don't make these 400s - it should not be a client error to be unaware of the service status ahead of time. On 12 July 2017 at 11:18, Matt Riedemann wrote: > I'm looking for some broader input on something being discussed in this > change: > >

Re: [openstack-dev] [tripleo][ci] decreased coverage for telemetry

On Tue, Jul 11, 2017 at 10:06 PM, Wesley Hayutin wrote: > > > On Tue, Jul 11, 2017 at 9:04 PM, Emilien Macchi wrote: >> >> On Tue, Jul 11, 2017 at 12:41 PM, Pradeep Kilambi wrote: >> > On Tue, Jul 11, 2017 at 3:17 PM, Wesley Hayutin

[openstack-dev] [all] Queens Goal for policy-in-code

Hi all, I'd like to reach out and get ahead of the curve now that we established the community goals for Queens. If you have any questions about the policy-in-code work [0] and how it pertains to your project, please don't hesitate to ping me in #openstack-dev. Once pike starts winding down, I'll

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

+1 On Fri, Jun 30, 2017 at 4:31 AM, Hidekazu Nakamura < hid-nakam...@vf.jp.nec.com> wrote: > +1 > > > -Original Message- > > From: Чадин Александр (Alexander Chadin) > > [mailto:a.cha...@servionica.ru] > > Sent: Tuesday, June 27, 2017 10:44 PM > > To: OpenStack Development Mailing List >

Re: [openstack-dev] [keystone] office hours report 2017-7-7

2017-07-12 10:35 GMT+09:00 Lance Bragstad : > Hey all, > > This is a summary of what was worked on today during office hours. Full logs > of the meeting can be found below: > > http://eavesdrop.openstack.org/meetings/office_hours/2017/office_hours.2017-07-11-19.00.log.html It

Re: [openstack-dev] [trove][all][tc] A proposal to rearchitect Trove

Excerpts from Amrith Kumar's message of 2017-07-12 06:14:28 -0500: > All: > > First, let me thank all of you who responded and provided feedback > on what I wrote. I've summarized what I heard below and am posting > it as one consolidated response rather than responding to each > of your messages

Re: [openstack-dev] [nova] Should PUT /os-services be idempotent?

On Wed, Jul 12, 2017 at 11:29 AM, Alex Xu wrote: > > > 2017-07-12 9:18 GMT+08:00 Matt Riedemann : >> >> I'm looking for some broader input on something being discussed in this >> change: >> >> >>

Re: [openstack-dev] [nova] Should PUT /os-services be idempotent?

On Wed, Jul 12, 2017 at 11:20 AM, Ed Leafe wrote: > On Jul 11, 2017, at 8:18 PM, Matt Riedemann wrote: > >> With the old APIs, if you tried to enable and already enabled service, it >> was not an error. The same is you tried to disable an already disabled

Re: [openstack-dev] [heat] Online video meet up this week (topic:review)

> > > This seems like a game of semantics. In your earlier message (quoted > above) you said, "we will make our meeting this week as an online > video meeting," and you've scheduled it for the exact same time as > your normal IRC meeting. I'm not sure how anyone can come to a > different

Re: [openstack-dev] [keystone] office hours report 2017-7-7

On 07/11/2017 09:28 PM, Mathieu Gagné wrote: > Hi, > > So this email is relevant to my interests as an operator. =) Glad to hear it! > > On Tue, Jul 11, 2017 at 9:35 PM, Lance Bragstad > wrote: > > *The future of the templated catalog

[openstack-dev] [heat] No meeting this week(There will be a review meetup this week)

Dear Team Just to be clear We will host a meet up for review (as what we pickup topic for just doing review) this week. *That means we not going to hold the meeting this week.* And the purpose of doing meetup with video conference is to find a way for the team to really able to join together and

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Wed, Jul 12, 2017 at 2:04 AM, Giulio Fidente wrote: > On 07/12/2017 01:53 AM, James Slagle wrote: > >> On Tue, Jul 11, 2017 at 5:53 PM, Steve Baker wrote: >> >>> >>> > >> What would be nice is when a heat->mistral->ansible upgrade step fails, >>> the

Re: [openstack-dev] [nova] bug triage experimentation

On 07/11/2017 04:31 PM, Jeremy Stanley wrote: On 2017-07-10 07:33:28 -0400 (-0400), Sean Dague wrote: [...] Ideally storyboard would just be a lot more receptive to these kinds of things, by emitting a more native event stream, Well, there is

Re: [openstack-dev] [heat] Online video meet up this week (topic:review)

On 2017-07-12 10:24:00 +0800 (+0800), Rico Lin wrote: > 2017-07-12 2:10 GMT+08:00 Jeremy Stanley : > > > > On 2017-07-12 01:47:02 +0800 (+0800), Rico Lin wrote: > > [...] > > > we will make our meeting this week as an online video meeting > > [...] > > > > Friendly reminder: "If

Re: [openstack-dev] [all][infra] ask.o.o down and review.o.o slow

On 2017-07-12 09:58, Andreas Jaeger wrote: > On 2017-07-12 08:51, Andreas Jaeger wrote: >> FYI, ask.o.o is currently down and review.o.o is slow and needs >> investigation and possible restart. >> >> I hope an admin can help soon with these two systems, for now please >> have patience, > >

Re: [openstack-dev] [trove][all][tc] A proposal to rearchitect Trove

All: First, let me thank all of you who responded and provided feedback on what I wrote. I've summarized what I heard below and am posting it as one consolidated response rather than responding to each of your messages and making this thread even deeper. As I say at the end of this email, I will

Re: [openstack-dev] [all][infra] ask.o.o down and review.o.o slow

On 2017-07-12 08:51, Andreas Jaeger wrote: > FYI, ask.o.o is currently down and review.o.o is slow and needs > investigation and possible restart. > > I hope an admin can help soon with these two systems, for now please > have patience, review.o.o has been restarted and is ready for reviews

Re: [openstack-dev] [Glare][TC] Application for inclusion of Glare in the list of official projects

On 11/07/17 19:21 -0500, Monty Taylor wrote: On 07/11/2017 06:47 AM, Flavio Percoco wrote: On 11/07/17 14:20 +0300, Mikhail Fedosin wrote: On Tue, Jul 11, 2017 at 1:43 AM, Monty Taylor wrote: On 07/10/2017 04:31 PM, Mikhail Fedosin wrote: Third, all these changes can

[openstack-dev] [Acceleration]Cyborg Team Weekly Meeting Agenda 2017.07.12

Hi Team, We will resume our meeting this week, an initial agenda could be found at : https://wiki.openstack.org/wiki/Meetings/CyborgTeamMeeting#Agenda_for_next_meeting . Mostly we will concentrate on 1. Moving the stubs ahead 2. Discuss API framework design proposal

[openstack-dev] [all][infra] ask.o.o down and review.o.o slow

FYI, ask.o.o is currently down and review.o.o is slow and needs investigation and possible restart. I hope an admin can help soon with these two systems, for now please have patience, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5,

Re: [openstack-dev] [infra] Gerrit slow

On 2017-07-12 08:06, Gary Kotton wrote: > Hi, > > Gerrit is very slow at the moment. Is anyone else hitting this issue? Yes, we need an admin to help. Btw. read https://docs.openstack.org/infra/manual/ on how to report infra issues, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org}

[openstack-dev] [infra] Gerrit slow

Hi, Gerrit is very slow at the moment. Is anyone else hitting this issue? Thanks Gary __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On 07/12/2017 01:53 AM, James Slagle wrote: On Tue, Jul 11, 2017 at 5:53 PM, Steve Baker wrote: [...] I think its important that we allow full support for both mistral-driven and manually running playbooks. If there was no option to run ansible-playbook directly then