Skip to content
This repository has been archived by the owner on Aug 2, 2023. It is now read-only.

Less configuration #1

Closed
vincentbernat opened this issue Feb 5, 2017 · 2 comments
Closed

Less configuration #1

vincentbernat opened this issue Feb 5, 2017 · 2 comments

Comments

@vincentbernat
Copy link

Hey!

To lessen the amount of configuration needed, the only mandatory parameter could be the EIP to use. exoip would add the current VM to the specified EIP and retrieve the peers from the API (those are VM that share the EIP). The cluster ID would be the EIP. The list of peers need to be refreshed at regular interval (or maybe only when the current master goes down for non-master or when the master receives messages from unknown peers). The metadata server could be used to retrieve the current VM.

@pyr
Copy link
Contributor

pyr commented Feb 5, 2017

The cluster ID is already the EIP. Priority is the same for all hosts by default so doesn't need to be provided. I wondered about adding support for fetching the current machine's NIC.

@pyr
Copy link
Contributor

pyr commented Feb 5, 2017

I disagree with fetching the list of peers from the API though, for now, it will be too brittle.

@pyr pyr closed this as completed in 8461926 Feb 5, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants