Deployment and Security: Difference between revisions

From Lingoport Wiki
Jump to navigation Jump to search
← Older editNewer edit →
Rdaly (talk | contribs)
4,499 edits
No edit summary
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]]

Revision as of 22:21, 26 November 2019

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.


  • 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.

Ports

  • Jenkins is accessed via
    • port 80 or 443
    • 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.
    • 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.

Other aspects

  • Jenkins installation requires access to the Jenkins update site, http://updates.jenkins-ci.org
  • Dashboard may require access to the SonarQube update site, http://update.sonarsource.org
  • Notifications are sent using an SMTP account: The system must allow access to an SMTP server (e.g. smtp.gmail.com for Google)
Retrieved from "https://wiki.lingoport.com/index.php?title=Deployment_and_Security&oldid=93865"