[script] Solus IP Block Usage Priorities (Usage % Thresholds)

[Jonathan]

This may help out anyone here using SolusVM.  It will let you define what % usage you want to run IP blocks to and adjust the IP block priorities as such.  As of this posting Solus hasn't release this feature to their production tier yet but it will be available in 1.16.13 or you can /scripts/upcp-beta on your master to get it.

It's designed to be run on a cron.  I wouldn't recommend running it any more often than once an hour or so.

https://github.com/neonardo1/solusvm-80ipblock

 

[MannDude]

Thanks for sharing! I'm sure some folks here will find it quite useful.

 

[Jonathan]

There's tons of room for improvement, I'll be adding a new feature and making some optimizations in a commit hopefully later tonight.

 

[Jonathan]

Updated with some MySQL optimizations (https://github.com/neonardo1/solusvm-80ipblock/commit/9784b417a0d91ac7212fc032a5e33f7adb2af75e) and added dynamic block balancing capabilities so it can assign from least used blocks first and attempt to get and maintain even distribution amongst your blocks if you choose to use this feature (https://github.com/neonardo1/solusvm-80ipblock/commit/caae943592911c140f5bbd2e09ee4ad505b7fc5d).

 

[HalfEatenPie]

So to put it in plain words...

This is focused on determining what IPs to allocate to a VPS right?  Like if you need to use 80% of each /24 then it'll automatically provision using the proper subnet in order to get the proper %usage right?  

This is great since Solus usually does it by... whatever ordering it does.  I think lowest number to highest number.  

Out of curiosity, (since I haven't seen the code yet) does this script round up or down?  Lets say you need 81% of a /24 used.  Would it be 81% at 80.1%?  Or does it need to be a solid 81% (which would mean a fraction of an IP since it can't be a perfect 81%)?  Or will 81.1% still be considered satisfactory to the upper limit? 

 

[Jonathan]

So to put it in plain words...

This is focused on determining what IPs to allocate to a VPS right?  Like if you need to use 80% of each /24 then it'll automatically provision using the proper subnet in order to get the proper %usage right?  

This is great since Solus usually does it by... whatever ordering it does.  I think lowest number to highest number.  

Out of curiosity, (since I haven't seen the code yet) does this script round up or down?  Lets say you need 81% of a /24 used.  Would it be 81% at 80.1%?  Or does it need to be a solid 81% (which would mean a fraction of an IP since it can't be a perfect 81%)?  Or will 81.1% still be considered satisfactory to the upper limit? 

That's precisely what it's designed to do.  It will go based on the highest to lowest (backwards feeling I know, blame Solus lol).  It doesn't round in that sense but it will recognize decimals and since it uses >=, 81.1 would meet the criteria, 80.9 would not.

 

[HalfEatenPie]

Alright sweet thanks for the clarification!  I didn't see it in the original post so I was a bit confused

Definitely looks like a nifty piece of software that'd be great to use!  Thanks for the contribution! 

 

[Nick_A]

Nice.

 

[Tyler]

This seems nice, and maybe there's something I am missing, but what exactly is the benefit to filling up your IP blocks in such a manner? I know Solus is weird about how it does the job, but I'm just not sure why one would care to fill them up in this way.  Perhaps I am missing something.

 

[Jonathan]

This seems nice, and maybe there's something I am missing, but what exactly is the benefit to filling up your IP blocks in such a manner? I know Solus is weird about how it does the job, but I'm just not sure why one would care to fill them up in this way.  Perhaps I am missing something.

ARIN IP assignment usage requirements.  It's not very useful for those getting IPs from their datacenter I guess.

 

[IndoVirtue]

Might be unrelated to this topic, but SolusVM add new features recently on v1.17:

Released: 15 September 2015

A new Priority option has been added while editing an IP block. The Priority field can contain a numeric value where the highest block value will be used first when assigning ip addresses to a virtual server when created from the API

If you look at IP block list, now they have additional priority column. It's still limited to which IP block should be used until it's exhausted. Usage percentage still remains to be seen yet.

 

[wlanboy]

Nice solution. I like simple (=effective) solutions solving a single problem.
Designed as a cron to set priorities on schedule. *thumbs up*

 

[Jonathan]

Might be unrelated to this topic, but SolusVM add new features recently on v1.17:

Released: 15 September 2015

A new Priority option has been added while editing an IP block. The Priority field can contain a numeric value where the highest block value will be used first when assigning ip addresses to a virtual server when created from the API

If you look at IP block list, now they have additional priority column. It's still limited to which IP block should be used until it's exhausted. Usage percentage still remains to be seen yet.

That priority feature of theirs is actually a dependency of this script.  This script controls those priorities.  They introduced them in a BETA version between 1.16 and 1.17 per my request.

I'll update my GitHub project to state that this only works with version of SolusVM >= 1.17

EDIT: I updated the readme to reflect requiring >= 1.17
https://github.com/neonardo1/solusvm-80ipblock/commit/95287f3b3dcfedc1c9e77dedf5694aa9dc087751