In 2.3 there is "juju upgrade-juju --ignore-agent-versions" but I think
that is only respected if the target controller already is 2.3 (eg, this
would help if you were trying to go from 2.3 to 2.4, but won't help going
2.2 to 2.3).
There is a separate command line utility that you can build in
In 2.3 there is "juju upgrade-juju --ignore-agent-versions" but I think
that is only respected if the target controller already is 2.3 (eg, this
would help if you were trying to go from 2.3 to 2.4, but won't help going
2.2 to 2.3).
There is a separate command line utility that you can build in
I have a vmware vm on my public network that is my juju host. In it I
have an lxc container that is also bridged to my public network. I
bootstrapped it with:
juju bootstrap manual/ipaddress modelname
I also created vms with public IP addresses that I setup an ubuntu
account and added
I have a vmware vm on my public network that is my juju host. In it I
have an lxc container that is also bridged to my public network. I
bootstrapped it with:
juju bootstrap manual/ipaddress modelname
I also created vms with public IP addresses that I setup an ubuntu
account and added
Alvaro,
The three charms have been promulgated (the first already was) and the
permissions set so that prometheus-charmers can release updates to stable
without reaching out to the list.
As far as I know, the promulgate sub-command will not be added to the charm
command, and new promulgations
I'm a bit curious what you mean by "manually provisioned machine". Are you
saying that you used the VMWare APIs directly to launch an instance, and
then "juju bootstrap IP" to start using that machine, and then "juju
add-machine ssh:IP" to add the second machine?
You could try doing "juju
I'm a bit curious what you mean by "manually provisioned machine". Are you
saying that you used the VMWare APIs directly to launch an instance, and
then "juju bootstrap IP" to start using that machine, and then "juju
add-machine ssh:IP" to add the second machine?
You could try doing "juju
