MacStadium Ideas/Feature Requests

Pass metadata to VM on launch

the lack of any ability to pass any kind of metadata or customizations into the launched workers is causing us some headaches. Our current workflow relies on being able to correlate the VM instances launched with those connected to Jenkins. With GCP etc, that's easy as we can set the VM name on launch, and that information passes down into the VM... 
Would like to pass at least the hostname to the VM
  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Oct 22 2019
  • Developing
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    19 Oct, 2020 09:40am

    I can't stress this enough how important this feature is for those organizations that launch multiple replicas and just can't differentiate them without some sort of metadata access from within VM.

  • Admin
    Howard Su commented
    9 Sep, 2020 06:01pm

    Thank you very much for the feedback Jan! We will take this to the development team. It is very helpful to know what other similar experience customers enjoy using.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    9 Sep, 2020 03:19pm

    VM tagging/labeling would be also a welcome feature, something similar to

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    14 Apr, 2020 06:17pm

    Metadata on VM: A customer would like a file with (minimum) container ID and node/port information on creation.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    3 Jan, 2020 06:59pm

    Possible solution: Create K8s label for pod, persisted as env variable. written to file and persisted to MacOS.