Skip to content
This repository has been archived by the owner on Apr 3, 2024. It is now read-only.

Support VIP for redis instance #34

Open
dhilipkumars opened this issue Aug 31, 2016 · 5 comments
Open

Support VIP for redis instance #34

dhilipkumars opened this issue Aug 31, 2016 · 5 comments

Comments

@dhilipkumars
Copy link
Member

While creating redis instances add attributes to support VIP so that service discovery can be made easy. This is related to #33

@dhilipkumars dhilipkumars added this to the Version 0.0.2 milestone Aug 31, 2016
@ChetanBhasin
Copy link

Hi! Is there a status update on this?

@dhilipkumars
Copy link
Member Author

@ChetanBhasin Hi Sorry we know we are terribly behind on schedule. We got pulled into some internal projects and couldn't spend time on this recently. We will try and get upto speed in completing these open issues.

@ChetanBhasin
Copy link

Thanks for the update!

@dhilipkumars
Copy link
Member Author

This framework is built on top of 'mesos-go' language binding. This language binding is pending update since some time, for VIP support the protobuf message specification should be upgraded. The current spec does not cover 'Labels' portion which is important in setting VIP. https://github.com/mesos/mesos-go/pull/263/files#diff-a9294dbaba0cf94ca6b1772f84ca5e9bR537. Long story short for us to be able to use VIP these changes to be pulled into master mesos/mesos-go#263.

@dhilipkumars dhilipkumars removed this from the Version 0.0.2 milestone Nov 7, 2016
@eddyzags
Copy link

eddyzags commented May 9, 2017

Hey! What about the service port ? Is there any way to define the service port of the redis master instance in order to contact it with marathon-lb ?
Example:
Definition: portMappings: [ { "containerPort": 6380, "hostPort": 0, "servicePort": 10001 } ]

Reachable with: marathon-lb.marathon.mesos:10001

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants