=== kadams54 is now known as kadams54-away
=== kadams54-away is now known as kadams54
[02:48] <toyo|work> can juju run things like apt-get update && apt-get upgrade on nodes?
[02:48] <toyo|work> in maas
[02:48] <toyo|work> guess thats not really a service
[02:50] <sarnold> toyo|work: a while back I put together an unattended-upgrades subordinate charm..
[02:51] <sarnold> toyo|work: I don't know if thats "the best" way to keep systems upgraded; landscape enrollment of the units is another option.
[02:52] <toyo|work> ah
[02:52] <toyo|work> would be nice if it was built into maas
[02:52] <toyo|work> :D
[03:26] <toyo|work> weird, I just tried setting up an apache instance tied to the juju-gui as a balancer and for whatever reason it didnt put a proxypass directive in the apache config so it dont work
[04:29] <toyo|work> when you juju destroy-machine is it supposed to power it down?
=== kadams54 is now known as kadams54-away
=== axw_ is now known as axw
[09:39] <rick_h_> toyo|work: yea, I think landscape is the 'official' answer to the upgrade/management story there.
[09:40] <rick_h_> toyo|work: if there's something missing in the juju-gui/apache relation please file a bug and we'll look into it. I think we tend to put things like haproxy in front and not sure we've got a well tested apache relation in that situations
=== kadams54 is now known as kadams54-away
=== kadams54-away is now known as kadams54
[18:21] <toyo|work> thanks rick_h_
[18:21] <toyo|work> rick_h_: I also figured out the answer to mass upgrades
[18:22] <toyo|work> juju run "sudo apt-get update" --all
=== kadams54 is now known as kadams54-away
=== kadams54 is now known as kadams54-away
=== kadams54-away is now known as kadams54
=== kadams54 is now known as kadams54-away