92f579891c
Remove lie from comment
2016-11-18 11:05:22 -08:00
fc1f557a36
Fix incorrect lock usage around consul maps
2016-11-18 10:12:02 -08:00
da9a8bbcef
Fix SyncNow
2016-11-18 10:12:02 -08:00
57e5e03ccc
New chaos test to exercise consul syncer
2016-11-18 10:12:02 -08:00
393efe2579
Switch syncer tests to use embedded consul
2016-11-15 10:22:25 -08:00
7367d6adb4
Removing warn msg
2016-09-04 17:22:49 -07:00
ec96e03563
Query consul without helpers in test to be safe
2016-08-31 14:14:17 -07:00
aa8cbe777a
Make comment more precise
2016-08-31 10:43:55 -07:00
7f6b5f4d2a
Fix error message when querying consul fails
2016-08-31 10:42:51 -07:00
db1cf6385e
Assert syncer state is consistent with consul's state
2016-08-31 09:19:54 -07:00
f6bf81270d
Remove extra consul service tracking entirely
...
Instead just remove all associated services on shutdown.
2016-08-30 17:10:15 -07:00
27912a95d6
Fix old services not getting removed from consul on update
...
Fixes #1661
2016-08-30 16:36:42 -07:00
ce4d236a40
Fixed CR defects
2016-08-24 01:33:44 +03:00
10cc50ad29
First attemt to fix issue #1636
2016-08-23 19:09:20 +03:00
4683aa3dc6
Cleaning up some code
2016-08-16 15:22:26 -07:00
69bc3a8fc8
Add support for initial check status
2016-08-16 12:05:15 -07:00
7d0fb58f03
Add a test for query string support
2016-08-11 12:22:46 -07:00
c651cbbfd6
Add error handling to check registration
2016-08-11 11:49:48 -07:00
f47a543a4d
Add support for query strings in check paths
2016-08-11 11:27:29 -07:00
c203885352
consul syncer uses multi-error
2016-08-09 12:24:50 -07:00
48b9684b1e
Using net.JoinHostPort instead of handcrafting addrs
2016-07-08 16:45:14 -07:00
b180223f4b
Allowing ports to be overriden in check definitions
2016-07-08 14:14:25 -07:00
871a31a8ec
Teach config.ConsulConfig how to construct a consulapi TLS client.
...
Said differently, centralize the creation of consul's client config
in one place and use it everywhere.
2016-06-16 22:51:06 -07:00
59c54e9aeb
Fix tests, don't take the address of DefaultConsulCommand()
2016-06-16 21:21:39 -07:00
d17af396ca
Create config.DefaultConsulConfig()
2016-06-16 20:41:05 -07:00
10ce8f27d4
Temporarily disable various syncer checks due to the API changes made earlier today.
2016-06-13 19:52:17 -07:00
a54b4e08f8
Drive-by comment correction
2016-06-13 18:14:50 -07:00
4b04e503f3
address comments
2016-06-13 17:32:18 -07:00
8bbf4a55e5
Fix IDs and domain scoping
2016-06-13 16:30:58 -07:00
2e10458367
Removing unwated line of code
2016-06-13 15:37:55 +02:00
d019d8ef8e
implemented reconciliation of unwanted services
2016-06-13 14:52:26 +02:00
232654cdee
register checks
2016-06-12 21:28:56 -07:00
a82c2bb058
Do not reconcile in client and cleanup executor a bit
2016-06-12 18:22:07 -07:00
c68d23b7d6
Merge pull request #1264 from hashicorp/b-rename-services
...
Rename ConsulService back to Service
2016-06-12 16:44:49 -07:00
751b2e1bcb
Remove initial delay of registering services with consul
2016-06-13 01:42:56 +02:00
8e231fa382
Rename ConsulService back to Service
2016-06-12 16:36:49 -07:00
917766a3df
Prefer `%+q` over `%q` in log messages.
2016-06-11 18:17:20 -04:00
bbd8dfa798
goling(1) compliance pass (e.g. Rpc* -> RPC)
2016-06-10 23:38:28 -04:00
bc771d35df
Query for the Nomad service across multiple Consul datacenters.
2016-06-10 23:05:14 -04:00
d99467ef5e
Always create a consul.Syncer. Use a default Consul Config if necessary.
2016-06-10 15:55:27 -04:00
f6a0459ae5
Always create a consul.Syncer. Use a default Consul Config if necessary.
2016-06-10 15:55:27 -04:00
447fe59fd2
Hand wave over the syncer tests atm, these will be fixed shortly.
2016-06-10 15:54:39 -04:00
fa7285cb5b
Don't spam the consul if Consul is not available.
...
Log once when Consul goes away, and log when Consul comes back.
2016-06-10 15:54:39 -04:00
a2109af862
Properly cover Syncer attributes with the registryLock.
...
trackedServices, delegateChecks, trackedChecks, and checkRunners
should all be covered. This lock needs to be reasonably narrow and
can't use defer due to possible recursive locking concerns further
downstream from the call sites.
2016-06-10 15:54:39 -04:00
f9b561b52f
On Syncer Shutdown, remove all services that match a Syncer's prefix.
2016-06-10 15:54:39 -04:00
57e084e4df
Sync checks with Consul by comparing the AgentCheckReg w/ ConsulService
...
The source of truth is the local Nomad Agent. Any checks are not local that
have a matching prefix are removed. Changed checks are re-registered
and missing checks are re-added.
2016-06-10 15:54:39 -04:00
197feae679
Sync services with Consul by comparing the AgentServiceReg w/ ConsulService
...
The source of truth is the local Nomad Agent. Any services not local that
have a matching prefix are removed. Changed services are re-registered
and missing services are re-added.
2016-06-10 15:54:39 -04:00
9a223936bb
Generate and sync Consul ServiceIDs consistently
2016-06-10 15:54:39 -04:00
bcad11cc2a
Rename runChecks to consulAvailable
...
Apologies in advance for the variable thrash, the fingerprinter is
no longer used to gate whether or not Consul is available any more.
2016-06-10 15:54:39 -04:00
efe00d2ccd
Update Syncer.Run() to call SyncServices().
2016-06-10 15:54:39 -04:00
83775c5c8b
Add "Service Groups" to the Syncer.
...
Now the right way to register services with the Syncer is to call
`SetServices(groupName, []*services)`. This was required to allow
the Syncer to sync either the Client, Server, or Both using a
single Syncer.
2016-06-10 15:54:39 -04:00
06e5e615a8
Rename command/agent/consul/sync.go to syncer.go
2016-06-10 15:54:39 -04:00
7956eb0c80
Rename structs.Task's `Service` attribute to `ConsulService`
2016-06-10 15:54:39 -04:00
05a2b9528c
Remove Syncer.registerService()
...
This call is obsolete by a future commit that changes the canonical
source of truth to be consul.AgentServiceRegistration structs, which
means it is not necessary to construct AgentServiceRegistration
objects every time a registration is made, we just reuse the existing
object.
2016-06-10 15:54:39 -04:00
8c813630e6
Move package client/consul/sync to command/agent/consul.
...
This has been done to allow the Server and Client to reuse the same
Syncer because the Agent may be running Client, Server, or both
simultaneously and we only want one Syncer object alive in the agent.
2016-06-10 15:54:39 -04:00
Michael Schurter