GCE provider
Andrew Wilkins
andrew.wilkins at canonical.com
Wed Mar 25 23:55:00 UTC 2015
On Wed, Mar 25, 2015 at 9:33 PM, Curtis Hovey-Canonical <
curtis at canonical.com> wrote:
> 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.
Indeed, I forgot that one. The boilerplate we generate should
not comment out "region".
>
> > 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.
authorized-keys is fine. That was a bad example.
In the Azure provider, credentials take the form of a certificate and key.
You *can* enter the cert/key inline in your environments.yaml, but you
can also specify management-certificate-path and the provider will read
that file and add the contents into the management-certificate attribute.
>
> --
> Curtis Hovey
> Canonical Cloud Development and Operations
> http://launchpad.net/~sinzui
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20150326/5dfd4b14/attachment-0001.html>
More information about the Juju-dev
mailing list