1 Reply Latest reply on Nov 23, 2019 4:51 PM by DionRow

    vRA 8 - Extensibility and VM MAC address

    DionRow Novice
    vExpert
    DionRow Nov 5, 2019 10:48 PM

      I have been working with the new inputProperties variable in vRO to attempt to extract the MAC address assigned to the deployed VM.  This is required for out DHCP/DNS registration process extensibility integration.  How can I extract this in the most efficient and reliable manner?

       

      I see that the MAC address is visible in the custom properties in "Deployments" when the VM is selected so Assembly and the Broker are obviously getting it somehow. 

       

      I could use the name of the VM and search the VC using the VC plugin then extract the MAC from there.

       

      But is there a better way?

       

      Thanks

      • 243 Views
      • Tags:
        • 1. Re: vRA 8 - Extensibility and VM MAC address
          DionRow Novice
          vExpert
          DionRow Nov 23, 2019 4:51 PM (in response to DionRow)

          We finally found the IPAM integration document for VRA8 and have been working to implement it.  This seems like the best way.  The documentation refers to the IPAM solution example from Infoblocks which can be used to work from.  It has a lot of extra stuff that is Infoblocks specific but once removed we were able to implement.

           

          The hardest was having to re-upload changes continually to test during development.  We ended up figuring out that we only needed to upload the first time and then change the "system" field in the database for that action to allow us to edit it in the VRA interface.  Once you edit it you change it back and test. 

           

          The command to make the action appear in the interface is:

           

          kubectl exec postgres-0  --namespace=prelude  -- sudo su postgres -c "psql -d abx-db -c \"update  abx_action set system = not system where id like 'DionsTest_%'\""

          then you may need to set the project for the action to test it

           

          once ready to test the IPAM switch it back to a system action:

           

          kubectl exec postgres-0  --namespace=prelude  -- sudo su postgres -c "psql -d abx-db -c \"update  abx_action set system = not system where id like 'DionsTest_%'\""

          kubectl exec postgres-0  --namespace=prelude  -- sudo su postgres -c "psql -d abx-db -c \"update  abx_action set project_id = '' where id like 'DionsTest_%'\""

           

          I will document this whole process at some point to help the next person.

          1 person found this helpful