| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2017-08-07 | |||
| 09:55:12 | bauzas | voilà. | |
| 09:56:28 | bauzas | FWIW, I'm in a perfect place for chasing bugs | |
| 09:56:38 | bauzas | litterally 200m away from the meditarean sea | |
| 10:09:43 | ratailor | Can anybody help me in debugging this code block. | |
| 10:09:44 | ratailor | https://github.com/openstack/nova/blob/master/nova/objects/host_mapping.py#L90-L93 | |
| 10:10:19 | ratailor | How can I check value of api_models.HostMapping.host in above code block. | |
| 10:10:22 | stephenfin | sdague, bauzas, cdent: Is live migration an operator or user-level operation, i.e. 'doc/source/admin' or 'doc/source/user'? | |
| 10:12:15 | stephenfin | I ask because I think I might need to move this document https://review.openstack.org/#/c/490952/1/doc/source/admin/migration.rst | |
| 10:12:29 | stephenfin | and this, for evacuate https://review.openstack.org/#/c/490952/1/doc/source/admin/evacuate.rst | |
| 10:13:15 | bauzas | stephenfin: live migrations are only possible for users that are having admin keystone rights | |
| 10:13:29 | stephenfin | bauzas: and evacuations? | |
| 10:14:12 | bauzas | stephenfin: AFAIR, evacuations are only for admin-only too since it requires a knowledge of your host health | |
| 10:14:19 | bauzas | stephenfin: but I can check the policy | |
| 10:14:44 | bauzas | stephenfin: the thing is, we show those operations by the CLI | |
| 10:14:45 | stephenfin | bauzas: So they both warrant staying in the admin guide. I'll keep them there so. Thanks! :) | |
| 10:14:53 | stephenfin | what do you mean? | |
| 10:14:59 | stephenfin | "by the CLI"? | |
| 10:15:07 | bauzas | stephenfin: I mean a single user can see those operations | |
| 10:15:14 | openstackgerrit | Sylvain Bauza proposed openstack/nova master: Add a prelude section for Pike https://review.openstack.org/491424 | |
| 10:15:34 | stephenfin | bauzas: You mean regardless of whether they're an admin or not? | |
| 10:15:40 | bauzas | stephenfin: yup | |
| 10:15:52 | bauzas | it will just give'em a 401 if they try | |
| 10:16:43 | bauzas | the fact is, I don't remember which specific move operation is either admin-only or regular user, depending if people provided a target or not | |
| 10:17:08 | bauzas | but anyway, those two tools (live-mig and evac) are aimed for admins anyway | |
| 10:18:21 | stephenfin | bauzas: Right, they can stay where they are now so | |
| 10:19:08 | bauzas | it'll take a while tho, under 1Mbps b/w | |
| 10:24:37 | bauzas | stephenfin: okay, confirmed, live-migrations and evacuations are admin-only, and cold migrations depend on whether you specify a target or not | |
| 10:30:07 | stephenfin | bauzas: Awesome. It stays in the admin guide so | |
| 10:35:48 | sdague | stephenfin: right, with default policy they are both admin only | |
| 10:36:09 | sdague | bauzas: I'm confused about your single user statement | |
| 10:42:58 | vks1 | sdague: hi | |
| 10:44:56 | sdague | vks1: morning | |
| 10:45:14 | vks1 | sdague: good morning | |
| 10:46:49 | vks1 | sdague: for REST API we use iso format for timestamp, which oslo API is used to generate that ? | |
| 10:50:17 | bauzas | sdague: sorry, was disconnected, which statement in particular? | |
| 10:56:43 | openstackgerrit | Stephen Finucane proposed openstack/nova master: doc: Add additional content to admin guide https://review.openstack.org/490952 | |
| 10:59:29 | sdague | vks1: I'm not sure it's coming from oslo | |
| 11:00:54 | sdague | vks1: I think they are going through this - https://github.com/openstack/nova/blob/6e77e75993c5b431c68c963bb06494ae5d36b944/nova/utils.py#L1344-L1355 | |
| 11:12:08 | openstackgerrit | Sylvain Bauza proposed openstack/nova master: Fix migrate single instance when it was created concurrently https://review.openstack.org/491439 | |
| 11:14:00 | bauzas | cdent: gibi: ^ | |
| 11:14:15 | gibi | bauzas: looking | |
| 11:22:23 | openstackgerrit | Stephen Finucane proposed openstack/nova master: trivial: Remove 'contrib' directory https://review.openstack.org/491443 | |
| 11:22:24 | openstackgerrit | Stephen Finucane proposed openstack/nova master: trivial: Remove files from 'tools' https://review.openstack.org/491444 | |
| 11:27:59 | gibi | bauzas: I left some comments in https://review.openstack.org/#/c/491439 | |
| 11:33:58 | stephenfin | asettle_: If you have time this week, I'd like your thoughts on what we can do with the admin guide going forward https://review.openstack.org/#/c/490952/ | |
| 11:34:46 | openstackgerrit | Balazs Gibizer proposed openstack/nova master: Test resize with too big flavor https://review.openstack.org/490814 | |
| 11:34:52 | asettle_ | stephenfin: I can do thoughts | |
| 11:34:55 | stephenfin | It's pretty...icky right now and I haven't even started dragging in the stuff from the old configuration guide | |
| 11:35:04 | stephenfin | asettle_: thoughts are good | |
| 11:36:21 | asettle_ | Okay, lemme go have a look at the beautiful build | |
| 11:36:41 | asettle_ | Well, that's just stunning isn't it | |
| 11:36:48 | asettle_ | I like the uhh... raw... blob ... of it all | |
| 11:36:58 | stephenfin | What can I say | |
| 11:36:59 | stephenfin | I've a knack | |
| 11:37:52 | asettle_ | You truly do | |
| 11:37:59 | asettle_ | Hmm, okay. I'll have a lookie and comment | |
| 11:40:03 | openstackgerrit | Balazs Gibizer proposed openstack/nova master: Test resize with too big flavor https://review.openstack.org/490814 | |
| 11:40:03 | asettle_ | It'd be cool to have this as Administration Guides or something similar :) (cause it's for the tasks, mostly) | |
| 11:40:58 | stephenfin | asettle_: Can't argue with that | |
| 11:42:04 | stephenfin | The tasks seem to be broken up into two types two: cloud-level tasks and instance-level ones | |
| 11:42:11 | stephenfin | *two types too | |
| 11:42:50 | stephenfin | I'd guess most of the configuration guides docs, once added, would fall into the former | |
| 11:44:21 | asettle_ | I would imagine so, ya | |
| 11:44:31 | asettle_ | Give me the afternoon to poke around :) I just gotta scoot out for lunch before afternoon meetings | |
| 12:05:03 | sdague | stephenfin / asettle_ another one of those subpages is here - https://review.openstack.org/#/c/490994/ | |
| 12:05:23 | sdague | I think I pushed that after you all had kicked off for the weekend | |
| 12:24:14 | stephenfin | sdague: done | |
| 12:24:56 | openstackgerrit | Stephen Finucane proposed openstack/python-novaclient master: tools: Remove dead script https://review.openstack.org/480138 | |
| 12:26:53 | openstackgerrit | Stephen Finucane proposed openstack/nova master: tools/xenserver: Remove 'cleanup_sm_locks' https://review.openstack.org/416520 | |
| 12:27:43 | stephenfin | Couple of trivial "remove dead files" patches here, were anyone looking for easy +2s https://review.openstack.org/#/q/topic:trivial+owner:%22Stephen+Finucane+%253Cstephenfin%2540redhat.com%253E%22+status:open | |
| 12:34:40 | cdent | jaypipes: your hip/back/whatever any better? | |
| 12:41:21 | maciejjozefczyk | Hello, im trying to create own periodic task outside upstream nova code (like nova.compute.manager tasks). Shouldn't it be registered the way like custom nova scheduler filters are ( option scheduler_available_filters in nova.conf)? Is it even possible to use both custom and generic periodic tasks in compute manager? | |
| 12:48:04 | cdent | stephenfin: do you consider https://review.openstack.org/#/c/490952/ done now? It’s sort of hard to tell/know and review other than “sure, lgtm” | |
| 12:50:22 | bauzas | gibi: looking | |
| 12:54:32 | bauzas | cdent: cdent: just to make sure, the -1s are about comments, right? | |
| 12:55:09 | cdent | bauzas: yes, as I tried to say on the comment: the code fix looks right, but the comments are misleading enough that they ought to be fixed | |
| 12:55:17 | bauzas | cdent: okay | |
| 12:55:48 | bauzas | cdent: tbc, we still need to use the ReqSpec record in case we don't have the instance list | |
| 12:56:02 | cdent | yes, that’s what my rewrite says | |
| 13:05:05 | openstackgerrit | Sylvain Bauza proposed openstack/nova master: Fix migrate single instance when it was created concurrently https://review.openstack.org/491439 | |
| 13:08:29 | jaypipes | cdent: yes, it is, thanks for asking. :) | |
| 13:09:05 | jaypipes | cdent: well, you might still have to shoot me, just not for that. | |
| 13:09:21 | cdent | have you seen our new exciting bug(s) for today? | |
| 13:09:39 | cdent | bauzas already fixed it, but it gives me dread | |
| 13:09:44 | jaypipes | cdent: the resize big flavor one from gibi? | |
| 13:10:01 | cdent | jaypipes: no, https://bugs.launchpad.net/nova/+bug/1708961 | |
| 13:10:02 | openstack | Launchpad bug 1708961 in OpenStack Compute (nova) "migration of single instance from multi-instance request spec fails with IndexError" [Critical,In progress] - Assigned to Sylvain Bauza (sylvain-bauza) | |
| 13:10:18 | cdent | I started doing some by hand testing over the weekend, bumped into that | |
| 13:10:45 | jaypipes | cdent: eww. :( | |
| 13:11:00 | openstack | Launchpad bug 1708958 in OpenStack Compute (nova) "disabling a compute service does not disable the resource provider" [Low,Confirmed] | |
| 13:11:00 | cdent | jaypipes: also bumped up against this question (not quite a bug, but an issue) https://bugs.launchpad.net/nova/+bug/1708958 | |
| 13:11:50 | jaypipes | cdent: that's definitely not a bug. and frankly, we cover that in the scheduler's integration with the "service group API". | |
| 13:11:58 | bauzas | jaypipes: remember the discussion we had in the review about being conservative with num_instances ? then, kaboom. :) | |
| 13:12:07 | cdent | jaypipes: it’s not a bug for nova | |
| 13:12:28 | jaypipes | cdent: hold up, I have a senior pug wandering around looking suspiciously prone to going the bathrooom.. | |
| 13:12:32 | bauzas | jaypipes: about the compute disabling, like I said in the comment, we have ComputeFilter for this | |
| 13:12:43 | jaypipes | fuck. too late. | |
| 13:12:46 | cdent | jaypipes: but it implies a reality mismatch between available resources | |
| 13:12:48 | cdent | :( | |
| 13:13:13 | bauzas | jaypipes: but we could possibly reduce the number of passed RPs to the scheduler if we have a way to know if the RP is stale | |