System Requirements

The Spectro Cloud SaaS platform is also available as a self-hosted on-premise deployment. The On-Premise version is a dedicated instance of the platform hosted in the customer's VMware environment. Spectro Cloud on-prem is available in two modes:

  • Quick Start Mode - A single VM deployment of the platform ideal for PoC purposes.
  • Enterprise Mode - A multi-node highly available version for production purposes.

The sections below describe the standard requirements and highlight specific requirements for both the deployment modes.

vSphere Environment Prerequisites

  • General requirements:
    • vCenter version : 6.7 and above
    • NTP configured on all ESXi Hosts
  • Zone Tagging

    Zone tagging is required for dynamic storage allocation across fault domains when provisioning workloads that require persistent storage. This is required for the installation of the Spectro Cloud Platform itself and also useful for workloads deployed in the tenant clusters if they have persistent storage needs. Use vSphere tags on data centers (k8s-region) and compute clusters (k8s-zone) to create distinct zones in your environment.

    As an example, assume your vCenter environment includes three compute clusters, cluster-1, cluster-2, and cluster-3, that are part of datacenter dc-1. You can tag them as follows:

    vSphere ObjectTag CategoryTag Value
    dc-1k8s-regionregion1
    cluster-1k8s-zoneaz1
    cluster-2k8s-zoneaz2
    cluster-3k8s-zoneaz3

    Note: The exact values for the k8s-region and k8s-zone tags can be different from the ones described in the above example, as long as they are unique.

  • Permissions

The following permissions are required for the account used to install the platform:

vSphere ObjectPrivileges
DatastoreAllocate Space
Browse Datastore
Low level file operations
Remove file
Update virtual machine files
Update virtual machine metadata
FolderCreate folder
Delete folder
Move folder
Rename folder
NetworkAssign Network
ResourceApply recommendation
Assign virtual machine to resource pool
Migrate powered off virtual machine
Migrate powered on virtual machine
Query vMotion
SessionsValidate session
Storage viewsView
TasksCreate task
Update Task
Virtual MachinesChange Configuration
* Change Settings
* Change Swapfile Placement
* Configure host USB device
* Configure raw device
* Add existing disk
* Add new disk
* Add or remove device
* Advanced configuration
* Change CPU count
* Change resource
* Configure managedBy
* Display connection settings
* Extend virtual disk
* Modify device settings
* Query Fault Tolerance compatibility
* Query unowned files
* Reload from path
* Remove disk
* Rename
* Reset guest information
* Set annotation
* Toggle fork parent
* Upgrade virtual machine compatibility
Guest operations
* Guest operation alias modification
* Guest operation alias query
* Guest operation modifications
* Guest operation program execution
* Guest operation queries
Interaction
* Power off
* Power on
Inventory
* Create from existing
* Create new
* Move
* Remove
Provisioning
* Allow disk access
* Allow file access
* Allow read-only disk access
* Allow virtual machine download
* Allow virtual machine files upload
* Clone template
* Clone virtual machine
* Create template from virtual machine
* Customize guest
* Deploy template
* Mark as template
* Mark as virtual machine
* Modify customization specification
* Promote disks
* Read customization specifications
Service Configuration
* Allow notifications
* Allow polling of global event notifications
* Manage service configurations
* Modify service configuration
* Query service configurations
* Read service configuration
Snapshot management
* Create snapshot
* Remove snapshot
* Rename snapshot
* Revert to snapshot
vSphere Replication
* Configure replication
* Manage replication
* Monitor replication
vAppImport
View OVF environment
vApp application configuration
vApp instance configuration
vSphere TaggingCreate vSphere Tag
Edit vSphere Tag

Network Requirements

  • Outgoing access from the platform VMs to the internet either directly or via a proxy.
  • An IP Address (static or DHCP) for the quick start virtual machine (also used as an installer for enterprise version).
  • A block of 5 IP addresses reserved for enterprise cluster. One IP address for each of the three enterprise cluster VMs. An IP to be used as VIP and an additional IP reserved for rolling upgrades.
  • Interconnectivity across all the 3 VMs on all ports.
  • Connectivity from the Virtual Machines to the vCenter.
Make sure that your Datacenter CIDR IP address does not overlap Kubernetes PodCIDR range. Kubernetes PodCIDR range settings can be changed during installation.

Proxy Requirements

  • If a proxy is used for outgoing connections, it should support both HTTP and HTTPS traffic.

  • Connectivity to the following domains and ports should be allowed:

    Top-level DomainPortDescription
    spectrocloud.com443Spectro Cloud content repository and pack registry
    s3.amazonaws.com443Spectro Cloud VMware OVA files
    gcr.io443Spectro Cloud and common 3rd party container images
    docker.io443Common 3rd party container images
    googleapis.com443For pulling Spectro Cloud images
    docker.com443Common 3rd party container images
    raw.githubusercontent.com443Common 3rd party content
    projectcalico.org443Calico container images
    quay.io443Common 3rd party container images
    grafana.com443Grafana container images and manifests
    github.com443Common 3rd party content

Hardware Requirements

The following section provides the hardware requirements for Spectro Cloud Platform VMs for various capacity levels.

  • Concurrent Tenant Clusters - The number of concurrent tenant cluster provisioning or deletion requests.

  • Total Managed Clusters - The number of parallel running tenant clusters.

    The size of the tenant cluster in terms of the number of nodes or size of the nodes does not impact the capacity guidance below.

Quick Start

CategoryConcurrent Tenant ClustersTotal Managed ClustersNo. of VMsMemoryCPUsStorage
Standard32018Gb4 Virtual CPUs80 GB

Enterprise

CategoryConcurrent Tenant ClustersTotal Managed ClustersNo. of VMsMemoryCPUsStorage
Standard320038Gb4 Virtual CPUs80 GB
For high availability purposes, it is recommended that you deploy the 3 VMs across 3 compute clusters.

Best Practices

The following steps are optional but recommended for production environments.

  • DNS Mapping:

    A DNS is used to access Spectro Cloud Management Console. While the Virtual IP Address (VIP) configured on the platform can be used to access the platform, it is recommended that you reserve a DNS for this purpose and map it to the VIP after installation.

  • SMTP Settings:

    Configure SMTP settings to enable the Spectro Cloud platform to send out email notifications. Email Notifications are sent out to new users when they are initially on-boarded to the platform so they can activate their accounts as well as to reset their password at a later time.

  • Trusted Certificate:

    Configure your platform with a trusted CA certificates.

  • FTP Location for backups:

    Configure a FTP location for platform backups and schedule daily backups.