From talking today with John Eckersberg and Scott Henson,
We're going to get network objects kicked into further gear soon, we think.
Just to give you the idea of the power involved, if you were doing a
/fully static deployment/ you could define a network, and then for each
system you would only have to define:
(A) the MAC addresses
(B) what network each MAC was on ("lab", "external",
"etc")
(C) whether the interface was static or not.
(D) optionally the dns-name, if using the DHCP management feature
All other parameters could be filled in, meaning if you are familiar
with all the data entry for static systems, this completely goes away.
We are going t add a drop down to each interface to specify which
network to use.
If the network is selected, the other fields in the network interface
editor will disappear.
We have a bit of work to do to handle what happens when you assign a
system to a different network (edit) or remove a system from a network,
etc.... but that is pretty much the only major roadblock
left from fleshing this out.
I can see this being a hugely powerful feature, even more so for the
static cases.
--Michael
Show replies by date