Re: [openstack-dev] [nova] about notification in nova

Hi, Are you using versioned notification? If you are using versioned nofitication, you should get an ``action_initiator_user`` and an ``action_initiator_project`` indicating who initiated this action, we had them since I649d8a27baa8840bc1bb567fef027c749c663432

Re: [openstack-dev] [nova] Volunteer needed to write reshaper FFU hook

I would like to help since I have now finished all the downstream works. But I may need to take some time understanding all the background information On Mon, Oct 29, 2018 at 11:25 PM Matt Riedemann wrote: > Given the outstanding results of my recruiting job last week [1] I have > been tasked

Re: [openstack-dev] [Searchlight] Reaching out to the Searchlight core members for Stein

Hi, Thanks for stand up, I would like to continue work on SL. On Sat, Aug 18, 2018 at 12:16 AM Trinh Nguyen wrote: > Dear Searchlight team, > > As you may know, the Searchlight project has missed several milestones, > especially the Rocky cycle. The TC already has the plan to remove >

Re: [openstack-dev] [Nova] A multi-cell instance-list performance test

Hi, Thanks alot for the reply, for your question #2, we did tests with two kinds of deployments: 1. There is only 1 DB with all 10 cells(also cell0) and it is on the same server with the API; 2. We took 5 of the DBs to another machine on the same rack to test out if it matters, and it turns out

Re: [openstack-dev] [docs][nova] about update flavor

's cpu?Otherwise,why we don't consider to add the function that > we can update the flavor's cpu? > > > -- Original -- > *From:* "Zhenyu Zheng"; > *Date:* 2018年8月16日(星期四) 下午3:56 > *To:* "OpenStack Developmen"; > *Subject:* Re: [open

Re: [openstack-dev] [docs][nova] about update flavor

We only allow update flavor descriptions(added in microversion 2.55) in Nova and what the horizon did was just delete the old one and create a new one, and I think it has been removed in last year. On Thu, Aug 16, 2018 at 3:19 PM Rambo wrote: > Hi,all > > I find it is supported that we

[openstack-dev] [Nova] A multi-cell instance-list performance test

like: max_thread_pool, use_tpool, etc. And we also tried to use a separate DB for some of the cells, but the result seems to be no big difference. So, the above are what we have now, and feel free to ping us if you have any questions or suggestions. BR, Zhenyu Z

Re: [openstack-dev] [nova]API update week 5-11

Thank you very much for the review and updates during the weekends. On Sat, Jul 14, 2018 at 4:05 AM Matt Riedemann wrote: > On 7/11/2018 9:03 PM, Zhenyu Zheng wrote: > > 2. Abort live migration in queued state: > > - > https://blueprints.launchpad.net/nova/+spec/ab

Re: [openstack-dev] [nova]API update week 5-11

> > 2. Abort live migration in queued state: > - > https://blueprints.launchpad.net/nova/+spec/abort-live-migration-in-queued-status > > - > https://review.openstack.org/#/q/topic:bp/abort-live-migration-in-queued-status+(status:open+OR+status:merged) > > - Weekly Progress: Review is going and it

Re: [openstack-dev] [nova] Continuously growing request_specs table

Thanks, I may have missed that one. On Mon, Jul 2, 2018 at 10:29 PM Matt Riedemann wrote: > On 7/2/2018 2:47 AM, Zhenyu Zheng wrote: > > It seems that the current request_specs record did not got removed even > > when the related instance is gone, which lead to a conti

[openstack-dev] [nova] Continuously growing request_specs table

Hi, It seems that the current request_specs record did not got removed even when the related instance is gone, which lead to a continuously growing request_specs table. How is that so? Is it because the delete process could be error and we have to recover the request_spec if we deleted it? How

Re: [openstack-dev] [nova] nova API meeting schedule

Glad to hear that the API meeting is happening again, I would also love to join. On Mon, Jun 11, 2018 at 10:49 AM Ghanshyam wrote: > Hi All, > > As you might know, we used to have Nova API subteam meeting on Wed [1] but > we did not continue that this year due to unavailability of members. > >

Re: [openstack-dev] [nova] Rocky PTG summary - cells

Thanks for the reply, both solution looks reasonable. On Thu, Mar 15, 2018 at 10:29 AM, melanie witt <melwi...@gmail.com> wrote: > On Thu, 15 Mar 2018 09:54:59 +0800, Zhenyu Zheng wrote: > >> Thanks for the recap, got one question for the "block creation": >

Re: [openstack-dev] [nova] Rocky PTG summary - cells

Thanks for the recap, got one question for the "block creation": * An attempt to create an instance should be blocked if the project has > instances in a "down" cell (the instance_mappings table has a "project_id" > column) because we cannot count instances in "down" cells for the quota >

[openstack-dev] [nova] Should we get auth from context for Neutron endpoint?

Hi Nova, While doing some test with my newly deployed devstack env today, it turns out that the default devstack deployment cannot cleanup networks after the retry attempt exceeded. This is because in the deployment with super-conductor and cell-conductor, the retry and cleanup logic is in

Re: [openstack-dev] [nova] PTL Election Season

Thanks for all the help in these cycles :) On Tue, Jan 23, 2018 at 5:34 PM, Yikun Jiang wrote: > Matt, Thanks for your all works. > As a beginner of Nova upstream player, really appreciate your patient > review and warm help. : ) > > Regards, > Yikun >

Re: [openstack-dev] [nova] heads up to users of Aggregate[Core|Ram|Disk]Filter: behavior change in >= Ocata

Thanks for the info, so it seems we are not going to implement aggregate overcommit ratio in placement at least in the near future? On Wed, Jan 17, 2018 at 9:19 AM, Zhenyu Zheng <zhengzhenyul...@gmail.com> wrote: > Thanks for the info, so it seems we are not going to implement

Re: [openstack-dev] [nova] heads up to users of Aggregate[Core|Ram|Disk]Filter: behavior change in >= Ocata

Thanks for the info, so it seems we are not going to implement aggregate overcommit ratio in placement at least in the near future? On Wed, Jan 17, 2018 at 5:24 AM, melanie witt wrote: > Hello Stackers, > > This is a heads up to any of you using the AggregateCoreFilter, >

[openstack-dev] [nova][cinder] Questions about truncked disk serial number

Hi, I meet a problem like this recently: When attaching a volume to an instance, in the xml, the disk is described as: [image: Inline image 1] where the serial number here is the volume uuid in Cinder. While inside the vm: in /dev/disk/by-id, there is a link for /vdb with the name of

Re: [openstack-dev] [nova][cinder] Questions about truncked disk serial number

, Zhenyu Zheng <zhengzhenyul...@gmail.com> wrote: > Hi, > > I meet a problem like this recently: > > When attaching a volume to an instance, in the xml, the disk is described > as: > > [image: Inline image 1] > where the serial number here is the volume uuid in Cinder.

Re: [openstack-dev] [all] Switching to longer development cycles

The contributors in APAC are growing and wish to be more involved in OpenStack, it will be really hard for us to join informal meetups( VISA Invitation letters, company support etc.) So I really hope the current official technical gathering remains, so that we can be more involved with the

Re: [openstack-dev] [all] Switching to longer development cycles

On Thu, Dec 14, 2017 at 7:02 PM, Kashyap Chamarthy wrote: > [..] > > For a relatively mature (~7 years; and ~5 years if we count from the > time governance changed to OpenStack Foudation) project, one official > contributor gathering per year sounds fine. And for those that

Re: [openstack-dev] [nova] reset key pair during rebuilding

Hi, FYI, we are going to use the existing PUT /servers/{server_uuid} API, adding the 'key_name' field. On Sat, Sep 23, 2017 at 9:58 PM, LIU Yulong wrote: > Hi nova developers, > > This mail is proposed to reconsider the key pair resetting of instance. > The nova queens

Re: [openstack-dev] [Horizon][Nova] Editing flavor causing instance flavor display error

ete action that causes all the problem. Maybe horizon can provide a copy-and-modify action and leave the deletion of the flavor to the admin. On Thu, Aug 3, 2017 at 5:59 PM, Sean Dague <s...@dague.net> wrote: > On 08/02/2017 10:12 PM, Zhenyu Zheng wrote: > > Hi All, > > > >

[openstack-dev] [Horizon][Nova] Editing flavor causing instance flavor display error

Hi All, Horizon provided the feature to allow user edit existing flavors, no matter it is currently used by any instances or not. While Nova doesn't provide this kind of ability, Horizon achieved this by deleting the old flavor first and create a new flavor with the requested properties. And the

Re: [openstack-dev] [Nova][Neutron] Allow passing security groups when attaching interfaces?

ill >>> have the default security group. >>> >>> You could try the first option by attaching the security group to the >>> port >>> >>> Thanks >>> >>> Gary >>> >>> *From: *Zhenyu Zheng <zhengzhenyul...@

[openstack-dev] [Nova][Neutron] Allow passing security groups when attaching interfaces?

Hi, Our product has meet this kind of problem, when we boot instances, we are allowed to pass security groups, and if we provided network id, ports with the sg we passed will be created and when we show instances, we can see security groups field of instance is the sg we provided. But when we

Re: [openstack-dev] [nova] Need volunteer(s) to help migrate project docs

I will help On Sat, Jun 24, 2017 at 12:23 AM, Matt Riedemann wrote: > The spec [1] with the plan to migrate project-specific docs from > docs.openstack.org to each project has merged. > > There are a number of steps outlined in there which need people from the > project

Re: [openstack-dev] [openstack-dev[[nova] Simple question about sorting CPU topologies

Friesen wrote: > > > On 06/20/2017 06:29 AM, Jay Pipes wrote: > > >> On 06/19/2017 10:45 PM, Zhenyu Zheng wrote: > > >>> Sorry, The mail sent accidentally by mis-typing ... > > >>> > > >>> My question is, what is the benefit of the above pre

Re: [openstack-dev] [openstack-dev[[nova] Simple question about sorting CPU topologies

Sorry, The mail sent accidentally by mis-typing ... My question is, what is the benefit of the above preference? BR, Kevin On Tue, Jun 20, 2017 at 10:43 AM, Zhenyu Zheng <zhengzhenyul...@gmail.com> wrote: > Hi, > > In https://github.com/openstack/nova/blob/master/ > nova/vir

[openstack-dev] [openstack-dev[[nova] Simple question about sorting CPU topologies

Hi, In https://github.com/openstack/nova/blob/master/nova/virt/hardware.py#L396 we calculated every possible CPU topologies and sorted by: # We want to # - Minimize threads (ie larger sockets * cores is best) # - Prefer sockets over cores possible = sorted(possible, reverse=True, key=lambda x:

[openstack-dev] [nova][cinder] Ceph volumes attached to local deleted instance could not be correctly handled

Hi all, We have met the following problem: we deployed our env with ceph as volume backend, we boot an instance and attach a ceph volume to this instance, when our nova-compute is down and we delete this instance, it will go local_delete and the ceph volume we attached to this instance will

Re: [openstack-dev] [nova][searchlight] When do instances get removed from Searchlight?

, March 6, 2017, Balazs Gibizer <balazs.gibi...@ericsson.com> wrote: > > > On Mon, Mar 6, 2017 at 3:09 AM, Zhenyu Zheng <zhengzhenyul...@gmail.com> > wrote: > >> Hi, Matt >> >> AFAIK, searchlight did delete the record, it catch the instance.delete &g

Re: [openstack-dev] [nova][searchlight] When do instances get removed from Searchlight?

Hi, Matt AFAIK, searchlight did delete the record, it catch the instance.delete notification and perform the action: http://git.openstack.org/cgit/openstack/searchlight/tree/searchlight/elasticsearch/plugins/nova/notification_handler.py#n100 ->

Re: [openstack-dev] [nova][docs] Is anyone interested in being the docs liaison for Nova?

Hi, I'm not a native English speaker but I would like to have a try if possible :) On Wed, Mar 1, 2017 at 11:45 PM, Matt Riedemann wrote: > There is a need for a liaison from Nova for the docs team to help with > compute-specific docs in the install guide and various

Re: [openstack-dev] [nova] Pike PTG recap - cells

Matt, Thanks for the recap, it's a pity I cannot attend PTG due to personal reason, I will be willing to take the work you mentioned, and will check the details with you. And another thing, I don't know whether you guys discussed or not, I saw in [1] we are talking about adding tags field(and

Re: [openstack-dev] [nova][cinder] Schedule Instances according to Local disk based Volume?

BTW, I think this can be done using new placement service, using the custom resource provider? correct? On Fri, Feb 24, 2017 at 10:18 AM, Zhenyu Zheng <zhengzhenyul...@gmail.com> wrote: > Matt, > > Thanks for the information, I will check that; But still I think the user > dem

Re: [openstack-dev] [nova][cinder] Schedule Instances according to Local disk based Volume?

On Fri, Feb 24, 2017 at 4:06 AM, Matt Riedemann <mrie...@linux.vnet.ibm.com> wrote: > On 9/26/2016 9:21 PM, Zhenyu Zheng wrote: > >> Hi, >> >> Thanks for the reply, actually approach one is not we are looking for, >> our demands is to attach the real physica

[openstack-dev] [Nova] How boot with bdm_v2={source_type=image, destination_type=local} should been used?

Hi All, As I was working on "Check destination_type when booting with bdm provided": https://review.openstack.org/#/c/402372/ and addressing reviewers comments, I find out that the current source_type=image, destination_type=local seems unusable. According to docs:

Re: [openstack-dev] [nova] Device tag in the API breaks in the old microversion

Thanks Alex for raising this up widely, as Chinese holiday is comming and Alex and me might be away for a week, And it will be better to fix this faster, so thanks Artom taking over to fix it :) On Wed, Jan 25, 2017 at 7:50 AM, Ghanshyam Mann wrote: > > On Wed, Jan 25,

Re: [openstack-dev] [nova] Different length limit for tags in object definition and db model definition

OK, added to my todo for the next cycle. On Tue, Jan 17, 2017 at 7:08 PM, Matt Riedemann wrote: > On 1/17/2017 3:31 AM, Roman Podoliaka wrote: > >> Hi all, >> >> Changing the type of column from VARCHAR(80) to VARCHAR(60) would also >> require a data migration (i.e.

Re: [openstack-dev] [nova] Different length limit for tags in object definition and db model definition

OK, then, lets try to work this out. On Tue, Jan 17, 2017 at 4:19 PM, Sergey Nikitin wrote: > Hi, Zhenyu! > > I think we should ask DB guys about migration. But my personal opinion is > that DB migration is much painful than new microversion. > > But it seems too late to

Re: [openstack-dev] [nova] Different length limit for tags in object definition and db model definition

amm...@gmail.com>: > >> On Tue, Jan 17, 2017 at 2:37 PM, Alex Xu <sou...@gmail.com> wrote: >> >>> >>> >>> 2017-01-17 10:26 GMT+08:00 Matt Riedemann <mrie...@linux.vnet.ibm.com>: >>> >>>> On 1/16/2017 7:12 PM, Zhenyu Zheng wro

[openstack-dev] [nova] Different length limit for tags in object definition and db model definition

Hi Nova, I just discovered something interesting, the tag has a limited length, and in the current implementation, it is 60 in the tag object definition: http://git.openstack.org/cgit/openstack/nova/tree/nova/objects/tag.py#n18 but 80 in the db model:

[openstack-dev] [searchlight] No Searchlight IRC meeting today

Hi everyone, As Travis sent out last week, most of the contributor will be on holiday this week and the next, so we decide not to hold the Searchlight IRC meeting today. The only remaining topic from last meeting was the pipeline patch: https://review.openstack.org/#/c/359972/ We have discussed

Re: [openstack-dev] [all] Adding CONTRIBUTING.rst files to projects

Agreed with Amrith, it might be useful and maybe also good for new contributors to learn how to have a commit to OpenStack. BUT over 130 identical patches to 130 different projects from one company/person in one run? I don't think this is going to help OpenStack growing. We should not let this

Re: [openstack-dev] [nova] Is this a correct use of scheduler hints and nova-scheduler

Thanks a for the information, I will propose a blueprint for the next cycle :) On Wed, Dec 7, 2016 at 4:38 PM, Sylvain Bauza <sba...@redhat.com> wrote: > > > Le 07/12/2016 04:21, Zhenyu Zheng a écrit : > > Hi all, > > > > I want to ask a question about us

[openstack-dev] [nova] Is this a correct use of scheduler hints and nova-scheduler

Hi all, I want to ask a question about using scheduler-hints, could we add custom scheduler keys to work with our custom filters? Is it designed to allow vendors add own custom filters and keys? Another question is, as we have now persistent scheduler-hints in request spec, is it possible to

Re: [openstack-dev] [searchlight] Propose Zhenyu Zheng for Searchlight core

om me, I'll be happy to see Kevin on the core list. >> >> On 10/19/16, 10:10 AM, "McLellan, Steven" <steve.mclel...@hpe.com> wrote: >> >> Hi, >> >> I'd like to propose Zhenyu Zheng (Kevin_Zheng on IRC) for Searchlight >> core. While he's most acti

Re: [openstack-dev] [nova] Propose to add FusionCompute driver to Nova

Thanks alot On Thu, Oct 13, 2016 at 5:26 PM, Christian Berendt < bere...@betacloud-solutions.de> wrote: > Hello Zheng. > > > On 13 Oct 2016, at 10:02, Zhenyu Zheng <zhengzhenyul...@gmail.com> > wrote: > > > > As mentioned above, FusionCompute has be

[openstack-dev] [nova] Propose to add FusionCompute driver to Nova

Hi All, We would like to propose FusionCompute driver to become an official Nova driver. FusionCompute is an computing virtualization software developed by Huawei, which can provide tuned high-performance and high reliabilities in VM instance provisioning, clustered resource pool management, and

Re: [openstack-dev] [nova][cinder] Schedule Instances according to Local disk based Volume?

So do we like the idea of "volume based scheduling?" On Tue, Sep 27, 2016 at 11:39 AM, Joshua Harlow wrote: > Huang Zhiteng wrote: > >> >> >> On Tue, Sep 27, 2016 at 12:00 AM, Joshua Harlow > > wrote: >> >> Huang

Re: [openstack-dev] [nova][cinder] Schedule Instances according to Local disk based Volume?

deployments. Thanks. On Mon, Sep 26, 2016 at 9:48 PM, Erlon Cruz <sombra...@gmail.com> wrote: > > > On Fri, Sep 23, 2016 at 10:19 PM, Zhenyu Zheng <zhengzhenyul...@gmail.com> > wrote: > >> Hi, >> >> Thanks all for the information, as for the filte

Re: [openstack-dev] [nova][cinder] Schedule Instances according to Local disk based Volume?

On Sun, Sep 25, 2016 at 1:02 AM, Matt Riedemann <mrie...@linux.vnet.ibm.com> wrote: > On 9/23/2016 8:19 PM, Zhenyu Zheng wrote: > >> Hi, >> >> Thanks all for the information, as for the filter >> Erlon(InstanceLocalityFilter) mentioned, this only solve

Re: [openstack-dev] [nova][cinder] Schedule Instances according to Local disk based Volume?

e a blueprint/spec for >> this and start working this through that. >> >> -Jay >> >> >> On 09/23/2016 02:51 AM, Zhenyu Zheng wrote: >> >> Hi Novaers and Cinders: >> >> Quite often application requirements would demand using locally attached

[openstack-dev] [nova][cinder] Schedule Instances according to Local disk based Volume?

Hi Novaers and Cinders: Quite often application requirements would demand using locally attached disks (or direct attached disks) for OpenStack compute instances. One such example is running virtual hadoop clusters via OpenStack. We can now achieve this by using BlockDeviceDriver as Cinder

[openstack-dev] [nova] Add support for tag instances when booting

/support-tag-instance-when-boot https://review.openstack.org/#/c/366469/ Comments? Thanks, Zhenyu Zheng __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org

Re: [openstack-dev] [Nova] Support specified volume_type when boot instance, do we like it?

ski wrote: > > > > > > > > On Mon, Aug 29, 2016, at 09:06 AM, Jordan Pittier wrote: > > > > > > > > > On Mon, Aug 29, 2016 at 8:50 AM, Zhenyu Zheng > > > <zhengzhenyul...@gmail.com> wrote: > > >> Hi, all > > >> >

[openstack-dev] [Nova] Support specified volume_type when boot instance, do we like it?

Hi, all Currently we have customer demands about adding parameter "volume_type" to --block-device to provide the support of specified storage backend to boot instance. And I find one newly drafted Blueprint that aiming to address the same feature:

[openstack-dev] [Nova] About deleting keypairs

Hi All, We have meet some problems when trying to cleanup resources, keypairs in particular. The scenario is like this, we have several projects in our public cloud, each project have their own admin, they can create and delete users, and their users may create keypairs; As keypairs are only

Re: [openstack-dev] [Nova] Questions about instance actions' update and finish

OK, then I will work on it in O On Thu, Jul 7, 2016 at 12:15 AM, Matt Riedemann <mrie...@linux.vnet.ibm.com> wrote: > On 7/4/2016 1:12 AM, Zhenyu Zheng wrote: > >> I'm willing to work on this, should this be a Blueprint for O? >> >> > The spec will need to

Re: [openstack-dev] [Nova] Questions about instance actions' update and finish

;>> On 6/29/2016 6:40 AM, Andrew Laski wrote: >> >>>> >> >>>> >> >>>> >> >>>> On Tue, Jun 28, 2016, at 09:27 PM, Zhenyu Zheng wrote: >> >>>>> How about I sync u

Re: [openstack-dev] [Nova] Questions about instance actions' update and finish

com> wrote: > > > > On Tue, Jun 28, 2016, at 03:26 AM, Zhenyu Zheng wrote: > > Hi all, > > I'm working on add pagination and timestamp filter for os-instance-actions > API: > https://review.openstack.org/#/c/326326/ > As Alex_xu pointed out that it will be better to

[openstack-dev] [Nova] Questions about instance actions' update and finish

Hi all, I'm working on add pagination and timestamp filter for os-instance-actions API: https://review.openstack.org/#/c/326326/ As Alex_xu pointed out that it will be better to filter by `updated_at` for timestamp filter which is reasonable, but when I tried to modify the patch I found out that:

Re: [openstack-dev] [nova] API changes on limit / marker / sort in Newton

I think it is good to share codes and a single microversion can make life more easier during coding. Can we approve those specs first and then decide on the details in IRC and patch review? Because the non-priority spec deadline is so close. Thanks On Tue, May 31, 2016 at 1:09 AM, Ken'ichi

Re: [openstack-dev] [nova] API changes on limit / marker / sort in Newton

Thanks for the information, really hope these two can get merged for Newton: https://review.openstack.org/#/c/240401/ https://review.openstack.org/#/c/239869/ On Sat, May 21, 2016 at 5:55 AM, Jay Pipes wrote: > +1 on all your suggestions below, Sean. > > -jay > > > On

[openstack-dev] [nova] Suggest to not deprecate os-migrations API

Hi All, According to https://github.com/openstack/nova/blob/master/releasenotes/notes/os-migrations-ef225e5b309d5497.yaml , we are going to deprecate the old os-migrations API, and two new APIs: /servers/{server uuid}/migrations and /servers/{server uuid}/migrations/{migration id} is added. As

Re: [openstack-dev] [nova] Versioned notification work continues in Newton

Great, glad to help. On Tue, Apr 12, 2016 at 9:03 PM, Balázs Gibizer wrote: > Hi, > > I just want to let the community know that the versioned notification > work we started in Mitaka is planned to be continued in Newton. > The planned goals for Newton: > *

[openstack-dev] [Nova] How about use IP instead of hostname when live Migrate.

Hi, Nova, Currently, we use destination host name as the target node uri by default (if the newly added config option live_migration_inbound_addr has not been set). This will need transformations from hostname to IP to perform the operation such as copy disks, and it will depend on DNS services,

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

gt;> On 03/05/2016 12:27 AM, Chris Friesen wrote: >> >>> On 03/04/2016 03:42 PM, Matt Riedemann wrote: >>> >>>> >>>> >>>> On 3/3/2016 9:14 PM, Zhenyu Zheng wrote: >>>> >>>>> Hm, I found out the reas

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

le or a microversion is needed? On Fri, Mar 4, 2016 at 10:27 AM, Zhenyu Zheng <zhengzhenyul...@gmail.com> wrote: > 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

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 <zhengzhenyul...@gmail.com> wrote: > Yes, so you are suggest fixing the return data of non-admin user use 'no

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

ote: > >> >> >> 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 do

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

53eb0d4d5cabdf635dd8181313/servers/40bab05f-0692-43df-a8a9-e7c0d58a73bd;, "rel": "bookmark"}], "key_name": null, "image": {"id": "6455625c-a68d-4bd3-ac2e-07382ac5cbf4", "links": [{"href": " http://10.229.45.17:8774/62bf

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

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" parameter. This is reasonable in some level, as delete is an update to instances. But as we have a limitation that

Re: [openstack-dev] [nova] Migration progress

I think we can add a config option for this and set a theoretical proper default value, we also add help messages to inform the the user about how inappropriate value of this config option will effect the performance. On Wed, Feb 3, 2016 at 7:45 PM, Daniel P. Berrange

Re: [openstack-dev] [telemetry][aodh] announcing Liusheng as new Aodh liaison

Congratulations Liusheng On Fri, Feb 5, 2016 at 12:07 AM, gordon chung wrote: > hi, > > we've been searching for a lead/liaison/lieutenant for Aodh for some > time. thankfully, we've had a volunteer. > > i'd like to announce Liusheng as the new lead of Aodh, the alarming > service

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

This is a bug, as tenant and user is maintained by keystone and quota are stored in nova db, so it has the cleanup problems. On Tue, Jan 19, 2016 at 8:12 PM, jialiang_song517 wrote: > Hi guys, > > I am working on bug #1449498, display the quota of a user has been

Re: [openstack-dev] [Nova][Glance] Nova + Glance_v2 = Love

Agreed with Sam, the point 6 is actually very important now for production deployment, as volume-backed instance is very common. Maybe we should keep it until we find a better solution. On Tue, Dec 29, 2015 at 9:41 PM, Sam Matzek wrote: > On Thu, Dec 24, 2015 at 7:49 AM,

Re: [openstack-dev] [openstack][nova] Microversions support for extensions without Controller

Hi, I think for this kind of change you should register a Blueprint and submit a spec for discussion. Sounds like it will be a bit change. BR On Sun, Dec 13, 2015 at 2:18 AM, Alexandre Levine wrote: > Hi all, > > os-user-data extension implements server_create

Re: [openstack-dev] [openstack][nova] Microversions support for extensions without Controller

Sorry, s/bit/big On Mon, Dec 14, 2015 at 10:46 AM, Zhenyu Zheng <zhengzhenyul...@gmail.com> wrote: > Hi, I think for this kind of change you should register a Blueprint and > submit a spec for discussion. Sounds like it will be a bit change. > > BR > > On Sun, Dec 13, 20

Re: [openstack-dev] [nova][cinder] About rebuilding volume-backed instances.

live-backup volume, but not support live-restore a volume. Are we planning to support this kind of action? Yours, Zheng On Mon, Nov 9, 2015 at 8:24 PM, Duncan Thomas <duncan.tho...@gmail.com> wrote: > On 9 November 2015 at 09:04, Zhenyu Zheng <zhengzhenyul...@gmail.com> > wrote: &

Re: [openstack-dev] [nova][cinder] About rebuilding volume-backed instances.

Hi, Thanks for the reply, for some scenario, launching an new instance is easier. But for production deployment, an instance may contain a large number of data such as keypairs, metadata, bdm etc. and it may have multiple internet interfaces that are connected to multiple networks. That is to

[openstack-dev] [nova][cinder] About rebuilding volume-backed instances.

Hi All, Currently, we have strong demands about "rebuilding"(or actions like rebuilding) volume-backed instances. As in production deployment, volume backed instance is widely used. Users have the demands of performing the rebuild(recovery) action for root device while maintain instance UUID

Re: [openstack-dev] [nova][api] Pagination in thre API

So lets work on the API WG guideline first, looking forward to get it done sooner, pagination is actually very useful in production deployment. On Thu, Nov 5, 2015 at 11:16 PM, Everett Toews wrote: > On Nov 5, 2015, at 5:44 AM, John Garbutt

[openstack-dev] [nova] Add expected_task for instance.save() used by block_device mapping in compute.manager._build_resources

Hi all, We have recently meet this problem: for large scale deployment, command can be sent concurrently, and for several times, when an instance was asked to be delete during it is launching, we observed that the vm_state and task_state of that instance has changed abnormally like this: When we

Re: [openstack-dev] [Nova] Migration state machine proposal.

I think it will be better if you can submit a spec for your proposal, it will be easier for people to give comment. On Wed, Oct 14, 2015 at 10:05 AM, Tang Chen wrote: > Hi, all, > > Please help to review this BP. > >

[openstack-dev] [nova][python-novaclient] Functional test fail due to publicURL endpoint for volume service not found

Hi, all I submitted a patch for novaclient last night: https://review.openstack.org/#/c/228769/ , and it turns out the functional test has failed due to: publicURL endpoint for volume service not found. I also found out that another novaclient patch: https://review.openstack.org/#/c/217131/ also

Re: [openstack-dev] [nova] [api] Nova currently handles list with limit=0 quite different for different objects.

nks > Alex > > On Sep 23, 2015, at 9:18 AM, Zhenyu Zheng <zhengzhenyul...@gmail.com> > wrote: > > Any thoughts on this? > > On Mon, Sep 14, 2015 at 11:53 AM, Zhenyu Zheng <zhengzhenyul...@gmail.com> > wrote: > >> Hi, Thanks for your reply, after check

Re: [openstack-dev] [nova] About availability zones

expect. Any thought about this? BR, Zheng On Wed, Sep 23, 2015 at 4:30 PM, Sylvain Bauza <sba...@redhat.com> wrote: > > > Le 23/09/2015 05:24, Zhenyu Zheng a écrit : > > Hi, all > > I have a question about availability zones when performing live-migration. > >

Re: [openstack-dev] [nova] [api] Nova currently handles list with limit=0 quite different for different objects.

Any thoughts on this? On Mon, Sep 14, 2015 at 11:53 AM, Zhenyu Zheng <zhengzhenyul...@gmail.com> wrote: > Hi, Thanks for your reply, after check again and I agree with you. I think > we should come up with a conclusion about how we should treat this limit=0 > across nova. And th

[openstack-dev] [nova] About availability zones

Hi, all I have a question about availability zones when performing live-migration. Currently, when performing live-migration the AZ of the instance didn't update. In usecase like this: Instance_1 is in host1 which is in az1, we live-migrate it to host2 (provide host2 in API request) which is in

Re: [openstack-dev] [nova] [api] Nova currently handles list with limit=0 quite different for different objects.

this. BR, Zheng On Sat, Sep 12, 2015 at 12:07 AM, Kevin L. Mitchell < kevin.mitch...@rackspace.com> wrote: > On Fri, 2015-09-11 at 15:41 +0800, Zhenyu Zheng wrote: > > Hi, I found out that nova currently handles list with limit=0 quite > > different for different object

[openstack-dev] [nova] Nova currently handles list with limit=0 quite different for different objects.

Hi, I found out that nova currently handles list with limit=0 quite different for different objects. Especially when list servers: According to the code: http://git.openstack.org/cgit/openstack/nova/tree/nova/api/openstack/common.py#n206 when limit = 0, it should apply as max_limit, but

Re: [openstack-dev] [Blazar] Anyone interested?

Hello, It seems like an interesting project. On Fri, Aug 28, 2015 at 7:54 PM, Pierre Riteau wrote: > Hello, > > The NSF-funded Chameleon project (https://www.chameleoncloud.org) uses > Blazar to provide advance reservations of resources for running cloud > computing

Re: [openstack-dev] [Bug 1482444] Abnormal changes of quota usage after instance restored by admin

Hi, I didn't reproduce this bug, maybe you can explain more details. On Tue, Aug 11, 2015 at 8:37 AM, 郑岳 zheng...@hihuron.com wrote: Hello everyone: I found a bug in openstack about project's quota usage in newest version. The link of bug description:

[openstack-dev] [nova] Adding Project_id to the display list when using nova server-group-list

Hi All, Currently, when using command: nova server-group-list, server groups' project id will not be displayed. As the admin user can use option --all-projects to list server groups in all projects, it will be really difficult to identify which serer group belongs to which project. It will be

[openstack-dev] [nova][cinder] Should we allow this kind of action?

Hi all, Recently, I've been asked to perform this kind of action using OpenStack: 1. Launch an volume-backended instance. 2. Take a snapshot of this instance using nova image-create, an image will be added in glance, the size is zero, and the BDM will be saved in it's metadata. 3. Create an