Deployment and Security - Revision history

Masnes: /* Ports */

2020-01-22T23:11:02Z

Ports

@@ Line 13: / Line 13: @@
 = Ports =
-* Jenkins is accessed via
+Please see [[Deployment_Scenarios#External_Access_and_Ports |External Access and Ports]].
 = Other aspects =

Rdaly: /* Ports */

2019-11-26T22:23:58Z

Ports

← Older revision		Revision as of 22:23, 26 November 2019
Line 25:		Line 25:
	* Access for the Lingoport (or internal) installation team is typically done over SSH / via PuTTY.		* Access for the Lingoport (or internal) installation team is typically done over SSH / via PuTTY.
	** Alternately, it may be done through GoToMeeting/Webex screensharing between a Lingoport engineer and a customer engineer. This process may be significantly slower.		** Alternately, it may be done through GoToMeeting/Webex screensharing between a Lingoport engineer and a customer engineer. This process may be significantly slower.
	* The system must be able to access https://globalyzer.com.		* The system must be able to access https://www.globalyzer.com.

	= Other aspects =		= Other aspects =

Rdaly: /* Ports */

2019-11-26T22:23:04Z

Ports

← Older revision		Revision as of 22:23, 26 November 2019
Line 22:		Line 22:
	** port 21 for FTP or		** port 21 for FTP or
	** port 22 for SFTP.		** port 22 for SFTP.
			** Other ports for different vendors
	* Access for the Lingoport (or internal) installation team is typically done over SSH / via PuTTY.		* Access for the Lingoport (or internal) installation team is typically done over SSH / via PuTTY.
	** Alternately, it may be done through GoToMeeting/Webex screensharing between a Lingoport engineer and a customer engineer. This process may be significantly slower.		** Alternately, it may be done through GoToMeeting/Webex screensharing between a Lingoport engineer and a customer engineer. This process may be significantly slower.

Rdaly at 22:21, 26 November 2019

2019-11-26T22:21:52Z

← Older revision		Revision as of 22:21, 26 November 2019
Line 1:		Line 1:
	~~= Introduction =~~
	A number of actors need access to the [[Terms_and_Definitions\|Dashboard]] and [[Terms_and_Definitions\|Jenkins]]. In addition, installation and configuration require some basic items, such as access to Jenkins plugins sites and [[Terms_and_Definitions \|SonarQube]] plugin site, SMTP email to send notifications, and SSH access for those in charge of setting up the system.

	= Typical Deployment and Ports =		= Typical Deployment of the Lingoport Suite and Ports =
	Setting up the Suite on a Customer's system can be done in many ways, as shown in the different deployment scenarios. The following is meant to show the necessary access to the system.		Setting up the Suite on a Customer's system can be done in many ways, as shown in the different deployment scenarios. The following is meant to show the necessary access to the system.


			* The code repository needs to be able to work with the Continuous Globalization Server. This is done through the Jenkins jobs and Lingobot.
			* The Continuous Globalization Server needs to be able to access the Globalyzer rulesets that are located either on our hosted server or on a local server.
			* The Continuous Globalization Server needs to be able to send and receive resource files with the Translation Management System.
			** The resource files are also stored in the code repository.
			* Additionally, there are administrative needs for Continuous Globalization Server to be able to access Jenkins plugins, SMTP email, and SSH access.

	[[File:Deployment - Wiki.gif\|500px]]		[[File:Deployment - Wiki.gif\|500px]]

Olibouban: /* Ports */

2018-07-11T19:46:10Z

Ports

← Older revision		Revision as of 19:46, 11 July 2018
Line 9:		Line 9:

	= Ports =		= Ports =
	* Jenkins is accessed via port 8080		* Jenkins is accessed via
	* Lingoport Dashboard is accessed via port 9000		** port 80 or 443
	* The Translation Vendor may be accessed by different means, for instance port 21 for FTP or port 22 for SFTP.		** port 8080 if installed prior to May 2018
			* Lingoport Dashboard is accessed via
			** port 80 or 443
			** port 9000 if installed prior to May 2018
			* The Translation Vendor may be accessed by different means, for instance
			** port 21 for FTP or
			** port 22 for SFTP.
	* Access for the Lingoport (or internal) installation team is typically done over SSH / via PuTTY.		* Access for the Lingoport (or internal) installation team is typically done over SSH / via PuTTY.
	** Alternately, it may be done through GoToMeeting/Webex screensharing between a Lingoport engineer and a customer engineer. This process may be significantly slower.		** Alternately, it may be done through GoToMeeting/Webex screensharing between a Lingoport engineer and a customer engineer. This process may be significantly slower.

Olibouban: /* Typical Deployment and Ports */

2018-07-11T19:44:27Z

Typical Deployment and Ports

← Older revision		Revision as of 19:44, 11 July 2018
Line 6:		Line 6:


			[[File:Deployment - Wiki.gif\|500px]]
	*The Customer's systems are shown in Light Blue; <b>CentOS</b> for the main system where [[~~Terms_and_Definitions \|Jenkins]] and [[Terms_and_Definitions\|Dashboard]] reside.~~
	*Access from outside the Customer's system are shown in Light Green.

	~~[[Image~~:Deployment ~~and Security~~.gif]]

	= Ports =		= Ports =

Masnes: /* Ports */

2017-11-28T21:38:55Z

Ports

← Older revision		Revision as of 21:38, 28 November 2017
Line 16:		Line 16:
	* Lingoport Dashboard is accessed via port 9000		* Lingoport Dashboard is accessed via port 9000
	* The Translation Vendor may be accessed by different means, for instance port 21 for FTP or port 22 for SFTP.		* The Translation Vendor may be accessed by different means, for instance port 21 for FTP or port 22 for SFTP.
	* Access for the Lingoport (or internal) installation team is typically done over SSH / via PuTTY.		* Access for the Lingoport (or internal) installation team is typically done over SSH / via PuTTY.
			** Alternately, it may be done through GoToMeeting/Webex screensharing between a Lingoport engineer and a customer engineer. This process may be significantly slower.
	* The system must be able to access https://globalyzer.com.		* The system must be able to access https://globalyzer.com.

Masnes: /* Ports */

2017-02-14T23:01:34Z

Ports

← Older revision		Revision as of 23:01, 14 February 2017
Line 16:		Line 16:
	* Lingoport Dashboard is accessed via port 9000		* Lingoport Dashboard is accessed via port 9000
	* The Translation Vendor may be accessed by different means, for instance port 21 for FTP or port 22 for SFTP.		* The Translation Vendor may be accessed by different means, for instance port 21 for FTP or port 22 for SFTP.
	* Access for the Lingoport (or internal) installation team ~~can be~~ done ~~in many ways, such as~~ SSH ~~for Telnet or Putty~~.		* Access for the Lingoport (or internal) installation team is typically done over SSH / via PuTTY.
	* The system must be able to access https://globalyzer.com.		* The system must be able to access https://globalyzer.com.

Rdaly: /* Introduction */

2016-12-22T16:37:30Z

Introduction

← Older revision		Revision as of 16:37, 22 December 2016
Line 1:		Line 1:
	= Introduction =		= Introduction =
	A number of actors need access to the [[Terms_and_Definitions\|Dashboard]] and [[Terms_and_Definitions\|Jenkins]. In addition, installation and configuration require some basic items, such as access to Jenkins plugins sites and [[Terms_and_Definitions \|SonarQube]] plugin site, SMTP email to send notifications, and SSH access for those in charge of setting up the system.		A number of actors need access to the [[Terms_and_Definitions\|Dashboard]] and [[Terms_and_Definitions\|Jenkins]]. In addition, installation and configuration require some basic items, such as access to Jenkins plugins sites and [[Terms_and_Definitions \|SonarQube]] plugin site, SMTP email to send notifications, and SSH access for those in charge of setting up the system.

	= Typical Deployment and Ports =		= Typical Deployment and Ports =

Rdaly: /* Typical Deployment and Ports */

2016-12-22T16:25:33Z

Typical Deployment and Ports

← Older revision		Revision as of 16:25, 22 December 2016
Line 7:		Line 7:


	*The Customer's systems are shown in Light Blue; <b>CentOS</b> for the main system where Jenkins and Dashboard reside.		*The Customer's systems are shown in Light Blue; <b>CentOS</b> for the main system where [[Terms_and_Definitions \|Jenkins]] and [[Terms_and_Definitions\|Dashboard]] reside.
	*Access from outside the Customer's system are shown in Light Green.		*Access from outside the Customer's system are shown in Light Green.