I wonder what is about redundancy and reliability of Scalr servers themselves ? What happens to the farm, instances, DB, Elastic IPs etc. when the Scalr controller itself goes down, either opensource self- hosted or paid Scalr.net service ? What will happen after launching it up, will it cure itself and recognize the farm instances launched prior to the crash? Where does it store it's on the fly config (if it does at all) ?
It is no point to build highly reliable app architecture only to have Scalr controller server as the weakest point. Wiki have no info on this topic, neither scalr.net offer any reliability guarantee or SLA. Only thing I was able to find is that Scalr1 is all-in-one pack, thus the questionable dependability. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
