Whirr
  1. Whirr
  2. WHIRR-229

dynamically calculate hardware requirements

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      right now, we are choosing arbitrary instance sizes that we know to work well. Using this approach, we have to repeat effort per-provider. Also, service requirements aren't visible. I suggest we switch to a dynamically calculated system.

      ex. instead of m1.small, do minRam( (-mx heap size + 25% overhead)*JVMs + overhead of os )

        Issue Links

          Activity

          Hide
          Andrew Bayer added a comment -

          We've got this to some extent now as a result of the whirr.template added in WHIRR-593. It doesn't figure out the minRam on its own, but it is provider-agnostic.

          Show
          Andrew Bayer added a comment - We've got this to some extent now as a result of the whirr.template added in WHIRR-593 . It doesn't figure out the minRam on its own, but it is provider-agnostic.

            People

            • Assignee:
              Unassigned
              Reporter:
              Adrian Cole
            • Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development