Integration

NOTE: The Tensor9 team takes care of integration for vendors - free of charge. It typically takes 1-4 weeks, depending upon the vendor's stack.

Step 1: Create facades for containers, virtual machines, and infrastructure

Build a container facade from an existing container to using a single tensor9 CLI command:

tensor9 -action BuildContainerFacade -img my-node-service:ded9f4b -applianceId 844385dc6fa8d4fc

Build a machine facade by defining the type of machine desired (e.g. CPU, Memory, GPU) and using a single tensor9 CLI command to build a virtual machine image (e.g. AWS AMI) for the vendor facade.

tensor9 -action BuildMachineFacade -spec my-machine-spec.json -applianceId 844385dc6fa8d4fc -cloud Aws

Build an infrastructure facade (e.g. for a queue, storage bucket, managed database, etc) with Terraform HCL.

Once defined, facades can be deployed with AWS Cloud Development Kit, Azure Resource Manager, Google Deployment Manager, Pulumi, or Terraform.

Step 2: Declare external services

Define a list of external services (if any) the software will need to communicate with from within the customer's appliance. The customer will have to explicitly trust any external services vendor software communicates with. As always: data that leaves the appliance (literally every single byte) is appended to the audit log.

Step 3: Performance testing

Software and infrastructure running in a customer's appliance usually has performance and scaling characteristics that differ from the SaaS context. Functional and load testing is important to make sure the on-prem offering meets all SLAs.