1 ===================================
2 ONAP MultiCloud Administrator Guide
3 ===================================
5 The guide for MultiCloud Administrator.
11 Multicloud doesn’t have any configuration file for now.
19 After Multicloud is up and running, administrator can check Multicloud
20 services from MSB. Go to MSB UI page, administrator should see several icons
21 with name that starts with multicloud.
23 .. image:: ./images/msb-icons.png
24 :alt: Multicloud icons in MSB
29 The icon named Multicloud is the main framework of Multicloud services. And
30 other icons are the plugin for corresponding backend cloud. For example,
31 multilcloud-vio is the plugin for VMware Integrated OpenStack.
33 Administrator can manage Multicloud from MSB UI page. By clicking the icon
34 named multicloud, there will be available api URL in the bottom of MSB UI
35 page. After filling required fields, and clicking `Try it out!`, administrator
36 can perform GET/POST/PUT/DELETE over Multicloud.
41 Besides the MSB UI page, Administrator could manage Multicloud from command
42 line interface(CLI). Multicloud’s CLI is the same as OpenStack’s CLI, and
43 therefore, administrator can use OpenStack Client to manage Multicloud.
44 To make OpenStack Client work with Multicloud, administrator needs to set the
45 environment variables of operation system. An example of environment variables
50 OS_AUTH_URL=http://<msb-ip>:80/api/multicloud/v0/<vim_info>/identity/v3
51 OS_PROJECT_ID=<project id in backend OpenStack>
52 OS_PROJECT_NAME=<project name in backend OpenStack>
53 OS_USER_DOMAIN_NAME=<domain name in backend OpenStack>
54 OS_USERNAME=<administrator username in backend OpenStack>
55 OS_PASSWORD=<password of administrator in backend OpenStack>
56 OS_REGION_NAME=<region name in backend OpenStack>
58 OS_IDENTITY_API_VERSION=3
60 <msb-ip> in OS_AUTH_URL is the IP address of MSB. <vim-info> is composed of
61 cloud_type and cloud_region_id. These two attributes are information of cloud
62 from A&AI. Other environment variables listed above are some information from
63 Multicloud’s backend OpenStack.
64 After exporting above variables into operation system, administrator can use
65 OpenStack Client to mange Multicloud. For example:
71 will list the virtual machine in Multicloud’s backend OpenStack.
74 Logging And Diagnostics
75 =======================
81 The logging file named "runtime_multivimbroker.log" located at /opt/multivimbroker/logs/ directory
82 would record INFO, WARN, ERROR and DEBUG level of information.
83 The format string of logging is "%(asctime)s-%(funcName)s-%(filename)s-%(lineno)d-%(levelno)s-%(content string)s".
84 If there are any issus happened in framework service, you are able to check ERROR level logging to
86 The content of this file list as below:
90 2017-11-03 07:03:31,646:[multivimbroker.pub.utils.restcall]:[restcall.py]-[63][DEBUG]:request=http://192.168.10.45:80/api/multicloud/v0/vmware_vio/identity/v2.0)
91 2017-11-03 07:08:38,020:[multivimbroker.pub.utils.restcall]:[restcall.py]-[63][DEBUG]:request=https://192.168.10.26:8443/aai/v11/cloud-infrastructure/cloud-regions/cloud-region/vmware/vio)
92 2017-11-03 07:08:38,103:[multivimbroker.pub.utils.restcall]:[restcall.py]-[63][DEBUG]:request=http://192.168.10.45:80/api/multicloud/v0/vmware_vio/identity/v2.0)
95 The stdout of framework service named "nohup.out" located at /opt/multivimbroker/ record each http request.
96 The content of this file looks like as below:
100 [25/Oct/2017 00:09:27] "POST /api/multicloud/v0/vmware_vio/identity/v2.0/tokens HTTP/1.0" 500 273
101 [25/Oct/2017 14:17:27] "POST /api/multicloud/v0/vmware_fake/identity/v2.0/tokens HTTP/1.0" 200 5389
102 [26/Oct/2017 23:44:13] "POST /api/multicloud/v0/vmware_vio/identity/v3/auth/tokens HTTP/1.0" 200 6213
105 Each line compose with http method, url and response code, so you are able to check the response status of