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

Directadmin: Remove IP selection on Package

    Details

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

      Description

      When configuring a Package using Directadmin, you must select a Server. The plans and the IP address(es) are fetched from the API and populated as Package fields.

      This is a big problem because it doesn't really allow you to sell from Server Groups, since the IP is server specific. It also doesn't work well when allowing the client to choose location by Server Group.

      On the contrary, cPanel works perfectly fine in this case. You specify a Server Group on the Package and not the Server, it makes an API call to a server in the group and fetches the Plans, and populates a plan dropdown. So long as all your Plans exist on all your WHM/cPanel servers there is no problem.

      But, when the IP is required for DA, the IP is unique and can only be used with the server for which it belongs.

      Question: Does DA's API still require that we send an IP address when provisioning a new DA account? If not, let's remove the requirement entirely.

      If it does require the IP, can we move the IP to the Module Server configuration and remove it from the Package? If yes, we should do that.

      Selecting a Server Group on the Package should NOT ask for a Server to be selected, as it should choose upon provisioning which server to use, and the IP should not be specified here.

      In other products, it seems like specifying the IP on the Server / module row is totally fine.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            abdy Abdy Franco
            Reporter:
            admin Paul Phillips
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Fix Release Date:
              27/Nov/24

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 4 days, 4 hours, 44 minutes
              4d 4h 44m

                Agile