open-nomad/client/consul/consul.go

package consul

import (
	"github.com/hashicorp/nomad/command/agent/consul"
)

// ConsulServiceAPI is the interface the Nomad Client uses to register and
// remove services and checks from Consul.
type ConsulServiceAPI interface {
	RegisterWorkload(*consul.WorkloadServices) error
	RemoveWorkload(*consul.WorkloadServices)
	UpdateWorkload(old, newTask *consul.WorkloadServices) error
	AllocRegistrations(allocID string) (*consul.AllocRegistration, error)
	UpdateTTL(id, output, status string) error
}
Refactor - wip 2018-06-11 20:33:18 +00:00			`package consul`
Refactor Consul Syncer into new ServiceClient Fixes #2478 #2474 #1995 #2294 The new client only handles agent and task service advertisement. Server discovery is mostly unchanged. The Nomad client agent now handles all Consul operations instead of the executor handling task related operations. When upgrading from an earlier version of Nomad existing executors will be told to deregister from Consul so that the Nomad agent can re-register the task's services and checks. Drivers - other than qemu - now support an Exec method for executing abritrary commands in a task's environment. This is used to implement script checks. Interfaces are used extensively to avoid interacting with Consul in tests that don't assert any Consul related behavior. 2017-02-01 00:43:57 +00:00
			`import (`
Fix alloc health with checks using interpolation Fixes an issue in which the allocation health watcher was checking for allocations health based on un-interpolated services and checks. Change the interface for retrieving check information from Consul to retrieving all registered services and checks by allocation. In the future this will allow us to output nicer messages. Fixes https://github.com/hashicorp/nomad/issues/2969 2017-08-07 22:54:05 +00:00			`"github.com/hashicorp/nomad/command/agent/consul"`
Refactor Consul Syncer into new ServiceClient Fixes #2478 #2474 #1995 #2294 The new client only handles agent and task service advertisement. Server discovery is mostly unchanged. The Nomad client agent now handles all Consul operations instead of the executor handling task related operations. When upgrading from an earlier version of Nomad existing executors will be told to deregister from Consul so that the Nomad agent can re-register the task's services and checks. Drivers - other than qemu - now support an Exec method for executing abritrary commands in a task's environment. This is used to implement script checks. Interfaces are used extensively to avoid interacting with Consul in tests that don't assert any Consul related behavior. 2017-02-01 00:43:57 +00:00			`)`

			`// ConsulServiceAPI is the interface the Nomad Client uses to register and`
			`// remove services and checks from Consul.`
			`type ConsulServiceAPI interface {`
client: improve group service stanza interpolation and check_re… (#6586) * client: improve group service stanza interpolation and check_restart support Interpolation can now be done on group service stanzas. Note that some task runtime specific information that was previously available when the service was registered poststart of a task is no longer available. The check_restart stanza for checks defined on group services will now properly restart the allocation upon check failures if configured. 2019-11-18 18:04:01 +00:00			`RegisterWorkload(*consul.WorkloadServices) error`
			`RemoveWorkload(*consul.WorkloadServices)`
			`UpdateWorkload(old, newTask *consul.WorkloadServices) error`
Fix alloc health with checks using interpolation Fixes an issue in which the allocation health watcher was checking for allocations health based on un-interpolated services and checks. Change the interface for retrieving check information from Consul to retrieving all registered services and checks by allocation. In the future this will allow us to output nicer messages. Fixes https://github.com/hashicorp/nomad/issues/2969 2017-08-07 22:54:05 +00:00			`AllocRegistrations(allocID string) (*consul.AllocRegistration, error)`
support script checks for task group services (#6197) In Nomad prior to Consul Connect, all Consul checks work the same except for Script checks. Because the Task being checked is running in its own container namespaces, the check is executed by Nomad in the Task's context. If the Script check passes, Nomad uses the TTL check feature of Consul to update the check status. This means in order to run a Script check, we need to know what Task to execute it in. To support Consul Connect, we need Group Services, and these need to be registered in Consul along with their checks. We could push the Service down into the Task, but this doesn't work if someone wants to associate a service with a task's ports, but do script checks in another task in the allocation. Because Nomad is handling the Script check and not Consul anyways, this moves the script check handling into the task runner so that the task runner can own the script check's configuration and lifecycle. This will allow us to pass the group service check configuration down into a task without associating the service itself with the task. When tasks are checked for script checks, we walk back through their task group to see if there are script checks associated with the task. If so, we'll spin off script check tasklets for them. The group-level service and any restart behaviors it needs are entirely encapsulated within the group service hook. 2019-09-03 19:09:04 +00:00			`UpdateTTL(id, output, status string) error`
Refactor Consul Syncer into new ServiceClient Fixes #2478 #2474 #1995 #2294 The new client only handles agent and task service advertisement. Server discovery is mostly unchanged. The Nomad client agent now handles all Consul operations instead of the executor handling task related operations. When upgrading from an earlier version of Nomad existing executors will be told to deregister from Consul so that the Nomad agent can re-register the task's services and checks. Drivers - other than qemu - now support an Exec method for executing abritrary commands in a task's environment. This is used to implement script checks. Interfaces are used extensively to avoid interacting with Consul in tests that don't assert any Consul related behavior. 2017-02-01 00:43:57 +00:00			`}`