Page Comparison

...

This bundle contains a collection of supported VMware templates for use in proof-of concepts and -concept and production field deployments. Each VM contains all the necessary DataCore Swarm software as well as dependencies. The software packages are pre-installed and unconfigured.

...

• A dedicated vSwitch for the Swarm Storage Network before importing VMs with the dual virtual network card.

• VMs are created on VMware ESX 7.0 and must be loaded into 6.7 U3 and above.

• If using vCenter, use the VMware vAPP OVF datacore-swarm-15.3.0-ESX.ovf to load the entire set of VMs in one command. Must include the nvram files as well.

• If not using vCenter, use an individual OVF for each template. This requires specifying the associated disk for each VM.

• A field engineer is required to configure the node_exporter service for the gateways in /etc/prometheus/prometheus.yml, an example is provided in the comments.

• A field engineer is required to configure the node_exporter service for the SCS in /etc/prometheus/prometheus.yml

• A field engineer is required to configure and deploy the elasticsearch_exporter service on the SwarmTelemetry VM. The process is as follows:

  1. modify the Elasticsearch Node IP in /usr/lib/systemd/system/elasticsearch_exporter.service file

  2. systemctl daemon-reload

  3. systemctl enable elasticsearch_exporter

  4. systemctl start elasticsearch_exporter this will start the service and listen on port 9114

  5. modify /etc/prometheus/prometheus.yml and uncomment the elasticsearch job definition pointing at port 9114

  6. promtool check config /etc/prometheus/prometheus.yml to verify no typo errors were done made in the config file.

  7. systemctl restart prometheus to activate the change

  8. Now you will see metrics populate the Swarm Search v7 dashboard.

...