Re: [openstack-dev] [neutron] Newton Midcycle - Tuesday dinner

Hi John, We will be able to accommodate 15+, as need be. See you all then. Regards, Martin From: John Schwarz To: "OpenStack Development Mailing List (not for usage questions)" Date: 14/08/2016 13:50 Subject:[openstack-dev] [neutron] Newton Midcycle - Tuesday di

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-15 12:56 GMT+08:00 Yingxin Cheng : > Hi, > > I'm concerned with the dependencies between "os-capabilities" library and > all the other OpenStack services such as Nova, Placement, Ironic, etc. > > Rather than embedding the universal "os-capabilities" in Nova, Cinder, > Glance, Ironic servic

Re: [openstack-dev] [cinder][drivers] Backend and volume health reporting

On Sun, Aug 14, 2016 at 5:53 PM, John Griffith wrote: > > ​I'd like to get a more detailed use case and example of a problem you > want to solve with this. I have a number of concerns including those I > raised in your "list manageable volumes" proposal.​ Most importantly > there's really no cle

Re: [openstack-dev] [all][tc][ptl] establishing project-wide goals

Doug Hellmann wrote: > [...] > Choosing to be a part of a community comes with obligations as well > as benefits. If, after a lengthy discussion of a community-wide > goal, involving everyone in the community, a project team is > resolutely opposed to the goal, does that not indicate that the > ne

Re: [openstack-dev] [tc][cinder] tag:follows-standard-deprecation should be removed

Sean Dague wrote: > On 08/12/2016 01:10 PM, Walter A. Boring IV wrote: >> I believe there is a compromise that we could implement in Cinder that >> enables us to have a deprecation >> of unsupported drivers that aren't meeting the Cinder driver >> requirements and allow upgrades to work >> without

[openstack-dev] [tripleo] Testing optional composable services in the CI

Hi everyone, happy Monday :) I'd like to start the discussion about CI-testing the optional composable services in the CI (I'm primarily interested in Ironic, but I know there are a lot more). Currently every time we change something in an optional service, we have to create a DO-NOT-MERGE p

Re: [openstack-dev] [nova][cinder][oslo] Lets move forward on making oslo.privsep logging more sane

Matt Riedemann wrote: > [...] > I think we could approve Angus' and maybe iterate/improve on it later > for what Walter wants, which is making oslo.privsep logging more > configurable like processutils so the caller can get the captured > stdout/stderr and decide what to do with it. +2ed (the solu

[openstack-dev] [mistral] Team meeting reminder - 08/15/2016

Hi, This is a reminder that we’ll have a team meeting today at #openstack-meeting at 16.00 UTC. Agenda: * Review action items * Current status (progress, issues, roadblocks, further plans) * Open discussion Dawid Deja

[openstack-dev] [nova][vitrage] host evacuate

Hi, In Vitrage project[1], I would like to add an option to call nova host-evacuate for a failed host. I noticed that there is an api for ‘nova evacuate’, and a cli (but no api) for ‘nova host-evacuate’. Is there a way that I can call 'nova host-evacuate’ from Vitrage code? Did you consider add

[openstack-dev] [neutron][networking-sfc] Unable to create openstack SFC

Hi all, I'm trying to launch Openstack SFC as explained in[1] by creating 2 SFs, 1 Web Server (DST) and the DHCP namespace as the SRC. I've installed OVS (Open vSwitch) 2.3.90 with Linux kernel 3.13.0-62 and the neutron L2-agent runs correctly. I followed the process by creating classifier, port pa

Re: [openstack-dev] [cinder] [nova] locking concern with os-brick

On 08/14/2016 06:23 PM, Patrick East wrote: > I like the sound of a more unified way to interact with compute node > services. Having a standardized approach for inter-service > synchronization for controlling system resources would be sweet (even if > it is just a more sane way of using local fil

Re: [openstack-dev] [Openstack-operators] [cinder] [nova] locking concern with os-brick

On 08/13/2016 06:07 PM, Matt Riedemann wrote: > > I checked a tempest-dsvm CI run upstream and we don't follow this > recommendation for our own CI on all changes in OpenStack, so before we > make this note in the release notes, I'd like to see us use the same > lock_path for c-vol and n-cpu in d

Re: [openstack-dev] [Neutron][networking-ovn]NAT and external network in OVN

Hi Chandra, thanks for your help. How can I configure nat by ovn api(ovn-nbctl/ovn-sbctl) as https://github.com/openvswitch/ovs/blob/master/tutorial/OVN-Tutorial.md ? or through openstack api(networking-ovn) ? Regards, Wilence On Wed, Aug 10, 2016 at 2:34 PM, Chandra Vejendla < chandra.vejen..

[openstack-dev] [vitrage] reference a type of alarm in template

I have a question on how to reference a type of alarm in template so that we can build scenarios. In the template sample [1], an alarm entity has three keys: `category`, `type` and `template_id`. It seems `type` is the only information to distinguish different alarms. However, when an alarm is rai

[openstack-dev] [Nova][API] Need naming suggestions for "capabilities"

Currently in Nova we're discussion adding a "capabilities" API to expose to users what actions they're allowed to take, and having compute hosts expose "capabilities" for use by the scheduler. As much fun as it would be to have the same term mean two very different things in Nova to retain some sem

[openstack-dev] [new][bandit] Release 1.1.0 (httpoxy, important fixes)

Hi folks, New bandit release 1.1.0 has been tagged. Importantly, this includes a security fix for a bug[1] in HTML formatted reports that could permit XSS. [New Features] - New test for HTTPoxy bug (CVE-2016-5386) - Man page added [Bug Fixes] - XSS bug fixed in HTML output (Security fix) - Vari

Re: [openstack-dev] [neutron][networking-ovs-dpdk] conntrack security group driver with ovs-dpdk

+ Jakub. On Wed, Aug 10, 2016 at 9:54 AM, wrote: > Hi, >> [Mooney, Sean K] >> In ovs 2.5 only linux kernel conntrack was supported assuming you had a 4.x >> kernel that supported it. that means that the feature was not available on >> bsd,windows or with dpdk. > Yup, I also thought about somethi

Re: [openstack-dev] [Nova][API] Need naming suggestions for "capabilities"

On 08/15/2016 09:27 AM, Andrew Laski wrote: Currently in Nova we're discussion adding a "capabilities" API to expose to users what actions they're allowed to take, and having compute hosts expose "capabilities" for use by the scheduler. As much fun as it would be to have the same term mean two ve

Re: [openstack-dev] [Nova][API] Need naming suggestions for "capabilities"

On Mon, Aug 15, 2016 at 8:27 AM, Andrew Laski wrote: > An API "capability" is going to be an action, or URL, that a user is > allowed to use. So "boot an instance" or "resize this instance" are > capabilities from the API point of view. Whether or not a user has this > capability will be determin

Re: [openstack-dev] [Nova][API] Need naming suggestions for "capabilities"

On Mon, Aug 15, 2016 at 9:33 AM, Jay Pipes wrote: > On 08/15/2016 09:27 AM, Andrew Laski wrote: > >> After some thought, I think I've changed my mind on referring to the >> adjectives as "capabilities" and actually think that the term >> "capabilities" is better left for the policy-like things. >

Re: [openstack-dev] [cinder] [nova] locking concern with os-brick

On 08/14/2016 06:23 PM, Patrick East wrote: > I like the sound of a more unified way to interact with compute node > services. Having a standardized approach for inter-service > synchronization for controlling system resources would be sweet (even if > it is just a more sane way of using local fil

Re: [openstack-dev] [Kuryr] Overlay MTU setup in docker remote driver

Hi Kuryr team, I open an issue in docker-libnetwork: https://github.com/docker/libnetwork/issues/1390 Appreciate for any idea or comments. Thanks. Regards, Liping Mao On 16/8/12 下午4:08, "Liping Mao (limao)" wrote: >Hi Kuryr team, > >When the network in neutron using overlay for vm, >it will

Re: [openstack-dev] [neutron] OVO Status Dashboard

Thanks Victor, This is a nice way to track the work. If this is going to replace the etherpad[1] then can I suggest including links to reviews in place of the In Progress/Done text for each entry? The color coding will preserve the completion status. John [1] https://etherpad.openstack.org/p/new

Re: [openstack-dev] [Nova][API] Need naming suggestions for "capabilities"

On 08/15/2016 10:50 AM, Dean Troyer wrote: On Mon, Aug 15, 2016 at 9:33 AM, Jay Pipes mailto:jaypi...@gmail.com>> wrote: On 08/15/2016 09:27 AM, Andrew Laski wrote: After some thought, I think I've changed my mind on referring to the adjectives as "capabilities" and actually

Re: [openstack-dev] [nova] Possible REST API design change for get-me-a-network (2.37)

On 8/11/2016 6:26 PM, Andrew Laski wrote: On Thu, Aug 11, 2016, at 06:54 PM, Chris Friesen wrote: On 08/11/2016 03:53 PM, Matt Riedemann wrote: I wanted to bring this up for awareness since we're getting close to feature freeze and want consensus before it gets too late. Ken'ichi brought up

Re: [openstack-dev] [nova] Possible REST API design change for get-me-a-network (2.37)

On 8/15/2016 10:37 AM, Matt Riedemann wrote: On 8/11/2016 6:26 PM, Andrew Laski wrote: On Thu, Aug 11, 2016, at 06:54 PM, Chris Friesen wrote: On 08/11/2016 03:53 PM, Matt Riedemann wrote: I wanted to bring this up for awareness since we're getting close to feature freeze and want consensus

Re: [openstack-dev] [Nova][API] Need naming suggestions for "capabilities"

> -Original Message- > From: Jay Pipes [mailto:jaypi...@gmail.com] > Sent: Monday, August 15, 2016 3:34 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [Nova][API] Need naming suggestions for > "capabilities" > > On 08/15/2016 09:27 AM, Andrew Laski wrote: > > C

[openstack-dev] [neutron][l2gw]Idea of redundant L2GW

Hi, I want to connect VXLAN segments to VLAN segments using a L2GW, and I want the L2GW to be redundant which is achieved by two or more baremetals. Is there some ideas for that? Or should I use STP/RSTP on OpenvSwitches? Regard, Eigo _

Re: [openstack-dev] [cinder] [nova] locking concern with os-brick

Sean Dague wrote: On 08/14/2016 06:23 PM, Patrick East wrote: We were talking through some of the implications of this change in #openstack-nova, and the following further concerns came out. 1) Unix permissions for services in distros Both Ubuntu and RHEL have a dedicated service user per ser

Re: [openstack-dev] [Nova][API] Need naming suggestions for "capabilities"

Excerpts from Jay Pipes's message of 2016-08-15 10:33:49 -0400: > On 08/15/2016 09:27 AM, Andrew Laski wrote: > > Currently in Nova we're discussion adding a "capabilities" API to expose > > to users what actions they're allowed to take, and having compute hosts > > expose "capabilities" for use by

[openstack-dev] [Puppet] Puppet OpenStack Application Module

I'd like to propose the creation of a puppet module to make use of Puppet Application orchestrator. This would consist of a Puppet-4 compatible module that would define applications that would wrap the existing modules. This will allow for the establishment of a shared module that is capable of ex

Re: [openstack-dev] [Nova][API] Need naming suggestions for "capabilities"

On 08/15/2016 12:01 PM, Doug Hellmann wrote: Excerpts from Jay Pipes's message of 2016-08-15 10:33:49 -0400: On 08/15/2016 09:27 AM, Andrew Laski wrote: Currently in Nova we're discussion adding a "capabilities" API to expose to users what actions they're allowed to take, and having compute hos

Re: [openstack-dev] [nova][vitrage] host evacuate

On 8/15/2016 4:24 AM, Afek, Ifat (Nokia - IL) wrote: Hi, In Vitrage project[1], I would like to add an option to call nova host-evacuate for a failed host. I noticed that there is an api for ‘nova evacuate’, and a cli (but no api) for ‘nova host-evacuate’. Is there a way that I can call 'nova

Re: [openstack-dev] [Nova][API] Need naming suggestions for "capabilities"

A fast reply where others will expand further (I hope): > On Aug 15, 2016, at 9:01 AM, Doug Hellmann wrote: > >> My vote is the following: >> >> GET /capabilities <-- returns a set of *actions* or *abilities* that the >> user is capable of performing > > Does this relate in any way to how Def

Re: [openstack-dev] [Nova][API] Need naming suggestions for "capabilities"

Excerpts from Jim Meyer's message of 2016-08-15 09:37:36 -0700: > A fast reply where others will expand further (I hope): > > > On Aug 15, 2016, at 9:01 AM, Doug Hellmann wrote: > > > >> My vote is the following: > >> > >> GET /capabilities <-- returns a set of *actions* or *abilities* that the

[openstack-dev] [ci-cd] Jenkinsfile support (or repo/s for them?)

Hi folks, I've been experimenting/investigating/playing around with the 'new' jenkins pipeline support (see https://jenkins.io/doc/pipeline/ for those who don't know what this is) and it got me thinking that there are probably X other people/groups/companies that are doing the same thing and

Re: [openstack-dev] [infra] Jenkinsfile support (or repo/s for them?)

On 16-08-15 01:19 PM, Joshua Harlow wrote: Hi folks, I've been experimenting/investigating/playing around with the 'new' jenkins pipeline support (see https://jenkins.io/doc/pipeline/ for those who don't know what this is) and it got me thinking that there are probably X other people/groups/c

Re: [openstack-dev] [infra] Jenkinsfile support (or repo/s for them?)

Much appreciated! -Josh Anita Kuno wrote: I suggest using the [infra] tag in the subject line if you are looking for input from the infra team. I have changed it for my reply. Thanks, Anita. __ OpenStack Development Mai

Re: [openstack-dev] [infra] Jenkinsfile support (or repo/s for them?)

Also for anyone requiring an example (with slack integration) of one of these: http://paste.openstack.org/show/557601/ The above is my WIP experiment for nova (I am new to groovy and this stuff, so it might be not *ideal* code, ha). Joshua Harlow wrote: Hi folks, I've been experimenting/in

Re: [openstack-dev] [ironic] Driver composition defaults call

Hi Julia, Thanks for discussing with Sam and sending out this email. I like the 5 steps described below! --ruby On 2016-08-11, 1:37 PM, "Julia Kreger" mailto:juliaashleykre...@gmail.com>> wrote: Yesterday as a group (jroll, rloo, dtantsur, matt128, devananda, vdrok, and myself) discussed defa

[openstack-dev] [neutron][networking-sfc] Unable to create openstack SFC

Please use the following configuration devstack: stable/mitakanetworking-sfc: masterLinux kerenl:     3.19.8   (if you have a multi-node setup).OVS:                2.4+ Weekly IRC meeting information is atMeetings/ServiceFunctionChainingMeeting - OpenStack | | | | ||

Re: [openstack-dev] [ironic] Driver composition defaults call

On 08/11/2016 10:37 AM, Julia Kreger wrote: > Yesterday as a group (jroll, rloo, dtantsur, matt128, devananda, > vdrok, and myself) discussed defaults for driver composition. > > The options we discussed were: > > * The existing specification[0] - Global and hardware_type > default_FOO_interfac

Re: [openstack-dev] [vitrage] reference a type of alarm in template

Hi, The "type" means where it was generated - aodh, vitrage, nagios... I think you are looking for"name", a field that describes the actual problem. We should add that to our documentation to clarify. Sent from Nine From: Yujun Zhang S

[openstack-dev] [Infra] Meeting Tuesday August 16th at 19:00 UTC

Hi everyone, The OpenStack Infrastructure (Infra) team is having our next weekly meeting on Tuesday August 16th, at 19:00 UTC in #openstack-meeting Meeting agenda available here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting Anyone is welcome to to add agenda

[openstack-dev] [Ceilometer] Newbie question regarding Ceilometer notification plugin

We are trying to develop a program which can draw the VMs topology. For this we need to listen VM creation/deletion event and act upon it. I would think Ceilometer is the right place for this. So I download and read Ceilometer a little bit. If somebody can give me a pointer to where I can start

Re: [openstack-dev] [ci-cd] Jenkinsfile support (or repo/s for them?)

On 08/15/2016 01:19 PM, Joshua Harlow wrote: Hi folks, I've been experimenting/investigating/playing around with the 'new' jenkins pipeline support (see https://jenkins.io/doc/pipeline/ for those who don't know what this is) and it got me thinking that there are probably X other people/groups/co

[openstack-dev] [new][openstack] osc-lib 1.0.1 release (newton)

We are tickled pink to announce the release of: osc-lib 1.0.1: OpenStackClient Library This release is part of the newton release series. With source available at: https://git.openstack.org/cgit/openstack/osc-lib With package available at: https://pypi.python.org/pypi/osc-lib Please

[openstack-dev] [ironic] weekly subteam status report

Hi, Here is this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === - Stats (diff between 1 Aug 2016 and 15 Aug 2016) - Ironic: 232 bugs (+16) + 199 wishlist items (-5). 36 new (+15), 160 in progress,

Re: [openstack-dev] [ci-cd] Jenkinsfile support (or repo/s for them?)

I've been experimenting/investigating/playing around with the 'new' jenkins pipeline support (see https://jenkins.io/doc/pipeline/ for those who don't know what this is) and it got me thinking that there are probably X other people/groups/companies that are doing the same thing and that to me

[openstack-dev] [new][oslo] oslo.db 4.7.1 release (mitaka)

We are psyched to announce the release of: oslo.db 4.7.1: Oslo Database library This release is part of the mitaka stable release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.db With package available at: https://pypi.python.org/pypi/oslo.db Please r

Re: [openstack-dev] [neutron] Neutron Port MAC Address Uniqueness

Hi, My (original) question regarding the uniqueness of Neutron port MAC addresses didn't concern SR-IOV support or vendor NICs. It was simply about the behavior w.r.t. virtual networks. I believe Armando has confirmed what I had been suspecting. Thanks, Anil -Original Message- From: M

Re: [openstack-dev] [Nova][API] Need naming suggestions for "capabilities"

On Mon, Aug 15, 2016, at 10:33 AM, Jay Pipes wrote: > On 08/15/2016 09:27 AM, Andrew Laski wrote: > > Currently in Nova we're discussion adding a "capabilities" API to expose > > to users what actions they're allowed to take, and having compute hosts > > expose "capabilities" for use by the schedul

[openstack-dev] [nova][keystone] auth for new metadata plugins

Review https://review.openstack.org/#/c/317739/ added a new dynamic metadata handler to nova. The basic jist is that rather than serving metadata statically, it can be done dyamically, so that certain values aren't provided until they are needed, mostly for security purposes (like credentials t

Re: [openstack-dev] [ci-cd] Jenkinsfile support (or repo/s for them?)

On 08/15/2016 02:47 PM, Joshua Harlow wrote: >> With nodepool and Zuul, there's simply no purpose to Jenkins any more >> for me. > > Fair point, and no disagreement on that effort being good and all; > though I can't quite say what companies that do use jenkins (the > majority?) are supposed to d

Re: [openstack-dev] [ci-cd] Jenkinsfile support (or repo/s for them?)

On 08/15/2016 03:47 PM, Joshua Harlow wrote: I've been experimenting/investigating/playing around with the 'new' jenkins pipeline support (see https://jenkins.io/doc/pipeline/ for those who don't know what this is) and it got me thinking that there are probably X other people/groups/companies

Re: [openstack-dev] [nova] os-capabilities library created

On 08/15/2016 12:56 AM, Yingxin Cheng wrote: Hi, I'm concerned with the dependencies between "os-capabilities" library and all the other OpenStack services such as Nova, Placement, Ironic, etc. Rather than embedding the universal "os-capabilities" in Nova, Cinder, Glance, Ironic services that w

Re: [openstack-dev] [nova] os-capabilities library created

On 08/15/2016 03:57 AM, Alex Xu wrote: 2016-08-15 12:56 GMT+08:00 Yingxin Cheng mailto:yingxinch...@gmail.com>>: Hi, I'm concerned with the dependencies between "os-capabilities" library and all the other OpenStack services such as Nova, Placement, Ironic, etc. Rather than

Re: [openstack-dev] [ci-cd] Jenkinsfile support (or repo/s for them?)

Sure, I get your point. Disagree that it's not a worthy effort to want to rid the world of impossible-to-reason-about CI configurations, but I get your point. I'm more of in disagreement that running two systems that are sorta similar is worthy (2 things to maintain, support, operate...), no

Re: [openstack-dev] [ci-cd] Jenkinsfile support (or repo/s for them?)

Monty Taylor wrote: On 08/15/2016 02:47 PM, Joshua Harlow wrote: With nodepool and Zuul, there's simply no purpose to Jenkins any more for me. Fair point, and no disagreement on that effort being good and all; though I can't quite say what companies that do use jenkins (the majority?) are supp

[openstack-dev] [puppet] weekly meeting #90

Hi Puppeteers! We'll have our weekly meeting tomorrow at 3pm UTC on #openstack-meeting-4 Here's a first agenda: https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160816 Feel free to add topics, and any outstanding bug and patch. See you tomorrow! Thanks, --

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-16 7:31 GMT+08:00 Jay Pipes : > On 08/15/2016 03:57 AM, Alex Xu wrote: > >> 2016-08-15 12:56 GMT+08:00 Yingxin Cheng > >: >> >> >> Hi, >> >> I'm concerned with the dependencies between "os-capabilities" >> library and all the other OpenStack servi

Re: [openstack-dev] [daisycloud-core] Daisy installer demo is out

Hello Zhijiang, I hit the following issue when trying to run 'installdaisy_el7_noarch.bin' No package httpd available. Error: Nothing to do Failed to issue method call: No such file or directory Failed to issue method call: Unit httpd.service failed to load: No such file or directory. httpd start

[openstack-dev] [glance] Last store and client releases for Newton

Hi all, It's that time in the release cycle when we need to wrap things up. The non-client libraries are lined up to be released for final version in R-6 and the client one along with n-3 in R-5. However, these libraries need some time to be tested in gate and for us to determine a stable versi

Re: [openstack-dev] [all][tc][ptl] establishing project-wide goals

On 15 Aug 2016, at 1:37, Thierry Carrez wrote: > Doug Hellmann wrote: >> [...] >> Choosing to be a part of a community comes with obligations as well >> as benefits. If, after a lengthy discussion of a community-wide >> goal, involving everyone in the community, a project team is >> resolutely

Re: [openstack-dev] [Kuryr] Overlay MTU setup in docker remote driver

Hi Kuryr team, I just notice, this can be fixed in kuryr bind code. I submit a bug to track this: https://bugs.launchpad.net/kuryr-libnetwork/+bug/1613528 And patch sets are here: https://review.openstack.org/#/c/355712/ https://review.openstack.org/#/c/355714/ Thanks. Regards, Liping Mao On 1

[openstack-dev] [nova][SR-IOV] PCI/SR-IOV meeting today is canceled 08/16/16

Sorry for the late mail, but I won't be able to chair the meeting today __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.op

Re: [openstack-dev] [nova][vitrage] host evacuate

On 15/08/2016, 19:29, "Matt Riedemann" wrote: >On 8/15/2016 4:24 AM, Afek, Ifat (Nokia - IL) wrote: >> Hi, >> >> In Vitrage project[1], I would like to add an option to call nova >> host-evacuate for a failed host. I noticed that there is an api for ‘nova >> evacuate’, and a cli (but no ap

Re: [openstack-dev] [Nova][API] Need naming suggestions for "capabilities"

> On Aug 15, 2016, at 10:49 AM, Doug Hellmann wrote: > > Excerpts from Jim Meyer's message of 2016-08-15 09:37:36 -0700: >> A fast reply where others will expand further (I hope): >> >>> On Aug 15, 2016, at 9:01 AM, Doug Hellmann wrote: >>> My vote is the following: GET /capab

Re: [openstack-dev] [OpenStack-docs] [Magnum] Using common tooling for API docs

Hi Anne, AFAIK, the API WG adopted Swagger (OpenAPI) as common tool for API docs. Anne, has not the adoption been changed? Otherwise, do we need to maintain much RST files also? IMO, for that the reference and the source code doesn't have conflict, these should be near each other as possible as