Installing and Configuring Atlassian Software
Installing and Configuring Atlassian Software
Firewall configura on
172.16.191.66 *
172.16.191.67 *
172.16.191.69
From:
172.16.191.70 * stage-
project.partseuropenet.eu
From :
Port :
PE-NB-2229
To : 81
172.16.191.71 * 10.50.101.137
stage-
Port:
project.partseuropenet.eu To : From:
22
stage- relay-cluster- stage-
172.16.191.72 * confluence.partseuropenet.eu eu01.hornetsecurity.com confluence.partseuropenet.eu
stage- Port : Port :
serviceportal.partseuropenet.eu 25 82
Port :
443 From:
172.16.191.73 * stage-
serviceportal.partseuropenet.eu
Port :
83
172.16.191.75
DNS names (A Records)
o https://stage-project.partseuropenet.eu
o https://stage-confluence.partseuropenet.eu
o https://stage-serviceportal.partseuropenet.eu
Before migration data you should create or have a admin user in INTERNAL DIRECTORY in each application which can login after restore the
database in new environment. Be careful that because of VLAN and Network configuration you may not be able to login with such a kind of user.
Also, we should stop the rest of the containers of each service and just have one container up from each service. It means that in each cluster there
should be just one node up. With this command
o “docker service scale atl_confluence-cluster-node2=0 atl_confluence-cluster-node3=0 atl_confluence-cluster-node4=0 atl_jira-cluster-
node2=0 atl_jira-cluster-node3=0 atl_jira-cluster-node4=0 atl_jsm-cluster-node2=0 atl_jsm-cluster-node3=0 atl_jsm-cluster-node4=0”
migrating database from old environments to the new environment.
o Export Jira-Software database to a xml file