| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2017-02-16 | |||
| 23:39:32 | mriedem | cdent: i've been seeing it off and on | |
| 23:39:39 | mriedem | i just haven't taken the 2 hours to investigate :) | |
| 23:39:49 | cdent | ow | |
| 23:40:38 | cdent | do you ever sleep or eat or recreate in some fashion (please don't tell me this is your recreation)? | |
| 23:41:14 | mriedem | when my wife forces me, yes | |
| 23:41:31 | mriedem | i only care about this since it kicked the last change for ocata ga out of the gagte | |
| 23:41:32 | mriedem | *Gate | |
| 23:42:56 | mriedem | she gets up at 4am and goes to bed at 7pm though so i will start getting texts here pretty quick to get my ass home and take over parenting duties | |
| 23:47:35 | cdent | g'night | |
| 23:47:59 | openstackgerrit | Sujitha proposed openstack/nova master: Adding auto_disk_config field to InstancePayload https://review.openstack.org/419185 | |
| 23:51:28 | mriedem | https://review.openstack.org/#/c/435154/1 | |
| 23:51:30 | mriedem | YES! | |
| 23:51:33 | mriedem | sdague: ^^^^ | |
| 23:51:39 | mriedem | jogo: even you ^ | |
| 23:51:42 | mriedem | mtreinish: ^ | |
| 23:52:56 | mtreinish | mriedem: hah, nice | |
| 23:54:09 | mriedem | ok i'm tapping out, back online later | |
| 23:55:25 | jogo | mriedem: done | |
| 23:55:46 | mriedem | ha | |
| 23:55:47 | mriedem | o/ | |
| #openstack-nova - 2017-02-17 | |||
| 00:26:16 | cburgess | mrodden So... food update... | |
| 00:26:20 | cburgess | Opps | |
| 00:26:29 | cburgess | Wrong person. | |
| 00:26:47 | cburgess | mriedem You still around? | |
| 00:27:10 | melwitt | cburgess: he's heading home right now, said he'll be back online later | |
| 00:27:23 | cburgess | melwitt Thanks... have a food update for him and wanted his opinion | |
| 00:27:34 | melwitt | :) | |
| 00:28:14 | edleafe | cburgess: if possible, please keep in mind those of us who are not meat eaters | |
| 00:28:29 | cburgess | Well thats a problem since he asked me about BBQ... ummm ok. | |
| 00:28:39 | cburgess | I'll... see what we can do. | |
| 00:28:47 | cburgess | bbq and not meat don't usually go well together... | |
| 00:38:41 | edleafe | cburgess: understood. I live in Texas, after all :) | |
| 00:39:06 | edleafe | cburgess: As long as there will be beer, I'll survive | |
| 00:40:13 | cburgess | edleafe No worries | |
| 00:45:15 | openstackgerrit | melanie witt proposed openstack/nova master: Count resources to check quota for cells https://review.openstack.org/416521 | |
| 00:45:16 | openstackgerrit | melanie witt proposed openstack/nova master: Add online migration to move quotas to API database https://review.openstack.org/410946 | |
| 00:45:16 | openstackgerrit | melanie witt proposed openstack/nova master: Make Quotas object favor the API database https://review.openstack.org/410945 | |
| 01:47:11 | xiaoyang | hi, everyone. Why instance live migration after success doesn't change the availability zone? | |
| 03:18:21 | Jeffrey4l | can i say, introducing nova_api database is only(or mainly?) used for nova cell v2? | |
| 03:18:28 | Jeffrey4l | alex_xu, ^^ ;) | |
| 03:24:44 | cku | We recently submitted a blueprint and spec for adding a Nova volume driver for Veritas HyperScale storage (https://review.openstack.org/#/c/430488/). | |
| 03:24:52 | cku | I'm uncertain about the process to take this forward. | |
| 03:25:02 | cku | 1. Should we submit a separate blueprint and spec to the Cinder project for the Nova volume driver's os-brick connector? | |
| 03:25:10 | cku | 2. Do we need to set up CI for the volume driver, the os-brick connector, or both? | |
| 03:25:19 | cku | 3. Which existing volume driver should I use as a model for the proper specs, architecture, and CI setup? | |
| 03:25:28 | cku | Thanks (eom) | |
| 03:26:01 | smcginnis | cku: I believe there is already a Cinder blueprint for HyperScale. | |
| 03:26:28 | smcginnis | cku: If you need an os-brick connector, you can associate that change in os-brick to the same blueprint. | |
| 03:26:48 | smcginnis | cku: The Cinder repo needs CI reporting. | |
| 03:27:06 | smcginnis | cku: We encourage also reporting on os-brick changes, but we haven't made that a requirement. (yet) | |
| 03:27:12 | cku | Yes, a Cinder volume driver, but that is different from the os-brick connector component of the Nova volume driver. | |
| 03:27:28 | smcginnis | os-brick is a shared library by Nova and Cinder. | |
| 03:28:28 | cku | Ah, so the blueprint and spec we submitted in the Nova project should suffice? | |
| 03:42:37 | smcginnis | cku: No, I mean the Cinder spec. os-brick is part of the Cinder umbrella. | |
| 03:42:53 | openstackgerrit | ChangBo Guo(gcb) proposed openstack/nova master: Use check_string_length from oslo_utils https://review.openstack.org/286390 | |
| 03:59:46 | mriedem | cku: i've already replied about this in the nova spec, and linked the nova blueprint to the cinder blueprint | |
| 03:59:54 | mriedem | but smcginnis has already answered most of this | |
| 04:00:12 | mriedem | Jeffrey4l: the nova_api database has gone back a few releases and mostly predates the majority of the cells v2 work | |
| 04:01:45 | mriedem | well i guess it was added for cells v2 primarily, i was thinking the request spec was in there first, but it's been around since liberty | |
| 04:12:54 | Jeffrey4l | mriedem, roger. thanks. | |
| 04:48:04 | mriedem | ocata rc2 patch is up and ready to go, should be released by tomorrow | |
| 05:19:34 | openstackgerrit | christopher.uhler proposed openstack/nova-specs master: Spec for libvirt driver extension for Veritas HyperScale https://review.openstack.org/430488 | |
| 06:10:30 | openstackgerrit | Anh Tran proposed openstack/nova master: Remove unused logging import https://review.openstack.org/435261 | |
| 08:17:25 | openstackgerrit | Anh Tran proposed openstack/nova master: Remove unused logging import https://review.openstack.org/435261 | |
| 08:33:17 | xiaoyang | hi, everyone. Why instance live migration after success doesn't change the availability zone? | |
| 08:53:18 | johnthetubaguy | xiaoyang: we don't really support availability zone concept, except for scheduling Nova resources close to Cinder resources when you first boot the instance | |
| 08:53:37 | johnthetubaguy | xiaoyang: sounds like a bug worth reporting (and fixing) though | |
| 08:54:12 | johnthetubaguy | it seems like live-migration shouldn't really allow you to move outside the original availability zone, but I guess we don't check that. | |
| 09:07:59 | bauzas | johnthetubaguy: there is something I saw about AZs | |
| 09:08:09 | bauzas | and live-migration | |
| 09:08:52 | bauzas | johnthetubaguy: tbc, if an instance is booted using the az flag, then we force to keep that instance in the AZ if live-migrate is calling the scheduler | |
| 09:09:01 | bauzas | but only after Mitaka | |
| 09:09:19 | johnthetubaguy | bauzas: ah, right, and I guess unless we force it to a host | |
| 09:11:48 | bauzas | yup using the new flag I added in Newton IIRC | |
| 09:12:01 | bauzas | (or Mitaka? not sure) | |
| 09:12:03 | bauzas | anyway | |
| 09:12:32 | bauzas | that said, I saw something weirdo in that from a internal perspective, and I'm still looking at it | |
| 09:16:46 | openstackgerrit | Zhenyu Zheng proposed openstack/nova master: Should raise correct error instead of class exist in Placement API https://review.openstack.org/428612 | |
| 09:19:54 | openstackgerrit | Silvan Kaiser proposed openstack/nova master: Removes getfattr from Quobyte Nova driver https://review.openstack.org/428646 | |
| 09:27:53 | openstackgerrit | Markus Zoeller (markus_z) proposed openstack/nova master: live-migration test hook for serial console https://review.openstack.org/347471 | |
| 09:29:32 | openstack | Launchpad bug 1652335 in OpenStack Compute (nova) "The scheduler returns limits even if the instance was boot using AZ forced flag" [Medium,Confirmed] - Assigned to Sylvain Bauza (sylvain-bauza) | |
| 09:29:32 | bauzas | johnthetubaguy: found the bug I noticed internally https://bugs.launchpad.net/nova/+bug/1652335 | |
| 10:01:21 | tojuvone | johnthetubaguy, Hi, continuing host maintenance where left before Ocata as working with it in Craton | |
| 10:01:29 | tojuvone | johnthetubaguy, https://review.openstack.org/428070/ | |
| 10:01:52 | mdbooth | lyarwood: Do you have an opinion on https://review.openstack.org/#/c/430091/5, btw? Trade off of expedient fix for 1 edge case vs a more complex fix for the underlying problem. I ask because your previous reviews were positive. | |
| 10:03:37 | johnthetubaguy | tojuvone: ah, remember to bug me about that one when we are back from the PTG, interesting in getting progress on that | |
| 10:05:05 | tojuvone | johnthetubaguy, Thanks | |
| 10:05:28 | johnthetubaguy | tojuvone: my initial take is you should focus on the os-services API instead of looking as os-hypervisors, because that is where all the actions are like force-host-down | |
| 10:06:58 | tojuvone | johnthetubaguy, yes, could remove that part. It was more or less to have os-hypervisors inline with fileds shown, but really not needed | |
| 10:11:17 | johnthetubaguy | tojuvone: I added a comment on the use cases, I think you should write out two flows: what the admin does during a "typical" maintenance, and what the user does. That should show how the new APIs are needed to enable those flows. | |
| 10:11:48 | johnthetubaguy | tojuvone: stuff like schedules windows for AZ A, B and C, user notes the windows and decides what workloads are affected, etc, etc | |
| 10:12:14 | johnthetubaguy | tojuvone: I would keep them separate though, do the admin flow, then the user flow that relates to what the admin has done | |
| 10:15:02 | tojuvone | johnthetubaguy, ok, now just have link to external material. But like you said, better to explain more in spec, so it is more readable | |
| 10:15:33 | johnthetubaguy | tojuvone: right, but you need to describe how that link gets used within the real situation | |
| 10:16:08 | johnthetubaguy | tojuvone: something tells me we should define expected start/stop times and a link for more information, so the scheduler can be told about what is happening | |
| 10:17:13 | johnthetubaguy | but once the use case is clear, it should be easier to understand | |
| 10:17:25 | xiaoyang | i think haveif make compute node add other aggregate which have different availability zone. The instance`s availability zone on this node will not change | |
| 10:17:46 | tojuvone | all that was moved away in Ocata as it was agreed earlier not to have that much in Nova | |
| 10:18:08 | tojuvone | I mean spec in Ocata | |
| 10:18:42 | tojuvone | all that start, stop, state was put to external service where there would only be a link | |