[openstack-dev] [devstack] [vitrage] install vitrage by devstack failed

Hi folks, While installing vitrage by devstack with a fresh clone I am hitting following error. What could be the problems here? Is there any configures i missed? Thank you for help~ ++./stack.sh:echo_summary:385 echo -e Initializing Vitrage 2016-04-22 07:38:02.311 | Initializing Vi

Re: [openstack-dev] [neutron] [nova] scheduling bandwidth resources / NIC_BW_KB resource class

Le 22/04/2016 02:49, Jay Pipes a écrit : On 04/20/2016 06:40 PM, Matt Riedemann wrote: Note that I think the only time Nova gets details about ports in the API during a server create request is when doing the network request validation, and that's only if there is a fixed IP address or specifi

[openstack-dev] [TripleO] Change 247669: Ceph Puppet: implement per-pool parameters:

Hi TripleO Team, If you could take care of ${subject}, it would be nice. [1] https://review.openstack.org/#/c/247669 Cheers, S __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ.

[openstack-dev] [Fuel] [Ci] Re-trigger by keyword in comment

Hi to all, please be informed that recently we've merged a patch[0] that allow to re-trigger fuel-ci[1] tests by commenting review with keywords "fuel: recheck"[2] For now actual list of Jenkins jobs with retrigger by "fuel: recheck"[2] keyword looks like: 7.0.verify-python-fuelclient 8.0.fuel-l

Re: [openstack-dev] More on the topic of DELIMITER, the Quota Management Library proposal

I strongly agree with Jay on the points related to "no reservation" , keeping the interface simple and the role for Delimiter (impose limits on resource consumption and enforce quotas). The point to keep user quota, tenant quotas in Keystone sounds interestring and would need support from Keystone

Re: [openstack-dev] [nova][neutron] os-vif status report

On Fri, Apr 22, 2016 at 04:25:54AM +, Angus Lees wrote: > In case it wasn't already assumed, anyone is welcome to contact me directly > (irc: gus, email, or in Austin) if they have questions or want help with > privsep integration work. It's early days still and the docs aren't > extensive (ah

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

On 04/22/2016 02:42 AM, Cathy Zhang wrote: > So let’s meet at "Salon C" for lunch from 12:30pm~1:50pm on Wednesday > and then continue the discussion at Room 400 at 3:10pm Thursday. > > Since Salon C is a big room, I will put a sign “Common Flow Classifier > and OVS Agent Extension” on the table

[openstack-dev] [Security][Barbican][all] Bring your own key fishbowl sessions

We have two BYOK sessions scheduled for the design summit, one on the Barbican track and one on the Security track. [1] Security: Wednesday 5:20pm-6:00pm Hilton Austin - MR 408 [2] Barbican: Thursday 3:10pm-3:50pm Hilton Austin - MR 406 I'd like to suggest two different approaches to getting the

Re: [openstack-dev] [all] [devstack] Adding example "local.conf" files for testing?

Absolutely, yes +1 Paul From: ZhiQiang Fan [mailto:aji.zq...@gmail.com] Sent: 21 April 2016 12:34 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [all] [devstack] Adding example "local.conf" files for testing? +1 more example and documentation are

[openstack-dev] [tripleo] Summit session etherpads

All, In preparation for our sessions next week, I created some etherpads and linked them all here: https://wiki.openstack.org/wiki/Design_Summit/Newton/Etherpads#TripleO Note that each one has the initial session description cut/pasted, and I've nominated some initial drivers for each session -

[openstack-dev] [watcher] Watcher meetings in Austin

Hi Watcher team, We will have a couple of meetings next week to discuss Watcher achievements during the Mitaka cycle and define priorities for Newton. Meetings will be held in the developer lounge in Austin https://wiki.openstack.org/wiki/Design_Summit/Newton/Etherpads#Watcher A proposed open ag

Re: [openstack-dev] [all] [devstack] Adding example "local.conf" files for testing?

Excellent idea and good for any new users to get everything they need in devstack with example local.conf +1 Thanks & Regards, J. Venkata Mahesh [cid:image001.jpg@01D19CA8.C9008BB0] From: Murray, Paul (HP Cloud) [mailto:pmur...@hpe.com] Sent: Friday, April 22, 2016 3:01 PM To: OpenStack Develo

[openstack-dev] [kolla] centos-binary-neutron-openvswitch-agent

Hi, After I deployed OpenStack with Kolla the first time, I found that the centos-binary-neutron-openvswitch-agent container mainly in restarting status. Is it OK? Or can you show me some way on how to figure out and resolve this kind of problems? Many thanks! [root@forimg tools]# docker

Re: [openstack-dev] [all] [devstack] Adding example "local.conf" files for testing?

This is so great. Then you should also know that the combination you are trying in local.conf has worked and your problem is perhaps not that one. +1 Br, Tomi > -Original Message- > From: EXT Markus Zoeller [mailto:mzoel...@de.ibm.com] > Sent: Thursday, April 14, 2016 10:32 AM > To: open

Re: [openstack-dev] [Heat][Horizon] Liberty horizon and get_file workaround?

There’s a patch to fix this problem in mitaka https://review.openstack.org/#/c/241700/ , Need to here more feedbacks about backport it to liberty release https://review.openstack.org/#/c/260436/ . Best Regar

Re: [openstack-dev] Summit Core Party after Austin

On 21/04/16 13:40 -0400, Doug Hellmann wrote: Excerpts from Thierry Carrez's message of 2016-04-21 18:22:53 +0200: Michael Krotscheck wrote: > So, HPE is seeking sponsors to continue the core party. The reasons are > varied - internal sponsors have moved to other projects, the Big Tent > has dra

Re: [openstack-dev] [kolla] centos-binary-neutron-openvswitch-agent

no. it is not OK. please attach the log of the neutron_openvswitch_agent . You can get it by using `docker logs neutron_openvswitch_agent` On Fri, Apr 22, 2016 at 5:50 PM, wrote: > Hi, > > After I deployed OpenStack with Kolla the first time, I found that the > centos-binary-neutron-openvswitch-

Re: [openstack-dev] [kolla] deploy kolla on ppc64

this should be a bug. we do not support the custom base image now. I will try to fix this, anyway. On Fri, Apr 22, 2016 at 5:29 AM, Franck Barillaud wrote: > I've been using Kola to deploy Mitaka on x86 and it works great. Now I > would like to do the same thing on IBM Power8 systems (ppc64). I'

Re: [openstack-dev] Summit Core Party after Austin

To all who have said the Core Party was a bad thing, let me echo Sean's feelings, and add that I actually liked the core parties more than any of the others, and actually found them to be a very good thing. I too got to meet people who I would normally not have had a chance to have a conversatio

Re: [openstack-dev] [stable][Openstack-stable-maint] Stable check of openstack/trove failed

The links being referenced in this email for the UNSTABLE outcomes appear to be missing. Also, I notice that a whole bunch of stable jobs failed around the same time. Would someone on stable-maint please confirm whether there was something environmental going on at the time before teams start di

Re: [openstack-dev] [magnum][app-catalog][all] Build unified abstraction for all COEs

For those interested in one aspect of this discussion (a common compute API for bare-metal, VM's and containers), there's a review of a spec in Trove [1], and a session at the summit [2]. Please join [2] if you are able Trove Container Support Thursday, April 28, 9:50am-10:30am

[openstack-dev] [horizon] Summit next week - Meetings cancelled

Hi all, Due to the summit next week, both of the usual Wednesday meetings are cancelled. Rob __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsub

Re: [openstack-dev] [stable][Openstack-stable-maint] Stable check of openstack/trove failed

Amrith Kumar wrote: The links being referenced in this email for the UNSTABLE outcomes appear to be missing. Also, I notice that a whole bunch of stable jobs failed around the same time. Would someone on stable-maint please confirm whether there was something environmental going on at the

Re: [openstack-dev] [stable][Openstack-stable-maint] Stable check of openstack/trove failed

On 04/22/2016 01:25 PM, Amrith Kumar wrote: The links being referenced in this email for the UNSTABLE outcomes appear to be missing. Also, I notice that a whole bunch of stable jobs failed around the same time. Would someone on stable-maint please confirm whether there was something environmen

Re: [openstack-dev] [TripleO] Change 247669: Ceph Puppet: implement per-pool parameters:

On Fri, Apr 22, 2016 at 3:51 AM, Shinobu Kinjo wrote: > Hi TripleO Team, > > If you could take care of ${subject}, it would be nice. > > [1] https://review.openstack.org/#/c/247669 > Well, the patch is in merge conflict, and has negative review from Cyril. I would suggest the committer, Felipe Al

[openstack-dev] [puppet] Summit etherpads + schedule

Hi, The schedule & etherpads for Puppet OpenStack sessions are documented here: https://wiki.openstack.org/wiki/Design_Summit/Newton/Etherpads#Puppet_OpenStack During the summit, we won't do the weekly meeting, the next one is May 3rd. Have a safe tip and see you next week! -- Emilien Macchi _

[openstack-dev] [TripleO] TripleO UI Demo

Hello all, I've created a demo video which shows latest changes in TripleO UI. You can watch it here: https://youtu.be/1Lc04DKGxCg -- Jirka __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: open

Re: [openstack-dev] [neutron] use hostname as nameserver when creating subnet

Sun zhengnan wrote: Hi all Can I use hostname as a nameserver when creating or updating a subnet? From API perspective, yes... I noticed that both ip and hostname are checked in neutron/api/attributes.py with _validate_nameservers. But only ip address is allowed in _validate_subnet in db

Re: [openstack-dev] [Fuel] [Ci] Re-trigger by keyword in comment

Hi Dmitry, Thank you for update. Is it intended that master.fuel-web.pkgs.ubuntu.review_fuel_web_deploy job for code requests to fuel-web runs at every recheck now? Before the change it was executed for new patch/r

Re: [openstack-dev] [Fuel] [Ci] Re-trigger by keyword in comment

Aleksey, actually I want to extend the test group we run there. Many changes coming out of nailgun are actually creating BVT failures that can only be prevented by such tests. One such extension would be adding a plugin to the deployment to ensure that basic plugins are still deployable. I'm ok wi

Re: [openstack-dev] Summit Core Party after Austin

On 18:57 Apr 21, Thierry Carrez wrote: > Thierry Carrez wrote: > >[...] > >I think it's inappropriate because it gives a wrong incentive to become > >a core reviewer. Core reviewing should just be a duty you sign up to, > >not necessarily a way to get into a cool party. It was also a bit > >exclusi

Re: [openstack-dev] [magnum][app-catalog][all] Build unified abstraction for all COEs

On Thu, Apr 21, 2016 at 9:30 PM, Fox, Kevin M wrote: > +1. > > From: Hongbin Lu [hongbin...@huawei.com] > Sent: Thursday, April 21, 2016 7:50 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [magnum][app-c

Re: [openstack-dev] [neutron] [nova] scheduling bandwidth resources / NIC_BW_KB resource class

On 4/22/2016 2:48 AM, Sylvain Bauza wrote: Le 22/04/2016 02:49, Jay Pipes a écrit : On 04/20/2016 06:40 PM, Matt Riedemann wrote: Note that I think the only time Nova gets details about ports in the API during a server create request is when doing the network request validation, and that's on

[openstack-dev] [Neutron][ML2][API]Binding a port to multiple hosts

After some discussion how portbinding handling could be improved during live migration, the following idea came up: Why not bind a port to both, the source and the target host during migration? This would allow us to set the portbinding for the target already in pre_live_migration. Doing so, we

[openstack-dev] [Fuel][plugins] Changing role regex from '*' to ['/.*/'] breaks MOS compatibility

Hello, deployment_tasks.yaml for the fuel-plugin-lma-collector plugin has this task definition: - id: lma-aggregator type: puppet version: 2.0.0 requires: [lma-base] required_for: [post_deployment_end] role: '*' parameters: puppet_manifest: puppet/manifests/aggregator.pp puppe

Re: [openstack-dev] [Fuel][plugins] Changing role regex from '*' to ['/.*/'] breaks MOS compatibility

Hello! I think your problem is related to the: https://bugs.launchpad.net/fuel/+bug/1570846 Fix to stable/mitaka was commited 20/04/2016 https://review.openstack.org/#/c/307658/ Could you, please, try to apply this patch and reply does it help or not. On Fri, Apr 22, 2016 at 5:40 PM, Guillaume

Re: [openstack-dev] [tc] Leadership training dates - please confirm attendance

On Thu, Apr 21, 2016 at 10:42 AM, Doug Hellmann wrote: > > Excerpts from Colette Alexander's message of 2016-04-21 08:07:52 -0700: > > > > > Hi everyone, > > > > Just checking in on this - if you're a current or past member of the TC and > > haven't yet signed up on the etherpad [0] and would like

Re: [openstack-dev] [neutron] [nova] scheduling bandwidth resources / NIC_BW_KB resource class

Le 22/04/2016 16:14, Matt Riedemann a écrit : On 4/22/2016 2:48 AM, Sylvain Bauza wrote: Le 22/04/2016 02:49, Jay Pipes a écrit : On 04/20/2016 06:40 PM, Matt Riedemann wrote: Note that I think the only time Nova gets details about ports in the API during a server create request is when d

Re: [openstack-dev] [Glance] Glare and future of artifacts in OpenStack.

Mike, thanks for the update. Very helpful. I did have a couple concerns, though, from the slides... 1) On Slide 8, you have a bullet point: "Quoting. We want to implement powerful nested quota support, rather than have one global quota config." I do not believe that Glare should have anythin

Re: [openstack-dev] More on the topic of DELIMITER, the Quota Management Library proposal

On 04/22/2016 07:51 AM, Amrith Kumar wrote: If it doesn’t make it harder, I would like to see if we can make the quota API take care of the ordering of requests. i.e. if the quota API is an extension of Jay’s example and accepts some data structure (dict?) with all the claims that a project wants

Re: [openstack-dev] [Security][Barbican][all] Bring your own key fishbowl sessions

> Thoughts? Is anyone interested in the pull model or actually implementing it? I say if the answer to that is no then only discuss the push model. Note that I am having a talk on BYOK on Tuesday at 11:15. My talk will go over provider key management, the push model, and the pull model. There are

[openstack-dev] [release][stable] networking-powervm 2.0.0 release (mitaka)

We are excited to announce the release of: networking-powervm 2.0.0: PowerVM Neutron ML2 Agent for OpenStack Neutron. This release is part of the mitaka stable release series. For more details, please see below. Changes in networking-powervm 1.0.0rc1..2.0.0 -

Re: [openstack-dev] [Fuel][plugins] Changing role regex from '*' to ['/.*/'] breaks MOS compatibility

Thanks Ilya! We're testing and will be reporting back on monday. Simon On Fri, Apr 22, 2016 at 4:53 PM, Ilya Kutukov wrote: > Hello! > > I think your problem is related to the: > https://bugs.launchpad.net/fuel/+bug/1570846 > > Fix to stable/mitaka was commited 20/04/2016 > https://review.openst

Re: [openstack-dev] More on the topic of DELIMITER, the Quota Management Library proposal

to that. It is sorely needed. My way of trying to go there complicated the API too much. Let me know if I can help in any way, but you already knew that. Thanks, -amrith > -Original Message- > From: Jay Pipes [mailto:jaypi...@gmail.com] > Sent: Friday, April 22, 2016 11:19 AM > To

Re: [openstack-dev] Question about OpenStack Code of Conduct

On 04/21/2016 02:04 PM, Jeremy Stanley wrote: > On 2016-04-21 17:54:56 + (+), Adrian Otto wrote: >> Below is an excerpt from: >> https://www.openstack.org/legal/community-code-of-conduct/ >> >> "When we disagree, we consult others. Disagreements, both social >> and technical, happen all the

Re: [openstack-dev] [Fuel] [Ci] Re-trigger by keyword in comment

Matthew, It's great that we have this test. But why to rerun it for no changes? It was executed only when a new patch was published for CR or CR was rebased. Now it is executed on "fuel:recheck". Agree, adding a plugin would be helpful. Aleksey Kasatkin On Fri, Apr 22, 2016 at 4:19 PM, Matth

[openstack-dev] [Fuel][MySQL][DLM][Oslo][DB][Trove][Galera][operators] Multi-master writes look OK, OCF RA and more things

[crossposting to openstack-operat...@lists.openstack.org] Hello. I wrote this paper [0] to demonstrate an approach how we can leverage a Jepsen framework for QA/CI/CD pipeline for OpenStack projects like Oslo (DB) or Trove, Tooz DLM and perhaps for any integration projects which rely on distribute

Re: [openstack-dev] [Heat][Horizon] Liberty horizon and get_file workaround?

On 22/04/16 01:06, Jason Pascucci wrote: Hi, I wanted to add my yaml as new resources (via /etc/heat/environment.d/default.yaml, but we use some external files in the OS::Nova::Server personality section. I think you're describing this bug: https://bugs.launchpad.net/heat/+bug/1454401 There

Re: [openstack-dev] [magnum][app-catalog][all] Build unified abstraction for all COEs

Thanks Amirth… I’m glad to see it hasn’t changed much since I was involved with Trove in its early days. What you are describing makes sense, and I view it as an LCD for managing common things across the database types, not an LCD for the database interaction performed by the user/client interacti

Re: [openstack-dev] Summit Core Party after Austin

Excerpts from Thierry Carrez's message of 2016-04-21 09:22:53 -0700: > Michael Krotscheck wrote: > > So, HPE is seeking sponsors to continue the core party. The reasons are > > varied - internal sponsors have moved to other projects, the Big Tent > > has drastically increased the # of cores, and th

Re: [openstack-dev] [magnum][app-catalog][all] Build unified abstraction for all COEs

Keith, I was with you all the way till your last sentence ... > -Original Message- > From: Keith Bray [mailto:keith.b...@rackspace.com] > Sent: Friday, April 22, 2016 11:53 AM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [magnum][app-

Re: [openstack-dev] [Glance] Glare and future of artifacts in OpenStack.

On 04/22/2016 10:10 AM, Jay Pipes wrote: 3) On Slide 9, you have this in "future work (in Newton)": "Tasks (asynchronous workflows) support." Please, please, please NO. There is absolutely no reason to couple a service that operates on artifacts in an asynchronous fashion with a service that

Re: [openstack-dev] [magnum][app-catalog][all] Build unified abstraction for all COEs

Thanks for the invite. I'll try my best to be there. :) As for the rest of the comments below, I think they are spot on, and I very much appreciate those features in Trove. It makes for a very nice way of dealing with databases. Thanks to the trove team for all the hard work put in to make it w

Re: [openstack-dev] Summit Core Party after Austin

The Vancouver core party was a fantastic opportunity to meet some very smart people and learn a lot about the projects they worked on. It was probably one of the most useful parts of the summit, certainly more so than the greasy marketing party, and arguably a much better use of developer time.

Re: [openstack-dev] [trove][magnum][app-catalog][all] Build unified abstraction for all COEs

Thanks Kevin, much appreciated. I've added [trove] to the subject so it shows up on their mail filters. -amrith > -Original Message- > From: Fox, Kevin M [mailto:kevin@pnnl.gov] > Sent: Friday, April 22, 2016 1:11 PM > To: OpenStack Development Mailing List (not for usage questions)

[openstack-dev] [Neutron] Neutron client and plan to transition to OpenStack client

Hi Neutrinos, During the Mitaka release the team sat together to figure out a plan to embrace the OpenStack client and supplant the neutron CLI tool. Please note that this does not mean we will get rid of the openstack-neutronclient repo. In fact we still keep python client bindings and keep the

[openstack-dev] [oslo] No weekly meeting next week

Howday folks, Since there is a summit next week it is highly likely that we will not have a weekly meeting next week (since there just won't be enough people online) so I just wanted to make sure people don't show up (although folks that aren't going to the summit are welcome to still show up

[openstack-dev] [fuel] Weekly meeting canceled for 4/28

We discussed in the meeting next week that, we will cancel the next week's IRC meeting due to summit activities. The meeting will resume its regular schedule on May-5 -- -- Andrew Woodward Mirantis Fuel Community Ambassador Ceph Community _

[openstack-dev] [murano] No weekly meetings on April 26th and May 3d

Due to summit, long flights and holidays, that happen in Russia and Ukraine early in May there would be no weekly meetings on 26th and 3d. --  Kirill Zaitsev Software Engineer Mirantis, Inc__ OpenStack Development Mailing Lis

[openstack-dev] [kolla][kubernetes] Mirantis participation in kolla-mesos project and shift towards Kubernetes

Hi folks, I’ve been approached by multiple people asking questions about what is happening with Mirantis engineers activity around the kolla-mesos project we started and I do feel that I owe an explanation to the community. Indeed during the last few months we significantly reduced the amount of

Re: [openstack-dev] [kolla] kolla-mesos development being scaled back

Hi folks, just posting a link to the email covering Mirantis position on it. http://lists.openstack.org/pipermail/openstack-dev/2016-April/093143.html On Wed, Apr 20, 2016 at 9:51 AM, Gerard Braad wrote: > On Wed, Apr 20, 2016 at 2:40 PM, Steven Dake (stdake) > wrote: > > Unfortunately > > the

[openstack-dev] [keystone] weekly meeting canceled on 4/26

as per usual, we will cancel the meeting the week of the summit - see you in austin! Steve __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscr

Re: [openstack-dev] summit tools

On 04/20/2016 06:53 PM, Tony Breeds wrote: > On Wed, Apr 20, 2016 at 04:13:38PM +, Neil Jerram wrote: >> A couple of questions about our Austin-related planning tools... >> >> - Can one's calendar at >> https://www.openstack.org/summit/austin-2016/summit-schedule/#day=2016-04-25 >> be exporte

[openstack-dev] [Congress] No meeting on April 27

No meeting for next week (April 27), since we'll be in Austin at the summit. We will send out an update about what happened during the summit next week. Tim __ OpenStack Development Mailing List (not for usage questions) Unsu

[openstack-dev] [trove] No weekly Trove meeting next week

As several of us will be at summit next week, there will be no weekly Trove meeting. The complete list of Trove design summit sessions can be found at [1]. There are also several talks about Trove [2] ... [5]. Thanks, -amrith [1] https://wiki.openstack.org/wiki/Design_Summit/Newton/Etherpads#T

Re: [openstack-dev] [Heat][Horizon] Liberty horizon and get_file workaround?

Based from stable policy, we don't backport new features [1]. The new feature also reads from an external URL, which I think might be too risky to add to stable branches. -Lin [1] http://docs.openstack.org/project-team-guide/stable-branches.html#review-guidelines On Fri, Apr 22, 2016 at 3:14 AM,

Re: [openstack-dev] [kolla][kubernetes] Mirantis participation in kolla-mesos project and shift towards Kubernetes

Sergey This is very interesting and exciting In fact, a few colleagues and myself actually plan to present at the Austin OS summit [1] around with the self-healing OpenStack Control Plane, a taste of which can be found here [2]. It’s a fully clustered, HA control plane PoC that we’ve put to

[openstack-dev] [nova] Distributed Database

OK, so I know that Friday afternoons are usually the worst times to write a blog post and start an email discussion, and that the Friday immediately before a Summit is the absolute worst, but I did it anyway. http://blog.leafe.com/index.php/2016/04/22/distributed_data_nova/ Summary: we are creati

Re: [openstack-dev] [nova] Distributed Database

Ed, fyi, i just got a ping about this effort: https://github.com/BeyondTheClouds/BeyondTheClouds.github.io/raw/master/DOCS/PAPERS/2015/nova-description/BTC-DISCOVERY-Overview.pdf https://github.com/BeyondTheClouds/rome https://beyondtheclouds.github.io/ They have a WG session: https://www.openst

Re: [openstack-dev] [Security][Barbican][all] Bring your own key fishbowl sessions

So that's one vote for option A and one vote for another vote :) On 22 Apr 2016 4:25 p.m., "Nathan Reller" wrote: > > Thoughts? > > Is anyone interested in the pull model or actually implementing it? I > say if the answer to that is no then only discuss the push model. > > Note that I am having a

Re: [openstack-dev] [nova] Distributed Database

On 04/22/2016 03:27 PM, Ed Leafe wrote: OK, so I know that Friday afternoons are usually the worst times to write a blog post and start an email discussion, and that the Friday immediately before a Summit is the absolute worst, but I did it anyway. http://blog.leafe.com/index.php/2016/04/22/dist

Re: [openstack-dev] [infra][devstack] stable/kilo devstack fails with pkg_resources.ContextualVersionConflict

On Thu, 21 Apr 2016 15:12:53 +1000 Tony Breeds wrote: > On Tue, Apr 19, 2016 at 01:14:34PM +0200, Lajos Katona wrote: > > Hi, > > > > In our internal CI system we realized that stable/kilo devstack > > fails with the following stack trace: > > > > > It seems that the root cause is that test

Re: [openstack-dev] [Neutron] Neutron client and plan to transition to OpenStack client

FYI: I've pushed a series of WIP patch sets [1], [2] and [3] to enable python-neutronclient OSC plugins. I've used "openstack network agent list" as the initial OSC plugin command example. Hopefully these will help during the discussions at the summit. [1] https://review.openstack.org/#/c/3095

Re: [openstack-dev] [release] release hiatus

Excerpts from Tony Breeds's message of 2016-04-22 09:22:59 +1000: > On Thu, Apr 21, 2016 at 02:13:15PM -0400, Doug Hellmann wrote: > > The release team is preparing for and traveling to the summit, just as > > many of you are. With that in mind, we are going to hold off on > > releasing anything un

Re: [openstack-dev] [Security][Barbican][all] Bring your own key fishbowl sessions

Can you please give a little more detail on what its about? Does this have any overlap with the instance user session: https://www.openstack.org/summit/austin-2016/summit-schedule/events/9485 Thanks, Kevin From: Rob C [hyaku...@gmail.com] Sent: Friday, April 22,

Re: [openstack-dev] [nova] Distributed Database

On Fri, Apr 22, 2016, at 04:27 PM, Ed Leafe wrote: > OK, so I know that Friday afternoons are usually the worst times to > write a blog post and start an email discussion, and that the Friday > immediately before a Summit is the absolute worst, but I did it anyway. > > http://blog.leafe.com/inde

Re: [openstack-dev] Summit Core Party after Austin

Excerpts from Chivers, Doug's message of 2016-04-22 10:17:45 -0700: > The Vancouver core party was a fantastic opportunity to meet some very smart > people and learn a lot about the projects they worked on. It was probably one > of the most useful parts of the summit, certainly more so than the g

Re: [openstack-dev] [Security][Barbican][all] Bring your own key fishbowl sessions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 No conflicts with your cross-project session as far as I can tell. In a nutshell BYOK-Push is a model where the customer retains full control of their cryptographic keys. The customer is expected to provide the necessary keys each and every time a

Re: [openstack-dev] [nova] Distributed Database

On 04/22/2016 04:32 PM, Andrew Laski wrote: On Fri, Apr 22, 2016, at 04:27 PM, Ed Leafe wrote: OK, so I know that Friday afternoons are usually the worst times to write a blog post and start an email discussion, and that the Friday immediately before a Summit is the absolute worst, but I did i

Re: [openstack-dev] [nova] Distributed Database

> However I do want to point out that cells v2 is not just about dealing > with scale in the database. The message queue is another consideration, > and as far as I know there is not an analog to the "distributed > database" option available for the persistence layer. Yeah, it's actually *mostly*

Re: [openstack-dev] [Neutron] Neutron client and plan to transition to OpenStack client

On 22 April 2016 at 13:58, Richard Theis wrote: > FYI: I've pushed a series of WIP patch sets [1], [2] and [3] to enable > python-neutronclient OSC plugins. I've used "openstack network agent list" > as the initial OSC plugin command example. Hopefully these will help > during the discussions at

Re: [openstack-dev] Summit Core Party after Austin

Hi all, On 22/04/16 16:40, Clint Byrum wrote: But in the mean time, maybe we can just send this message to party planners: Provide us with interesting spaces to converse and bond in, and we will be happier. Spoke with the party planners and got the inside gossip :) The good news: for the Aust

Re: [openstack-dev] Summit Core Party after Austin

On Fri, Apr 22, 2016 at 2:58 PM, Tom Fifield wrote: > Hi all, > > On 22/04/16 16:40, Clint Byrum wrote: > >> But in the mean time, maybe we can just send this message >> to party planners: Provide us with interesting spaces to converse and >> bond in, and we will be happier. >> > > Spoke with the

Re: [openstack-dev] [Security][Barbican][all] Bring your own key fishbowl sessions

Oh, I think I understand. something like: You set up your private cloud with a public region ala K2K federation. The other Cloud then shows up as another region in your cloud. This would then allow your barbican in one region to be accessible to vm's launched in the public region? Kind of a cr

Re: [openstack-dev] [nova] Distributed Database

On Fri, Apr 22, 2016 at 2:57 PM, Dan Smith wrote: > > However I do want to point out that cells v2 is not just about dealing > > with scale in the database. The message queue is another consideration, > > and as far as I know there is not an analog to the "distributed > > database" option availab

[openstack-dev] Thank you to our Event Planners

I would like to take a moment to say thank you to all the folks in our community who take the time and trouble to plan events for all of us to enjoy. Events of all kinds help us to learn and grow by extending ourselves and learning about different ways of doing things. We get to interact with new f

Re: [openstack-dev] [nova] Distributed Database

> This would be a very interesting direction to explore. Focus on the pain > points of the message queue and then look at addressing the beast that > is the database layer separately. I am going to toss support in behind a > lot of what has been said in this thread already. But I really wanted to >

[openstack-dev] [neutron] [networking-sfc] Network-sfc project f2f2 meet-up place and time

Hi Everyone, As we discussed in our project meeting, we should have a f2f meeting during the summit. let's meet at "Salon C" for lunch from 12:30pm~1:50pm on Tuesday. Since Salon C is a big room, I will put a sign "Networking-SFC Project Meet-Up" on the table. Thanks, Cathy ___

Re: [openstack-dev] [Neutron] Neutron client and plan to transition to OpenStack client

Hi Richard, Thanks for the information :) Was waiting for it. On Sat, Apr 23, 2016 at 3:27 AM, Armando M. wrote: > > > On 22 April 2016 at 13:58, Richard Theis wrote: > >> FYI: I've pushed a series of WIP patch sets [1], [2] and [3] to enable >> python-neutronclient OSC plugins. I've use

Re: [openstack-dev] Thank you to our Event Planners

On 04/22/2016 05:22 PM, Anita Kuno wrote: I would like to take a moment to say thank you to all the folks in our community who take the time and trouble to plan events for all of us to enjoy. Events of all kinds help us to learn and grow by extending ourselves and learning about different ways of

Re: [openstack-dev] [nova] Distributed Database

On 04/22/2016 05:29 PM, Dan Smith wrote: This would be a very interesting direction to explore. Focus on the pain points of the message queue and then look at addressing the beast that is the database layer separately. I am going to toss support in behind a lot of what has been said in this threa

Re: [openstack-dev] [Neutron] Neutron client and plan to transition to OpenStack client

thanks to richard, tangchen, reepid and others for picking this up and running with it; and thanks to armando for embracing OSC and putting it in neutron's plan. On Fri, Apr 22, 2016 at 6:33 PM, reedip banerjee wrote: > Hi Richard, > Thanks for the information :) > > Was waiting for it. > >

Re: [openstack-dev] Summit Core Party after Austin

Many thanks Tom! > -Original Message- > From: Tom Fifield [mailto:t...@openstack.org] > Sent: Friday, April 22, 2016 5:59 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] Summit Core Party after Austin > > Hi all, > > On 22/04/16 16:40, Clint Byrum wrote: > > But

[openstack-dev] kolla-kubernetes [kolla][kubernetes]

Just want to give everyone a heads up about a schedule change for kolla summit sessions. Kolla-kubernetes was a kolla spec [1] that we had intended to cover at summit in a design session. We are going to change it to a fish bowl session instead to be held on Wednesday at 9am and the documentatio

[openstack-dev] [lbaas][octavia] No Octavia IRC meeting 4/27/16

Since most of us will be attending the summit next week I am canceling the Octavia IRC meeting on April 27th. Michael __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.op

Re: [openstack-dev] [neutron] [networking-sfc] Network-sfc project f2f2 meet-up place and time

Sounds good. Thanks Cathy. Anil On Fri, Apr 22, 2016 at 3:30 PM, Cathy Zhang wrote: > Hi Everyone, > > > > As we discussed in our project meeting, we should have a f2f meeting > during the summit. > > let’s meet at "Salon C" for lunch from 12:30pm~1:50pm on Tuesday. > > Since Salon C is a big r

[openstack-dev] [kolla][vote] Place kolla-mesos in openstack-attic

Fellow Core Reviewers, Since many of the engineers working on the kolla-mesos repository are moving on to other things[1], possibly including implementing Kubernetes as an underlay for OpenStack containers, I propose we move the kolla-mesos repository into the attic[2]. This will allow folks t

[openstack-dev] [kubernetes] Introducing the Kubernetes OpenStack Special Interest Group

Colleagues, I'm happy to announce within the OpenStack community the Kubernetes OpenStack Special Interest Group. Kubernetes Community currently runs to the deeper integration between OpenStack and Kubernetes and one of the main aims now - to work on enabling OpenStack as a platform for running Ku

Re: [openstack-dev] [kolla][vote] Place kolla-mesos in openstack-attic

+1 since Mirantis was only company actively developing kolla-mesos. If anyone want's to take over kolla-mesos, now is the time. On 22 April 2016 at 19:08, Steven Dake (stdake) wrote: > Fellow Core Reviewers, > > Since many of the engineers working on the kolla-mesos repository are moving > on to

Re: [openstack-dev] [ironic][nova][horizon] Serial console support for ironic instances

Hi all, Thank you Yuiko. I'll join the console session. See you at the venue. (2)Add console drivers using ironic-console-server https://review.openstack.org/#/c/302291/ (ironic-console-server) https://review.openstack.org/#/c/306754/ (console logging spec) https://review.openstack.org/#/c/306755

  1   2   >