Re: Update: Locks & Service Discovery in CF Runtime
Dear Luan,toggle quoted message Show quoted text
Maybe that's a stupid question which has already been answered, but doesn't consul release 0.8 address most of the criticism from the CF community?
I see now big efforts on all sides (CF and BOSH teams) invested in building our own solution to a problem which seems to be pretty generic.
Do we think that's something we should spend engineering resources on and that others (e.g. HashiCorp in this case) cannot solve the problem to se be our needs? At least to me it seems that they try to move in the right direction.
Maybe my perspective on this is just too generic and I'm not deep enough in the technical details.
What do you think?
Thanks and warm regards
On 24. Apr 2017, at 20:35, Luan Santos <lsantos(a)pivotal.io<mailto:lsantos(a)pivotal.io>> wrote:
We have been working on the milestones proposed before in order to lessen and remove our dependencies on Consul.
Please see the updated Locks & Service Discovery in CF Runtime<https://docs.google.com/document/d/1zw2tQtpBqYol9usIuK_3VKmXHCMW6J9Dupzjr16J-TY/edit> document for more details and discussion.
Software Engineer, Cloud Foundry @ Pivotal