HashiCorp/Consul - Revision history

Pio2pio: Pio2pio moved page HashiCorp Consul to HashiCorp/Consul without leaving a redirect

2020-08-23T13:19:20Z

Pio2pio moved page HashiCorp Consul to HashiCorp/Consul without leaving a redirect

← Older revision	Revision as of 15:19, 23 August 2020
(No difference)

Pio2pio: /* Define a service */

2019-03-12T06:36:28Z

Define a service

← Older revision		Revision as of 08:36, 12 March 2019
Line 63:		Line 63:
	curl http://localhost:8500/v1/catalog/service/web		curl http://localhost:8500/v1/catalog/service/web
	curl 'http://localhost:8500/v1/health/service/web?passing'		curl 'http://localhost:8500/v1/health/service/web?passing'
			</source>


	;Updating Services		;Updating Services
Line 68:		Line 70:

	Alternatively, the HTTP API can be used to add, remove, and modify services dynamically.		Alternatively, the HTTP API can be used to add, remove, and modify services dynamically.
	~~</source>~~

	= References =		= References =

Pio2pio: /* Define a service */

2019-03-12T06:36:08Z

Define a service

← Older revision		Revision as of 08:36, 12 March 2019
Line 64:		Line 64:
	curl 'http://localhost:8500/v1/health/service/web?passing'		curl 'http://localhost:8500/v1/health/service/web?passing'

			;Updating Services
			Service definitions can be updated by changing configuration files and sending a SIGHUP to the agent. This lets you update services without any downtime or unavailability to service queries.

			Alternatively, the HTTP API can be used to add, remove, and modify services dynamically.
	</source>		</source>

	= References =		= References =
	*[https://blog.fraq.io/tech/consul-template/ A practical and simple consul-template example] Tutorial with docker restart based on a template change		*[https://blog.fraq.io/tech/consul-template/ A practical and simple consul-template example] Tutorial with docker restart based on a template change

Pio2pio: /* References */

2019-03-12T06:34:51Z

References

@@ Line 48: / Line 48: @@
 </source>
 = References =
 *[https://blog.fraq.io/tech/consul-template/ A practical and simple consul-template example] Tutorial with docker restart based on a template change

Pio2pio: /* Run consul agent */

2019-03-11T20:23:52Z

Run consul agent

← Older revision		Revision as of 22:23, 11 March 2019
Line 35:		Line 35:


			Basic cluster checks and calls
	<source lang=bash>		<source lang=bash>
	consul members -details		consul members -details

Pio2pio: /* Run consul */

2019-03-11T20:23:10Z

Run consul

← Older revision		Revision as of 22:23, 11 March 2019
Line 6:		Line 6:
	</source>		</source>

	= Run consul =		= Run consul agent =
	You need run at least one <tt>consul server</tt> 3-5 are recommended.		You need run at least one <tt>consul server</tt> 3-5 are recommended.
	All other agents do run in a <tt>client</tt> mode, it's very light weight process that :		All other agents do run in a <tt>client</tt> mode, it's very light weight process that :
Line 16:		Line 16:
	Run consul in dev mode where single server is also acting as a client:		Run consul in dev mode where single server is also acting as a client:
	<source lang=bash>		<source lang=bash>
	consul agent -dev -node <~~consul_srv_name~~>		consul agent -dev -node <consul_hostname>
	# -node is optional as by default hostname is used, but for OSX with period in it will case problems with dns queries		# -node is optional as by default hostname is used, but for OSX with period in it will case problems with dns queries
	</source>		</source>


			Consul will start listenig on following ports
	<source lang=bash>		<source lang=bash>
	~~Consult will start listenig on following ports~~
	Netid State Local Address:Port		Netid State Local Address:Port
	udp UNCONN 127.0.0.1:8301		udp UNCONN 127.0.0.1:8301
Line 36:		Line 36:

	<source lang=bash>		<source lang=bash>
	consul members		consul members -details
	Node Address Status Type Build Protocol DC Segment		Node Address Status Type Build Protocol DC Segment
	u18gui-1 127.0.0.1:8301 alive server 1.4.3 2 dc1 <all>		u18gui-1 127.0.0.1:8301 alive server 1.4.3 2 dc1 <all>

			# API call
			curl localhost:8500/v1/catalog/nodes

			# DNS interface, using dns lookups, consuls listenig on udp/tcp:8600 port
			dig @127.0.0.1 -p 8600 <consul_hostname>.node.consul
	</source>		</source>

Pio2pio: /* Run consul */

2019-03-11T20:14:59Z

Run consul

@@ Line 18: / Line 18: @@
 consul agent -dev -node <consul_srv_name>
 # -node is optional as by default hostname is used, but for OSX with period in it will case problems with dns queries
 consul members
 </source>

Pio2pio: /* Install */

2019-03-11T19:54:22Z

Install

@@ Line 4: / Line 4: @@
 unzip consul_1.4.3_linux_amd64.zip
 sudo mv consul /usr/bin
 </source>

Pio2pio at 19:39, 11 March 2019

2019-03-11T19:39:59Z

← Older revision		Revision as of 21:39, 11 March 2019
Line 1:		Line 1:
			= Install =
			<source lang=bash>
			wget https://releases.hashicorp.com/consul/1.4.3/consul_1.4.3_linux_amd64.zip
			unzip consul_1.4.3_linux_amd64.zip
			sudo mv consul /usr/bin
			</source>

	= References =		= References =
	*[https://blog.fraq.io/tech/consul-template/ A practical and simple consul-template example] Tutorial with docker restart based on a template change		*[https://blog.fraq.io/tech/consul-template/ A practical and simple consul-template example] Tutorial with docker restart based on a template change

Pio2pio: /* References */

2018-09-25T06:55:30Z

References

← Older revision		Revision as of 08:55, 25 September 2018
Line 1:		Line 1:
	= References =		= References =
	*[https://blog.fraq.io/tech/consul-template/ A practical and simple consul-template example] Tutorial with docker restart based on a template change		*[https://blog.fraq.io/tech/consul-template/ A practical and simple consul-template example] Tutorial with docker restart based on a template change
			*[https://github.com/hashicorp/consul-template Consul template] Official Git repository

	[[Category: linux]] [[Category: hashicorp]]		[[Category: linux]] [[Category: hashicorp]]