aboutsummaryrefslogtreecommitdiffstats
path: root/docs/user_guide.rst
blob: 516199a23f750a029ff911d44443ecc0bd15f46f (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
.. Copyright 2017 Huawei Technologies Co., Ltd.

.. _cli_user_guide:

CLI user guide
==============

**One Command to command whole Onap !!**

Provides unified commands to operate any products from Linux console and web command console.
Configure the following environment variables, before using it:

1. **OPEN_CLI_HOST_URL** - Catalog or service URL
2. **OPEN_CLI_HOST_USERNAME** - Service user name
3. **OPEN_CLI_HOST_PASSWORD** - Service user password

To Run a command
-----------------
Type **oclip <command>** from linux console.

To Run in Interactive mode
--------------------------
Type **oclip** from linux/web console.

And use the directive set to set the values for following parameters:

1. **host-url** - Catalog or service URL
2. **host-username** - Service user name
3. **host-password** - Service user password

Set the product version
------------------------
CLI framework is enhanced to handle multiple product versions at same
time. so to choose the product version, set environment variable
**OPEN_CLI_PROUDCT_IN_USE**.

NOTE: In interactive mode, product version can be selected using
typing **use <product-version>**

Run *oclip [-v|--version]* to see the CLI and available product version details

Profiling arguments
-------------------
In interactive mode, user can use profiles for for “set arguments value once and use it ever”.

Please follow the steps given below for setting profiles:

1.    Open the CLI interactive console

2.    Create the profile, say ‘onap-deployment-1’ by running ‘profile onap-deployment-1’
There is no limit in number of profiles. OCLIP will create a profile if not exist already,
otherwise on typing 'profile' on the console, corresponding profiles will be effective.
So you can switch across profiles by using this directive 'profile'.

3.    For example, to add the credentials, Run following steps:

a.    set host-url=<aai-url>

b.    set host-username=AAI

c.    set host-pasword=AAI

d.    Type 'set' to print all these arguments stored so far.

NOTE: Profiles are not limited to set only credentials, you can set any frequently using
common arguments, which are listed in command help.

NOTE: For setting service specific parameters, use in the form of <service-name>:<param-name>=<param-value>.
For example, following setting will be used only for aai service:

a.    set aai:host-url=<aai-url>

b.    set aai:host-username=AAI

c.    set aai:host-pasword=AAI


4.    You can override these stored arguments by providing them as arguments directly while
running the CLI.

5.    Profile information is persisted, so when you disconnect and connect again the CLI console,
you can start use the same profile again.

NOTE: Use the directive 'set' for setting the values for parameters and 'unset' for reseting the values.

In Beijing release, new default profile named as 'onap-beijing' is delivered with all default ONAP service
credentials. so user could use this profile to avoid setting the credentials every time.

Batching support & Parameter file
---------------------------------
For a given scenario where, user wants to run a command with different set of inputs, this feature could be used.

For example, in ONAP, user wants to register multiple clouds at a given time, so user can create a parameter file
as given below and capture inputs for one or more clouds:

parameter file name: /usr/mrkanag/cloud-list.yaml

cloud-1:
  - name: cloud-region-1
  - description: Provides the test cloud environment
cloud-2:
  - name: cloud-region-2
  - description: Provides the production cloud environment

To register all these clouds in ONAP execute the cloud-register command with parameter file in inputs as below:

onap -p  /usr/mrkanag/cloud-list.yaml cloud-register

Now OCLIP will iterate the command cloud-register for every cloud mentioned in the parameter file /usr/mrkanag/cloud-list.yaml.
When user use this approach to execute the command with multiple entries in parameter file is called as *batching*.

Help
----
*oclip [-h|--help]*
*oclip <command> [-h|--help]*

Debug Mode
----------
To run in debug mode, set following environment variables:

1. OPEN_CLI_CLI_DEBUG - By default its false, otherwise Set to true

2. OPEN_CLI_CLI_DEBUG_PORT - By default it is 5005, otherwise set to new TCP port number

More details
-------------
https://wiki.onap.org

Command usage guide
-------------------
Following document provides the help message for commands supported in this release.

.. toctree::
   :maxdepth: 1

   cmd_help.rst
   cmd_help_onap_amsterdam.rst
   cmd_help_onap_beijing.rst

Command Samples
---------------
Following document provides the samples for commands supported in this release.

.. toctree::
   :maxdepth: 1

   cmd_sample.rst
   cmd_sample_onap_amsterdam.rst

End to end service creation tutorial
------------------------------------
Following document provides the tutorial for service creation using CLI.

.. toctree::
   :maxdepth: 1

   user_guide_end_to_end_onap_cli_commands.rst

PNF/VNF on-boarding tutorial
------------------------------------
Following document provides the tutorial for PNF/VNF on-boarding tutorial using CLI.

.. toctree::
   :maxdepth: 1

   user_guide_pnf_on_boarding.rst