network spaces - aws support

[Dimiter Naydenov]

Hey James,

Can you please also paste the full logs (scrubbed of secrets) of `juju
bootstrap ... --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 help
figuring out the issue.

From what I can understand, you're trying to bootstrap on a non-default,
possibly private VPC (accessed via its internal address over a VPN
connection maybe?), and then add a model with the same VPC and
credentials. If OTOH, the VPC used for add-model is different, the
machines there won't be able to talk to the controller's VPC unless it
has a public address (cross VPC communication currently relies on having
that, 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

On 08/02/2016 01:04 AM, James Beedy wrote:
> Thanks, Marco.
> 
> `juju status --format yaml` <- http://paste.ubuntu.com/21818491/
> 
> The messages for the machines show "Security group sg-9d6c8ce7 and
> subnet subnet-930c61b8 belong to different networks. (InvalidParameter)'"
> 
> This seems odd, as the subnet I've bootstrapped to is 'subnet-930c61b8'
> 
> On Mon, Aug 1, 2016 at 2:53 PM, Marco Ceppi <marco.ceppi at canonical.com
> <mailto:marco.ceppi at canonical.com>> wrote:
> 
>     What does `juju status --format yaml` produce? it should provide
>     more fruitful machine errors.
> 
>     Marco
> 
>     On Mon, Aug 1, 2016 at 5:46 PM James Beedy <jamesbeedy at gmail.com
>     <mailto:jamesbeedy at gmail.com>> wrote:
> 
>         I'm having some issues with deploying instances to network
>         spaces on aws. 
> 
>         Problem: Instance errors on deploy
> 
>         I have successfully bootstrapped into my aws vpc with `juju
>         bootstrap mycloud aws --credential mycred --config
>         vpc-id=my-vpcid--config force-vpc-id='true' --upload-tools` and
>         subsequently created a model on my aws controller in the vpc
>         with `juju add-model my-new-model -credential mycred
>         --config vpc-id=my-vpcid --config force-vpc-id='true'`.
>         Following which, I add a network space, and then my subnet
>         -> http://paste.ubuntu.com/21814798/. Ok, everything looks great
>         so far .... then I go and launch an instance and it all falls
>         apart -> http://paste.ubuntu.com/21815678/
> 
>         Any insight into what is going on here would be greatly
>         appreciated. Are these network spaces ops even supported on aws?
> 
>         ~thanks
> 
>         --
>         Juju-dev mailing list
>         Juju-dev at lists.ubuntu.com <mailto:Juju-dev at lists.ubuntu.com>
>         Modify settings or unsubscribe at:
>         https://lists.ubuntu.com/mailman/listinfo/juju-dev
> 
> 
> 
> 


-- 
Dimiter Naydenov <dimiter.naydenov at canonical.com>
Juju Core Sapphire team <http://juju.ubuntu.com>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20160802/325adbef/attachment.pgp>