Remote API Platform Standard (Mobile Center integration use case)

Please answer the following to submit a new shell standard request:

1. How will you name the new shell standard?
* For example, Networking Routers Standard

Remote API Platform

2. What type of devices do you need the standard for?
* Please provide specific devices and vendors you have in mind. For example Cisco 12K Router.

Micro Focus Mobile Center - connected child resources are physical and emulated devices to be managed by the mobile center farm

3. What are the use cases for this shell standard? Please describe your intended flow inside CloudShell for using such a resource.
* For example, I need a switch with L2 connectivity that will be the infrastructure for VLAN connectivity in my sandbox. In the blueprint, I want to define L2 connections between resources and in the Sandbox I want those connections to be activated.

To model the Mobile Center inventory in cloudshell and to connect and modify the devices via connected api commands on the phone device shell

4. How do you see the data model structure?
* For example, I need "Switch" root level, under it, I need a "Module" and "Power Port", under the "Module" I need a "Port". If you have some diagram please attach of the required resource structure please attach to your standard request.

There will be the root which will be the particular mobile center server which wraps up the api commands. There will be no child resources, rather the phones will be indepenedent shells with a "physical" connection to the mobile center resource

4a. Please attach a diagram or sketch of the requested data model structure (optional)

5. Do remote connections (QualiX) should be enabled on the root and/or subs? For example - Yes, only on the root level.

No

6. Which attributes are required on the root level?
* For example, on my "Switch" I need the following attribute - Address, User, Password, Model, Vendor, SNMP Community etc.

- Server Address <string>

- Server Port <string>

- SSL Enabled (https) <boolean>

- Admin User <string>

- Admin Password <string>

7. Which attributes are required on each sub-resource type?
* For example, on my "Module" I need the following attributes - Model, Serial Number etc. On the "Port" I need the following attributes - MAC Address, IP Address, Duplex etc.
No sub resources. All phones will be independent shells.

8. What commands does the shell need to have? for each command, give a description and define input/output if required
* For example, I need my Switch to support - Autoload, L2 Connectivity, Save and Restore Configuration, Shutdown etc.
- reserve_phone(phone)

- unreserve_phone(phone)

- download_app(phone, target_app)

- delete_app(phone, target_app)

9. If you already have some draft of the standard YAML files, templates and/or documentation please attach here (optional)