Your SEE does not require any additional software to be installed for the default operation. It does, however, require one or more network ports to be configured so that you can communicate with the Secure Foundation Platform (SFP) hypervisor to install your application(s) which will reside in one or more virtual machines.
Once you have configured your network ports, you can use SSH to access the SFP and configure one or more virtual machines that will execute your application. The SEE is configured to only allow public key authentication access to the SFP. Your SSH private key is delivered to you as part of the SEE delivery and you should ensure to keep it safe.
Your applications will be executed in one or more virtual machines. The virtualization engine which the SFP provides is based upon KVM (Kernel-based Virtual Machine) and QEMU (Quick EMUlator) and allows you to execute Linux based virtual machines without the need to install additional device drivers.
The SEE does not provide tools to create a virtual machine from scratch and it is recommended to use the SEE to create a virtual machine from an installation disk or an installation USB drive. The virtual disk image (or images) must be created and tested outside the SEE. Once you have a working VM image file, this is imported into the hypervisor using the SCP command or the upload function in WebConf. While the SEE does not provide a method to create virtual disk image files, it does provide protection against theft and manipulation of your applications and data, once your application is deployed.
The following sections provide information on the SEE network ports and describes how to power on the SEE and access PrimeKey’s integrated Lights On (PiLO).