Pros, cons and costs to help facilitate our decision about running these tools in the Cloud versus a Server*.
Pros and Cons
| Pros | Cons | |
|---|---|---|
| Cloud |
|
|
| Server |
|
|
*Server means running on Amazon AWS hosting where the OpenLMIS team is responsible for the server security, backups, updates, management, etc.
**Atlassian has accepted this new feature request, but schedule is unknown: https://jira.atlassian.com/browse/CLOUD-6999
Cost & Effort Comparison
Include licenses/subscriptions as well as estimated labor/time costs.
| Up-Front Effort | Annual Estimated Costs & Effort | |
|---|---|---|
| Cloud with no new plug-ins (status quo) | Small Effort to disable Gliffy in January 2017 | $0/year & zero on-going effort It's free!, as long as we are willing to live without more plug-ins and without a custom domain name. |
| Cloud + plug-ins | Small Effort to enable plug-ins | $13,200/year - $32,400/year for the plug-ins we want See plugin costs for a list of plugins we'd likely consider along with their variable costs. Zero AWS costs, minimal sysadmin effort. |
| Server + plug-ins | Large Effort to migrate
| AWS: Plug-ins: $0. All the plug-ins we want to use are free in Server edition. Admin Effort: 24-60 hours / year sysadmin time (2-5 hrs / month estimated) |
On-going maintenance for the Server edition
- upgrading JIRA and Confluence (a few times each year; usually it is low effort unless something breaks, then requires expertise to repair)
- arranging and managing backups
- upgrade Amazon AWS server OS (roughly monthly; requires some Linux sysadmin skills; usually low effort unless something breaks)
- rebuild the server or re-install JIRA and Confluence (only needed every 3-5 years)
Plugin Cost - Details
Atlassian's policy for all plugins is that their server-editions are free to use for open-source projects. No such generosity, however, is afforded to cloud versions of the plugins. If we would like Atlassian to host our JIRA/Confluence instances, we will therefore have to pay for all plugins we choose to use.
Our cost for plugins should we opt for cloud hosting depends on the following variables:
1) Which plugins we want.
2) The maximum number of users for which we'd like our Atlassian products to be licensed.
To account for these variables, the following set of potential costs was given above in the "Cost & Effort Comparison" table: $513, $1138, and $2659. The rest of this section details how these values were determined.
The cost for plug-ins run within the cloud varies according to the number of users one’s Atlassian product is licensed to allow. While we currently have 157 active (as opposed to disabled) users, our cloud license allows for up to 500.
The available pricing tiers based on the maximum number of users a system allows are as follows: 10 users, 15 users, 25, 50, 100, 500, and 2000. Although it’s conceivable that we can cull our current set of 157 users down to 100, curating the list would require both upfront and continued effort. There exists no standard price delta from one user-tier to another amongst plugins. Values for both the 100 and 500 user-tiers are thus respectively included below.
The Plugins listed below are ones in which we’ve shown interest. They comprise the "broader set of plugins" referred to within the "Cost & Effort Comparison" table. The subset of underlined plugins constitute the "select few plugins" referenced in the aforementioned table.
JIRA:
eazyBI Reports and Charts for JIRA Cloud: $150 or $200 / month
Agile Story Plugin for JIRA: $213 or $438 / month (these represent average costs of the two related plugins under consideration)
Gantt Cloud: $42 or $56 / month
Gliffy Diagrams for JIRA: $150 or $500 / month
JIRA Misc Workflow Extensions: $50 or $95 / month
Zephyr: $200 or $350 / month
Confluence:
Gliffy Diagrams: $150 or $500 / month
Advanced Tables: $10 or $20 / month
Questions for Confluence: $150 or $250 / month
Team Calendars: $150 or $250 / month