I have a number of questions regarding how to handle stop hooks properly:
1. Background services - stop them or stop & disable them?
The docs say "stop runs immediately before the end of the unit's
destruction sequence. It should be used to ensure that the charm's software
is not running, and wil
1. The stop hook happens when the unit is being removed entirely. It does
not run on reboot (and there's no reboot hook). The docs on the start hook
mention this: "Note that the charm's software should be configured so as to
persist through reboots without further intervention on juju's part." T
On Wed, Oct 19, 2016 at 10:42 AM Nate Finch
wrote:
> 1. The stop hook happens when the unit is being removed entirely. It does
> not run on reboot (and there's no reboot hook). The docs on the start hook
> mention this: "Note that the charm's software should be configured so as to
> persist thr
Shilpa,
There are some documentation about creating storage on MAAS here:
https://maas.ubuntu.com/docs/storage.html
Using this document you should be able to create block devices in MAAS that
you can later use in Juju.
The Juju storage documentation can be found here:
https://jujucharms.com/docs
Matt and I took a look at the following interfaces from IBM today:
-
IBM NFSStorage interface
-
https://bugs.launchpad.net/charms/+bug/1578166
-
+1 from us after lint fixes
-
IBM PlatformMaster interface
-
https://bugs.launchpad.net/charms/+bug/15
Marco Ceppi writes:
> Colocation is a rare scenario, a more common one is manual provider.
Err, sorry, but colocation isn't rare; the majority of clouds we
deploy with juju have ceph colocated with nova compute.
And, to be clear, this is not a theoretical problem, I've been burnt
super badly by
Hi,
I have configured a MAAS cluster and have block device 'sdb' attached to
one of the nodes which I am using to deploy my charm as shown below:
After this I created a storage pool called maastest with attribute tag as
'sdb' and deployed my charm. In the MAAS controller console I see that the
Team,
>From what I can gather, Juju either allows or disallows you to bootstrap to
a specific network/subnet dependent on whether or not the provider supports
a network space bootstrap constraint. The EC2 provider just so happens to
be one of the providers which doesn't support controller placemen
