juju bootstrap starts up the node.
The node loads, and then nothing. I get a juju status of
no reachable server, it's like MaaS does not report to Juju that the node is ready for Juju. MaaS UI does show the node as allocated.
That is where it stays until I issue
juju destroy-environment, which MaaS executes to the letter, shutting down the node and then shows the node as "ready" in the MaaS UI.
I waited an hour and watched the node load before running the destroy command.
error details no reachable server
structure: i have the maas-region and cluster running off one dell 1800 running ubuntu 12.04.4 server. eth0 is internet connected @ xxx.xxx.xxx.100,to the public switch (which gives me xxx.xx.xxx.100/MAAS and full internet access) eth1 is connected to private none managed gigabit switch, eth1 set to xx.xx.xx.1., eth1 is set to manged with maas dns/dhcp hosting the all 10 dell 1950 gen 2s. servers get internal addressing.
all machines commission and enlisted and become ready normally.
i install juju client on a machine operating in the public side on the connection, running ubuntu 12.4.4 64 bit
i can access the maas ui, and everything is looks normal. then the juju client from configuration to access becomes overwhelming.
1st errors come when for some reason juju tries to get the needed tools from amazomaws. (remember i am in maas). the 2nd is that if i don't tell it where to find the authorized keys it does not go. my environments.yaml is
default: maas environments: maas: type: maas maas-server: 'http://xxx.xxx.xxx/MAAS/' maas-oauth: '3Ey3RueWP2X4asFahJ:CmR3fPYaTBwxhvx87X:Sample' admin-secret: '' authorized-keys-path: /xxx/xxxxx/id_xxx.pub
after all correction i just get the above described.