Earlier  
Posted Nick Remark
#openstack-nova - 2020-06-17
06:51:16 bauzas good morning Nova
06:51:32 bauzas gibi: what's the problem ?
06:52:26 bauzas gibi: nevermind, saw your pastebin
06:56:36 brinzhang0 morning gibi, bauzas
06:57:03 brinzhang0 Can I fix this bug ?https://bugs.launchpad.net/nova/+bug/1468992
06:57:03 openstack Launchpad bug 1468992 in OpenStack Compute (nova) "nova list's --tenant filter does not return expected servers" [Low,Triaged] - Assigned to Vishakha Agarwal (vishakha.agarwal)
06:58:13 brinzhang0 I saw in the list servers api doesnot contain tenant_id to filter servers, but the CLI can do by novaclinet
06:59:15 brinzhang0 Do you have time to check this bug?
07:01:45 bauzas gibi: no issues with py37 testing http://paste.openstack.org/show/794847/
07:01:47 bauzas for me
07:01:57 bauzas gibi: I'd suggest you to 'git clean -xfd' your repo
07:02:26 bauzas brinzhang0: looking
07:04:25 brinzhang0 bauzas: cool
07:05:23 bauzas brinzhang0: saw johnthetubaguy's comment ? https://bugs.launchpad.net/nova/+bug/1468992/comments/5
07:05:23 openstack Launchpad bug 1468992 in OpenStack Compute (nova) "nova list's --tenant filter does not return expected servers" [Low,Triaged] - Assigned to Vishakha Agarwal (vishakha.agarwal)
07:05:42 bauzas I agree with him, we should discuss this in a spec
07:05:48 brinzhang0 bauzas: I saw
07:06:22 brinzhang0 I would like to submit a spec, so I want to ensure for you, that I will continue
07:09:25 bauzas brinzhang0: sorry but I don't understand your question, do you want to be sure I'll review the spec ?
07:10:10 brinzhang0 bauzas: no, I just want to ensure that I can push a spec for this bug
07:11:05 brinzhang0 I worry about doing meaningless things, so I ask you firstly
07:15:41 brinzhang0 bauzas: how about now? I think I said clearly ^
07:16:08 gibi bauzas: git clean did not help, removing venv did not help. But removing $HOME/.cache/pip directory and then removing the venv did helped.
07:16:59 bauzas gibi: ack, gtk
07:17:22 bauzas brinzhang0: ahah, gotcha, well, it changes the API, right?
07:17:37 bauzas if so, we need a microversion, hence a spec
07:18:07 brinzhang0 gibi: in my env installed 3.6.8, Can I install py3.7 directly? Then directly ./stack.sh?
07:18:20 bauzas when i say "it changes the API", that means that the API will behave differently for the same call
07:18:26 brinzhang0 bauzas: yes, I will submit a spec
07:20:10 gibi bauzas, stephenfin: by removing $HOME/.cache/pip dir I got different dependency versions so some of it caused the fail for me locally http://paste.openstack.org/show/794848/
07:20:56 gibi brinzhang0: I think you can, but I talking about unit test not devstack
07:21:08 openstackgerrit Sylvain Bauza proposed openstack/nova-specs master: Routed network scheduling spec https://review.opendev.org/733703
07:21:47 brinzhang0 I know, that I want to update my local env, but I am not sure after I update the py37 it can work good
07:22:19 bauzas gibi: you're still having problems ?
07:22:28 brinzhang0 gibi: I donot know do you have the same same experience^
07:22:44 gibi bauzas: with the new deps the test passes now locally.
07:23:02 gibi bauzas: so I guess there is some deps that we should blacklist
07:23:44 bauzas ahah, gotcha
07:23:58 bauzas well, we don't use tooz for example
07:24:15 gibi bauzas: I guess we get tooz transitively
07:24:17 bauzas neither taskflow AFAIK
07:24:55 gibi bauzas: virt/powervm uses taskflow in nova
07:25:01 bauzas gibi: sure but the issue you got was on mock, right?
07:25:11 gibi yeah, it was a mock issue
07:25:12 bauzas argh /o\
07:25:31 gibi so none of the deps stands out
07:25:40 gibi brinzhang0: I think you are save to upgrade to 3.7
07:25:53 bauzas gibi: I had problems with my local env when I upgraded from an old Fedora release (which was using py2) to F31
07:26:02 brinzhang0 gibi: trying now
07:26:10 bauzas but i fixed all of them by cleaning up my repos
07:26:20 bauzas gibi: have you changed your OS too ?
07:27:23 gibi bauzas: it was a fresh machine I had to move of my testing effort so it is a fresh install of ubuntu 18.04 where I see the problem
07:29:49 gibi I guess when I run the test on that machine first I got some bad deps and then later new version of those deps was released so the problem gone now as I forced the redownload
07:30:10 gibi by deleting the local pip cache
08:19:14 openstackgerrit Takashi Natsume proposed openstack/nova master: Remove hacking rules for python 2/3 compatibility https://review.opendev.org/733987
08:19:33 openstackgerrit Takashi Natsume proposed openstack/nova master: Remove six.PY2 and six.PY3 https://review.opendev.org/726512
08:19:47 openstackgerrit Takashi Natsume proposed openstack/nova master: Remove six.add_metaclass https://review.opendev.org/726565
08:20:00 openstackgerrit Takashi Natsume proposed openstack/nova master: Remove six.reraise https://review.opendev.org/726898
08:20:18 openstackgerrit Takashi Natsume proposed openstack/nova master: Remove six.moves https://review.opendev.org/727224
08:20:29 openstackgerrit Takashi Natsume proposed openstack/nova master: Remove six.iteritems/itervalues/iterkeys https://review.opendev.org/727757
08:20:43 openstackgerrit Takashi Natsume proposed openstack/nova master: Remove six.byte2int/int2byte https://review.opendev.org/727777
08:20:55 openstackgerrit Takashi Natsume proposed openstack/nova master: Remove six.binary_type/integer_types/string_types https://review.opendev.org/728094
08:21:08 openstackgerrit Takashi Natsume proposed openstack/nova master: Remove six.text_type (1/2) https://review.opendev.org/728109
08:21:26 openstackgerrit Takashi Natsume proposed openstack/nova master: Remove six.text_type (2/2) https://review.opendev.org/728117
09:35:35 openstackgerrit Wenping Song proposed openstack/nova master: delete sub resource provider when delete resource provider https://review.opendev.org/719163
09:48:25 openstackgerrit sunhao proposed openstack/nova stable/train: hardware: Raise useful error for invalid mempage size https://review.opendev.org/735950
10:04:23 stephenfin bauzas: Care to review https://review.opendev.org/#/c/734658/ ?
10:04:32 bauzas I can
10:04:42 stephenfin ta
10:04:47 bauzas fwiw, I want to look at runways
10:47:25 brinzhang0 stephenfin: hi, we encounter an issue, and I register a blueprint, can you review it? https://blueprints.launchpad.net/oslo.cache/+spec/enable-sasl-protocol
10:48:14 brinzhang0 stephenfin: thanks
11:57:11 openstackgerrit Alexandre Arents proposed openstack/nova master: Snapshot: offload glance upload in a native thread https://review.opendev.org/734776
11:57:17 openstackgerrit Balazs Gibizer proposed openstack/nova master: Extend is_ipv6_supported() to cover more error cases https://review.opendev.org/736167
12:02:35 openstackgerrit Alexandre Arents proposed openstack/nova master: Limit the number of concurrent snapshots https://review.opendev.org/736169
12:17:27 openstackgerrit Sean McGinnis proposed openstack/nova master: Use unittest.mock instead of third party mock https://review.opendev.org/714676
12:27:58 openstackgerrit Sean McGinnis proposed openstack/nova master: hacking: force explicit import of python's mock https://review.opendev.org/708768
12:41:47 openstackgerrit Merged openstack/nova master: libvirt: Don't allow "reserving" file-backed memory https://review.opendev.org/734658
13:00:15 openstackgerrit Alexandre Arents proposed openstack/nova master: Limit the number of concurrent snapshots https://review.opendev.org/736169
13:04:23 openstackgerrit Alexandre Arents proposed openstack/nova master: Snapshot: offload glance upload in a native thread https://review.opendev.org/734776
13:37:45 openstackgerrit Stephen Finucane proposed openstack/nova stable/ussuri: libvirt: Don't allow "reserving" file-backed memory https://review.opendev.org/736219
14:02:19 openstackgerrit Balazs Gibizer proposed openstack/nova master: Extend is_ipv6_supported() to cover more error cases https://review.opendev.org/736167
14:24:19 TheJulia Greetings nova folks, would nova be generally amenable if the ironic virt driver had a capability for a user of reserving a physical baremetal machine but not actually triggering the deployment. We're thinking this would basically be a trait, and we could teach ironic to just ignore the deploy if the trait is present, but we woudl also likely update permissions so the user is "leased" the physical node.
14:25:09 dansmith TheJulia: you mean exclude machines with that trait set from the scheduling decision right?
14:25:28 TheJulia well, mark it in use/active in nova
14:26:00 TheJulia and tell ironic "hey, this user asked for and is now allocated this hardware" and then the user can pivot APIs to perform super advanced operations
14:26:32 dansmith meaning nova just "reserves" the node in ironic but does nothing with it, assuming the user is going to do stuff with it out of band?
14:26:50 TheJulia no, more like we just skip the final step telling ironic to perform the deployment
14:27:01 dansmith how is that different?
14:27:39 TheJulia today we actually trigger a deployment which means the machine is delivered in an active state
14:28:00 dansmith I mean how is what you said not what I said?
14:28:17 sean-k-mooney TheJulia: this sound more like a blazar usecase
14:28:27 dansmith if nova reserves the node (i.e. in placement) but just doesn't ask ironic to do anything with it, that's what you're asking right?
14:28:30 dansmith sean-k-mooney: agreed
14:28:43 sean-k-mooney that said we have a trait for marking a compute node as down today
14:28:56 sean-k-mooney if it was a maintaince usecase then that woudl be approporte to use
14:29:04 sean-k-mooney we dont really have a reservation concept in nova however
14:29:10 sean-k-mooney not sure how we would cleanly add one
14:29:11 dansmith sean-k-mooney: I think TheJulia is asking for the opposite of that, for nova to do everything we would normally do to boot on a node, but just ... not boot on the node
14:29:40 dansmith sean-k-mooney: which is basically making nova a reserve-but-don't-touch service, which wouldn't be sensical for anything other than resources that already exist (i.e. physical machines)

Earlier   Later