Hardware configuration inheritance for new nodes

When customer adds new nodes to the environment that is already deployed he has to setup network and hard disks configuration manually. But in most cases customer needs just the same configuration that already presented in the existing cloud.

Sometimes a customer adds new nodes a few monthes after the initial deployment, by this time no one remembers the details of hardware configuration. In simple cases the hardware configuration can be seen in UI but if nodes were configured through CLI it's not so easy to extract current configuration from database.

So it'll be nice to have some hardware configuration inheritance from old nodes (with the same role) to the new one.

It's also useful for big deployments with substandard configuration. In this case we can configure the one node with CLI and then just inherit this configuration.

There are many ways to implement this feature.

- We can forget about "default" configuration and use "default for this cloud" configuration. In this case user can change the configuration manually during the initial deployment and then save this changes as "default". After this all the new nodes can inherit this configuration.

- Another way user can select some deployed node in the UI and set the checkbox "Inherit hardware configuration from this node" or something.

- Import/Export hardware configuration in json or yaml files. In this case the file shouldn't contain any node ID so it can be applied on any node later.