cloudmin bandwidth measurement

Thanks for the cloudmin 5.3 release which includes a solution to our request of being able to select which interface(s) to calculate bandwidth measurement

However, it seems to be requiring ssh access to the VM concerned to be able to select the interfaces. Please let us know if this is correct or we are missing something obvious?

We dont always have ssh access to the customer VM. Please let us know regarding the same..

Status: 
Closed (fixed)

Comments

Yes, currently the Network Interfaces page only appears if the system has SSH access.

However, that may be fixable - are these virtual systems, or physical?

Both. Both types of machines have multiple interfaces with eth0 having publicly routeable addresses and eth1 etc being private interfaces.

For physical systems, Cloudmin requires SSH access to login and collect network interface stats. Only for Xen and KVM instances can the stats be collected "externally" without SSH ..

okay..certainly...

So for virtual systems, how do we specify the interfaces if there is no ssh access...?

In /etc/webmin/servers/ we observe that "bw_ifaces=eth0" is being added to the correcponsing .serv files...So for a quickish way, do we add "bw_ifaces=eth0" to .serv files of all virtual systems ?

Please advise

The work-around for now is to set the interfaces for bandwidth monitoring using the Cloudmin command-line API.

On the master system, run something like :

cloudmin modify-limits --host your-xen-instance --bw-interfaces eth0

I will fix the UI to allow interfaces for bandwidth monitoring to be set in this case in a future release. .

Shouldn't we be setting it like to measure bandwidth for only public interfaces where

cloudmin modify-limits --host your-xen-instance --bw-interfaces vifX.xx

something ?

Cloudmin will convert the VM interface name like eth1 to the appropriate vifX.1 interface when actually doing the collection. The X would vary depending on the ID of the Xen instance anyway ..

Cloudmin will convert the VM interface name like eth1 to the appropriate vifX.1 interface when actually doing the collection. The X would vary depending on the ID of the Xen instance anyway ..

Cloudmin will convert the VM interface name like eth1 to the appropriate vifX.1 interface when actually doing the collection. The X would vary depending on the ID of the Xen instance anyway ..

Cloudmin will convert the VM interface name like eth1 to the appropriate vifX.1 interface when actually doing the collection. The X would vary depending on the ID of the Xen instance anyway ..

Automatically closed -- issue fixed for 2 weeks with no activity.