./sysutils/consul, Tool for service discovery, monitoring and configuration

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 1.2.0, Package name: consul-1.2.0, Maintainer: filip

Consul is a tool for service discovery and configuration. Consul
is distributed, highly available, and extremely scalable.


Required to build:
[lang/go] [pkgtools/cwrappers]

Master sites:

SHA1: 80b62983aa44a7f90ad1619333a693a1d0af1fd5
RMD160: 97cd544c27de436a6f910f67e4a9cf4d643bb70c
Filesize: 16784.232 KB

Version history: (Expand)


CVS history: (Expand)


   2018-07-03 14:14:30 by Filip Hajny | Files touched by this commit (2) | Package updated
Log message:
sysutils/consul: Update to 1.2.0.

FEATURES:

- Connect Feature Beta: This version includes a major new feature for
  Consul named Connect. Connect enables secure service-to-service
  communication with automatic TLS encryption and identity-based
  authorization.
  - Connect must be enabled explicitly in configuration so upgrading a
    cluster will not affect any existing functionality until it's
    enabled.
  - This is a Beta feature, we don't recommend enabling this in
    production yet. Please see the documentation for more information.
- dns: Enable PTR record lookups for services with IPs that have no
  registered node
- ui: Default to serving the new UI. Setting the `CONSUL_UI_LEGACY`
  environment variable to `1` or `true` will revert to serving the old
UI

IMPROVEMENTS:

- agent: A Consul user-agent string is now sent to providers when
  making retry-join requests
- client: Add metrics for failed RPCs
- agent: Add configuration entry to control including TXT records for
  node meta in DNS responses
- client: Make RPC rate limit configuration reloadable

BUG FIXES:

- agent: Fixed an issue where watches were being duplicated on reload.
- agent: Fixed an issue with Agent watches on a HTTPS only agent would
  fail to use TLS.
- agent: Fixed bug that would cause unnecessary and frequent logging
  yamux keepalives
- dns: Re-enable full DNS compression
   2018-06-12 19:50:29 by Benny Siegert | Files touched by this commit (102) | Package updated
Log message:
Revbump all Go packages after lang/go update.
   2018-05-14 18:12:41 by Filip Hajny | Files touched by this commit (2) | Package updated
Log message:
sysutils/consul: Update to 1.1.0.

FEATURES:

- UI: The web UI has been completely redesigned and rebuilt and is in
  an opt-in beta period.
- api: Added support for Prometheus client format in metrics endpoint
  with `?format=prometheus` (see docs)
- agent: New Cloud Auto-join provider: Joyent Triton.
- agent: (Consul Enterprise) Implemented license management with
  license propagation within a datacenter.

BREAKING CHANGES:

- agent: The following previously deprecated fields and config options
  have been removed
  - `CheckID` has been removed from config file check definitions (use
    `id` instead).
  - `script` has been removed from config file check definitions (use
    `args` instead).
  - `enableTagOverride` is no longer valid in service definitions (use
    `enable_tag_override` instead).
  - The deprecated set of metric names (beginning with
    `consul.consul.`) has been removed along with the
    `enable_deprecated_names` option from the metrics configuration.

IMPROVEMENTS:

- agent: Improve DNS performance on large clusters
- agent: `start_join`, `start_join_wan`, `retry_join`,
  `retry_join_wan` config params now all support go-sockaddr templates
- server: Added new configuration options `raft_snapshot_interval` and
  `raft_snapshot_threshold` to allow operators to  configure how often
  servers take raft snapshots. The default values for these have been
  tuned for large and busy clusters with high write load.

BUG FIXES:

- agent: Only call signal.Notify once during agent startup
- agent: Add support for the new Service Meta field in agent config
- api: Add support for the new Service Meta field in API client
- agent: Updated serf library for two bug fixes - allow enough time
  for leave intents to propagate
- agent: When node-level checks (e.g. maintenance mode) were deleted,
  some watchers currently in between blocking calls may have missed
  the change in index.
   2018-04-16 14:36:12 by Filip Hajny | Files touched by this commit (2) | Package updated
Log message:
sysutils/consul: Update to 1.0.7.

IMPROVEMENTS:

- build: Bumped Go version to 1.10
- agent: Blocking queries on service-specific health and catalog
  endpoints now return a per-service `X-Consul-Index` improving watch
  performance on very busy clusters.
- agent: All endpoints now respond to OPTIONS requests.
- agent: List of supported TLS cipher suites updated to include newer
  options,
- agent: WAN federation can now be disabled by setting the serf WAN
  port to -1.
- agent: Added support for specifying metadata during service
  registration.
- agent: Added a new `discover-max-stale` config option to enable
  stale requests for service discovery endpoints.
- agent: (Consul Enterprise) Added a new option to the snapshot agent
  for configuring the S3 endpoint.
- dns: Introduced a new config param to limit the number of A/AAAA
  records returned.
- dns: Upgrade vendored DNS library to pick up bugfixes and
  improvements.
- server: Updated yamux library to pick up a performance improvement.
- server: Add near=\_ip support for prepared queries
- api: Add support for GZIP compression in HTTP responses.
- api: Add `IgnoreCheckIDs` to Prepared Query definition to allow
  temporarily bypassing faulty health checks

BUG FIXES:

- agent: Fixed an issue where the coordinate update endpoint was not
  correctly parsing the ACL token.
- agent: Fixed an issue where `consul monitor` couldn't be terminated
  until the first log line is delivered
- agent: Added warnings for when a node name isn't a valid DNS name
  and when the node name, a service name or service tags would exceed
  the allowed lengths for DNS names
- agent: Added truncation of TCP DNS responses to prevent errors for
  exceeding message size limits
- agent: Added -config-format flag to validate command to specify the
  syntax that should be used for parsing the config
- agent: HTTP Checks now report the HTTP method used instead of always
  reporting as a GET
- server: Fixed an issue where the leader could miss clean up after a
  leadership transition.
   2018-03-30 13:56:27 by Benny Siegert | Files touched by this commit (94) | Package updated
Log message:
Revbump all Go packages after 1.10.1 update.

ok wiz@ for committing during freeze
   2018-03-04 16:52:21 by Benny Siegert | Files touched by this commit (95) | Package updated
Log message:
Revbump all Go packages after Go 1.10 update.
   2018-02-27 12:37:44 by Filip Hajny | Files touched by this commit (2) | Package updated
Log message:
sysutils/consul: Update to 1.0.6. Simplify Makefile.

## consul 1.0.6
- agent: Fixed a panic when using the Azure provider for retry-join.
- agent: Fixed a panic when querying Consul's DNS interface over TCP.
   2018-02-08 13:58:32 by Filip Hajny | Files touched by this commit (2) | Package updated
Log message:
sysutils/consul: Update to 1.0.5.

SECURITY:

- dns: Updated DNS vendor library to pick up bug fix in the DNS server
  where an open idle connection blocks the accept loop.

FEATURES:

- agent: Added support for gRPC health checks that probe the standard
  gRPC health endpoint.

IMPROVEMENTS:

- agent: (Consul Enterprise) The `disable_update_check` option to
  disable Checkpoint now defaults to `true`
- build: Bumped Go version to 1.9.3.

BUG FIXES:

- agent: (Consul Enterprise) Fixed an issue where the snapshot agent's
  HTTP client config was being ignored in favor of the HTTP
  command-line flags.
- agent: Fixed an issue where health checks added to services with
  tags would cause extra periodic writes to the Consul servers, even
  if nothing had changed.
- agent: Fixed several areas where reading from catalog, health, or
  agent HTTP endpoints could make unintended mofidications to Consul's
  state in a way that would cause unnecessary anti-entropy syncs back
  to the Consul servers.
- agent: Fixed an issue where Serf events for failed Consul servers
  weren't being proactively processed by the RPC router.