I did some tests with a DHCP green, but it didn’t work properly. Unfortunately I didn’t access to the vps console, I saw only that nethserver had problems when the ip changed. I tried to add a script to compare ip in the db and ip obtained via dhcp, and correct the db if needed, but I lost access.
I agree that dhcp on vps is a scenario we need to support perfectly.
Since dhcp is supported on red, we could find a way to build a red-only system. Or assign the green role to a “virtual card”.
The red-only scenario is not a viable option, we already did some tests in the past.
We must stick on a green-only configuration with a static IP address.
Maybe we could fake somehow the dhcp scenario, by running dhclient for the green interface and saving the current ip address inside the db. Also the system must ignore dhcp renewal for green interfaces.
This can be done.
I agree, if this option is set, the system must be configured in a peculiar way.
This is a wrong assumption. For example, on Rackspace (which is a big VPS player) the server has 2 interfaces: one for the outside world and one for connecting to other vm inside the same data center.
Beside this, I don’t get what is the purpose of a virtual green interface. Could you make an example?
This is much work distributed across many package. I’d propose a simple documentation with some cut&paste commands to harden the system if installed on a VPS.
Still my implementation lacks web interface support, but we could already do some tests.
The implementation doesn’t parse any ifcfg file, but uses the dynamic flag present inside the ip address show command output.