At the moment orbiter has not a status. It doesn't know where it triggers a scaling action for example. This can be a big limitation because a future feature can be:
Don't trigger another scale action if you did something just 1 minutes ago. Because it can be just a false positive behavior.
Or
Give me the list of scaling that orbiter did this week
Or
Move away from a yml based configuration to something like
Manage autoscaling group not via tags (because some providers maybe it doesn't support tags but store the servers managed by orbiter in orbiter itself.
Etcd can be a good candidate to have an embedded distributed storage to support all these features.
This is a very big change, it's not going to be done soon. But it's still something good to have.
At the moment orbiter has not a status. It doesn't know where it triggers a scaling action for example. This can be a big limitation because a future feature can be:
Or
Or
Or
Etcd can be a good candidate to have an embedded distributed storage to support all these features.
This is a very big change, it's not going to be done soon. But it's still something good to have.