Friday, 2018-03-09

*** k0da has quit IRC00:02
*** esberglu has joined #openstack-powervm03:02
*** esberglu has quit IRC04:10
*** chhagarw has joined #openstack-powervm04:31
*** chhavi__ has joined #openstack-powervm04:31
*** k0da has joined #openstack-powervm08:28
*** apearson has joined #openstack-powervm13:29
*** k0da has quit IRC13:35
*** k0da has joined #openstack-powervm13:41
*** AlexeyAbashkin has joined #openstack-powervm13:56
*** tjakobs has joined #openstack-powervm13:58
*** edmondsw has joined #openstack-powervm13:59
*** AlexeyAbashkin has quit IRC14:01
*** AlexeyAbashkin has joined #openstack-powervm14:03
*** AlexeyAbashkin has quit IRC14:07
*** AlexeyAbashkin has joined #openstack-powervm14:43
*** AlexeyAbashkin has quit IRC14:47
*** AlexeyAbashkin has joined #openstack-powervm14:51
*** esberglu has joined #openstack-powervm15:37
*** AlexeyAbashkin has quit IRC15:45
catmandohey all16:13
catmandois there a doc that describes powervm's scheduler_hints? i only know of "host_aggregate_id"16:14
*** k0da has quit IRC16:31
edmondswcatmando this is the best I could find: https://www.ibm.com/developerworks/community/blogs/ibmsyssw/entry/real_world_applications_with_ibm_platform_resource_scheduler_part_ii?lang=en17:43
edmondswbut I would warn you away from that stuff if possible... look for an OpenStack community way of doing what you want to do, so it will be portable and more stable across upgrades17:44
edmondswe.g. instead of host_aggregate_id I think you would specify availability zone17:47
edmondswhttps://docs.openstack.org/nova/pike/admin/availability-zones.html17:47
*** k0da has joined #openstack-powervm18:40
*** chhavi__ has quit IRC19:02
*** chhagarw has quit IRC19:02
*** k0da has quit IRC19:03
edmondswesberglu are you updating prep_devstack since https://review.openstack.org/#/c/550499/ merged?19:10
edmondswand do you intend to try backporting to pike, or going to modify/remove the TODO?19:10
esbergluedmondsw: Yeah I will update19:11
esbergluPike backport https://review.openstack.org/#/c/550866/19:11
edmondswtx19:11
esbergluedmondsw: 638119:15
edmondsw+2 tx19:16
edmondswesberglu CI failed with "Error: unable to connect to node 'rabbit@powervm-ci-powervm-devstacked-77270': nodedown"19:41
edmondswyou restarting or something?19:41
esbergluedmondsw: Already looking into it19:42
esbergluSeems to be due to https://review.openstack.org/#/c/539991/19:43
edmondswesberglu looks like it still checks for the hostname, but no longer checks for 127.0.0.1... but that error wasn't using 127.0.0.1... was something else needing that, e.g. to start rabbitmq?19:51
edmondswcurious what our /etc/hosts looks like now :)19:52
esberglu6382 for CI fix20:39
*** k0da has joined #openstack-powervm21:07
esbergluPowerVM CI will be down for the afternoon for a redeploy to pick up a fix21:51
*** tjakobs has quit IRC22:03
*** edmondsw has quit IRC22:27
*** AndyWojo has quit IRC22:28
*** AndyWojo has joined #openstack-powervm22:28
*** esberglu has quit IRC22:53
*** apearson has quit IRC23:17
*** edmondsw has joined #openstack-powervm23:49
*** edmondsw has quit IRC23:54

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!