=== CyberJacob is now known as CyberJacob|Away [02:07] in a juju-local setup the storage port 8040 is the default for what? mongo server? [02:08] i installed juju-core first in saucy then saw the config-local doc and installed juju-local. do i have to remove juju-core at this point? [02:10] reason i ask is this error message shows up doing a fresh juju-local setup: ERROR Get http://10.0.3.1:8040/provider-state: dial tcp 10.0.3.1:8040: connection refused [02:11] the comments from generate-config dont really tell me what storage-port 8040 is [02:14] https://bugs.launchpad.net/juju-core/+bug/1240709, nm [02:14] <_mup_> Bug #1240709: local provider fails to start [03:23] marcoceppi, FYI you can in fact change the network the local provider ends up using by updating the lxc network configuration in /etc/default/lxc-net and running sudo restart lxc-net === CyberJacob|Away is now known as CyberJacob === freeflying_away is now known as freeflying === wedgwood is now known as Guest16041 === freeflying is now known as freeflying_away === jeremydei_ is now known as jeremydei [21:49] You can boot this node using Avahi-enabled boot media or an adequately configured DHCP server. See https://maas.ubuntu.com/docs/nodes.html for instructions. [21:54] What about the idea of an Ubuntu Tarot deck written in Java like this one: http://www.osho.com/Main.cfm?Area=Magazine&Sub1Menu=Tarot&Sub2Menu=OshoZenTarot&Language=English [21:55] The user could jusr choose a card, and it might say "Try editing your DHCP settings ." :-) [22:45] I'm having trouble with getting juju to connect to the environment after I run juju bootstrap. The first time, it asks if I want to confirm the SSH key, which I do. Then it just hangs [22:46] I've tried sshing to the address using the username ubuntu, and that connects just fine and I can run commands on the bootstrap node [22:46] how should I go about debugging/trying to figure out where the problem lies? [22:50] the bootstrap node is a saucy VM running on a KVM virtual machine (for testing purposes) that is managed by MaaS. The computer I'm running the "juju status" command from is the actual host computer, running raring. I've looked at the console of the VM, and it looks like everything completed, I see stuff like "Cloud-init v. 0.7.3 finished" on the VM display === freeflying_away is now known as freeflying