Re: [openstack-dev] [kuryr] Did kuryr need to know about Docker's cluster store?

On Fri, Mar 4, 2016 at 5:01 AM, Vikas Choudhary wrote: > Since libnetwork talks to cluster store independent of plugin, I think no > changes are required on Kuryr side. That's right. Docker handles all the KV storage interaction from the data it receives from Kuryr.

Re: [openstack-dev] [ceilometer] Unable to get ceilometer events for instances running on demo project

This is a usage question not supposed to appear on this -dev list. But anyway, you may want to check if you have the following lines in your ceilometer.conf file: [notification] store_events = True Regards, Qiming On Wed, Mar 02, 2016 at 10:56:53PM +0500, Umar Yousaf wrote: > I have a

Re: [openstack-dev] [keystone][nova] Many same "region_name" configuration really meaingful for Multi-region customers?

Hi, From my previous 3K+ nodes 6+ regions OpenStack operations experience in Yandex, I found useless to have Cinder and Neutron services in cross-region manner. BTW, nova-neutron cross-region interactions are still legitimate use case: you may utilize one neutron for many nova regions.

Re: [openstack-dev] [OpenStack-docs] Fwd: [Neutron][LBaaS][Octavia][Docs] Need experienced contributor documentation best-practices and how-tos

Hello Lana! Thank you for your prompt reply-- I found it extremely helpful! Comments inline: > > So in the intervening days I've been going through the openstack-manuals, > > openstack-doc-tools, and other repositories, trying to figure out where I > > make my edits. I found both the CLI and

Re: [openstack-dev] [magnum][heat] spawn a group of nodes on different availability zones

On Fri, Mar 04, 2016 at 01:09:26PM +0800, Qiming Teng wrote: > Another option is to try out senlin service. What you need to do is > something like below: > > 1. Create a heat template you want to deploy as a group, say, > node_template.yaml > > 2. Create a senlin profile spec (heat_stack.yaml)

Re: [openstack-dev] [keystone][nova] Many same "region_name" configuration really meaingful for Multi-region customers?

Hi, From my previous 3K+ nodes 6+ regions OpenStack operations experience in Yandex, I found useless to have Cinder and Neutron services in cross-region manner. BTW, nova-neutron cross-region interactions are still legitimate use case: you may utilize one neutron for many nova regions. --

Re: [openstack-dev] [magnum][heat] spawn a group of nodes on different availability zones

Another option is to try out senlin service. What you need to do is something like below: 1. Create a heat template you want to deploy as a group, say, node_template.yaml 2. Create a senlin profile spec (heat_stack.yaml) which may look like, for example: type: os.heat.stack version: 1.0

Re: [openstack-dev] [keystone][nova] Many same "region_name" configuration really meaingful for Multi-region customers?

Hi Dolph, It seems use one configuration could simply like below: nova.conf: ** client_region_name = RegionOne All clients would use that region instead of create many different section/properties(what nova do now) for that. But I'd like to hear what's nova/keystone developers

[openstack-dev] [release][requirements] global requirements update squash for milestone

We have a handful of requirements changes for community releases that we need to land this week before fully freezing the repo. We're starting to see merge conflicts, so I've combined them all into one commit to make it easier to land the changes quickly. https://review.openstack.org/288249

Re: [openstack-dev] [neutron] - Changing the Neutron default security group rules

On 03/03/16 23:12, Jonathan Proulx wrote: To go a little further down my wish list I'd really like to do be able to offer a standard selection of security groups for my site no tjust 'default', but that may be a bit off this topic. Briefly my motivation is that 'internal' here includes a

[openstack-dev] What's Up, Doc? 4 March 2016

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi everyone, This week I've been concentrating on getting ready for the release, and I'm very pleased to announce that we now have not one but two release managers for Mitaka. Please welcome Brian and Olga, thanks to you both for stepping up to

Re: [openstack-dev] [keystone][nova] Many same "region_name" configuration really meaingful for Multi-region customers?

Unless someone on the operations side wants to speak up and defend cross-region nova-cinder or nova-neutron interactions as being a legitimate use case, I'd be in favor of a single region identifier. However, both of these configuration blocks should ultimately be used to configure keystoneauth,

Re: [openstack-dev] [kuryr] Did kuryr need to know about Docker's cluster store?

Since libnetwork talks to cluster store independent of plugin, I think no changes are required on Kuryr side. Regards Vikas On Thu, Mar 3, 2016 at 9:54 PM, Mike Spreitzer wrote: > On Feb 5 I was given a tarchive of kuryr with an install script that > configures the docker

Re: [openstack-dev] [Neutron][LBaaS][Octavia][Docs] Need experienced contributor documentation best-practices and how-tos

On 3 March 2016 at 18:35, Stephen Balukoff wrote: > Hi Armando, > > Please rest assured that I really am a fan of requiring. I realize that > sarcasm doesn't translate to text, so you'll have to trust me when I say > that I am not being sarcastic by saying that. > >

Re: [openstack-dev] [telemetry][aodh] "aodh alarm list" vs "aodh alarm search"

On Fri, Mar 04, 2016 at 09:57:35AM +0800, liusheng wrote: > Hi folks, > Currently, we have supported "aodh alarm list" and "aodh alarm > search" commands to query alarms. They both need mandatory "--type" > parameter, and I want to drop the limitation[1]. if we agree that, > the "alarm list"

Re: [openstack-dev] [kuryr] Docker cannot find the created network with kuryr driver

Hi Liping, I apply your method, it works, so cool, much thanks!珞 Thanks & Best regards ! Mars Ma On Thu, Mar 3, 2016 at 11:45 PM, Liping Mao (limao) wrote: > Hi Mars, > > I get similar problem before, it is because I capability_scope is

Re: [openstack-dev] [nova] Non-Admin user can show deleted instances using changes-since parameter when calling list API

Hm, I found out the reason: https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/servers.py#L1139-L1145 here we filtered out parameters like "deleted", and that's why the API behavior is like above mentioned. So should we simple add "deleted" to the tuple or a microversion is

[openstack-dev] [trove][release] Releases for Trove and python-troveclient

Members of the Trove team, Earlier today I tagged Trove release 5.0.0.0b3[1] and python-troveclient version 2.1.0[2]. A request has also been submitted to update constraints to reflect the new client version[3]. Thanks to all who submitted code for features in this release. I know that there

Re: [openstack-dev] [OpenStack-docs] Fwd: [Neutron][LBaaS][Octavia][Docs] Need experienced contributor documentation best-practices and how-tos

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/03/16 11:41, Stephen Balukoff wrote: > Hah! Didn't realize that 'docs' had its own mailing list. XD Anyway, please > see the e-mail below: Thanks for drawing this to our attention. > > -- Forwarded message -- > From: Stephen

[openstack-dev] [TripleO] IPv4 network isolation testing update

Some progress today: After rebuilding the test-env workers nodes in our CI rack to support multiple-nics we got a stack to go into CREATE_COMPLETE with network isolation enabled in CI. https://review.openstack.org/#/c/288163/ Have a look at the Ceph result here:

Re: [openstack-dev] [ironic] Midcycle summary part 3/6

Hi, Lucas, Thank you for your correspondence. > I think we meant UEFI >= 2.4 there. That make sence! > Apparently in the UEFI version 2.4 some feature was introduced that is > required for the boot from volume > case. > Which function of UEFI 2.4 do you point to? It would be very helpful if

Re: [openstack-dev] [Neutron][LBaaS][Octavia][Docs] Need experienced contributor documentation best-practices and how-tos

Hi Armando, Please rest assured that I really am a fan of requiring. I realize that sarcasm doesn't translate to text, so you'll have to trust me when I say that I am not being sarcastic by saying that. However, I am not a fan of being given nebulous requirements and then being accused of

Re: [openstack-dev] [nova] Non-Admin user can show deleted instances using changes-since parameter when calling list API

Anyway, I updated the bug report: https://bugs.launchpad.net/nova/+bug/1552071 and I will start to working on the bug first. On Fri, Mar 4, 2016 at 9:29 AM, Zhenyu Zheng wrote: > Yes, so you are suggest fixing the return data of non-admin user use 'nova > list

[openstack-dev] [telemetry][aodh] "aodh alarm list" vs "aodh alarm search"

Hi folks, Currently, we have supported "aodh alarm list" and "aodh alarm search" commands to query alarms. They both need mandatory "--type" parameter, and I want to drop the limitation[1]. if we agree that, the "alarm list" will only used to list all alarms and don't support any query

Re: [openstack-dev] [Neutron][LBaaS][Octavia][Docs] Need experienced contributor documentation best-practices and how-tos

On 3 March 2016 at 16:56, Stephen Balukoff wrote: > Hello! > > I have a problem I'm hoping someone can help with: I have gone through the > task of completing a shiny new feature for an openstack project, and now > I'm trying to figure out how to get that last

Re: [openstack-dev] [nova] Non-Admin user can show deleted instances using changes-since parameter when calling list API

Yes, so you are suggest fixing the return data of non-admin user use 'nova list --deleted' but leave non-admin using 'nova list --status=deleted' as is. Or it would be better to also submit a BP for next cycle to add support for non-admin using '--status=deleted' with microversions. Because in my

Re: [openstack-dev] [Fuel] [murano] [yaql] yaql.js

(and thus port YAQL to JS) FYI, you’re not the first one to have that idea. =) We have https://review.openstack.org/#/c/159905/3 an initial draft of how YAQL may look on JS. It’s outdated, but most certainly can be revived and finished if you have interest in helping us make it happen. =) -- 

[openstack-dev] [Neutron][LBaaS][Octavia][Docs] Need experienced contributor documentation best-practices and how-tos

Hello! I have a problem I'm hoping someone can help with: I have gone through the task of completing a shiny new feature for an openstack project, and now I'm trying to figure out how to get that last all-important documentation step done so that people will know about this new feature and use

Re: [openstack-dev] [ceilometer] Unable to get IPMI meter readings

Hi Kapil, Currenlyt, the ipmi pollsters can only get the ipmi data from system bus due to the security concerns. So you have the make sure the ceilometer-agent-ipmi is running on the same machine you want get the hardware.ipmi.node.power metric from. Also you should make sure your machine have

Re: [openstack-dev] [nova] A prototype implementation towards the "shared state scheduler"

Hi again, Yingxin, sorry for the delayed response... been traveling. Comments inline :) On 03/01/2016 12:34 AM, Cheng, Yingxin wrote: Hi, I have simulated the distributed resource management with the incremental update model based on Jay's benchmarking framework:

Re: [openstack-dev] [Cinder] Status of cinder-list bug delay with 1000's of volumes

On 03/03/2016 06:38 PM, Walter A. Boring IV wrote: > Adam, > As the bug shows, it was fixed in the Juno release. The icehouse > release is no longer supported. I would recommend upgrading your > deployment if possible or looking at the patch and see if it can work > against your Icehouse

Re: [openstack-dev] [fuel] Fuel 9.0/Mitaka is now in Feature Freeze

Following feature freeze exceptions were granted, ordered by their merge deadline. See linked emails for additonal conditions attached to some of these exceptions. UCA, 3/10: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088309.html Multipath disks, 3/10:

Re: [openstack-dev] [Fuel] [FFE] LCM readiness for all deployment tasks

Granted, merge deadline March 15. -- Dmitry Borodaenko On Tue, Mar 01, 2016 at 05:03:11PM +0100, Szymon Banka wrote: > Hi All, > > I’d like to request a Feature Freeze Exception for "LCM readiness for all > deployment tasks” [1] until Mar 11. > > We need additional 1.5 week to finish and

Re: [openstack-dev] [Fuel][FFE] Enable UCA repositories for deployment

Granted, merge deadline March 10. -- Dmitry Borodaenko On Wed, Mar 02, 2016 at 06:27:32PM +0300, Matthew Mosesohn wrote: > Hi all, > > I would like to request a feature freeze exception for "Deploy with > UCA packages" feature. > > I anticipate 2 more days to get tests green and add some

Re: [openstack-dev] [Fuel] FFE request for osnailyfacter refactoring for Puppet Master compatibility

Granted conditionally, design consensus deadline March 10, merge deadline March 16 for patches that do not conflict with fuel-openstack-tasks and fuel-remove-conflict-openstack, March 24 for remaining patches. If design consensus is not reached by March 10, the exception will be revoked. --

Re: [openstack-dev] [Fuel] [FFE] Unlock Settings Tab

Granted, merge deadline March 24, task history part of the feature is to be excluded from this exception grant unless a consensus is reached by March 10. Relevant part of the meeting log starts at: http://eavesdrop.openstack.org/meetings/fuel/2016/fuel.2016-03-03-16.00.log.html#l-198 -- Dmitry

Re: [openstack-dev] [kolla][security][release] Obtaining the vulnerability:managed tag

On 2016-03-03 23:57:04 + (+), Steven Dake (stdake) wrote: [...] > If anything in this email is wrong, feel free to correct me and > get us on the right track. [...] Sounds on track to me. The goal of having some guidelines for this was mainly just to try and avoid the VMT taking

Re: [openstack-dev] [Fuel] [FFE] FF exception request for SR-IOV

Granted, merge deadline March 16, feature to be marked experimental until QA has signed off that it's fully tested and stable. -- Dmitry Borodaenko On Wed, Mar 02, 2016 at 01:40:26PM +0200, Aleksey Kasatkin wrote: > > And we need to write a new patch for: >

Re: [openstack-dev] [Neutron][LBaaS]Removing LBaaS v1 - are weready?

Ok. Thanks for the info. Kevin From: Brandon Logan [brandon.lo...@rackspace.com] Sent: Thursday, March 03, 2016 2:42 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Neutron][LBaaS]Removing LBaaS v1 - are weready? Just for clarity,

Re: [openstack-dev] [Fuel] [FFE] Component registry improvements

Denied. A fairly large patch with potentially intrusive refactoring that is not required for any other features. We can safely postpone this until Newton. -- Dmitry Borodaenko On Wed, Mar 02, 2016 at 11:05:52AM +0200, Andriy Popovych wrote: > Hi, > > I would like to request a feature freeze

Re: [openstack-dev] [Fuel][Upgrade][FFE] Reassigning Nodes without Re-Installation

Denied. This came in very late (patch remained in WIP until 1 day before FF), covers a corner case, there was not enough risk analysis, it wasn't represented in the IRC meeting earlier today, and the spec for the high-level feature is sitting with a -1 from fuel-python component lead since 1.5

Re: [openstack-dev] [kolla][security][release] Obtaining the vulnerability:managed tag

Tristan, Flying a bit by the seat of my pants here. I can't find a simple check-list of how exactly you get a project managed by the VMT :) If anything in this email is wrong, feel free to correct me and get us on the right track. The kolla-coresec team consists of the following folks: Martin

Re: [openstack-dev] [Cinder] Status of cinder-list bug delay with 1000's of volumes

Adam, As the bug shows, it was fixed in the Juno release. The icehouse release is no longer supported. I would recommend upgrading your deployment if possible or looking at the patch and see if it can work against your Icehouse codebase. https://review.openstack.org/#/c/96548/ Walt On

[openstack-dev] [cinder] Nested quota -1 limit race condition

Hey all, Nested quotas has officially started fighting back - while writing Tempest tests for the nested quota support [1], I hit a race-condition related to the nested quota -1 support that has me stumped. I opened a bug for it [2] with more details, but basically the issue occurs when if you

Re: [openstack-dev] [Fuel][FFE] Remove conflicting openstack module parts

Granted, merge deadline 3/20. -- Dmitry Borodaenko On Tue, Mar 01, 2016 at 11:26:57PM +, Andrew Woodward wrote: > I'd like to request a feature freeze exception for the Remove conflicting > openstack module parts feature [0] > > This is necessary to make the feature Decouple Fuel and

Re: [openstack-dev] [Fuel][FFE] Decouple Fuel and OpenStack tasks

Granted, merge deadline 3/20. -- Dmitry Borodaenko On Tue, Mar 01, 2016 at 10:07:55PM +, Andrew Woodward wrote: > I'd like to request a feature freeze exception for Decouple Fuel and > OpenStack tasks feature [0]. > > While the code change [1] is ready and usually passing CI we have too

Re: [openstack-dev] [Fuel][FFE] FF exception request for non-root accounts on slave nodes

Denied. Most of this feature has landed before FF as expected, the rest can wait until Newton. At least, operators who want to disable root access to target nodes are now able to do so, with some exceptions and some additional manual tweaking that we should clean up in the next release. --

[openstack-dev] [Cinder] Status of cinder-list bug delay with 1000's of volumes

Hey all (hi John), What's the status of this [1]? We're experiencing this behavior in Icehouse - wondering where it was addressed and if so, when. I always get confused when I look at the launchpad/review portals. [1] https://bugs.launchpad.net/cinder/+bug/1317606 *Adam Lawson* AQORN, Inc.

Re: [openstack-dev] [Fuel][FFE] Multi-release packages

Denied. This change is likely to require a Nailgun DB schema change, and can benefit from more design discussions. -- Dmitry Borodaenko On Tue, Mar 01, 2016 at 11:00:24PM +0300, Alexey Shtokolov wrote: > Fuelers, > > I would like to request a feature freeze exception for "Multi-release >

Re: [openstack-dev] [Fuel][FFE] FF exception request for Numa and CPU pinning

Granted, merge deadline March 16, feature to be marked experimental until QA has signed off that it's fully tested and stable. -- Dmitry Borodaenko On Tue, Mar 01, 2016 at 10:23:08PM +0300, Dmitry Klenov wrote: > Hi, > > I'd like to to request a feature freeze exception for "Add support for >

Re: [openstack-dev] [Fuel][FFE] FF exception request for HugePages

Granted, merge deadline March 16, feature to be marked experimental until QA has signed off that it's fully tested and stable. -- Dmitry Borodaenko On Tue, Mar 01, 2016 at 10:23:06PM +0300, Dmitry Klenov wrote: > Hi, > > I'd like to to request a feature freeze exception for "Support for Huge

Re: [openstack-dev] [Fuel] [FFE] FF exception request for DPDK

Granted, merge deadline March 24, feature to be marked experimental until QA has signed off that it's fully tested and stable. -- Dmitry Borodaenko On Thu, Mar 03, 2016 at 05:27:11PM +0300, Vladimir Eremin wrote: > Hi, > > All patches for DPDK feature [1] are on review, new patches are not

Re: [openstack-dev] [Neutron][LBaaS]Removing LBaaS v1 - are weready?

Just for clarity, V2 did not reuse tables, all the tables it uses are only for it. The main problem is that v1 and v2 both have a pools resource, but v1 and v2's pool resource have different attributes. With the way neutron wsgi works, if both v1 and v2 are enabled, it will combine both sets of

Re: [openstack-dev] [Fuel] Feature Freeze Exception Request - switching to CentOS-7.2

As we agreed, we have switched ISO builds to latest CentOS 7.2 snapshots. You can see now that each ISO build (see for ex. [1]) produces several *_id.txt artifacts. Note that centos_mirror_id.txt points to CentOS snapshot at http://mirror.fuel-infra.org/pkgs/ BVT test is stable, see [2], and

Re: [openstack-dev] [Neutron][LBaaS]Removing LBaaS v1 - are weready?

Just because you had thought no one was using it outside of a PoC doesn't mean folks aren''t using it in production. We would be happy to migrate to Octavia. We were planning on doing just that by running both v1 with haproxy namespace, and v2 with Octavia and then pick off upgrading lb's one

Re: [openstack-dev] [app-catalog] Nominating Kirill Zaitsev to App Catalog Core

+1! :) From: Christopher Aedo [d...@aedo.net] Sent: Thursday, March 03, 2016 1:10 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [app-catalog] Nominating Kirill Zaitsev to App Catalog Core I'd like to propose

Re: [openstack-dev] [oslo] PTL for Newton and beyond

On Thu, Mar 03, 2016 at 06:32:42AM -0500, Davanum Srinivas wrote: > Team, > > It has been great working with you all as PTL for Oslo. Looks like the > nominations open up next week for elections and am hoping more than > one of you will step up for the next cycle(s). I can show you the > ropes

Re: [openstack-dev] [neutron] - Changing the Neutron default security group rules

On 2016-03-03 09:35:54 -0500 (-0500), sridhar basam wrote: [...] > As other have said elsewhere in this thread, you already have the > ability to not use the firewall driver in neutron. I'm still struggling to find documentation on how a tenant^Wproject can disable the firewall driver in Neutron

Re: [openstack-dev] [Fuel][FFE] Use RGW as a default object store instead of Swift

Denied. This is a major functional change and it needs a lot more discussion than a single review posted 2 days before Feature Freeze. Lets start this discussion now, summarize its result in a spec, and see if it's something we want to target for Newton. -- Dmitry Borodaenko On Wed, Mar 02,

[openstack-dev] [Trove] Feature Freeze request for CouchDB backup & restore

Hello,    I would like to request a feature freeze for the following feature: Add support for CouchDB backup & restore [1]. The code for this feature is complete and up for review [2]. The integration tests requires a new library which was added to global-requirements [3]. Unit tests and

Re: [openstack-dev] [Fuel] [FFE] Add multipath disks support

Granted, merge deadline March 10. On Tue, Mar 01, 2016 at 04:27:50PM +0100, Szymon Banka wrote: > Hi All, > > I’d like to request a Feature Freeze Exception for "Add multipath disks > support” until Mar 9. > This feature allows to use FC multipath disks in Fuel nodes – BP [1], spec > [2]. > >

Re: [openstack-dev] [Fuel] [FFE] Use packetary for building ISO

On Thu, Mar 03, 2016 at 11:21:58PM +0800, Thomas Goirand wrote: > On 03/03/2016 07:14 PM, Aleksey Zvyagintsev wrote: > > Hello team's , > > Please take in mind my HUGE +1 > > We really need to remove package building process from iso build flow. > Same point of view over here. Let's get rid of the

[openstack-dev] [sahara-tests] Sahara-tests release and launchpad project

Hi, sahara folks! I would like to propose release sahara-tests. All steps from spec implemented except releases and packaging.[0] Release criteria: framework ready for testing a new release of Sahara. Next step: build a package and publish to PyPI. Also, I think we need to create a separate

Re: [openstack-dev] [Fuel] FFE request for ConfigDB service

Granted, merge deadline March 24, no impact expected in core components (fuel-library, fuel-web, fuel-ui). -- Dmitry Borodaenko On Tue, Mar 01, 2016 at 04:22:05PM +0300, Oleg Gelbukh wrote: > Greetings, > > As you might know, we are working on centralised storage for > deployment

Re: [openstack-dev] [all][i18n] Liaisons for I18n

On Mon, Feb 29, 2016 at 05:26:44PM +0800, Ying Chun Guo wrote: > If you are interested to be a liaison and help translators, > input your information here: > https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n . So https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n says the CPL

[openstack-dev] [release][congress] python-congressclient 1.2.3 release (mitaka)

We are tickled pink to announce the release of: python-congressclient 1.2.3: Client for Congress This release is part of the mitaka release series. With source available at: http://git.openstack.org/cgit/openstack/python-congressclient Please report issues through launchpad:

[openstack-dev] [app-catalog] Nominating Kirill Zaitsev to App Catalog Core

I'd like to propose Kirill Zaitsev to the core team for app-catalog and app-catalog-ui. Kirill has been actively involved with the Community App Catalog since nearly the beginning of the project, and more recently has been doing the heavy lifting around implementing GLARE for a new backend. I

Re: [openstack-dev] [nova] deprecating pluggable managers

++ Long time coming :) On 03/03/2016 11:31 AM, Sean Dague wrote: As we were evaluating bits of configuration that we really don't expect people to use, one of the issues is pluggable managers. From the early days of Nova the classes that ran the service managers were defined in the config file.

[openstack-dev] [Trove] [FFE] DB2 Backup & Restore and CouchDB functions

I'd like to request a feature freeze exception for "Implement backup and restore functionality for db2 express c" [1] and "Implement database and user functions for CouchDB" [2] The patch implementing db2 backup and restore is up for review [3] and has covered unit tests. CouchDB user and database

[openstack-dev] [Trove][FFE] CouchDB Configuration Groups

I'd like to request a feature freeze exception for "CouchDB Configuration Groups". [1] The code/tests for this feature are complete and have been in review [2] since Feb 17. The FFE is being requested so that Sonali (or myself) address the nits reviewers left and to have more time to review/test

Re: [openstack-dev] [Neutron][LBaaS]Removing LBaaS v1 - are weready?

Kevin, If we are offering a migration tool it would be namespace -> namespace (or maybe Octavia since [1]) — given the limitations nobody should be using the namespace driver outside a PoC so I am a bit confused why customers can’t self migrate. With 3rd party Lbs I would assume vendors

Re: [openstack-dev] [murano][stable] New blocking stable/liberty bug 1552887

Hi Matt! FYI, it looks like a change made to the stable/liberty branch for murano  on 3/1 broke the unit tests Thank you for your notification. This issue was fixed a few hours ago in this patch [0] Cheers! [0] - https://review.openstack.org/#/c/286856/ --  Victor Ryzhenkin Quality Assurance

[openstack-dev] [release][horizon] django_openstack_auth 2.2.0 release (mitaka)

We are tickled pink to announce the release of: django_openstack_auth 2.2.0: Django authentication backend for use with OpenStack Identity This release is part of the mitaka release series. With source available at: http://git.openstack.org/cgit/openstack/django_openstack_auth/ With

[openstack-dev] [release][barbican] python-barbicanclient 4.0.0 release (mitaka)

We are tickled pink to announce the release of: python-barbicanclient 4.0.0: Client Library for OpenStack Barbican Key Management API This release is part of the mitaka release series. With source available at: https://git.openstack.org/cgit/openstack/python-barbicanclient/ Please report

[openstack-dev] [Trove][FFE] Vertica Cluster Grow and Shrink

I'd like to request a feature freeze exception for "Vertica Cluster Grow and Shrink". [1] The code/tests for this feature are complete and have been in review [2] since Feb 17. The FFE is being requested so that the reviewers have more time to review/test etc. Hopefully the review process can

[openstack-dev] [Trove][FFE] Vertica configuration groups

I'd like to request a feature freeze exception for "Vertica configuration groups". [1] The code/tests for this feature are complete and have been in review [2] since Feb 23. The FFE is being requested so that the reviewers have more time to review/test etc. Hopefully the review process can be

[openstack-dev] [Neutron] Mitaka release planning

Hi Neutrinos, Mitaka-3 is out [1] and we should be focussing on rc1. This is the time where we switch gear: - Test M-3, find issues and target them for RC1 [2]; - Apply/agree for FFE status for pending features on the postmortem [3]; - For features that get FFE granted, I'll be moving

[openstack-dev] [docs] Octavia configuration options were deleted but needed for Mitaka

This is in reference to bug: https://bugs.launchpad.net/openstack-manuals/+bug/1552797 The liberty documentation set has the octavia.conf section: http://docs.openstack.org/liberty/config-reference/content/networking-plugin-lbaas.html The current Mitaka documentation does not have an

[openstack-dev] [murano][stable] New blocking stable/liberty bug 1552887

FYI, it looks like a change made to the stable/liberty branch for murano on 3/1 broke the unit tests, details are in the bug: https://bugs.launchpad.net/murano/+bug/1552887 -- Thanks, Matt Riedemann __ OpenStack

[openstack-dev] [nova] deprecating pluggable managers

As we were evaluating bits of configuration that we really don't expect people to use, one of the issues is pluggable managers. From the early days of Nova the classes that ran the service managers were defined in the config file. However, something we largely haven't supported in a real way in a

Re: [openstack-dev] [nova][cinder] Limits on volume read throughput?

On 03/03/2016 01:13 PM, Preston L. Bannister wrote: > Scanning the same volume from within the instance still gets the same > ~450MB/s that I saw before. Hmmm, with iSCSI inbetween that could be the TCP memcpy limitation. Measuring iSCSI in isolation is next on my list. Both on

Re: [openstack-dev] [sahara] FFE Request for Improving anti-affinity in Sahara

Hi, On Fri, Mar 4, 2016 at 12:43 AM, Sergey Lukjanov wrote: > Hi, > > correct spec link is https://review.openstack.org/#/c/269202/ > Sorry for the incorrect links Specification Review: https://review.openstack.org/#/c/269202/

Re: [openstack-dev] [nova][cinder] Limits on volume read throughput?

Note that my end goal is to benchmark an application that runs in an instance that does primarily large sequential full-volume-reads. On this path I ran into unexpectedly poor performance within the instance. If this is a common characteristic of OpenStack, then this becomes a question of concern

Re: [openstack-dev] [sahara] FFE Request for Improving anti-affinity in Sahara

Hi, correct spec link is https://review.openstack.org/#/c/269202/ Spec isn't approved and so FFE isn't granted. It's very important to not spread the team's efforts onto reviewing specs and additional features in the pre-RC time frame, so, I'm considering non-merged spec as a blocker for FFE.

Re: [openstack-dev] [Neutron] Evolving the stadium concept

Hi folks, Status update on this matter: Russell, Kyle and I had a number of patches out [1], to try and converge on how to better organize Neutron-related efforts. As a result, a number of patches merged and a number of patches are still pending. Because of Mitaka feature freeze, other

[openstack-dev] [sahara] FFE Request for Improving anti-affinity in Sahara

Hi folks, I would like to request a FFE for the feature “Improving anti-affinity in Sahara”: BP: https://blueprints.launchpad.net/sahara/+spec/improving-anti-affinity Specification Review:

Re: [openstack-dev] [neutron] - Changing the Neutron default security group rules

Mathieu Gagné wrote: > We had issue with GRE but unrelated to the one mentioned above. > > Although security group is configured to allow GRE, > nf_conntrack_proto_gre module is not loaded by iptables/Neutron and > traffic is dropped. We had to load the module manually. > Let's put together a

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

During our meeting this morning we touched on some of the excellent stuff markvan is doing with Horizon integration testing (thanks!) We also talked some more about transition/implementation details around using GLARE as the backend for the app catalog. kzaitsev_mb is making some excellent

Re: [openstack-dev] [Openstack-operators] OpenStack Contributor Awards

On Tue, Feb 16, 2016 at 2:48 AM Tom Fifield wrote: > > in the meantime, let's use this thread to discuss the fun part: goodies. > What do you think we should lavish award winners with? Soft toys? > Perpetual trophies? baseball caps ? > "I made a substantial contribution to

Re: [openstack-dev] [ceilometer] Unable to get IPMI meter readings

So, we upgraded our openstack install from Juno to Kilo 2015.1.1 Not sure if this fixed some stuff, but I can now get samples for hardware.ipmi.(fan|temperature). However, I want to get hardware.ipmi.node.power samples and I get the following error in the ceilometer log- ERROR

Re: [openstack-dev] [neutron] - Changing the Neutron default security group rules

On 2016-03-03 12:53 PM, Sean M. Collins wrote: > sridhar basam wrote: >> This doesn't sound like a neutron issue but an issue with how the >> conntrack module for GRE changed in the kernel in 3.18. >> >> >> http://comments.gmane.org/gmane.comp.security.firewalls.netfilter.general/47705 >> >> Sri >

Re: [openstack-dev] [fuel][plugins] Should we maintain example plugins?

IMHO it is important to keep plugin examples and keep testing them, very valuable for plugin developers. For example, I've encountered [0] the case where "plugin as role" feature wasn't easily testable with fuel-qa because not compliant with the last plugin data structure, and more recently we've

Re: [openstack-dev] [neutron] - Changing the Neutron default security group rules

sridhar basam wrote: > This doesn't sound like a neutron issue but an issue with how the > conntrack module for GRE changed in the kernel in 3.18. > > > http://comments.gmane.org/gmane.comp.security.firewalls.netfilter.general/47705 > > Sri Oooh! Wicked nice find. Thanks Sri! -- Sean M.

[openstack-dev] [Murano] [FFE] Support TOSCA definitions for applications

Hi all, I would like to request a feature freeze exception for "Support TOSCA definitions for applications" [1]. The spec is already merged [2], patch is on review [3] and the task is almost finished. I am looking forward for your decision about considering this change for a FFE. [1]

Re: [openstack-dev] [neutron] - Changing the Neutron default security group rules

Hi Jon, As part of our FWaaS V2 efforts [1] we have been rethinking FWaaS and Security Groups. The idea is that eventually to augment Security Groups with some richer functionality and provide a default FWaaS policy to add to the (vm) port. Furthermore there is a way to “share” Firewall rules

[openstack-dev] [release][ironic] ironic-lib 1.1.0 release (mitaka)

We are pumped to announce the release of: ironic-lib 1.1.0: Ironic common library This release is part of the mitaka release series. With package available at: https://pypi.python.org/pypi/ironic-lib For more details, please see below. Changes in ironic-lib 1.0.0..1.1.0

Re: [openstack-dev] [nova] Non-Admin user can show deleted instances using changes-since parameter when calling list API

On 3/3/2016 2:55 AM, Zhenyu Zheng wrote: Yes, I agree with you guys, I'm also OK for non-admin users to list their own instances no matter what status they are. My question is this: I have done some tests, yet we have 2 different ways to list deleted instances (not counting using

Re: [openstack-dev] [fuel][plugins] Should we maintain example plugins?

On Thu, Mar 3, 2016 at 7:19 AM, Matthew Mosesohn wrote: > > Hi Fuelers, > > I would like to bring your attention a dilemma we have here. It seems > that there is a dispute as to whether we should maintain the releases > list for example plugins[0]. In this case, this is

Re: [openstack-dev] [oslo] PTL for Newton and beyond

On 03/03/2016 04:05 AM, Flavio Percoco wrote: Thanks for all your hard work as an Oslo PTL. You did amazing and I think you'd do an awesome mentor for other folks as well. It was an honor to have you as a PTL and I look forward to keep working with you as an Oslo contributor. +2 +A ;) -Josh

Re: [openstack-dev] [nova] Non-Admin user can show deleted instances using changes-since parameter when calling list API

On 3/3/2016 10:02 AM, Matt Riedemann wrote: On 3/3/2016 2:55 AM, Zhenyu Zheng wrote: Yes, I agree with you guys, I'm also OK for non-admin users to list their own instances no matter what status they are. My question is this: I have done some tests, yet we have 2 different ways to list

  1   2   >