network spaces - aws support

[James Beedy]

To my utter dismay, setting the correct config 'vpc-id-force' gave me the
same result....

Let me scrub and collect my machine-0.log for you.



On Tue, Aug 2, 2016 at 9:36 AM, James Beedy <jamesbeedy at gmail.com> wrote:

> Dimiter,
>
> Thanks for the insight.
>
>
>
>
>
>
> *Can you please also paste the full logs (scrubbed of secrets) of
> `jujubootstrap ... --debug` (with the vpc-id etc., but please also
> include`--config logging-config='<root>=TRACE'`), and machine-0.log
> from/var/log/juju on the bootstrap node, once completed? That will
> helpfiguring out the issue.*
> `juju bootstrap creativedrive aws --credential creativedrive --config vpc-id=vpc-ff069a98
> --config force-vpc-id='true' --config loggin-config='<root>=TRACE'
> --upload-tools --debug` <- http://paste.ubuntu.com/21908548/
>
> machine-0.log shows  "2016-08-02 16:16:16 TRACE juju.apiserver
> request_notifier.go:127 -> [2] machine-0
> {"request-id":53,"response":{"config":{"access-key":"","agent-version":"2.0-beta13","authorized-keys":"juju-client-key\nssh-rsa
> ssh-rsa
> juju-system-key\n","automatically-retry-hooks":true,"default-series":"","development":false,"disable-network-management":false,"firewall-mode":"instance","force-vpc-id":true,"ignore-machine-addresses":false,"logging-config":"\u003croot\u003e=TRACE;unit=DEBUG","name":"controller","proxy-ssh":false,"region":"us-east-1","secret-key":"/E","ssl-hostname-verification":true,"storage-default-block-source":"ebs","test-mode":false,"type":"ec2","uuid":"259be235-a255-416d-8bbf-75e128d05794","vpc-id":"vpc-ff069a98"
> ,"vpc-id-force":false}}}"
>
>
> Just realizing now, I have been specifying 'vpc-force-id', not
> 'vpc-id-force' (grrrr).
>
> I would expect to see this resolved when I apply the correct config. I'll
> report back shortly.
>
> Thanks for your time!
>
>
>
>
>
>
> *From what I can understand, you're trying to bootstrap on a
> non-default,possibly private VPC (accessed via its internal address over a
> VPNconnection maybe?), and then add a model with the same VPC
> andcredentials.*
> ^ Exactly
>
>
>
>
> * If OTOH, the VPC used for add-model is different, themachines there
> won't be able to talk to the controller's VPC unless ithas a public address
> (cross VPC communication currently relies on havingthat, fancier setups
> with VPN gateways is not yet supported).*
>
> ^
>
> The error in status implies 2 separate VPCs are used (or a VPC and
> EC2-Classic - i.e. no VPC) for the controller and hosted model.
>
> Cheers,
> Dimiter
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20160802/f4c543e8/attachment.html>