I have added a space to my model. I am trying to deploy some charms to the space. I have added constraints to the charms in my bundle that constrain them to the space and add root-disk=20G.
The root-disk constraint seems to be applied, but the spaces constraint doesn't stick.
You can see from the attached screen shot that the NAT_COMMON_* subnets have the addresses that match the subnets that are in my space, and from the output of the juju run command that the ip addresses of the machines in my model aren't in the space I have constrained them to.
This is the first time I have used spaces in aws with juju > 2.7.6. Using spaces via constraints seems to work fine using the jaas controller.
I have added a space to my model. I am trying to deploy some charms to the space. I have added constraints to the charms in my bundle that constrain them to the space and add root-disk=20G.
The root-disk constraint seems to be applied, but the spaces constraint doesn't stick.
juju spaces https:/ /paste. ubuntu. com/p/MkQCmPqMX V/
bundle.yaml https:/ /paste. ubuntu. com/p/fvxJkkTkn k/
juju status https:/ /paste. ubuntu. com/p/W8FpRjmrX R/
juju run --all "ip a | grep 'ens\|eth'" https:/ /paste. ubuntu. com/p/FtsBKN23f 3/
You can see from the attached screen shot that the NAT_COMMON_* subnets have the addresses that match the subnets that are in my space, and from the output of the juju run command that the ip addresses of the machines in my model aren't in the space I have constrained them to.
This is the first time I have used spaces in aws with juju > 2.7.6. Using spaces via constraints seems to work fine using the jaas controller.