GCE provider

[Curtis Hovey-Canonical]

On Wed, Mar 25, 2015 at 3:04 AM, Andrew Wilkins
<andrew.wilkins at canonical.com> wrote:
> Hey folks,
>
> I just signed up for a GCE trial, and tested out the provider on master.
> Found a couple of issues.
>
> I've filed https://bugs.launchpad.net/juju-core/+bug/1436191. I suspect the
> same issue would exist on 1.23, but haven't tested. I haven't set the
> status/importance, because I don't know what the importance is (there's no
> CI or docs?), and I'd like for someone to confirm the bug.

I just got CI credentials yesterday evening. As CI is using a project
shared by several Canonical staff, it isn't clear to me if I should be
creating new client ids or how to generate keys and not interfere with
other people.

Contrary to text generated by init, 'region' is required.

> Second, a UX thing. It was mostly clear how to generate keys, but it wasn't
> super clear what format to put them into environments.yaml. Obviously
> this'll be documented, but I think it'd be nice if in environments.yaml we
> could just specify the location of the JSON file that GCE spits out, and
> have Juju extract the info it needs, like we do with certs and SSH keys.

I assumed I could use authorized-keys.


-- 
Curtis Hovey
Canonical Cloud Development and Operations
http://launchpad.net/~sinzui