This section discusses more options in the SE Group configuration, which are specific to the cloud that the SE group is created under.
High Availability and Placement Settings
VS Placement across SEs: When placement is compact, NSX Advanced Load Balancer spins up and fills up the minimum number of SEs and places the virtual services on SEs which are already running. When placement is distributed, NSX Advanced Load Balancer maximizes virtual service performance by avoiding placements on existing SEs. Instead, it places virtual services on newly spun-up SEs, up to the maximum number of Service Engines. By default, placement is compact for elastic HA N+M mode and legacy HA active/standby mode.
Host and Data Store Scope
Host Scope Service Engine: SEs are deployed on any host that most closely matches the resources and reachability criteria for placement. This setting directs their placement as follows:
Any: The default setting allows SEs to be deployed to any host that best fits the deployment criteria.
Cluster: Excludes SEs from deploying within specified clusters of hosts. Checking the Include check box reverses the logic, ensuring SEs only deploy within specified clusters.
Host: Excludes SEs from deploying on specified hosts. The Include check box reverses the logic, ensuring SEs are only deployed within specified hosts.
Data Store Scope for Service Engine Virtual Machine: Sets the storage location for SEs to store the OVA (vmdk) file for VMware deployments.
Any: NSX Advanced Load Balancer will determine the best option for data storage. n Local: The SE will only use storage on the physical host.
Shared: NSX Advanced Load Balancer will prefer using the shared storage location. When this option is clicked, specific data stores may be identified for exclusion or inclusion.
