| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2020-01-17 | |||
| 04:02:59 | dustinc | efried, gibi: ^ series ready for re-review, thanks!! | |
| 05:51:26 | openstackgerrit | Brin Zhang proposed openstack/nova master: Follow-up: Add delete_on_termination to volume-attach API https://review.opendev.org/680655 | |
| 08:44:54 | kiseok7 | Hello all, I would like to add a code on upstream; an option in [cinder] section to allow to attach only volumes in the specified AZ. how I can process it? it need a blue print? | |
| 08:46:52 | lyarwood | kiseok7: doesn't [cinder]/cross_az_attach=False provide this? | |
| 08:47:09 | lyarwood | kiseok7: or did you want use a specific cinder AZ | |
| 08:47:20 | lyarwood | want to* | |
| 08:56:28 | kiseok7 | lyarwood: yes, it provides a part of. with [cinder]/cross_az_attach=False, nova creates instance with a volume in same AZ. but in my case, I need to attach another volume to the instance in different AZ. | |
| 09:02:19 | lyarwood | kiseok7: kk, I thought the AZ stuff in cinder was just left over from when it was nova-volume in our tree tbh, it might be worth writing this up on the mailing list for a wider discussion. | |
| 09:04:24 | kiseok7 | lyarwood: thank for help . I will try it. | |
| 09:21:15 | bauzas | good morning Nova | |
| 10:03:36 | brinzhang | bauzas: good morning | |
| 10:04:01 | bauzas | brinzhang: morning ! | |
| 10:04:02 | brinzhang | nova has the nova-live-migration zuul fail, can you try to check? | |
| 10:04:57 | brinzhang | bauzas: that impact so many patch :( | |
| 10:05:20 | bauzas | brinzhang: orly? | |
| 10:05:31 | bauzas | I can look at the gate | |
| 10:05:58 | brinzhang | Yeah, cool~ | |
| 11:33:44 | admin0 | hi all .. if all 3 controllers crashed ( no db anymore, wiped out) and all I have is the compute node now ( with the disk file) how do I boot it up ? i can't seem to find the libvirt xml anywhere | |
| 11:37:22 | yoctozepto | admin0: libvirtd alive? could ask it via virsh | |
| 11:37:50 | admin0 | virsh list --all == blank | |
| 11:37:51 | yoctozepto | oh, you probably mean that node died too | |
| 11:38:41 | admin0 | i have to showcase how openstack saves data even when the 3 controllers are dead .so instealled openstack,booted up some instances, nuked the 3 controllers and rebooted the compute node | |
| 11:38:51 | admin0 | so all i see now is the disk files in nova | |
| 11:39:03 | admin0 | but not the .xml definitions | |
| 11:39:08 | yoctozepto | well, the definitions are in the database... | |
| 11:39:21 | yoctozepto | if you want to show just that data is where it is | |
| 11:39:43 | yoctozepto | could boot any other vm and attach this image | |
| 11:39:52 | sean-k-mooney | admin0: well nova does not exactly save data on the compute nodes but in the live case there will be libvirt domain xmls | |
| 11:39:54 | admin0 | but for the test-case, all 3 controllers and db is nuked and unavailable | |
| 11:40:15 | yoctozepto | admin0: yeah, but you said you have the disk files | |
| 11:40:21 | admin0 | i do have them | |
| 11:40:24 | yoctozepto | could boot any vm in there | |
| 11:40:28 | yoctozepto | on that compute host | |
| 11:40:36 | yoctozepto | if you really want to show it is there for some reason | |
| 11:40:39 | sean-k-mooney | so when the contler are gone you can still use virsh to start the instaces | |
| 11:40:52 | admin0 | the only way i see is install virt-manager on my machne, add the compute node, and then create a new instance pointing to this disk | |
| 11:40:53 | sean-k-mooney | by the way you proably need to use sudo virsh list --all | |
| 11:41:09 | yoctozepto | ^ and this | |
| 11:41:12 | sean-k-mooney | if you dont use sudo you wont see the system slice | |
| 11:41:33 | yoctozepto | sean-k-mooney: admin0 mentioned downing the compute | |
| 11:41:36 | admin0 | i am logged in as root, did sudo virsh list --all .. see nothing | |
| 11:41:43 | yoctozepto | so it's likely it's reallly not there | |
| 11:41:46 | admin0 | yes .. the compute node was also rebooted | |
| 11:41:50 | yoctozepto | yeah | |
| 11:41:59 | yoctozepto | then either restore controllers | |
| 11:42:07 | sean-k-mooney | ok in that case have you confirmed the libvirtd systemd service is running | |
| 11:42:19 | admin0 | so test case is "oops something bad happened" . controllers are nuked, db is gone and compute nodes are rebooted | |
| 11:42:30 | sean-k-mooney | no the domains will be there | |
| 11:42:38 | sean-k-mooney | it wont be affect by the reboot | |
| 11:42:39 | admin0 | which folder | |
| 11:43:06 | sean-k-mooney | ill have to check but first you should make sure the libvirt is running | |
| 11:43:22 | sean-k-mooney | do sudo systemctl status libvirtd | |
| 11:43:47 | admin0 | its active and running | |
| 11:44:08 | sean-k-mooney | and you have no domain definitions? | |
| 11:44:24 | sean-k-mooney | did you put your instnace dir on nfs? | |
| 11:44:43 | yoctozepto | sean-k-mooney is right, I just verified instance files are really persistent | |
| 11:44:47 | yoctozepto | sorry, I got confused | |
| 11:44:56 | admin0 | nope -- https://gist.github.com/a1git/d5d6c0cbb1e89ce6f7a7c5476b43f472 | |
| 11:45:04 | yoctozepto | my path is: /etc/libvirt/qemu/ | |
| 11:45:05 | admin0 | its local disk | |
| 11:45:08 | admin0 | oh | |
| 11:45:13 | admin0 | i was lookign into the wrong place | |
| 11:45:26 | admin0 | i see the instance definitions | |
| 11:45:36 | admin0 | but i cannot see them using sudo virsh list --all then ? | |
| 11:45:43 | yoctozepto | hmm, strange | |
| 11:45:58 | sean-k-mooney | how have you deployed openstack by the way | |
| 11:46:14 | sean-k-mooney | devstack? ooo? kolla? | |
| 11:47:00 | yoctozepto | (I have kolla and sean-k-mooney was right regarding behavior in there) | |
| 11:47:04 | admin0 | osa ( openstack ansible ) | |
| 11:47:12 | yoctozepto | ah, the third option | |
| 11:47:18 | admin0 | :D | |
| 11:47:20 | yoctozepto | or the fourth actually ;D | |
| 11:47:25 | yoctozepto | (counting devstack) | |
| 11:47:31 | admin0 | well, hav been trying to do kolla many times .. but still on osa | |
| 11:47:40 | yoctozepto | no problem | |
| 11:48:08 | sean-k-mooney | ok so you libvirt is running in an lxc container or on the host? | |
| 11:48:24 | admin0 | thing is if i ask some hard questions on kolla related to config or troubleshooting, there is no help on kolla but on osa its more in depth and instant .. which probably is because of rackspace | |
| 11:48:29 | admin0 | its on metal | |
| 11:48:56 | sean-k-mooney | ok can you try virsh --connect qemu:///system list | |
| 11:48:58 | yoctozepto | admin0: :O no help on kolla? how is that? | |
| 11:49:30 | sean-k-mooney | well i guess with --all | |
| 11:50:24 | sean-k-mooney | the xmls should be in /etc/libvirt/qemu | |
| 11:50:27 | yoctozepto | admin0: finally try: virsh define /etc/libvirt/qemu/that_one_file_you_missed_so_much.xml - maybe there was an error in there | |
| 11:51:09 | admin0 | error: invalid argument: could not find capabilities for arch=x86_64 -- wow .same server .. | |
| 11:51:44 | yoctozepto | see, now you got help from kolla, your argument is no longer valid (pun intended) | |
| 11:51:55 | yoctozepto | ;D | |
| 11:52:13 | yoctozepto | kidding aside, this really looks lolz | |
| 11:52:45 | sean-k-mooney | it looks like libvirt cannot find the x86_64 emulator | |
| 11:52:57 | admin0 | i will try kolla again .. won't doubt that .. but this is #nova channel :D | |
| 11:53:01 | yoctozepto | mhm, at least its config/definitions | |
| 11:53:22 | yoctozepto | admin0: yeah, I'm just teasing | |
| 11:53:36 | yoctozepto | though reboot does not get rid of those | |
| 11:53:38 | sean-k-mooney | well its complaining that virsh capabilities is not working | |
| 11:54:11 | sean-k-mooney | no a reboot would not cause this and nither would nuking the contolers | |
| 11:54:26 | sean-k-mooney | this host has been broken by something else that is unrelated | |
| 11:54:57 | yoctozepto | +1, I know the drill | |
| 11:54:59 | admin0 | in virsh capabilities i do see <arch>x86_64</arch> reported with the flags | |
| 11:55:05 | yoctozepto | some issues popping up only after reboot | |
| 11:55:20 | yoctozepto | as in "cleanup gone wrong and discovered weeks later" | |
| 11:55:40 | yoctozepto | odd | |