Categoria:Tinki - Historial de revisió

Joan a 14:41, 21 març 2018

2018-03-21T14:41:53Z

← Versió més antiga	Revisió del 14:41, 21 març 2018
Línia 1:	Línia 1:
		Information about the TINKI project for Karl Mayer

Joan: Pàgina blanquejada

2018-03-21T14:40:00Z

Pàgina blanquejada

← Versió més antiga		Revisió del 14:40, 21 març 2018
Línia 1:		Línia 1:
	~~= tinki-team =~~

	To install and run the stack, execute <code>docker-compose up -d</code> from the project folder. In a similar fashion, use <code>docker-compose down</code> to halt the services. To backup the whole stack use the <code>backup-all.sh</code> script.

	~~<pre>ssh user@fedora-atomic.cadt.com -p 2222~~
	~~cd /home/tinki-team~~
	~~docker-compose up -d~~
	~~bash ./backup-all.sh</pre>~~
	~~Inside the container server, the stack should be located at <code>/home/tinki-team</code> holding a <code>docker-compose.yml</code> manifest with the following services:~~

	* Artifactory HTTP: http://fedora-atomic.cadt.com:8103
	* Gitlab HTTP: http://fedora-atomic.cadt.com:8101
	* Gitlab SSH: http://fedora-atomic.cadt.com:22
	* Jenkins HTTP: http://fedora-atomic.cadt.com:8080
	* Jira HTTP: http://fedora-atomic.cadt.com:8102

	~~== Artifactory ==~~

	The Artifactory service exposes its web interface on '''port 8103'''. A full system backup can be done via the service's API. Backup settings need to be [https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-ExportSystemSettingsExample retrieved] and sent back via [https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-ExportSystem POST], as explained in the official guide. Similarly, to restore the system, [https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-ImportSystemSettingsExample retrieve] the restoration settings and send them back via [https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-FullSystemImport POST], as shown in Artifactory's API guide. The current backup script will save the copy inside the container's <code>/tmp/backup</code> folder, and sync it with the host <code>/srv/data/artifactory</code>. Logs can be found on <code>/opt/jfrog/artifactory/logs</code> and are linked to the host's <code>/srv/log/artifactory</code> folder.

	~~<pre>bash ./artifactory/backup.sh</pre>~~
	~~== Gitlab ==~~

	The Gitlab service exposes its web interface on '''port 8101''', and also '''port 22''' for Git's SSH operations. Backup information can be found in their [https://docs.gitlab.com/ce/raketasks/backup_restore.html#creating-a-backup-of-the-gitlab-system official guide], mainly done by the service's backup creation Rake task. Configuration files should also be copied along, these include <code>/etc/gitlab/gitlab.rb</code>, <code>/etc/gitlab/gitlab-secrets.json</code> and <code>/var/opt/gitlab/config/secrets.yml</code>, as shown in the [https://docs.gitlab.com/ce/raketasks/backup_restore.html#storing-configuration-files same guide]. To restore the service follow the commands described in the [https://docs.gitlab.com/ce/raketasks/backup_restore.html#restore restoration section]. The current backup script will save the copy in the container's <code>/var/opt/gitlab</code> folder, and sync it with the host's <code>/srv/data/gitlab/data</code>. Logs can be found on <code>/var/log/gitlab</code> and are linked to the host's <code>/srv/log/gitlab</code> folder.

	~~<pre>bash ./gitlab/backup.sh</pre>~~
	~~== Jenkins ==~~

	The Jenkins service exposes its web interface on '''port 8080'''. Jenkins is fairly simple to backup and there is no script, simply copy the <code>/var/jenkins_home</code> folder into the desired location. Restoration is done by replacing the target folder with the backup. Jenkins home folder is synced with the host's <code>/srv/data/jenkins</code> location. Logs can be found on <code>/var/jenkins_home/logs</code> and are linked to the host's <code>/srv/log/jenkins</code> folder. General information can be found in the official [https://wiki.jenkins.io/display/JENKINS/Administering+Jenkins administration guide].

	~~== Jira ==~~

	The Jira service exposes its web interface on '''port 8102'''. According to the information present in their [https://confluence.atlassian.com/adminjiraserver/backing-up-data-938847673.html official guide], the current backup script will save the dump inside the host's <code>/srv/data/jira/db</code> folder. Its home folder can be found at the container's <code>/opt/jira</code> and is mapped to the host's <code>/srv/data/jira/data</code> folder. Logs can be found on <code>/opt/jira/log</code> and are linked to the host's <code>/srv/log/jira</code> folder.

	~~<pre>bash ./jira/backup.sh</pre>~~

	~~-----~~

	~~== References ==~~

	* JFrog Artifactory User Guide. Export System Settings Example [online]. Available at https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-ExportSystemSettingsExample (Accessed 16 March 2018).
	* JFrog Artifactory User Guide. Export System [online]. Available at https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-ExportSystem (Accessed 16 March 2018).
	* JFrog Artifactory User Guide. Import System Settings Example [online]. Available at https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-ImportSystemSettingsExample (Accessed 16 March 2018).
	* JFrog Artifactory User Guide. Full System Import [online]. Available at https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-FullSystemImport (Accessed 16 March 2018).
	* Backing up and restoring GitLab. Creating a backup of the GitLab system [online]. Available at https://docs.gitlab.com/ce/raketasks/backup_restore.html#creating-a-backup-of-the-gitlab-system (Accessed 16 March 2018).
	* Backing up and restoring GitLab. Storing configuration files [online]. Available at https://docs.gitlab.com/ce/raketasks/backup_restore.html#storing-configuration-files (Accessed 16 March 2018).
	* Backing up and restoring GitLab. Restore [online]. Available at https://docs.gitlab.com/ce/raketasks/backup_restore.html#restore (Accessed 16 March 2018).
	* Jenkins Wiki. Administering Jenkins [online]. Available at https://wiki.jenkins.io/display/JENKINS/Administering+Jenkins (Accessed 16 March 2018).
	* Atlassian Documentation. Backing up data [online]. Available at https://confluence.atlassian.com/adminjiraserver/backing-up-data-938847673.html (Accessed 16 March 2018).

Marcb a 14:06, 21 març 2018

2018-03-21T14:06:11Z

← Versió més antiga		Revisió del 14:06, 21 març 2018
Línia 19:		Línia 19:
	The Artifactory service exposes its web interface on '''port 8103'''. A full system backup can be done via the service's API. Backup settings need to be [https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-ExportSystemSettingsExample retrieved] and sent back via [https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-ExportSystem POST], as explained in the official guide. Similarly, to restore the system, [https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-ImportSystemSettingsExample retrieve] the restoration settings and send them back via [https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-FullSystemImport POST], as shown in Artifactory's API guide. The current backup script will save the copy inside the container's <code>/tmp/backup</code> folder, and sync it with the host <code>/srv/data/artifactory</code>. Logs can be found on <code>/opt/jfrog/artifactory/logs</code> and are linked to the host's <code>/srv/log/artifactory</code> folder.		The Artifactory service exposes its web interface on '''port 8103'''. A full system backup can be done via the service's API. Backup settings need to be [https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-ExportSystemSettingsExample retrieved] and sent back via [https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-ExportSystem POST], as explained in the official guide. Similarly, to restore the system, [https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-ImportSystemSettingsExample retrieve] the restoration settings and send them back via [https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-FullSystemImport POST], as shown in Artifactory's API guide. The current backup script will save the copy inside the container's <code>/tmp/backup</code> folder, and sync it with the host <code>/srv/data/artifactory</code>. Logs can be found on <code>/opt/jfrog/artifactory/logs</code> and are linked to the host's <code>/srv/log/artifactory</code> folder.

	<~~source lang="bash"~~>bash ./artifactory/backup.sh</~~source~~>		<pre>bash ./artifactory/backup.sh</pre>
	== Gitlab ==		== Gitlab ==

	The Gitlab service exposes its web interface on '''port 8101''', and also '''port 22''' for Git's SSH operations. Backup information can be found in their [https://docs.gitlab.com/ce/raketasks/backup_restore.html#creating-a-backup-of-the-gitlab-system official guide], mainly done by the service's backup creation Rake task. Configuration files should also be copied along, these include <code>/etc/gitlab/gitlab.rb</code>, <code>/etc/gitlab/gitlab-secrets.json</code> and <code>/var/opt/gitlab/config/secrets.yml</code>, as shown in the [https://docs.gitlab.com/ce/raketasks/backup_restore.html#storing-configuration-files same guide]. To restore the service follow the commands described in the [https://docs.gitlab.com/ce/raketasks/backup_restore.html#restore restoration section]. The current backup script will save the copy in the container's <code>/var/opt/gitlab</code> folder, and sync it with the host's <code>/srv/data/gitlab/data</code>. Logs can be found on <code>/var/log/gitlab</code> and are linked to the host's <code>/srv/log/gitlab</code> folder.		The Gitlab service exposes its web interface on '''port 8101''', and also '''port 22''' for Git's SSH operations. Backup information can be found in their [https://docs.gitlab.com/ce/raketasks/backup_restore.html#creating-a-backup-of-the-gitlab-system official guide], mainly done by the service's backup creation Rake task. Configuration files should also be copied along, these include <code>/etc/gitlab/gitlab.rb</code>, <code>/etc/gitlab/gitlab-secrets.json</code> and <code>/var/opt/gitlab/config/secrets.yml</code>, as shown in the [https://docs.gitlab.com/ce/raketasks/backup_restore.html#storing-configuration-files same guide]. To restore the service follow the commands described in the [https://docs.gitlab.com/ce/raketasks/backup_restore.html#restore restoration section]. The current backup script will save the copy in the container's <code>/var/opt/gitlab</code> folder, and sync it with the host's <code>/srv/data/gitlab/data</code>. Logs can be found on <code>/var/log/gitlab</code> and are linked to the host's <code>/srv/log/gitlab</code> folder.

	<~~source lang="bash"~~>bash ./gitlab/backup.sh</~~source~~>		<pre>bash ./gitlab/backup.sh</pre>
	== Jenkins ==		== Jenkins ==

Línia 33:		Línia 33:
	The Jira service exposes its web interface on '''port 8102'''. According to the information present in their [https://confluence.atlassian.com/adminjiraserver/backing-up-data-938847673.html official guide], the current backup script will save the dump inside the host's <code>/srv/data/jira/db</code> folder. Its home folder can be found at the container's <code>/opt/jira</code> and is mapped to the host's <code>/srv/data/jira/data</code> folder. Logs can be found on <code>/opt/jira/log</code> and are linked to the host's <code>/srv/log/jira</code> folder.		The Jira service exposes its web interface on '''port 8102'''. According to the information present in their [https://confluence.atlassian.com/adminjiraserver/backing-up-data-938847673.html official guide], the current backup script will save the dump inside the host's <code>/srv/data/jira/db</code> folder. Its home folder can be found at the container's <code>/opt/jira</code> and is mapped to the host's <code>/srv/data/jira/data</code> folder. Logs can be found on <code>/opt/jira/log</code> and are linked to the host's <code>/srv/log/jira</code> folder.

	<~~source lang="bash"~~>bash ./jira/backup.sh</~~source~~>		<pre>bash ./jira/backup.sh</pre>

	-----		-----

Marcb a 14:05, 21 març 2018

2018-03-21T14:05:36Z

← Versió més antiga		Revisió del 14:05, 21 març 2018
Línia 3:		Línia 3:
	To install and run the stack, execute <code>docker-compose up -d</code> from the project folder. In a similar fashion, use <code>docker-compose down</code> to halt the services. To backup the whole stack use the <code>backup-all.sh</code> script.		To install and run the stack, execute <code>docker-compose up -d</code> from the project folder. In a similar fashion, use <code>docker-compose down</code> to halt the services. To backup the whole stack use the <code>backup-all.sh</code> script.

	<~~source lang="bash"~~>ssh user@fedora-atomic.cadt.com -p 2222		<pre>ssh user@fedora-atomic.cadt.com -p 2222
	cd /home/tinki-team		cd /home/tinki-team
	docker-compose up -d		docker-compose up -d
	bash ./backup-all.sh</~~source~~>		bash ./backup-all.sh</pre>
	Inside the container server, the stack should be located at <code>/home/tinki-team</code> holding a <code>docker-compose.yml</code> manifest with the following services:		Inside the container server, the stack should be located at <code>/home/tinki-team</code> holding a <code>docker-compose.yml</code> manifest with the following services:

Marcb: Es crea la pàgina amb «= tinki-team = To install and run the stack, execute `docker-compose up -d` from the project folder. In a similar fashion, use docker-compose down 2018-03-21T14:03:56Z Es crea la pàgina amb «= tinki-team = To install and run the stack, execute <code>docker-compose up -d</code> from the project folder. In a similar fashion, use <code>docker-compose down</c...». Pàgina nova = tinki-team = To install and run the stack, execute <code>docker-compose up -d</code> from the project folder. In a similar fashion, use <code>docker-compose down</code> to halt the services. To backup the whole stack use the <code>backup-all.sh</code> script. <source lang="bash">ssh user@fedora-atomic.cadt.com -p 2222 cd /home/tinki-team docker-compose up -d bash ./backup-all.sh</source> Inside the container server, the stack should be located at <code>/home/tinki-team</code> holding a <code>docker-compose.yml</code> manifest with the following services: * Artifactory HTTP: http://fedora-atomic.cadt.com:8103 * Gitlab HTTP: http://fedora-atomic.cadt.com:8101 * Gitlab SSH: http://fedora-atomic.cadt.com:22 * Jenkins HTTP: http://fedora-atomic.cadt.com:8080 * Jira HTTP: http://fedora-atomic.cadt.com:8102 == Artifactory == The Artifactory service exposes its web interface on '''port 8103'''. A full system backup can be done via the service's API. Backup settings need to be [https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-ExportSystemSettingsExample retrieved] and sent back via [https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-ExportSystem POST], as explained in the official guide. Similarly, to restore the system, [https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-ImportSystemSettingsExample retrieve] the restoration settings and send them back via [https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-FullSystemImport POST], as shown in Artifactory's API guide. The current backup script will save the copy inside the container's <code>/tmp/backup</code> folder, and sync it with the host <code>/srv/data/artifactory</code>. Logs can be found on <code>/opt/jfrog/artifactory/logs</code> and are linked to the host's <code>/srv/log/artifactory</code> folder. <source lang="bash">bash ./artifactory/backup.sh</source> == Gitlab == The Gitlab service exposes its web interface on '''port 8101''', and also '''port 22''' for Git's SSH operations. Backup information can be found in their [https://docs.gitlab.com/ce/raketasks/backup_restore.html#creating-a-backup-of-the-gitlab-system official guide], mainly done by the service's backup creation Rake task. Configuration files should also be copied along, these include <code>/etc/gitlab/gitlab.rb</code>, <code>/etc/gitlab/gitlab-secrets.json</code> and <code>/var/opt/gitlab/config/secrets.yml</code>, as shown in the [https://docs.gitlab.com/ce/raketasks/backup_restore.html#storing-configuration-files same guide]. To restore the service follow the commands described in the [https://docs.gitlab.com/ce/raketasks/backup_restore.html#restore restoration section]. The current backup script will save the copy in the container's <code>/var/opt/gitlab</code> folder, and sync it with the host's <code>/srv/data/gitlab/data</code>. Logs can be found on <code>/var/log/gitlab</code> and are linked to the host's <code>/srv/log/gitlab</code> folder. <source lang="bash">bash ./gitlab/backup.sh</source> == Jenkins == The Jenkins service exposes its web interface on '''port 8080'''. Jenkins is fairly simple to backup and there is no script, simply copy the <code>/var/jenkins_home</code> folder into the desired location. Restoration is done by replacing the target folder with the backup. Jenkins home folder is synced with the host's <code>/srv/data/jenkins</code> location. Logs can be found on <code>/var/jenkins_home/logs</code> and are linked to the host's <code>/srv/log/jenkins</code> folder. General information can be found in the official [https://wiki.jenkins.io/display/JENKINS/Administering+Jenkins administration guide]. == Jira == The Jira service exposes its web interface on '''port 8102'''. According to the information present in their [https://confluence.atlassian.com/adminjiraserver/backing-up-data-938847673.html official guide], the current backup script will save the dump inside the host's <code>/srv/data/jira/db</code> folder. Its home folder can be found at the container's <code>/opt/jira</code> and is mapped to the host's <code>/srv/data/jira/data</code> folder. Logs can be found on <code>/opt/jira/log</code> and are linked to the host's <code>/srv/log/jira</code> folder. <source lang="bash">bash ./jira/backup.sh</source> ----- == References == * JFrog Artifactory User Guide. Export System Settings Example [online]. Available at https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-ExportSystemSettingsExample (Accessed 16 March 2018). * JFrog Artifactory User Guide. Export System [online]. Available at https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-ExportSystem (Accessed 16 March 2018). * JFrog Artifactory User Guide. Import System Settings Example [online]. Available at https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-ImportSystemSettingsExample (Accessed 16 March 2018). * JFrog Artifactory User Guide. Full System Import [online]. Available at https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-FullSystemImport (Accessed 16 March 2018). * Backing up and restoring GitLab. Creating a backup of the GitLab system [online]. Available at https://docs.gitlab.com/ce/raketasks/backup_restore.html#creating-a-backup-of-the-gitlab-system (Accessed 16 March 2018). * Backing up and restoring GitLab. Storing configuration files [online]. Available at https://docs.gitlab.com/ce/raketasks/backup_restore.html#storing-configuration-files (Accessed 16 March 2018). * Backing up and restoring GitLab. Restore [online]. Available at https://docs.gitlab.com/ce/raketasks/backup_restore.html#restore (Accessed 16 March 2018). * Jenkins Wiki. Administering Jenkins [online]. Available at https://wiki.jenkins.io/display/JENKINS/Administering+Jenkins (Accessed 16 March 2018). * Atlassian Documentation. Backing up data [online]. Available at https://confluence.atlassian.com/adminjiraserver/backing-up-data-938847673.html (Accessed 16 March 2018).