Re: [openstack-dev] [heat] Changing the default Server/SoftwareDeployment transports?

On 22/01/16 04:36, Steven Hardy wrote: Hi all, Wanted to start some discussion re $subject, context is: https://bugs.launchpad.net/heat/+bug/1507568 Here, we're hitting issues because by default OS::Nova::Server uses the POLL_SERVER_CFN transport. This made sense back when the

Re: [openstack-dev] [nova] need your help on bug #1449498

On 1/19/2016 6:32 AM, Zhenyu Zheng wrote: This is a bug, as tenant and user is maintained by keystone and quota are stored in nova db, so it has the cleanup problems. On Tue, Jan 19, 2016 at 8:12 PM, jialiang_song517 > wrote: __

Re: [openstack-dev] [Nova] sponsor some LVM development

On 22 Jan 2016 17:43, "James Bottomley" < james.bottom...@hansenpartnership.com> wrote: > > On Fri, 2016-01-22 at 14:58 +0100, Premysl Kouril wrote: > > Hi Matt, James, > > > > any thoughts on the below notes? > > To be honest, not really. You've repeated stage two of the Oracle > argument: wheel

Re: [openstack-dev] [heat] spec-lite for simple feature requests

On 01/20/2016 10:21 AM, Rabi Mishra wrote: Hi All, As discussed in the team meeting, below is the proposed spec-lite process for simple feature requests. This is already being used in Glance project. Feedback/comments/concerns are welcome, before we update the contributor docs with this:).

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

I fall very much in the same mentality as Ben. I'm +1 to all of his points, with a few comments inline. On 01/22/2016 12:24 PM, Ben Nemec wrote: So I haven't weighed in on this yet, in part because I was on vacation when it was first proposed and missed a lot of the initial discussion, and

Re: [openstack-dev] [Fuel] Relieving CI/gate jenkins bottleneck

On 2016-01-22 10:51:21 +0100 (+0100), Bogdan Dobrelya wrote: [...] > Let's just do the best to reuse upstream modules as is, eventually. > > [0] > https://github.com/openstack/fuel-library/blob/master/deployment/Puppetfile Sorry to be pedantic, but the actual upstream URL equivalent is:

Re: [openstack-dev] [Nova] sponsor some LVM development

On Fri, 2016-01-22 at 21:49 +0100, Premysl Kouril wrote: > On 22 Jan 2016 17:43, "James Bottomley" < > james.bottom...@hansenpartnership.com> wrote: > > The 3x difference in the benchmarks would seem to indicate a local > > tuning or configuration problem, because it's not what most people > >

[openstack-dev] [app-catalog] App Catalog IRC meeting minutes - 1/21/2016

Yesterday we had a good conversation about including TOSCA assets in the Community App Catalog, as well as covered some updates on work we recently merged. One of the nicest bits is extracting "last updated" date for assets so the "recently added/modified" banner on the web site will be more

Re: [openstack-dev] [stable] No stable team meeting on Tuesday 1/26

On 1/18/2016 3:41 PM, Matt Riedemann wrote: There are three meetups happening next week and I'll be at one of them, so we're going to cancel next week's meeting. So the next meeting will be on Monday 2/1 at 2100 UTC. I just remembered that I'm on vacation the week of 2/1. I don't think

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

On 2016-01-22 13:54:22 +0100 (+0100), Thierry Carrez wrote: [...] > As a lot of people said, ideally you would add features and repay > technical debt continuously. [...] If we're pulling ideals into this, ideally we wouldn't _consider_ new features until we've reasonably stabilized the ones we

Re: [openstack-dev] [Fuel] Stop deployment can break production cluster. How we should avoid it?

Hi! I also vote for solution "mark a cluster 'operational' after successful deployment". It is simple and guarantee that we do not erase main components. Also it will free resources to support stop/rerun(resume) feature on task based deployment which will works much better (without node destroy

Re: [openstack-dev] [monasca] Anomaly & Prediction Engine

Hi Pradip, There are several components in Monasca. I'm not sure what the acronym APE is stands for. Is that Anomaly and Prediction Engine? The list of components in Monasca and the languages that they are implemented in is as follows: 1. API: Both Java and Python. 2. Persister: Both

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

On Fri, 2016-01-22 at 13:54 +0100, Thierry Carrez wrote: > Zane Bitter wrote: > > [...] Honestly, it > > sounds like the kind of thing you come up with when you've given > > up. > > I tend to agree with that... I think healthy projects should > naturally > come up with bursts of feature addition

Re: [openstack-dev] [neutron] BGP Dynamic Routing Development Going Forward

On 22 January 2016 at 08:57, Tidwell, Ryan wrote: > I wanted to raise the question of whether to develop BGP dynamic routing > in the Neutron repo or spin it out to as a stadium project. This question > has been raised recently on reviews and in offline discussions. For

Re: [openstack-dev] [Monasca] alarms based on events

Hi Prema, I assumed that the component that is translating and sending to the Monasca API would be sending metrics periodically. If that isn't the case, then support for non-periodic metrics would need to be added. Sorry, I should heave realized this in my previous response. I don't think it

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On 01/22/2016 12:30 PM, Ryan Brady wrote: > > > On Fri, Jan 22, 2016 at 12:24 PM, Ben Nemec > wrote: > > So I haven't weighed in on this yet, in part because I was on vacation > when it was first proposed and missed a lot of the

[openstack-dev] [neutron][networking-calico] To be or not to be an ML2 mechanism driver?

networking-calico [1] is currently implemented as an ML2 mechanism driver, but I'm wondering if it might be better as its own core plugin, and I'm looking for input about the implications of that, or for experience with that kind of change; and also for experience and understanding of hybrid ML2

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On Fri, Jan 22, 2016 at 12:24 PM, Ben Nemec wrote: > So I haven't weighed in on this yet, in part because I was on vacation > when it was first proposed and missed a lot of the initial discussion, > and also because I wanted to take some time to order my thoughts on it. >

[openstack-dev] [monasca] Anomaly & Prediction Engine

Monasca folks, We discussed about Anomaly & Prediction Engine in this week's irc meeting and decided we would exchange info using this list. I'm really interested in having this functionality but the status is prototype now. We know that there are a lot of related tech around it and the tech

Re: [openstack-dev] [Neutron] L3-HA - Solution for GW not pingable issue bug/1365461

Hi! This is great that you look into this issue! I think that first solution looks more solid, my concern here is how does this will affect the performance? On Thu, Jan 21, 2016 at 12:12 PM, Lubosz Kosnik wrote: > He neutrinos, > > Currently I'm working on this bug

Re: [openstack-dev] [devstack] Failure on installing openstack with latest devstack.

Vikram Choudhary wrote on 01/22/2016 08:11:52 AM: > From: Vikram Choudhary > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 01/22/2016 08:12 AM > Subject: [openstack-dev] [devstack] Failure

[openstack-dev] [heat] Changing the default Server/SoftwareDeployment transports?

Hi all, Wanted to start some discussion re $subject, context is: https://bugs.launchpad.net/heat/+bug/1507568 Here, we're hitting issues because by default OS::Nova::Server uses the POLL_SERVER_CFN transport. This made sense back when the SoftwareDeployment stuff was first implemented, but now

Re: [openstack-dev] [Fuel] Relieving CI/gate jenkins bottleneck

Another point is to use upstream links for modules w/o downstream patches. I noticed we *always* put it to the deployment/Puppetfile [0] as "https://review.fuel-infra.org/puppet-modules/...;. Why should we? Let's just do the best to reuse upstream modules as is, eventually. [0]

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

On 22 January 2016 at 02:38, Robert Collins wrote: > On 21 January 2016 at 07:38, Ian Cordasco wrote: >> >> I think this is a solid proposal but I'm not sure what (if anything) the TC >> needs to do about this. This is something most

Re: [openstack-dev] [Fuel] Stop deployment can break production cluster. How we should avoid it?

On 22.01.2016 11:45, Dmitry Pyzhov wrote: > Guys, > > There is a tricky bug with our 'stop deployment' > feature: https://bugs.launchpad.net/fuel/+bug/1529691 > > It cannot be fixed easily because it is a design flaw. By design we > cannot leave a node in unpredictable state. So we move all

[openstack-dev] [Fuel] Stop deployment can break production cluster. How we should avoid it?

Guys, There is a tricky bug with our 'stop deployment' feature: https://bugs.launchpad.net/fuel/+bug/1529691 It cannot be fixed easily because it is a design flaw. By design we cannot leave a node in unpredictable state. So we move all nodes that are not in ready state back to bootstrap. But

Re: [openstack-dev] [devstack] Failure on installing openstack with latest devstack.

Thanks Markus. Will try! On Fri, Jan 22, 2016 at 2:31 PM, Markus Zoeller wrote: > Vikram Choudhary wrote on 01/22/2016 08:11:52 AM: > > > From: Vikram Choudhary > > To: "OpenStack Development Mailing List (not for usage questions)" >

[openstack-dev] [release] mitaka-2 development milestone

Hello everyone, The second milestone of the Mitaka development cycle, "mitaka-2", is now reached. Some OpenStack projects following the milestone-based release schedule took the opportunity to publish a development artifact, which contains all the new features and bugfixes that have been added

Re: [openstack-dev] [Monasca] collectd-Monasca Python plugin

Hello Roland: >> How would you map the metric names and fields in collectd to a monasa name >> and dimensions? I'm on it. I'm reading the API from collectd and monasca, to figure out how to connect them. Next week I'll upload a spec and I'll wait for your comments. Thank you for your interest!

Re: [openstack-dev] [nova][bugs] nova-bugs-team IRC meeting

The dates and times are final now [1]. They differ from the previously dates in this thread! The first and next meetings will be: Tuesday 2016-02-09 18:00 UTC #openstack-meeting-4 Tuesday 2016-02-23 18:00 UTC #openstack-meeting-4 Tuesday 2016-03-01 10:00 UTC

Re: [openstack-dev] [nova][bugs] nova-bugs-team IRC meeting

On 22 January 2016 at 10:08, Markus Zoeller wrote: > The dates and times are final now [1]. They differ from the previously > dates in this thread! The first and next meetings will be: > > Tuesday 2016-02-09 18:00 UTC #openstack-meeting-4 > Tuesday 2016-02-23

[openstack-dev] [tripleo] puppet-tripleo gate is broken

TL;DR, please review https://review.openstack.org/#/q/b5001ceca43459f7e4e4efc9191692b42a335091,n,z and CI will be back for the module. Thanks, -- Emilien Macchi signature.asc Description: OpenPGP digital signature __

[openstack-dev] [release][all] independent and unmanaged projects should record their releases, too

The openstack/releases repo is used to produce releases for managed projects, but all projects may submit information about their releases to have that data published for reference. If you are the release liaison for a project, and you are tagging releases directly, please also consider adding

[openstack-dev] Keystone token-get failing during devstack juno-eol installation

Hi, I tried to install devstack (juno-eol) on Ubuntu 12.04 and seeing "keystone token get failing.." as below - 2016-01-22 11:06:33.470 | + screen -S stack -p g-api -X log on 2016-01-22 11:06:33.473 | + ln -sf /opt/stack/logs/screen-g-api.2016-01-22-053014.log /opt/stack/logs/screen-g-api.log

Re: [openstack-dev] [Neutron] L3-HA - Solution for GW not pingable issue bug/1365461

From the performance perspective it will require additional CPU time because of the need to run that bash script. I will try to prepare it as simple as possible but probability that it will kill server when there will be spawned huge amount of routers is not so big - after the implementation we

[openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

Hi folks, A new plug-in for making collectd[1] stats available to Ceilometer [2] is ready for use. The collectd-ceilometer-plugin make system statistics from collectd available to Ceilometer. These additional statistics make it easier to detect faults and identify performance bottlenecks

Re: [openstack-dev] [Fuel] Relieving CI/gate jenkins bottleneck

+1 for defaulting to upstream for CI. If we have a strong case where we need to make a patch in order to make unit tests pass, we could switch a module back to review.fuel-infra.org/puppet-modules/ with a FIXME and a LP bug ID so we can switch it back quickly once the upstream issue is

Re: [openstack-dev] [heat] Changing the default Server/SoftwareDeployment transports?

+1 from me. Somewhat related, would also be nice to switch the default for "user_data_format" in OS::Nova::Server to RAW someday, as now it defaults to HEAT_CFNTOOLS. Best regards, On Fri, Jan 22, 2016 at 11:38 AM Steven Hardy wrote: > Hi all, > > Wanted to start some

Re: [openstack-dev] [monasca] Anomaly & Prediction Engine

(Apology for ignorance) - can anyone from Monasca please point any related documentation about the APE micro-service which (whatever be the state currently it is) currently we have in Monasca? Its in python or in Java? --pradip On Fri, Jan 22, 2016 at 4:12 PM, Osanai, Hisashi <

[openstack-dev] [cinder] Core/minimum features requirements for Cinder Driver

Hey Guys, I would like to know the requirement for core/minimum features that any new Cinder driver should implement. Provided lot many features have been added in Cinder since Icehouse release, Is the core feature requirements mentioned in [1] still valid for recent and upcoming releases or

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

Zane Bitter wrote: [...] Honestly, it sounds like the kind of thing you come up with when you've given up. I tend to agree with that... I think healthy projects should naturally come up with bursts of feature addition and bursts of repaying technical debt. That is why I prefer not to be too

Re: [openstack-dev] [Monasca] collectd-Monasca Python plugin

One question. After pushing the data to Monasca (gathering from collectd) - what else could potentially be done on this data to get some interesting inside about the system? Of course, specially for legacy system cases, it would be an awesome addition (similar line of Ceilometer - I guess).

Re: [openstack-dev] [cinder] Core/minimum features requirements for Cinder Driver

On 01/22/2016 01:17 PM, vishal yadav wrote: > Hey Guys, > > I would like to know the requirement for core/minimum features that > any new Cinder driver should implement. Provided lot many features > have been added in Cinder since Icehouse release, Is the core feature > requirements mentioned in

Re: [openstack-dev] [Fuel] Relieving CI/gate jenkins bottleneck

On 22.01.2016 12:19, Matthew Mosesohn wrote: > +1 for defaulting to upstream for CI. If we have a strong case where we > need to make a patch in order to make unit tests pass, we could switch a > module back to review.fuel-infra.org/puppet-modules/.. >

Re: [openstack-dev] Keystone token-get failing during devstack juno-eol installation

What is in the Apache / keystone log? On Fri, Jan 22, 2016 at 1:56 AM, Jonnalagadda, Venkata < venkata.jonnalaga...@intl.att.com> wrote: > Hi, > > > > I tried to install devstack (juno-eol) on Ubuntu 12.04 and seeing > “keystone token get failing..” as below – > > > > 2016-01-22 11:06:33.470 | +

[openstack-dev] [searchlight] Nominating Li Yingjun to Searchlight Core

I am nominating Li Yingjun (yingjun on IRC) to join the Searchlight core reviewers team. We are a young project and he has already made a noticeable impact with his contributions. You may review his Searchlight [0] and cross-project [1] activity reports below. He has been participating in

[openstack-dev] [puppet] CI status

Hi, Here is a quick Puppet OpenStack CI status. Failures: 1/ Puppet 3.8.5 is out and some syntax jobs are currently broken. Bug reports: https://bugs.launchpad.net/puppet-murano/+bug/1537251 https://bugs.launchpad.net/puppet-ironic/+bug/1537251 Related to

Re: [openstack-dev] [puppet] CI status

On 01/22/2016 06:32 PM, Emilien Macchi wrote: > Hi, > > Here is a quick Puppet OpenStack CI status. > > Failures: > > 1/ Puppet 3.8.5 is out and some syntax jobs are currently broken. > > Bug reports: https://bugs.launchpad.net/puppet-murano/+bug/1537251 >

Re: [openstack-dev] [neutron] BGP Dynamic Routing Development Going Forward

I agree with Armando and feel option 2 would be viable if we really want to deliver this feature in Mitaka time frame. Adding a new stadium project invites more work and can be done in N release. Thanks Vikram On Jan 22, 2016 11:47 PM, "Armando M." wrote: > > > On 22 January

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On Fri, 2016-01-22 at 11:24 -0600, Ben Nemec wrote: > So I haven't weighed in on this yet, in part because I was on > vacation > when it was first proposed and missed a lot of the initial > discussion, > and also because I wanted to take some time to order my thoughts on > it. >  Also because my

[openstack-dev] [kolla] interesting development work which isn't extremely complex for new developers

Hi folks, We have had tremendous activity on the drop-root blueprint here: https://blueprints.launchpad.net/kolla/+spec/drop-root Unfortunately the work didn't finish in mitaka-2. There are 5 TODO items left. These are services which need to be securified. There is a significant example

Re: [openstack-dev] [monasca] Anomaly & Prediction Engine

Thanks Hisashi. I am sorry - by APE - I meant Anamoly and Prediction engine only. Thanks a lot for the link. --pradip On Sat, Jan 23, 2016 at 12:18 AM, Hochmuth, Roland M < roland.hochm...@hpe.com> wrote: > Hi Pradip, There are several components in Monasca. I'm not sure what the >

[openstack-dev] [kolla] 40 hour time commitment requested from core reviewers before Feb 9th/10th midcycle

Hello, In our weekly IRC meeting, all developers and others in attendance were in unanimous agreement that upgrades are the #1 priority for Kolla to solve [1]. inc0 has developed both a simple database migration implementation around keystone [2] as well as a more complex playbook around

Re: [openstack-dev] [neutron] BGP Dynamic Routing Development Going Forward

The real question that needs to be asked (at least for me) is how this feature can work with other plugins/ML2 drivers that are not the reference implementation. How hard (possible) it is to take the API part (or maybe even the agent) and use that in another Neutron implementation. Then focus on

Re: [openstack-dev] [Monasca] collectd-Monasca Python plugin

Thanks Alonso. On 1/22/16, 2:56 AM, "Alonso Hernandez, Rodolfo" wrote: >Hello Roland: > >>> How would you map the metric names and fields in collectd to a monasa >>>name and dimensions? >I'm on it. I'm reading the API from collectd and monasca, to figure out

[openstack-dev] [neutron] BGP Dynamic Routing Development Going Forward

I wanted to raise the question of whether to develop BGP dynamic routing in the Neutron repo or spin it out to as a stadium project. This question has been raised recently on reviews and in offline discussions. For those unfamiliar with this work, BGP efforts in Neutron entail admin-only

Re: [openstack-dev] [Fuel] Stop deployment can break production cluster. How we should avoid it?

Dmitry, > We can mark a cluster 'operational' after successful deployment. And we > can disable 'stop' button on this kind of clusters. I think this is a best solution so far. Moreover, I don't know how to fix it properly since there could be a lot of questions how this button should behave at

Re: [openstack-dev] Dynamically adding Extra Specs

Hi! Comments inline... On 01/22/2016 01:26 AM, Dhvanan Shah wrote: Hi, I had a few queries regarding adding extra specs for VM requests. According to my understanding if I want to add extra specs to requests then I need to change that in different flavors adding those capabilities by setting

Re: [openstack-dev] [Fuel] Relieving CI/gate jenkins bottleneck

And one more thing [0]. We should fix the Rakefile to call unit tests only for modules being changed by a patch under test. This makes even more sense bearing in mind the patch [1] which as well disables unit tests and syntax checks for upstream modules we clone by librarian. [0]

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

I gave a couple of ad-hoc demo's of my Mistral dev environment this week. For those interested in tinkering with TripleO Mistral actions in tripleo-common here are links to the code I used for those. Still a rough prototype but hopefully demonstrates how these things might work:

[openstack-dev] [OpenStack-Ansible] Mid Cycle Sprint

Hi everyone, We've finalised the arrangements for the Mid Cycle sprint. Given that the Ops Mid Cycle [1] is in the UK (15-16 Feb) and AnsibleFest [2] is also in the UK (18 Feb), Rackspace has offered to host the Mid Cycle sprint at their offices in Hayes (West London) on 17 Feb from 8am to 6pm.

[openstack-dev] [Nova][Devstack] Booted instance doesn't have internet connection

Hi guys. I took minimal configuration of devstack from here https://github.com/openstack-dev/devstack/blob/master/doc/source/configuration.rst And tried to boot server. It was booted but there is no internet connection on the instance. Does some one faced with such an issue? I have no idea how fix

Re: [openstack-dev] [Monasca] alarms based on events

Hi Roland, I had a chat with people on IRC about it and I understood that in order for my use case to work the Monasca software needs to implement "non-periodic" metrics (because the monitored box sends out the event only on health change and not periodicaly) and I understood that this

Re: [openstack-dev] [TripleO] add support for other types of virtual switches in os_net_config

On Thu, 2016-01-21 at 16:05 -0800, Xin Wu wrote: > Hi, all > >      This is Xin from Big Switch. I'm proposing to make os_net_config > support more types of virtual switches. >      Current os_net_config supports ovs_bridge, linux_bridge and > different types of interfaces associated with ovs and

Re: [openstack-dev] [Nova] sponsor some LVM development

Hi Matt, James, any thoughts on the below notes? Best Regards, Prema On 19 Jan 2016 20:47, "Premysl Kouril" wrote: > Hi James, > > > > > > You still haven't answered Anita's question: when you say "sponsor" do > > you mean provide resources to existing developers to

Re: [openstack-dev] [Nova] sponsor some LVM development

On Fri, 2016-01-22 at 14:58 +0100, Premysl Kouril wrote: > Hi Matt, James, > > any thoughts on the below notes? To be honest, not really. You've repeated stage two of the Oracle argument: wheel out benchmarks and attack alleged "complexity". I don't really have a great interest in repeating a

Re: [openstack-dev] [Nova] sponsor some LVM development

On Tue, Jan 19, 2016 at 8:47 PM, Fox, Kevin M wrote: > One feature I think we would like to see that could benefit from LVM is > some kind of multidisk support with better fault tolerance > > For example: > Say you have a node, and there are 20 vm's on it, and thats all

[openstack-dev] [release] no release team meeting 29 Jan

There will be no release team meeting on 29 Jan 2016. We will resume meeting the following week. Doug __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [keystone][neutron][requirements] - keystonemiddleware-4.1.0 performance regression

On 1/20/2016 2:15 PM, Sean Dague wrote: On 01/20/2016 02:59 PM, Morgan Fainberg wrote: So this was due to a change in keystonemiddleware. We stopped doing in-memory caching of tokens per process, per worker by default [1]. There are a couple of reasons: 1) in-memory caching produced

Re: [openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

nice! thanks Emma! i'm wondering if there's an additional metrics/resources we should add to gnocchi to accommodate the data? On 22/01/2016 6:11 AM, Foley, Emma L wrote: Hi folks, A new plug-in for making collectd[1] stats available to Ceilometer [2] is ready for use. The

[openstack-dev] [cinder][bugs] volume:create_snapshot is missing from etc/cinder/policy.json

Found that the "volume:create_snapshot": "rule:admin_or_owner", action was missing from the cinder policy.json file. I am looking for someone to review the change and close the bug. Any help would be appreciated. Original Bug https://bugs.launchpad.net/cinder/+bug/1530196 Gerrit review

Re: [openstack-dev] [API] [Glance] New v2 Image Import

On 08/01/16 17:14 +, Ian Cordasco wrote: Hey all, Yo! Thanks for taking the time to read the spec and writing this email. Yes, the more eyes the better -- so thanks. Flavio asked me to document the various alternatives. At very least it's good to capture them in the spec.

Re: [openstack-dev] [Nova] sponsor some LVM development

On 01/22/2016 09:33 AM, Matthew Booth wrote: On Tue, Jan 19, 2016 at 8:47 PM, Fox, Kevin M > wrote: One feature I think we would like to see that could benefit from LVM is some kind of multidisk support with better fault tolerance

[openstack-dev] [murano] Nominate Rong Zhu to Murano Core

I would like to nominate Rong Zhu (zhurong on IRC) join to the Murano core-reviewers team. He has been an active member of the Murano team for some time now. You can check his review activity report here: http://stackalytics.com/report/contribution/murano-group/90 Team please vote for this change

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

So I haven't weighed in on this yet, in part because I was on vacation when it was first proposed and missed a lot of the initial discussion, and also because I wanted to take some time to order my thoughts on it. Also because my initial reaction...was not conducive to calm and rational

[openstack-dev] [murano] Nominate Victor Ryzhenkin to Murano Core

I would like to nominate Victor Ryzhenkin (freerunner on IRC) join to the Murano core-reviewers team. He has been an active member of the Murano team for some time now. You can check his review activity report here: http://stackalytics.com/report/contribution/murano-group/90 Team please vote for

[openstack-dev] Announcing Ekko -- Scalable block-based backup for OpenStack

Dear community, We would like to introduce you to a new community-driven OpenStack project called Ekko. The aim of Ekko is to provide incremental block-level backup and restore of Nova instances. We see backups as a key area that is missing in OpenStack. One issue that has previously prevented

Re: [openstack-dev] [nova][testing] How to run a subset of py34 unit tests

On Fri, Jan 22, 2016 at 06:46:48PM -0800, melanie witt wrote: > Hi everyone, > > I noticed because of the way we run the py34 tests in tox.ini, I'm not able > to specify a filter regex the way I normally do as a positional arg, for > example: 'tox -epy34 nova.tests.unit.network' doesn't filter

Re: [openstack-dev] [Neutron] MTU configuration pain

The fun continues, now using an OpenStack deployment on physical hardware that supports jumbo frames with 9000 MTU and IPv4/IPv6. This experiment still uses Linux bridge for consistency. I'm planning to run similar experiments with Open vSwitch and Open Virtual Network (OVN) in the next week. I

[openstack-dev] [nova][testing] How to run a subset of py34 unit tests

Hi everyone, I noticed because of the way we run the py34 tests in tox.ini, I'm not able to specify a filter regex the way I normally do as a positional arg, for example: 'tox -epy34 nova.tests.unit.network' doesn't filter and it runs everything. ('tox -epy27 nova.tests.unit.network' will only

Re: [openstack-dev] [nova][testing] How to run a subset of py34 unit tests

Melanie, The following should work as well source .tox/py34/bin/activate ostestr --regex *.network.* Thanks, Dims On Fri, Jan 22, 2016 at 9:46 PM, melanie witt wrote: > Hi everyone, > > I noticed because of the way we run the py34 tests in tox.ini, I'm not able > to

[openstack-dev] [tacker] Reminder - Mid-cycle Meetup next week in San Jose, CA

Heads up for folks interested in NFV Orchestration. Tacker team is hosting a mid-cycle meetup next week in San Jose. Agenda, logistics and sign-up sheet are in the etherpad [1]. - Sridhar [1] https://etherpad.openstack.org/p/tacker-mitaka-midcycle

Re: [openstack-dev] [searchlight] Nominating Li Yingjun to Searchlight Core

+1 -Original Message- From: Tripp, Travis S Sent: Friday, January 22, 2016 4:10 PM To: OpenStack List Subject: [openstack-dev] [searchlight] Nominating Li Yingjun to Searchlight Core I am nominating Li Yingjun (yingjun on IRC) to join the Searchlight core reviewers team. We are a young

Re: [openstack-dev] [searchlight] Nominating Li Yingjun to Searchlight Core

+1 Li's submitted a number of patches to Searchlight, showed a good understanding of it, and has very actively reviewed patches and specs from other contributors. On 1/22/16, 6:09 PM, "Tripp, Travis S" wrote: >I am nominating Li Yingjun (yingjun on IRC) to join the

[openstack-dev] OpenStack Developer Mailing List Digest January 16-22

Perma link: http://www.openstack.org/blog/2016/01/openstack-developer-mailing-list-digest-20160122 Success Bot Says - mriedem: nova liberty 12.0.1 released [1]. - OpenStack Ansible Kilo 11.2.7 has been released. - OpenStack-Ansible Liberty 12.0.4 has been released. - Tell us