| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2021-03-15 | |||
| 10:08:47 | openstack | bug 1917592 in OpenStack Compute (nova) "Missed 'accel_uuids' when we the 'shelved_offload_time' time out in shelving instance periodic task" [Medium,In progress] https://launchpad.net/bugs/1917592 - Assigned to Brin Zhang (zhangbailin) | |
| 10:09:03 | bauzas | brinzhang: good afternoon | |
| 10:09:13 | bauzas | (I have to leave in 5 mins for getting my children from school) | |
| 10:10:00 | brinzhang | bauzas: ack, dont worry | |
| 10:10:34 | brinzhang | about your concern, does it need to add an cyborg get multiple arqs apis? | |
| 10:15:13 | bauzas | brinzhang: well, the point is that we call the Cyborg API for each of the instance | |
| 10:15:49 | bauzas | but my -1 was more about the L9480 | |
| 10:17:35 | brinzhang | bauzas: ack, not in a hurry, thanks | |
| 10:18:50 | brinzhang | gibi: do you have some suggestion? bauzas's concern is the cyborgclient may get many times if there are some bound accel:device_profile instance | |
| 10:19:16 | brinzhang | s/some/any/ | |
| 13:17:25 | lyarwood | elod / bauzas / melwitt ; https://review.opendev.org/c/openstack/nova/+/780287 - final stable/queens ceph fix should be good to go btw | |
| 13:47:18 | sean-k-mooney | gibi: hi yep its an issue ill fix that and convert it to using the info cache quickly otherwise are you ok with the approch | |
| 13:48:21 | sean-k-mooney | im technically off this week but im going to intermitenly check the status of the vdpa patches until they are all merged but expect delays since i will only be checking evey few hours | |
| 13:49:32 | gibi | sean-k-mooney: I'm OK with the approach | |
| 14:27:00 | openstackgerrit | Takashi Kajinami proposed openstack/osc-placement master: Add openstackclient-plugin-jobs https://review.opendev.org/c/openstack/osc-placement/+/780598 | |
| 14:30:15 | bauzas | dansmith: I got hit by Zuul when changing the pre-live-migration method, so I'll try to not accept 5.0 | |
| 14:32:36 | k-s-dean | Hi would someone be able to help me. | |
| 14:32:51 | k-s-dean | How does nova notify neutron / designate of VM details ? | |
| 14:38:44 | sean-k-mooney | via a port update. for neutron it updates teh device_id with the instance uuid in port binding prodmently and designate reads the info from the neutron port | |
| 14:39:01 | sean-k-mooney | nova does not directly interact with designate | |
| 14:43:13 | k-s-dean | sean thanks for answering I'm getting ignore in all the other channels, I'm hitting an issue where the fixed IPs are being put in DNS. I've been asking around but cant get to the bottom of it. It worked in stein. | |
| 14:43:52 | sean-k-mooney | i think that is expected | |
| 14:44:41 | sean-k-mooney | when using designate the fixed ips set on the neutron port are registred in dns so that vms can directlly ssh to other vms via there host/dns name | |
| 14:44:42 | k-s-dean | In the neutron documentation it says that the VMs name gets appended on to the dns domain on port update events. | |
| 14:44:56 | k-s-dean | specifically for floating IPs | |
| 14:45:40 | k-s-dean | something has obviously changed since I last installed openstack. | |
| 14:46:19 | sean-k-mooney | i was always under the impression that both fix and floating ips were always regeistred | |
| 14:46:30 | sean-k-mooney | though the dns name might be different for each | |
| 14:46:50 | k-s-dean | The floating IP is being registered but like so | |
| 14:47:05 | k-s-dean | 10-30-0-205.os.example.com. | A | 10.30.0.205 | |
| 14:47:27 | k-s-dean | I swear that in stein the VMs name was added to that DNS name | |
| 14:47:49 | k-s-dean | https://docs.openstack.org/ocata/networking-guide/config-dns-int.html#config-dns-int-dns-resolution | |
| 14:47:54 | k-s-dean | these docs are wrong then. | |
| 14:49:42 | sean-k-mooney | i have 172-20-5-191.cloud.seanmooney.info. cyborg-1.cloud.seanmooney.info. cyborg-1.sean.cloud.seanmooney.info. | |
| 14:49:46 | sean-k-mooney | all for the same vm | |
| 14:50:08 | k-s-dean | are those assigned to the floating IP or fixed IP | |
| 14:50:13 | sean-k-mooney | fixed | |
| 14:50:38 | k-s-dean | is that for internal DNS resolution then ? | |
| 14:50:44 | k-s-dean | not external | |
| 14:51:02 | k-s-dean | because I thought dns mask needed to be setup for that | |
| 14:51:16 | sean-k-mooney | well this is my home cloud and all the ips in my neturon subnet allocation pool are routable | |
| 14:51:32 | sean-k-mooney | my vms only get public ipv6 address | |
| 14:51:45 | k-s-dean | Yeah, so thats where I think there has been a major change. | |
| 14:52:02 | k-s-dean | in the neutron docs. Use case 2: Floating IPs are published with associated port DNS attributes | |
| 14:52:26 | k-s-dean | you can see at the end the floating IP is assigned the VMS name. | |
| 14:52:42 | k-s-dean | I can work around this by using a flat provider network, | |
| 14:52:55 | k-s-dean | and attach the VMs directly to the network. | |
| 14:52:58 | sean-k-mooney | well floating ips are named by the enduser when you create them | |
| 14:53:08 | sean-k-mooney | nova does not create floating ips fro you | |
| 14:53:47 | k-s-dean | ok i thought that when you attach a floating IP to an instance, neutron would notify nova of the port update and nova would notify designate of the VMS name | |
| 14:54:00 | sean-k-mooney | no | |
| 14:54:36 | sean-k-mooney | to attach a floating ip you call the nova api but we do not call designate. | |
| 14:54:49 | sean-k-mooney | its possible that designate is listing to nova notifcation bus | |
| 14:55:06 | k-s-dean | it is. | |
| 14:55:22 | k-s-dean | the way this works has obviously changed, since stein | |
| 14:55:22 | sean-k-mooney | im not sure it does any more | |
| 14:55:24 | sean-k-mooney | it used too | |
| 14:55:38 | sean-k-mooney | but any change in this behavior is on the designate/neutron side | |
| 14:55:50 | k-s-dean | if the expected workflow is that the dns name for floating IPs is specified by the user then I'll have to live with that. | |
| 14:56:36 | k-s-dean | on my last openstack installation. it worked as specified in Use case 2: Floating IPs are published with associated port DNS attributes | |
| 14:56:42 | k-s-dean | in the neutron docs i posted above. | |
| 14:56:42 | openstackgerrit | Merged openstack/nova master: libvirt: Use firmware metadata files to configure instance https://review.opendev.org/c/openstack/nova/+/779304 | |
| 14:58:07 | sean-k-mooney | well as i said that behavior before was not provided by nova it was provide by designate | |
| 14:58:31 | sean-k-mooney | it might still be possibel to do but you would have to look at what was change in designate and if its configurable | |
| 14:58:53 | k-s-dean | ok thanks sean, much appreciated | |
| 14:59:07 | k-s-dean | I've been going round in circles because this use to work before. | |
| 15:00:12 | sean-k-mooney | looking at my own installl designate has stopped registering dns entires entirely which is nice of it. | |
| 15:00:31 | k-s-dean | wow ok. | |
| 15:01:11 | sean-k-mooney | i will be reinsitalling my home cloud in the next month or so and designate as much as i like it is one of the service im trying to desicied if ill keep | |
| 15:01:14 | k-s-dean | I basically have to disable the nova:fixed handler in designate-sink so that it does not register the fixed IPs | |
| 15:01:28 | k-s-dean | What would you use instead ? | |
| 15:01:56 | sean-k-mooney | for my home install just updating my cloudflare dns entires by hand | |
| 15:02:07 | k-s-dean | I'm open to suggestions. Its just a nice to have if I can register VM names in DNS. I dont have to faf around with my internal firewall. | |
| 15:02:13 | sean-k-mooney | which would be a regression but i could live with it | |
| 15:02:29 | sean-k-mooney | k-s-dean: yep it really is nice to have | |
| 15:03:20 | k-s-dean | oh well. I plan on using terraform for spinning up VMs so I guess i'll manually have to specify the dns name each time. | |
| 15:03:36 | k-s-dean | or I switch to a flat network completely. then it works as I expect. | |
| 15:04:37 | k-s-dean | I'm tempted to run, Stein containers in kolla to see if that works. but i know different versions aren't supported between release | |
| 15:04:40 | sean-k-mooney | in my case i think i just have a bug in the verion i have deployed as it use to work fine | |
| 15:04:59 | sean-k-mooney | im also debating about removing https://docs.openstack.org/neutron/latest/admin/config-bgp-dynamic-routing.html | |
| 15:05:17 | k-s-dean | is your cloud exposed directly to the internet ? via your ISP | |
| 15:05:40 | sean-k-mooney | not quite | |
| 15:05:46 | stephenfin | gibi: bauzas: lyarwood: Despite appearances, sean-k-mooney is on PTO this week so I was going to rework https://review.opendev.org/c/openstack/nova/+/780333/ I think it's important enough to warrant inclusion | |
| 15:05:49 | stephenfin | Any issues with me doing that? | |
| 15:06:21 | stephenfin | Just waiting for https://review.opendev.org/c/openstack/nova/+/770532/ to (hopefully) merge first since the rest of the series is in merge conflict too | |
| 15:06:33 | sean-k-mooney | k-s-dean:i have a ipv6 tunnel from hurican eletric which i then have a /48 from which i can allocate to vms | |
| 15:07:11 | lyarwood | stephenfin: none, should we ban sean-k-mooney ? /s | |
| 15:07:32 | stephenfin | kick them kick them kick them... | |
| 15:07:38 | sean-k-mooney | hehe im finishin ga release note update and ill be going away then | |
| 15:07:58 | sean-k-mooney | i need to charge the battery in my car... | |
| 15:08:08 | lyarwood | where did I put that ban hammer | |
| 15:08:11 | sean-k-mooney | turns out you should drive it more then once every few months | |
| 15:08:14 | lyarwood | haha | |
| 15:08:17 | k-s-dean | Sorry, I'm taking up your time. I'll shoot off and live with the limitations. | |
| 15:08:17 | lyarwood | yeah | |
| 15:08:34 | sean-k-mooney | k-s-dean: no worres sorry i could not help more | |
| 15:09:46 | k-s-dean | No problem thanks for helping me out. Better to get an answer from someone who is actively working on openstack. then I can go tell my boss that we will have to live with it rather than expecting it to work. | |
| 15:11:35 | sean-k-mooney | k-s-dean: if you dont get a responce on the designate channel try emailing the mailing list. | |
| 15:11:56 | sean-k-mooney | i use designate but i dont follow its developemnt so there might be a simple fix i dont know about | |
| 15:13:07 | k-s-dean | ok will do. I'm gonna try build a designate stein container push that to my environment see if it breaks. | |