Skip to content
← Help us Improve Solus

How can we improve current and future versions of solus?

Help us Improve Solus: Networking & IP Management

Categories

(thinking…)

Improved IP block management

We have a lot of IPv4 /27 and /26 public IP blocks. At our various locations we share VLANs and IP blocks between many servers. Each time we add a new server we have to manually add the server to many IP blocks. This is a tedious exercise. It's the most tedious exercise we do in SolusVM management. We would like to request some kind of better design. I think what would be better is if SolusVM had some higher level "grouping" of network blocks that you then assigned to servers in same VLAN. When we needed to add a new network block we could add it to the one "group" which would then apply to all servers that already had that group. We raised a ticket on this on August 31st 2017 for reference.

25 votes

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Brandon S shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Anthony Srdar commented  ·   ·  Report

    I had asked for this back in 2012, sad to see it's still in the request stage.

  • Brandon commented  ·   ·  Report

    We had to get our developers to create an external custom web panel to interface with SolusVM database to allow easily adding a new node to all the desired subnets in a few clicks. The current SolusVM interface for IP block management had become too cumbersome.

  • Anonymous commented  ·   ·  Report

    We badly need improvement in IP block management, it is so outdated and cumbersome, we need simplicity and allow us to add on per subnet block

  • Brandon commented  ·   ·  Report

    Anyway it is implemented that makes good sense is fine with us if it achieves the same result. This is the absolute worst most inefficient thing we have to do in SolusVM as we add a lot of net blocks to SolusVM. Please make this a high priority.

  • Anonymous commented  ·   ·  Report

    it think it is a bit complicated formulated.

    Would it be not enough to just add the option to define an VLAN per added subnet?
    So, the VM, thats using a subnet, is automated assigned on the right vlan?

    maybe a cross reverence to:
    https://solus.uservoice.com/forums/914134-help-us-improve-solus/suggestions/34944664-vlan-support

    @Plesk Team,
    If you looking for a technical way to implement it, take maybe a look on Proxmox and how they did it.

  • Brandon S commented  ·   ·  Report

    Hello asmith. Yes that is correct. It would save having to add the new server to many ip blocks.

  • Adminasmith (Admin, Plesk Intl GmbH) commented  ·   ·  Report

    Hi Brandon,

    Thanks for the suggestion, for clarity and to make sure I understand you correctly the process you would like would be:

    1) Add network block and have the ability to select an 'IP Pool' or 'IP Group'

    2) When adding a new slave/node to the SolusVM master select the 'IP Pool/Group' at the same time.

    Then you can add a new network block to the pool without having to manually assign the correct individual servers.

    Do I have that right?