Whitepaper 'FinOps and cost management for Kubernetes'

OptScale is fully available as an open source solution under Apache 2.0 on GitHub

Ebook 'From FinOps to proven cloud cost management & optimization strategies'

Get the ebook

Technical whitepapers

Deployment requirements for Hystax Acura

Hystax Acura component

System requirements

Network requirements

Allow traffic to/from the following ports

Hystax Acura (controller)

deployed from the image provided by Hystax

VM with:

• 8 vCPUs
• Memory: 16 GB RAM
• Disk space: 200 GB drive

• Ingress - tcp/443
• Ingress - tcp/4443
• Ingress - udp/12201
• Egress - tcp/443
• Egress - tcp/80 (to Hystax Cloud Agent)
• Egress - tcp/3260 (to Hystax Cloud Agent)

Cloud Agent (VMware)

downloaded from Acura Control Panel and deployed from an OVA template

VM with:

• 2 CPUs
• Memory: 4 GB RAM

• Ingress - tcp/80
• Ingress - tcp/3260
• Ingress - udp/15000
• Egress - tcp/udp 902 (to ESXi hosts)
• Egress - tcp/443 (to vCenter and ESXi hosts)

Cloud Agent

(all other supported cloud platforms)

VM with:

• 2 CPUs
• Memory: 4 GB RAM

• Ingress - tcp/80
• Ingress - tcp/3260
• Ingress - udp/15000

Replication Agent Windows

downloaded from Acura Control Panel - internal

• Memory: 2 GB RAM
• CPU: x64 processor
• Disk space: 100 MB required for product installation and not less than 15% free space of disk size for VSS snapshots creation Software:
• Microsoft .NET Framework 4.0

• tcp/443 - send data to the Acura host
• udp/12201 - send logs to Acura

Replication Agent Linux

downloaded from Acura Control Panel - internal

• Memory: 500 MB RAM
• Disk space: 100 MB required for product installation and not less than 15% free space of disk size for snapshots creation

• tcp/443 - send data to the Acura host
• udp/12201 - send logs to Acura

Replication Agent VMware

downloaded from Acura Control Panel - external

VM with:

• 2 CPUs
• Memory: 4 GB RAM

Note: there are several host permissions that the agent requires to operate

• Source host - tcp/80, tcp/443
• vSphere host - tcp/443
• ESXi host(s) - tcp/udp/902
• udp/12201 - send logs to Acura

Failback Agent VMware

Note: host permissions

• tcp/80 - communicate with the Acura host
• tcp/443 - vSphere host
• tcp/udp/902 - ESXi host(s)
• udp/12201- send logs to Acura

Failback Agent Flexible Engine

Note: host permissions

• tcp/443 - communicate with the Acura host
• udp/12201 - send logs to Acura
• Ports to communicate with the cloud API, e.g. tcp/5000 for keystone

Failback Agent OpenStack

Note: host permissions

• tcp/443 - communicate with the Acura host
• udp/12201 - send logs to Acura
• Ports to communicate with the cloud API, e.g. tcp/5000 for keystone

Failback to other clouds

For other clouds, failback is done in a form of a live reverse migration of workloads to the source environment. Internal replication agents are installed directly to failover machines.

To run ML/AI or any type of workload with optimal performance and infrastructure cost with OptScale – a FinOps and MLOps open source platform, contact us today.