THIS QUESTION TRIGGERED Moustafa TO START A JOURNEY-AN INNER SEARCH-OF TRUE PASSION, PURPOSE, AND MEANING which eventually led him to buying a ONE-WAY TICKET TO INDIA IN 2012. This is how Moustafa felt many years ago while he was running a multi-million dollar business in Dubai and living a seemingly successful life. So in our example up there, once we've picked a new hostname we'd need to go find our vCAC:Entity and updateVCACEntity with our new values since we actually want to override things in the request.Without knowing the answer to this question, you will always feel like something is missing, no matter how successful you are. Writing back to that object does nothing, of course. It's a lot easier to use than the old system and a lot more transparent, but does require a bit of effort to move to it.Įdit: more clarity for anyone who reads this: while you get all that data in JSON or what have you, it's still on you to update the appropriate entities. We do this at the state of Lifecycle State Phase "PRE" and Lifecycle State Name of "VMPSMasterWorkflow32.Requested" in this case to intercept the build request before anything is provisioned (and at this time do a bunch of things to prep the machine provisioning.) You can also create an input of the name "payload" with a type of "Properties" and it will just give you everything regardless, and it's up to you to parse it properly. So we have a workflow bound with an input of "machine" and type of "string" which winds up being a JSON object that we can parse for and get the custom properties of our incoming machine provisioning request, and then override the value as needed. This is broken down for you when you create the event subscription, for example this is Machine Provisioning: You basically create an input by a specific name and get a predictable input from the event broker. Similar to the old stubs, there is a predictable/expected input. If you add the stubs directly as a property they will show on the blueprint and the resulting object.Ĭorrect. This is how the custom hostnaming workflows used to work.Įdit: to be clear, if you inject (which is what that link did), you should only see the data show up after a request (meaning the blueprint says nothing, but the provisioning/provisioned item will have additional data injected). You can also embed thing into the sort of global execution thread that works the other way and looks for certain blueprints/phases being executed and joins in on the fun. One of them you wandered into: you can use custom properties on the blueprint to directly call a workflow ID at certain points. There are a bunch of ways to pin a workflow into a blueprint in vRA 6's stub style. That should have some basics on how to make it all work right. A lot of the old stub methods still exist and are needed to do a few things, but overall it was an (imo) confusing and opaque system. You may want to look at the Event Broker since you have this tagged as vRA 7.
0 Comments
Leave a Reply. |