| openstackgerrit | Merged openstack/senlin-tempest-plugin master: Remove check for content-length on delete https://review.opendev.org/688521 | 00:00 |
|---|---|---|
| openstackgerrit | Merged openstack/senlin master: [train][goal] Define new 'senlin-tempest-api-ipv6-only' job in gate https://review.opendev.org/676910 | 01:49 |
| openstackgerrit | Erik Olof Gunnar Andersson proposed openstack/senlin master: Enable Apache by default https://review.opendev.org/688253 | 01:59 |
| openstackgerrit | Erik Olof Gunnar Andersson proposed openstack/senlin master: Split engine service into three services https://review.opendev.org/688784 | 02:04 |
| openstackgerrit | Erik Olof Gunnar Andersson proposed openstack/senlin master: Enable Apache by default https://review.opendev.org/688253 | 18:28 |
| rm_work | dtruong: do you know if Receivers can be disabled somehow, or does it matter if we disable other bits? | 19:20 |
| rm_work | i don't see anything about updating existing ones, or any status field, so guessing not... | 19:27 |
| rm_work | but they just won't do anything if the cluster itself is size 0, or policies are disabled, right? | 19:28 |
| dtruong | rm_work There is no way to disable receivers. | 20:51 |
| dtruong | Receivers are just webhooks to do certain cluster operations. | 20:51 |
| dtruong | It will still respect your cluster properties (like min and max size). | 20:52 |
| dtruong | Since the disable sets those to 0, calling the receiver for scale-out will just return an error saying that it would violate the size constraints. | 20:53 |
| dtruong | ^ By disable I mean the ospurge cluster disable | 20:54 |
| rm_work | right | 21:06 |
| rm_work | kk | 21:06 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!