Support subnet (VPC) on EC2 environments
Bug #1073133 reported by
Francisco Souza
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyjuju |
Won't Fix
|
Low
|
Unassigned |
Bug Description
It would be nice if juju support VPC, allowing to deploy services in a subnet. It could be a setting in the environments.yaml file or a parameter to `juju deploy` (IMO, a parameter in the environment makes more sense).
For example:
environments:
sample:
type: ec2
control-bucket: juju-25b96216d0
admin-secret: c921cf2b77a0407
default-series: precise
ssl-
subnet-id: subnet-aa00aa00
Changed in juju: | |
milestone: | none → 0.8 |
Changed in juju: | |
importance: | Medium → Low |
To post a comment you must log in.
What about if juju managed the vpc as a 1-1 resource to env (ie. created the vpc for the env, tied to the lifecycle of the env)?
The biggest issue with vpc that i'm aware of is the problems that occur if the env has more exposed service units then the available elastic ips (10 total per my reading of the docs, 5 for the account, and 5 for a vpc user).