juju bootstrap on three subnets out of 5 not possible

marking as field critical as this is blocking the deployment on aws.

subscribed ~field-critical

As this is field-critical and as you note Juju doesn't currently support the ability to bootstrap to multiple subnets I think that the only work around atm is going to be to manually add the machines in the right subnets/zones and then enable-ha --to the machines brought up.

There's work to make zones constraints that might help with this on going but I'm not 100% sure on the tie in between the subnets and the AZ here.

Actually rereading, if you're trying to bootstrap and deploy to only 3 of the 5, can we not just remove the extra subnets from the VPC?

Richard,
They have to have more subnets because of vpn access to us. Also they have
plan to being more workloads on those extra subnet. It is field critical
critical if it blocks the deployment. But can we enable ha juju enable-ha
with --to parameters.

Thanks and Regards,
Narinder Gupta
Canonical, Ltd.
+1.281.736.5150

Ubuntu- Linux for human beings | www.ubuntu.com | www.canonical.com

On Tue, Nov 20, 2018 at 9:00 AM Richard Harding <email address hidden>
wrote:

> Actually rereading, if you're trying to bootstrap and deploy to only 3
> of the 5, can we not just remove the extra subnets from the VPC?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1804244
>
> Title:
> juju bootstrap on three sunbets out of 5 not possible
>
> Status in juju:
> New
>
> Bug description:
> canonical is trying to bootstrap a controller on aws where in single
> vpc we have multiple private and public subnet says 5 of them. but
> only 3 out of 5 subnets were supposed to be used for HA bootstrap and
> also workload should also be on those three subnets only.
>
> currently there is no way to provide multiple subnet during bootstrap
> or after bootstrap to enable HA on multiple AZs on different subnet.
>
> currently we are using the following for single subnet.
> juju bootstrap aws/us-east-1 nrg --credential canadm --config
> vpc-id=<vpc id> --config vpc-id-force=true --bootstrap-constraints
> "root-disk=50G" --bootstrap-series xenial --to "subnet=<subnet id>"
>
> and then juju enable-ha
>
> juju add-space private "172.25.10.0/24" -m controller
> juju add-space private "172.25.10.0/24" -m default
> juju set-model-constraints spaces=private -m controller
> juju set-model-constraints spaces=private -m default
> juju switch controller
> juju enable-ha
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1804244/+subscriptions
>

Given that you have a workaround with the manual machines and enable-ha --to I'm going to move it from critical to field-high according to the standards in https://wiki.canonical.com/DCD/FieldSLA

The fact that this is missing functionality in Juju this doesn't qualify for the field SLA definitions as outlined in the wiki linked above.

can't you use

juju enable-ha --to subnet=b,subnet=c

or does the --to not support the full syntax

Also, are these subnets separated by zones?

Ideally this would all be done by spaces and you would put the controller
into a space that only has the 3 subnets you want. We do still have the
chicken and egg problem where AWS doesn't define spaces until we have a
controller.

John
=:->

On Nov 21, 2018 02:40, "Tim Penhey" <email address hidden> wrote:

The fact that this is missing functionality in Juju this doesn't qualify
for the field SLA definitions as outlined in the wiki linked above.

** Tags removed: field-high

** Summary changed:

- juju bootstrap on three sunbets out of 5 not possible
+ juju bootstrap on three subnets out of 5 not possible

--
You received this bug notification because you are a member of Canonical
Field Critical, which is subscribed to the bug report.
Matching subscriptions: juju bugs
https://bugs.launchpad.net/bugs/1804244

Title:
  juju bootstrap on three subnets out of 5 not possible

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1804244/+subscriptions

I have not tried syntax juju enable-ha --to subnet=b,subnet=c i will try
that and let you know. There are five subnet in three zone and that could
be case in future deployment as well so its worth to find out what is
supported and whats not on aws. For spaces i have to bootstrap first. I
have plan to test single space multiple subnet as well.

Thanks and Regards,
Narinder Gupta
Canonical, Ltd.
+1.281.736.5150

Ubuntu- Linux for human beings | www.ubuntu.com | www.canonical.com

On Tue, Nov 20, 2018 at 8:15 PM John A Meinel <email address hidden>
wrote:

> can't you use
>
> juju enable-ha --to subnet=b,subnet=c
>
> or does the --to not support the full syntax
>
> Also, are these subnets separated by zones?
>
> Ideally this would all be done by spaces and you would put the controller
> into a space that only has the 3 subnets you want. We do still have the
> chicken and egg problem where AWS doesn't define spaces until we have a
> controller.
>
> John
> =:->
>
> On Nov 21, 2018 02:40, "Tim Penhey" <email address hidden> wrote:
>
> The fact that this is missing functionality in Juju this doesn't qualify
> for the field SLA definitions as outlined in the wiki linked above.
>
> ** Tags removed: field-high
>
> ** Summary changed:
>
> - juju bootstrap on three sunbets out of 5 not possible
> + juju bootstrap on three subnets out of 5 not possible
>
> --
> You received this bug notification because you are a member of Canonical
> Field Critical, which is subscribed to the bug report.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1804244
>
> Title:
> juju bootstrap on three subnets out of 5 not possible
>
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1804244/+subscriptions
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1804244
>
> Title:
> juju bootstrap on three subnets out of 5 not possible
>
> Status in juju:
> Triaged
>
> Bug description:
> canonical is trying to bootstrap a controller on aws where in single
> vpc we have multiple private and public subnet says 5 of them. but
> only 3 out of 5 subnets were supposed to be used for HA bootstrap and
> also workload should also be on those three subnets only.
>
> currently there is no way to provide multiple subnet during bootstrap
> or after bootstrap to enable HA on multiple AZs on different subnet.
>
> currently we are using the following for single subnet.
> juju bootstrap aws/us-east-1 nrg --credential canadm --config
> vpc-id=<vpc id> --config vpc-id-force=true --bootstrap-constraints
> "root-disk=50G" --bootstrap-series xenial --to "subnet=<subnet id>"
>
> and then juju enable-ha
>
> juju add-space private "172.25.10.0/24" -m controller
> juju add-space private "172.25.10.0/24" -m default
> juju set-model-constraints spaces=private -m controller
> juju set-model-constraints spaces=private -m default
> juju switch controller
> juju enable-ha
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1804244/+subscriptions
>

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.