| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2017-04-10 | |||
| 21:26:45 | jroll | good, I didn't want him anyway | |
| 21:38:26 | mriedem | i guess we should care about https://review.openstack.org/#/q/topic:bp/prep-for-network-aware-scheduling-pike,n,z at some point | |
| 21:38:29 | mriedem | given we didn't at all for ocata | |
| 21:41:40 | cdent | so many things | |
| 21:45:53 | mriedem | yeah too many things | |
| 21:53:20 | mtreinish | mriedem: +A | |
| 21:55:48 | mriedem | hells yes! | |
| 22:11:35 | mriedem | sdague: johnthetubaguy: alex_xu: for your tomorrow, jaypipes left some good comments in the spec to deprecate os-virtual-interfaces https://review.openstack.org/#/c/455023/ - mainly around trimming the fat on the existing response, which johnthetubaguy had also touched on back in newton or ocata when we talked about this | |
| 22:11:50 | mriedem | i'm just wondering how slim we want to get | |
| 22:23:28 | openstackgerrit | melanie witt proposed openstack/nova-specs master: Amend spec for placement project/user association https://review.openstack.org/454352 | |
| 22:28:05 | openstackgerrit | melanie witt proposed openstack/nova-specs master: Amend spec for placement project/user association https://review.openstack.org/454352 | |
| 22:28:26 | mriedem | rpodolyaka_afk: are you owning this spec for pavel now? https://review.openstack.org/#/c/381912/ | |
| 22:30:37 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Remove aggregate uuid generation on load from DB https://review.openstack.org/448579 | |
| 22:33:53 | openstackgerrit | Matt Riedemann proposed openstack/nova master: 2.43: Remove Location header from createImage and createBackup responses https://review.openstack.org/455443 | |
| 22:48:52 | dtp | these shadow tables - do they store the state of records at every change, or only the final state of the record when it is deleted from its main table? | |
| 22:58:33 | mriedem | dtp: they are used during archive | |
| 22:58:43 | mriedem | the "deleted" records are moved from the main tables to the shadow tables | |
| 22:58:49 | mriedem | during nova-manage db archive_deleted_rows | |
| 22:58:58 | mriedem | so yeah final state | |
| 22:59:06 | dtp | cool, thanks | |
| 23:00:17 | mriedem | dtp: btw, when we get to the api part of that uuid in api bp, i think i'll let you do the os-services api which should be much more straightforward than the os-hypervisors api changes | |
| 23:00:19 | mriedem | i'll take the latter | |
| 23:00:30 | mriedem | since it's going to be more than just the uuid stuff in that one, it's basically a re-write | |
| 23:00:45 | dtp | ok | |
| 23:01:27 | dtp | do you want shadow_services.uuid indexed? | |
| 23:02:18 | mriedem | no | |
| 23:02:24 | mriedem | we don't query anything out of the shadow tables | |
| 23:02:30 | mriedem | so don't care about constraints or indexes there | |
| 23:16:10 | dtp | mriedem are you still tracking who's coming to boston? | |
| #openstack-nova - 2017-04-11 | |||
| 00:13:24 | openstackgerrit | Dan Peschman proposed openstack/nova master: Add uuid to Service model https://review.openstack.org/453025 | |
| 02:06:29 | openstackgerrit | Alex Xu proposed openstack/nova-specs master: Deprecate multinic proxy API https://review.openstack.org/384261 | |
| 02:06:45 | alex_xu | mriedem: ^ updated | |
| 02:12:26 | openstackgerrit | Alex Xu proposed openstack/nova master: placement: Add Traits API to placement service https://review.openstack.org/376200 | |
| 02:40:40 | openstackgerrit | Spencer Yu proposed openstack/python-novaclient master: Nova client should retry with Retry-After value https://review.openstack.org/447766 | |
| 03:18:43 | mriedem | alex_xu: thanks, a couple of small things were missed | |
| 03:18:51 | mriedem | but overall should be easy to fix and then i'm +2 | |
| 03:20:19 | openstackgerrit | Ghanshyam Mann proposed openstack/nova master: Fix api-ref for create servers response https://review.openstack.org/451673 | |
| 03:25:34 | mriedem | tommylikehu: re https://review.openstack.org/#/c/453272/3/specs/pike/approved/nova-support-attached-volume-extend.rst@26 nova does not yet support volume multiattach upstream | |
| 03:25:38 | mriedem | so a VM is correct there | |
| 03:27:13 | tommylikehu | mriedem: thanks | |
| 03:39:06 | openstackgerrit | Bob Ball proposed openstack/nova master: XenAPI: device tagging https://review.openstack.org/333781 | |
| 03:41:04 | mriedem | tommylikehu: mgagne: comments inline https://review.openstack.org/#/c/453272/3 | |
| 03:55:45 | tommylikehu | mriedem: great, thanks! | |
| 04:35:32 | openstackgerrit | Mathieu Gagné proposed openstack/nova-specs master: Nova support for attached volume extend https://review.openstack.org/453272 | |
| 05:10:35 | openstackgerrit | Mathieu Gagné proposed openstack/nova-specs master: Nova support for attached volume extend https://review.openstack.org/453272 | |
| 05:42:24 | openstackgerrit | Mathieu Gagné proposed openstack/nova-specs master: Nova support for attached volume extend https://review.openstack.org/453272 | |
| 05:51:31 | openstackgerrit | Alex Xu proposed openstack/nova-specs master: Deprecate multinic proxy API https://review.openstack.org/384261 | |
| 06:07:52 | openstackgerrit | Lei Zhang proposed openstack/nova master: Add sync traits command for placement https://review.openstack.org/450125 | |
| 06:16:13 | nirendra | Hi, Nova placement API checks for max_units which is local_gb for the host. This makes allocation_ratio useless. So if I'm trying to create a VM with 80GB root disk and disk_allocation_ratio as 100, it fails for a host which does not have 80GB local storage | |
| 06:16:26 | nirendra | Is this a known bug? I couldn't find one in Launchpad | |
| 07:16:20 | openstackgerrit | YuYang proposed openstack/nova master: VMware:fix get VM root device conditional verify https://review.openstack.org/454441 | |
| 07:20:26 | openstackgerrit | YuYang proposed openstack/nova master: VMware:fix get VM root device conditional verify https://review.openstack.org/454441 | |
| 07:49:58 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: api-ref: Parameter verification for servers-actions (1/4) https://review.openstack.org/455563 | |
| 07:52:13 | openstackgerrit | Zhenyu Zheng proposed openstack/nova master: Fix HTTP 500 raised for getColsolelog for stopped instance https://review.openstack.org/455183 | |
| 07:55:49 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: api-ref: Parameter verification for servers-actions (2/4) https://review.openstack.org/455568 | |
| 08:00:30 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: api-ref: Parameter verification for servers-actions (3/4) https://review.openstack.org/455570 | |
| 08:04:57 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: api-ref: Parameter verification for servers-actions (4/4) https://review.openstack.org/455573 | |
| 09:03:15 | d9k | when instance is destroyed neutron deletes ipsets while nova is modifying iptables and https://ptpb.pw/16S8 happens, acquiring neutron-ipset lock in (network/linux_net.py) IptablesManager._apply seems to fix the problem | |
| 09:15:19 | jsheeren | hi, question: is it possible to limit image A to be only able to use flavor X and Y, image B only flavor Z? | |
| 09:28:42 | prabhuraj | Hi team, Someone could review the following changes : | |
| 09:28:48 | prabhuraj | https://review.openstack.org/#/c/397471/ | |
| 09:29:05 | prabhuraj | https://review.openstack.org/#/c/397459/ | |
| 09:40:10 | BobBall | Howdy - Trying to use device tagging I'm getting an "Invalid input for field/attribute networks" - nova cli says I need to use ",tag=<value>" but schema validation fails if I add it. Openstack cli doesn't seem to support tags (According to help text anyway)... | |
| 09:40:19 | BobBall | Can someone remind me how to use tagging? | |
| 09:41:45 | johnthetubaguy | openstack cli doesn't support microversions yet | |
| 09:41:53 | johnthetubaguy | afaik | |
| 09:42:09 | johnthetubaguy | did you try with nova client? | |
| 09:42:21 | BobBall | Yes - that's what failed the schema validation when running it | |
| 09:44:38 | BobBall | http://paste.openstack.org/show/606121/ - I'm clearly using the wrong syntax | |
| 09:45:08 | BobBall | (or device tagging is broken...) | |
| 09:49:15 | abhi89 | johnthetubaguy: can you please review https://review.openstack.org/#/c/455118/2 | |
| 09:58:13 | johnthetubaguy | BobBall: that doesn't seem good | |
| 09:58:29 | BobBall | OK - so the nova client does not now support nova microversion 2.42 - for some reason 7.1.0 was installed | |
| 09:59:00 | BobBall | it's just weird that novaclient 7.1.0 lists tag in the help text but doesn't support the microversion which introduced the API | |
| 09:59:04 | johnthetubaguy | BobBall: try do the full debug and see what version is requested | |
| 09:59:10 | johnthetubaguy | yeah, thats... inconsistent | |
| 09:59:25 | johnthetubaguy | probably only got some of the patches landed | |
| 09:59:33 | BobBall | nova client is requesting 2.41 - which doesn't support tagging... *jumps with joy* | |
| 09:59:54 | johnthetubaguy | BobBall: did you try explicitly request the new version, it might be we couldn't raise the maximum at that point | |
| 10:00:14 | BobBall | Yes - python-novaclient says it's not supported. | |
| 10:00:18 | johnthetubaguy | not 100% sure thats a thing | |
| 10:00:20 | johnthetubaguy | ha | |
| 10:00:41 | johnthetubaguy | abhi89: I think this might be the code you need to change for your bug: https://github.com/openstack/nova/blob/3092d2adcb6bab0bf39b01ea0561ec7e6a3990fd/nova/compute/manager.py#L1585 | |
| 10:01:25 | Dinesh_Bhor | sfinucan: Hi, addressed your review comments. Already got one +2 please take a look at it whenever you are free: https://review.openstack.org/#/c/364687/ | |
| 10:01:38 | sfinucan | Dinesh_Bhor: Will do | |
| 10:01:55 | Dinesh_Bhor | sfinucan: thanks | |
| 10:05:51 | ishant | Hi All, I am creating instance and it always sets availability_zone as None even though default_availability_zone value is 'nova' | |
| 10:06:17 | ishant | beacuse of this port device_owner is always set as compute:None | |
| 10:06:27 | BobBall | Even the latest python-novaclient does not support the required API micro version!!! http://git.openstack.org/cgit/openstack/python-novaclient/tree/novaclient/__init__.py | |
| 10:06:55 | BobBall | In other words, I think no one can use python-novaclient to specify device tagging at all. | |
| 10:15:36 | sfinucan | ralonsoh: You around. Question on https://review.openstack.org/#/c/444415 for you | |
| 10:16:57 | ralonsoh | sfinucan: hi! | |
| 10:18:04 | sfinucan | ralonsoh: How come we're using the 'extra_info' column in that review rather than adding a new capabilities column? | |
| 10:18:54 | sfinucan | I didn't even question it until you said that nothing else was using the column now. If it was important enough to move out the other stuff, why re-add new stufF? | |
| 10:19:33 | ralonsoh | sfinucan: that is the easy way, to add a new field | |
| 10:20:05 | ralonsoh | sfinucan: instead of this, we decided not to modify the DB schema and add this information into extra_info | |
| 10:20:36 | ralonsoh | sfinucan: extra_info is initially a bucket for "other" information, not so relevant | |
| 10:22:06 | sfinucan | ralonsoh: OK. What's the long term strategy then? Drop that entire table in favour of resource providers? | |
| 10:22:18 | openstackgerrit | Stephen Finucane proposed openstack/nova master: Add description to policies in hypervisors.py https://review.openstack.org/451294 | |
| 10:22:48 | ralonsoh | sfinucan: yes, move every item (network:capabilities, etc) to resource providers | |