Logical divisions of a subnet in Foreman, separate to physical and proxy layout
In our computing cluster we use a full class B network for all the machines. Inside this class B we do a logical clasification. As example:
10.1.1.1 to 10.1.1.254 subnet 255.255.0.0 >> nodes hardware A
10.1.2.1 to 10.1.2.254 subnet 255.255.0.0 >> nodes hardware B
10.1.3.1 to 10.1.3.254 subnet 255.255.0.0 >> storage nodes
I am deploying foreman and for us it would nice to be able to define all this "false subnets" inside foreman. This way if we now add "nodes hardware C" and define a hostgroup inside foreman for these machines, we could define that every node in this hostgroup is in "subnet-nodes-hardware-C" which would be something like 10.1.4.1 to 10.1.4.254 netmask 255.255.0.0
I tried to achieve this setup but I have seen that if for example I add to foreman the "false subnet" with "network address" 10.1.5.0 and netmask 255.255.0.0 associated to my hostgroup "nodes hardware X", when foreman tries to communicate with my dhcp it fails because foreman looks for subnet 10.1.5.0 in the dhcp which doesn't exists because the only available network in the dhcpd is the class B 10.1.0.0/255.255.0.0
This is an example error in my proxy log when foreman tries to suggest a free ip:
10.1.0.3 - - [16/Sep/2014 17:40:54] "GET /10.1.5.0/unused_ip?from=10.1.5.1&to=10.1.5.254 HTTP/1.1" 404 25 0.0094
And this is the error when I manually insert the ip in this range in the foreman webui:
E, [2014-09-16T17:41:15.907528 #6087] ERROR -- : No Subnet detected for: "10.1.5.0" D, [2014-09-16T17:41:15.907994 #6087] DEBUG -- : /usr/share/foreman-proxy/modules/dhcp/dhcp/server.rb:110:in `addRecord'
Of course it's just a suggestion but adding this feature to foreman would be really nice :)
By now I will just define the B class in foreman.
thanks for your work and for this great software.