Installation & Configuration
Extract the downloaded archive containing the virtual appliance and import it using either the Windows vSphere Client or the VMware vSphere Web client.
After choosing the Cluster, ESXi Host, Datastore and Network, the OVF Deployment Wizard asks you for the vApp specific settings.
These are the Guest OS settings consisting of:
- Network Configuration, DHCP enabled or IP (Don´t forget the DNS server that is used to resolve your vCenter and Slack.com!)
- Proxy if needed (important as OpBot needs to connect to Slack.com)
- VMware vCenter IP or FQDN (remember to configure DNS if needed)
- VMware vCenter credentials (please only use a read-only user for security reasons)
- Slack API token (the one you wrote down when adding the custom bot)
- OpBot Key - you should have received an email when starting your trial
That´s it – just power on the virtual machine and if everything has been setup correctly, OpBot should be active in Slack.
Important: You can change any of the configurations within the vApp settings and restart the VM to activate them. Just think about a password change for the VMware vCenter account.
Import using PowerCLI
If you want to automatically import the vApp into your vCenter without typing all information manually, please customize the following PowerCLI snippet:
Update of the appliance using PowerCLI
Luc Dekens wrote a great article how to upgrade the appliance and saving all the vApp settings before: http://www.lucd.info/2017/01/10/upgrade-appliance-ovftools
|Can I deploy multiple Bots within one Slack account?|
Yes, but Slack doesn't allow multiple OpBots at the same time. Nevertheless, you can just add another integration and use a custom bot (search for Bots). You can use the Slack Token for another deployed OpBot appliance.