Wednesday, 2019-04-24

*** gmann_afk is now known as gmann02:16
*** licanwei has quit IRC02:57
*** licanwei has joined #openstack-watcher05:20
*** d34dh0r53 has quit IRC06:22
*** josecastroleon has joined #openstack-watcher07:52
*** d34dh0r53 has joined #openstack-watcher09:46
*** gmann has quit IRC09:54
*** gmann has joined #openstack-watcher09:56
*** gmann has quit IRC10:44
*** josecastroleon has quit IRC12:35
*** irclogbot_0 has quit IRC12:55
*** irclogbot_1 has joined #openstack-watcher12:56
*** altlogbot_2 has quit IRC12:57
*** altlogbot_2 has joined #openstack-watcher12:59
*** gmann has joined #openstack-watcher13:51
*** altlogbot_2 has quit IRC16:09
*** altlogbot_0 has joined #openstack-watcher16:13
*** ianychoi has quit IRC16:14
*** ianychoi has joined #openstack-watcher16:15
*** altlogbot_0 has quit IRC16:43
*** altlogbot_1 has joined #openstack-watcher16:45
*** altlogbot_1 has quit IRC16:53
*** altlogbot_1 has joined #openstack-watcher16:57
openstackgerritMerged openstack/watcher master: Drop use of
*** mriedem has joined #openstack-watcher18:54
mriedemrandom question, but has anyone talked about leveraging the placement service within watcher? maybe as a way to supersede some of the stuff the nova scheduler does with placement? i don't know much about watcher, but i assume it has to keep track of some kind of inventory of resources and consumers of resources based on things in nova (either by polling the compute API and/or listening for nova's notifications)18:55
*** openstackgerrit has quit IRC18:57
*** mriedem has left #openstack-watcher21:14

Generated by 2.15.3 by Marius Gedminas - find it at!