Earlier  
Posted Nick Remark
#openstack-nova - 2017-01-12
22:15:43 mriedem to opt in or pin the version
22:15:57 mriedem which is exactly what you have to do if you're requesting specific microversions via the python API
22:15:59 scottda ildikov: But why are you using 3.0? You'll still need the version with the new APIs
22:16:06 mriedem microversions in the python API bindings is opt-in,
22:16:21 mriedem the shell is a convenience to use the latest available that the client understands and the server can provide,
22:16:34 mriedem if you're coding to the shell and worry about changes with microversions, then you also have to pin with --os-compute-api-version
22:16:34 scottda BBIAB
22:17:18 ildikov scottda: I'm trying to make Nova pick up the new Cinder APIs and I kind of got stuck with how to do that and hence the questions on every relevant channel
22:21:17 openstackgerrit Dan Smith proposed openstack/nova: Make api_samples tests use simple cell environment https://review.openstack.org/410473
22:21:21 openstackgerrit Dan Smith proposed openstack/nova: WIP Move instance creation to conductor https://review.openstack.org/319379
22:26:43 cdent #success edleafe found narrowed down an important bug in gabbi
22:26:44 openstackstatus cdent: Added success to Success page
22:26:58 cdent huh
22:27:03 cdent I've wanted to try that for a while
22:27:18 mriedem found narrowed down?
22:28:12 cdent both
22:28:35 cdent english, when typed, is my 6th language
22:28:41 mriedem heh
22:31:04 cdent sadly, I'm a total fail at solving the bug
22:31:12 cdent I guess that'll have to be tomorrow
22:32:56 mriedem just mark the bug as low-hanging-fruit
22:33:04 mriedem you'll have 10 new contributors lined up to fix it
22:33:32 stewie925_ hello all, hopefully a quick question - I have set up compute on my openstack and then I tried "sudo service nova-api restart" - it returned "nova-api stop/waiting nova-api start/running, process 4383"
22:33:41 stewie925_ is that a confirmation that the nova-api restarted successfully?
22:33:59 mriedem stewie925_: i know you're not new to this channel, but see the channel topic
22:34:15 cdent mriedem: that explains it. I haven't been tagging the bugs.
22:34:22 mriedem how you're deploying it on which distro and what packages etc etc isn't really for this channel
22:34:31 stewie925_ sorry
22:34:52 mriedem np - you'll know it's running if there are logs somewhere
22:51:15 openstackgerrit Davanum Srinivas (dims) proposed openstack/nova: [WIP][py35] Trying to get cinder+rally working https://review.openstack.org/419476
22:53:18 dims mriedem : i think i am very close to nova boot a vm with this https://review.openstack.org/#/c/419476/
22:56:26 mriedem [WIP][py35] Trying to get cinder+rally working ?
22:56:30 mriedem wrong title?
22:57:20 dims mriedem : actually i am watching gate-rally-dsvm-py35-cinder-nv over at https://review.openstack.org/#/c/418643/ and debugging nova started from a rally test
23:07:20 mriedem jroll: fyi https://review.openstack.org/#/c/415867/
23:07:29 mriedem just updated that thing
23:08:23 jroll mriedem: u-c already landed, and I put up https://review.openstack.org/#/c/419630/ this morning
23:08:42 mriedem jroll: https://review.openstack.org/#/c/415867/ is the one that the nova change depends on
23:08:49 mriedem https://review.openstack.org/#/c/364413/ depends on ^
23:08:49 jroll yeah, I see that now
23:08:56 mriedem and is therefore infinitely more important :)
23:09:31 jroll ya
23:46:33 openstackgerrit Ed Leafe proposed openstack/nova: Add check for invalid allocation amounts https://review.openstack.org/416752
23:46:33 openstackgerrit Ed Leafe proposed openstack/nova: Remove the Allocation.create() method. https://review.openstack.org/416751
23:46:34 openstackgerrit Ed Leafe proposed openstack/nova: Fix missing RP generation update https://review.openstack.org/419137
23:54:51 dims nova.boot_server/attach_volume/detach_volume works! http://logs.openstack.org/43/418643/2/check/gate-rally-dsvm-py35-cinder-nv/c48f74a/rally-plot/results.html.gz#/CinderVolumes.create_and_attach_volume/details
23:54:56 dims (py35)
#openstack-nova - 2017-01-13
02:12:02 openstackgerrit Zhenyu Zheng proposed openstack/nova: Don't delete neutron port when attach failed https://review.openstack.org/403568
02:24:42 alex_xu Kevin_Zheng: just commented on https://review.openstack.org/#/c/419256/7, we still can make it simpler
02:25:12 Kevin_Zheng Thanks
02:45:35 openstackgerrit Jeremy Liu proposed openstack/python-novaclient: Enable coverage report in console output https://review.openstack.org/419723
02:54:20 openstackgerrit Anusha Unnam proposed openstack/nova: Add keypairs field to InstancePayload https://review.openstack.org/419730
03:04:06 openstackgerrit Anusha Unnam proposed openstack/nova: Add keypairs field to InstancePayload https://review.openstack.org/419730
03:28:36 mriedem edleafe: have you ever seen this failure in a functional test run for placement? http://logs.openstack.org/60/416760/1/check/gate-nova-tox-db-functional-ubuntu-xenial/f192837/console.html#_2017-01-12_15_22_00_609678
03:28:43 openstackgerrit zhaolihui proposed openstack/nova: Fix keypair quota error https://review.openstack.org/403529
03:30:42 mriedem seems to be random
03:33:17 openstackgerrit Zhenyu Zheng proposed openstack/nova: [poc] add some code to reject known bad filters. https://review.openstack.org/419256
03:33:41 openstackgerrit Davanum Srinivas (dims) proposed openstack/nova: [WIP][py35] Trying to get cinder+rally working https://review.openstack.org/419476
03:37:19 mriedem nvm i think it's a problem in that change actually
03:37:23 mriedem i'm probably missing some backport
03:46:49 alex_xu johnthetubaguy: gmann, Kevin_Zheng puts two ideas into single patch https://review.openstack.org/419256, probably enough to take look at how those looks like in the code.
03:53:38 openstackgerrit Davanum Srinivas (dims) proposed openstack/nova: [WIP][py35] Trying to get cinder+rally working https://review.openstack.org/419476
03:55:12 gmann alex_xu: johnthetubaguy Kevin_Zheng thanks, while giving try i got a way to reject known property from schema itself
03:55:38 gmann alex_xu: johnthetubaguy Kevin_Zheng we can do with 'not' propoerty, i commented on this about how - https://review.openstack.org/#/c/408571/38
03:56:07 gmann actually in draft3 formatter it was 'disallow' and in 4 it is 'not'
03:56:17 gmann https://github.com/json-schema/json-schema/wiki/anyOf,-allOf,-oneOf,-not#not
03:56:22 gmann https://github.com/json-schema/json-schema/wiki/anyOf,-allOf,-oneOf,-not#replacing-schemas-in-disallow
03:56:57 gmann so basically with empty object with not like- 'not': {} we can reject all values of given element
03:57:38 alex_xu gmann: what kind of error message we can get?
03:58:09 diga gibi: Hi
03:58:34 gmann alex_xu: yea that is nice point
03:58:44 gmann alex_xu: it will like Invalid input for field/attribute system_metadata. Value: . {} is not allowed for 'mymeta'
03:58:58 gmann which we might need to modify seems
04:00:00 Kevin_Zheng Actually I like the format way better
04:00:55 alex_xu gmann: if we can get a correct message that will be great, not sure there is way to change that message
04:01:29 Kevin_Zheng it will be harder than the new format thing I think
04:01:56 alex_xu yea, i'm also worry about that
04:01:58 gmann alex_xu: yea error message is issue but let me check if we can easily modify that
04:02:03 Kevin_Zheng the mssage is below the one I changed for the current way
04:02:45 Kevin_Zheng maybe hard to identify the "not" thing because it might be a validation error?
04:02:46 alex_xu gmann: really appreciate that :)
04:03:00 Kevin_Zheng VallidationError
04:03:38 gmann Kevin_Zheng: yea it will be validation error from json itself
04:04:45 Kevin_Zheng gmann: yeah, but other also raise ValidationError and the msg was generated. So we have to identify the case of this
04:04:58 Kevin_Zheng maybe harder than the current way
04:05:49 gmann Kevin_Zheng: yea, that is pain point.
04:14:24 gmann alex_xu: Kevin_Zheng yea we have to add hack for that which kindda new overridden code on top of json schema. That is what new formatter way.
04:31:33 openstackgerrit Davanum Srinivas (dims) proposed openstack/nova: [WIP][py35] Trying to get cinder+rally working https://review.openstack.org/419476
04:36:57 gmann alex_xu: Kevin_Zheng i think formatter is ok which is much easy, how about showing few schema example with new 'format' also in https://review.openstack.org/#/c/419256/7
05:19:23 openstackgerrit Zhenyu Zheng proposed openstack/nova: [poc] add some code to reject known bad filters. https://review.openstack.org/419256
05:21:21 Kevin_Zheng gmann: thanks, and I replied your comment, and I just came up with the idea to also assert the error message in one test, will add it later
05:24:52 gmann Kevin_Zheng: i see, nice. thanks test case will be nice there
05:57:54 openstackgerrit zhaolihui proposed openstack/nova: Fix keypair quota error https://review.openstack.org/403529
06:16:28 openstackgerrit Jeremy Liu proposed openstack/python-novaclient: Enable coverage report in console output https://review.openstack.org/419723
06:35:20 openstackgerrit Istvan Imre proposed openstack/python-novaclient: Pass relevant parameters to Token based authentication https://review.openstack.org/419441
06:56:30 openstackgerrit Zhenyu Zheng proposed openstack/nova: [poc] add some code to reject known bad filters. https://review.openstack.org/419256
06:57:02 Kevin_Zheng gmann, alex_xu tests added ^
08:04:11 snikitin In our upgrade case we can try to fill diagnostics fields by information we got from old hypervisor drivers (most of fields in old and new diagnostics objects are equal) and left other fields empty. And of course we should log warning something like "Your compute is to old so data in diagnostics response may be incomplete" . What do you think?
08:04:11 snikitin As response of new micriversion is standartized we must return all diagnostics fields. But as we noted in spec and docs, some of this fields may be 'None' because some hypervisors can't provides some kinf in information.
08:04:11 snikitin alex_xu: Hi Alex! good point about upgrade problem in diagnostics api. You described case when we have new api and old compute, right? I think we can handle this case in view class https://review.openstack.org/#/c/355540/18/nova/api/openstack/compute/views/server_diagnostics.py

Earlier   Later