On Thu, Mar 26, 2015 at 9:54 AM, Eric Snow <eric.s...@canonical.com> wrote:
> On Wed, Mar 25, 2015 at 5:55 PM, Andrew Wilkins > <andrew.wilk...@canonical.com> wrote: > > On Wed, Mar 25, 2015 at 9:33 PM, Curtis Hovey-Canonical > > <cur...@canonical.com> wrote: > >> > >> On Wed, Mar 25, 2015 at 3:04 AM, Andrew Wilkins > >> <andrew.wilk...@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". > > Yeah, I'm not sure what happened there. Either we had a default and > removed it but failed to update the config text, or we were going to > have a default but missed actually adding it. Would it make sense to > have a default region? We do for AWS (us-east-1). I think it wouldn't hurt to do the same for GCE. I expect most people would be using that region anyway, and it'll be helpful for if/when we want to have a way of creating environments without the YAML file. > > > >> > >> > >> > 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. > > I'm writing up a patch that basically does this. > > -eric >
-- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
