Agreed it is a framework that can connect to any type of API.
But is it truly an open-source framework ?
I say : not when it comes to reservations.
I've been working practically non-stop with WFA and I've had a lot of challenges with the "cached datasource"-model.
Since you're always looking at cached information, the whole OCUM-resynch cycle can be a pain in the ass.
Just think about provisioning :
Each object that is created has be available in the datasource for the next workflow, or it will fail.
Reservations can overcome a lot of those issues.
When you create a volume with the certified WFA command, that volume will appear the get-volume-finders.
And that's because the certified commands can add reservations.
But it's not always possible to use the certified commands.
Sometimes I want to create my own create-rename-delete commands.
So this a warm request to allow us to add/remove our own reservations.
How hard can it be to open the reservation through an API ?
Only then will WFA be truly "open source".
I think that this is a great discussion point, Mirko. It is definitely something that I have had challenges with. I too have been working with WFA forever (in fact since the Alpha days of 0.6 [wow it has been forever]). Honestly, the introduction of reservations in 1.1.1 was huge. The limitation on the existing commands has made working with reservations very difficult. I have two major issues with lack of reservation support.
Mirko, thank you for starting this conversation. I agree that this is something that we should discuss and bring up with the WFA team.
Jeremy Goodrum, NetApp
@ I also agree completely that waiting for UM to refresh (UM6.0 doesn't even have a way to force a refresh [not as far as I have found] so this means a hard set 15min) does not work.
Attaching commands that can be of some help here.
The 2 commands :
(1) Refresh Monitoring on OCUM6.0 for a given cluster
(2) Run the DataSource acquisition for a given scheme.
These 2 commands can be used as the end commands in a workflow and work quite good. It solves the need for command reservation to some extent.
3. Powershell 3.0 ( needed by the "Run the DataSource acquisition" command )
I agree with everything that has been said so far. I'd love to have a way for adding reservations in custom commands and had a few situations in the past were this caused issues.
Not sure if "open source" is the correct term for this discussion as WFA itself is not an open-source product (and not intended to be) though it is very open. But everything that is used by certified content should be available to custom building blocks as well and reservations is the one big exeception we currently have.
Regarding "How hard can it be" - I'm sure there was a good reason to not open up this mechanism so there is likely some technical challenge to this. It should still be possible to do but there wasn't any non-open-source motivation included in the initial decision.