search

cloudfoundry-attic / etcd-release

Apache License 2.0
3 stars 17 forks source link

Use of etcd-release as key-value store and locking #49

Closed subhankarc closed 6 years ago

subhankarc commented 6 years ago

Hi,

We were currently evaluating ETCD to be used as part of Service Fabrik (https://github.com/cloudfoundry-incubator/service-fabrik-broker) mainly for key value store and for distributed locking. I heard there is some issue for which CF is moving away from ETCD release, was wondering if I can get details around that and if you can comment whether we can use it for our use-case.

cf-gitbot commented 6 years ago

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/153739156

The labels on this github issue will be updated when the story is started.

genevieve commented 6 years ago

Our issues were mostly about upgrades in the context of bosh. To maintain the cluster, you cannot jump between major/minor versions. You need to upgrade each node in the cluster to the next minor and so on until you reach the version are you are looking for. This would mean having every version of etcd-release necessary to go through each minor and to bosh deploy with each one. This would mean multiple deploys and it's something we hoped for a better solution to.

Hope this clarifies it a bit!