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 dele

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

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 is and does, so > thanks fo

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] 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: [openstack-dev] [nova] config options help text > > improvement: current status >

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.

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

[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: https://pypi.python.org/pyp

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 devil's advocate, but

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

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 exp

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 wa

Re: [openstack-dev] [Fuel][FFE] API must allow VIP to be manually set to ANY valid IP address

I'm glad to inform you that all required functionality for the feature was successfully landed into upstream and FFE is not needed anymore. On Mon, Feb 29, 2016 at 7:23 PM, Artem Roma wrote: > Colleagues, > I would like to request a feature freeze exception for 'API must allow VIP > to be manual

Re: [openstack-dev] [docs] Can we get the "configuration reference" of master more often?

On Thu, Mar 3, 2016 at 9:51 AM, Andreas Jaeger wrote: > On 2016-03-03 15:37, Markus Zoeller wrote: > > The "configuration reference" manual at [1] is really helpful to get > > an overview of the options and we (Nova folks) were wondering if we > > could have that updated more often [2]. > > > > R

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

On Wed, Mar 02, 2016 at 10:19:50PM +, James Denton wrote: :My opinion is that the current stance of ‘deny all’ is probably the safest bet for all parties (including users) at this point. It’s been that way for years now, and is a substantial change that may result in little benefit. After all

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

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 devil's advocate, but wouldn't the main difference between notifications and hooks be that

[openstack-dev] [release][stable][keystone] keystone 8.1.0 release (liberty)

We are jazzed to announce the release of: keystone 8.1.0: OpenStack Identity This release is part of the liberty stable release series. For more details, please see below. 8.1.0 ^ New Features * [bug 1490804 (https://bugs.launchpad.net/keystone/+bug/1490804)] Audit IDs are

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

> > * 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 forward with a > > developer change in default value, ranges etc (changing help tex

Re: [openstack-dev] FW: [magnum][magnum-ui] Liaisons for I18n

I added Magnum to the list... Feel free to add your name and IRC nick, Shu. https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n > One thing to note. > > The role of i18n liaison is not to keep it well translated. > The main role is in a project side, > for example, to encourage i18n relate

Re: [openstack-dev] [docs] Can we get the "configuration reference" of master more often?

On 2016-03-03 15:37, Markus Zoeller wrote: > The "configuration reference" manual at [1] is really helpful to get > an overview of the options and we (Nova folks) were wondering if we > could have that updated more often [2]. > > Right now it is from November 2015 [3] and we (Nova folks) put a l

[openstack-dev] [release][stable][keystone] keystoneauth1 1.1.2 release (liberty)

We are thrilled to announce the release of: keystoneauth1 1.1.2: Authentication Library for OpenStack Identity This release is part of the liberty stable release series. With source available at: http://git.openstack.org/cgit/openstack/keystoneauth Please report issues through launchpad:

[openstack-dev] [release][stable][keystone] keystonemiddleware 2.3.3 release (liberty)

We are jazzed to announce the release of: keystonemiddleware 2.3.3: Middleware for OpenStack Identity This release is part of the liberty stable release series. With source available at: http://git.openstack.org/cgit/openstack/keystonemiddleware Please report issues through launchpad:

Re: [openstack-dev] [docs] Can we get the "configuration reference" of master more often?

On Thu, Mar 3, 2016 at 8:37 AM, Markus Zoeller wrote: > The "configuration reference" manual at [1] is really helpful to get > an overview of the options and we (Nova folks) were wondering if we > could have that updated more often [2]. > > Right now it is from November 2015 [3] and we (Nova folk

[openstack-dev] [docs] Can we get the "configuration reference" of master more often?

The "configuration reference" manual at [1] is really helpful to get an overview of the options and we (Nova folks) were wondering if we could have that updated more often [2]. Right now it is from November 2015 [3] and we (Nova folks) put a lot of effort this cycle in improving the help of our

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

On Wed, Mar 2, 2016 at 1:46 PM, Clark Boylan wrote: > On Wed, Mar 2, 2016, at 09:38 AM, Sean M. Collins wrote: > > 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 > >

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

Hey liusheng, When I run the command event-list with admin tenant I get all the available events but when I run the same command with demo environment variables set,I get empty list. So why I am not able to get the events for instances running on demo tenant like admin??? Regards, Umar On Mar 3, 20

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

Hi, All patches for DPDK feature [1] are on review, new patches are not expected: * https://review.openstack.org/286611 Support for DPDK enablement on node interfaces * https://review.openstack.org/284283 Add DPDK support for node interfaces For DPDK bonding [2]: * https://review.openstack.org/2

[openstack-dev] [Trove][FFE] Module management

I'd like to request a feature freeze exception for "Add support for adding and applying module configuration to an instance" [1] The work was split up and several parts of this have already merged in Mitaka. [2][3][4]. I have one more troveclient commit and a commit for the remainder of the ser

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

Excerpts from Davanum Srinivas (dims)'s message of 2016-03-03 06:32:42 -0500: > 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

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

+1. Thanks Dims!:) Regards, Martin - Martin Hickey | Software Development | OpenStack | Tel: + 353 21 7306040 From: Gary Kotton To: "OpenStack Development Mailing List (not for usage questions)" Date: 03/03/2016 12:40 Subject:Re: [openstack-dev] [oslo] PTL for Ne

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

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 for adding version 9.0 to the list. Right now, we run a swarm test that tries to install the e

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

Hey liusheng, When I run the command event-list with admin tenant I get all the available events but when I run the same command with demo environment variables set,I get empty list On Mar 3, 2016 2:19 PM, "liusheng" wrote: > Hi Umar, > You can only get the events(or events without project info)

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

Maksim, good job! +1 from my side though I am not a core. On Thu, Mar 3, 2016 at 4:10 PM, Aleksey Zvyagintsev < azvyagint...@mirantis.com> wrote: > +1 > > On Thu, Mar 3, 2016 at 12:57 PM, Aleksandr Didenko > wrote: > >> +1 >> >> On Thu, Mar 3, 2016 at 11:00 AM, Kyrylo Galanov >> wrote: >> >>> +

Re: [openstack-dev] [Horizon] Blueprints for Outreachy internship

Hi Richard, Thanks for you reply. I had a short conversation with Matthias and we decided to put the blueprint for context-sensitive help as an internship idea for now. Maybe I add another project to the list, then I can look

[openstack-dev] [nova] Identifying Mitaka release blockers

We have now 11-15 days left [1] until it is planned to release the first release candidate. To provide a stable release, we need to identify the potential release blockers. Bugs which potentially block the release should be tagged with "mitaka-rc-potential". They can then be queried in Launchpad w

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

+1 On Thu, Mar 3, 2016 at 12:57 PM, Aleksandr Didenko wrote: > +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,

Re: [openstack-dev] [puppet] adding ovs dpdk agent into neutron

> -Original Message- > From: Vladimir Eremin [mailto:vere...@mirantis.com] > Sent: Wednesday, March 2, 2016 8:49 PM > To: OpenStack Development Mailing List (not for usage questions) > > Cc: Emilien Macchi ; m...@mattfischer.com; Mooney, > Sean K > Subject: Re: [openstack-dev] [puppet]

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, Davanum Srinivas wrote: > >> Team, > >>

Re: [openstack-dev] [puppet] adding ovs dpdk agent into neutron

> -Original Message- > From: Emilien Macchi [mailto:emil...@redhat.com] > Sent: Wednesday, March 2, 2016 8:33 PM > To: Ptacek, MichalX ; 'OpenStack Development > Mailing List (not for usage questions)' d...@lists.openstack.org>; m...@mattfischer.com > Cc: Mooney, Sean K ; Czesnowicz, Prz

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

+1 Gracias Dims! On 3/3/16, 2:26 PM, "Sean Dague" wrote: >On 03/03/2016 06:32 AM, 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 f

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

On 03/03/2016 06:32 AM, 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 and help smoothen the

[openstack-dev] [Fuel] [Ci] New 'fuel-astute' gate job

Hi to all, please be informed that starting from today we're launching gate job [1] for 'fuel-astute' package [2] Mentioned job will be triggered on each commit and will perform next steps: - build a package from the commit - run system tests scenario [3] with using created package - vote in a pa

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

Markus Zoeller/Germany/IBM@IBMDE wrote on 03/03/2016 11:45:52 AM: > From: Markus Zoeller/Germany/IBM@IBMDE > To: "OpenStack Development Mailing List \(not for usage questions\)" > > Date: 03/03/2016 11:47 AM > Subject: Re: [openstack-dev] [nova] config options help text > improvement: current s

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

On 03/03/16 06:32 -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 Btw, small nit, it's in R-3 (March 14-18). http://releases.openstack.org/mitaka/schedule.html Flav

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

On 03/03/16 06:32 -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 and help smoothen the transiti

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

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: [openstack-dev] [nova] config options help text > improvement: current status > > Excerpts from Markus Zoeller's message of 2016-03-02 18:45:45 +0100: > > [a lo

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

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 and help smoothen the transition process if you let me know about your interest i

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 security groups to allow all traffic. They had a few reasons for th

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. >> >> They had a few reasons for this that I will

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

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 2.5/2.6/2.3.1 but > 2.4? > In the etherpad

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 we've successfully moved [1] virtual-box scripts from fuel-main >>> [2

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

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 > > > > On 3/2/2016 11:45 AM, Markus Zoeller wrote: > > TL;

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 :-( What caught my eye was

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 text > improvement: current status > > On 2016-03-02 19:11, Tim

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 inte

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] [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 fuel-virtualbox [3] git repo, I propose to update >> fuel-v

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 chang

[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 Mars Ma, Please email this question to the

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 port_security port

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' out of the box so the

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] [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] [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 /v2.1/62bfb653eb0d4d5cabdf635dd81

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 tem

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

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 http://docs.openstack.org/draft/c

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 using >> "changes-since" par

<    1   2