search

kapilt / juju-digitalocean

JuDo - A juju provider for digital ocean using a client side plugin and manual provisioning.
111 stars 17 forks source link

Windows support: wrong juju directory for environments.yaml #15

Closed 0vermind closed 10 years ago

0vermind commented 10 years ago

juju-docean seems to search for environments.yaml in the wrong directory (C:\Users\overmind.juju\ ) instead of (c:\Users\overmind\AppData\Roaming\Juju) when trying to boostrap:

(juju-docean) c:\Users\overmind>juju-docean bootstrap --constraints="mem=512M, region=ams2" -v
Configuration error: Juju environments.yaml not found C:\Users\overmind/.juju\environments.yaml
kapilt commented 10 years ago

i've pushed a commit to at least lookup the default juju home from its windows location, but windows support is not likely without using something like cygwin, or digital ocean growing some better support for userdata (which removes the need for the plugin to ssh into machines) you can vote on that feature request for digital ocean here http://digitalocean.uservoice.com/forums/136585-digitalocean/suggestions/3736274-support-cloudinit-instance-metadata

kapilt commented 10 years ago

The underlying issue here on windows being that the plugin runs openssh client to update the machines which isn't available under windows without a cygwin environment, and i'd rather not up the installation dependency stack to include the nesc bits to do this entirely in python (paramiko and openssl).

kapilt commented 10 years ago

i've looked around and realistically we're not going to be drop the ssh requirement even with userdata, as we need it to bootstrap. iotw. windows support isn't coming.