User talk:Jch/consul - Revision history

Zcrayfish: nowiki'd a dead link.

2023-08-28T01:52:32Z

nowiki'd a dead link.

← Older revision		Revision as of 01:52, 28 August 2023
Line 26:		Line 26:
	=== Web UI ===		=== Web UI ===

	One need to download and unpack https://dl.bintray.com/mitchellh/consul/0.5.0_web_ui.zip in some directory.<br/>		One need to download and unpack <nowiki>https://dl.bintray.com/mitchellh/consul/0.5.0_web_ui.zip</nowiki> in some directory.<br/>
	The contents of this zip file is a index.html with some js and css files in a subdirectory <pre>		The contents of this zip file is a index.html with some js and css files in a subdirectory <pre>
	Archive: 0.5.0_web_ui.zip		Archive: 0.5.0_web_ui.zip

2015-05-23T16:26:03Z

What if ?

← Older revision		Revision as of 16:26, 23 May 2015
Line 133:		Line 133:
	I plan to advertize available NBD with {"service": "nbd", "tags": ["<name>"]} ans access it with nbd:name.nbd.service.consul:name.<br/>		I plan to advertize available NBD with {"service": "nbd", "tags": ["<name>"]} ans access it with nbd:name.nbd.service.consul:name.<br/>
	''but before that, need to use new nbd format with nammes on an unique port instead of differentiation by port (old scheme)''		''but before that, need to use new nbd format with nammes on an unique port instead of differentiation by port (old scheme)''

			Is there a clean way to dynamically add a tag to a service on a given consul node without losing existing tags ?

	=== Cheks ===		=== Cheks ===

2015-05-14T08:40:01Z

Open questions

← Older revision		Revision as of 08:40, 14 May 2015
Line 159:		Line 159:

	=== Triggers ===		=== Triggers ===

			=== Open questions ===

			* How to know (from any node in the cluster) which is the active leader?
			** an alternative is to define an applicative leader as in https://consul.io/docs/guides/leader-election.html

	= envconsul =		= envconsul =

2015-05-14T08:36:45Z

Machines discovery

← Older revision		Revision as of 08:36, 14 May 2015
Line 107:		Line 107:

	List machines = <pre>consul members</pre> or <pre>curl localhost:8500/v1/catalog/nodes</pre>		List machines = <pre>consul members</pre> or <pre>curl localhost:8500/v1/catalog/nodes</pre>

	~~list PXEservers = servers in "consul members"~~

	~~get consul leader = ???~~

	=== Services discovery ===		=== Services discovery ===

2015-05-14T08:35:53Z

What if ?

← Older revision		Revision as of 08:35, 14 May 2015
Line 129:		Line 129:
	==== What if ? ====		==== What if ? ====

	What if I register a service service1 with tag tag1 on node node1,		What if I register a service service1 with tag tag1 on node node1,<br/>
	then I register a service service1 with tag tag2 on node2.		then I register a service service1 with tag tag2 on node2.<br/>
	then I register a service service1 with tag tag3 on node1?		then I register a service service1 with tag tag3 on node1?<br/>
			will the tags just add?<br/>
			''NO, the lastest registration overwrite previous one.''

	~~will the tags just add?~~		I plan to advertize available NBD with {"service": "nbd", "tags": ["<name>"]} ans access it with nbd:name.nbd.service.consul:name.<br/>
			''but before that, need to use new nbd format with nammes on an unique port instead of differentiation by port (old scheme)''
	I plan to advertize available NBD with {"service": "nbd", "tags": ["<name>"]} ans access it with nbd:name.nbd.service.consul:name.

	=== Cheks ===		=== Cheks ===

2015-05-14T04:21:37Z

Securing consul

← Older revision		Revision as of 04:21, 14 May 2015
Line 97:		Line 97:

	We will follow coredumb recommandations as on https://www.mauras.ch/securing-consul.html and based on sample config provided in the package.		We will follow coredumb recommandations as on https://www.mauras.ch/securing-consul.html and based on sample config provided in the package.

			With gossip encryption, we observe some flapping in the presence of nodes...

	== Usage ==		== Usage ==

2015-05-14T04:01:41Z

Configuration

← Older revision		Revision as of 04:01, 14 May 2015
Line 93:		Line 93:

	If an agent (or server) has several private IP addresses, one has to specify the address to be used in /etc/conf.d/consul (with -bind=<IP>). That address has to be reachable by all consul members!		If an agent (or server) has several private IP addresses, one has to specify the address to be used in /etc/conf.d/consul (with -bind=<IP>). That address has to be reachable by all consul members!

			=== Securing consul ===

			We will follow coredumb recommandations as on https://www.mauras.ch/securing-consul.html and based on sample config provided in the package.

	== Usage ==		== Usage ==

2015-05-14T01:28:16Z

Introduction

← Older revision		Revision as of 01:28, 14 May 2015
Line 10:		Line 10:
	Now in repo edge/testing		Now in repo edge/testing

	We will experiment to find the right spec to allocate the consul servers for 100 to 1000 agents.		We will experiment to find the right spec to allocate the consul servers for 100 to 1000 agents. For now, we have a 52 nodes cluster.

	We plan to orchestrate our VM fleet based on consul events, envconsul and consul-template. All with ash scripts and smart setup.		We plan to orchestrate our VM fleet based on consul events, envconsul and consul-template. All with ash scripts and smart setup.

2015-05-13T07:05:19Z

Install: web ui

@@ Line 23: / Line 23: @@
 apk add consul@testing
 </pre>
 == Configuration ==

2015-05-13T06:43:59Z

Services discovery

← Older revision		Revision as of 06:43, 13 May 2015
Line 94:		Line 94:
	curl http://localhost:8500/v1/catalog/service/<service> : Lists the nodes in a given service		curl http://localhost:8500/v1/catalog/service/<service> : Lists the nodes in a given service
	curl http://localhost:8500/v1/catalog/node/<node> : Lists the services provided by a node		curl http://localhost:8500/v1/catalog/node/<node> : Lists the services provided by a node
			</pre>

			For instance: <pre>
			http_proxy= curl http://localhost:8500/v1/catalog/services?pretty
	</pre>		</pre>