It may help to remove the UI from the model -- the UI does not guarantee a
stateful session.
The UI interacts with the management server using end-user API calls.
Mutating API calls generally have 2 steps:
1. Create / modify the entity in the db
2. Call the backend provisioning steps. This is the
Hi,
I would appreciate if anyone can provide feedback on following questions:
Roughly what is the number of cloudStack deployments that are in JVM
(tomcat or other server) cluster mode where all session objects, http
sessions, beans etc are seamlessly failed over to the other node in case
one of
As far as I know no one deploys in this manner.
On 1/17/13 6:30 AM, Adnan Ashraf mohammad.adnan.ash...@gmail.com wrote:
Hi,
I would appreciate if anyone can provide feedback on following questions:
Roughly what is the number of cloudStack deployments that are in JVM
(tomcat or other server)
Thanks for the feedback. so how does CloudStack provide HA/failover
guarantees? (not just the apache CloudStack but also the Citrix enterprise
CloudPlatform and cloudPortal/CPBM)?
A service provider using CloudStack would expect nothing breaks from two
angle: user's perspective and back-end
