Re: [openstack-dev] [nova] About live-resize spec

ok, thanks, I will pick up and get Claudiu's help as well, the original spec is abandoned ,could you please help to restore it? Best Regards! Kevin (Chen) Ji 纪 晨 Engineer, zVM Development, CSTL Notes: Chen CH Ji/China/IBM@IBMCN Internet: jiche...@cn.ibm.com Phone: +86-10-82451493 Address: 3/F

Re: [openstack-dev] [nova][api] why need PUT /servers/{server_id}/metadata/{key} ?

yes, I didn't go to that detail and missed the delete flag , that's exactly what I am looking for, which is a little bit confusing... Thanks for the info for know this... Best Regards! Kevin (Chen) Ji 纪 晨 Engineer, zVM Development, CSTL Notes: Chen CH Ji/China/IBM@IBMCN Internet:

Re: [openstack-dev] [tc][nova][mogan] How to show respect to the original authors?

Excerpts from Michael Still's message of 2017-09-20 10:25:17 -0600: > Dims, I'm not sure that's actually possible though. Many of these files > have been through rewrites and developed over a large number of years. > Listing all authors isn't practical. > > Given the horse has bolted on forking

[openstack-dev] [QA] Meeting Thursday Sept 21st at 8:00 UTC

Hello everyone, Please reminder that the weekly OpenStack QA team IRC meeting will be Thursday, Sept 21st at 8:00 UTC in the #openstack-meeting channel. The agenda for the meeting can be found here:

[openstack-dev] [neutron] This week drivers meeting

Hi Neutrinos, We will cancel this week's drivers meeting. We will resume normally next week, on September 28th Best regards Miguel __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [infra] Unable to add member to Zun core team

Hi Infra team, I tried to add Kien Nguyen kie...@vn.fujitsu.com to the Zun's core team [1], but gerrit prevented me to do that. Attached file showed the error. Could anyone provide suggestion for this? Best regards, Hongbin [1]

[openstack-dev] [Mogan]Tasks update of Mogan Project

Hi, We are glad to present this week's tasks update of Mogan. See the details below: Essential Priorities == 1. Adopt servers (wanghao, litao) blueprint: https://blueprints.launchpad.net/mogan/+spec/manage-existing-bms spec: https://review.openstack.org/#/c/459967/ merged code:

[openstack-dev] [Blazar] PTG recap

Hi all, This is a summary of Queens PTG discussion for Blazar. We had lots of items in the meeting. So I write down main topics in the mail. If you're interested in all items, please see the queens PTG etherpad page[1]. Priorities for Queens cycle --- We discussed

Re: [openstack-dev] [vitrage] Extending Topology

Dear Ifat, Usman is here. Previously, I contacted you for contributing to OpenStack Vitrage project but could not follow up with you for sometime due to various reasons. However, to get actively involved in OpenStack project, I have decided to join OpenStack Summit in Sydney. Also, based on my

[openstack-dev] [neutron] team ptg photos

https://photos.app.goo.gl/Aqa51E2aVkv5b4ah1 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [ptg] Simplification in OpenStack

Wading in a bit late as I've been off-list for a while, but I have thoughts here. Excerpts from Jay Pipes's message of 2017-09-13 13:44:55 -0400: > On 09/12/2017 06:53 PM, Boris Pavlovic wrote: > > Mike, > > > > Great intiative, unfortunately I wasn't able to attend it, however I > > have some

Re: [openstack-dev] [all] review.openstack.org downtime and Gerrit upgrade TODAY 15:00 UTC - 23:59 UTC

On Mon, Sep 18, 2017, at 04:58 PM, Clark Boylan wrote: > On Mon, Sep 18, 2017, at 06:43 AM, Andreas Jaeger wrote: > > Just a friendly reminder that the upgrade will happen TODAY, Monday > > 18th, starting at 15:00 UTC. The infra team expects that it takes 8 > > hours, so until 2359 UTC. > > This

[openstack-dev] question about OpenStack Python glance API -- list share image by tenant.

Deal all I have a question about the openstack python glance client api I want to get the list of all the shared image by tenant , but don't know how to get the list.. I can only find out this, list sharing, but when i use tenant, it did not work, showed some error "No tenant_id"

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

Excerpts from Tony Breeds's message of 2017-09-20 17:18:51 -0400: > On Wed, Sep 20, 2017 at 04:51:21PM -0400, Doug Hellmann wrote: > > Excerpts from Jeremy Stanley's message of 2017-09-20 18:59:50 +: > > > On 2017-09-20 14:46:32 -0400 (-0400), Tony Breeds wrote: > > > [...] > > > > I'd like to

Re: [openstack-dev] [tc][nova][mogan] How to show respect to the original authors?

On 20 Sep 2017, at 9:25, Michael Still wrote: > Dims, I'm not sure that's actually possible though. Many of these files > have been through rewrites and developed over a large number of years. > Listing all authors isn't practical. > > Given the horse has bolted on forking these files, I feel

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

On Wed, Sep 20, 2017 at 04:51:21PM -0400, Doug Hellmann wrote: > Excerpts from Jeremy Stanley's message of 2017-09-20 18:59:50 +: > > On 2017-09-20 14:46:32 -0400 (-0400), Tony Breeds wrote: > > [...] > > > I'd like to find a solution that doesn't need a tox_install.sh > > [...] > > > > This

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

Excerpts from Jeremy Stanley's message of 2017-09-20 18:59:50 +: > On 2017-09-20 14:46:32 -0400 (-0400), Tony Breeds wrote: > [...] > > I'd like to find a solution that doesn't need a tox_install.sh > [...] > > This wart came up when discussing Zuul v3 job translations... what > would be

[openstack-dev] [docs][i18n][ptg] Denver PTG Summary for Docs (and i18n)

Hi all, Just wanted to share a few notes and a brief summary of what happened in Denver last week, during the Project Team Gathering, in docs and i18n shared sessions. We had a fairly good attendance of 5 to 15 ppl during the first two days. A number of people primarily working on other projects

Re: [openstack-dev] [neutron] MTU native ovs firewall driver

Since OVS is doing L2 forwarding, you should be fine setting the MTU to as high as you choose, which would probably be the segment_mtu in the config, since that's what it defines - the largest MTU that (from the Neutron API perspective) is usable and (from the OVS perspective) will be used in the

[openstack-dev] [ansible][kayobe][kolla] Announcing the availability of kayobe 2.0.0 and 3.0.0

Hi, I am pleased to announce the availability of not one, but two releases of kayobe[1]. Both provide numerous enhancements over previous releases. Kayobe 2.0.0 is based on the Ocata OpenStack release, and Kayobe 3.0.0 on Pike. Please see the release notes[2] for further information. A bit about

Re: [openstack-dev] [nova] Is there any reason to exclude originally failed build hosts during live migration?

On Wed, Sep 20, 2017 at 10:15 PM, melanie witt wrote: > On Wed, 20 Sep 2017 13:47:18 -0500, Matt Riedemann wrote: > >> Presumably there was a good reason why the instance failed to build on a >> host originally, but that could be for any number of reasons: resource >> claim

[openstack-dev] [nova] Pike 16.0.1 bug fix release proposed

FYI, I've got a release proposed for Pike 16.0.1: https://review.openstack.org/#/c/505796/ This includes several bug fixes for regressions introduced in 16.0.0. A lot of these have to do with properly making allocations in Placement or cleaning up allocations from Placement during move

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

On 2017-09-20 15:19:47 -0400 (-0400), Tony Breeds wrote: > On Wed, Sep 20, 2017 at 06:59:50PM +, Jeremy Stanley wrote: > > On 2017-09-20 14:46:32 -0400 (-0400), Tony Breeds wrote: > > [...] > > > I'd like to find a solution that doesn't need a tox_install.sh > > [...] > > > > This wart came

Re: [openstack-dev] [nova] Is there any reason to exclude originally failed build hosts during live migration?

On Wed, 20 Sep 2017 13:47:18 -0500, Matt Riedemann wrote: Presumably there was a good reason why the instance failed to build on a host originally, but that could be for any number of reasons: resource claim failed during a race, configuration issues, etc. Since we don't really know what

Re: [openstack-dev] [nova] Is there any reason to exclude originally failed build hosts during live migration?

On 09/20/2017 12:47 PM, Matt Riedemann wrote: I wanted to bring it up here in case anyone had a good reason why we should not continue to exclude originally failed hosts during live migration, even if the admin is specifying one of those hosts for the live migration destination. Presumably

Re: [openstack-dev] [ovs-announce] CFP for OpenStack Open Source Days Sydney

On Wed, Sep 20, 2017 at 3:21 PM, Ben Pfaff wrote: > In May, the OpenStack Summit graciously offered Open vSwitch use of a > room for a day of talks, and it worked out great. For the OpenStack > Summit in Sydney, which will be held Nov. 6-8, they've again offered us > time for Open

[openstack-dev] [magnum] issue with admin_osc.keystone().trustee_domain_id

We are in the process of integrating MAGNUM into our OpenStack distribution. We are working with NEWTON version of MAGNUM. We have the MAGNUM processes up and running and configured. However we are seeing the following error (see stack trace below) on virtually all MAGNUM CLI calls. The code

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

On Wed, Sep 20, 2017 at 06:59:50PM +, Jeremy Stanley wrote: > On 2017-09-20 14:46:32 -0400 (-0400), Tony Breeds wrote: > [...] > > I'd like to find a solution that doesn't need a tox_install.sh > [...] > > This wart came up when discussing Zuul v3 job translations... what > would be ideal is

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

On 2017-09-20 14:46:32 -0400 (-0400), Tony Breeds wrote: [...] > I'd like to find a solution that doesn't need a tox_install.sh [...] This wart came up when discussing Zuul v3 job translations... what would be ideal is if someone has the bandwidth to work upstream in tox to add a constraints file

Re: [openstack-dev] [skip-level-upgrades][fast-forward-upgrades] PTG summary

On 09/20/2017 02:25 PM, Doug Hellmann wrote: Excerpts from Dan Smith's message of 2017-09-20 10:09:54 -0700: - Modify the `supports-upgrades`[3] and `supports-accessible-upgrades`[4] tags I have yet to look into the formal process around making changes to these tags but I will aim to

[openstack-dev] [nova] Is there any reason to exclude originally failed build hosts during live migration?

It's a weird question, so I'll explain. An issue came up in IRC today where someone was trying to live migrate an instance to a specified host, and the RetryFilter in the scheduler was kicking out the specified host, even though other similar instances were live migrating to that specified

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

On Wed, Sep 20, 2017 at 02:24:32PM -0400, Doug Hellmann wrote: > That solves the problem of having the constraints file disappear after > the EOL, but it doesn't really solve the problem of having to update the > branches every time we open one. Having tox_install.sh figure out the > URL from the

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

On 2017-09-20 14:37:27 -0400 (-0400), Doug Hellmann wrote: > Excerpts from Jeremy Stanley's message of 2017-09-20 18:35:23 +: > > On 2017-09-20 14:24:32 -0400 (-0400), Doug Hellmann wrote: > > [...] > > > it doesn't really solve the problem of having to update the > > > branches every time we

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

On Wed, Sep 20, 2017 at 02:09:15PM -0400, Tony Breeds wrote: > On Wed, Sep 20, 2017 at 01:43:51PM -0400, Tony Breeds wrote: > > > The solution I thought we decide on at the PTG is: > > * Add a post job to all branches that publish a constraints/$series.txt > >to $server (I don't mind if it's

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

Excerpts from Jeremy Stanley's message of 2017-09-20 18:35:23 +: > On 2017-09-20 14:24:32 -0400 (-0400), Doug Hellmann wrote: > [...] > > it doesn't really solve the problem of having to update the > > branches every time we open one. Having tox_install.sh figure out > > the URL from the

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

On 2017-09-20 14:24:32 -0400 (-0400), Doug Hellmann wrote: [...] > it doesn't really solve the problem of having to update the > branches every time we open one. Having tox_install.sh figure out > the URL from the .gitreview file addresses that, but it may be too > magic for some folks. I don't

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

On 17-09-20 13:43:51, Tony Breeds wrote: > On Wed, Sep 20, 2017 at 01:08:45PM -0400, Doug Hellmann wrote: > > Excerpts from Jeremy Stanley's message of 2017-09-20 13:36:38 +: > > > On 2017-09-20 08:41:14 -0400 (-0400), Doug Hellmann wrote: > > > [...] > > > > Is there any reason not to use the

Re: [openstack-dev] [skip-level-upgrades][fast-forward-upgrades] PTG summary

Excerpts from Dan Smith's message of 2017-09-20 10:09:54 -0700: > >> - Modify the `supports-upgrades`[3] and `supports-accessible-upgrades`[4] > >> tags > >> > >>I have yet to look into the formal process around making changes to > >>these tags but I will aim to make a start ASAP. > > >

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

Excerpts from Tony Breeds's message of 2017-09-20 13:43:51 -0400: > On Wed, Sep 20, 2017 at 01:08:45PM -0400, Doug Hellmann wrote: > > Excerpts from Jeremy Stanley's message of 2017-09-20 13:36:38 +: > > > On 2017-09-20 08:41:14 -0400 (-0400), Doug Hellmann wrote: > > > [...] > > > > Is there

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

On Wed, Sep 20, 2017 at 01:43:51PM -0400, Tony Breeds wrote: > The solution I thought we decide on at the PTG is: > * Add a post job to all branches that publish a constraints/$series.txt >to $server (I don't mind if it's releases.o.o or tarballs.o.o). Actually we might be better to do this

[openstack-dev] [all][charms][fuel][Packaging-Deb] Remove old numeric branches

Hello all, Now we have cleaned up some of the older series based branches I've taken a look at some of the numeric based branches. The projects in $subject are particularly impacted. I've made my best guess at which branches are current, but I'd really appreciate guidance on the life span of

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

On Wed, Sep 20, 2017 at 01:08:45PM -0400, Doug Hellmann wrote: > Excerpts from Jeremy Stanley's message of 2017-09-20 13:36:38 +: > > On 2017-09-20 08:41:14 -0400 (-0400), Doug Hellmann wrote: > > [...] > > > Is there any reason not to use the published files for all regular > > > builds,

Re: [openstack-dev] [TripleO] TripleO/Ansible PTG session

On Tue, Sep 19, 2017 at 8:37 AM, Giulio Fidente wrote: > On 09/18/2017 05:37 PM, James Slagle wrote: >> - The entire sequence and flow is driven via Mistral on the Undercloud >> by default. This preserves the API layer and provides a clean reusable >> interface for the CLI

Re: [openstack-dev] [skip-level-upgrades][fast-forward-upgrades] PTG summary

- Modify the `supports-upgrades`[3] and `supports-accessible-upgrades`[4] tags I have yet to look into the formal process around making changes to these tags but I will aim to make a start ASAP. We've previously tried to avoid changing assert tag definitions because we then have to

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

Excerpts from Jeremy Stanley's message of 2017-09-20 13:36:38 +: > On 2017-09-20 08:41:14 -0400 (-0400), Doug Hellmann wrote: > [...] > > Is there any reason not to use the published files for all regular > > builds, instead of having tox.ini point to a git URL? Maybe only for > > regular

Re: [openstack-dev] [skip-level-upgrades][fast-forward-upgrades] PTG summary

Excerpts from Lee Yarwood's message of 2017-09-20 14:29:12 +0100: > My thanks again to everyone who attended and contributed to the > skip-level upgrades track over the first two days of last weeks PTG. > I've included a short summary of our discussions below with a list of > agreed actions for

Re: [openstack-dev] [neutron] MTU native ovs firewall driver

On Wed, Sep 20, 2017 at 9:33 AM, Ajay Kalambur (akalambu) wrote: > So I was forced to explicitly set the MTU on br-int > ovs-vsctl set int br-int mtu_request=9000 > > > Without this the tap device added to br-int would get MTU 1500 > > Would this be something the ovs l2 agent

Re: [openstack-dev] [neutron] MTU native ovs firewall driver

So I was forced to explicitly set the MTU on br-int ovs-vsctl set int br-int mtu_request=9000 Without this the tap device added to br-int would get MTU 1500 Would this be something the ovs l2 agent can handle since it creates the bridge? Ajay On 9/20/17, 7:28 AM, "Ajay Kalambur (akalambu)"

Re: [openstack-dev] [tc][nova][mogan] How to show respect to the original authors?

Dims, I'm not sure that's actually possible though. Many of these files have been through rewrites and developed over a large number of years. Listing all authors isn't practical. Given the horse has bolted on forking these files, I feel like a comment acknowledging the original source file is

Re: [openstack-dev] [all] dashboard query changes since upgrade

Excerpts from Sean Dague's message of 2017-09-19 09:35:26 -0400: > On 09/19/2017 09:00 AM, Sean Dague wrote: > > I've been iterating through gerrit dashboards this morning trying to > > figure out why they no longer show any changes. > > > > It looks like the query: label:Code-Review>=-2,self now

Re: [openstack-dev] [ironic] [ironic-ui] Proposing Anup Navare (anupn) for ironic-ui-core

++ I think Anup would be a great addition to the core team :) Thank you for all your contributions! Beth > On 20 Sep 2017, at 01:16, Julia Kreger wrote: > > Greetings fellow stackers! > > I would like to propose adding Anup Navare to ironic-ui-core. Anup has >

Re: [openstack-dev] [zun][unit test] Any python utils can collect pci info?

Hi Eric, Thanks for pointing this out. This BP (https://blueprints.launchpad.net/zun/+spec/use-privsep) was created to track the introduction of privsep. Best regards, Hongbin > -Original Message- > From: Eric Fried [mailto:openst...@fried.cc] > Sent: September-18-17 10:51 AM > To:

[openstack-dev] [openstack-ansible] Meeting Cancelled 9/21

Just wanted to let everyone know we will be cancelling the IRC meeting on 9/21 Thanks, Amy (spotz) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [all] Marking <= mitaka EOL

On Wed, Sep 20, 2017 at 11:23:07AM -0400, Tony Breeds wrote: > On Wed, Sep 20, 2017 at 08:39:56PM +1000, Joshua Hesketh wrote: > > Hi All, > > > > I've processed the list that Tony sent through this morning, removing the > > branches and tagging their positions as described. > > Thanks Josh! >

Re: [openstack-dev] [ironic] [ironic-ui] Proposing Anup Navare (anupn) for ironic-ui-core

Thank you Julia for proposing me for the ironic-ui-core team. Anup -Original Message- From: Julia Kreger [mailto:juliaashleykre...@gmail.com] Sent: Tuesday, September 19, 2017 5:16 PM To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [all][QA][group-based-policy][zaqar][packaging_deb][fuel][networking-*] Marking <= mitaka EOL

On Wed, Sep 20, 2017 at 12:56:07PM +0200, Andreas Jaeger wrote: > So, for fuel we have stable/7.0 etc - what are the plans for these? Can > we retire them as well? > > Those are even older AFAIK, As discussed on IRC, when I started this I needed to start with something small and simple, so I

Re: [openstack-dev] [all] Marking <= mitaka EOL

On Wed, Sep 20, 2017 at 08:39:56PM +1000, Joshua Hesketh wrote: > Hi All, > > I've processed the list that Tony sent through this morning, removing the > branches and tagging their positions as described. Thanks Josh! > The only exception being that openstack/zaqar doesn't have stable/liberty

[openstack-dev] [glance] upcoming spec-related deadlines

Hello Glance Community, We came up with a fairly aggressive roadmap for Queens, particularly given Glance's current personnel situation. Thus, it's unlikely that much more can be added, and thus, we can freeze spec proposals early to eliminate distractions. So here are the relevant deadlines:

Re: [openstack-dev] [glance] Queens PTG: Thursday summary

Hi Belmiro, Thanks for the feedback about the "hidden" property. To push this along, would you mind reading through this patch and the comments on it and responding? Or if you think it's close to a working proposal, you could grab the text, revise, make Fei Long a co-author, and propose it for

Re: [openstack-dev] [skip-level-upgrades][fast-forward-upgrades] PTG summary

Lee, I can chair meeting in Sydney. Thanks, Arkady -Original Message- From: Lee Yarwood [mailto:lyarw...@redhat.com] Sent: Wednesday, September 20, 2017 8:29 AM To: openstack-dev@lists.openstack.org; openstack-operat...@lists.openstack.org Subject: [openstack-dev]

Re: [openstack-dev] [skip-level-upgrades][fast-forward-upgrades] PTG summary

Lee, I can chair meeting in Sydney. Thanks, Arkady -Original Message- From: Lee Yarwood [mailto:lyarw...@redhat.com] Sent: Wednesday, September 20, 2017 8:29 AM To: openstack-dev@lists.openstack.org; openstack-operat...@lists.openstack.org Subject: [openstack-dev]

[openstack-dev] [neutron] MTU native ovs firewall driver

Hi i am using large mtu setting of 9000. with the hybrid firewall driver i see large mtu set on both tap devices and the linuxbridges While i switch from ovs hybrid firewall driver to native ovs firewall driver i now see the tap device gets the default 1500 mtu i have the right setting for mtu

[openstack-dev] [publiccloud-wg] PublicCloud WG Meetup at OpenStack Days UK next week

Hi folks, Just a quick heads-up. We have a planning meeting scheduled for the new OpenStack Passport Program at the OpenStack Days UK conference in London next week. When: 26th September, 2017 @ 2pm Where: Etc Venues, Bishopsgate 155, London @ Bishopsgate Room 1. We're planning to outline

Re: [openstack-dev] [nova][api] why need PUT /servers/{server_id}/metadata/{key} ?

On 9/20/2017 8:33 AM, Alex Xu wrote:  is there any use-case that people update server's metadata such frequently? If you have automation tooling updating the metadata for whatever reason it could be a problem. This was the reported bug FWIW: https://bugs.launchpad.net/nova/+bug/1650188

Re: [openstack-dev] [sahara] PTG Summary

Thanks Telles - we all appreciate your leadership which was conducive to a very productive PTG. Another exciting point to highlight is more community visibility and involvement regarding Sahara's plugins: 1) Plugin upgrades tied to a release milestone visible on the official release schedule

[openstack-dev] [ironic] code patches & bugs

Hi, Just a reminder to make sure that if you are submitting a code patch to fix something that could be apparent to our users, that it should be considered a bug (or a feature). Which means that there should be a launchpad bug [1] associated with it, and a release note. I know we've been

[openstack-dev] [tripleo] Deploy Keystone, Glance and Mariadb in Kubernetes with TripleO

Hey Folks, I just posted a screencast sharing the progress I've made on the kubernetes effort[0]. I've pasted part of the blog post below in case you want to discuss some parts of it. What if I want to play with it? === Here's a small recap of what's needed to play

Re: [openstack-dev] [all] pypy broken for many repos

On 2017-09-18 22:44, Sean McGinnis wrote: > On Sun, Sep 17, 2017 at 08:32:00AM +0200, Andreas Jaeger wrote: >> Currently we use pypy for a couple of projects and many of these fail >> with the version of pypy that we use. >> >> A common error is "Pypy fails with "RuntimeError: cryptography 1.9 is

[openstack-dev] [sahara] PTG Summary

Hello Saharan's and interested folks, this past week we had our PTG at Denver and it was a very productive one, with so many discussions and too much to do after that. In the next lines I will describe a little of the main decisions made by the Sahara team. Pike Retrospective

Re: [openstack-dev] [tc][nova][mogan] How to show respect to the original authors?

On 20/09/17 12:21 +, Jeremy Stanley wrote: On 2017-09-20 07:51:29 -0400 (-0400), Davanum Srinivas wrote: [...] please indicate which file from Nova, so if anyone wanted to cross check for fixes etc can go look in Nova [...] While the opportunity has probably passed in this case, the ideal

Re: [openstack-dev] [devstack] Why do we apt-get install NEW files/debs/general at job time ?

On 2017-09-20 15:17:28 +0200 (+0200), Attila Fazekas wrote: [...] > The image building was the good old working solution and unless > the image build become a super expensive thing, this is still the > best option. [...] It became a super expensive thing, and that's the main reason we stopped

Re: [openstack-dev] [nova][api] why need PUT /servers/{server_id}/metadata/{key} ?

On Wed, Sep 20, 2017 at 10:14 PM, Matt Riedemann wrote: > On 9/20/2017 12:48 AM, Chen CH Ji wrote: >> >> in analyzing other code, found seems we don't need PUT >> /servers/{server_id}/metadata/{key} ? >> >> as the id is only used for check whether it's in the body and we will

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

On 2017-09-20 08:41:14 -0400 (-0400), Doug Hellmann wrote: [...] > Is there any reason not to use the published files for all regular > builds, instead of having tox.ini point to a git URL? Maybe only for > regular builds off of stable branches? I'm not sure what you mean by "regular builds" but

Re: [openstack-dev] [nova][api] why need PUT /servers/{server_id}/metadata/{key} ?

2017-09-20 21:14 GMT+08:00 Matt Riedemann : > On 9/20/2017 12:48 AM, Chen CH Ji wrote: > >> in analyzing other code, found seems we don't need PUT >> /servers/{server_id}/metadata/{key} ? >> >> as the id is only used for check whether it's in the body and we will >> honor the

[openstack-dev] [skip-level-upgrades][fast-forward-upgrades] PTG summary

My thanks again to everyone who attended and contributed to the skip-level upgrades track over the first two days of last weeks PTG. I've included a short summary of our discussions below with a list of agreed actions for Queens at the end. tl;dr s/skip-level/fast-forward/g

Re: [openstack-dev] [devstack] Why do we apt-get install NEW files/debs/general at job time ?

On Wed, Sep 20, 2017 at 3:11 AM, Ian Wienand wrote: > On 09/20/2017 09:30 AM, David Moreau Simard wrote: > >> At what point does it become beneficial to build more than one image per >> OS >> that is more aggressively tuned/optimized for a particular purpose ? >> > > ... and

Re: [openstack-dev] [nova][api] why need PUT /servers/{server_id}/metadata/{key} ?

On 9/20/2017 12:48 AM, Chen CH Ji wrote: in analyzing other code, found seems we don't need PUT /servers/{server_id}/metadata/{key} ? as the id is only used for check whether it's in the body and we will honor the whole body (body['meta'] in the code)

Re: [openstack-dev] [nova][api] why need PUT /servers/{server_id}/metadata/{key} ?

On Wed, Sep 20, 2017 at 2:48 PM, Chen CH Ji wrote: > in analyzing other code, found seems we don't need PUT > /servers/{server_id}/metadata/{key} ? > > as the id is only used for check whether it's in the body and we will honor > the whole body (body['meta'] in the code) >

Re: [openstack-dev] [nova] About live-resize spec

On 9/20/2017 12:16 AM, Chen CH Ji wrote: spec [1] has been there since 2014 and some patches proposed but abandoned after that, can someone please provide some info/background about why it's postponed or due to some limitations that nova hasn't been implemented yet? some operators suggested

Re: [openstack-dev] [docs][ptls][install] Install guide vs. tutorial

On 9/19/2017 4:57 PM, Sean McGinnis wrote: On 9/19/17, 2:43 PM, "Eric Fried" wrote: Alex- Regardless of what the dictionary might say, people associate the word "Tutorial" with a set of step-by-step instructions to do a thing. "Guide" would be

Re: [openstack-dev] [nova] [notification] not transforming HostAPI related versioned notifications

On 9/20/2017 4:06 AM, Balazs Gibizer wrote: Do you feel we need something more user facing documentations about these decisions? No, this is fine. Thanks for explaining. -- Thanks, Matt __ OpenStack Development Mailing

Re: [openstack-dev] [docs][ptls][install] Install guide vs. tutorial

Excerpts from Sean McGinnis's message of 2017-09-19 16:57:40 -0500: > > > On 9/19/17, 2:43 PM, "Eric Fried" wrote: > > > > > > Alex- > > > > > > Regardless of what the dictionary might say, people associate the > > > word > > > "Tutorial" with a set of

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

Excerpts from Jeremy Stanley's message of 2017-09-20 12:30:59 +: > On 2017-09-20 07:11:51 -0500 (-0500), Matthew Thode wrote: > > On 17-09-20 13:35:44, Michal Pryc wrote: > > > EOL releases for the nova component (checked neutron as well, > > > possibly many other components) have wrong

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

On 2017-09-20 07:11:51 -0500 (-0500), Matthew Thode wrote: > On 17-09-20 13:35:44, Michal Pryc wrote: > > EOL releases for the nova component (checked neutron as well, > > possibly many other components) have wrong pointers to the > > upper-constraints.txt files as they are referencing > >

Re: [openstack-dev] [tc][nova][mogan] How to show respect to the original authors?

On 2017-09-20 07:51:29 -0400 (-0400), Davanum Srinivas wrote: [...] > please indicate which file from Nova, so if anyone wanted to cross > check for fixes etc can go look in Nova [...] While the opportunity has probably passed in this case, the ideal method is to start with a Git fork of the

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

On 17-09-20 13:35:44, Michal Pryc wrote: > Hi, > > EOL releases for the nova component (checked neutron as well, possibly many > other components) have wrong pointers to the upper-constraints.txt files as > they are referencing stable/branch rather then branch-eol, see example: > >

[openstack-dev] [charms] PTG summary

Hi All Here’s a summary of the charm related discussion from PTG last week. # Cross Project Discussions ## Skip Level Upgrades This topic was discussed at the start of the week, in the context of supporting upgrades across multiple OpenStack releases for operators. What was immediately

Re: [openstack-dev] [tc][nova][mogan] How to show respect to the original authors?

Zhenguo, Thanks for bringing this up. For #1, yes please indicate which file from Nova, so if anyone wanted to cross check for fixes etc can go look in Nova For #2, When you pick up a commit from Nova, please make sure the commit message in Mogan has the following * The gerrit change id(s) of

[openstack-dev] EOL tags and upper-constraints.txt in tox.ini

Hi, EOL releases for the nova component (checked neutron as well, possibly many other components) have wrong pointers to the upper-constraints.txt files as they are referencing stable/branch rather then branch-eol, see example: https://github.com/openstack/nova/blob/liberty-eol/tox.ini#L12

Re: [openstack-dev] [all] review.openstack.org downtime and Gerrit upgrade TODAY 15:00 UTC - 23:59 UTC

On Wed, Sep 20, 2017 at 12:00 PM Paul Bourke wrote: > I had the following bookmark: > > status:open is:mergeable (project:openstack/kolla OR > project:openstack/kolla-ansible) NOT label:Code-Review>=-2,self NOT > owner:pauldbourke NOT age:1month branch:master > > Which

Re: [openstack-dev] [all] review.openstack.org downtime and Gerrit upgrade TODAY 15:00 UTC - 23:59 UTC

I had the following bookmark: status:open is:mergeable (project:openstack/kolla OR project:openstack/kolla-ansible) NOT label:Code-Review>=-2,self NOT owner:pauldbourke NOT age:1month branch:master Which basically means, find changes that are: * open * in kolla or kolla-ansible * not

Re: [openstack-dev] [all][QA][group-based-policy][zaqar][packaging_deb][fuel][networking-*] Marking <= mitaka EOL

On 2017-08-24 05:14, Tony Breeds wrote: > Hello all, > We have a number of old stable/* branches hanging around and I'd > like to mark anything <= stable/mitaka as EOL. I've highlighted a few > projects on the subject line: > > QA: Are the older branches of grenade safe to go? IIUC we don't

Re: [openstack-dev] [all] Marking <= mitaka EOL

Hi All, I've processed the list that Tony sent through this morning, removing the branches and tagging their positions as described. The only exception being that openstack/zaqar doesn't have stable/liberty or stable/liberty2 branches to EOL. Let me know if I've missed anything. Cheers, Josh

[openstack-dev] [acceleration]Cyborg Team Meeting 2017.09.20

Hi Team, We will resume our weekly meeting today, altho it might be a pretty laid back one considering we just finished PTG last week. Agenda could be found here [0] as usual [0] https://wiki.openstack.org/wiki/Meetings/CyborgTeamMeeting -- Zhipeng (Howard) Huang Standard Engineer IT Standard

Re: [openstack-dev] [glance] Queens PTG: Thursday summary

Hi Brian, as we discussed in the past the image lifecycle has been a problem for us for a long time. However, I have some concerns in adding/maintaining a new project only to help the image discovery. At CERN we have a small set of images that we maintain and offer as "public" images to

Re: [openstack-dev] [tripleo] Install Kubernetes in the overcloud using TripleO

On 20.9.2017 10:15, Bogdan Dobrelya wrote: On 08.06.2017 18:36, Flavio Percoco wrote: Hey y'all, Just wanted to give an updated on the work around tripleo+kubernetes. This is still far in the future but as we move tripleo to containers using docker-cmd, we're also working on the final goal,

[openstack-dev] [mogan] Weekly meeting canceled this week

Hello team, I'll cancel tomorrow's IRC meeting due to the virtual PTG this Friday. See you all on next meeting! -- Best Regards, Zhenguo Niu __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [neutron][oslo.messaging][femdc]Topic names for every resource type RPC endpoint

I wrote those lines. At that time, I tried a couple a publisher and a receiver at that scale. It was the receiver side what crashed trying to subscribe, the sender was completely fine. Sadly I don't keep the test examples, I should have stored them in github or something. It shouldn't be hard to

Re: [openstack-dev] [nova] [notification] not transforming HostAPI related versioned notifications

On Wed, Sep 20, 2017 at 2:37 AM, Matt Riedemann wrote: On 9/19/2017 10:35 AM, Balazs Gibizer wrote: > Hi, > > Similar to my earlier mail about not transforming legacy notifications > in the networking area [1] now I want to propose not to transform > HostAPI related

[openstack-dev] [tc][nova][mogan] How to show respect to the original authors?

Hi all, I'm from Mogan team, we copied some codes/frameworks from Nova since we want to be a Nova with a bare metal specific API. About why reinventing the wheel, you can find more informations here [1]. I would like to know what's the decent way to show our respect to the original authors we

  1   2   >