| 2013-01-30 07:58:37 |
Raphaël Badin |
description |
The first cluster controller to connect to the region is assumed to be the local (i.e. running on the same machine as the region) cluster controller. It is automatically accepted and the hostname sent to the nodes handled by this cluster will be the one used by the region controller itself.
Two problems:
- accepting a remote cluster is a security risk
- if the first cluster to connect is not the one installed alongside the region (i.e. if "maas-region-controller" is installed separately and a cluster controller is installed on another machine), the pxe config information sent by this cluster to the nodes will contain a wrong address (it will contain the address of the region controller).
Either we fix these 2 problems of we force the installation of a cluster controller alongside the region controller (i.e. we make 'maas-region-controller' depend on 'maas-cluster-controller'). |
The first cluster controller to connect to the region is assumed to be the local (i.e. running on the same machine as the region) cluster controller. It is automatically accepted and the hostname sent to the nodes handled by this cluster will be the one used by the region controller itself.
Two problems:
- accepting a remote cluster is a security risk
- if the first cluster to connect is not the one installed alongside the region (i.e. if "maas-region-controller" is installed separately and a cluster controller is installed on another machine), the pxe config information sent by this cluster to the nodes will contain a wrong address (it will contain the address of the region controller).
Either we fix these 2 problems or we force the installation of a cluster controller alongside the region controller (i.e. we make 'maas-region-controller' depend on 'maas-cluster-controller'). |
|
