Each VCP node has the size parameter associated with it.
The size parameter is represented by the
salt:control:cluster:internal:node:<VCP_NAME>:size path in Reclass, where
<VCP_NAME> is the name of your VCP node. For example, for prx01:
root@cfg01:~# salt kvm01* pillar.items salt:control:cluster:internal:node:prx01:size --out json
{
"kvm01.<CLUSTER_NAME>.local": {
"salt:control:cluster:internal:node:prx01:size": "openstack.proxy"
}
}
The size parameter defines disk, network, RAM, and CPU metadata per a VCP
node class. For example:
root@cfg01:~# salt kvm01* pillar.items salt:control:size:openstack.control --out json
{
"kvm01.<CLUSTER_NAME>.local": {
"salt:control:size:openstack.control": {
"net_profile": "default",
"ram": 32768,
"cpu": 8,
"disk_profile": "small"
}
}
}
The disk_profile parameter is the profile that describes the disk
configuration for a VCP node. You can extend a VCP image and connect it to
a VM. For example:
root@cfg01:~# salt kvm01* pillar.items virt:disk --out json
{
"kvm01.<CLUSTER_NAME>.local": {
"virt:disk": {
"small": [
{
"system": {
"size": 8000
}
}
]
}
}
}