community 
Connected Commands - non PDU use cases
I am thinking of using a feature 'Run Connected Resource Command' for non-PDU resources.
The PDU case is described here. It is not clear to me what is the significance of Tags="power"
Any experience with this feature for non-PDU resources?
Here is the use case:
- the sandbox resources (different sandboxes) are connected to a shared firewall
- the shared firewall is admin-only resource, and not part of the sandboxes reserved by the regular users
- users need to run resource commands that will do actions on that shared firewall (set ACLs, etc.)
Hi,
We indeed encountered requests for modelling devices that support "connected commands" outside of the PDU use case. We've just released a new shell standard to support such devices, please see this standard. To model a resource with connected commands you should use this standard, and tag the relevant commands with the tag "remove_connectivity" (not "power"). Any endpoint that will be connected (in CloudShell) to one of the sub-resources of the resource will get the connected commands.
Regarding the use case you described - can you clarify what type of "resources" you connect to the shared firewall? and why do you model the shared firewall as admin only?
Thanks,
Alona
Hi Alona,
Thank you for your answer.
About my use case. I'd like to connect resources of type router and switch to the shared firewall. I do not want my users to see that shared firewall or to reserve it.
About Save/Restore sandbox state of this shared resource.
Restoring state of this (entire) resource might affect other sandboxes/resources connected to this shared resource. I guess you left this to the authors of the orchestration scripts to figure out.
About Attributes, User Input
I noticed that many of the attributes listed in the table are allowed for user to change ('User Input' = yes). That might not be the optimal way to work with resource shared across multiple sandboxes (and users).
Thanks,
George
Hi,
Thank you for the clarification of the use case.
Regarding the Save & Restore behavior for this resource - this behavior is custom and will be defined in the setup and teardown script associated with sandbox. Do note that it won't be required to add the shared firewall to the users sandboxes in order to launch its connected commands, so practically the shared firewall can remain an "inventory resource" and booked in sandboxes only by admins for administrative tasks.
The "user input = yes" property means that the attribute's value can be populated by admin or domain-admin on resource creation and editing (in the Inventory), vs. attributes that their values can be populated only by the driver's Autoload command. Attribute which are marked as "user input = yes" won't be editable to end users.
Alona.
Hi Alona,
Thanks for clarifying.
