Commits on Sep 28, 2016

1. etcd: Add static cluster configuration option …

   Currently the only way to configure an etcd cluster is by using the
   discovery service. This may not always be an option especially for
   offline scenarios. An option 'enable_discovery_service' is added to
   allow for the enabling/disabling of using the discovery service versus
   using a static cluster configuration. This option is defaulted to 'true'
   to maintain the use of the discovery service as the default. When the
   discovery service option is disabled the etcd cluster will be statically
   configured and will be comprised of each instance.
   
   Additionally static configuration requires that each etcd member be
   named explicitly. This means that each node requires a 'user-data' file
   that has the etcd member name set. When the discovery service option is
   disabled a 'user-data' file for each instance will be created. The name
   of each of these files will be 'user-data' appended with the instance
   id (ex. user-data-01) and will have the etcd member name set to the
   instance name (ex. core-01).

   

   fillet54 committed Sep 28, 2016
   Configuration menu

   • View commit details
   • Copy full SHA for 0773382
   • Browse repository at this point

   Copy the full SHA

   0773382 View commit details

   Browse the repository at this point in the history

2. etcd: Fix etcd v1 static configuration …

   Incorrectly assumed that etcd v1 and v2 static configuration was the
   same. In v1 a peers list should be provided that is just a list of the
   peers ip and port. In addition to a peers list an initial leader must be
   selected by not having a peers list. This was accomplished by deleting
   the peers list for the last instance of the cluster.

   

   fillet54 committed Sep 28, 2016
   Configuration menu

   • View commit details
   • Copy full SHA for 2e70734
   • Browse repository at this point

   Copy the full SHA

   2e70734 View commit details

   Browse the repository at this point in the history