OnApp 5.2 is our first release with full support for recipes working with vCloud Director. Recipes are OnApp’s built in scripting system. You can use Recipes to customize virtual servers during provisioning, by installing apps, customizing configurations and a wide range of other useful, time-saving (and most importantly, billable) tasks.
OnApp v5.2 now uses VMware tools to push scripts to the virtual machines so that they can run even without connectivity to the outside world. This means there is no longer a requirement to have a public IP, and Recipes will work when connected to all three types of networks available within OnApp.
Since we are working with VMware tools, there are a few prerequisites that are required in order for them to work correctly inside of OnApp:
- Your OnApp CP must be able to communicate with the ESXi hosts within your vCloud Director environment directly.
- Guest customization must be enabled on the virtual machine(s) that you wish to run the recipe on.
- Administrator password must be set (or automatically generated) in guest customization section.
- OnApp must have a working vCenter password added to your vCloud Director hypervisor (this is also used to gather performance metrics).
As an administrator of OnApp, you should create some recipes that your end customers will be able to apply to their virtual machines. For more details and specifics on creating a Recipe, refer to our documentation portal: https://docs.onapp.com/display/52AG/Create+Recipe
You can apply Recipes in multiple ways:
- During vApp deployment, you can assign one, or multiple recipes to be run immediately post-deployment.
- You can apply specific recipes to one, or multiple, virtual machines from the recipes menu item on the sidebar.
- You can assign recipes to virtual machines, post deployment, based on certain triggers, directly from the virtual machine ‘overview’ menu.
Note: you will need to ensure that the roles you want to be able to assign these Recipes to have the appropriate permissions. For assigning Recipes during vApp deployment, there were new permissions added in OnApp v5.2 to allow this – under the vApp group, the permission “Assign recipes to VS” is required.