Thanks for spotting this, I will dig into it later on (check the docs, verify that vnc=auto works correctly).
I'm pretty sure the attribute was called "vnc:ip" when I originally worked on the driver back in 2010 though. Also next time when you send a patch like this please include more information (error message, etc.) and reference to the documentation and / or official client library which says that "vnc=auto" is the right parameter. Thanks On Wed, Dec 26, 2012 at 8:15 AM, Rick Copeland <[email protected]> wrote: > Hi, > > I'm using libcloud to manage a multi-cloud deployment and trying to use the > ElasticHosts support. While I can build & launch servers just fine, it's > not possible as far as I can tell to actually log in to the servers via > libcloud. > > The API provides for a "VNC password" which will be used to set a password > for a "toor" user, but there is a bug in the libcloud driver where it > passes a vnc:ip=auto param instead of vnc=auto. The vnc:ip param is not > recognized by elastichosts, so the API call fails. The fix is here: > https://gist.github.com/4381128 > > -Rick Copeland >
