The HN requests additional CNs from the PCM (Pool Cluster Manager). Accordingly, the PCM checks the contract conditions for the customer, schedules pool nodes for customer use and “moves” them to the customer cluster (= assigns them to the requested customer VLAN).
The pool nodes by default are cleaned (HDD erased, audit report) and provisioned with mini Linux on RAM disk. They are moved to the customer cluster along with audit certificates on cleaned disk(s). At the customer cluster, the new nodes get provisioned with the customer preferred setup, OS, configuration, retrieved from the customer individual private repository.
By receiving customer specific setup, the new nodes become CNs of the customer cluster. Although provisioning can be provided and managed by customers themselves, VCODYNE initially deploys a VM based management node (MN) for this purpose as optional starting point. This MN resides on the HN inside the customer cluster and is – like anything inside the customer perimeter – under full control (root access) of the customer. Also, the images or packets to be deployed are stored on the individual HN and are not shared with any other customer. VCODYNE equips the MN with a number of images to start with while the customer is free to modify, replace or delete.