How do I move the subnet for Jira on Azure

[Jason Soloff]

Hi Folks -

So I have Jira installed on Azure using the Marketplace script built by Atlassian. All good so far. The problem is that the install defaulted to a particular subnet CIDR (10.0.0.0/16) and I need to move the entire install to a different subnet (say 10.5.0.0/16) because other things need that range and I can't "peer" the subnets in Azure when its occupied like that. I have the same problem with Confluence and BitBucket... they all assume 10.0.0.0/16 to install into and set up a dozen servers and interfaces. Hopefully someone can A) tell me how to do a "global change" for the Atlassian installs to get them to sit on the right subnets, B) suggest how to add an additional gateway to bridge/route between subnets, or C) how to update the Atlassian marketplace install script so that I can redeploy everything in the right place. It really seems dumb not to be able to pick a subnet to deploy into at the start of the script.

Thanks in advance

[Pramodh M · Accepted solution]

Hi @Jason Soloff 

You can deploy the template from this link https://bitbucket.org/atlassian/atlassian-azure-deployment/src/master/jira/ and change the VNet Address Prefix values in the template when you are deploying Data Center (In here - https://bitbucket.org/atlassian/atlassian-azure-deployment/src/master/jira/nestedtemplates/azuredeploy-vpc.json)

Between Subnets Azure takes care of the connection, there's nothing we need to do for connection between subnets.

For VNet as you said peering connection should be established.

Thanks,
Pramodh

[Jason Soloff]

Thank you. Looks like you've pointed me in the right direction

[Pramodh M]

@Jason Soloff 

Happy to help :-)

Please let me know if you have any queries.

Please accept the answer if I have answered your query.

Thanks,
Pramodh

[Pramodh M]

FYI,

Plan the VNet Address Space so that, Application Gateway is deployed in Empty Subnet, Jumpbox in Separate Subnet and then Jira Nodes are deployed in Private Subnets.