VMware Cloud Community
ronaldod
Enthusiast
Enthusiast

second day actions

Hi Specialists.

Having the next issue.

I use second day actions for adding disks, extend, etc. As a requirement we need to add some external logging to it.

I could make a workflow that is doing this direct on the vCenter but then the deployment in vRA is not updated. And i could use an async call to the standard second day but then i loose the ability to monitor the progress of this action.

Anyone an idea how get this done with the following requirements

  • can monitor the action
  • vRA deployment is updated when action is done.

 

Curious on your input

Reply
0 Kudos
2 Replies
emacintosh
Hot Shot
Hot Shot

What are your logging requirements?  Do you just need to capture that it was launched/completed and the inputs?  Or do you need to capture the workings of the action itself?

We log the majority of requests to Splunk by subscribing to the relevant event topics.  So in this case, it would be subscribing to deployment.resource.action.pre/post topics.  And then the workflow that is called enumerates the inputs, gets the status, etc. and sends it over to Splunk.  And then we build dashborads to see which day-2's are being run, if they're succeeding, etc.

We also log our scripts there as well.  So if we write any custom day-2 actions, the corresponding script we ultimately call to do the work will send its params/details/messages to Splunk as well.  Although, that wouldn't be an option for oob day-2 actions of course.  

Reply
0 Kudos
ronaldod
Enthusiast
Enthusiast

The workflow is pushing data to ticket system. Send emails with details. etc. So the "second day" is pretty large and was using it from the VRA. Now thinking to move the functionality to the service broker. And use the id of the machine as disk as one of the inputs.

 

Reply
0 Kudos