Re: [openstack-dev] [nova] IBM z/VM CI asks for reporting permission to Nova changes

Thanks for your help, we have been running the CI for months and star to report to nova patches after grant the access could you please help to approve https://review.openstack.org/#/c/464915/ as we already got a +2 and please let us know anything we need to get the spec approved, thanks~ Best

[openstack-dev] [vitrage] Reminder: Vitrage virtual PTG this week

Hi, We will hold the Vitrage Queens virtual PTG this week, on October 17-19. You are welcome to join! More details can be found in the etherpad[1]. The regular weekly IRC meeting will be canceled. [1] https://etherpad.openstack.org/p/vitrage-ptg-queens Thanks, Ifat.

Re: [openstack-dev] [nova][ironic] Concerns over rigid resource class-only ironic scheduling

Hi Matt, As i understand John's spec https://review.openstack.org/#/c/507052/, it is actually a replacement for capabilities(qualitative only) for ironic. It doesnt cover the quantitative capabilities as 'traits' are meant only for qualitative capabilities. Quantitative capabilities are covered

Re: [openstack-dev] [ironic] How is the interface for tftpboot server typically configured on OVS ?

Here's an ASCII diagram[1] of the network topology on the controllers of a system we deployed earlier this year using kayobe[2]. As Sam said, we don't touch the neutron OVS bridge, in this case because it's managed entirely by kolla-ansible. Instead, we create a Linux bridge which is plugged into

[openstack-dev] [ironic] Kernel parameters needed to boot from iscsi

Hi Recently i've been helping some customers in the boot from ISCSI feature. So far everything was working, but we had a problem when booting the deployment image. It needed specifically a flag rd.iscsi.ibft=1 rd.iscsi.firmware=1 in the grub commands. But as the generated deployment image doesn't

Re: [openstack-dev] [tc][election] Question for candidates: How do you think we can make our community more inclusive?

On 15/10/17 01:26 +0100, Erno Kuvaja wrote: What we really need to focus on is to get people _wanting_ to join us. There is next to nothing easy in OpenStack with all it's complexity and that's perfectly fine. Easy is not fun, we all want to challenge ourselves. And we have amazing community to

Re: [openstack-dev] [tc][election] Question for candidates: How do you think we can make our community more inclusive?

/me waves Thanks a bunch for replying to my email. As some of you may know, this is a topic that is very close to me and I that I pay lots of attention to. There's some overlap in some of your replies and I've taken notes offline so we can work together on some of them (although I'd love to see

Re: [openstack-dev] [tc] [stable] [tripleo] [kolla] [ansible] [puppet] Proposing changes in stable policy for installers

Emilien Macchi wrote: > [...] > ## Proposal > > Proposal 1: create a new policy that fits for projects like installers. > I kicked-off something here: https://review.openstack.org/#/c/511968/ > (open for feedback). > Content can be read here: >

Re: [openstack-dev] [TripleO] containerized undercloud in Queens

On 10/3/17 10:46 PM, Dan Prince wrote: > > > This reduces our complexity greatly I think in that once it is completed > will allow us to eliminate two project (instack and instack-undercloud) > and the maintenance thereof. Furthermore, as this dovetails nice with > the Ansible >   > >  IMHO

Re: [openstack-dev] [tc] Technical Committee Status update, October 13th

Thierry Carrez wrote: > == Final call on votes == > > We need to make a final call on the Glare project team application for > the Queens cycle. If by the end of day (AOE) on Monday there is no > majority support for it, the application will be denied. So please jump > on that review if you

Re: [openstack-dev] [tripleo][networking] Organizing the networking squad

​Hi,​ On Tue, Oct 10, 2017 at 10:55 AM, Brent Eagles wrote: > Hi all, > > The list of TripleO squads includes a "networking squad". In previous > cycles, coordinating outside of IRC and email conversations seemed > unnecessary as there were only a few contributors and a

Re: [openstack-dev] [tc] [stable] [tripleo] [kolla] [ansible] [puppet] Proposing changes in stable policy for installers

Emilien, I generally thought the stable policy seemed reasonable enough for lifecycle management tools. I’m not sure what specific problems you had in TripleO although I did read your review. Kolla was just tagged with the stable policy, and TMK, we haven’t run into trouble yet, although the

Re: [openstack-dev] [tc] [stable] [tripleo] [kolla] [ansible] [puppet] Proposing changes in stable policy for installers

On 16 October 2017 at 12:27, Thierry Carrez wrote: > Emilien Macchi wrote: >> [...] >> ## Proposal >> >> Proposal 1: create a new policy that fits for projects like installers. >> I kicked-off something here: https://review.openstack.org/#/c/511968/ >> (open for feedback).

[openstack-dev] [nova] Interesting bug when unshelving an instance in an AZ and the AZ is gone

This is interesting from the user point of view: https://bugs.launchpad.net/nova/+bug/1723880 - The user creates an instance in a non-default AZ. - They shelve offload the instance. - The admin deletes the AZ that the instance was using, for whatever reason. - The user unshelves the instance

Re: [openstack-dev] [tc] [stable] [tripleo] [kolla] [ansible] [puppet] Proposing changes in stable policy for installers

On Mon, Oct 16, 2017 at 2:33 PM, Steven Dake (stdake) wrote: > Emilien, > > I generally thought the stable policy seemed reasonable enough for lifecycle > management tools. I’m not sure what specific problems you had in TripleO > although I did read your review. Kolla was

Re: [openstack-dev] [nova] Interesting bug when unshelving an instance in an AZ and the AZ is gone

On 10/16/2017 11:00 AM, Dean Troyer wrote: [not having a dog in this hunt, this is what I would expect as a cloud consumer] Thanks for the user perspective, that's what I'm looking for here, and operator perspective of course. On Mon, Oct 16, 2017 at 10:22 AM, Matt Riedemann

Re: [openstack-dev] [nova] Interesting bug when unshelving an instance in an AZ and the AZ is gone

[not having a dog in this hunt, this is what I would expect as a cloud consumer] On Mon, Oct 16, 2017 at 10:22 AM, Matt Riedemann wrote: > - The user creates an instance in a non-default AZ. > - They shelve offload the instance. > - The admin deletes the AZ that the instance

[openstack-dev] [nova] Notification update week 42

Hi, Here is the status update / focus settings mail for w42. Bugs [High] https://bugs.launchpad.net/nova/+bug/1706563 TestRPC.test_cleanup_notifier_null fails with timeou [High] https://bugs.launchpad.net/nova/+bug/1685333 Fatal Python error: Cannot recover from stack overflow. - in py35

Re: [openstack-dev] [tc][election] Question for all candidates in TC election: What will you do if you don't win?

On 10/16/2017 09:09 AM, Amrith Kumar wrote: > In a recent conversation on #openstack-tc where we bemoaned the ills > of Stackalytics and related management-by-objectives to Heisenberg's > uncertainty principle, the conversation (on 10-03, for example) veered > towards why people were interested

Re: [openstack-dev] [puppet] Proposing Alfredo Moralejo core on puppet-openstack-integration

sounds good, updating Gerrit permissions now. Thanks all, On Fri, Oct 13, 2017 at 2:09 PM, Iury Gregory wrote: > +1 > > On Oct 13, 2017 17:13, "Alex Schultz" wrote: > > +1 thanks for the great contributions > > On Fri, Oct 13, 2017 at 11:49 AM,

[openstack-dev] [neutron] Bug deputy report

Hi all, I was the bug deputy for the last week and I won't be attending today the upstream meeting so I'm sending out this report: There was one critical issue but got attention: https://bugs.launchpad.net/neutron/+bug/1722967 and just a few bugs that need attention from somebody with broader

Re: [openstack-dev] [tripleo] Repo structure for ansible-k8s-roles-* under TripleO's umbrella

On 11/10/17 07:48 +0200, Flavio Percoco wrote: On 10/10/17 10:34 -0600, Alex Schultz wrote: On Tue, Oct 10, 2017 at 5:24 AM, Flavio Percoco wrote: On 09/10/17 12:41 -0700, Emilien Macchi wrote: On Mon, Oct 9, 2017 at 2:29 AM, Flavio Percoco wrote:

Re: [openstack-dev] [tc][election] Question for candidates: How do you think we can make our community more inclusive?

Excerpts from Colleen Murphy's message of 2017-10-15 11:38:47 +0200: > On Fri, Oct 13, 2017 at 2:45 PM, Flavio Percoco wrote: > > > Greetings, > > > > Some of you, TC candidates, expressed concerns about diversity and > > inclusiveness > > (or inclusivity, depending on your

Re: [openstack-dev] [tc][election] Question for all candidates in TC election: What will you do if you don't win?

Excerpts from Amrith Kumar's message of 2017-10-15 08:15:51 -0400: > Full disclosure, I'm running for election as well. I intend to also > provide an answer to the question I pose here, one that I've posed > before on #openstack-tc in an office hours session. > > Question 1: > > "There are M

Re: [openstack-dev] [tc] [stable] [tripleo] [kolla] [ansible] [puppet] Proposing changes in stable policy for installers

On Mon, Oct 16, 2017 at 7:33 AM, Steven Dake (stdake) wrote: > Emilien, > > I generally thought the stable policy seemed reasonable enough for lifecycle > management tools. I’m not sure what specific problems you had in TripleO > although I did read your review. Kolla was

[openstack-dev] [ironic] summary of the ironic-inspector virtual sprint

Hi all, We've had a virtual sprint for ironic-inspector. Most of the time we were discussing the potential re-architecture of it. Please see https://etherpad.openstack.org/p/inspector-queens-virtual-ptg for notes and action items, and https://bluejeans.com/s/5yDpk for the recording. Dmitry

Re: [openstack-dev] [tc][election] Question for all candidates in TC election: What will you do if you don't win?

On Sun, Oct 15, 2017 at 5:15 AM, Amrith Kumar wrote: > Full disclosure, I'm running for election as well. I intend to also > provide an answer to the question I pose here, one that I've posed > before on #openstack-tc in an office hours session. > > Question 1: > > "There

Re: [openstack-dev] [tripleo][networking] Organizing the networking squad

Include me as well Brent. // Harald On 16 Oct 2017 3:41 p.m., "Saravanan KR" wrote: Thanks for initiating Brent. Yes, I would participate in the networking squad. Regards, Saravanan KR On Mon, Oct 16, 2017 at 6:43 PM, Brent Eagles wrote: > Hi, > >

Re: [openstack-dev] [ironic] ironic and traits

On 16 October 2017 at 17:55, Eric Fried wrote: > * Adding references to the specs: ironic side [1]; nova side [2] (which > just merged). > > * Since Jay is on vacation, I'll tentatively note his vote by proxy [3] > that ironic should be the source of truth - i.e. option (a).

Re: [openstack-dev] [puppet] Proposing Alfredo Moralejo core on puppet-openstack-integration

Great!, Thank you all for those words On Mon, Oct 16, 2017 at 5:21 PM, Emilien Macchi wrote: > sounds good, updating Gerrit permissions now. > > > Thanks all, > > On Fri, Oct 13, 2017 at 2:09 PM, Iury Gregory wrote: >> +1 >> >> On Oct 13, 2017 17:13,

[openstack-dev] [ptls] UPDATE: Project Onboarding Rooms

Hello Everyone :) With only a few weeks left before the summit, the Onboarding rooms have started to be published to the schedule[1]. Monday has been filled with the following teams: - Congress - Heat - Glance - Blazar - Magnum - Keystone - Barbican - Charms - QA -

Re: [openstack-dev] [ptls] Sydney Forum Project Onboarding Rooms

Added Kolla to my list. Would the speakers be you and Michal? -Kendall (diablo_rojo) On Thu, Oct 12, 2017 at 5:51 PM Jeffrey Zhang wrote: > Hi Kendall, > > Kolla project would like to have a on-boarding session too. > > thanks. > > On Fri, Oct 13, 2017 at 5:58 AM,

Re: [openstack-dev] [ptls] Sydney Forum Project Onboarding Rooms

Added Tricircle to my list :) Should be able to avoid conflicts without too much issue. -Kendall (diablo_rojo) On Thu, Oct 12, 2017 at 6:50 PM joehuang wrote: > Hello, Kendall, > > Tricircle would like to have an on-boarding session too, if there is > still time slot left

[openstack-dev] [infra][all] Stable branch jobs in Zuul v3

Hi, If you have started moving Zuul configuration into your project repos, please note the following: You will probably need to backport at least the "project" stanza to stable branches. Zuul's configuration is global; that includes configuration loaded from all branches of a project. So

Re: [openstack-dev] [TripleO] containerized undercloud in Queens

On Wed, 2017-10-04 at 15:10 +0200, Dmitry Tantsur wrote: > (top-posting, as it is not a direct response to a specific line) > > This is your friendly reminder that we're not quite near > containerized > ironic-inspector. The THT for it has probably never been tested at > all, and the > iptables

Re: [openstack-dev] [ironic] ironic and traits

* Adding references to the specs: ironic side [1]; nova side [2] (which just merged). * Since Jay is on vacation, I'll tentatively note his vote by proxy [3] that ironic should be the source of truth - i.e. option (a). I think the upshot is that it's easier for Ironic to track and resolve

Re: [openstack-dev] [docs] sitemap automation suggestions

As for logging 301s, 302s and 404s and the scope, I don't think we are interested in checking EOL content for those. As we are about to approve https://review.openstack.org/#/c/507629/, we also want everybody to understand broken links found in EOL content won't be fixed, since no content updates

Re: [openstack-dev] [tc][election] Question for all candidates in TC election: What will you do if you don't win?

In a recent conversation on #openstack-tc where we bemoaned the ills of Stackalytics and related management-by-objectives to Heisenberg's uncertainty principle, the conversation (on 10-03, for example) veered towards why people were interested in running for election to the Technical Committee.

Re: [openstack-dev] [tc] [stable] [tripleo] [kolla] [ansible] [puppet] Proposing changes in stable policy for installers

Excerpts from Emilien Macchi's message of 2017-10-13 15:02:10 -0700: > Greeting folks, > > I hope we can get attention from stable-maint, release-managers and > installers projects. > > > ## Background > > Some projects tried hard to follow stable policy but it didn't finish > well:

[openstack-dev] [TripleO] Migrating TripleO jobs to native Zuul v3

Hi, Unless you've been hiding under a rock (which is totally understandable), you know that Zuul v3 is here. Zuul v3 can be seen as a hindrance as of late because it's been messing up with the gate jobs or preventing your patches to merge, etc. Hopefully, the "legacy" Zuul v3 jobs are all fixed

[openstack-dev] [ironic] ironic and traits

Hi all, I promised John to dump my thoughts on traits to the ML, so here we go :) I see two roles of traits (or kinds of traits) for bare metal: 1. traits that say what the node can do already (e.g. "the node is doing UEFI boot") 2. traits that say what the node can be *configured* to do (e.g.

Re: [openstack-dev] [all][tc] TC Candidates: what does an OpenStack user look like?

On 14/10/17 11:47, Doug Hellmann wrote: Excerpts from Zane Bitter's message of 2017-10-13 15:21:14 -0400: Replying to myself here, to avoid singling anyone in particular out. I want to rephrase the question, because people are overwhelmingly either failing to understand or refusing to answer it

Re: [openstack-dev] [tc] [stable] [tripleo] [kolla] [ansible] [puppet] Proposing changes in stable policy for installers

On Mon, Oct 16, 2017 at 4:27 AM, Thierry Carrez wrote: > Emilien Macchi wrote: >> [...] >> ## Proposal >> >> Proposal 1: create a new policy that fits for projects like installers. >> I kicked-off something here: https://review.openstack.org/#/c/511968/ >> (open for

[openstack-dev] [forum] Schedule Is Available

Hey all, Thanks to Jimmy McArthur for getting the schedule posted so quickly! Here's the schedule posted on the Summit site filtering by forum related sessions: https://www.openstack.org/summit/sydney-2017/summit-schedule/#day=2017-11-06_groups=63 Please reply to give corrections. I will be

Re: [openstack-dev] [tc] [stable] [tripleo] [kolla] [ansible] [puppet] Proposing changes in stable policy for installers

So my 0.02$ Problem with handling Newton goes beyond deployment tools. Yes, it's popular to use, but if our dependencies (openstack services themselves) are unmaintained, so should we. If we say "we support Newton" in deployment tools, we make kind of promise we can't keep. If for example there

[openstack-dev] [ironic] this week's priorities and subteam reports

of upstream work. Reviewing it 20171016. Ansible deploy interface (pas-ha, yuiryz) - - spec: http://specs.openstack.org/openstack/ironic-specs/specs/not-implemented/ansible-deploy-driver.html - status as of 27 Sep 2017: - clean up happening while

[openstack-dev] [refstack] October 17, 2017 RefStack meeting cancelled

The October 17, 2017 RefStack meeting is cancelled. Our next team meeting will be held on October 24, 2017. -Chris __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [all][elections] Voting for the TC Election is now open

Excerpts from Kendall Nelson's message of 2017-10-15 00:12:26 +: > Hello All, > > Voting for the TC Election is now open and will remain open until 23:45 > October 20th, 2017 UTC. > > We are selecting 6 TC members, please rank all candidates in your order of > preference. > > You are

[openstack-dev] [telemetry][ceilometer] adding Hanxi Liu as ceilometer core

hi, i'd like to welcome Hanxi Liu as the newest core member of ceilometer project[1]. Just want to say thanks for the past contributions, for rep'ing us at the PTG, and for being (possibly) the only person on Earth with a Telemetry team sticker on their laptop. look forward to more. :) [1]

Re: [openstack-dev] [Swift] SPDK uses Swift as a target system to support k-v store

Sounds interesting! I'd be *very* interested to see *any* work that's been done to make use of SPDK functionality for faster or more efficient HTTP -> rotational media storage. Couple of thoughts... 1) I think the memcache or redis API would be a better target for SPDK research than Swift's

Re: [openstack-dev] [tc] [stable] [tripleo] [kolla] [ansible] [puppet] Proposing changes in stable policy for installers

Steve, I can see how #1 might be a problem in general and should be addressed in reasonable ways. For #2, I think your analysis of the tech in use is accurate and if a new policy is made it be general yet inclusive enough to permit lifecycle management tools to improve and grow. Regards

Re: [openstack-dev] [forum] Schedule Is Available

Mike, Thanks for sending this out. Long lines in descriptions of many events are not being wrapped, take Rochelle's session "Refstack: OpenStack to OPNFV, Vertical, Integrated, Interop" at 3:30pm on Wednesday. Any chance the descriptions could be wrapped? -amrith On Mon, Oct 16, 2017 at 7:43

Re: [openstack-dev] [ptls] Sydney Forum Project Onboarding Rooms

I am the speaker. Michal couldn't be Sydney this summit. On Tue, Oct 17, 2017 at 1:05 AM, Kendall Nelson wrote: > Added Kolla to my list. Would the speakers be you and Michal? > > -Kendall (diablo_rojo) > > > On Thu, Oct 12, 2017 at 5:51 PM Jeffrey Zhang

Re: [openstack-dev] [masakari]Propose changes of the core team

Oops, sorry, my previous mail didn't contain "[masakari]" tag in title. On 2017/10/16 11:34, Rikimaru Honjo wrote: Hi, On 2017/10/13 18:39, Sam P wrote: Hi All Masakari Cores,   I would like to propose following changes to Masakari core team. Current core team: Masahito Muroi Rikimaru Honjo

Re: [openstack-dev] [forum] Schedule Is Available

Hey all. That’s an issue with some of the formatting we copy/pasta’d to our scheduling tool. I’ll review all of them tomorrow to make sure that problem is remedied. Apologies for the oversight!! Jimmy > On Oct 16, 2017, at 9:28 PM, Amrith Kumar wrote: > > Mike, > >

[openstack-dev] The CI issue: “cp: cannot create regular file '/opt/stack/new/bin/etcd': Text file busy

Hi all, When I build the jobs “dsvm-tempest-full” and “dsvm-tempest-my-cinder-driver” (which are defined in openstack-dev/ci-sandbox), the error message shows in /$LOG_PATH/console.html: +/opt/stack/new/devstack-gate/devstack-vm-gate.sh:main:L753: /tmp/ansible/bin/ansible primary -f 5 -i

Re: [openstack-dev] [ironic] Kernel parameters needed to boot from iscsi

Greetings Yolanda! I guess I'm slightly not clear. In fact, I may be slightly even more confused since we've discussed this directly. Thinking out loud, there are two different scenarios of booting from iSCSI. 1) Human created/assigned/associated LUN off of a SAN which we want a node to boot

Re: [openstack-dev] [nova] Interesting bug when unshelving an instance in an AZ and the AZ is gone

On 10/16/2017 09:22 AM, Matt Riedemann wrote: 2. Should we null out the instance.availability_zone when it's shelved offloaded like we do for the instance.host and instance.node attributes? Similarly, we would not take into account the RequestSpec.availability_zone when scheduling during

[openstack-dev] [keystone] specification proposal freeze deadline

Hey all, Sending out a reminder that keystone's specification proposal freeze deadline is this week. We're still in the process of getting formal dates merged to the schedule [0], but this is roughly the same time line we use every release. Let me know if you have any questions. Thanks! [0]

Re: [openstack-dev] [tripleo][networking] Organizing the networking squad

Thanks for initiating Brent. Yes, I would participate in the networking squad. Regards, Saravanan KR On Mon, Oct 16, 2017 at 6:43 PM, Brent Eagles wrote: > Hi, > > On Tue, Oct 10, 2017 at 10:55 AM, Brent Eagles wrote: >> >> Hi all, >> >> The list of

Re: [openstack-dev] [policy] AWS IAM session

Sending out a gentle reminder to vote for time slots that work for you [0]. We'll keep the poll open for a few more days, or until we reach quorum. Thanks! [0] https://beta.doodle.com/poll/ntkpzgmcv3k6v5qu On 10/11/2017 01:48 PM, Lance Bragstad wrote: > Oh - one note about the doodle [0]. All

[openstack-dev] [oslo][blazar][heat] Remove oslotest.mockpatch

The oslotest.mockpatch has been deprecated in favor of native fixtures in [1] , need remove its usage in python-heatclient, python-blazarclient [2][3], Heat/Blazar team please help review, then we'll merge [4] [1]https://review.openstack.org/#/c/245199/