Over the past few months I've been helping to get Oracle Solaris available in the Oracle Cloud. In particular, the Oracle Cloud Compute Service is an Infrastructure as a Service (IaaS) offering that allows users to create VMs on demand using a self-service web portal. Not unlike OpenStack, users can choose from a variety of shapes based on the number of virtual CPUs (defined by Oracle CPUs) and memory to allocate to the VM. There are a number of pricing options from dedicated environments that are single tenant, unmetered and avoid any possible noisy neighbour effect, to shared, multi-tenant environments.
Creating a VM on the service is super easy and I've walked through a typical user experience at the following screencast:
To be consistent with the existing experience using the compute service with Oracle Linux, we've pre-configured a default opc user that you can use to log into your VM environment using your SSH public keys. We've made sure though that's we're also consistent with Oracle Solaris security best practices, so this user will be assigned the System Administrator privilege, and have access to the root role with an expired password of solaris_opc. We've also changed the default IPS publisher from the Oracle Solaris release repository to the support repository - since all users of the compute service will get a support entitlement to access the latest Support Repository Updates and file bugs against Oracle Solaris at no additional cost.
There's a couple of gotchas that are worth noting - in particular when you create a bootable storage volume separately to creating your VM instance. This is because the compute cloud service also supports the ability to create ephemeral storage volumes (storage volumes that are created and destroyed as you start and stop your VM). If you're wanting to update the VM with the latest SRU, you'll need to be careful during your instance creation, as shown in the following screencast: