-
Notifications
You must be signed in to change notification settings - Fork 0
Brooklyn Ideas
Great ideas. No implementation planned (yet).
Using Brooklyn to manage the roll-out of a change to an application, with the capability to roll back the change should something go wrong. Brooklyn should be able to upgrade a cluster or fabric (customizable speed?) without conflict or end-user downtime. Brooklyn must be able to rollback partially successful/aborted rollouts.
- db replication and security, backup -- autoscale db cluster
- wide area replication -- possibly write-behind
- db upgrade policy
- db security / encryption -- ssl on every connection -- easy option to turn on, automate storage encryption ? - encrypted volumes (in the cloud)
When doing upgrades/updates to database layers, it would be useful to represent a particular schema or version of the database as an entity.
There should be an option within Brooklyn which automatically secures all connections using SSL, with Brooklyn handling admin of the SSL.
- collate + inspect logs (eg django sentry, serves errors in admin bit)
- alerts
It would be useful to have an entity for production systems that automatically and randomly kills production entities to test the resilience of the application, like Netflix’s Chaos Monkey. (blog, git repo, brooklyn-dev thread) This might first be implemented using the web GUI.
A method of deploying Brooklyn management entity to a cloud, then having the management entity deploy the managed service/application into the cloud around it.
Discussions ongoing.