Transcript
In this screencast, we will show how to provision a cluster at the public cloud provider using OpenAble Affirmation. There are a few challenges when managing multi-site, multi-cloud deployments. Each public cloud provider has its own way of approaching similar things, deploying bare metal hosts, managing the IP address ranges, managing the IP address ranges, and enrolling the secure shell keys. Manual provisioning itself is time consuming and leaves room for error. OpenAble Affirmation is addressing these and other challenges by providing the unified approach to provision clusters both on-prem and at the selected public cloud provider. Even considering that there are going to be some settings that are exclusive to a specific public cloud provider. OneForm is also going to take care of everything from enrolling keys to deploying and configuring hosts, creating networks, and forming a single cluster out of provisioned resources. In the end, an administrator will have a ready-to-use cluster. Once the resources are no longer needed, OneForm will take care of deprovisioning these resources and removing them from the public cloud provider. OneForm is a separate package and needs to be installed separately. Provider drivers are not bundled with the package and are maintained in a separate repository, which gives the flexibility of updating, fixing, and extending this without affecting the OpenAble core. Under the hood, OpenAble Affirmation relies on common technologies such as Terraform, Ansible, and our own OneDeploy collection. Now let's walk through the process. OneForm is distributed as a separate package and must be installed separately. Please follow the official documentation to install OneForm and import the provider drivers. Before provisioning any clusters, you must create a provider. Navigate to Providers tab. By default, you have only the on-prem provider configured. Press the Create button to start the wizard. Now you must select the specific driver for the provider. While at the moment of recording, there are three provider drivers, the project is continuously developed and the number of providers is growing. For this demonstration, we will create a provider with a scaleway driver. Name your provider and proceed to the next configuration screen. Each driver has an individual set of values you need to supply. In the case of scaleway, these include the access key, secret key, and project ID. Additionally, you should select the region and zone. In this demonstration, we will be using Paris region and the Paris 2 zone. Press the Finish button to finalize the process. Now that the provider has been added, we can provision a cluster. Navigate to the Clusters tab. OneForm will take care of provisioning hosts, networks, and data stores, and will add them as a separate cluster. Press the Create button and select the Install a new cloud cluster option from the list. For this demonstration, we have only one provider available. Name the future cluster. On the Deployment Type page, select the scaleway SSH cluster. Note that each provider has its own set of deployment types. On the User Inputs page, configure the provision. Define the number of hosts to provision, host operating system, VXLAN network range, instance type, and the number of public IPs. On the last page, before starting the provision, you can define tags. These tags will be transformed into the provider supported tags and will be applied to the provisioned resources. The provision may take some time to finalize, and this time heavily depends on the driver you've chosen. You may follow the deployment either in SoundStone or switch to the command line and view the log file. OneForm logs can be found under the var log1 OneForm directory. In this case, the ID of the provision is 2, and the name of the file is 2.log. The running state indicates that the process is over and the cluster has been provisioned without any errors and is ready to use. Reviewing the resources, we can see the virtual networks, data stores, and hosts that are part of the provision. Let's verify that the cluster can be used. First, navigate to the storage, apps, and download an image from the marketplace. In this demonstration, we will use OpenSUSE 15. Let's wait until the image is in the ready state. Now let's instantiate the OpenSUSE 15 virtual machine template from the Templates, VM Templates tab. We will deploy two virtual machines to make sure that both hosts can handle the load, and we will proceed with the default settings. Additionally, let's set the newly provisioned cluster as a scheduling requirement and press the Finish button. In a brief moment, we can confirm that virtual machines were deployed successfully and are running on two different hosts. Once the cluster is no longer needed, we can deprovision all of the resources from the same clusters page. After a while, we can confirm that the resources are destroyed. And this concludes the screencast where we will be using OpenSUSE 15 to deploy virtual machines to our virtual machines. We have shown one form in action by provisioning a cluster at the scale with Cloud Provider, deploying two virtual machines to verify that the cluster can handle the workload, and then deprovisioning the cluster, confirming that every action is done using OpenAble or Sunstone without accessing the specific Cloud Provider's control panel. Thank you for watching and see you in the next screencast.
