Re: [openstack-dev] [neutron][osc] Openstack client, Openstack SDK and neutronclient consistency

Excerpts from Sławek Kapłoński's message of 2016-11-16 22:36:41 +0100: > Hello, > > Few days ago someone reported bug [1] and I started checking it. I found > that when I'm trying to create QoS policy with neutronclient or OSC then > name parameter is neccessary. > But this parameter is not

[openstack-dev] [Gluon] IRC Meeting canceled on Nov 23 for Thanksgiving Holiday Week

Hello, It will be Thanksgiving Holiday week in US next week. Thus it was agreed in our IRC meeting today that our IRC meeting would be canceled next week (Nov 23). Thanks Bin __ OpenStack Development Mailing List (not for

Re: [openstack-dev] [neutron] neutron-lib impact

On 16 November 2016 at 10:11, Gary Kotton wrote: > Hi, > > I agree with you on a number of points that you have made below. But you > are mixing things up. One you state that we should be moving faster and it > is patches like this that actually hinder us. We are not moving

Re: [openstack-dev] [ironic] python-wsmanclient future

+1 -Original Message- From: Jim Rollenhagen [mailto:j...@jimrollenhagen.com] Sent: Tuesday, November 15, 2016 10:00 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [ironic] python-wsmanclient future On

[openstack-dev] [neutron] Openstack client, Openstack SDK and neutronclient consistency

Hello, Few days ago someone reported bug [1] and I started checking it. I found that when I'm trying to create QoS policy with neutronclient or OSC then name parameter is neccessary. But this parameter is not neccessary in Neutron API - I can create policy without name when calling API directly

Re: [openstack-dev] [neutron][fwaas] neutron-fwaas meeting time change

Thanks Nate. Based on further conversations and with the time change I think what we intended was: 14:00 UTC Tokyo: 11:00pm Bengaluru: 07:30pm US (EST): 09:00am US (PST): 06:00am I am fine with Mon or Tue. Thanks Sridar On 11/14/16, 12:07 PM, "Nate Johnston"

Re: [openstack-dev] [manila][cinder] [api] API and entity naming consistency

On 11/16/2016 11:28 AM, Ravi, Goutham wrote: + [api] in the subject to attract API-WG attention. We already have a guideline in the API-WG around resource names for “_” vs “-“ - https://specs.openstack.org/openstack/api-wg/guidelines/naming.html#rest-api-resource-names . With some exceptions

[openstack-dev] [nova] review priorities ocata summit session recap

The final design summit session at the Ocata summit was, as usual, the review priorities session. The full etherpad is here: https://etherpad.openstack.org/p/ocata-nova-summit-priorities Given the short cycle and restricted core reviewer bandwidth we're really only making resource providers

Re: [openstack-dev] [nova] Problem with Quota and servers spawned in groups

-- Best regards / Pozdrawiam Sławek Kapłoński sla...@kaplonski.pl On Wed, 16 Nov 2016, Chris Friesen wrote: > On 11/15/2016 06:50 PM, melanie witt wrote: > > On Tue, 15 Nov 2016 18:10:40 -0600, Chris Friesen wrote: > > > I'm in favor of your change, since the existing behaviour doesn't make >

[openstack-dev] [Gluon] IRC Meeting Time

Hello folks, Sorry to those who have missed our IRC meeting today. I should have sent a reminder that because US and Europe have changed to standard time, while our IRC meeting time is always UTC 1800, the local meeting time in US and Europe should have adjusted accordingly. Thanks Bin

Re: [openstack-dev] [kolla][kolla-ansible][kolla-kubernetes] Kolla core election policy change - vote

+1 -Ryan - Original Message - From: "Michał Jastrzębski" To: "OpenStack Development Mailing List (not for usage questions)" Sent: Wednesday, November 16, 2016 1:23:27 PM Subject: [openstack-dev]

Re: [openstack-dev] [i18n] [glance] ESL question 'shared' vs 'shareable'

Hello devs, As a Korean translator, I also quite agree with the idea. Some images with "shared" state but actually not shared yet would be awkward, and "shareable" word would cover such context : those images can be shard but may not be shared yet (although the addition of "image members"is

Re: [openstack-dev] [kolla][kolla-ansible][kolla-kubernetes] Kolla core election policy change - vote

+1 2016-11-16 16:55 GMT-03:00 Ryan Hallisey : > +1 > > -Ryan > > - Original Message - > From: "Michał Jastrzębski" > To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > Sent: Wednesday,

Re: [openstack-dev] [neutron][osc] Openstack client, Openstack SDK and neutronclient consistency

On 11/16/2016 04:03 PM, Doug Hellmann wrote: > Excerpts from Sławek Kapłoński's message of 2016-11-16 22:36:41 +0100: >> Hello, >> >> Few days ago someone reported bug [1] and I started checking it. I found >> that when I'm trying to create QoS policy with neutronclient or OSC then >> name

Re: [openstack-dev] [charms] Deploy Keystone To Public Cloud

This should work, a charm school at ODS drove this exact thing. I'll give it a try tomorrow to see if I can help. Marco On Thu, Nov 17, 2016, 12:14 AM James Beedy wrote: > I'm having an issue getting a response back (mostly timeouts occur) when > trying to talk to

[openstack-dev] [Neutron][networking-sfc] We will have networking-sfc meeting at 1700 UTC on 11/17/2016

Hi Everyone, We will cover the following topics: 1. Newton release which has been completed 2. Big Stadium assessment walk through (I think we have got all items taken care of with a few pending for Neutron driver team approval) 3. Ocata Release time line 4. Ocata

Re: [openstack-dev] [neutron][osc] Openstack client, Openstack SDK and neutronclient consistency

> Excerpts from Sławek Kapłoński's message of 2016-11-16 22:36:41 +0100: >> Hello, >> So I want to ask all of You how in Your opinion it should be solved. >> Currently there is inconsistency between CLI clients and >> API/Horizon/Openstack SDK (I checked that it is possible to create >> resource

[openstack-dev] [charms] Deploy Keystone To Public Cloud

I'm having an issue getting a response back (mostly timeouts occur) when trying to talk to keystone deployed to AWS using private (on vpn) or public ip address. I've had luck with setting os-*-hostname configs, and ssh'ing in and running the keystone/openstack client locally from the keystone

Re: [openstack-dev] [Congress] Magnum_driver

Hi Ruben, The fieldnames you care about are the fields as they show up in the JSON that gets returned from the magnum-client methods inside the datasource driver, e.g. from these methods... self.magnum.cluster_template.list() self.magnum.cluster.list() Several ways to check that you have the

[openstack-dev] [nova] ocata summit libvirt imagebackend refactor session recap

Sorry for getting behind on these, but we're nearing the finish line on summit session recaps. :) We had a design summit session to reflect a bit on what went well and what didn't go so well with the libvirt imagebackend refactor work in the Newton release, and where to go from here. The full

[openstack-dev] [QA] Meeting Thursday Nov 17th at 9:00 UTC

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

Re: [openstack-dev] [neutron][trunk-port] OVS tbr bridge wasn't be created by OVS agent

Hi, Brain Thanks for your reply. I try to build a new environment with devstack and the code from the master branch. But I meet some OVS problems. Please let me show them. I installed the devstack ( Ubuntu 14.04 and code from master branch ) successfully. But I found that OVS version is 2.0.2.

[openstack-dev]   [neutron][networking-vpp]  - networking-vpp don‘t support the latest version.

Hi, I use the devstack to install the latest version(master) to using networking-vpp. It's failed. The log here: Traceback (most recent call last): File "/usr/bin/vpp-agent", line 6, in ＜module＞ from networking_vpp.agent.server import main File

Re: [openstack-dev] [kolla][kolla-ansible][kolla-kubernetes] Kolla core election policy change - vote

On Wed, Nov 16, 2016 at 7:23 PM, Michał Jastrzębski wrote: > Hello, > > In light of recent events (kolla-kubernetes becoming thriving project, > kolla-ansible being split) I feel we need to change of core reviewer > election process. > > Currently Kolla was single core team.

[openstack-dev] [documentation]guide on new project template

Hello, Tricircle is just a new big-tent project, would like to know which documentation are necessary for the project and whether there are documentation templates. I just find this page for new project, but no clue how to organize an new project's documentation. Many thanks if someone can

Re: [openstack-dev] [nova] Problem with Quota and servers spawned in groups

On 11/17/2016 12:27 AM, Chris Friesen wrote: On 11/16/2016 03:55 PM, Sławek Kapłoński wrote: As I said before, I was testing it and I didn't have instances in Error state. Can You maybe check it once again on current master branch? I don't have a master devstack handy...will try and set one

Re: [openstack-dev] oaktree - a friendly end-user oriented API layer - anybody want to help?

>From encapsulation perspective, it's quite good for multi-steps approach to >make it being consistently with different version of image upload. Another thought about Oaktree as a service: would it be a job for Oaktree to find proper OpenStack? For the location could be varied in different

[openstack-dev] [daisycloud-core] Nominating Ya Zhou for daisycloud-core reviewer

Daisycloud-core team, I'd like to nominate Ya Zhou(IRC name 'zhouya') for daisycloud-core core reviewer. Ya started to work on Daisycloud-core since the beginning of the project and he has made significant contribution to project in last three months including adding Kolla backend,

Re: [openstack-dev] [kolla][kolla-ansible][kolla-kubernetes] Kolla core election policy change - vote

On Wed, Nov 16, 2016 at 11:53 PM, Michał Jastrzębski wrote: > Hello, > > In light of recent events (kolla-kubernetes becoming thriving project, > kolla-ansible being split) I feel we need to change of core reviewer > election process. > > Currently Kolla was single core team.

Re: [openstack-dev] 答复: [neutron][lbaasv2][octavia] Not able to create loadbalancer

Thanks a lot Michael. Recreating the amphora image with Ubuntu Trusty solved the issue for me. We are planning to add octavia on our *ansible* managed cloud, but could not find any concrete documentation.Will give it a try. Regards, Ganpat On Wed, Nov 16, 2016 at 10:20 PM, Michael Johnson

Re: [openstack-dev] [Craton] NFV planned host maintenance

On Wed, Nov 16, 2016 at 10:54 AM, Sulochan Acharya wrote: > Hi, > > On Wed, Nov 16, 2016 at 2:46 PM, Ian Cordasco > wrote: > >> -Original Message- >> From: Juvonen, Tomi (Nokia - FI/Espoo) >> Reply: OpenStack

[openstack-dev] [ironic][ironic-python-agent]code-review about this commit of numa node

Hi ironic team： I send this email to ask something about https://review.openstack.org/#/c/369245/ . This commit is about https://bugs.launchpad.net/ironic-python-agent/+bug/1622940. The jenkins has +1 for this commit.I hope you could spare some time to give me some advice of this commit.

Re: [openstack-dev] [nova] Problem with Quota and servers spawned in groups

On 11/16/2016 03:55 PM, Sławek Kapłoński wrote: As I said before, I was testing it and I didn't have instances in Error state. Can You maybe check it once again on current master branch? I don't have a master devstack handy...will try and set one up. I just tried on a stable/mitaka

Re: [openstack-dev] [kolla][kolla-ansible][kolla-kubernetes] Kolla core election policy change - vote

+1 From: Michał Jastrzębski [inc...@gmail.com] Sent: Wednesday, November 16, 2016 10:23 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [kolla][kolla-ansible][kolla-kubernetes] Kolla core election policy change

Re: [openstack-dev] oaktree - a friendly end-user oriented API layer - anybody want to help?

No Morgan. You were supposed to stay quiet on this so we could spread vial behind the scenes rumors on how Monty is trying to bring back CORBA!!! My apologies to all the young folks not familiar with CORBA... On a serious note this work has the potential to be extremely valuable and I am look

Re: [openstack-dev] oaktree - a friendly end-user oriented API layer - anybody want to help?

On Wed, Nov 16, 2016 at 9:34 AM, Monty Taylor wrote: > (there are parts of this that are hand-wavey - but how does it sound in > general?) That sounds basically good because that noise I heard last night must have been you sneaking in and stealing those steps from my white

Re: [openstack-dev] [neutron] neutron-lib impact

Hi, The directory integration will break all of the plugins and neutron projects. I do not think that this is something that we should do. It breaks the neutron API contract. I think that we should only unblock the patch https://review.openstack.org/#/c/386845. I think that due to the fact that

Re: [openstack-dev] oaktree - a friendly end-user oriented API layer - anybody want to help?

Consider that Shade/Oaktree will interact with multiple clouds, it's necessary to establish check and gate test environment for multi-clouds. This is also one requirement from Tricircle. Best Regards Chaoyi Huang (joehuang) From: Monty Taylor

Re: [openstack-dev] [Stable] Usefulness of Weekly Meeting

  -Original Message- From: Tony Breeds Reply: OpenStack Development Mailing List (not for usage questions) , OpenStack Development Mailing List (not for usage questions) Date: November 15,

Re: [openstack-dev] [api]

If you're including me as a vote for nin, you should also consider me as a vote for not_in. Otherwise, count me as half a vote for either. I still think not_in is just ever-so slightly better than nin.  -Original Message- From: milanisko k Reply: OpenStack

Re: [openstack-dev] [ironic] [stable] Proposing Jay Faulkner for ironic-stable-maint

> On Nov 16, 2016, at 08:02, Dmitry Tantsur wrote: > > Hi! > > I'm formally proposing that the ironic-stable-maint team [1] adds Jay > Faulkner. He's been consistently reviewing stable patches as shown by [2]. I > fully trust that his operator experience will help his

Re: [openstack-dev] [keystone] meeting format poll

On 2016-11-15 17:23:49 -0500 (-0500), Steve Martinelli wrote: > I don't bother with the time slider, the meeting agenda is never deleted > from the etherpad, we just keep tacking on Oh, I see, using it as an append-only log (and hope nobody erases anything or the pad doesn't spontaneously

[openstack-dev] [new][horizon] XStatic-JSEncrypt 2.3.1.0 release

We are satisfied to announce the release of: XStatic-JSEncrypt 2.3.1.0: JSEncrypt 2.3.1 (XStatic packaging standard) Download the package from: https://pypi.python.org/pypi/XStatic-JSEncrypt For more details, please see below. Changes in XStatic-JSEncrypt 2.0.0.1..2.3.1.0

Re: [openstack-dev] [all][tricircle][neutron]Tricircle now is one of OpenStack Big-Tent project

Hi, Shinobu, Team work leads the project here :) Gergely also provided use cases from OPNFV: https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2016-November/013661.html Or you can directly find it here: http://artifacts.opnfv.org/netready/docs/requirements/index.html#georedundancy Best

Re: [openstack-dev] [Stable] Usefulness of Weekly Meeting

  -Original Message- From: Ian Cordasco Reply: Ian Cordasco Date: November 16, 2016 at 07:06:27 To: OpenStack Development Mailing List (not for usage questions) Subject:  Re: [openstack-dev] [Stable]

Re: [openstack-dev] [glance] Flakey functional test (Was: [Openstack-stable-maint] Stable check of openstack/glance failed)

> Hi Glance team members, > > Over the weekend one of our stable periodic jobs failed. It failed on > a test (glance.tests.functional.test_reload.TestReload.test_reload) > that I've seen fail a couple times previously. I've created a bug for > this: https://bugs.launchpad.net/glance/+bug/1641670 

[openstack-dev] [ironic] [bifrost] Proposing Yolanda Robla-Mota and Chris Krelle to bifrost-core

Since it's creation, bifrost has valued input from users to better support their specific use cases in the community. As time has passed, we've realized the needed to grow the core team in order to improve review velocity and further diversity. To this end, I am proposing two individuals to the

Re: [openstack-dev] [glance] Flakey functional test (Was: [Openstack-stable-maint] Stable check of openstack/glance failed)

  -Original Message- From: tomislav.suk...@telekom.de Reply: OpenStack Development Mailing List (not for usage questions) Date: November 16, 2016 at 07:46:18 To: openstack-dev@lists.openstack.org

[openstack-dev] [Tacker] Unable to assign IP address to connection points.

Hi All, [Tacker] I have tried to launch the vnf Instance using Tacker. vnf is launched succesfully and able to do SSH. I have faced the issue, the connection points (CP2, CP3) are not getting ip addreess except managament CP (CP1). Could you please let me know is this Tacker issue or any

[openstack-dev] [watcher] How to verify that my strategy works well within watcher?

I had a debate with my team about how can I be sure the strategy I want to use to optimize my cluster with Watcher works well. Also, how a developer can guarantee its strategy works well? After a lot of discussions, we found a consensus: - For the unit tests, a developer should be able to

[openstack-dev] [tricircle]agenda of weekly meeting Nov.16

Hello, team, Tricircle now is one of OpenStack big-tent project, let's continue the weekly meeting. Agenda of Nov.16 weekly meeting: 1. Ocata feature development discussion 2. Documentation requirement: http://docs.openstack.org/contributor-guide/quickstart/new-projects.html 3. Open

Re: [openstack-dev] [all][tricircle][neutron]Tricircle now is one of OpenStack Big-Tent project

On Wed, Nov 16, 2016 at 6:46 PM, joehuang wrote: > Hi, Shinobu, > > Team work leads the project here :) > Indeed. Let's move on - Shinobu > > Gergely also provided use cases from OPNFV: > https://lists.opnfv.org/pipermail/opnfv-tech-discuss/ > 2016-November/013661.html

Re: [openstack-dev] [keystone] meeting format poll

On 2016-11-16 09:33:54 -0500 (-0500), Steve Martinelli wrote: [...] > As silly as it sounds, not having to log in has > made a noticeable difference -- it's not just me (or another ptl) setting > the agenda) Not silly at all, and in fact very useful feedback! I still hold out hope that once we

[openstack-dev] [nova][hyperv] hyper-v CI issues

cfriesen was asking in IRC today why this libvirt-only driver change in nova kept failing the hyper-v CI: https://review.openstack.org/#/c/346263 http://64.119.130.115/nova/346263/9/ It looks like there are a few issues: 1. The hyper-v CI doesn't appear to be testing cfriesen's change, it's

Re: [openstack-dev] [Stable] Usefulness of Weekly Meeting

On 11/16/2016 7:53 AM, Ian Cordasco wrote: -Original Message- From: Ian Cordasco Reply: Ian Cordasco Date: November 16, 2016 at 07:06:27 To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [keystone] Weekly Policy Meeting

Just sending out a reminder that we'll be having our first meeting in 90 minutes. You can find all information about our agenda in the etherpad [0] as well as a link to the hangout [1]. See you there! [0] https://etherpad.openstack.org/p/keystone-policy-meeting [1]

Re: [openstack-dev] [keystone] meeting format poll

On Wed, Nov 16, 2016 at 9:10 AM, Jeremy Stanley wrote: > On 2016-11-15 17:23:49 -0500 (-0500), Steve Martinelli wrote: > > I don't bother with the time slider, the meeting agenda is never deleted > > from the etherpad, we just keep tacking on > > Oh, I see, using it as an

Re: [openstack-dev] [Craton] NFV planned host maintenance

-Original Message- From: Juvonen, Tomi (Nokia - FI/Espoo) Reply: OpenStack Development Mailing List (not for usage questions) Date: November 11, 2016 at 02:27:19 To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [Tacker] Unable to assign IP address to connection points.

Hi Prasad: The first two things to check are: 1 - Check the VM instance in Horizon to confirm that there are three IP addresses assigned to it. If there is only one IP address assigned to the VM, check the subnet configuration for the vnf_private and private networks and make sure they

Re: [openstack-dev] [nova] Problem with Quota and servers spawned in groups

On 11/15/2016 06:50 PM, melanie witt wrote: On Tue, 15 Nov 2016 18:10:40 -0600, Chris Friesen wrote: I'm in favor of your change, since the existing behaviour doesn't make sense. But at some point I guess consistency trumps correctness, and if a new microversion is necessary to mark the new

Re: [openstack-dev] [api]

On Nov 16, 2016, at 7:42 AM, Ian Cordasco wrote: > If you're including me as a vote for nin, you should also consider me as a > vote for not_in. Otherwise, count me as half a vote for either. I still think > not_in is just ever-so slightly better than nin. It is on

Re: [openstack-dev] [neutron][dvr][fip] router support two external network

Hi thanks, this is the case what i am looking for. At 2016-11-13 19:38:57, "Irena Berezovsky" wrote: Hi, The case you are describing may be related to the previously discussed RFE [1]. Having additional networks with FIP range attached via router interface should be

[openstack-dev] [neutron]Do we need to rfe to implement active-active router?

hi Currently, neutron support DVR router and legacy router. For high availability, there is HA router in reference implementation of legacy mode and DVR mode. I am considering whether is active-active router needed in both mode?

Re: [openstack-dev] oaktree - a friendly end-user oriented API layer - anybody want to help?

On 11/15/2016 07:16 PM, Jay Pipes wrote: > Awesome start, Monty :) Comments inline. Yay - thanks Jay! > On 11/15/2016 09:56 AM, Monty Taylor wrote: >> Hey everybody! >> >> At this past OpenStack Summit the results of the Interop Challenge were >> shown on stage. It was pretty awesome - 17

Re: [openstack-dev] [glance] Flakey functional test (Was: [Openstack-stable-maint] Stable check of openstack/glance failed)

-Original Message- From: tomislav.suk...@telekom.de Reply: OpenStack Development Mailing List (not for usage questions) Date: November 16, 2016 at 09:48:40 To: openstack-dev@lists.openstack.org

[openstack-dev] [all][ptls][tc][goals] acknowledging community goals for Ocata

We still have quite a few teams who have not acknowledged the goal for Ocata. Remember, *all* teams are expected to respond, even if there is no work to be done. The most important feature of this new process is communication, which won't happen if teams don't participate. Please take a few

Re: [openstack-dev] [glance] Flakey functional test (Was: [Openstack-stable-maint] Stable check of openstack/glance failed)

> > Since there's nothing pointing to any problems here, I would just ask is > > it possible that log file is not created if there's nothing to log? > > I don't think that's possible. We start glance's services (when under test) > with debug=True and verbose=True which means the config options

[openstack-dev] [manila][cinder] API and entity naming consistency

For the moment Manila project, as well as Cinder, does have inconsistency between entity and API naming, such as: - "share type" ("volume type" in Cinder) entity has "/types/{id}" URL - "share snapshot" ("volume snapshot" in Cinder) entity has "/snapshots/{id}" URL BUT, Manila has other

Re: [openstack-dev] oaktree - a friendly end-user oriented API layer - anybody want to help?

On 11/15/2016 11:26 PM, joehuang wrote: >> Glance Image Uploads and Swift Object Uploads (and downloads). Having >> those two data operations go through an API proxy seems inefficient. >> However, having them not in the API seems like a bad user experience. >> Perhaps if we take advantage of the

[openstack-dev] [ironic] ocata summit summary

Hi all, Sorry for the late-ness of this email, but wanted to send a wrap-up of the Ocata summit from ironic's perspective. It was another super productive summit and I'm thankful for all of the people who showed up and made it so. :) As always, we discussed priorities for the cycle and those

[openstack-dev] [neutron][metadata] Is there HTTP attack issue in metadata proxy functionality offered by reference implementation?

hi Currently, nova metadata service is proxy by metadata agent in dhcp agent or l3 router agent, it is depended on whether network attach to router or not. In essential, metadata agent implements a http proxy functionality by computer node host protocal stack. In other words, it exposes

Re: [openstack-dev] [manila][cinder] API and entity naming consistency

On 11/16/2016 10:22 AM, Valeriy Ponomaryov wrote: For the moment Manila project, as well as Cinder, does have inconsistency between entity and API naming, such as: - "share type" ("volume type" in Cinder) entity has "/types/{id}" URL - "share snapshot" ("volume snapshot" in Cinder) entity has

Re: [openstack-dev] oaktree - a friendly end-user oriented API layer - anybody want to help?

On 11/16/2016 09:34 AM, Monty Taylor wrote: > On 11/15/2016 11:26 PM, joehuang wrote: >>> Glance Image Uploads and Swift Object Uploads (and downloads). Having >>> those two data operations go through an API proxy seems inefficient. >>> However, having them not in the API seems like a bad user

[openstack-dev] [i18n] [glance] ESL question 'shared' vs 'shareable'

Hello Translators, We're having a discussion about a new image "visibility" value for Glance, and before we go too far, it would be helpful to know whether what we're worried about is going to matter for ESL people. Here's the situation: Since the Diablo release, Glance end users have had the

Re: [openstack-dev] [neutron] neutron-lib impact

On 16 November 2016 at 00:55, Gary Kotton wrote: > Hi, > > The directory integration will break all of the plugins and neutron > projects. I do not think that this is something that we should do. It > breaks the neutron API contract. > The plugin directory is an

Re: [openstack-dev] [all][ptls][tc][goals] acknowledging community goals for Ocata

On Wed, Nov 16, 2016 at 9:35 AM, Doug Hellmann wrote: > We still have quite a few teams who have not acknowledged the goal for > Ocata. Remember, *all* teams are expected to respond, even if there is > no work to be done. The most important feature of this new process is >

[openstack-dev] 答复: [neutron][lbaasv2][octavia] Not able to create loadbalancer

After the amphora vm was created, the Octavia worker tried to plug VIP to the amphora vm, but failed. It could not connect to the amphora agent. You may ssh to the vm and check if the networks and ip addresses are correctly set. Good luck. -hzhao 发件人: Ganpat

[openstack-dev] [ironic] [stable] Proposing Jay Faulkner for ironic-stable-maint

Hi! I'm formally proposing that the ironic-stable-maint team [1] adds Jay Faulkner. He's been consistently reviewing stable patches as shown by [2]. I fully trust that his operator experience will help his judgment on not landing dangerous things :) So for those on the team already, please

[openstack-dev] [Congress] Magnum_driver

Hi everybody, first of all: Tim thanks for your help. I've read the code in python-magnumclient/magnumclient/v1/cluster_templates_shell.py and in python-magnumclient/magnumclient/v1/clusters_shell.py, so I've modify the translators in the magnum_driver according to

Re: [openstack-dev] [Craton] NFV planned host maintenance

Hi, On Wed, Nov 16, 2016 at 2:46 PM, Ian Cordasco wrote: > -Original Message- > From: Juvonen, Tomi (Nokia - FI/Espoo) > Reply: OpenStack Development Mailing List (not for usage questions) > > Date:

Re: [openstack-dev] [neutron][metadata] Is there HTTP attack issue in metadata proxy functionality offered by reference implementation?

On Wed, Nov 16, 2016 at 11:52 AM, Clint Byrum wrote: > > IMO the HTTP metadata service and the way it works is one of the worst > ideas we borrowed from EC2. Config drive (which I didn't like when I > first saw it, but now that I've operated clouds, I love) is a simpler > system

Re: [openstack-dev] [neutron]Do we need to rfe to implement active-active router?

On Wed, Nov 16, 2016 at 10:42 AM, huangdenghui wrote: > hi > Currently, neutron support DVR router and legacy router. For high > availability, there is HA router in reference implementation of legacy mode > and DVR mode. I am considering whether is active-active router

Re: [openstack-dev] [all][ptls][tc][goals] acknowledging community goals for Ocata

On Wed, Nov 16, 2016 at 10:21 AM, Anne Gentle wrote: > > > > On Wed, Nov 16, 2016 at 9:35 AM, Doug Hellmann > wrote: > >> We still have quite a few teams who have not acknowledged the goal for >> Ocata. Remember, *all* teams are expected to

Re: [openstack-dev] [neutron][metadata] Is there HTTP attack issue in metadata proxy functionality offered by reference implementation?

Excerpts from huangdenghui's message of 2016-11-17 00:05:39 +0800: > hi > Currently, nova metadata service is proxy by metadata agent in dhcp agent > or l3 router agent, it is depended on whether network attach to router or > not. In essential, metadata agent implements a http proxy

Re: [openstack-dev] 答复: [neutron][lbaasv2][octavia] Not able to create loadbalancer

Hi Ganpat, FYI, we are on freenode IRC: #openstack-lbaas if you would like to chat interactively. So, I see the amp is expecting systemd, which probably means you are using a "master" version of diskimage-builder with a stable/newton version of Octavia. On November 2nd, they switched

Re: [openstack-dev] 答复: [neutron][lbaasv2][octavia] Not able to create loadbalancer

Here are the steps i followed 1. Created a LB stack@devstack-openstack:~/devstack$ neutron lbaas-loadbalancer-list +--+--+-+-+--+ | id | name | vip_address | provisioning_status |

Re: [openstack-dev] [neutron][lbaasv2][octavia] Not able to create loadbalancer

Hi Ganpat, Yes, as hzhao mentioned, this error means that the controller was unable to connect to the amphora over the management network. Please check that this section is properly setup: http://docs.openstack.org/developer/octavia/guides/dev-quick-start.html#load-balancer-network-configuration

Re: [openstack-dev] [manila][cinder] [api] API and entity naming consistency

+ [api] in the subject to attract API-WG attention. We already have a guideline in the API-WG around resource names for “_” vs “-“ - https://specs.openstack.org/openstack/api-wg/guidelines/naming.html#rest-api-resource-names . With some exceptions (like share_instances that you mention), I see

Re: [openstack-dev] [i18n] [glance] ESL question 'shared' vs 'shareable'

On Wed, Nov 16, 2016 at 04:04:52PM +, Brian Rosmaita wrote: > Hello Translators, > > We're having a discussion about a new image "visibility" value for Glance, > and before we go too far, it would be helpful to know whether what we're > worried about is going to matter for ESL people. > >

[openstack-dev] [app-catalog] App Catalog IRC meeting Thursday November 17th

Join us tomorrow (Thursday) for our weekly meeting, scheduled for November 17th at 17:00UTC in #openstack-meeting-3 The agenda can be found here, and please add to if you want to discuss something with the Community App Catalog team: https://wiki.openstack.org/wiki/Meetings/app-catalog Now that

Re: [openstack-dev] [keystone] Weekly Policy Meeting

We had some issues using Hangouts because we hit the maximum limit of attendees. To make it so that everyone could participate equally, we moved the meeting to #openstack-keystone [0]. I have an action item to propose an official meeting to the irc-meetings repository. Patch for the meeting is

Re: [openstack-dev] [neutron] neutron-lib impact

Hi, I agree with you on a number of points that you have made below. But you are mixing things up. One you state that we should be moving faster and it is patches like this that actually hinder us. We are not moving as the core team is dwindling down and people are leaving the project. We need

Re: [openstack-dev] [keystone] Weekly Policy Meeting

May I could suggest another action item? I think we need clear use cases. What policy and authorization capabilities are users expecting keystone to have? What are the short-comings of the implementation we have today? On Wed, Nov 16, 2016 at 1:06 PM, Lance Bragstad wrote:

[openstack-dev] [kolla][kolla-ansible][kolla-kubernetes] Kolla core election policy change - vote

Hello, In light of recent events (kolla-kubernetes becoming thriving project, kolla-ansible being split) I feel we need to change of core reviewer election process. Currently Kolla was single core team. That is no longer the case, as right now we have 3 distinct core teams (kolla, kolla-ansible

Re: [openstack-dev] [kolla] Kolla-ansible is available

I think some kolla-kubernetes folks will still want to use kolla genconfig. Not sure it really does need the ansible dependency though. if the dep is removed, it may be better to put it in the kolla repo then the kolla-ansible repo. Thanks, Kevin From: Jeffrey

Re: [openstack-dev] [all] important changes to pep8 python jobs

On Thu, Nov 03, 2016 at 12:29:09PM -0400, Paul Belanger wrote: > Greetings, > > We (openstack-infra) are proposing a change to the current pep8[1] job for > python jobs, and would like to bring your attention to it. > > We'll be removing the extra-index-url field from pip.conf which forces the

Re: [openstack-dev] [api]

Guys, thanks for the responses, so far we've got (if I'm not mistaken): ?state=nin: 3 (including me) ?state=not_in: 1 ?state=out: 0 ?not_state=in: 0 I'd like to finish this poll by EOW so that more folks have the opportunity to express their preference. Cheers, milan 2016-11-15 13:50