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 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] 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 >

[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] 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. --

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] 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

[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] [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

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] [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] [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] [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] [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] [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. =) -- 

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] [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

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] [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] 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] [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] [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] [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] [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] [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] 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

[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

[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] [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

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. --

[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] [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] [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] [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

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] [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] [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] [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

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] [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?

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] [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] [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] [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] [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

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

[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

[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] [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] [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] [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] [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] [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] [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] [ironic] Remember to follow RFE process

Hi, > Ironic'ers, please remember to follow the RFE process; especially the cores. > > I noticed that a patch [1] got merged yesterday. The patch was associated > with an RFE [2] that hadn't been approved yet :-( What caught my eye was > that the commit message didn't describe the actual API

Re: [openstack-dev] [Fuel] Nominate Maksim Malchuk for the fuel-virtualbox-core team

+1 On Thu, Mar 3, 2016 at 2:53 AM, Roman Vyalov wrote: > +1 > > On Wed, Mar 2, 2016 at 5:47 PM, Sergey Kulanov > wrote: > >> Hey Fuelers, >> >> Since we've successfully moved [1] virtual-box scripts from fuel-main [2] >> to >> separate

Re: [openstack-dev] [Fuel] Nominate Maksim Malchuk for the fuel-virtualbox-core team

+1 On Thu, Mar 3, 2016 at 11:00 AM, Kyrylo Galanov wrote: > +1 > > On Thu, Mar 3, 2016 at 2:53 AM, Roman Vyalov wrote: > >> +1 >> >> On Wed, Mar 2, 2016 at 5:47 PM, Sergey Kulanov >> wrote: >> >>> Hey Fuelers, >>> >>> Since

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

Hello team's , Please take in mind my HUGE +1 We really need to remove package building process from iso build flow. On Wed, Mar 2, 2016 at 3:40 PM, Vladimir Kozhukalov < vkozhuka...@mirantis.com> wrote: > Andrew, > > I think everything will be ready by Wednesday 03/09/2016. We have just >

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

Kevin Benton wrote: * Neutron cannot be trusted to do what it says it's doing with the security groups API so users want to orchestrate firewalls directly on their instances. If that’s really a reason for someone, then they should just use ’noop' firewall_driver. Or

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

Salvatore Orlando wrote: On 3 March 2016 at 10:38, Ihar Hrachyshka wrote: Kevin Benton wrote: Hi, I know this has come up in the past, but some folks in the infra channel brought up the topic of changing the default

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

Kevin Benton wrote: Hi, I know this has come up in the past, but some folks in the infra channel brought up the topic of changing the default security groups to allow all traffic. They had a few reasons for this that I will try to summarize here: * Ports 'just work'

Re: [openstack-dev] [ironic] Remember to follow RFE process

2016-03-03 11:01 GMT+01:00 Lucas Alvares Gomes : > Hi, > > > Ironic'ers, please remember to follow the RFE process; especially the > cores. > > > > I noticed that a patch [1] got merged yesterday. The patch was associated > > with an RFE [2] that hadn't been approved yet

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

Hi, Jim, Julia, and Ironicers, I have some questions about the BFV. > > * Hardware supports the UEFI 2.4 spec Could you please explain the reason that chose version not 2.5/2.6/2.3.1 but 2.4? In the etherpad[1], I was not able to read the reason why ironicers chose version 2.4. [1]

Re: [openstack-dev] [Neutron] VM could not get IP from dhcp server

Hi Michal Thanks for your reply. I think it's not the problem of scurity group rule, as comparing the working environment. The vxlan tunnel works correctly, and the packet sent from vm have arrived at network node, meanwhile we catch it on physical NIC, but do not catch it on vxlan port.

Re: [openstack-dev] [nova] config options help text improvement: current status

Andreas Jaeger wrote on 03/03/2016 09:31:44 AM: > From: Andreas Jaeger > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 03/03/2016 09:43 AM > Subject: Re: [openstack-dev] [nova] config options help

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

On 3 March 2016 at 10:38, Ihar Hrachyshka wrote: > Kevin Benton wrote: > > Hi, >> >> I know this has come up in the past, but some folks in the infra channel >> brought up the topic of changing the default security groups to allow all >> traffic. >> >>

Re: [openstack-dev] [nova] config options help text improvement: current status

Matt Riedemann wrote on 03/03/2016 03:50:18 AM: > From: Matt Riedemann > To: openstack-dev@lists.openstack.org > Date: 03/03/2016 03:51 AM > Subject: Re: [openstack-dev] [nova] config options help text > improvement: current status > >

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

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 changes-since): 1. "GET

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

Thanks & Best regards ! Mars Ma -- Forwarded message -- From: Gal Sagie Date: Thu, Mar 3, 2016 at 5:41 PM Subject: Re: [kuryr] Docker cannot find the created network with kuryr driver To: Mars Ma Hello

Re: [openstack-dev] [fuel] Newton PTL and CL elections

Dmitry Borodaenko wrote: Team, We're only two weeks away from the beginning of the Newton elections period. Based on the Fuel 9.0/Mitaka release schedule [0], I propose the following dates for PTL and CL self-nomination and election periods: PTL self-nomination: March 13-20 PTL election: March

Re: [openstack-dev] [cinder] Proposal: changes to our current testing process

On 02/03, Ivan Kolodyazhny wrote: > I'll try to implement such scenario and step-by-step guideline soon. > That would be fantastic!! Thank you very much Looking forward to it. :-) Cheers, Gorka. > Regards, > Ivan Kolodyazhny, > http://blog.e0ne.info/ > > On Wed, Mar 2, 2016 at 5:16 PM, Eric

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

Hi Daisuke, On Thu, Mar 3, 2016 at 10:53 AM, Fujita, Daisuke wrote: > Hi, Jim, Julia, and Ironicers, > > I have some questions about the BFV. > >> > * Hardware supports the UEFI 2.4 spec > > Could you please explain the reason that chose version not

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

On Wed, Mar 02, 2016 at 11:36:17AM -0800, Gregory Haynes wrote: :Clearly, some operators and users disagree with the opinion that 'by :default security groups should closed off' given that we have several :large public providers who have changed these defaults (despite there :being no documented

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

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 "make world" approach ASAP. Cheers, Thomas Goirand (zigo)

Re: [openstack-dev] [nova] config options help text improvement: current status

Excerpts from Markus Zoeller's message of 2016-03-03 12:50:55 +0100: > Doug Hellmann wrote on 03/02/2016 07:19:22 PM: > > > From: Doug Hellmann > > To: openstack-dev > > Date: 03/02/2016 07:20 PM > > Subject: Re:

Re: [openstack-dev] [oslo][all] Documenting configuration options lifespan

Excerpts from Ronald Bradford's message of 2016-03-03 09:54:16 -0500: > > > * When an option is changed, or marked as deprecated, during normal > > reviews > > > it should then be identified accordingly with these new attributes. > > > * The "changed" attribute would only be applicable moving

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

On Wed, Mar 02, 2016 at 02:05:40PM -0600, Monty Taylor wrote: :(try writing an idempotent ansible playbook that tries to make your :security group look exactly like you want it not knowing in advance :what security group rules this provider happens to want to give you :that you didn't think to

[openstack-dev] [release][glance] glance_store 0.13.0 release (mitaka)

We are stoked to announce the release of: glance_store 0.13.0: OpenStack Image Service Store Library This release is part of the mitaka release series. With source available at: http://git.openstack.org/cgit/openstack/glance_store With package available at:

Re: [openstack-dev] [Fuel] UI code freeze

Fuel UI code has been completely removed from fuel-web repo and CI jobs to verify fuel-web RR with fuel-ui code and fuel-ui RR with fuel-web code have been set up. So the code separation can be considered as done. Though there is one thing needs to be done and we don't know how to solve that task

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

2016-03-03 2:11 GMT+08:00 Matt Riedemann : > > > On 3/2/2016 3:02 AM, Zhenyu Zheng wrote: > >> Hi, Nova, >> >> While I'm working on add "changes-since" parameter support for >> python-novaclient "list" CLI. >> >> I realized that non-admin can list all deleted instances

Re: [openstack-dev] [nova] config options help text improvement: current status

On 2016-03-02 19:11, Tim Bell wrote: > > Great. Does this additional improved text also get into the configuration > guide documentation somehow ? It should, the reference part of configuration guide is autogenerated. The current draft version for Mitaka is at

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

On Wed, Mar 02, 2016 at 05:40:20PM -0500, Zane Bitter wrote: > On 02/03/16 05:50, Mathieu Velten wrote: > >Hi all, > > > >I am looking at a way to spawn nodes in different specified > >availability zones when deploying a cluster with Magnum. > > > >Currently Magnum directly uses predefined Heat

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

Hi Umar, You can only get the events(or events without project info) belong to admin tenant if you run event-list command with admin project; and you can only get the events belong to demo tenant with event-list running with demo project. -- Liu sheng 在 2016/3/1 14:00, Umar Yousaf 写道: I have

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

Thank you both for your answers ! Indeed I need it sooner rather than later (as usual :) ) so the Newton release is a bit too far away. In the meantime I just test your solution with the index and the map and it works great !  I'll use that for now, and we will discuss taking over the Heat bp

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

On Thu, Mar 03, 2016 at 09:09:03AM -0600, Sam Matzek wrote: > On Wed, Mar 2, 2016 at 8:25 PM, Adam Young wrote: > > On 02/29/2016 01:49 PM, Andrew Laski wrote: > >> > >> > >> On Mon, Feb 29, 2016, at 01:18 PM, Dan Smith wrote: > > Forgive my ignorance or for playing

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

On Thu, Mar 3, 2016 at 8:22 AM, Ronald Bradford wrote: > Dims, > > As my first project and cycle in OpenStack I have really appreciated your > input and direction as I was starting out and during Mitaka cycle. > It has been great to learn just a bit of what PTL of Oslo

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

Dims, As my first project and cycle in OpenStack I have really appreciated your input and direction as I was starting out and during Mitaka cycle. It has been great to learn just a bit of what PTL of Oslo is and does, so thanks for all your hard work. I hope I can work with the team to help turn

[openstack-dev] [networking guide] - Meeting reminder

Folks, Just a kind reminder that our IRC meeting will start in 20 minutes. https://wiki.openstack.org/wiki/Documentation/NetworkingGuide/Meetings Channel: #openstack-meeting Thanks, Edgar __ OpenStack Development Mailing

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

Hi Mars, I get similar problem before, it is because I capability_scope is global. After I modify it to local, it works. But it should already be fixed in the following patch: https://review.openstack.org/#/c/264653/ You may check your capability_scope config or use latest code to have a try.

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

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

[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

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

On Feb 5 I was given a tarchive of kuryr with an install script that configures the docker daemon to use consul as its cluster store. If I modify the config of docker to use etcd instead then do I need to change anything in Kuryr? Thanks, Mike

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] [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] [oslo] PTL for Newton and beyond

Dims, Thanks a lot for your hard work being PTL! It has been great working with you! Thanks, Oleksii On Thu, Mar 3, 2016 at 2:40 PM, Gary Kotton wrote: > +1 > > Gracias Dims! > > > > > On 3/3/16, 2:26 PM, "Sean Dague" wrote: > > >On 03/03/2016 06:32 AM,

  1   2   >