Thanks. This is actually for when I have deployed a unit on ec2 machine but
within a new lxc on that machine so not for local. Does this still apply? I am
not quite sure how these network bridges need to be configured so if anybody is
familiar with their setup and how to access the units within
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-10-07 11:47, Mike Sam wrote:
Thanks. This is actually for when I have deployed a unit on ec2
machine but within a new lxc on that machine so not for local. Does
this still apply? I am not quite sure how these network bridges
need to be
the command
juju deploy --to lxc:1
on 1.15.1 worked for me and the lxc is running on the machine when I ssh to it
but did not check if the actual unit has been deployed on it or not. Are you
saying the accessibility is not supported yet?
On Oct 7, 2013, at 12:49 AM, John Arbash Meinel
Hi Mike
I'm sorry, it looks like we never hooked up the early validation that would
have told you it wouldn't work right now. It's my fault -- it languished in
review a bit, and I didn't think through the consequences of leaving it
out. At the moment containerization only works against the MAAS
Sure, no worries, thank you for clarifying this.
I am curious, in terms of lxc work on general ec2 and not vpc, is this going to
be doable at all?
On Oct 7, 2013, at 1:43 AM, William Reade william.re...@canonical.com wrote:
Hi Mike
I'm sorry, it looks like we never hooked up the early
Expanding a bit, internal communication between services and units isn't
along defined channels/ports by the charm, so in effect without vpc you'll
need a separate network overlay (ala tinc or gre) which has some overhead.
Its much more efficient to just use the provider (aws) network
Could you please elaborate as to why more specifically?
Also anything we can do within the charm to do this?
On Oct 7, 2013, at 9:46 AM, Kapil Thangavelu kapil.thangav...@canonical.com
wrote:
Theoretically yes, in juju probably not.
On Mon, Oct 7, 2013 at 9:43 AM, Mike Sam
Vpcs have gotten alot of attention from amazon in the last year. The August
2013 added feature for attaching public addresses to public subnet
instances addresses quite alot of the access/management issues afaics for
simple/dev vpc usage (no need for bastion hosts in public subnets to access
or
