![]() ![]() When deploying a new SimpliVity Federation an Arbiter and the vCenter environment must exist prior to the deployment of the SimpliVity nodes. The Arbiter and the vCenter Server are required components of a HPE SimpliVity Federation. I also refer to the HPE SimpliVity Arbiter as the Arbiter. Note that I refer to the HPE SimpliVity Federation, as a SimpliVity Federation, or just simply as a Federation. Platform Services Controller (PSC) and vCenter Server Topology and Placement. ![]() HPE SimpliVity Arbiter Requirements and Placement.The following are two of the key factors which influence HPE SimpliVity Federation design which this post will focus on: This post also includes two HPE SimpliVity Federations design examples. This post provides an overview of HPE SimpliVity Federation design focusing on the HPE SimpliVity Arbiter’s function, the Arbiter’s requirements, and the placement of the Arbiter along with some guidance on the design of the vCenter environment supporting an HPE SimpliVity Federation. Most of the questions are around the purpose and placement of the Arbiter, support for vCenter running in a SimpliVity Cluster, and the deployment topology to use for the vCenter environment. I get a lot of questions about the SimpliVity Federation.
0 Comments
Leave a Reply. |