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.

...

• SwarmSearch1: upgraded to elasticsearch 7.17.9 

• SwarmSearch1: switched to bundled jvm in /etc/sysconfig/elasticsearch, removed openjdk 1.8.x 

• SwarmSearch1: OEM-85, use the configure script to make an elasticsearch.yml file. 

• SwarmTelemetry: OEM-84, removed cluster_state alert 

• SwarmTelemetry: TELE-17, added job label to handle multiple enumeration feeds 

...

• SwarmTelemetry: added new dashboard Swarm Health Processor v1 (support only) 

• SwarmTelemetry: WARNING: all All dashboard panels migrated to the new grafana 8.x format, ; Grafana 9.3.2 is now required for all 15.3 dashboards. Some GUI functionality was lost, so the dashboard will look different. This is a required step to jump to the next hurdle, which is grafana 10.x , and its new UI 

• SwarmTelemetry: Swarm Search v7 now shows segment delete ratio, as well as hourly operations and per operation type charts. 

• SwarmTelemetry: added job definition for node_exporter on SCS 

• SwarmContentGateway: Upgraded to cloudgateway 7.10.6 / UIC 7.9.1/UIS 3.5.0 

• SwarmContentGateway: OEM-83, usePath reverts to default, and haproxy timeouts are adjusted to match our KB. 

• SwarmContentGateway: Upgraded to node_exporter 1.16.0 

• SwarmClusterServices: upgraded to swarm-storage 15.3.0 

• SwarmClusterServices: added node_exporter 1.16.0 

The bundle package can be found at DataCore Downloads.

Prerequisites

• 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 . 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.

Disk-to-VM Mapping

The following is a sample mapping example of OVF with the associated disks:

VM Template Overview

The following is a sample example of the VM template:

Software Versions

The following software versions are required for the Swarm 15.2 VMware bundle:

References