Versions Compared

Old Version 16

changes.mady.by.user Ben Leibert

Saved on

compared with

New Version 17

changes.mady.by.user Brandon Bowersox-Johnson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Re-organized around 3 scenarios

Fill in prosPros, cons and costs to help facilitate our decision about running these tools in the Cloud versus a Server*.

...

Cannot install arbitrary plug-ins (limited set supported on Cloud

ProsCons
Cloud
  • Less maintenance
  • Less expensive (see cost grid below)
  • Free option
    (as long as we don't use plug-ins; see cost options below)
  • No AWS hosting costs


  • Limited set of plug-ins is supported in Cloud
  • Some 3rd-party plug-ins are costly in Cloud but free in Server (e.g., Gliffy)
  • No custom domain names allowed yet in Cloud
Server
  • Effort and down-time required to migrate
  • More Requires on-going maintenance effortMore expensive
  • AWS hosting costs


*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  

...

Include licenses/subscriptions as well as estimated labor/time costs.

  • $0 for server, and nothing more in terms of operational cost that the server-option wouldn't also require
    • $513 / month for a select few plugins and a minimal number of users
    OR
    $1,138 / month for a select few plugins and the current number of users
    OR
    $2,659 / month for broader set of plugins and the current number of users

    		Up-Front Costs & EffortAnnual Estimated Costs & Effort
    Cloud
    		$0 (already on cloud)with no new plug-ins
    (status quo) 

    Small Effort to disable Gliffy in January 2017
    (to save and re-attach as PNGs)

    $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

    • Ben's time (+/-100 hours)
    • ~2 day downtime during migration
    • manual or scripted clean-up of links

    AWS:  

    As is: $3


    Currently $3,528/year hosting     (

    $294/month -

    see worksheet)

    Minimize cost:

    Can reduce to $1,203/year (

    $100.25/month effective rate -

    see worksheet with reductions)

    —meaning that we

    (reduce the AWS resources allocated and commit resources for one year)

    Plug-ins: $0. All the plug-ins we want to use are free in Server edition.

    Admin Effort: 24-60 hrs sys admin hours / year sysadmin time (2-5 hrs / month estimated)


    On-going maintenance for the Server edition

    ...