On 30/10/16 19:34, James Beedy wrote:
>
> Problem: Multiple 3rd party/vendors need access to application
> environments and infrastructure. Network address space not segregated
> correctly - no way to separate bootstrap controller from app env
> subnets/spaces.
Juju already has the concept of
Rick,
Let me try and detail in short what I'm implementing for networking on aws.
Problem: Multiple 3rd party/vendors need access to application environments
and infrastructure. Network address space not segregated correctly - no way
to separate bootstrap controller from app env subnets/spaces.
James, can you provider more detailed info on the rules of your deployment
you're looking for?
You mention wanting a controller away from other things on a subnet? Does
this reach out true for HA nodes on that controller, workloads brought up
by that controller? Are you expecting some sort of
Dimiter,
Thanks for looking into this. That sounds like an awesome solution!
~James
> Team,
>
> From what I can gather, Juju either allows or disallows you to bootstrap
> to a specific network/subnet dependent on whether or not the provider
> supports a network space bootstrap constraint. The
On 10/19/2016 11:45 PM, James Beedy wrote:
> Team,
>
> From what I can gather, Juju either allows or disallows you to bootstrap
> to a specific network/subnet dependent on whether or not the provider
> supports a network space bootstrap constraint. The EC2 provider just so
> happens to be one of
Team,
>From what I can gather, Juju either allows or disallows you to bootstrap to
a specific network/subnet dependent on whether or not the provider supports
a network space bootstrap constraint. The EC2 provider just so happens to
be one of the providers which doesn't support controller
Team,
>From what I can gather, Juju either allows or disallows you to bootstrap to
a specific network/subnet dependent on whether or not the provider supports
a network space bootstrap constraint. The EC2 provider just so happens to
be one of the providers which doesn't support controller
the constraints language for the bootstrap
machines and also keep this language as the way to describe the default
host on create-environment. In other words:
juju bootstrap constraints=XXX
juju create-environment foo constraints=XXX
Does that sound about right?
Mark
signature.asc
Description: OpenPGP
--constraint', and
I've always unset it after bootstrapping.
Matt
On Thu, Aug 27, 2015 at 12:19 PM, John Meinel j...@arbash-meinel.com
wrote:
I think his issue is that he can juju bootstrap --constraints and then
immediately juju set-env to remove the constraints. But juju quickstart
--constraints
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27.08.2015 07:29, Matt Rae wrote:
Hi All, when using 'juju bootstrap --constraints' the constraint is
used for bootstrap, but the constraint is also set on the
environment for future machines.
Is it helpful to set the additional environment
Hi All, when using 'juju bootstrap --constraints' the constraint is used
for bootstrap, but the constraint is also set on the environment for future
machines.
Is it helpful to set the additional environment constraint?
So far I've frequently seen the bootstrap constraint used to choose which
11 matches
Mail list logo
