Re: [openstack-dev] [mistral][logo] Fwd: Mistral team draft logo

On 7 Dec 2016, at 20:37, Jay Pipes wrote: > > To me, it kind of looks like people jumping joyously off the top of a ferris > wheel. Haha :)) I didn’t have THIS kind of association in my mind. That’s funny. Thanks, Jay! Renat Akhmerov @Nokia

Re: [openstack-dev] [all][stable][ptls] Tagging liberty as EOL

On Tue, Nov 22, 2016 at 01:35:48PM +1100, Tony Breeds wrote: > I'll batch the removal of the stable/liberty branches between Nov 28th and Dec > 3rd (UTC+1100). Then during Decemeber I'll attempt to cleanup > zuul/layout.yaml > to remove liberty exclusions and jobs. This took longer as there

Re: [openstack-dev] [neutron][lbaas] New extensions for HAProxy driver based LBaaSv2

On Wed, 2016-12-07 at 06:50 -0800, Michael Johnson wrote: > Lubosz, > > I would word that very differently.  We are not dropping LBaaSv2 > support.  It is not going away.  I don't want there to be confusion > on > this point. > > We are however, moving/merging the API from neutron into Octavia.

[openstack-dev] [kolla] Kolla-Kubernetes tagging -> on the road to 1.0.0

Hey folks, Jeffrey delegated to me to determine the tagging structure for kolla-kubernetes. I was under the mistaken impression we need to tag 1.0.0 with the milestone tags (such as 1.0.0.0b2/1.0.0.0b3) for kolla-kubernetes. That is not the case. We will be tagging 0.4.0 next, then 0.5.0,

Re: [openstack-dev] [nova] placement/resource providers update 4

On 12/07/2016 07:06 PM, Matt Riedemann wrote: On 12/7/2016 2:40 AM, Sylvain Bauza wrote: FWIW, I think POST is not that complex and allows us to have room for further request information like traits, without defeating the purpose to have something RESTful. The proposal is up, comments welcome

Re: [openstack-dev] Questions about how to setup nova-lxd

On 12/7/2016 6:14 PM, zhihao wang wrote: Hi All I have installed openstack (Newton) on Ubuntu 16.04 on 4 Nodes, and I want to install and configure Nova-LXD on my exiting openstack, so that I can create and run Linux Container using LXD. I am wondering is there anyone know how to setup this,

Re: [openstack-dev] [tricircle]agenda of weekly meeting Dec.7

Hello, Dims, Thank you very much, interesting to know their work. Would like to get in touch with those folks. Best Regards Chaoyi Huang (joehuang) From: Davanum Srinivas [dava...@gmail.com] Sent: 07 December 2016 19:40 To: OpenStack Development Mailing

[openstack-dev] Questions about how to setup nova-lxd

Hi All I have installed openstack (Newton) on Ubuntu 16.04 on 4 Nodes, and I want to install and configure Nova-LXD on my exiting openstack, so that I can create and run Linux Container using LXD. I am wondering is there anyone know how to setup this, and is there any user guide for this?

Re: [openstack-dev] [nova] placement/resource providers update 4

On 12/7/2016 2:40 AM, Sylvain Bauza wrote: FWIW, I think POST is not that complex and allows us to have room for further request information like traits, without defeating the purpose to have something RESTful. The proposal is up, comments welcome https://review.openstack.org/#/c/392569/

Re: [openstack-dev] [acceleration]Team Biweekly Meeting 2016.12.07 agenda

Hi Miro, Yes it is, and please find all the necessary information on the wiki page :) On Thu, Dec 8, 2016 at 1:27 AM, Miroslav Halas wrote: > Howard, > > > > Thank you for sharing. I wasn’t able to join because I was quite confused > about the channel to join (tried

Re: [openstack-dev] [oslo][monasca] Can we uncap python-kafka ?

On Mon, Dec 05, 2016 at 04:03:13AM +, Keen, Joe wrote: > I wasn’t able to set a test up on Friday and with all the other work I > have for the next few days I doubt I’ll be able to get to it much before > Wednesday. It's Wednesday so can we have an update? Yours Tony. signature.asc

Re: [openstack-dev] [neutron] Vlan aware VMs or trunking

I think we will probably end up having to support the direct pass through anyway. The reason that landed in the spec is because someone claimed they had switches that couldn't do translation very well. We will just need volunteers to make the changes required on the Neutron side. On Wed, Dec 7,

Re: [openstack-dev] [Horizon] Draft team mascot

I also like Radomir’s version. From: "Ramirez, Eddie" Reply-To: OpenStack List Date: Wednesday, December 7, 2016 at 11:28 AM To: OpenStack List Subject: Re: [openstack-dev] [Horizon] Draft team

Re: [openstack-dev] [neutron] trunk api performance and scale measurments

Yes, this actually has to do with the policy check on any list of objects, including ports. The patch has to do with bypassing this individual object check for get and delete as the individual attribute checks are bypassed. The mentality is, if you have a list of objects with a base action of

Re: [openstack-dev] [Kuryr][Magnum] How stable is kuryr-kubernetes?

Hi Mike, On the Magnum side, myself and Hongbin Lu have been tracking the Kuryr driver for integration with Magnum. We did some early integration with the Mitaka version of the libnetwork driver but we left those patches as work-in-progress since there has been major redesign as you noted.

Re: [openstack-dev] [all] Creating a new IRC meeting room ?

On 2016-12-07 12:14:06 -0600 (-0600), Ian Cordasco wrote: [...] > So I'm all for non-official projects using their own channels for > meetings. My only wish (as someone working on a non-official > project) would be that we could use meeting bot the same way we > would in a meeting channel. It's

[openstack-dev] [ironic] unsupported drivers and their future

HI all, we (ironic community) some time ago decided [0] to require third-party CI for any driver that is present in the main ironic code tree. I'd like to discuss the state of currently unsupported drivers and how to proceed with them. Here is the current rundown, please correct me if I've got

Re: [openstack-dev] [Horizon] Draft team mascot

Very fixed, much color, so right. Wow. +1 Radomir’s From: Rob Cresswell (rcresswe) [mailto:rcres...@cisco.com] Sent: Wednesday, December 7, 2016 4:50 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Horizon]

Re: [openstack-dev] [neutron] Vlan aware VMs or trunking

On Wed, Dec 7, 2016 at 7:34 PM, Kevin Benton wrote: > >It work only when whole switch is aimed by single customer, it will not > work when several customers sharing the same switch. > > Do you know what vendors have this limitation? I know the broadcom > chipsets didn't prevent

Re: [openstack-dev] [all] Creating a new IRC meeting room ?

  -Original Message- From: Thierry Carrez Reply: OpenStack Development Mailing List (not for usage questions) Date: December 7, 2016 at 07:30:40 To: openstack-dev@lists.openstack.org Subject: 

Re: [openstack-dev] [neutron] Vlan aware VMs or trunking

>It work only when whole switch is aimed by single customer, it will not work when several customers sharing the same switch. Do you know what vendors have this limitation? I know the broadcom chipsets didn't prevent this (we allowed VLAN rewrites scoped to ports at Big Switch). If it's common to

Re: [openstack-dev] [acceleration]Team Biweekly Meeting 2016.12.07 agenda

Howard, Thank you for sharing. I wasn’t able to join because I was quite confused about the channel to join (tried openstack-acc and openstack-meetinc-cp). Is #openstack-cyborg the channel to use going forward? Thanks, Miro From: Zhipeng Huang [mailto:zhipengh...@gmail.com] Sent: Wednesday,

Re: [openstack-dev] [neutron] Vlan aware VMs or trunking

On Wed, Dec 7, 2016 at 7:12 PM, Kevin Benton wrote: > > > On Wed, Dec 7, 2016 at 8:47 AM, Vasyl Saienko > wrote: > >> @Armando: IMO the spec [0] is not about enablement of Trunks and >> baremetal. This spec is rather about trying to make user request

Re: [openstack-dev] [neutron] Vlan aware VMs or trunking

On Wed, Dec 7, 2016 at 8:47 AM, Vasyl Saienko wrote: > @Armando: IMO the spec [0] is not about enablement of Trunks and > baremetal. This spec is rather about trying to make user request with any > network configuration (number of requested NICs) to be able successfully >

Re: [openstack-dev] [Zun] About k8s integration

Hello Hongbin. See inline comments. Kind regards, Denis Makogon 2016-12-07 2:56 GMT+02:00 Hongbin Lu : > Hi all, > > > > This is a continued discussion of the k8s integration blueprint [1]. > Currently, Zun exposes a container-oriented APIs that provides service for >

Re: [openstack-dev] OpenStack Dev Digest November 26 to December 2

Gave the wrong link for the HTML verison before. Sorry! Actual HTML version: http://www.openstack.org/blog/2016/12/openstack-developer-mailing-list-digest-november-26-december-2/ On Mon, Dec 5, 2016 at 2:55 PM Jeremy Stanley wrote: > On 2016-12-05 20:45:08 + (+),

Re: [openstack-dev] [neutron] Vlan aware VMs or trunking

@Armando: IMO the spec [0] is not about enablement of Trunks and baremetal. This spec is rather about trying to make user request with any network configuration (number of requested NICs) to be able successfully deployed on ANY ironic node (even when number of hardware interfaces is less than

Re: [openstack-dev] [all] Creating a new IRC meeting room ?

On Wed, Dec 07, 2016 at 02:29:03PM +0100, Thierry Carrez wrote: > > So how about: > - we enable an #openstack-meeting-5 to instantly relieve scheduling pressure > - we allow teams to hold meetings in their project channel if they want > to (and show them all on the meeting agenda through the

Re: [openstack-dev] [acceleration]Team Biweekly Meeting 2016.12.07 agenda

Hi Team, Thanks for attending today's meeting and having a great discussion, please find the minutes at https://wiki.openstack.org/wiki/Cyborg/MeetingLogs On Wed, Dec 7, 2016 at 4:30 PM, Zhipeng Huang wrote: > Hi Team, > > Please find the initial agenda for today's

Re: [openstack-dev] [neutron] Vlan aware VMs or trunking

Just to be clear, in this case the switches don't support VLAN translation (e.g. [1])? Because that also solves the problem you are running into. This is the preferable path for bare metal because it avoids exposing provider details to users and doesn't tie you to VLANs on the backend. 1.

Re: [openstack-dev] [neutron][lbaas] New extensions for HAProxy driver based LBaaSv2

Completely true Michael, It’s like my mind is already in state that this project will loose support in next few releases. 2 are the standard for OpenStack. So like personally I don’t like to work and contribute to something what will be lost in future. And not like years future but near future

Re: [openstack-dev] [neutron] Vlan aware VMs or trunking

On 7 December 2016 at 04:02, Vasyl Saienko wrote: > Armando, Kevin, > > Thanks for your comments. > > To be more clear we are trying to use neutron trunks implementation with > baremetal servers (Ironic). Baremetal servers are plugged to Tor (Top of > the Rack) switch.

Re: [openstack-dev] [tripleo] Proposing Alex Schultz core on puppet-tripleo

10 positive replies, I think it's a yes :-) Thanks again Alex for your hard work, it's very appreciated. On Fri, Dec 2, 2016 at 4:16 PM, Giulio Fidente wrote: > On 12/01/2016 11:26 PM, Emilien Macchi wrote: >> >> Team, >> >> Alex Schultz (mwhahaha on IRC) has been active on

Re: [openstack-dev] [neutron][lbaas] New extensions for HAProxy driver based LBaaSv2

Lubosz, I would word that very differently. We are not dropping LBaaSv2 support. It is not going away. I don't want there to be confusion on this point. We are however, moving/merging the API from neutron into Octavia. So, during this work the code will be transitioning repositories and you

Re: [openstack-dev] [Performance][shaker] Triangular topology

- Mail original - > De: "Ilya Shakhat" > À: "OpenStack Development Mailing List (not for usage questions)" > > Envoyé: Mardi 6 Décembre 2016 14:39:28 > Objet: Re: [openstack-dev] [Performance][shaker] Triangular topology > >

Re: [openstack-dev] [mistral][logo] Fwd: Mistral team draft logo

To me, it kind of looks like people jumping joyously off the top of a ferris wheel. Best, -jay On 12/07/2016 02:21 AM, Renat Akhmerov wrote: Please provide your feedback on the draft logo for Mistral. My opinion: I think it looks pretty nice and it has valid associations in my mind with what

Re: [openstack-dev] [all] Creating a new IRC meeting room ?

Dolph Mathews wrote: > [...] > I think it honestly reflects our current breakdown of contributors & > collaboration. The artificial scarcity model only helps a vocal minority > with cross-project focus, and just results in odd meeting times for the > majority of projects that don't hold primetime

[openstack-dev] [Vitrage] [Aodh] Vitrage – Aodh Integration

Hi all, My name is Alexey Weyl and I am a core contributor in the Vitrage team. In the Austin Openstack summit we discussed with the Aodh team about creating a new alarm type, and after explaining it we got an approval [1]. Members from the Aodh team were in our design session in the Openstack

[openstack-dev] [networking-odl] Neutron with OpenDaylight Boron controller

Hi folks, We are trying to deploy Neutron with OpenDaylight Boron-0.5.0 controller using DevStack (master version) on Ubuntu 14.04 and there is a number of issues we face. First, we tried to deploy OpenDaylight with odl-ovsdb-openstack feature using the following local.conf [0]. In this case VMs

Re: [openstack-dev] [neutron] Vlan aware VMs or trunking

Armando, Kevin, Thanks for your comments. To be more clear we are trying to use neutron trunks implementation with baremetal servers (Ironic). Baremetal servers are plugged to Tor (Top of the Rack) switch. User images are spawned directly onto hardware. Ironic uses Neutron ML2 drivers to plug

Re: [openstack-dev] [tricircle]agenda of weekly meeting Dec.7

Chaoyi, Is there any interest in this work? http://cs.brown.edu/~rfonseca/pubs/yu16netex.pdf https://goo.gl/photos/hwHfMNo4xDMfVK8j8 Please let me know and i'll get you in touch with those folks. Thanks, Dims On Wed, Dec 7, 2016 at 3:00 AM, joehuang wrote: > Hello, team,

Re: [openstack-dev] [neutron] trunk api performance and scale measurments

On 12/6/16, 6:06 PM, "Tidwell, Ryan" wrote: > >I failed to make much mention of it in previous write-ups, but I also >encountered scale issues with listing ports after a certain threshold. I >haven’t gone back > to identify where the tipping point is, but I did notice that

[openstack-dev] [horizon] Please avoid blueprint overload

Hey all, So this was discussed at the summit, but its still being done; we keep hugely overloading blueprint scope. There are dozens of patches assigned to a vague "identity tables" blueprint, which was already marked Obsolete. Several of these were just small unrelated features that are

Re: [openstack-dev] [Horizon] Draft team mascot

Radomir’s version has my vote. On 7 Dec 2016, at 10:11, Radomir Dopieralski > wrote: Here, fixed. On Wed, Dec 7, 2016 at 10:54 AM, Radomir Dopieralski >wrote: That looks kinda like a

Re: [openstack-dev] [Horizon] Draft team mascot

Here, fixed. On Wed, Dec 7, 2016 at 10:54 AM, Radomir Dopieralski wrote: > That looks kinda like a white baboon. It definitely doesn't look like Doge > -- wrong color, wrong head. I think the legs are too long too. > > On Wed, Dec 7, 2016 at 10:31 AM, Timur Sufiev

Re: [openstack-dev] [Horizon] Draft team mascot

That looks kinda like a white baboon. It definitely doesn't look like Doge -- wrong color, wrong head. I think the legs are too long too. On Wed, Dec 7, 2016 at 10:31 AM, Timur Sufiev wrote: > I still think this one https://wtf.jpg.wtf/0c/10/1479414543- >

Re: [openstack-dev] [Horizon] Draft team mascot

I still think this one https://wtf.jpg.wtf/0c/10/1479414543-0c1052f7c2f9990b6b0c472076594cb1.jpeg is the best :). On Wed, Dec 7, 2016 at 1:07 AM Jason Rist wrote: > On 12/06/2016 01:48 PM, Richard Jones wrote: > > >> On 6 Dec 2016, at 20:19, Richard Jones

Re: [openstack-dev] [nova] Is this a correct use of scheduler hints and nova-scheduler

Thanks a for the information, I will propose a blueprint for the next cycle :) On Wed, Dec 7, 2016 at 4:38 PM, Sylvain Bauza wrote: > > > Le 07/12/2016 04:21, Zhenyu Zheng a écrit : > > Hi all, > > > > I want to ask a question about using scheduler-hints, could we add > >

Re: [openstack-dev] [nova] placement/resource providers update 4

Le 07/12/2016 01:07, melanie witt a écrit : > On Tue, 6 Dec 2016 16:04:14 -0500, Jay Pipes wrote: >> We're discussing only doing: >> >> GET /resource_providers? >> >> Once we start doing claims in the scheduler, we'll have the ability to >> do: >> >> POST /allocations >> { >> > all kinds

Re: [openstack-dev] [nova] Is this a correct use of scheduler hints and nova-scheduler

Le 07/12/2016 04:21, Zhenyu Zheng a écrit : > Hi all, > > I want to ask a question about using scheduler-hints, could we add > custom scheduler keys to work with our custom filters? Is it designed to > allow vendors add own custom filters and keys? > I tend to disagree with that approach from

[openstack-dev] [acceleration]Team Biweekly Meeting 2016.12.07 agenda

Hi Team, Please find the initial agenda for today's meeting at https://wiki.openstack.org/wiki/Meetings/CyborgTeamMeeting#Next_meeting_:_UTC_1500.2C_Dec_7th -- Zhipeng (Howard) Huang Standard Engineer IT Standard & Patent/IT Prooduct Line Huawei Technologies Co,. Ltd Email:

[openstack-dev] [tricircle]agenda of weekly meeting Dec.7

Hello, team, Bug-smash and meetup in last week is very good, let's continue the weekly meeting. Agenda of Dec.7 weekly meeting: 1. Bug smash and meetup summary 2. Ocata feature development review 3. legacy tables clean after splitting 4. Open Discussion How to join: # IRC