Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-1647

SolusVM: Change config options to add to plan values

        Details

        • Type: Improvement
        • Status: Closed
        • Priority: Major
        • Resolution: Fixed
        • Affects Version/s: 3.5.0-b1
        • Fix Version/s: 3.5.0-b3
        • Component/s: Modules
        • Labels:
          None

          Description

          SolusVM was updated to include config options for v3.5.0-b1. However, several of these need to be updated:
          custommemory
          customdiskspace
          custombandwidth
          custommemoryswap
          customcpus

          These may need to be renamed, and will need to add to the current plan value when a service is provisioned/updated.

          Plan values can be determined in the latest SolusVM version via:
          https://documentation.solusvm.com/display/DOCS/List+Plans+Per+VT

          When these config options are changed, they must update the server using the following actions:
          Update Bandwidth: https://documentation.solusvm.com/display/DOCS/Change+Bandwidth+Limits?src=contextnavpagetreemode
          Update Memory: https://documentation.solusvm.com/display/DOCS/Change+Memory?src=contextnavpagetreemode
          Update Hard Disk: https://documentation.solusvm.com/display/DOCS/Change+Hard+Disk+Size?src=contextnavpagetreemode
          Update CPUs: https://documentation.solusvm.com/display/DOCS/Change+CPU?src=contextnavpagetreemode

          I don't see an API action for updating swap memory. Thus, updating that config option in Blesta will only update it locally. Any charges will still be accrued.

            Issue Links

            relates to

            New Feature - A new feature of the product, which has yet to be developed. CORE-1473 SolusVM: Add configurable option support

            • Major - Major loss of function.
            • Closed

            Improvement - An improvement or enhancement to an existing feature or task. CORE-1668 Include removed config options when editing service

            • Major - Major loss of function.
            • Closed

            Improvement - An improvement or enhancement to an existing feature or task. CORE-1681 SolusVM: Update how swap (burst) is determined for OpenVZ

            • Major - Major loss of function.
            • Closed

              Activity

              Hide
              Permalink
              tyson Tyson Phillips (Inactive) added a comment -

              Updating swap alongside memory (memory|swap, e.g. 512|256) appears to have no affect on Xen virtualizations. If the default plan value for swap is unknown and not overridden, the swap will default to 512 since it is required to be entered.

              Show
              tyson Tyson Phillips (Inactive) added a comment - Updating swap alongside memory (memory|swap, e.g. 512|256) appears to have no affect on Xen virtualizations. If the default plan value for swap is unknown and not overridden, the swap will default to 512 since it is required to be entered.

                People

                • Assignee:
                  tyson Tyson Phillips (Inactive)
                  Reporter:
                  tyson Tyson Phillips (Inactive)
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:
                    Fix Release Date:
                    26/May/15