Earlier  
Posted Nick Remark
#openstack-nova - 2018-08-09
02:56:50 openstackgerrit Takashi NATSUME proposed openstack/nova master: [placement] api-ref: add description for 1.29 https://review.openstack.org/589407
03:12:36 openstackgerrit Vishakha Agarwal proposed openstack/nova master: Quota details for key_pair "in_use" is 0. https://review.openstack.org/590081
03:17:19 openstackgerrit Chen proposed openstack/nova master: Trivial fix on migration doc https://review.openstack.org/589028
04:13:29 openstackgerrit Merged openstack/nova stable/queens: Fix bad links for admin-guide https://review.openstack.org/590068
05:32:31 openstackgerrit Vishakha Agarwal proposed openstack/nova master: Quota details for key_pair "in_use" is 0. https://review.openstack.org/590081
06:05:26 openstackgerrit Vishakha Agarwal proposed openstack/nova master: Quota details for key_pair "in_use" is 0. https://review.openstack.org/590081
06:55:14 openstackgerrit Sergii Golovatiuk proposed openstack/nova master: libvirt: Always escape IPv6 addresses when used in migration URI https://review.openstack.org/589548
07:15:50 openstackgerrit liuyamin proposed openstack/python-novaclient master: Replace os-client-config to openstacksdk https://review.openstack.org/590141
07:23:14 openstackgerrit Tetsuro Nakamura proposed openstack/nova master: Adds a test for _get_provider_ids_matching() https://review.openstack.org/590150
08:04:48 gibi melwitt, mriedem: opened a versioned notification bp for stein https://blueprints.launchpad.net/nova/+spec/versioned-notification-transformation-stein
08:19:07 mdbooth lyarwood: Passing: https://review.openstack.org/#/c/587013/ !
08:21:47 mdbooth lyarwood: Also passed without the rebase workaround. I'll merge them and resubmit.
08:27:24 openstackgerrit Matthew Booth proposed openstack/nova master: fixtures: Track volume attachments within CinderFixtureNewAttachFlow https://review.openstack.org/587013
08:36:02 openstackgerrit Jose Castro Leon proposed openstack/nova master: Fix get_device_path from network mounted volume https://review.openstack.org/590188
08:49:46 openstackgerrit Matthew Booth proposed openstack/nova master: Add regression test for bug#1784353 https://review.openstack.org/587014
09:13:44 lyarwood mdbooth: cool, thanks again for working through this :)
09:14:27 mdbooth lyarwood: np.
09:14:46 mdbooth lyarwood: Started accidentally while reviewing and seemed silly to stop :)
09:21:19 lyarwood mdbooth: are you going to rebase https://review.openstack.org/#/c/587071/ ?
09:21:30 lyarwood mdbooth: np if not, I have time to work on it this morning finally
09:21:46 mdbooth lyarwood: I was going to leave that for you, that's the real bit :)
09:21:56 lyarwood mdbooth: tis cool, thanks again
09:22:12 mdbooth lyarwood: Incidentally, did you consider the 'fix it in compute' approach
09:22:26 mdbooth I know that's where the patch started, then you moved to conductor
09:22:55 mdbooth But in fixing the fixture I can across other cleanup in compute which already does exactly what I was talking about
09:23:10 lyarwood mdbooth: yeah the remove_volume_connections call
09:23:33 mdbooth Yeah
09:24:12 lyarwood mdbooth: yeah I'll take a look now, it's a shame to flip back again but meh
09:25:02 mdbooth lyarwood: I'm not saying do it, just asking if it's feasible/worth considering
09:25:12 mdbooth Or if you've already considered and rejected it, in fact
09:28:22 lyarwood mdbooth: yeah understood, I think it is feasible and ultimatley a better approach I just haven't looked into the knock on impact of changing shutdown_instance.
09:28:44 mdbooth lyarwood: ack
09:39:39 goutham1 HI all i a facing this issue in rally when i try to create a deployment it throws this error Env manager got invalid spec:
09:39:40 goutham1 any idea on how to fix it ??
09:39:40 goutham1 2:57
09:39:40 goutham1 ["There is no Platform plugin with name: 'existing@openstack'"]
09:39:55 goutham1 rally deployment create --fromenv --name=existing
09:39:56 goutham1 ["There is no Platform plugin with name: 'existing@openstack'"]
09:39:56 goutham1 Env manager got invalid spec:
09:40:14 goutham1 it shows something of this sort any idea on how to fix this ??
09:41:21 mdbooth goutham1: You'll want to try #openstack for user issues, I think
09:41:38 goutham1 thank mdbooth thanks
09:52:05 tobasco gibi: maybe a stupid question but is the os-server-external-events interface related to legacy or versioned notifications in nova?
09:52:28 gibi tobasco: no it doesn't
09:52:48 gibi tobasco: os-server-external-events is in the REST API
09:53:18 tobasco ok thanks
09:53:21 gibi tobasco: when I say nova notifications I mean notification emitted on the notifications or versioned_notification RPC topic
09:55:54 neiljerram Good morning everyone.
09:58:05 neiljerram I am struggling with a problem in Queens where I can do novaclient.images.list() if novaclient is for the admin tenant, but I get 401 if novaclient is for some other tenant/project.
09:59:41 neiljerram This was working in a Pike installation, and using Keystone v2 for authentication. In my Queens install I don't have Keystone v2 so am now using Keystone v3 for auth.
09:59:53 neiljerram Any thoughts?
10:00:37 neiljerram I believe any tenant/project should be able to list images, right?
10:04:21 neiljerram When I do novaclient.images.list() with a non-admin tenant, and get 401, there is no new logging in nova-api.log. (Whereas when I do a successful list with the admin tenant, I see a 200 log line in nova-api.log.)
10:05:11 neiljerram Therefore I guess that this 401 is coming from some middleware before nova-api? But I don't know how to debug or see any logging for that middleware...
10:09:02 neiljerram Ah, just realized that I should be asking all this in #openstack instead...
10:11:24 openstackgerrit Balazs Gibizer proposed openstack/nova master: Use placement 1.28 in scheduler report client https://review.openstack.org/583667
10:18:55 openstackgerrit Sergii Golovatiuk proposed openstack/nova master: libvirt: Always escape IPv6 addresses when used in migration URI https://review.openstack.org/589548
10:21:11 mdbooth neiljerram: :) You're also best talking to glance directly for listing images. Pretty sure nova would just proxy it. Actually, I wonder if novaclient just talks to glance instead? When can we kill that, btw?
10:22:50 neiljerram mdbooth, I think you're right that nova proxies this to glance. When I try this with an admin tenant, I see a 200 log line in nova-api.log - which I think means that it can't be going directly to glance; right?
10:23:28 mdbooth neiljerram: Yeah, it means we saw it.
10:24:15 neiljerram mdbooth, I think my problem may be more to do with not understanding how users and tokens work in Keystone v3...
10:26:32 neiljerram mdbooth, If it's OK to ask this here: if I have just created some new project and user (in that project), do I also need to explicitly set up some token(s) for that user? Or will that happen under the covers when I first try to do something with that user?
10:40:45 openstackgerrit Balazs Gibizer proposed openstack/nova master: Use placement 1.28 in scheduler report client https://review.openstack.org/583667
10:55:05 lyarwood mdbooth: https://review.openstack.org/#/c/589567/3 - would you mind taking a look at my latest comment here, basically we wanted to introduce a workaround to avoid using qemu-img to aviod the RT from blocking other operations, however this path is also used during LM to get the sizes of disks before we recreate on the dest if required. I'm tempted to just close this change and move on but I might be
10:55:08 lyarwood missing something here.
10:55:29 mdbooth lyarwood: ack. Looking now.
10:56:09 lyarwood mdbooth: note the logic in the current change is all backwards, I was rewriting it to always default to using os.path.getsize and only use qemu-img when the workaround was enabled.
10:56:45 lyarwood mdbooth: but that reintroduces 1770640
10:58:02 mdbooth lyarwood: We should really just write that data into disk.info and read it from there.
11:00:13 lyarwood mdbooth: yeah looks like get_instance_disk_info always checks the config
11:01:36 lyarwood the actual instance config that is, not disk.info
11:02:28 lyarwood mdbooth: brb need to drop for 10 mins
11:02:33 mdbooth lyarwood: k
11:07:20 openstackgerrit Chen proposed openstack/nova master: Add additional info to resource provider aggregates update API https://review.openstack.org/590243
11:15:30 mdbooth lyarwood: If you're back, why the hell didn't we just stat it?
11:15:51 mdbooth lyarwood: Probably because qemu-img is there and we weren't considering the performance impact.
11:16:23 mdbooth lyarwood: But for allocated size, stat should give us exactly what we want, be really fast, and we don't need a workaround.
11:27:29 openstackgerrit Merged openstack/nova master: Docs: Add guide to migrate instance with snapshot https://review.openstack.org/584442
11:33:31 openstackgerrit Matthew Booth proposed openstack/nova master: Improve performance of get_allocated_disk_size https://review.openstack.org/590253
11:33:50 mdbooth lyarwood: How about ^^^ instead? Just throwing that out as a proposal.
11:36:48 openstackgerrit Merged openstack/nova master: Fix host validity check for live-migration https://review.openstack.org/401009
11:55:56 openstackgerrit Rajesh Tailor proposed openstack/nova stable/queens: Fix host validity check for live-migration https://review.openstack.org/590262
11:58:03 openstackgerrit Rajesh Tailor proposed openstack/nova stable/pike: Fix host validity check for live-migration https://review.openstack.org/590263
11:59:58 lyarwood mdbooth: sorry that took a while
12:00:18 lyarwood mdbooth: yeah but we also need the virtual size
12:00:29 mdbooth lyarwood: Where?
12:00:31 lyarwood mdbooth: and that's the more important value tbh
12:01:14 lyarwood mdbooth: so we need it to work out over_committed_disk_size but also during LM to ensure we create the dest disks correctly
12:02:13 lyarwood mdbooth: your change is still good
12:02:28 lyarwood mdbooth: but I don't think it stops us from calling qemu-img to get the virtual size
12:02:48 mdbooth lyarwood: Yes, you're right
12:03:28 mdbooth Something somewhere said it the regression was introduced in a particular change, and that change only added get_allocated_disk_size
12:03:48 lyarwood mdbooth: yeah the bug for this highlights that change first I think
12:04:23 lyarwood mdbooth: that introduced the first call to qemu-img, then we noticed that broke LM so I introduced the virtual size call
12:04:23 mdbooth Ok. We could also eliminate get_disk_size, but that would be more complex
12:04:48 mdbooth We'd have to cache it
12:05:07 lyarwood mdbooth: yeah I think we can do that for virtual size
12:05:10 mdbooth I think. Not hard, but harder.
12:05:19 mdbooth Possibly not worth it harder
12:05:52 mdbooth Incidentally, that is the only use of get_allocated_disk_size

Earlier   Later