search

vmware-samples / vcenter-event-broker-appliance

The VMware Event Broker Appliance Fling enables customers to unlock the hidden potential of events in their SDDC to easily create event-driven automation.
Other
157 stars 68 forks source link

Enable the VEBA appliance to be built automatically via GitHub Actions and a self-hosted runner in a private environment. #724

Closed AndyTauber closed 2 years ago

AndyTauber commented 2 years ago

Is your feature request related to a problem? Please describe. In order to enable the future goal of having automated testing of the VEBA appliance, we will first need to create an automated build process for the VEBA appliance.

Describe the solution you'd like The VEBA appliance build requires an ESX host and vCenter and so is not able to be built by a GitHub provided runner. A self-hosted runner in a private environment will be necessary. The current repo will need minor changes to the variable structure and the addition of a powerCLI script to fix the photon VM to a specific host so that DRS does not move it.

Describe alternatives you've considered Instead of a private lab, we may look at building the VEBA appliance in VMC on AWS.

github-actions[bot] commented 2 years ago

Howdy 🖐   AndyTauber ! Thank you for your interest in this project. We value your feedback and will respond soon.

AndyTauber commented 2 years ago

We were able to POC a self-hosted runner within a private environment but found that the solution had too many limitations. If the environment is truly private, retrieval of the resultant OVA to be used in further testing becomes difficult. The environment is also relatively complex (requires vCenter and ESXi host). For using a self-hosted runner in corporate environments, there are security concerns that are difficult to mitigate. From what we learned, the suggestion is to not use github actions to build in a private environment and will close this issue.