hello
I am starting to work with Atlassian tools in my DevOps and whould like to know that is the recommended size for the VM need to creat in Azure for:
Confluence, JIRA, Bit Bucket
(will have 2 environment - prod, none prod).
what is the optimize number of VM for such implementation?
(for example: can all none prod tools be on the same server?)
if and what kind of DB will I need
thanks
kfir
Atlassian provides some specific guidance for choosing Azure node when you run Data Center. If you are just running Server instances, then the Jira sizing guide is your best bet.
From my experience, it's best to run each application in a dedicated VM. As @Thomas Deiler and @Corentin Méhat point out, this simplifies troubleshooting and reduces downtime when upgrading. It also prevents swamping compute resources under peak loads. Especially when the products are integrated, it is common for Bitbucket, Confluence, and Jira to all want RAM and CPU at the same time, when teams are at their busiest. This option also allows you to better tune performance, by bumping up the VM size per application.
Hello,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just FYI, the recommendations page linked above is for Jira 6.3. Here's the updated version for Jira Data Center 7.x: Jira Data Center size profiles.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi Thomas
thank for the reply. my question then, what size would you start with?(is there a best practice)? I believe I will start with around 100 users to start with.
kfir
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear @Kfir Goldwasser,
I recommend to have for a staging environment same configuration as for prod. So you can quickly figure out, of an upgrade/other modification is working as expected and apply the changes to prod.
If you have enough resources on the VM host system, create for each application an one instance. Reduces risk and downtime greatly when updating.
So long
Thomas
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.