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

On Wed, Nov 16, 2016 at 9:10 AM, Fox, Kevin M wrote: > whats the plan for genconfig? its based on ansible right now, but may fit > better as a non ansible specific tool? the core issue is: k8s depends on the ansible configuration file. now Kolla is split. how the kolla-k8s

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

On Wed, Nov 16, 2016 at 1:53 AM, Michał Jastrzębski wrote: > Hello, > > I wanted to thank Steve for doing the work, but kolla-ansible is now > open for business:) > > Couple of clarifications how it's going to work: > > 1. Currently Kolla-ansible is copy from kolla repo. We

Re: [openstack-dev] [heat][tripleo] New repository for software-config elements

2016-11-16 5:08 GMT+08:00 Steve Baker : > > > On Tue, Nov 15, 2016 at 10:26 PM, Thomas Herve wrote: > >> Hi all, >> >> Historically elements to create images using software config were >> developed in the heat-templates repository, which turned out to mean

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

Great! - Shinobu On Wed, Nov 16, 2016 at 3:39 PM, joehuang wrote: > Hi all, > > Tricircle was officially accepted yesterday as a big-tent project. > > The purpose of the Tricircle project is to provide networking automation > across Neutron in multi-region OpenStack

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

Hi all, Tricircle was officially accepted yesterday as a big-tent project. The purpose of the Tricircle project is to provide networking automation across Neutron in multi-region OpenStack clouds deployment. Use cases for the Tricircle are described in

Re: [openstack-dev] [neutron] OVO support

We won't be able to take a hard and fast rule on this just because of the way Neutron currently works and the semantics we offer the mechanism drivers and extensions in ML2. Right now when a port is created in ML2, we allow extensions and mechanism drivers to make changes as part of the same

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

Hi All, I am using devstack stable/newton branch and have deployed octavia for neutron-lbaasv2. Here is my local.conf [[local|localrc]] HOST_IP=10.0.2.15 DATABASE_PASSWORD=$ADMIN_PASSWORD MYSQL_PASSWORD=$ADMIN_PASSWORD RABBIT_PASSWORD=$ADMIN_PASSWORD SERVICE_PASSWORD=$ADMIN_PASSWORD

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

> 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 gRPC streaming protocol support > doing a

[openstack-dev] [Horizon] Meeting at 20:00 UTC this Wednesday, 16th November

Hi folks, The Horizon team will be having our next meeting at 20:00 UTC this Wednesday, 16th November in #openstack-meeting-3 Meeting agenda is here: https://wiki.openstack.org/wiki/Meetings/Horizon Anyone is welcome to to add agenda items and everyone interested in Horizon is encouraged to

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

Hi neutrinos, As mentioned during the last team meeting [1], there is a change [2] in the works aimed at adopting the neutron plugins directory as provided in neutron-lib 1.0.0 [3]. As shown in [2], the switch to using the directory is relatively straightforward. I leave the rest of the affected

Re: [openstack-dev] [Ironic] Baremetal Storage Service?

On 11/14/2016 10:22 PM, Akira Yoshiyama wrote: 2016-11-14 2:19 GMT+09:00 Jay Pipes >: On 11/13/2016 01:52 AM, Akira Yoshiyama wrote: No. "physical storages" means storage products like EMC VNX, NetApp Data ONTAP, HPE Lefthand and so on. Say there

Re: [openstack-dev] [kolla][kubernetes] kolla-kubernetes spec voting delay

On Wed, Nov 16, 2016 at 8:01 AM, Swapnil Kulkarni wrote: > On Wed, Nov 16, 2016 at 7:30 AM, Ryan Hallisey wrote: >> Hey folks, >> >> There has been a lot of input in the spec and tons IRC discussion >> over the last two days. I'm glad the discussion is

Re: [openstack-dev] [kolla][kubernetes] kolla-kubernetes spec voting delay

On Wed, Nov 16, 2016 at 7:30 AM, Ryan Hallisey wrote: > Hey folks, > > There has been a lot of input in the spec and tons IRC discussion > over the last two days. I'm glad the discussion is very active :). > > The goal of the spec is to capture the ideas and the discussion

[openstack-dev] [neutron] [vpnaas] vpnaas no longer part of the neutron governance

Hi As of today, the project neutron-vpnaas is no longer part of the neutron governance. This was a decision reached after the project saw a dramatic drop in active development over a prolonged period of time. What does this mean in practice? - From a visibility point of view, release notes

[openstack-dev] [kolla][kubernetes] kolla-kubernetes spec voting delay

Hey folks, There has been a lot of input in the spec and tons IRC discussion over the last two days. I'm glad the discussion is very active :). The goal of the spec is to capture the ideas and the discussion in one readable doc so no one has to read the 1 lines of IRC discussion that has

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

On Tue, Nov 15, 2016 at 5:16 PM, Jay Pipes wrote: > Awesome start, Monty :) Comments inline. > > 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

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

Awesome start, Monty :) Comments inline. 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 different people from 17 different clouds ran the same workload. And it worked!

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

whats the plan for genconfig? its based on ansible right now, but may fit better as a non ansible specific tool? Thanks, Kevin From: Michał Jastrzębski [inc...@gmail.com] Sent: Tuesday, November 15, 2016 9:53 AM To: OpenStack Development Mailing List (not

[openstack-dev] Gerrit downtime on Tuesday 2016-11-22 at 21:00UTC

Hi everyone, On Tuesday, November 22nd from approximately 21:00 through 21:30 UTC Gerrit will be unavailable while we complete project renames. Currently, we plan on renaming the following projects: rsc -> valence Existing reviews, project watches, etc, for these projects will all be carried

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

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 behaviour then a spec is required, and at that

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

On 11/15/2016 02:02 AM, Sławek Kapłoński wrote: Hello, IMHO receiving multiple uuids is not related to bug which I want to resolve somehow but if Chris wrote it I thought that it is maybe somehow related to "spawn multiple instances" feature. So can You maybe review my patch

Re: [openstack-dev] [devstack][neutron] - dropping direct route to VMs (FIXED_RANGE)

On 15 November 2016 at 15:04, Kevin Benton wrote: > Hi all, > > > Right now, we do something in devstack that does not reflect how > deployments are normally done. We setup a route on the parent host to the > private tenant network that routes through the tenant's router[1].

[openstack-dev] [devstack][neutron] - dropping direct route to VMs (FIXED_RANGE)

Hi all, Right now, we do something in devstack that does not reflect how deployments are normally done. We setup a route on the parent host to the private tenant network that routes through the tenant's router[1]. This behavior originates from a very long time ago[2] and I'm not sure if it even

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

On Tue, Nov 15, 2016 at 10:25:26AM -0800, Ian Cordasco wrote: > Hi all, > > So the stable-maintenance team (and liaisons to it) have had a meeting > scheduled for a while now. Recently, however, we've had trouble > getting more than one person to attend meetings when we have them. I need to

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

On Tue, Nov 15, 2016 at 4:53 PM, Jeremy Stanley wrote: > On 2016-11-15 15:31:40 -0500 (-0500), Steve Martinelli wrote: > > I really like the etherpad approach, its nice to see the history from > > previous meetings > > Strange, I personally find it way easier to navigate the

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

On 2016-11-15 15:31:40 -0500 (-0500), Steve Martinelli wrote: > I really like the etherpad approach, its nice to see the history from > previous meetings Strange, I personally find it way easier to navigate the change history for a MediaWiki page than use the time slider in Etherpad:

[openstack-dev] [OpenStack-Infra] [StoryBoard] Meeting Time Rearrangement

Hi folks, Last week at the StoryBoard meeting we discussed the fact that the meeting time has become inconvenient for most of the people who attend. As a result, we took the decision to move the meeting slot to 1900 UTC on Wednesdays in #openstack-meeting We'll be having our first

Re: [openstack-dev] [release][networking-bigswitch] tagging a branch and releasing on tarballs.openstack.org

Excerpts from Aditya Vaja's message of 2016-11-16 01:50:39 +0530: > Hi All, > [Redirect to a more specific mailing list if applicable] > I’m trying to tag a release on the networking-bigswitch project for > stable/newton branch and see if it pops up on >

Re: [openstack-dev] [osc][openstackclient][cliff] translation the command description in help

On Tue, Nov 15, 2016 at 4:08 PM, Steve Martinelli wrote: > $ find . -name '*.py' -exec sed -i .bak -e 's/""".*"""/_description=_("&")/g' > {} \; > > pep8 just burned me here, make sure you add a space between the = operator

[openstack-dev] [osc][openstackclient][cliff] translation the command description in help

The following is a PSA for all OpenStackClient plugins. Matt Edmonds filed bug 1636209 [1] against OpenStackClient because the main help message was not getting translated. In the example below, the "Create new user" string was not translated (some of the help text was removed for readability):

Re: [openstack-dev] [heat][tripleo] New repository for software-config elements

On Tue, Nov 15, 2016 at 10:26 PM, Thomas Herve wrote: > Hi all, > > Historically elements to create images using software config were > developed in the heat-templates repository, which turned out to mean > that this had to be packaged, etc. Today we were asked if tags could >

Re: [openstack-dev] [nova][libvirt] Lets make libvirt's domain XML canonical

On 9/30/2016 11:03 AM, Matthew Booth wrote: I thought it was a counter-argument (unless I've misunderstood). If you migrate the instance as-is without modification, you don't need to worry about whether it's currently a rescue instance. This problem goes away. The major complication I can

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

I agree with Steve. I just want to highlight that the wiki is viable again if we wanted to change. The move to etherpad was a necessity, now we have options we should be sure eveyrone is still happy with it. On Tue, Nov 15, 2016 at 12:31 PM, Steve Martinelli wrote: > I

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

I really like the etherpad approach, its nice to see the history from previous meetings On Tue, Nov 15, 2016 at 2:39 PM, Lance Bragstad wrote: > Hey folks, > > In today's keystone meeting, Morgan mentioned that we had the ability to > go back to using OpenStack Wikis for

[openstack-dev] tagging a branch and releasing on tarballs.openstack.org

Hi All, [Redirect to a more specific mailing list if applicable] I’m trying to tag a release on the networking-bigswitch project for stable/newton branch and see if it pops up on https://tarballs.openstack.org/networking-bigswitch/ [https://tarballs.openstack.org/networking-bigswitch/] .

[openstack-dev] [new][requirements] openstack_requirements 1.0.0 release

We are psyched to announce the release of: openstack_requirements 1.0.0: OpenStack python dependency management tools This is the first release of openstack_requirements. Download the package from: https://pypi.python.org/pypi/openstack_requirements For more details, please see below.

[openstack-dev] [nova] Nova Bugs Team Meeting

Hey folks! I completely mixed up the time due to recent Daylight Savings time changes and missed the meeting. It also seems I didn't mail out the meeting reminder. If you have anything you had wanted to bring up, please reach out to me via email or irc. Otherwise, the next 1800 UTC meeting will be

[openstack-dev] [keystone] meeting format poll

Hey folks, In today's keystone meeting, Morgan mentioned that we had the ability to go back to using OpenStack Wikis for meeting agendas. I created a poll to get feedback [0]. Let's keep it open for the week and look at the results as a team at our next meeting. Thanks! [0]

[openstack-dev] [oslo] rabbitmq timeout

Hi We see an issue where if we boot 10 instances on 1 compute node at a time we see that sometimes a few instances error out on compute node with following Traceback It looks like the RPC message call from compute saying set Instance to Active is timing out. It seems to help to set rpc

Re: [openstack-dev] [diskimage-builder] 01-override-yum-arch question

On 11/14/2016 11:55 AM, dmar...@redhat.com wrote: I was looking at 01-override-yum-arch in diskimage-builder, and have a question. Is the following code correct in git, or should $arch be written into /etc/dnf/vars/arch, similar to the yum path (for F22 and older) as shown below? ---

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

On 2016-11-15 12:20:35 -0600 (-0600), Michał Jastrzębski wrote: > I think we could use git submodule in kolla-ansible to download kolla. > That would help us deal with gates in kolla-ansible short term. > Thoughts? The Infra team has _strongly_ recommended against employing Git submodules within

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

Hi all, So the stable-maintenance team (and liaisons to it) have had a meeting scheduled for a while now. Recently, however, we've had trouble getting more than one person to attend meetings when we have them. I wonder if it would be more useful to less frequent meetings (perhaps every other

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

I think we could use git submodule in kolla-ansible to download kolla. That would help us deal with gates in kolla-ansible short term. Thoughts? On 15 November 2016 at 12:07, Paul Bourke wrote: > Seems good so far, thanks Michal / Steve. Cores don't forget to add >

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

Seems good so far, thanks Michal / Steve. Cores don't forget to add openstack/kolla-ansible to your watched projects in Gerrit :) I assume we just -2 any Ansible related patches currently open against the openstack/kolla project with instructions on how to resubmit. Also has it been

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

Hello, I wanted to thank Steve for doing the work, but kolla-ansible is now open for business:) Couple of clarifications how it's going to work: 1. Currently Kolla-ansible is copy from kolla repo. We will need to propose patches to remove docker from it. Also remove ansible bits from kolla. 2.

[openstack-dev] [ironic] ending the API meetings

Hi, We are ending the ironic API meetings that we started in July [0]. There were few AND mighty meetings. I thank Devananda for an awesome job of addressing some major API pain points in his epic "Evolving our REST API" series of specifications [1]! Now we need to follow his lead and get

Re: [openstack-dev] [gnocchi] new measures backlog scheduling

On 15/11/16 04:53 AM, Julien Danjou wrote: > Yeah in the case of the Swift driver for Gnocchi, I'm not really sure > how much buckets we should create. Should we make the user pick a random > number like the number of partition in Swift and then create the > containers in Swift? Or can we have

Re: [openstack-dev] [Horizon] ui-cookiecutter

Great! I'll be sure to bring it up on your behalf (if you are not there).   - Original message -From: Shuu Mutou To: "openstack-dev@lists.openstack.org" Cc: Haruhiko Katou Subject: Re: [openstack-dev]

Re: [openstack-dev] [Glance] [api] Community Images Impasse

On 11/15/2016 10:35 AM, Brian Rosmaita wrote: > Adding '[api]' to subject to get API-WG attention. > > On 11/15/16, 11:26 AM, "Ian Cordasco" wrote: > >> Hi all, >> >> One of our priorities for Ocata-1 (whose deadline Glance has set for >> 17 November 2016) is the

Re: [openstack-dev] [Congress] Magnum_driver

Hi Ruben, Did a little debugging for you... 1) Run your unit tests $ tox -epy34 congress.tests.datasources.test_magnum ... File "/Users/tim/opencode/congress/congress/tests/datasources/test_magnum_driver.py", line 3, in from congress.datasources import magnum_driver File

Re: [openstack-dev] [tripleo][ci] jobs shuffle to add IPv6 coverage

On 18 Oct, Gabriele Cerami wrote: > Hello, > > after adding coverage in CI for HA IPv6 scenario here > https://review.openstack.org/363674 we wanted to add IPv6 testing on the > gates. > To not use any more resources the first suggestion to add IPv6 to the > gates was to make all HA jobs IPv6,

[openstack-dev] [Glance] [api] Community Images Impasse

Adding '[api]' to subject to get API-WG attention. On 11/15/16, 11:26 AM, "Ian Cordasco" wrote: >Hi all, > >One of our priorities for Ocata-1 (whose deadline Glance has set for >17 November 2016) is the Community Images work that has been discussed >now for several

[openstack-dev] [Glance] Community Images Impasse

Hi all, One of our priorities for Ocata-1 (whose deadline Glance has set for 17 November 2016) is the Community Images work that has been discussed now for several cycles and prioritized since the end of Newton. Like we often do in Glance, we've reached an impasse in the 11th hour. To summarize,

Re: [openstack-dev] [glance] priorities for O-1

  -Original Message- From: Ian Cordasco Reply: Ian Cordasco Date: November 14, 2016 at 10:58:16 To: OpenStack Development Mailing List (not for usage questions) Subject:  Re: [openstack-dev] [glance]

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

On Tue, Nov 15, 2016 at 8:56 AM, Monty Taylor wrote: > The auth story. The native/default auth for gRPC is oauth. It has the > ability for pluggable auth, but that would raise the barrier for new > languages. I'd love it if we can come up with a story that involves > making

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

On Mon, Nov 7, 2016 at 8:51 AM, Dmitry Tantsur wrote: > Hi folks! > > In view of the Ironic governance discussion [1] I'd like to talk about > wsmanclient [2] future. > > This project was created to split away wsman code from python-dracclient to > be reused in other drivers

Re: [openstack-dev] Fedora AArch64 (64-bit ARM) support in diskimage-builder

On 11/14/2016 09:44 PM, Gregory Haynes wrote: On Mon, Nov 14, 2016, at 05:06 PM, dmar...@redhat.com wrote: On 11/14/2016 04:40 PM, Ben Nemec wrote: On 11/11/2016 10:55 AM, dmar...@redhat.com wrote: I have been looking at using diskimage-builder on Fedora AArch64. While there is 64-bit ARM

Re: [openstack-dev] [nova][vmware] status of vmware third party CI?

On 11/15/2016 10:09 AM, Matt Riedemann wrote: I've got a docs patch that failed both nova-net and neutron vmware third party CI: https://review.openstack.org/#/c/397382/ The nova-net one failed some aggregates response validation:

[openstack-dev] [nova][vmware] status of vmware third party CI?

I've got a docs patch that failed both nova-net and neutron vmware third party CI: https://review.openstack.org/#/c/397382/ The nova-net one failed some aggregates response validation: http://208.91.1.172/logs/ext-nova-dsvm/397382/2/2074/tempest_results.html.gz That's not even related to

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

Great idea, I just ran into a similar issue when investigating the following Kubernetes issue[1], and the OpenStack provider. They are running into similar issues around networking and what a "public" network address is, which is exactly what Shade had to deal with, in the public clouds that we

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

Hey everybody! At this past OpenStack Summit the results of the Interop Challenge were shown on stage. It was pretty awesome - 17 different people from 17 different clouds ran the same workload. And it worked! However, one of the reasons it worked is because they all used the Ansible modules we

[openstack-dev] [Congress] relevant horizontal efforts at PTG

Hi all! aimeeu asked during team meeting about relevant sessions on Monday and Tuesday. I don't have anything official. I think it's more a matter of you and your org's interest in contributing to those horizontal efforts.  If you're looking to contribute to a horizontal project, horizon, the

Re: [openstack-dev] [vitrage]bp:static-datasource-config-formatworking items

From: Yujun Zhang Date: Tuesday, 15 November 2016 at 16:03 On Tue, Nov 15, 2016 at 8:44 PM Weyl, Alexey (Nokia - IL) > wrote: Ok, sounds good. We need to understand what is the common way in openstack to work with deprecated code. Maybe it

Re: [openstack-dev] [Browbeat] Nominate Justin Kilpatrick as core.

Alright, I have 1, +1... Any one else (I think Alex +1ed on IRC)? Since I nominated him obviously I +1! Joe On Tue, Nov 8, 2016 at 9:24 AM, Sindhur Malleni wrote: > +1. I think Justin's done some awesome work and would be a great addition to > the core team. Better get

Re: [openstack-dev] [neutron] OVO support

My two cents on this. OVO is going to be the new layer to access to DB model classes, therefore all the calls to the database(ensuring that there is an opened session) and the process to receive(validating fields) and/or return data(determining if a specific column exists) should be managed

[openstack-dev] [monasca][release] Release of openstack/monasca-grafana-datasource 1.0.0 failed

It looks like the monasca-grafana-datasource repository isn't set up in the way our release job expects for publishing nodejs projects. >From the log: 2016-11-15 14:03:26.945891 | + npm install 2016-11-15 14:03:27.287904 | npm ERR! install Couldn't read dependencies 2016-11-15 14:03:27.289483 |

Re: [openstack-dev] [vitrage]bp:static-datasource-config-formatworking items

On Tue, Nov 15, 2016 at 8:44 PM Weyl, Alexey (Nokia - IL) < alexey.w...@nokia.com> wrote: > Ok, sounds good. > > We need to understand what is the common way in openstack to work with > deprecated code. > Maybe it could be discussed in next weekly meeting. Anybody who has experience on it please

Re: [openstack-dev] [heat][tripleo] New repository for software-config elements

On 15/11/16 04:26, Thomas Herve wrote: Hi all, Historically elements to create images using software config were developed in the heat-templates repository, which turned out to mean that this had to be packaged, etc. Today we were asked if tags could be added to help maintaining the packages.

Re: [openstack-dev] [tc][kolla] Ansible module with GPLv3

Jeremy Stanley wrote: > [...] > A quick search for http://codesearch.openstack.org/?q=gpl=1 turns > up the openstack/murano-apps repo which has content aggregated under > a mix of Apache License v2.0, GPLv2 (inherited from Plone), GPLv3 > (from Clearwater), and GNU AGPLv3 (SugarCRM); it calls them

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

On 11/15/16 5:12 AM, zhi wrote: Sorry, I forgot to say my local environment is Liberty. :) According to the blueprint and reviews this didn't land until Newton, maybe some in Mitaka, so I wouldn't expect it to work in Liberty. -Brian 2016-11-15 18:07 GMT+08:00 zhi

Re: [openstack-dev] [api]

On 14/11/16 20:52, Ian Cordasco wrote: not_in is nice and explicit while nin and out are a bit, more clever. I think we should avoid trying to be clever. Agreed - I think not_in is more intelligible and guessable than the other suggestions. Miles

Re: [openstack-dev] [ALU] Re: [ALU] [vitrage]bp:static-datasource-config-formatworking items

Ok, sounds good. We need to understand what is the common way in openstack to work with deprecated code. From: Yujun Zhang [mailto:zhangyujun+...@gmail.com] Sent: Tuesday, November 15, 2016 12:29 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [ALU] Re:

[openstack-dev] [nova] Nova API sub-team meeting

Hi, We have weekly Nova API meeting tomorrow. The meeting is being held Wednesday UTC1300 and irc channel is #openstack-meeting-4. The proposed agenda and meeting details are here: https://wiki.openstack.org/wiki/Meetings/NovaAPI Please feel free to add items to the agenda. Thanks

[openstack-dev] [nova] next notification subteam meeting

Hi, The next notification subteam meeting will be held on 2016.11.15 17:00 UTC [1] on #openstack-meeting-4. Cheers, gibi [1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20161115T17 __ OpenStack

Re: [openstack-dev] [Horizon] Proposing Kenji Ishii for core

+1 2016年11月15日(火) 20:47 Rob Cresswell (rcresswe) : > Big +1 from me > > > On 14 Nov 2016, at 00:24, Richard Jones wrote: > > > > Hi Horizon core team, > > > > I propose Kenji Ishii as a new Horizon core reviewer. Kenji has been a > > solid Horizon

[openstack-dev] [neutron][calico] networking-calico IRC meeting today

Hi all; just wanted to remind that there will be a networking-calico IRC meeting today [1]. Please feel free to add to the agenda at [2] (or ask me to do that if you prefer). Thanks! Neil [1] http://eavesdrop.openstack.org/#Networking_Calico_Meeting [2]

Re: [openstack-dev] [api]

On Nov 14, 2016 3:49 PM, "Edward Leafe" wrote: > > On Nov 14, 2016, at 3:14 PM, Ed Leafe wrote: > > > Since we already had ‘new’, I thought that ‘nin’ would be consistent. No other reason to prefer it, though. > > s/new/neq > > Damn you autocorrect! I forgot

Re: [openstack-dev] [Horizon] Proposing Kenji Ishii for core

Big +1 from me > On 14 Nov 2016, at 00:24, Richard Jones wrote: > > Hi Horizon core team, > > I propose Kenji Ishii as a new Horizon core reviewer. Kenji has been a > solid Horizon contributor for some time, with thoughtful and helpful > reviews showing good judgment

Re: [openstack-dev] [Openstack-operators] [openstack-operators][openstack-ansible]deploying mutli-node openstack on baremetal nodes

Hi Akshay, If I understand correctly, you're looking to deploy the services on metal hosts (rather than in containers) - in that case you would need to adjust the env.d/*.yml (service files) to set the property "is_metal: True". The second query regarding multiple VLans - if you are using

Re: [openstack-dev] [Horizon] Proposing Kenji Ishii for core

+1 2016-11-14 9:24 GMT+09:00 Richard Jones : > Hi Horizon core team, > > I propose Kenji Ishii as a new Horizon core reviewer. Kenji has been a > solid Horizon contributor for some time, with thoughtful and helpful > reviews showing good judgment and good knowledge of

[openstack-dev] [openstack-operators][openstack-ansible]deploying mutli-node openstack on baremetal nodes

Hi, I want to deploy openstack using openstack-ansilbe. I am having difficulty in understanding where to define baremetal host deployment and how to define multiple vlans that can be used to separate the networks(mgmt, tunnel, external). I went through

Re: [openstack-dev] [kolla] Propose removal of TrivialFix requirement

Thanks for the reminder Andreas, patchset here: https://review.openstack.org/397672 On 15/11/16 10:29, Andreas Jaeger wrote: On 2016-11-15 11:10, Paul Bourke wrote: Given the window for this vote is now closed and I saw no minus ones I'll assume this has passed. TrivialFix is now optional.

Re: [openstack-dev] [ALU] [vitrage] bp:static-datasource-config-formatworking items

Hi, Alexey I plan to split the implementation to several steps, because it will take weeks to complete. I'm afraid it would be too big a patch to review if I submit all changes in one patch set. Instead I want to get comments as earlier as possible. Each submit will be covered by additional unit

Re: [openstack-dev] [kolla] Propose removal of TrivialFix requirement

On 2016-11-15 11:10, Paul Bourke wrote: > Given the window for this vote is now closed and I saw no minus ones > I'll assume this has passed. TrivialFix is now optional. Is TrivialFix mentioned in the docs and do those need updating for the changed policy? Andreas -- Andreas Jaeger

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

Sorry, I forgot to say my local environment is Liberty. :) 2016-11-15 18:07 GMT+08:00 zhi : > Hi, all > > I followed this guide[1] to create trunk ports and created a vm by > using trunk port. But I met a weird problem. OVS agent didn't generate " > tbr " bridge. All

Re: [openstack-dev] [kolla] Propose removal of TrivialFix requirement

Given the window for this vote is now closed and I saw no minus ones I'll assume this has passed. TrivialFix is now optional. Thanks, -Paul On 04/11/16 22:51, Steven Dake (stdake) wrote: Paul, I’ll take your request as a request for a vote of the core reviewers. My vote is +1 in favor

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

Hi, all I followed this guide[1] to create trunk ports and created a vm by using trunk port. But I met a weird problem. OVS agent didn't generate " tbr " bridge. All the OVS bridges shows below: " [root@server-64 ~]# ovs-vsctl list-br br-int br-physnet4 br-tun " Why did the

Re: [openstack-dev] [gnocchi] new measures backlog scheduling

On Tue, Nov 15 2016, gordon chung wrote: >> I'm stepping in to an area here (gnocchi) that I know very little about, >> so please forgive me where I mess up. >> >> First, as a practical note, stuff in Swift will be /much/ better when >> you spread it across the entire namespace. It's a lot better

Re: [openstack-dev] [ALU] [vitrage] bp:static-datasource-config-formatworking items

Hi Yujun, Good job! This is a very important change for Vitrage. I have a couple of questions please: 1. Why do we want to create a new datasource ‘static’ and not rename the current ‘static_physical’ datasource and change it to work with the new format? 2. How are you planning to use the old

Re: [openstack-dev] [neutron] OVO support

I could be wrong, but I suspect we're doing it this way to be able to do changes to several objects atomically, and roll back the transactions if at some point in time what we're trying to accomplish is not possible. Thoughts? On Tue, Nov 15, 2016 at 10:06 AM, Gary Kotton

[openstack-dev] [heat][tripleo] New repository for software-config elements

Hi all, Historically elements to create images using software config were developed in the heat-templates repository, which turned out to mean that this had to be packaged, etc. Today we were asked if tags could be added to help maintaining the packages. Before we do that, I wonder if we should

[openstack-dev] [neutron] OVO support

Hi, It seems like a lot of the object work is being done under database transactions. My understanding is that the objects should take care of this internally. Any thoughts? Thanks Gary __ OpenStack Development Mailing List

[openstack-dev] [tacker] No Tacker weekly meeting today

Hi Tackers, There will be no weekly meeting today as there are no agenda items from the team. We will meet next week on Nov 22nd 2016. Please feel free to add your agenda items in meeting wiki link [1]. [1] https://wiki.openstack.org/wiki/Meetings/Tacker#Agenda Thanks, Sripriya

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

Hello, IMHO receiving multiple uuids is not related to bug which I want to resolve somehow but if Chris wrote it I thought that it is maybe somehow related to "spawn multiple instances" feature. So can You maybe review my patch https://review.openstack.org/#/c/371592/ to fix