Any way of disabling Orchestrator cache?

[Zeppa]

Hello everybody,

We're facing some inconsistences while working with workflows and vcloud director web console in parallel, especially when we have to pick inputs at the beggining of the workflows.

Any chance of disabling the cache?

Thanks,

Luciano

[cdecanini_ · Accepted solution]

What version of the vCloud plug-in are you using ? 1.5 or 5.1 ?

There is no way to disable it but in 5.1 you can change the timeout. If you put a short one you will get close to real time but then it may impact performance.

Christophe.

[Zeppa]

I'm using 1.5. And vloud is also 1.5 Any problem with my current workflows developed for 1.5 if I install the new plugin?
Thanks Chris.Tell me also where to look for the param to tweak timeout.

[cdecanini_]

The 5.1 plug-in requires vCloud 5.1. The parameter is right on the vCDHost object.

I wrote a document about upgrading from vCD 1.5 custom workflows to 5.1. It is in the document section (here)

Is the problem that when someone create / delete an object in the vCD UI you do not see the update before 20 min in vCO ?

There is a way to force the update programatically with calling updateInternalState on the parent object. If you do it on the vCDHost it should update your inventory. Again if you set a recurrent task to do this every 3 min it will reload all the objects everytime so this may not be optimal.

Christophe.

[cdecanini_]

OK I have to correct my last statement.

UpdateInternalState() only refreshes the scripting object so next time you use this object within the workflow it is updated.

It has nothing to do with refreshing the inventory. The inventory is automatically refreshed by calling methods creating / deleting objects.

In the vCO client part of the inventory can be refreshed with right click refresh. F5 will refresh everything.

In the vSphere Web client the inventory is re-discovered everytime you need it to select an object.

Christophe.

[Zeppa]

Thanks again