Localyzer Machine Translation through a Proxy Server - Revision history

Masnes: /* Rational */

2020-11-05T21:13:04Z

Rational

← Older revision		Revision as of 21:13, 5 November 2020
Line 1:		Line 1:
	= ~~Rational~~ =		= Rationale =

	A proxy Server may be used for Localyzer Machine Translation through '''Amazon Translate''' if necessary for IT/Network/Security requirements. Only Amazon Translate is supported as of 2020-11-05.		A proxy Server may be used for Localyzer Machine Translation through '''Amazon Translate''' if necessary for IT/Network/Security requirements. Only Amazon Translate is supported as of 2020-11-05.

Masnes at 20:12, 5 November 2020

2020-11-05T20:12:18Z

← Older revision		Revision as of 20:12, 5 November 2020
Line 1:		Line 1:
	= Rational =		= Rational =

	A proxy Server may be used for Localyzer Machine Translation through '''~~AWS~~''' if necessary for IT/Network/Security requirements.		A proxy Server may be used for Localyzer Machine Translation through '''Amazon Translate''' if necessary for IT/Network/Security requirements. Only Amazon Translate is supported as of 2020-11-05.

	This is done by setting the ''''https_proxy'''' environment variable. Another variable, 'http_proxy', is available for http connections, but will not be needed for use with Amazon Translate.		This is done by setting the ''''https_proxy'''' environment variable. Another variable, 'http_proxy', is available for http connections, but will not be needed for use with Amazon Translate.
Line 66:		Line 66:
	If you're able to connect to the proxy via telnet, you're able to use the proxy to get your remote ip from https://canhazip.com, and if the result you get from https://canhazip.com via the proxy is different than without the proxy, then you are ready to proceed.		If you're able to connect to the proxy via telnet, you're able to use the proxy to get your remote ip from https://canhazip.com, and if the result you get from https://canhazip.com via the proxy is different than without the proxy, then you are ready to proceed.

	= Defining the Proxy for use with Localyzer ~~AWS Machine~~ Translate =		= Defining the Proxy for use with Localyzer Amazon Translate =

	To set a proxy server, define the environment variable "https_proxy" prior to running Localyzer with ~~AWS Machine Translation~~. Through Jenkins, the easiest way to do so is:		To set a proxy server, define the environment variable "https_proxy" prior to running Localyzer with Amazon Translate. Through Jenkins, the easiest way to do so is:

	: Manage Jenkins -> (Goes to a new page)		: Manage Jenkins -> (Goes to a new page)
Line 139:		Line 139:
	You are now using an https proxy!		You are now using an https proxy!

	Please see [[Machine Translation]] for details of Localyzer Machine Translation. Proxy configurations have been validated with ~~the~~ '''~~AWS~~''' ~~MT Vendor~~. It will take effect automatically as long as the https_proxy environment variable is set.		Please see [[Machine Translation]] for details of Localyzer Machine Translation. Proxy configurations have been validated with '''Amazon Translate'''. It will take effect automatically as long as the https_proxy environment variable is set.

Masnes at 20:08, 5 November 2020

2020-11-05T20:08:36Z

@@ Line 4: / Line 4: @@
 This is done by setting the ''''https_proxy'''' environment variable. Another variable, 'http_proxy', is available for http connections, but will not be needed for use with Amazon Translate.
 = Proxy Validation =
@@ Line 10: / Line 36: @@
 Test steps (example proxy used is http://masnes.testproxy.internal.lingoport.io:3128):
-* SSH to your system
+* SSH to the Lingoport Suite System
 * Install 'telnet', if it is not already present <code>sudo yum install telnet</code>
 * Validate that you can connect to your proxy server, while keeping proxy settings clear - for now:

Masnes: /* Proxy Validation */

2020-11-04T21:38:44Z

Proxy Validation

← Older revision		Revision as of 21:38, 4 November 2020
Line 20:		Line 20:
	::: <code>Connected to masnes.testproxy.internal.lingoport.io.</code>		::: <code>Connected to masnes.testproxy.internal.lingoport.io.</code>
	::: <code>Escape character is '^]'.</code>		::: <code>Escape character is '^]'.</code>
	::: '''Note:''' <code>Enter</code> will quit and return you to your terminal.		::: '''Note:'''After connection is established, <code>Enter</code> will quit and return you to your terminal. If connection takes a while, use <code>Ctrl-C</code> instead.
	:: If the connection '''takes more than 5 seconds''', you may '''not''' be able to connect to the proxy. '''Please check your security groups / firewall / networking settings before continuing!'''		:: If the connection '''takes more than 5 seconds''', you may '''not''' be able to connect to the proxy. '''Please check your security groups / firewall / networking settings before continuing!'''
	* Next, as a comparison point, try curling to an external site that will return your ip address, without using the proxy settings yet.		* Next, as a comparison point, try curling to an external site that will return your ip address, without using the proxy settings yet.

Masnes: /* Defining the Proxy for use with Localyzer AWS Machine Translate */

2020-11-04T21:33:57Z

Defining the Proxy for use with Localyzer AWS Machine Translate

← Older revision		Revision as of 21:33, 4 November 2020
Line 58:		Line 58:
	[[File:Jenkins-config-env-https proxy.png]]		[[File:Jenkins-config-env-https proxy.png]]

	Click 'Save' ~~to apply your changes~~.		Click either 'Save' or 'Apply' once you are finished.

	= Validating the Proxy through Jenkins =		= Validating the Proxy through Jenkins =

Masnes: /* Defining the Proxy for use with Localyzer AWS Machine Translate */

2020-11-04T21:33:08Z

Defining the Proxy for use with Localyzer AWS Machine Translate

← Older revision		Revision as of 21:33, 4 November 2020
Line 57:		Line 57:

	[[File:Jenkins-config-env-https proxy.png]]		[[File:Jenkins-config-env-https proxy.png]]

			Click 'Save' to apply your changes.

	= Validating the Proxy through Jenkins =		= Validating the Proxy through Jenkins =

Masnes: /* Proxy Validation */

2020-11-04T21:29:56Z

Proxy Validation

← Older revision		Revision as of 21:29, 4 November 2020
Line 7:		Line 7:
	= Proxy Validation =		= Proxy Validation =

	It is recommended that you validate you have access to ~~they~~ proxy you'll use, from your system, prior to enabling it.		It is recommended that you validate you have access to the proxy you'll use, from your system, prior to enabling it.

	Test steps (example proxy used is http://masnes.testproxy.internal.lingoport.io:3128):		Test steps (example proxy used is http://masnes.testproxy.internal.lingoport.io:3128):

Masnes at 21:23, 4 November 2020

2020-11-04T21:23:04Z

← Older revision		Revision as of 21:23, 4 November 2020
Line 40:		Line 40:
	If you're able to connect to the proxy via telnet, you're able to use the proxy to get your remote ip from https://canhazip.com, and if the result you get from https://canhazip.com via the proxy is different than without the proxy, then you are ready to proceed.		If you're able to connect to the proxy via telnet, you're able to use the proxy to get your remote ip from https://canhazip.com, and if the result you get from https://canhazip.com via the proxy is different than without the proxy, then you are ready to proceed.

	= Defining the Proxy for use with ~~LRM~~ AWS Machine Translate =		= Defining the Proxy for use with Localyzer AWS Machine Translate =

	To set a proxy server, define the environment variable "https_proxy" prior to running ~~LRM~~ with AWS Machine Translation. Through Jenkins, the easiest way to do so is:		To set a proxy server, define the environment variable "https_proxy" prior to running Localyzer with AWS Machine Translation. Through Jenkins, the easiest way to do so is:

	: Manage Jenkins -> (Goes to a new page)		: Manage Jenkins -> (Goes to a new page)

Masnes: /* Validating the Proxy through Jenkins */

2020-11-04T20:14:16Z

Validating the Proxy through Jenkins

← Older revision		Revision as of 20:14, 4 November 2020
Line 111:		Line 111:
	You are now using an https proxy!		You are now using an https proxy!

	Please see [[Machine Translation]] for details of Localyzer Machine Translation. Proxy configurations have been validated with the '''AWS''' MT Vendor.		Please see [[Machine Translation]] for details of Localyzer Machine Translation. Proxy configurations have been validated with the '''AWS''' MT Vendor. It will take effect automatically as long as the https_proxy environment variable is set.

Masnes: /* Proxy Validation */

2020-11-04T20:10:54Z

Proxy Validation

← Older revision		Revision as of 20:10, 4 November 2020
Line 21:		Line 21:
	::: <code>Escape character is '^]'.</code>		::: <code>Escape character is '^]'.</code>
	::: '''Note:''' <code>Enter</code> will quit and return you to your terminal.		::: '''Note:''' <code>Enter</code> will quit and return you to your terminal.
	:: If the connection '''takes more than 5 seconds''', you may '''not''' be able to connect to the proxy. Please check your security groups / firewall / networking settings before continuing!		:: If the connection '''takes more than 5 seconds''', you may '''not''' be able to connect to the proxy. '''Please check your security groups / firewall / networking settings before continuing!'''
	* Next, as a comparison point, try curling to an external site that will return your ip address, without using the proxy settings yet.		* Next, as a comparison point, try curling to an external site that will return your ip address, without using the proxy settings yet.
	:: Here, we use 'https://canhazip.com' as the external site. We set a timeout in case the connection is blocked.		:: Here, we use 'https://canhazip.com' as the external site. We set a timeout in case the connection is blocked.