Hi ONAP CLI team,

We are considering ONAP CLI for a new 5G RAN project potentially. Could you 
please let us know these capabilities of ONAP CLI?

* Support *User-specific settings*

There are a number of cli configuration parameters (called user variables) 
which can be set either permanently or on a session basis.  These settings have 
a default value which is defined in the file *xxx*. If one or more user 
variables need to be changed from the default value, It is also possible to 
define user variables on a session basis by using the command.

I suppose this should be possible:

- Session basis: use set/unset command

- Permanent: use profile command (i.e. profiling arguments)

* Support Scripting:

Support Python/ TCL/Perl scripts, save the result into a plain text file.

Sample content of scripts to retrieve the meters of given services:

* Get the name list of service running in a node
* Get the meters (xxx) from a given service included in the name list.
* If meters exist, save the meters in a local file named as meters.
* If meters does NOT exist, save the “Meters does NOT exist” in the command 
line log file.
* Support interactive mode to get the input from end-user, such as value of a 
parameters, Y/N selection. For example:

Enter the name of the new server definition:

Enter the administrator login ID: (admin)

Enter the administrator password:

Save the admin password for this server? (Y/n)

Enter the context root of the administration services: (admin)

Enter the connection timeout in seconds: (30)

Make this server the default? (Y/n)

· Defaults are displayed in parenthesis. Press the *Enter* key to select the 
default.

Questions that require a yes or no answer display (Y/n) or (y/N). The character 
in uppercase is the default. Press the *Enter* key to select the default, or y 
(for yes) or n (for no) followed by the *Enter* key. For example, if you press 
*Enter* after the last prompt in the example, the server profile that you are 
defining becomes the default server profile.

* Read config info into a XML config file.
* Output result/response of command to a XML file
* Pass a image file to micro service in a sequence.
* Get a file from micro service
* Wrap the existing K8S kubectl command into customer commands developed in the 
plugins.

# Get commands with basic output

kubectl get services # List all services in the namespace

kubectl set image deployment/frontend www = image:v2               # Rolling 
update "www" containers of "frontend" deployment, updating the image kubectl 
logs my-pod                                 # dump pod logs (stdout) kubectl 
logs -l name = myLabel                        # dump pod logs, with label 
name=myLabel (stdout) https://kubernetes.io/docs/reference/kubectl/cheatsheet/

Thanks in advance!

Best Regards,

Khoa


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22521): https://lists.onap.org/g/onap-discuss/message/22521
Mute This Topic: https://lists.onap.org/mt/78455311/21656
Mute #cli:https://lists.onap.org/g/onap-discuss/mutehashtag/cli
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-


Reply via email to