Difference between revisions of "Trove/HeatIntegration"
< Trove
(Created page with "Reasons for waiting to install heat. We want to use heat, but i dont feel like its at a state where it fits our clustering integration. --------------------------------------...") |
|||
| Line 1: | Line 1: | ||
| − | Reasons for waiting to | + | Reasons for waiting to integrate heat. We want to use heat, but i dont feel like its at a state where it fits our clustering integration, which was the major reason for integrating. |
------------------------------------------------ | ------------------------------------------------ | ||
1) Companies who are looking at reddwarf are not yet looking at heat, and a hard dependency might stifle growth of the product initially | 1) Companies who are looking at reddwarf are not yet looking at heat, and a hard dependency might stifle growth of the product initially | ||
* CERN | * CERN | ||
| − | |||
2) homogeneous LaunchConfiguration | 2) homogeneous LaunchConfiguration | ||
* a database cluster is heterogeneous | * a database cluster is heterogeneous | ||
* Our cluster configuration will need to specify different sized slaves, and allow a customer to upgrade a single slaves memory | * Our cluster configuration will need to specify different sized slaves, and allow a customer to upgrade a single slaves memory | ||
| − | * | + | * heat said if this is something that has a good use case, they could potentially make it happen |
3) have to modify template to scale out | 3) have to modify template to scale out | ||
* This doable but will require hacking a template in code and pushing that template | * This doable but will require hacking a template in code and pushing that template | ||
| − | * I assume removing a slave will require the same | + | * I assume removing a slave will require the same finagling of the template |
* I understand that a better version of this is coming | * I understand that a better version of this is coming | ||
Revision as of 22:13, 2 July 2013
Reasons for waiting to integrate heat. We want to use heat, but i dont feel like its at a state where it fits our clustering integration, which was the major reason for integrating.
1) Companies who are looking at reddwarf are not yet looking at heat, and a hard dependency might stifle growth of the product initially
- CERN
2) homogeneous LaunchConfiguration
- a database cluster is heterogeneous
- Our cluster configuration will need to specify different sized slaves, and allow a customer to upgrade a single slaves memory
- heat said if this is something that has a good use case, they could potentially make it happen
3) have to modify template to scale out
- This doable but will require hacking a template in code and pushing that template
- I assume removing a slave will require the same finagling of the template
- I understand that a better version of this is coming
