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

Oh, sorry, this exception was gone after I set "ovs-vsctl set-controller br-ex tcp:127.0.0.1:6640 ". Thanks 2016-11-17 15:07 GMT+08:00 zhi : > 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.

[openstack-dev] [vitrage] Barcelona Summit recap

Hi, Barcelona summit was very successful and productive for the Vitrage team. Below is a summary of our main activities during the summit. Sessions 1. Keynotes demo - OpenStack and OPNFV - Keeping Your Mobile Phone Calls Connected Ifat Afek, Ryota Mibu and Ildiko Vancsa presented how

[openstack-dev] [neutron] OVS agent reports error "ovs-ofctl: br-int is not a bridge or a socket"

Hi, all I build a devstack which code from master branch. By default the OVS version is 2.0.2 when install devstack. So I reinstall the OVS 2.6.0. I meet an exception in OVS agent when all OVS services runs okay. Exception shows below: 2016-11-17 15:47:29.175 ERROR neutron.agent.linux.utils [req

[openstack-dev] [openstack-ansible] pip issues

Hi all, Context: openstact-ansible newton, tag: 14.0.1 OS: ubuntu 16.04 LTS the pip command is unable to download packages form the repo container. I can reach the repo container from within galera container through the port 8181: *root@node01:~# lxc-attach -n node01_galera_container-368f269ar

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

On> 11/16/16, 8:22 PM, "Ben Swartzlander" wrote: > > 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 “-“ - > > ht

Re: [openstack-dev] [openstack-ansible] pip issues

Hello, Is this a greenfield newton? Could you wget your http://172.16.1.2:8181/os-releases/14.0.1/requirements_constraints.txt file reliably? Are you using haproxy? Are all the backends OK there? Don’t hesitate to come by our irc channel, it’s probably easier to have a conversation there. B

[openstack-dev] [networking-ovn] OVN native gateway workflow

Greetings, I'm testing OVN integration with RDO Openstack. I can create tenant networks and attach VMs to them with no issues. However I don't get how the gateway scheduling works. It seems like whenever I create an external provider network and attach it to my DLR, OVN should schedule a gateway ro

Re: [openstack-dev] [all] Embracing new languages in OpenStack

Ok, as promissed I've pushed a patch with a reference document that collects what I had written in my post and the feedback from this thread. I believe the patch needs tons of discussion so, y'all, get to it :) I've added members from different teams to help filling in some of the sections speci

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

Yeah, I had the same situation in Juju 2.0 ! (all is ok with Juju 1.25) (with AWS provider) It happens because OpenStack charms started to use 'network-get --primary-address public' instead of 'unit-get'. Then 'network-get public' returns private address and then charms register endpoint with priv

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

+1 On 17/11/16 07:18, Martin André wrote: 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

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

Many thanks Cratoners, I think all this looks promising while some things need to be worked out. Have to chew this a bit and also join to IRC to discuss further (just that I am in different timezone). As seen in the discussion, there might be a problem in making notification that can be used t

Re: [openstack-dev] [openstack-ansible] pip issues

Hi Jesse and Jean-Philippe, Thank you both for your responses. @Jesse I am just having one node for the infra and one repo, for now: root@maas:/opt/openstack-ansible/playbooks# ansible repo_all -m shell -a "du -sh /var/www/repo/*" Variable files: "-e @/etc/openstack_deploy/user_secrets.yml -e @

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

Hello, Thx all of You for explanations. So I think that [1] can be closed as "Won't fix" now. Am I right? [1] https://bugs.launchpad.net/neutron/+bug/1640767 -- Best regards / Pozdrawiam Sławek Kapłoński [email protected] On Wed, 16 Nov 2016, Dean Troyer wrote: > > Excerpts from Sławek Kapł

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

Hello, Ok. So it's different case. I was thinking only about issues with quotas. For me this which You described is more related to scheduler/placement API(?). Do You think that it should be taken in same specs? -- Best regards / Pozdrawiam Sławek Kapłoński [email protected] On Thu, 17 Nov 20

Re: [openstack-dev] [openstack-ansible] pip issues

For the sake of record and FYI - Instead of cross-posting, this discussion has been continued on the openstack-operators ML. From: Jean-Philippe Evrard Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Thursday, November 17, 2016 at 9:10 AM To: "OpenStack Developme

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

Hi Jay, Thank you for your replies. 2016-11-16 11:38 GMT+09:00 Jay Pipes : > 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 stor

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

+1 On 11/17/16, 2:50 AM, "Paul Bourke" wrote: >+1 > >On 17/11/16 07:18, Martin André wrote: >> 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

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

Can we stick to one tag [kolla] for all ML discussion? A whole slew of people already have filters setup. Kolla is one project with one mission with multiple deliverables. No other project that has multiple deliverables tags emails per deliverable. I don’t think this is an occasion to be a s

[openstack-dev] [git-upstream] How to view only commits applied since last import

Hi Darragh / git-upstream community, I've been looking at a way to easily view a log of what commits made since the last upstream import when managing a branch with git-upstream. Right now this can be hard to do - something like 'git log upstream/master..HEAD' shows a lot of duplicate commits

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

On Thu, Nov 17, 2016 at 4:55 AM, Sławek Kapłoński wrote: > Thx all of You for explanations. So I think that [1] can be closed as > "Won't fix" now. Am I right? > > [1] https://bugs.launchpad.net/neutron/+bug/1640767 Maybe? Doug, Monty and I are talking about OpenStackClient and Shade, not neutro

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

I totally agree with the direction of OSC and shade. The similar discussion happens in neutronclient side before too. >From user perspective, 'name' is really useful to identify resources, even though admin usually use ID to identify resources. In the past neutronclient discussion, requiring at le

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

On 11/17/2016 04:03 AM, Ravi, Goutham wrote: > > > On> 11/16/16, 8:22 PM, "Ben Swartzlander" wrote: > > > > 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 th

[openstack-dev] [murano] Nominating Felipe Monteiro for murano core

Hello team, I would like to nominate Felipe for murano core. His and his teams work on increasing murano unit test coverage in Newton and Ocata has allowed us to reach astonishing 85% I would like to personally thank Felipe for his dedication to making murano a more mature and stable project! You

[openstack-dev] [openstack-ansible][openstack-ansible-plugins] error in rabbitmq installation , config template plugin

Hi All I am relatively new to Ansible, trying to run a playbook installing rabbit server https://github.com/openstack/openstack-ansible-rabbitmq_server (all stable/newton) - name: Install RabbitMQ server hosts: rabbitmq_all user: root roles: - { role: "rabbitmq_server", tags: [ "rabbit

Re: [openstack-dev] [openstack-ansible][openstack-ansible-plugins] error in rabbitmq installation , config template plugin

The error you’re seeing is because that role has dependencies which can’t be resolved. The deps are here: https://github.com/openstack/openstack-ansible-rabbitmq_server/blob/stable/newton/meta/main.yml#L35 The roles are mostly designed to be re-usable without the integrated repository, but to d

[openstack-dev] [nova] Welcome Lee Yarwood to nova-stable-maint core

I've added Lee Yarwood to the nova-stable-maint core team: https://review.openstack.org/#/admin/groups/540,members Lee has done a great job the last few months of proposing backports and reviewing changes to nova on the stable branches. So please help me in welcoming and congratulating Lee on

Re: [openstack-dev] [murano] Nominating Felipe Monteiro for murano core

+1 On Thu, Nov 17, 2016 at 4:29 PM Kirill Zaitsev wrote: > Hello team, I would like to nominate Felipe for murano core. > His and his teams work on increasing murano unit test coverage in Newton > and Ocata has allowed us to reach astonishing 85% > I would like to personally thank Felipe for his

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

+1 On Thu, Nov 17, 2016 at 8:26 PM, Steven Dake (stdake) wrote: > Can we stick to one tag [kolla] for all ML discussion? A whole slew of > people already have filters setup. Kolla is one project with one mission > with multiple deliverables. No other project that has multiple > deliverables t

[openstack-dev] [kolla][git]How to backport commit after repo split

We have split kolla repo into two repos. the dockerfile related code remains in kolla repo which builds images. and the ansible playbook related code is moved into kolla-ansible which deploy the images. But it brings a new challenge. How to backport the kolla-ansible change to kolla in stable bran

Re: [openstack-dev] [nova] Welcome Lee Yarwood to nova-stable-maint core

Le 17/11/2016 14:53, Matt Riedemann a écrit : > I've added Lee Yarwood to the nova-stable-maint core team: > > https://review.openstack.org/#/admin/groups/540,members > > Lee has done a great job the last few months of proposing backports and > reviewing changes to nova on the stable branches.

Re: [openstack-dev] [openstack-ansible][openstack-ansible-plugins] error in rabbitmq installation , config template plugin

Many thanks I was aware of the dependencies and download them all to /home/centos/ansible-installation/roles/dependencies [centos@ansible-tests-tshtilma dependencies]$ ls apt_package_pinning lxc_container_create lxc_hosts openstack_hosts pip_install also my test playbook was taken from the e

Re: [openstack-dev] [openstack-ansible][openstack-ansible-plugins] error in rabbitmq installation , config template plugin

From: "Shtilman, Tomer (Nokia - IL)" Date: Thursday, November 17, 2016 at 2:11 PM To: "OpenStack Development Mailing List (not for usage questions)" , Jesse Pretorius Subject: RE: [openstack-dev] [openstack-ansible][openstack-ansible-plugins] error in rabbitmq installation , config template

Re: [openstack-dev] [openstack-ansible][openstack-ansible-plugins] error in rabbitmq installation , config template plugin

Hi Tomer, I noticed you said you have _v2_config_template.py in your action plugins path, but you should also have verify you have the "config_template" in your library path: ie. https://github.com/openstack/openstack-ansible-plugins/blob/master/library/config_template On Thu, Nov 17, 2016 at 8:1

[openstack-dev] [release] [glance] Immutability of migrations between beta releases

Hi all, Glance was hoping to include our Community Images feature work in Ocata-1, but we have had some 11th hour communications about how migrations will look to and affect end users and operators. For now, we're not going to include that feature, but it raised a discussion during our meeting tod

[openstack-dev] [architecture] Reminder: Arch-WG Meeting today, and -- repo

Just a friendly reminder that we have a meeting today at 19:00 UTC. Please come join us and add anything you'd like to talk about to the Agenda: https://wiki.openstack.org/wiki/Meetings/Arch-WG On another note, we have a repository now to facilitate our processes: https://review.openstack.org/#/

Re: [openstack-dev] [openstack-ansible][openstack-ansible-plugins] error in rabbitmq installation , config template plugin

Yes config_template is there, I have cloned the whole git project, not specific files Thanks -Original Message- From: Logan V. [mailto:[email protected]] Sent: יום ה 17 נובמבר 2016 16:25 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [op

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

On 11/17/2016 04:58 AM, Sławek Kapłoński wrote: Hello, Ok. So it's different case. I was thinking only about issues with quotas. For me this which You described is more related to scheduler/placement API(?). Do You think that it should be taken in same specs? Given that we need a spec to cover

Re: [openstack-dev] [kolla][git]How to backport commit after repo split

Seen as both repos stem from the same codebase, we should be able to just cherry-pick changes as usual. If a fix comprises of a change to both kolla and kolla-ansible, it will just mean two cherry-picks. Will need to wait till the relevant pieces are removed from both repos to confirm this but

Re: [openstack-dev] [murano] Nominating Felipe Monteiro for murano core

+1 On Thu, Nov 17, 2016 at 5:54 AM, Alexander Tivelkov wrote: > +1 > > On Thu, Nov 17, 2016 at 4:29 PM Kirill Zaitsev > wrote: > >> Hello team, I would like to nominate Felipe for murano core. >> His and his teams work on increasing murano unit test coverage in Newton >> and Ocata has allowed u

[openstack-dev] [nova] Thanks to those reviewing specs this week

I just wanted to say thanks to everyone reviewing specs this week. I've seen a lot of non-core newer people to the specs review process chipping in and helping to review a lot of the specs we're trying to get approved for Ocata. It can be hard to grind through several specs reviews in a day so

Re: [openstack-dev] [nova] Thanks to those reviewing specs this week

On 11/17/2016 10:15 AM, Matt Riedemann wrote: I just wanted to say thanks to everyone reviewing specs this week. I've seen a lot of non-core newer people to the specs review process chipping in and helping to review a lot of the specs we're trying to get approved for Ocata. It can be hard to grin

[openstack-dev] [murano] Removing Ekaterina Chernova and Filip Blaha from cores

I’m proposing to remove Ekaterina Chernova and Filip Blaha from the list of murano cores. They both have been very active in the previous cycles, but their focus have shifted and we haven’t seen much activity in Newton and Ocata. If the situation would change — I would be very happy to welcome ba

Re: [openstack-dev] [nova] Thanks to those reviewing specs this week

> I just wanted to say thanks to everyone reviewing specs this week. I've > seen a lot of non-core newer people to the specs review process chipping > in and helping to review a lot of the specs we're trying to get approved > for Ocata. It can be hard to grind through several specs reviews in a > d

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

Ganpat, Great to hear. FYI, our documentation lives here: http://docs.openstack.org/developer/octavia/ I will note that we have bugs for more documentation to be created, but there is a good start at the link above. Michael On Wed, Nov 16, 2016 at 10:36 PM, Ganpat Agarwal wrote: > Thanks a lo

Re: [openstack-dev] [neutron] OVS agent reports error "ovs-ofctl: br-int is not a bridge or a socket"

On 11/17/2016 03:14 AM, zhi wrote: Hi, all I build a devstack which code from master branch. By default the OVS version is 2.0.2 when install devstack. So I reinstall the OVS 2.6.0. I meet an exception in OVS agent when all OVS services runs okay. Exception shows below: 2016-11-17 15:47:29.175

[openstack-dev] [Neutron][L3-subteam] Weekly IRC meeting canceled on November 24th

Dear L3-subteam, Due to the Thanksgiving holiday in the USA, we will cancel our weekly meeting on November 24th. We will resume normally on December 1st Best regards Miguel __ OpenStack Development Mailing List (not for usag

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

Hi Songming Yan, Thanks for reporting this. Supporting Newton is definitely on our ToDo list. Expect some patch soon on this topic. Regards, Jerome De : 阎松明 Répondre à : "OpenStack Development Mailing List (not for usage questions)" Date : jeudi 17 novembre 2016 à 08:29 À : "openstack-dev@list

[openstack-dev] [all][api] POST /api-wg/news

Greetings OpenStack community, A pleasant but short meeting this week. During the open discussion we all agreed that the increased activity on the mailing list using the [api] tag -- with explicit invitations to engage in discussions -- was great to see happening and great to participate in.

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

Hello, Thx for clarifications and closing this bug. -- Best regards / Pozdrawiam Sławek Kapłoński [email protected] On Thu, 17 Nov 2016, Akihiro Motoki wrote: > I totally agree with the direction of OSC and shade. > The similar discussion happens in neutronclient side before too. > > From u

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

Hello, Ok, I will try maybe to write such specs if I will have a while. -- Best regards / Pozdrawiam Sławek Kapłoński [email protected] On Thu, 17 Nov 2016, Chris Friesen wrote: > On 11/17/2016 04:58 AM, Sławek Kapłoński wrote: > > Hello, > > > > Ok. So it's different case. I was thinking o

Re: [openstack-dev] [Openstack-operators] [nova] More file injection woes

On 11/14/2016 4:16 AM, Daniel P. Berrange wrote: On Fri, Nov 11, 2016 at 07:11:51PM -0600, Matt Riedemann wrote: Chris Friesen reported a bug [1] where injected files on a server aren't in the guest after it's evacuated to another compute host. This is because the injected files aren't persisted

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

Hi, What would active-active exactly be in DVR mode ? -Thomas Le 16/11/2016 à 16:42, huangdenghui a écrit : 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 whe

Re: [openstack-dev] [networking-ovn] OVN native gateway workflow

On Thu, Nov 17, 2016 at 4:23 AM, Michael Kashin wrote: > Greetings, > I'm testing OVN integration with RDO Openstack. I can create tenant > networks and attach VMs to them with no issues. However I don't get how the > gateway scheduling works. It seems like whenever I create an external > provide

[openstack-dev] feedback Re: [ironic] ocata summit summary

Hi, Thanks for the great summary Jim! As an aside (or in addition to this?), we (or maybe I should speak for myself only) am always interested in constructive feedback and suggestions on how we (as a community) can improve. If you have ideas on how we can improve the design sessions at the sum

[openstack-dev] [Neutron] Stepping down from core

Neutron (and Openstack), It is with regret that I report that my work situation has changed such that I'm not able to keep up with my duties as a Neutron core reviewer, L3 lieutenant, and drivers team member. My participation has dropped off considerably since Newton was released and I think it is

Re: [openstack-dev] [Neutron] Stepping down from core

Hi Carl, Sorry to hear that you are stepping down as core. Hope to see you back in OpenStack neutron and thanks for all the work and reviews that you have done. Wish you all success. Thanks Swami From: Carl Baldwin [mailto:[email protected]] Sent: Thursday, November 17, 2016 10:43 AM To: OpenSt

Re: [openstack-dev] [Neutron] Stepping down from core

There is a secret clause in the CLA that says once you are core you have to give public notice 2 years in advance of stepping down, so you're going to have to keep working. :) On Thu, Nov 17, 2016 at 10:42 AM, Carl Baldwin wrote: > Neutron (and Openstack), > > It is with regret that I report tha

Re: [openstack-dev] [Neutron] Stepping down from core

Sad to see you go, Carl. Good luck! Eugene. On Thu, Nov 17, 2016 at 10:42 AM, Carl Baldwin wrote: > Neutron (and Openstack), > > It is with regret that I report that my work situation has changed such > that I'm not able to keep up with my duties as a Neutron core reviewer, L3 > lieutenant, and

[openstack-dev] [manila] Deadlines and no meeting next week

For those who missed the weekly meeting tonight there were 2 important things you should know: The meeting next week is canceled. The low-priority spec merge deadline was extended to tomorrow midnight (18 Nov 23:59 UTC) because we wanted to accept more specs for Ocata, and there are several w

Re: [openstack-dev] [Neutron] Stepping down from core

Carl, Thank you for all your great work over the years. Sorry to see you go. John > On Nov 17, 2016, at 1:42 PM, Carl Baldwin wrote: > > Neutron (and Openstack), > > It is with regret that I report that my work situation has changed such that > I'm not able to keep up with my duties as a Neu

[openstack-dev] [neutron] rally failure in the gate

Hi folks, Please do not recheck rally failures. There was a breaking change introduced by aodh [0] that prevented rally to work on trusty. We are switching to xenial as we speak anyway [1], so the glitch should be short lived. Thanks, Armando [0] https://review.openstack.org/#/c/372586/ [1] htt

Re: [openstack-dev] [murano] Removing Ekaterina Chernova and Filip Blaha from cores

no objections On Thu, Nov 17, 2016 at 7:28 AM, Kirill Zaitsev wrote: > I’m proposing to remove Ekaterina Chernova and Filip Blaha from the list > of murano cores. They both have been very active in the previous cycles, > but their focus have shifted and we haven’t seen much activity in Newton >

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

+1 On Tue, Nov 15, 2016 at 5:02 AM, Akira Yoshiyama wrote: > +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 ha

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

-Original Message- From: Paul Belanger Reply: OpenStack Development Mailing List (not for usage questions) Date: November 16, 2016 at 12:13:26 To: [email protected] Subject:  Re: [openstack-dev] [all] important changes to pep8 python jobs > On Thu, Nov 03, 2016 at 12:29

[openstack-dev] [charms] Barbican Hostname Config Params

Is there a specific reason the barbican charm doesn't have the os-{internal,private}-hostname config params? Thanks __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]

Re: [openstack-dev] [Neutron] Stepping down from core

Sorry to hear this Carl. You've been a great asset to openstack. Good luck to your future endeavors! Thanks, Brandon On Thu, 2016-11-17 at 11:42 -0700, Carl Baldwin wrote: > Neutron (and Openstack), > > It is with regret that I report that my work situation has changed > such that I'm not able

Re: [openstack-dev] [Neutron] Stepping down from core

Hi Carl, Thanks for all the hard work, Neutron is definitely better because of it. Hope to work with you again some day. Good luck with your new endeavor! -Brian On 11/17/2016 01:42 PM, Carl Baldwin wrote: Neutron (and Openstack), It is with regret that I report that my work situation has

Re: [openstack-dev] [Neutron] Centralizing some config options will break many stadium projects

I've refreshed the agent config patch [1] with the needed-by/depends-on using the example patch in Dragonflow [2]. [1] https://review.openstack.org/#/c/343045/ [2] https://review.openstack.org/#/c/391853/ On Fri, Oct 28, 2016 at 4:25 PM, Armando M. wrote: > > > On 27 October 2016 at 22:18, Bra

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

+1 from me. Kenji is also very active in the plugin space.   - Original message -From: David Lyle To: "OpenStack Development Mailing List (not for usage questions)" Cc:Subject: Re: [openstack-dev] [Horizon] Proposing Kenji Ishii for coreDate: Thu, Nov 17, 2016 11:51 AM  +1On Tue, Nov 15, 20

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

On 15/11/16 09:56, 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! However, one of the reasons it worked is becau

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

On 11/17/2016 05:24 PM, Zane Bitter wrote: > On 15/11/16 09:56, 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 i

[openstack-dev] [docs][upgrades] time to add official docs for upgrading services?

In the keystone docs we have notes about how to upgrade between releases [1], so does the nova team [2]. Is it time we create an official guides to [3] for this subject? [1] http://docs.openstack.org/developer/keystone/upgrading.html [2] http://docs.openstack.org/developer/nova/upgrade.html [3] h

Re: [openstack-dev] [murano] Nominating Felipe Monteiro for murano core

+1 Regards, Zhu Rong__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [daisycloud-core] Agenda for IRC meeting 0800UTC Nov. 18 2016

1) Roll Call 2) OPNFV: Escalator Support 3) OPNFV: CI Progress 4) Core Code Abstraction 5) Newton B.R., Zhijiang __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]

[openstack-dev] [nova] Problem with flavor's root_gb is 0 when instance booted from image.

Currently, a flavor with its root_gb is 0 should be only used for volume booted or for testing purposes: https://github.com/openstack/nova/blob/master/api-ref/source/parameters.yaml#L1782~L1787 I have a use case: Users may create some virtual machines for the processing of their business, these

Re: [openstack-dev] [kolla][git]How to backport commit after repo split

Yes. it works. Maybe we should add this into develop doc. thanks Paul. On Thu, Nov 17, 2016 at 11:00 PM, Paul Bourke wrote: > Seen as both repos stem from the same codebase, we should be able to just > cherry-pick changes as usual. If a fix comprises of a change to both kolla > and kolla-ansible

Re: [openstack-dev] [OpenStack-docs] [OpenStack-operators] [docs][upgrades] time to add official docs for upgrading services?

Good timing, I was about to send a follow-up email about this spec. I agree, this content needs to be more visible, which is why the spec proposed to move upgrade notes to the Upgrades chapter in the Operations Guide. However, it seems like the general consensus is to keep content in project repo

Re: [openstack-dev] [kolla][git]How to backport commit after repo split

At some point, it would be good if the kolla-ansible repo is added as a submodule of the kolla one to simplify things. Thanks, Juan > On Nov 17, 2016, at 22:19, Jeffrey Zhang wrote: > > Yes. it works. Maybe we should add this into develop doc. > > thanks Paul. > > On Thu, Nov 17, 2016 at 1

[openstack-dev] What's Up, Doc? 18 November

Hi everyone, Welcome to Ocata! It was great to catch up with many of you in Barcelona, and always refreshing to see the energy around our little project and catch that enthusiasm all over again :) Of course, Ocata is a *very* short cycle, so we've deliberately cut down our deliverables list to

[openstack-dev] [Horizon] End of week wrap-up

Hi folks, This week's Horizon goings-on saw several of the priority patches[1] for O-1 land, though more won't make it into that release. O-1 will be tagged in a few hours, once we sort out some issues with the npm test suite introduced with a recent patch. The team meeting this week[2] was a bus

[openstack-dev] [devstack] Specify OpenvSwitch version in local.conf

hi, all. I have a quick question about devstack. Can I specify OpenvSwitch version in local.conf when during the installation of devstack? I want to OVS 2.6.0 in my devstack. Can I specify it? Thanks Zhi Chang __ OpenStack

Re: [openstack-dev] [Neutron] Stepping down from core

Carl - You are an asset to Neutron community. Missing you as core is a hard thing. I wish a grand U turn again at your work towards Neutron. Wishing you all the best. /Trinath From: Carl Baldwin [mailto:[email protected]] Sent: Friday, November 18, 2016 12:13 AM To: OpenStack Development Mail

[openstack-dev] [tricircle] About playing Neutron LBaaS

Hi, all, Recently I try to configure and play Neutron LBaaS in one OpenStack instance and have some trouble when creating a load balancer. I install devstack with neutron networking as well as LBaaS in one VM. The detailed configuration of local.conf is pasted in the link http://paste.openstack.o