I have inherited a complicated system and lack knowledge (much knowledge!).
We run our jira/confluence onsite servers in VM's, they talk to a postgres database also hosted on an Ubuntu VM. Alongside these we also have have a VM labelled as 'jira web-apps' and another VM labelled NGINX (a certificate server).
We are thinking of a migration to a cloud based/hosted atlassian service and toward this end need to know if we did migrate to the cloud, would we still require the jira-web-apps VM and/or the NGINX cert server VM?
Or are these services handled if hosted by atlassian?
Could explain briefly what the jira web-app server does and also the NGINX cert server role in this system? Or what config file I can peruse, the location of a config for each might help too.
We also have a DNS server (bind) and I understand the role this plays in our system.
Look forward to a reply,
Thanks in advance
Hi Joe,
If you're considering moving to Jira Cloud (and I highly recommend taking a look at the Jira Cloud Migration Assistant we provide to help with this), then Atlassian handles all the functions you'd have separate VMs for. If I understand your environment correctly, you currently have:
Servers 1-3 are definitely handled by Atlassian's Cloud infrastructure. nginx is likely sitting "in front" of your Jira/Confluence servers in order to terminate TLS/SSL requests (if you are running over HTTPS).
I'm not clear what 'jira web-apps' might be - if you're able to log in on that VM and run the top command, you might be able to determine if there are any processes running on it. My guess is that this is simply a legacy VM and that you have other VMs running now where the actual Jira/Confluence java applications are running.
Cheers,
Daniel
Thanks Danial,
1/ Jira and Confluence are each running in seperate VM's.
2/ Correct
3/ Yes, but and we also have a DNS server (BIND). Couldn't that do rev proxy?
4/ Yes, I can login, I think 'mongod' could be what we are looking for but I don't know what it is doing or even if we need it? anyway here is the 'top' stuff:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1521 root 20 0 693784 37528 5748 S 2.6 1.8 931:29.42 Eaton-IPP
978 mongodb 20 0 787700 53768 27004 S 0.3 2.6 323:32.16 mongod
27238 local 20 0 41804 3844 3196 R 0.3 0.2 0:02.27 top
1 root 20 0 37736 4988 3264 S 0.0 0.2 1:08.24 systemd
2 root 20 0 0 0 0 S 0.0 0.0 0:00.94 kthreadd
3 root 20 0 0 0 0 S 0.0 0.0 2:42.36 ksoftirqd/0
5 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/0:0H
7 root 20 0 0 0 0 S 0.0 0.0 13:43.92 rcu_sched
8 root 20 0 0 0 0 S 0.0 0.0 0:00.00 rcu_bh
9 root rt 0 0 0 0 S 0.0 0.0 0:00.00 migration/0
10 root rt 0 0 0 0 S 0.0 0.0 0:21.70 watchdog/0
11 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kdevtmpfs
12 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 netns
13 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 perf
14 root 20 0 0 0 0 S 0.0 0.0 0:02.67 khungtaskd
15 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 writeback
16 root 25 5 0 0 0 S 0.0 0.0 0:00.00 ksmd
17 root 39 19 0 0 0 S 0.0 0.0 0:00.00 khugepaged
18 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 crypto
19 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kintegrityd
20 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset
21 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kblockd
22 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 ata_sff
23 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 md
24 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 devfreq_wq
27 root 20 0 0 0 0 S 0.0 0.0 0:02.02 kswapd0
28 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 vmstat
29 root 20 0 0 0 0 S 0.0 0.0 0:00.00 fsnotify_mark
30 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ecryptfs-kthrea
46 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kthrotld
47 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 acpi_thermal_pm
48 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset
49 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset
50 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset
51 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset
52 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset
53 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset
54 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset
55 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset
56 root 20 0 0 0 0 S 0.0 0.0 0:00.01 scsi_eh_0
57 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 scsi_tmf_0
58 root 20 0 0 0 0 S 0.0 0.0 0:00.00 scsi_eh_1
59 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 scsi_tmf_1
65 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 ipv6_addrconf
78 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 deferwq
79 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 charger_manager
80 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset
128 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset
129 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset
130 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset
131 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset
132 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset
133 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
And after speaking with staff here, it may well be legacy and doing nothing. I will shut jira-web-apps down and we'll see what happens. Thank you for your answer above, most helpful. And I am indeed using the atlassian cloud migration resources to help with all this...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
After 24 hours no one has reported any issues, the sun still came up and jira/confluence continue to run as before! Jira-webapps appears to be redundant. I'll leave it off.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.