Re: [openstack-dev] [tacker] [hacking] [requirements] pep8 to pycodestyle

On Tue, Dec 12, 2017 at 4:37 AM, Ben Nemec wrote: > It's probably worth noting here that this is to reflect an upstream rename > from pep8 to pycodestyle, not an actual change in the library we use for > style checking. It's mentioned in the commit messages, but for

Re: [openstack-dev] [nova] Listing servers with filters and policy

+operators list On 12/11/2017 5:03 PM, Sam Morrison wrote: Hi Nova devs, I’m after some feedback on how to give “non-admin” users the ability to list instances using “admin” filters. https://review.openstack.org/#/c/526558/ Basically just trying to be able to do some finer grained

Re: [openstack-dev] [etsinfv][gap-04][blazar]: Clarification on the scope of the capacity query

Hi Gerg0 and Jay, Thanks for the replay. I just mentioned the privilege for MANO/NFVO and what they can do with the privilege as Jay said. IMO, MANO/NFVO needs the admin privileges for some operations, e.g. creating a new tenant/project for a new VNFM or migrating a VM for failure recovery.

[openstack-dev] [os-upstream-institute] Meeting on the 12th is cancelled

Hi All, I’m out of town in a time zone that doesn’t compatible with the meeting this Tuesday (Dec 12). Our highest priority item right now is to move forward with migrating content form the training guides repository over to the Contributor Portal. Please look into the tasks on StoryBoard for

Re: [openstack-dev] [keystone] keystone client service_catalog is None

Thank you Boris for the pointers! On 12/9/17, 7:07 AM, "Boris Bobrov" wrote: >Hi, > >Have a look at how openstackclient does this. Read this code: >https://github.com/openstack/python-openstackclient/blob/master/openstackc >lient/identity/v3/catalog.py#L43 >and then this

Re: [openstack-dev] [keystone] Upcoming Deadlines

Thanks Lance for a comprehensive summary. However I'm bit puzzled with application credentials spec, specifically with the sentence 'This model, while convenient for keystone, increases the risk of account compromise by requiring the distribution of unencrypted passwords.' My personal preference

[openstack-dev] [all] cyclomatic complexity check in flake8 & Python 3

We have around 60 repos using the 'mccabe' package to do cyclomatic complexity checks in flake8 in their gate jobs.[1] Based on advice received at the time[2], the version of mccabe that we use in the gate is effectively pinned to 0.2.1 by hacking (the project, not... never mind).[3] This is

Re: [openstack-dev] [nova][cinder]VolumeNotCreated: Volume did notfinish being created even after we waited 12 seconds or 5 attempts. And itsstatus is error.

Thank you ,I solved it.Because I pass a wrong parameters,lead to the problem,Thank you again! -- Original -- From: "Matt Riedemann"; Date: Mon, Dec 11, 2017 11:54 PM To: "openstack-dev"; Subject: Re:

Re: [openstack-dev] [tacker] [hacking] [requirements] pep8 to pycodestyle

It's probably worth noting here that this is to reflect an upstream rename from pep8 to pycodestyle, not an actual change in the library we use for style checking. It's mentioned in the commit messages, but for anyone just scanning the mailing list it may not be obvious. I left a review on

[openstack-dev] [nova] Listing servers with filters and policy

Hi Nova devs, I’m after some feedback on how to give “non-admin” users the ability to list instances using “admin” filters. https://review.openstack.org/#/c/526558/ Basically just trying to be able to do some finer grained permission handling as

Re: [openstack-dev] [First Contact] [OUI] Call for Project Liaisons

Pretty sure he said both!:) Amy (spotz) On Mon, Dec 11, 2017 at 4:33 PM, Kendall Nelson wrote: > Thank you Matt! > > To clarify, you want to be Project Liaison for sSwift? Or a member of the > SIG? Or both? :) > > -Kendall (diablo_rojo) > > > On Mon, Dec 11, 2017 at 2:18

Re: [openstack-dev] [keystone] Upcoming Deadlines

Sending out a gentle reminder that feature proposal freeze will be next week. It looks like all possible features are in flight based on the current state of the specs repository. The only exception is the unified limit specification, which was rebased and passing today [0]. Thanks! [0]

Re: [openstack-dev] [First Contact] [OUI] Call for Project Liaisons

Thank you Matt! To clarify, you want to be Project Liaison for sSwift? Or a member of the SIG? Or both? :) -Kendall (diablo_rojo) On Mon, Dec 11, 2017 at 2:18 PM Matthew Oliver wrote: > I'll put my hand up for my timezone. Especially as interest in my side of > the world

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

On Mon, Dec 11, 2017 at 1:20 PM, Brad P. Crochet wrote: > > > On Fri, Dec 8, 2017 at 6:35 PM Alex Schultz wrote: >> >> Hey folks, >> >> So I went through the list of blueprints and moved some that were >> either not updated or appeared to have a bunch of

Re: [openstack-dev] [First Contact] [OUI] Call for Project Liaisons

I'll put my hand up for my timezone. Especially as interest in my side of the world grows I'd love to make sure there is someone available. Project: Swift Name: Matthew Oliver IRC: mattolverau email: m...@oliver.net.au timezone: UTC +11 (AEDT) Matt On Tue, Dec 12, 2017 at 8:25 AM, Kendall

[openstack-dev] [First Contact] [OUI] Call for Project Liaisons

Hello, As some of you may know there is a newly formed SIG focused on the initial interactions of someone new to the community called the First Contact SIG. While the team we have looking out for these first introductions is growing they can only get us so far. After we get them up to speed with

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

On Fri, Dec 8, 2017 at 6:35 PM Alex Schultz wrote: > Hey folks, > > So I went through the list of blueprints and moved some that were > either not updated or appeared to have a bunch of patches not in a > mergable state. > > Please take some time to review the list of

Re: [openstack-dev] [cinder] Leaving the Cinder Core team

Scott, Very sorry to have you go.  Thank you for letting us know that you won't be able to continue participating.  It has been a pleasure to work with you over the years and hope we will continue to cross paths. Best wishes and keep in touch! Sincerely, Jay On 12/11/2017 1:11 PM, Scott

[openstack-dev] [cinder] Leaving the Cinder Core team

It is with mixed feelings that I announce my resignation from the OpenStack Cinder core reviewer team. It has been a great pleasure to watch the OpenStack project evolve over the years I have participated, and bit of sadness to move into a new role at work where I am no longer involved. After

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

> -Original Message- > From: Alex Schultz [mailto:aschu...@redhat.com] > Sent: Monday, December 11, 2017 8:31 PM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

On Fri, Dec 8, 2017 at 6:11 PM, Moshe Levi wrote: > Hi Alex, > > I don't see the tripleo ovs hardware offload feature. The spec was merge into > queens [1], but for some reason the blueprint is not in approve state [2]. > Just as a reminder it's everyone's responsibility

Re: [openstack-dev] [etsinfv][gap-04][blazar]: Clarification on the scope of the capacity query

Hi Jay, Okay. Thanks for the clarification. Makes sense. Random-thinking: Maybe the best would be to have a privilege level what covers the needs of MANO/NFVO, but still not full admin privileges. Do you think is this possible? Br, Gerg0 -Original Message- From: Jay Pipes

Re: [openstack-dev] Need advice on https://review.openstack.org/#/c/521632/

Hi - Yes, planning to keep the manifest, just removing the ping test and the > code that is dependent on that succeeding. > Would the ping test and code be suitable for a TripleO Validation? https://github.com/openstack/tripleo-validations Thanks -dant > > Uploading a new PS to reflect

Re: [openstack-dev] [tripleo] Reminder about bug priority

On Mon, Dec 11, 2017 at 5:42 PM, Emilien Macchi wrote: > A lot of bugs are set Critical or High. > Just a few reminder on how we like to use the criteria in TripleO: > > - "Critical" should be used when a bug makes a basic deployment > impossible. For example, a bug that

Re: [openstack-dev] Need advice on https://review.openstack.org/#/c/521632/

Thanks for your comments Emilien! Yes, planning to keep the manifest, just removing the ping test and the code that is dependent on that succeeding. Uploading a new PS to reflect this approach. Thanks, Sandhya On 12/11/17, 12:22 PM, "Emilien Macchi" wrote: Hi Sandhya,

Re: [openstack-dev] Need advice on https://review.openstack.org/#/c/521632/

Hi Sandhya, See inline: On Mon, Dec 11, 2017 at 8:49 AM, Sandhya Dasu (sadasu) wrote: > Hi Steven and Emilien, > > I need your advice on how to proceed with the fix in > https://review.openstack.org/#/c/521632/. > > > > The issue in question is that code in puppet-neutron

[openstack-dev] Zuul dashboard available

Hi, I'd like to draw your attention to a recently added feature in Zuul. If you visit http://zuulv3.openstack.org/ you will note three tabs at the top of the screen (you may need to shift-reload the page): Status, Jobs, Builds. The "Jobs" page shows you a list of all of the jobs in the system,

[openstack-dev] Need advice on https://review.openstack.org/#/c/521632/

Hi Steven and Emilien, I need your advice on how to proceed with the fix in https://review.openstack.org/#/c/521632/. The issue in question is that code in puppet-neutron for the Nexus switch, performs a ping test to see if all the Nexus switches specified in the configuration are actually

Re: [openstack-dev] [tripleo] Proposing Wesley Hayutin core on TripleO CI

I went ahead and added Wes part of tripleo-core, when we expect him to use +2 on tripleo-ci and tripleo-quickstart(-extras) repos. Thanks! On Mon, Dec 11, 2017 at 8:41 AM, Sagi Shnaidman wrote: > +1 > > On Wed, Dec 6, 2017 at 5:45 PM, Emilien Macchi

Re: [openstack-dev] [tripleo] Proposing Wesley Hayutin core on TripleO CI

+1 On Wed, Dec 6, 2017 at 5:45 PM, Emilien Macchi wrote: > Team, > > Wes has been consistently and heavily involved in TripleO CI work. > He has a very well understanding on how tripleo-quickstart and > tripleo-quickstart-extras work, his number and quality of reviews are >

Re: [openstack-dev] [nova][cinder]VolumeNotCreated: Volume did not finish being created even after we waited 12 seconds or 5 attempts. And its status is error.

On 12/11/2017 12:37 AM, 李杰 wrote:  Hi,all:         Now I boot a volume-backed instance,and set" block_device_allocate_retries=120 " ,but the result is still is volume did not finish being created.Can you give me some advice?Help in troubleshooting this issue will be appreciated. Have

Re: [openstack-dev] [Zun] PTL on vacation for 3 weeks

Hello, @Hongbin, Enjoy your vacation! Team, please feel free to reach me at mkrai on #openstack-zun. I am happy to serve as Zun’s temporary PTL. Regards, Madhuri From: Hongbin Lu [mailto:hongbin...@gmail.com] Sent: Friday, December 8, 2017 10:00 PM To: OpenStack Development Mailing List (not

[openstack-dev] [tripleo] Reminder about bug priority

A lot of bugs are set Critical or High. Just a few reminder on how we like to use the criteria in TripleO: - "Critical" should be used when a bug makes a basic deployment impossible. For example, a bug that affects all CI gate jobs is critical. Something that any deployment can hit is critical. A

Re: [openstack-dev] [etsinfv][gap-04][blazar]: Clarification on the scope of the capacity query

On 12/11/2017 07:24 AM, Csatari, Gergely (Nokia - HU/Budapest) wrote: Hi Masahito, Thanks for the answer. Some clarification questions. You mention that the NFVO works as both an user and an admin for the cloud. Is this becouse the resource usage per user info is more for cloud operators

Re: [openstack-dev] [neutron][l2gw] Preventing DB out-of-sync

Hi Michael, Yes, it's a similar issue but different aspect. Actually, the case for l2gw is worse, considering we have to deal with 2 existing back-end driver which have different understanding for the interfaces. But I think the proposed approach for networking-ovn is inspiring and helpful for

Re: [openstack-dev] [tripleo] The Weekly Owl - 1st Edition

On Mon, Dec 11, 2017 at 1:58 AM, Flavio Percoco wrote: > Good stuff, Emilien! > > Quick question: > > How are you collecting these updates? I know about various etherpads but I > want > to confirm that those are the source for these updates. IF not, where would > you > like me

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

Hi, Here is the status update / focus settings mail for 50 Bugs [Undecided] https://bugs.launchpad.net/nova/+bug/1535254 illustration of 'notify_on_state_change' are different from implementation The fix merged to the master and stable/pike. The stable/ocata backport has been proposed

Re: [openstack-dev] [masakari] problems starting up masakari instance monitoring in devstack @ master

I started up a VM and then deleted the VM ... and got some errors that make me think i don’t have the masakari client setup correctly. Any ideas ? Greg. i.e. stack@devstack-masakari:~/devstack$ nova list

Re: [openstack-dev] [masakari] problems starting up masakari instance monitoring in devstack @ master

Went back and started up corosync and pacemaker and now masakari-instancemonitor starts successfully. stack@devstack-masakari:~/masakari-monitors$ sudo masakari-instancemonitor & [1] 25973 stack@devstack-masakari:~/masakari-monitors$ 2017-12-11 12:47:49.483 25974 INFO masakarimonitors.service

Re: [openstack-dev] [horizon] Fetch resources in parallel

Hi Team, It's me again and I've got some new tests results [3]. I'd got the following test environment: - 3 controllers - 2 computes - 1 node with horizon - 60 items per page - 60 instances launched with only 3 different images. As always, any feedback is welcome [3]

Re: [openstack-dev] [masakari] problems starting up masakari instance monitoring in devstack @ master

Actually, i’m guessing this is wrong because masakari-instancemonitor fails to start when i use these instructions. stack@devstack-masakari:~/masakari-monitors$ sudo masakari-instancemonitor & [1] 22959 stack@devstack-masakari:~/masakari-monitors$ Traceback (most recent call last): File

[openstack-dev] [tripleo] Pike deployment times VS Ocata

This week on science confirms the obvious, containerized deployments are faster, more reliable, and scale better. Really great work everyone, TripleO deployment at 50 nodes is starting to get boring! Here's the report, comment if you find anything confusing or inaccessible.

Re: [openstack-dev] [masakari] problems starting up masakari instance monitoring in devstack @ master

Honjo, Assuming the masakari instance monitor is up and running, What is the actual USE CASE / TEST CASE for demonstrating instance monitoring ? e.g. is it ? · launch a VM · ps -ef | fgrep qemu// to find the qemu process containing the running VM · kill -9 ·

Re: [openstack-dev] [etsinfv][gap-04][blazar]: Clarification on the scope of the capacity query

Hi Masahito, Thanks for the answer. Some clarification questions. You mention that the NFVO works as both an user and an admin for the cloud. Is this becouse the resource usage per user info is more for cloud operators while the resource usage per tenant / per resource provider is more for

Re: [openstack-dev] [masakari] problems starting up masakari instance monitoring in devstack @ master

thanks Honjo, I’ll try this out now. I’m assuming that it is ok to start ONLY the instance-monitor if that’s all i want to test. Is that correct ? In that case, following the instructions you pointed me at, I would do the following: · setup devstack oi.e. with ‘enable_plugin

Re: [openstack-dev] [Neutron] Propose Slawek Kaplonski for Neutron core

Just checked this ... +1 to Slaweq ... he is a real gem to Neutron :) On Thu, Nov 30, 2017 at 12:51 AM, Miguel Lavalle wrote: > Hi Neutron Team, > > I want to nominate Slawek Kaplonski (irc: slaweq) to Neutron core. Slawek > has been an active contributor to the project

Re: [openstack-dev] [tripleo] The Weekly Owl - 1st Edition

Good stuff, Emilien! Quick question: How are you collecting these updates? I know about various etherpads but I want to confirm that those are the source for these updates. IF not, where would you like me (and others) to provide the updates so you can collect them from a single place? Thanks