| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2018-05-16 | |||
| 16:28:46 | mriedem | i'm free tomorrow, depends on stephen's hard drop everything and leave the office time :) | |
| 16:28:47 | stephenfin | Heh, and I can't do after-after (tag rugby game to play) | |
| 16:28:53 | mriedem | see! | |
| 16:29:11 | dansmith | we'll all also be in YVR | |
| 16:29:20 | stephenfin | aaaand I'm gone to Vancouver Friday AM | |
| 16:29:26 | mriedem | stephenfin, see, you need to start a family, give up on friends, and confine yourself to your desk | |
| 16:29:39 | stephenfin | dansmith: That would work. Don't imagine it'll take long | |
| 16:29:40 | mriedem | start working on your sweet sweet paunch | |
| 16:29:49 | mriedem | yeah we can punt to YVR... | |
| 16:30:38 | stephenfin | Aye, but if efried_rollin can fit in 8 sessions a week, I should probably try fit in a tag game | |
| 16:30:46 | stephenfin | mriedem: Sweet | |
| 16:34:27 | mriedem | efried_rollin: esberglu: +2 on https://review.openstack.org/#/c/549053/ | |
| 16:36:41 | esberglu | mriedem: ack, tx for review | |
| 16:36:57 | cfriesen | stephenfin: tag rugby? that's not as much fun. :) | |
| 16:39:39 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Add granular policy rules for usages https://review.openstack.org/568706 | |
| 17:00:16 | lbragstad | mriedem: let me know if this helps https://review.openstack.org/#/c/568901/ | |
| 17:02:08 | lbragstad | it's rough - but it might also be beneficial to add in a section on how the service is responsible for checking the scope of the resource in the request against the token being used, and how that differs from the scope_types check | |
| 17:09:07 | mriedem | lbragstad: thanks, in a tab, will look in a bit | |
| 17:10:36 | lbragstad[m] | mriedem: cool, thanks for bringing it up | |
| 17:48:30 | melwitt | dansmith: would you please update the topic with the new runways https://etherpad.openstack.org/p/nova-runways-rocky | |
| 17:48:38 | mriedem | jaypipes: dansmith: i went over the mirror aggregates to placement change https://review.openstack.org/#/c/553597/ - think we just need to determine what to do about safe_connect usage in there and how idempotent we should be | |
| 17:48:38 | melwitt | *channel topic | |
| 17:48:40 | dansmith | yeah sorry | |
| 17:48:57 | melwitt | thanks mriedem for swarpping the runways | |
| 17:49:03 | melwitt | swapping | |
| 17:49:10 | mriedem | np | |
| 17:49:38 | dansmith | um which is the powervm one? | |
| 17:49:43 | dansmith | looks like multiple specs | |
| 17:49:49 | dansmith | but just powervm-localdisk now? | |
| 17:50:13 | melwitt | it's multiple blueprints. they used to be in one and were asked to split them into specless bps, IIRC | |
| 17:50:30 | melwitt | one for each parity thing. so it's a little weird | |
| 17:50:43 | jaypipes | thx mriedem | |
| 17:51:49 | mriedem | i'll also push a docs change for the rocky requirement in nova-api to have placement configured for things like local delete and deleting compute services | |
| 17:52:06 | mriedem | those are idempotent today but you'll get warnings in the logs if placement isn't configured for nova-api | |
| 17:53:37 | melwitt | oh and powervm-vscsi is blocked on CI coverage so powervm-localdisk is the only one left | |
| 17:53:39 | melwitt | derp | |
| 17:58:24 | mriedem | esberglu: powervm ci seems to be unwell http://184.172.12.213/00/549300/27/check/nova-in-tree-pvm/03c26c0/logs/console.txt.gz | |
| 17:58:41 | mriedem | m echo 'Didn'\''t find service registered by hostname after 60 seconds' | |
| 17:59:03 | mriedem | i believe that timeout is configurable now if you need to bump it | |
| 17:59:45 | mriedem | http://git.openstack.org/cgit/openstack-dev/devstack/tree/lib/nova#n1066 | |
| 18:02:47 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Use RequestSpec.user_id in scheduler.utils.claim_resources https://review.openstack.org/568917 | |
| 18:06:29 | esberglu | mriedem: Not a timeout, legit failure for the service to come up http://184.172.12.213/53/549053/18/check/nova-in-tree-pvm/9c1c445/logs/n-cpu.txt.gz | |
| 18:07:00 | mriedem | oh nice | |
| 18:07:26 | esberglu | mriedem: I thought https://review.openstack.org/#/c/549053/18/nova/virt/powervm/disk/driver.py@64 should make @abstractproperty accessible? | |
| 18:07:34 | esberglu | What am I missing | |
| 18:07:48 | mriedem | @abc.abstractproperty | |
| 18:07:55 | mriedem | https://docs.python.org/2/library/abc.html#abc.abstractproperty | |
| 18:07:56 | mriedem | i think anyway | |
| 18:08:51 | esberglu | mriedem: I guess I misunderstood add_metaclass. New patch incoming | |
| 18:09:08 | mriedem | yeah unit tests and pep8 failed in https://review.openstack.org/#/c/549053/ | |
| 18:14:05 | openstackgerrit | Eric Berglund proposed openstack/nova master: PowerVM Driver: DiskAdapter parent class https://review.openstack.org/549053 | |
| 18:14:06 | openstackgerrit | Eric Berglund proposed openstack/nova master: PowerVM Driver: Localdisk https://review.openstack.org/549300 | |
| 18:23:37 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Update nova-status and docs for required placement 1.24 https://review.openstack.org/568923 | |
| 18:25:04 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Update nova-status and docs for required placement 1.24 https://review.openstack.org/568923 | |
| 18:31:06 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Update placement upgrade docs for nova-api dependency on placement https://review.openstack.org/568925 | |
| 18:33:05 | mriedem | esberglu: hmm http://logs.openstack.org/53/549053/19/check/openstack-tox-py27/c882f7f/testr_results.html.gz | |
| 18:33:47 | esberglu | mriedem: Guess it's time to figure out why I can't run tox locally | |
| 18:34:41 | mriedem | self.st_adpt = disk_dvr.DiskAdapter(None, None) | |
| 18:34:46 | mriedem | your test is trying to instantiate the abc | |
| 18:36:28 | mriedem | so either just leave that in the test for SSPDiskAdapter, | |
| 18:36:45 | mriedem | or make a little fake DiskAdapter subclass for your generic base class tests? | |
| 18:54:54 | openstackgerrit | Merged openstack/nova master: Debug logs for allocation_candidates filters https://review.openstack.org/568712 | |
| 19:00:24 | dansmith | mriedem: melwitt: cells meeting? I've got nothing and tssurya isn't around | |
| 19:00:35 | melwitt | I don't have anything either | |
| 19:01:22 | mriedem | nope | |
| 19:01:25 | dansmith | woot | |
| 19:14:43 | openstackgerrit | Matt Riedemann proposed openstack/nova-specs master: Add additional information for z/VM spec. https://review.openstack.org/562154 | |
| 19:15:28 | mriedem1 | dansmith: +2 on ^ - barring some english / grammar stuff in there, it sounds like that reflects the ML thread which i think you know more about than i do | |
| 19:39:34 | openstackgerrit | Eric Berglund proposed openstack/nova master: PowerVM Driver: DiskAdapter parent class https://review.openstack.org/549053 | |
| 19:39:35 | openstackgerrit | Eric Berglund proposed openstack/nova master: PowerVM Driver: Localdisk https://review.openstack.org/549300 | |
| 19:44:29 | mriedem | can we remove the 'build_instance' hook yet? https://github.com/openstack/nova/blob/7bdb7dbbddf9fcb4284d490bf315d6756f4015e7/nova/compute/manager.py#L2209 | |
| 19:44:41 | mriedem | hooks have been officially deprecated for a couple of years now | |
| 19:45:31 | mriedem | LOG.warning(_LW("Hooks are deprecated as of Nova 13.0 and " | |
| 19:45:31 | mriedem | "will be removed in a future release")) | |
| 19:46:23 | mriedem | the issue being, because _do_build_and_run_instance has the hook, we return the build_results enum, which means when we are checking to see if the compute should be auto-disabled due to consecutive failures, we don't have any context on why the build failed https://github.com/openstack/nova/blob/7bdb7dbbddf9fcb4284d490bf315d6756f4015e7/nova/compute/manager.py#L1679 | |
| 19:46:26 | mriedem | dansmith: ^ | |
| 19:47:12 | mriedem | if we get a BuildAbortException from the bowels https://github.com/openstack/nova/blob/7bdb7dbbddf9fcb4284d490bf315d6756f4015e7/nova/compute/manager.py#L1903 we just return the 'failed' enum and consider everything fatal / misconfig even if it's not | |
| 19:48:01 | mriedem | 13.0 is mitaka | |
| 19:48:16 | dansmith | I'm missing what the linkage with the hook is | |
| 19:48:21 | dansmith | (but of course I'm fine with removing) | |
| 19:49:59 | dansmith | mriedem: ^ | |
| 19:51:08 | mriedem | https://bugs.launchpad.net/nova/+bug/1742102 | |
| 19:51:09 | openstack | Launchpad bug 1742102 in OpenStack Compute (nova) "Simple user can disable compute" [High,Confirmed] - Assigned to jichenjc (jichenjc) | |
| 19:51:15 | mriedem | see the 2nd to last comment there | |
| 19:52:39 | mriedem | trying to determine context on what happens when we call _build_failed() | |
| 19:52:43 | dansmith | mriedem: sorry I | |
| 19:52:50 | dansmith | am totally missing what hooks has to do with anything | |
| 19:52:55 | mriedem | if it's volume overquota, we don't need to count that against consecutive build failures | |
| 19:53:16 | dansmith | I get that | |
| 19:53:20 | mriedem | this is where we call _build_failed() to see if we disable the service https://github.com/openstack/nova/blob/7bdb7dbbddf9fcb4284d490bf315d6756f4015e7/nova/compute/manager.py#L2209 | |
| 19:53:32 | mriedem | at that point, we have 0 context on the actual exception that occurred | |
| 19:53:51 | mriedem | so if i wanted to inspect the BuildAbortException let's say to see if it was a volume overquota issue, i can't do that | |
| 19:54:12 | dansmith | what does that have to do with hooks? | |
| 19:54:17 | mriedem | i can't do that because, except for one base64 decode error exception, _do_build_and_run_instance doesn't raise exceptions | |
| 19:54:31 | mriedem | _do_build_and_run_instance only returns build_results.* enums which are there for hooks | |
| 19:54:36 | mriedem | https://github.com/openstack/nova/blob/7bdb7dbbddf9fcb4284d490bf315d6756f4015e7/nova/compute/manager.py#L2209 | |
| 19:55:10 | mriedem | at least that's my understanding, | |
| 19:55:22 | mriedem | so what i want is for _do_build_and_run_instance to raise it's actual failure, | |
| 19:55:32 | mriedem | so we can inspect it up the stack in _build_failed() | |
| 19:55:40 | dansmith | you know you're not actually linking me to _do_build_and_run_instance right? | |