Wednesday, 2018-03-28

*** openstack has joined #openstack-powervm00:15
*** ChanServ sets mode: +o openstack00:15
*** AlexeyAbashkin has joined #openstack-powervm02:12
*** AlexeyAbashkin has quit IRC02:16
*** arunman has joined #openstack-powervm04:39
*** arunman has quit IRC04:59
*** chhagarw has joined #openstack-powervm05:03
*** arunman has joined #openstack-powervm05:05
*** chhagarw has quit IRC05:12
*** k0da has joined #openstack-powervm05:55
*** k0da has quit IRC06:06
*** k0da has joined #openstack-powervm07:43
*** AlexeyAbashkin has joined #openstack-powervm08:00
*** efried has quit IRC11:47
*** efried has joined #openstack-powervm11:48
*** edmondsw has joined #openstack-powervm12:06
*** chhagarw has joined #openstack-powervm12:08
*** arunmani_ has joined #openstack-powervm13:54
*** arunman has quit IRC13:56
*** efried has quit IRC13:56
*** efried has joined #openstack-powervm13:56
*** tjakobs has joined #openstack-powervm13:57
*** esberglu has joined #openstack-powervm14:05
*** efried has quit IRC14:51
*** efried has joined #openstack-powervm14:52
*** tjakobs has quit IRC15:02
*** tjakobs has joined #openstack-powervm15:03
esbergluedmondsw: For cold migration CI, we are limited by the fact that the hosts have to be in the same ssp cluster15:26
esbergluAnd currently each neo has it's own ssp cluster15:26
*** k0da has quit IRC15:27
esbergluThere's probably a way to force them to be on the same neo though15:28
esbergluBut good news is that it was easy enough to get a multinode setup running within the CI env and our base tempest test suite is mostly passing15:29
edmondswesberglu you lost me with that force comment...15:43
edmondswI think you'd have to setup the SSP cluster to span both neos15:44
esbergluFor multinode we would spawn 2 instances15:44
esbergluFor compute nodes15:44
esbergluIf they both land on the same neo cold mig will work15:45
esbergluIf they don't (which is far more likely), cold mig won't work15:45
esbergluSo I'll need to find some way to ensure that both computes are running on the same neo15:45
esbergluOr change how we do our SSP clusters15:45
edmondswinstances = VMs where we run the devstack AIO and remote pypowervm?15:45
esbergluedmondsw: Yeah15:46
edmondswok, I think I'm following15:46
esbergluBut for multinode15:46
edmondswshouldn't we be able to force the 2nd instance onto the same host as the first15:46
esbergluinstances = VMs where we run devstack compute and remote pypowervm15:46
esbergluedmondsw: I'm hoping so15:47
edmondswwe could either do a targeted deployment of the 2nd instance, or use an affinity group15:47
edmondswtargeted deployment would be by specifying availability_zone as ZONE:HOST on the create server API call15:50
edmondswe.g. nova:neo115:51
*** tjakobs has quit IRC16:09
*** tjakobs has joined #openstack-powervm16:10
*** AlexeyAbashkin has quit IRC17:08
*** arunmani_ has quit IRC17:42
*** k0da has joined #openstack-powervm17:44
*** k0da has quit IRC18:06
*** chhagarw has quit IRC18:16
*** k0da has joined #openstack-powervm18:49
*** AlexeyAbashkin has joined #openstack-powervm18:54
*** AlexeyAbashkin has quit IRC18:59
*** esberglu has quit IRC19:25
*** esberglu has joined #openstack-powervm19:26
*** esberglu has quit IRC19:31
*** esberglu has joined #openstack-powervm19:38
*** edmondsw has quit IRC21:43
*** tjakobs has quit IRC21:44
-openstackstatus- NOTICE: the zuul web dashboard will experience a short downtime as we roll out some changes - no job execution should be affected21:52
efriedesberglu: yt?22:15
esbergluefried: Assuming this is about mriedem in nova22:17
efriedesberglu: Done.22:30
*** esberglu has quit IRC22:32
*** k0da has quit IRC23:19
-openstackstatus- NOTICE: Zuul has been restarted to update to the latest code; existing changes have been re-enqueued, you may need to recheck changes uploaded in the past 10 minutes23:59

Generated by 2.15.3 by Marius Gedminas - find it at!