CipherSpace Load Balancer - Revision history

Mathias: /* How to Modify the Load Balancer's Configuration. */

2017-08-03T09:53:13Z

How to Modify the Load Balancer's Configuration.

← Older revision		Revision as of 09:53, 3 August 2017
Line 222:		Line 222:
	# Clone the Load Balancer's Template in case you have to roll back.		# Clone the Load Balancer's Template in case you have to roll back.
	# Change the configuration in the new template by adding variables, removing variables or modifying existing variables.		# Change the configuration in the new template by adding variables, removing variables or modifying existing variables.
	# Terminate the old load balancer VM		# Terminate the old load balancer VM.
	# Instantiate the new template again.		# Instantiate the new template again.

Mathias: /* Basic Configuration */

2017-08-03T09:51:47Z

Basic Configuration

← Older revision		Revision as of 09:51, 3 August 2017
Line 89:		Line 89:

	The variable <code>SERVICE_X_IP_RANGE</code> <code>=</code> <code>{</code> <code>dotted notation</code><code>-</code><code>dotted notation</code><code>}</code> defines the IP addresses of the backend servers. This variable is '''mandatory'''.<br />		The variable <code>SERVICE_X_IP_RANGE</code> <code>=</code> <code>{</code> <code>dotted notation</code><code>-</code><code>dotted notation</code><code>}</code> defines the IP addresses of the backend servers. This variable is '''mandatory'''.<br />
	In our example <code>~~SERVICE_X_IP_RANGE~~</code> has the value <code>10.4.0.11-10.4.0.13</code>		In our example <code>SERVICE_0_IP_RANGE</code> has the value <code>10.4.0.11-10.4.0.13</code>

	The variable <code>SERVICE_X_BACKEND_PORT</code> <code>=</code> <code>{</code> <code>int</code> <code>}</code> defines the TCP port the backend servers are listening to. This variable is optional. If this variable isn't defined, the value of the variable <code>SERVICE_X_LISTEN_PORT</code> will be used instead.<br />		The variable <code>SERVICE_X_BACKEND_PORT</code> <code>=</code> <code>{</code> <code>int</code> <code>}</code> defines the TCP port the backend servers are listening to. This variable is optional. If this variable isn't defined, the value of the variable <code>SERVICE_X_LISTEN_PORT</code> will be used instead.<br />
	In our example <code>~~SERVICE_X_BACKEND_PORT~~</code> has the value <code>8080</code>		In our example <code>SERVICE_0_BACKEND_PORT</code> has the value <code>8080</code>

	So, our example will be configured as follows:		So, our example will be configured as follows:

Mathias: /* Health Checks */

2017-08-03T09:50:00Z

Health Checks

← Older revision		Revision as of 09:50, 3 August 2017
Line 126:		Line 126:
	By default, server health check only consist in trying to establish a TCP connection. You can add a complete HTTP request after an established TCP connection by adding the following variable:		By default, server health check only consist in trying to establish a TCP connection. You can add a complete HTTP request after an established TCP connection by adding the following variable:

	<code>SERVICE_X_CHECK_URI</code> <code>=</code> <code>{</code> <code>uri</code> <code>}</code>		<code>SERVICE_X_CHECK_URI</code> <code>=</code> <code>{</code> <code><uri></code> <code>}</code>

	where <code><uri></code>is the URI referenced in the HTTP requests.<br />		where <code><uri></code>is the URI referenced in the HTTP requests.<br />

Mathias: /* Basic Configuration */

2017-08-03T09:48:09Z

Basic Configuration

← Older revision		Revision as of 09:48, 3 August 2017
Line 88:		Line 88:
	In our example <code>SERVICE_0_LISTEN_PORT</code> has the value <code>80</code>		In our example <code>SERVICE_0_LISTEN_PORT</code> has the value <code>80</code>

	The variable <code>SERVICE_X_IP_RANGE</code> <code>=</code> <code>{</code> <code>dotted</code> <code>notation</code> <code>}</code> defines the IP addresses of the backend servers. This variable is '''mandatory'''.<br />		The variable <code>SERVICE_X_IP_RANGE</code> <code>=</code> <code>{</code> <code>dotted notation</code><code>-</code><code>dotted notation</code><code>}</code> defines the IP addresses of the backend servers. This variable is '''mandatory'''.<br />
	In our example <code>SERVICE_X_IP_RANGE</code> has the value <code>10.4.0.11-10.4.0.13</code>		In our example <code>SERVICE_X_IP_RANGE</code> has the value <code>10.4.0.11-10.4.0.13</code>

Line 100:		Line 100:
	SERVICE_0_IP_RANGE = 10.4.0.11-10.4.0.13		SERVICE_0_IP_RANGE = 10.4.0.11-10.4.0.13
	SERVICE_0_BACKEND_PORT = 8080</pre>		SERVICE_0_BACKEND_PORT = 8080</pre>

			==== Elastic Configuration ====

			Let's assume that we have currently three web servers running (as described in the previous section), but we plan to extend our web servers to a maximum of 50. In this case, we just need to put a wider range in the variable <code>SERVICE_X_IP_RANGE</code> as follows:

			<pre> SERVICE_0_IP_RANGE = 10.4.0.11-10.4.0.60</pre>

			The load balancer will be then configured to balance the load to these new servers as soon as they are available.

	==== Health Checks ====		==== Health Checks ====

Stoyan: /* HTTP only Variables */

2017-08-02T14:56:08Z

HTTP only Variables

← Older revision		Revision as of 14:56, 2 August 2017
Line 180:		Line 180:
	Default value is Null. This variable isn't mandatory.		Default value is Null. This variable isn't mandatory.
	* <code>SERVICE_X_SSL_OFFLOAD_CERT</code> <code>=</code> <code>{</code> <code>string</code> <code>}</code> defines the certificate chains to offload encrypted connections.<br />		* <code>SERVICE_X_SSL_OFFLOAD_CERT</code> <code>=</code> <code>{</code> <code>string</code> <code>}</code> defines the certificate chains to offload encrypted connections.<br />
	It has to be a string which contains the following files in PEM format: <code>~~chain~~</code>, <code>key</code>and <code>intermediate</code>. Order is not important. Default value is Null. This variable isn't mandatory.		It has to be a string which contains the following files in PEM format: <code>certificate</code>, <code>key</code>and <code>intermediate</code>. Order is not important. Default value is Null. This variable isn't mandatory.
	* <code>SERVICE_X_REDIRECT_TO_HTTPS</code> <code>=</code> <code>{</code> <code>True</code> <code>}</code> defines the presence of a 301 redirect from http to https.<br />		* <code>SERVICE_X_REDIRECT_TO_HTTPS</code> <code>=</code> <code>{</code> <code>True</code> <code>}</code> defines the presence of a 301 redirect from http to https.<br />
	Default value is Null. This variable isn't mandatory.		Default value is Null. This variable isn't mandatory.

Stoyan: /* Health Checks */

2017-08-02T14:52:03Z

Health Checks

← Older revision		Revision as of 14:52, 2 August 2017
Line 117:		Line 117:
	By default, server health check only consist in trying to establish a TCP connection. You can add a complete HTTP request after an established TCP connection by adding the following variable:		By default, server health check only consist in trying to establish a TCP connection. You can add a complete HTTP request after an established TCP connection by adding the following variable:

	<code>SERVICE_X_CHECK_URI</code> <code>=</code> <code>{</code> <code>~~string~~</code> <code>}</code>		<code>SERVICE_X_CHECK_URI</code> <code>=</code> <code>{</code> <code>uri</code> <code>}</code>

	where <code><uri></code>is the URI referenced in the HTTP requests.<br />		where <code><uri></code>is the URI referenced in the HTTP requests.<br />

Stoyan: /* Configure the Load Balancer */

2017-08-02T14:45:22Z

Configure the Load Balancer

← Older revision		Revision as of 14:45, 2 August 2017
Line 36:		Line 36:
	# Click on the "Network" tab		# Click on the "Network" tab
	#:[[file:lb_8.png\|500px\|border]]		#:[[file:lb_8.png\|500px\|border]]
	#:and select a Virtual Network for your NIC (the same network as ~~your other~~ VMs).		#:and select a Virtual Network for your NIC (the same network as the VMs which provide the service you would like to load balance).
	#:[[file:lb_9.png\|600px\|border]]		#:[[file:lb_9.png\|600px\|border]]
	#:<br />		#:<br />
	#:If your load balancer ~~is directly connected to the internet~~ (~~and not via a virtual router~~), you ~~should~~ add another NIC and attach it to the ~~Internet~~ Virtual Network.		#:If clients connect to your load balancer from a different network (Internet for example) you need to add another NIC and attach it to the appropriate Virtual Network.
	#:[[file:lb_10.png\|600px\|border]]		#:[[file:lb_10.png\|600px\|border]]
	#:<br />		#:<br />
Line 50:		Line 50:
	#:[[file:lb_13.png\|700px\|border]]		#:[[file:lb_13.png\|700px\|border]]
	#:<br />		#:<br />
	# If you have ~~added another NIC to your load balancer~~, you should ~~specify the new NIC as~~ default gateway by adding the variable <code>GATEWAY_IFACE</code>and assign it with the number of ~~your new~~ NIC (typically <code>1</code>).		# If you have 2 NICs, you should set default gateway by adding the variable <code>GATEWAY_IFACE</code>and assign it with the number of the NIC on which requests from clients are coming. (typically <code>1</code>).
	#:<code>GATEWAY_IFACE = 1</code>		#:<code>GATEWAY_IFACE = 1</code>
	#:<br />		#:<br />

Mathias: /* Start and Check the Load Balancer */

2017-07-27T10:20:56Z

Start and Check the Load Balancer

← Older revision		Revision as of 10:20, 27 July 2017
Line 203:		Line 203:
	# When the new VM is in the <code>RUNNING</code> state, click on the console icon [[file:lb_17.png\|25px]] to access the VM.		# When the new VM is in the <code>RUNNING</code> state, click on the console icon [[file:lb_17.png\|25px]] to access the VM.
	# In the console you will see the login prompt and after a while you will see wether the HAProxy configuration was successful or not. If not, terminate the VM, modify the variables in the template and re-instantiate the VM.		# In the console you will see the login prompt and after a while you will see wether the HAProxy configuration was successful or not. If not, terminate the VM, modify the variables in the template and re-instantiate the VM.
	[[file:lb_18.png\|700px\|border]]		#:[[file:lb_18.png\|700px\|border]]
			#:<br />

	== How to Modify the Load Balancer's Configuration. ==		== How to Modify the Load Balancer's Configuration. ==

Mathias: /* Start and Check the Load Balancer */

2017-07-27T10:06:10Z

Start and Check the Load Balancer

← Older revision		Revision as of 10:06, 27 July 2017
Line 198:		Line 198:
	#:[[file:lb_15.png\|500px\|border]]		#:[[file:lb_15.png\|500px\|border]]
	#:A new window will appear		#:A new window will appear
	#:[[file:lb_16.png\|~~700px~~\|border]]		#:[[file:lb_16.png\|600px\|border]]
	#:<br />		#:<br />
	# You can assign a name to your load balancer or leave the field empty. Click on "Instantiate" to start the instantiation.		# You can assign a name to your load balancer or leave the field empty. Click on "Instantiate" to start the instantiation.

Mathias: /* Start and Check the Load Balancer */

2017-07-27T10:02:20Z

Start and Check the Load Balancer

← Older revision		Revision as of 10:02, 27 July 2017
Line 201:		Line 201:
	#:<br />		#:<br />
	# You can assign a name to your load balancer or leave the field empty. Click on "Instantiate" to start the instantiation.		# You can assign a name to your load balancer or leave the field empty. Click on "Instantiate" to start the instantiation.
	# When the new VM is in the <code>RUNNING</code> state, click on the console icon [[file:lb_17.png\|25px] to access the VM.		# When the new VM is in the <code>RUNNING</code> state, click on the console icon [[file:lb_17.png\|25px]] to access the VM.
	# In the console you will see the login prompt and after a while you will see wether the HAProxy configuration was successful or not. If not, terminate the VM, modify the variables in the template and re-instantiate the VM.		# In the console you will see the login prompt and after a while you will see wether the HAProxy configuration was successful or not. If not, terminate the VM, modify the variables in the template and re-instantiate the VM.
	[[file:lb_18.png\|700px\|border]]		[[file:lb_18.png\|700px\|border]]