An interesting scenario
Jonathan Aquilina
jaquilina at eagleeyet.net
Tue Jan 21 11:06:41 UTC 2014
I have an interesting scenario which either is already catered for or should
be catered for.
I am currently using a local provider for testing and contribution purposes.
I bootstrapped an environment and deployed the juju-gui i then shut down the
computer and powered it on again this morning the bootstrapped environment
came up just fine yet the instance i created with the juju gui did not
jaquilina at jaquilina-Satellite-S75-A:~/.juju$ juju status
environment: local
machines:
"0":
agent-state: started
agent-version: 1.16.5.1
dns-name: 10.0.3.1
instance-id: localhost
series: saucy
"1":
agent-state: started
agent-version: 1.16.5.1
instance-id: jaquilina-local-machine-1
instance-state: missing
series: precise
services: {}
jaquilina at jaquilina-Satellite-S75-A:~/.juju$ sudo lxc-ls --fancy
NAME STATE IPV4 IPV6 AUTOSTART
--------------------------------------------------------------
jaquilina-local-machine-1 RUNNING 10.0.3.50 - YES
As can be seen the instance state is missing. I removed the entire
bootstrapped environment and recreated it again
machines:
"0":
agent-state: started
agent-version: 1.16.5.1
dns-name: 10.0.3.1
instance-id: localhost
series: saucy
services: {}
Now the scenario is this. This is more for cloud providers as well as those
hosting private clouds. But what does one do if you have a server which fails
or power cycles itself for one reason or another. How will one bring back up
the instances that were running on it?
Regards
Jonathan
More information about the Juju-dev
mailing list