[05:16] <thetrav> how do I set my MaaS nodes to automatically execute a script on start up?
[05:17] <thetrav> this is the nodes managed by MaaS, not the region/cluster controllers
[06:20] <mup> Bug #1252768 changed: removing (including with --purge) fails on pg script <MAAS:New> <maas (Ubuntu):New> <https://launchpad.net/bugs/1252768>
[06:32] <mup> Bug #1252768 was opened: removing (including with --purge) fails on pg script <MAAS:New> <maas (Ubuntu):New> <https://launchpad.net/bugs/1252768>
[06:38] <mup> Bug #1252768 changed: removing (including with --purge) fails on pg script <MAAS:New> <maas (Ubuntu):New> <https://launchpad.net/bugs/1252768>
[07:14] <mup> Bug #1440994 was opened: maas api "device read <hostname>" returns HTML 404  <api> <juju-net> <robustness> <MAAS:New> <https://launchpad.net/bugs/1440994>
[07:14] <mup> Bug #1440996 was opened: maas api "device create" exists but is not documented. <api> <doc> <juju-net> <MAAS:New> <https://launchpad.net/bugs/1440996>
[07:44] <mup> Bug #1440998 was opened: maas api "device update <id>" requires setting parent= in addition to hostname=, but it's not documented as required <api> <doc> <juju-net> <MAAS:New> <https://launchpad.net/bugs/1440998>
[07:44] <mup> Bug #1441002 was opened: maas api "device set-sticky-ip-address" fails with "500: 'bool' object has not attribute 'uuid'". <api> <juju-net> <robustness> <MAAS:New> <https://launchpad.net/bugs/1441002>
[08:06] <mup> Bug #1440894 changed: get_effective_power_parameters() - exceptions.AttributeError: 'unicode' object has no attribute 'copy' <MAAS:New> <https://launchpad.net/bugs/1440894>
[08:06] <mup> Bug #1441013 was opened: maas api "device claim-sticky-ip-address" does not allocate an address when there are existing IPs assigned <api> <juju-net> <robustness> <MAAS:New> <https://launchpad.net/bugs/1441013>
[08:18] <mup> Bug #1441018 was opened: maas api "device release-sticky-ip-address" could use a better error message <api> <confusing-ui> <doc> <juju-net> <MAAS:New> <https://launchpad.net/bugs/1441018>
[08:30] <dimitern> rvba, hey there
[08:30] <rvba> \o dimitern
[08:30] <dimitern> rvba, as you've probably noticed I've tested the 1.8-alpha10 devices support and filed a bunch of bugs
[08:30] <rvba> dimitern: yes, going through them now…
[08:31] <dimitern> rvba, cheers
[08:31] <rvba> Thanks dimitern!
[08:31] <dimitern> rvba, as a general feedback - it looks much more stable than initially :)
[08:31] <rvba> dimitern: cool ;)
[08:32] <dimitern> rvba, what I couldn't quite get is how will the devices work with ipaddresses - I mean claim-sticky-ip is one option, but I was thinking of using ipaddresses reserve and then set-sticky-ip-address with it (to better fit in our addressable containers workflow)
[08:33] <rvba> dimitern: you don't need to reserve the IP and then claim it for the device: just one call to claim-sticky-ip should be enough.
[08:34] <rvba> dimitern: also, don't use set-sticky-ip-address.  Just use claim-sticky-ip-address.
[08:34] <dimitern> rvba, is the effect the same? the allocated IP will show as "Static IP" wrt IP Assignement and come from the static range?
[08:34] <rvba> dimitern: we will remove set-sticky-ip-address since claim-sticky-ip-address does exactly the same thing as set-sticky-ip-address when you pass an explicit IP address.
[08:34] <rvba> dimitern: yes
[08:35] <dimitern> rvba, ok, so we'll change juju to use claim-sticky-ip-address for containers instead of ipaddresses reserve, once the 1.8 release is in trusty
[08:35] <rvba> dimitern: sounds good.
[08:36] <dimitern> rvba, or that won't happen before october?
[08:36] <rvba> dimitern: I'm not sure about the timing tbh.  roaksoax will know.
[08:37] <dimitern> rvba, ok, we'll chat on the interlock today
[08:38] <rvba> k
[08:39] <mup> Bug #1441021 was opened: maas api "ipaddresses release" unhelpful success message; bad error message on invalid <api> <confusing-ui> <doc> <juju-net> <MAAS:New> <https://launchpad.net/bugs/1441021>
[12:18] <mup> Bug #1441133 was opened: MAAS version not exposed over the API <api> <MAAS:Triaged> <https://launchpad.net/bugs/1441133>
[13:20] <mup> Bug #1441159 was opened: devices web UI is not updating (need to refresh) <confusing-ui> <dashboard> <juu-core> <MAAS:New> <https://launchpad.net/bugs/1441159>
[13:20] <mup> Bug #1441160 was opened: maas should allow comment on why a system is broken <MAAS:Triaged> <https://launchpad.net/bugs/1441160>
[14:32] <mup> Bug #1440994 changed: maas api "device read <hostname>" returns HTML 404  <api> <juju-net> <robustness> <MAAS:Invalid> <https://launchpad.net/bugs/1440994>
[15:15] <mup> Bug #1441211 was opened: 1.8b1 Node remains clicked in the main page after accessing node details page <MAAS:Triaged> <https://launchpad.net/bugs/1441211>
[15:21] <mup> Bug #1441211 changed: 1.8b1 Node remains clicked in the main page after accessing node details page <MAAS:Triaged> <https://launchpad.net/bugs/1441211>
[15:33] <mup> Bug #1441211 was opened: 1.8b1 Node remains clicked in the main page after accessing node details page <confusing-ui> <ui> <MAAS:Triaged> <https://launchpad.net/bugs/1441211>
[16:00] <saltlake> champs , does anyone have experience with HP proliant servers ? My maas server is unable to control HP server nodes since it is unable to determine the power parameters for those servers. Those servers have ILO2 on them (as displayed on the boot up screen) But I have no idea how and what powere paamaters to set for these HP proliant nodes in their maas configuration
[16:15] <saltlake> I just need a pointer on how to set the power parameters for these HP dl360 G6 nodes.
[17:57] <mup> Bug #1441211 changed: 1.8b1 Node remains clicked in the main page after accessing node details page <confusing-ui> <ui> <MAAS:Triaged> <https://launchpad.net/bugs/1441211>