Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2021-06-16
11:21:48 sean-k-mooney it lest you know if it will fail but no need to recheck it
11:59:15 admin1 where is the live_migration_downtime defined ?
11:59:19 admin1 is it on kvm or in nova ?
12:01:15 sean-k-mooney admin1: nova has options that we pass to libvirt which then modulates the qemu downtime
12:01:37 sean-k-mooney admin1: https://docs.openstack.org/nova/latest/configuration/config.html#libvirt.live_migration_downtime
12:01:56 sean-k-mooney admin1: nova is not direcly involved in managing the vm during the livemigration
12:02:15 sean-k-mooney we invoke libvirt wiht a set of parmaters and then wait for ti to complete
12:04:38 sean-k-mooney melwitt: i think this is all you need to fix in the backports for bionic by the way https://review.opendev.org/c/openstack/nova/+/795433/1/roles/run-evacuate-hook/tasks/main.yaml#44
12:05:12 sean-k-mooney well and lines 67-69
12:05:53 sean-k-mooney the version of libvirt in bionic does not support socket activation so we just need to remove the socket lines
12:11:22 admin1 sean-k-mooney, so i just need to add those lines in nova.conf, restart the compute service ( systemctl ) and thats it ?
12:11:51 admin1 are those lines only needed in the actual compute nodes, or in the whole cluster ( nova scheduler, api etc ) ?
12:12:34 sean-k-mooney they are used on the source compute i think
12:12:45 sean-k-mooney so all the comptues that you want to tune
12:12:50 admin1 do they go under libvirt or under default ?
12:13:02 sean-k-mooney but i do not think they are used by any other services
12:13:11 sean-k-mooney they are in the libvirt section
12:13:12 admin1 libvirt. ( dot ) means its under libvirt i guess
12:13:20 sean-k-mooney yes
12:13:23 sean-k-mooney it does
12:13:50 sean-k-mooney so update the configs on the computes restart compute services and it will take effect
12:20:44 admin1 does these value make sense: live_migration_downtime: 5000 # ( default 500) && live_migration_downtime_steps: 20 # default (10) && live_migration_completion_timeout: 8000 # (default 800)
12:21:56 admin1 don't want to corrupt the instance , ram etc
12:28:22 opendevreview Lee Yarwood proposed openstack/nova stable/train: libvirt: Set driver_iommu when attaching virtio devices to SEV instance https://review.opendev.org/c/openstack/nova/+/796642
13:13:56 opendevreview Stephen Finucane proposed openstack/nova stable/train: Reproduce bug 1897528 https://review.opendev.org/c/openstack/nova/+/792116
13:13:57 opendevreview Stephen Finucane proposed openstack/nova stable/train: Ignore PCI devices with 32bit domain https://review.opendev.org/c/openstack/nova/+/792117
13:40:51 ozzzo The topic in this channel is a bit unfriendly, and gives bad advice. Nobody is answering questions in #openstack, and this is the correct place to ask Nova questions. Can we change the topic?
14:08:54 opendevreview Lee Yarwood proposed openstack/nova master: Add check job for FIPS https://review.opendev.org/c/openstack/nova/+/790519
14:21:02 sean-k-mooney ozzzo: the topic is intentional
14:21:27 ozzzo i don't doubt that, but it is still bad advice
14:21:29 sean-k-mooney in the past we have had some user be quite unresonable and demand support form upstream for there sepcific thing
14:21:48 lyarwood stephenfin / gibi ; https://review.opendev.org/c/openstack/nova/+/796523 easy review if you have time
14:22:08 sean-k-mooney ozzzo: #openstack is inteded to be for general quetions
14:22:11 ozzzo it's true that there are idiots on irc, but asking questions in #openstack is a waste of time because nobody who knows any answers is watching there
14:22:17 sean-k-mooney but ill admign i dont tend to have it open
14:22:23 ozzzo I try to help out sometimes but I don't know much
14:22:57 sean-k-mooney i do not monitor it i used to have it open by default but i only responded if i was pingged
14:23:06 sean-k-mooney i shoudl set back up my default chanlles list after the mvoe
14:23:15 sean-k-mooney ozzzo: did you have a question by the way
14:23:52 sean-k-mooney ozzzo: we proably could just remove for support bit
14:23:58 ozzzo I don't, but the other day someone was fruitlessly asking questions in #openstack, and I sent him here, but the message scared him off
14:24:01 sean-k-mooney and just not this is for development mainly
14:24:24 ozzzo *nova questions
14:25:15 opendevreview Lee Yarwood proposed openstack/nova master: tests: Allow bindep and test-setup.sh to run successfully on RHEL https://review.opendev.org/c/openstack/nova/+/796428
14:25:50 sean-k-mooney its hard to express what type of questions are ok here in a way that is aprochable to new commer but also provides a safty net for peopel to fall back on when peopel are lookign for upstream to provide support for free
14:26:21 sean-k-mooney you know that most of use are happy to help, at least to a point
14:31:55 opendevreview Lee Yarwood proposed openstack/nova master: DNM - Test bindep and test-setup.sh changes against centos8 https://review.opendev.org/c/openstack/nova/+/796684
14:32:06 lyarwood stephenfin: ^
14:43:09 ganso lyarwood, melwitt: thanks for the +2+W on the wallaby one! if you could please take a look at the victoria backport now when you have a minute: https://review.opendev.org/c/openstack/nova/+/795542
14:43:49 ganso bauzas also as reviewed the original patch ^
14:43:54 ganso thanks in advance
14:44:10 bauzas ganso: ack, opening a new tab
14:52:57 opendevreview Stephen Finucane proposed openstack/nova master: Move 'check-cherry-picks' test to gate, n-v check https://review.opendev.org/c/openstack/nova/+/796626
14:53:36 stephenfin lyarwood: sean-k-mooney: ^
14:54:29 lyarwood stephenfin: awesome thanks
14:56:17 sean-k-mooney looks good to me
14:56:41 sean-k-mooney we had the env varable beforefore for downstream?
14:56:56 sean-k-mooney or was it there for another reason
14:57:13 sean-k-mooney having it be a different tox enve removes the need for it but just wondering
14:57:40 lyarwood downstream
14:58:14 sean-k-mooney ack, thats what i tought but was not sure
14:58:19 lyarwood but I never got around to replacing the original hackaround with it
14:58:30 lyarwood the original being to truncate the file
14:58:38 lyarwood \o/
15:07:25 opendevreview Merged openstack/nova master: tests: Merge flavor tests https://review.opendev.org/c/openstack/nova/+/783662
15:08:19 opendevreview Merged openstack/nova master: tests: Remove useless mocks https://review.opendev.org/c/openstack/nova/+/778730
15:10:20 admin1 if vms ( backed up by ceph) fail to live migrate, is a pause + migrate enough .. or they need to be shutdown and then migrated ?
15:11:14 admin1 i used this setting: live_migration_downtime: 10000 ; live_migration_downtime_steps: 20 ; live_migration_downtime_delay: 100 ; live_migration_completion_timeout: 15000
15:11:27 admin1 which helped 8 stuck instances to migrate .. 2 fail to migrate no matter what
15:41:20 opendevreview Lee Yarwood proposed openstack/nova master: tests: Allow bindep and test-setup.sh to run on EL distros https://review.opendev.org/c/openstack/nova/+/796428
15:41:21 opendevreview Lee Yarwood proposed openstack/nova master: DNM - Test bindep and test-setup.sh changes against centos8 https://review.opendev.org/c/openstack/nova/+/796684
15:49:01 opendevreview Merged openstack/nova master: Allow X-OpenStack-Nova-API-Version header in CORS https://review.opendev.org/c/openstack/nova/+/796319
15:49:51 opendevreview Merged openstack/nova master: tests: Remove duplicate policy tests https://review.opendev.org/c/openstack/nova/+/778731
15:50:11 melwitt ganso: ack will do
15:51:50 sean-k-mooney admin1: you can jsut do a cloud migrate
15:51:56 sean-k-mooney no need to pause
15:52:02 melwitt sean-k-mooney: ack thanks for the hint
15:52:08 sean-k-mooney or you can do a live migrate with a force complete call
15:52:19 sean-k-mooney force-complete will pause the vm
15:52:40 admin1 oh .. ok
15:53:34 admin1 openstack server migrate --help .. there is no such parameter ( force-complete)
15:54:09 sean-k-mooney https://docs.openstack.org/api-ref/compute/?expanded=force-migration-complete-action-force-complete-action-detail#force-migration-complete-action-force-complete-action
15:55:16 sean-k-mooney "openstack server migration force complete" is the comand
15:55:54 sean-k-mooney sean@p50:~$ openstack help server migration force complete
15:55:56 sean-k-mooney usage: openstack server migration force complete [-h] <server> <migration>
15:55:58 sean-k-mooney Force an ongoing live migration to complete. This command requires ``--os-compute-api-version`` 2.22 or greater.
15:56:00 sean-k-mooney positional arguments:
15:56:02 sean-k-mooney <server> Server (name or ID)
15:56:04 sean-k-mooney <migration> Migration (ID)
15:56:06 sean-k-mooney so basically you have to start the live migration
15:56:22 sean-k-mooney then you can get the migration id and then force the completeion of the live migation
15:57:41 sean-k-mooney melwitt: sorry dont rememebr the context of that but if the hint? helpped im glad
15:57:57 sean-k-mooney oh
15:58:07 sean-k-mooney melwitt: the socket activation?
15:58:23 melwitt sean-k-mooney: haha yeah the fixing for bionic thing
16:00:09 melwitt stephenfin, lyarwood, bauzas: I'm meh about approving older branches before the newer one merges, I don't think it solves the ping problem. in my case it's just I don't always remember to review all the older versions and I don't often like to do them all at the same time anyway
16:01:11 stephenfin I figured it would solve the ping problem, or at least significantly reduce it
16:01:35 stephenfin in theory, if all branches were approved, one could get them merged by a simple recheck
16:05:00 opendevreview Stephen Finucane proposed openstack/nova master: tests: Speed up 'servers' API tests https://review.opendev.org/c/openstack/nova/+/778732
16:05:56 melwitt yeah. I guess one potential thing that could happen is if the author/rechecker doesn't realize they can't merge out of order and they go on a recheck loop in the wrong order. I have seen that before anyway but I'd imagine it's more tempting when you see the shiny +W on there

Earlier   Later