Administering JIRA Software Data Center on Azure
Once you've deployed JIRA Software Data Center to Azure using the reference deployment template, administering the application is similar to managing an application on your own hardware, with the exception that you'll need to go via the jumpbox to access your nodes and shared home directory. To access your jumpbox and nodes you'll need:
- the SSH credentials you provided during setup,
- the JIRA node credentials you provided during setup
- the public DNS name or IP address of your jumpbox (you can obtain this through the Azure portal via Menu > Resource groups > <your resource group> > jiranat), and
- the node IP addresses, listed against the
jiracluster (instance n)row in Connected devices. (You can obtain this through the Azure portal via Menu > Resource groups > <your resource group> > jiravnet).
Currently, Atlassian templates for Azure Resource Manager are recommended for proof of concept deployments only.
Connecting to your Azure jumpbox and nodes over SSH
Access the jumpbox via a terminal or command line using:
$ ssh JUMPBOX_USERNAME@DNS_NAME_OR_IP_ADDRESS
Once you've accessed the jumpbox, we can jump to any of the nodes in the cluster, using:
$ ssh NODE_USERNAME@NODE_IP_ADDRESS
You'll then be asked for your node password - after providing this, you should be connected to the node.
For your Azure deployment, you may need to make changes to your dbconfig.xml or server.xml files, just as you would for a deployment on your own hardware:
- your shared server.xml lives in /media/atl/jira/shared/server.xml
- your shared dbconfig.xml lives in /media/atl/jira/shared/dbconfig.xml
In Azure, these files are copied from the shared home to the local home when a new node joins the cluster.
So, when making changes in server.xml or dbconfig.xml on existing nodes, it's important to also update the files in the shared home, otherwise a new node joining the cluster will be setup with outdated configuration.
These files are only accessible from the existing nodes. The shared home is mounted (think of it as a network harddisk) on each node under /media/atl/jira/shared.
So from an existing node (when you're logged in through SSH), you can go to /media/atl/jira/shared
We recommend you use the Azure native backup facility, which utilizes snapshots to back up your JIRA Software Data Center.
Migrating your existing instance into Azure
We recommend you use the standard options availble to migrate data between JIRA instances.