vpsAdmin version 2.5.0 mainly improves network configuration, IP addresses and traffic monitoring.
For some time, vpsAdmin has let you divide system resources among multiple VPSes, but additional public IPv4 addresses cost extra. Often, no public IP address is needed at all: a private address behind NAT is enough. vpsAdmin now distinguishes public and private addresses. To obtain a private address, contact support, and bear in mind that private addresses may change when we introduce the 10Gbit network. It is best to wait a little longer.
We plan to allow private addresses to be allocated in larger blocks (/27, or 32 addresses). It currently looks as though we will make this available when the 10Gbit network is introduced. vpsAdmin already has everything it needs.
Private addresses also bring a change in traffic accounting. Traffic within our network is counted as private and does not count towards the set limit. Traffic between VPSes on the same node is not counted at all.
Traffic collection and storage have been reworked because the old solution could no longer keep up. The traffic table in the database has about 80 million rows, and calculating monthly traffic had become inefficient, with results commonly taking tens of seconds to appear. The new solution maintains monthly totals in another, much smaller table that is faster to work with.
The live traffic monitor finally works as it should. The web interface has more filtering options and updates automatically. You can also monitor traffic in a terminal: vpsfreectl has a new command, ip_traffic top, a TUI application similar to iftop.
The full list of changes is in the release notes.