| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2018-08-01 | |||
| 14:13:39 | sean-k-mooney | i have have been trying to figure out how to run coverage test of nova on and off but never actully done it beacues im not sure i want to know | |
| 14:14:15 | sean-k-mooney | that said i would not mind spending a little tiem working on code coverage to learn some of the code base i dont normally touch | |
| 14:15:21 | mriedem | sean-k-mooney: https://review.openstack.org/587636 | |
| 14:15:48 | mriedem | tox -e cover only runs unit tests, so misses all functional test coverage | |
| 14:16:05 | sean-k-mooney | mriedem: yes i started to review it :) | |
| 14:16:07 | mriedem | but a coverage report doesn't give you any idea of end to end scenario coverage | |
| 14:16:20 | sean-k-mooney | mriedem: ya | |
| 14:19:11 | sean-k-mooney | they also need python 3... time to go install that on centos again. | |
| 14:19:39 | efried | melwitt, dansmith, mriedem: Thoughts on requesting +r for this channel? | |
| 14:19:56 | sean-k-mooney | efried: +r? | |
| 14:19:59 | dansmith | no way | |
| 14:20:16 | efried | sean-k-mooney: http://lists.openstack.org/pipermail/openstack-dev/2018-August/132692.html | |
| 14:20:27 | dansmith | sean-k-mooney: requires registered nicks to join | |
| 14:20:44 | sean-k-mooney | dansmith: ah ok to stop spam | |
| 14:20:47 | efried | yuh | |
| 14:21:08 | dansmith | freenode is catching them very quickly so one spam message every now and again is pretty minor, and it's just a recent wave | |
| 14:21:15 | sean-k-mooney | we are getting some but not a lot | |
| 14:21:29 | dansmith | yeah, +r would be a major overreaction IMHO | |
| 14:22:03 | sean-k-mooney | +r might also break some irc relays/bouncers | |
| 14:22:19 | dansmith | and casual users coming here to debug one thing | |
| 14:22:59 | dansmith | my bouncer gets un-authed often enough during netsplits, that I'm sure it would affect people with bouncers | |
| 14:23:15 | efried | okay, you're clearly opposed, I'll drop it for now. | |
| 14:24:59 | pooja_jadhav | efried: Hi | |
| 14:25:20 | efried | pooja_jadhav: Howdy. | |
| 14:25:54 | pooja_jadhav | efried: I need ur help in live migrate API testing. I am stuck at one point. | |
| 14:26:09 | dansmith | mriedem: I'll start up a patch for said node-removal cleanup | |
| 14:26:39 | openstack | Launchpad bug 1784874 in OpenStack Compute (nova) "ResourceTracker doesn't clean up compute_nodes or stats entries" [Low,Triaged] | |
| 14:26:39 | mriedem | dansmith: https://bugs.launchpad.net/nova/+bug/1784874 | |
| 14:26:44 | dansmith | mriedem: thanks | |
| 14:26:53 | efried | pooja_jadhav: I'm definitely not an expert in that realm. I'll do what I can - which will probably mean shunting you to mriedem and dansmith :) | |
| 14:27:15 | pooja_jadhav | efried: https://ask.openstack.org/en/question/62555/live-migrations-over-ssh-fail-from-nova-but-work-from-virsh/ (same happing with me right now) using virsh migrate i am able to migrate instance but using nova migrate API i can not. | |
| 14:28:32 | tssurya | mriedem: we don't | |
| 14:28:36 | sean-k-mooney | pooja_jadhav: have you exchaged passwordless ssh keys between all node for the use used in the migration | |
| 14:28:54 | sean-k-mooney | pooja_jadhav: e.g. nova for qemu+ssh://nova@compute-1/system | |
| 14:29:18 | pooja_jadhav | sean-k-mooney: yes, i have added password less ssh keys in authorize_keys file | |
| 14:29:30 | tssurya | we disabled that filter recently | |
| 14:29:38 | dansmith | tssurya: when you moved to ocata? | |
| 14:29:42 | dansmith | to/past | |
| 14:30:10 | sean-k-mooney | pooja_jadhav: and you can ssh fine with the nova users key betewen compute-1 and coumpute-2 | |
| 14:30:32 | pooja_jadhav | sean-k-mooney: not checked with nova users | |
| 14:31:18 | pooja_jadhav | i have checked by u qemu+ssh://nsername@hostname/system | |
| 14:32:33 | sean-k-mooney | pooja_jadhav: if the host key of every node is not in the known hosts for the relevent user then the propm to add the key will break the live migration | |
| 14:32:49 | openstackgerrit | Vishakha Agarwal proposed openstack/nova master: 'Updated_at' is NULL when show aggregate info https://review.openstack.org/580271 | |
| 14:33:02 | sean-k-mooney | pooja_jadhav: unless you turn of the host key checking that is. | |
| 14:34:44 | pooja_jadhav | sean-k-mooney: Can u tell me command how to check ssh by nova user from node 1 to node 2. | |
| 14:36:03 | openstackgerrit | Merged openstack/nova master: [placement] Use own set_middleware_defaults https://review.openstack.org/587183 | |
| 14:36:05 | sean-k-mooney | "sudo su -l nova" then "ssh nova@node-1" if that does not work you need to use ssh-copy-id to copy your key to node-1 | |
| 14:36:55 | sean-k-mooney | pooja_jadhav: ^ then just repeat for each node | |
| 14:38:15 | sean-k-mooney | pooja_jadhav: non node-1 you shoudl check by sshing to node-2 obvioulsy but in the general case you should ssh to all other node nodes from all nodes in your cloud | |
| 14:38:53 | pooja_jadhav | sean-k-mooney: I have already copied passwordless ssh keys still after hitting command "ssh nova@openstack02-VirtualBox" its asking me for password.. How come? I am really not understanding. | |
| 14:39:30 | sean-k-mooney | pooja_jadhav: did you copy your passwordless ssh key or nova's | |
| 14:40:53 | pooja_jadhav | sean-k-mooney: mine ssh key.. how to generate nova's ssh keys? I haven't done it before :( | |
| 14:41:07 | sean-k-mooney | you need to copy the key of whatever user nova-compute/libvirt are running as. | |
| 14:41:14 | sean-k-mooney | ssk-keygen | |
| 14:41:18 | sean-k-mooney | as the nova user | |
| 14:43:03 | openstackgerrit | Merged openstack/nova master: Ensure the order of AllocationRequestResources https://review.openstack.org/587700 | |
| 14:43:12 | openstackgerrit | Merged openstack/nova master: Fix the incorrect description and sample https://review.openstack.org/528180 | |
| 14:43:25 | sean-k-mooney | pooja_jadhav: by the way if you get that to work and you hit this error http://paste.openstack.org/show/726939/ for me it was caused because of iptables so i just flushed them with "sudo iptables -F" "sudo iptables -X". dont do that in production obviously but it works for devstack | |
| 14:44:16 | pooja_jadhav | 4)cat ~/.ssh/id_rsa.pub | |
| 14:44:16 | pooja_jadhav | sean-k-mooney: i have used this command to generate ssh keys : 3)ssh-keygen -t rsa -C "pooja.jadhav@nttdata.com" | |
| 14:45:35 | openstackgerrit | Vishakha Agarwal proposed openstack/nova master: 'Updated_at' is NULL when show aggregate info https://review.openstack.org/580271 | |
| 14:45:43 | sean-k-mooney | pooja_jadhav: that should work but the defaults will also work if you just hit enter 3-4 times when your the nova user | |
| 14:54:35 | tssurya | dansmith: after we moved to queens | |
| 14:54:44 | dansmith | okay | |
| 14:54:48 | tssurya | we only use custom resource_classes | |
| 14:55:06 | tssurya | for capabilities as well | |
| 15:05:40 | mriedem | bauzas: replied to you in https://review.openstack.org/#/c/584962/ | |
| 15:05:52 | lyarwood | mriedem: https://review.openstack.org/#/q/topic:bug/1784353 - nothing urgent, but if you have time this week would you mind taking a look at this BFV reschedule bug? | |
| 15:06:34 | bauzas | mriedem: well, I'm not really torn for your change | |
| 15:07:06 | mriedem | bauzas: you don't see the need for that cache? | |
| 15:07:12 | bauzas | mriedem: I mean, are we like calling a RPC API when we look at the bdms ? | |
| 15:07:18 | mriedem | yes | |
| 15:07:18 | mriedem | dude | |
| 15:07:35 | mriedem | we're getting all bdms for each instance to determine if it's volume-backed | |
| 15:07:44 | mriedem | that's a db query roundtrip through conductor | |
| 15:08:05 | bauzas | objects.BlockDeviceMappingList.get_by_instance_uuid() ? | |
| 15:08:06 | mriedem | and the bfv-ness of an instance isn't going to change | |
| 15:08:24 | bauzas | ah okay | |
| 15:08:27 | mriedem | yes https://github.com/openstack/nova/blob/master/nova/compute/utils.py#L215 | |
| 15:10:24 | bauzas | okay +2 then | |
| 15:11:33 | mriedem | thanks | |
| 15:11:49 | mriedem | lyarwood: sure | |
| 15:13:19 | lyarwood | mriedem: cheers, the actual bugfix is WIP as I'm not sure where the fix should land, any advice would be appreciated. | |
| 15:27:31 | gnuoy | Hi, I'm trying to understand this sentence from the cells layout doc: "The Neutron metadata API proxy should be global across all cells, and thus be configured as an API-level service with access to the [api_database]/connection information." | |
| 15:28:04 | openstackgerrit | Konstantinos Samaras-Tsakiris proposed openstack/nova master: Hide hypervisor id on windows guests https://review.openstack.org/579897 | |
| 15:28:10 | gnuoy | Is it honestly saying that the neutron metadata proxy needs access to the nova api db ? | |
| 15:28:39 | gnuoy | https://docs.openstack.org/nova/latest/user/cellsv2-layout.html#neutron-metadata-api-proxy | |
| 15:29:23 | openstackgerrit | Balazs Gibizer proposed openstack/nova master: Improve NeutronFixture and remove unncessary stubbing https://review.openstack.org/587412 | |
| 15:31:39 | kosamara | sean-k-mooney: updated https://review.openstack.org/#/c/579897 | |
| 15:42:40 | openstackgerrit | Chen proposed openstack/nova master: Make nova-manage db archive_delete_rows take --all-cells https://review.openstack.org/587858 | |
| 15:57:33 | sean-k-mooney | kosamara: +1 from me. its annoying that that is needed but ya the only other thing i can think of is to remove the os_type=windows from the glance image | |
| 15:58:23 | sean-k-mooney | dansmith: see the message form openstackgerrit above | |
| 15:58:41 | dansmith | sean-k-mooney: yeah I see :) | |
| 15:58:56 | sean-k-mooney | dansmith: i guess infra turned it on across the board do we want to keep it on? | |
| 15:59:07 | dansmith | not sure we have a choice | |
| 15:59:09 | kosamara | sean-k-mooney: thanks | |
| 15:59:18 | dansmith | I was just discussing with them | |
| 15:59:27 | dansmith | apparently the sniper doesn't work as well in all channels, for whatever reason, | |
| 15:59:29 | dansmith | but still, | |
| 15:59:56 | dansmith | like email, managing spam is just one of those things.. closing the door on an open community is a bad solution, IMHO, but whatever | |