determine the instance type at deploy
Bug #808969 reported by
Juan L. Negron
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| pyjuju |
Fix Released
|
Wishlist
|
Unassigned | ||
Bug Description
Right now in Ensemble we can determine the default instance type by modifying the environment.yaml file. It would be useful to determin the image-id and the instance-type at deploy time so, the sysadmin can determine the size and type of the instance to be deployed with the understanding that the default would be the image/type determined in the environment.yaml file.
This would allow for better resource allocation ( ie: a simple web server may require a smaller instance than a hadoop-master node or a cassandra node )>
-Juan
| Changed in ensemble: | |
| milestone: | none → dublin |
Revision history for this message
| Clint Byrum (clint-fewbar) wrote | #1 |
| Changed in ensemble: | |
| status: | New → Confirmed |
| importance: | Undecided → Wishlist |
| Changed in ensemble: | |
| milestone: | dublin → none |
Revision history for this message
| Kapil Thangavelu (hazmat) wrote | #2 |
| Changed in juju: | |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
Agreed, deploy and add-unit should take an instance-type argument.