1 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
3 .. _clamp-policy-gui-label:
11 1 - How to run the Front-End Gui
12 ================================
13 This section describes how to run the front end on your local machine.
17 **Building and running CLAMP**
20 :ref:`Clamp ACM Smoke Tests <policy-clamp-runtime-smoke-label>`
22 **Step 1:** Go to the clamp directory
26 cd /clamp/extra/bin-for-dev
28 **Step 2:** Inside the clamp directory run
34 **Step 3:** Check docker container id
40 **Step 4:** Log into docker container
44 docker exec -it 'container_id' bash
46 **Step 5:** Go into mariadb shell
52 **Step 6:** Enter password
56 .. image:: images/01-gui.png
58 **Step 7:** Go into cldsdb4 database
64 **Step 8:** Verify if there is data in the following table 'loop_templates'
68 select * from loop_templates;
70 ** If for some reason the database is empty do the go to the '/docker-entrypoint-initdb.d/dump' directory
76 **Step 9:** Once the database is up and running need to start the clamp emulator, by running the following command inside the /clamp/extra/bin-for-dev
82 **Step 10:** Verify if mariadb and the emulator is running
88 .. image:: images/02-gui.png
90 **Step 11:** Start the backend service by running the command inside the /clamp/extra/bin-for-dev
97 .. _building-ui-label:
99 2 - Checking out and building the UI
100 ====================================
102 **Step 1:** Checkout the UI from the repo
106 git clone "https://gerrit.nordix.org/onap/policy/gui"
108 **Step 2:** Change into the "gui" directory and run the following
114 **Step 3:** Go into the gui-clamp/ui-react directory and run the following
120 **Step 4:** Start the front end UI
124 npm start --scripts-prepend-node-path
126 *If you get the following error*
128 .. image:: images/03-gui.png
134 Then change ``"version": "${project.version}",`` to ``"version": "2.1.1",``
136 Save and close, then delete the node_modules directory
150 npm start --scripts-prepend-node-path
152 **Step 5:** Once the UI starts at localhost:3000 it will ask for credentials:
157 3 - How to Commission/Decommission the TOSCA Service Template
158 =============================================================
160 This section describes how to commission and decommission the Tosca Service Template
164 See :ref:`Policy GUI Prerequisites<clamp-policy-gui-label>`
166 **Step 1:** From the Main Menu Click on TOSCA Automation Composition Dropdown
168 .. image:: images/04-gui.png
170 **Step 2:** From the Dropdown Menu Select Upload Automation Composition To Commissioning
172 .. image:: images/05-gui.png
174 **Step 3:** On the window Upload Tosca to Commissioning API Click on the input box that says 'Please Select a file'
176 .. image:: images/06-gui.png
178 **Step 4:** Once the yaml file is selected click on Upload Tosca Service Template
180 .. image:: images/07-gui.png
182 **Step 5:** After the upload there should have a message "Upload Success" in green
184 .. image:: images/08-gui.png
186 **Step 6:** To validate that the TOSCA Service Template has been commissioned click on Manage Commissioned Automation Composition Template
188 .. image:: images/09-gui.png
190 **Step 7:** In the View Tosca Template Window click on Pull Tosca Service Template
192 .. image:: images/10-gui.png
194 **Step 8:** Once the Tosca Service Template has been pulled there should be a json object rendered in the window
196 .. image:: images/11-gui.png
198 **Step 9:** Click on Close close the window
200 **Step 10:** Click on Edit Automation Composition Properties
202 .. image:: images/12-gui.png
204 **Step 11:** In the Change ACM Common Properties change the appropriate properties and click on save and there should have a popup saying 'Changes Saved. Commission When Ready...'
206 .. image:: images/13-gui.png
208 **Step 12:** After saving the changes click on Commission and should have a Green message saying 'Commissioning Success'
210 .. image:: images/14-gui.png
212 **Step 13:** To Decommission the Tosca Service Follow Step 6 and 8
214 **Step 14:** Once the json objected is rendered in the window click on delete
216 .. image:: images/11-gui.png
218 **Step 14:** Once the json objected is rendered in the window click on delete
220 .. image:: images/11-gui.png
222 **Step 15:** If the delete is successful it should show a message "Delete Successful"
224 .. image:: images/15-gui.png
226 4 - How to Save Instance Properties and Change The Order State
227 ==============================================================
229 This section describes how to save the instance properties and change it's order state
233 see building-ui-label_
235 **Step 1:** Go to the participant http directory
239 cd /clamp/participant/participant-impl/participant-impl-http
241 **Step 2:** Run he following command
245 mvn spring-boot:run -Dspring-boot.run.arguments=--server.port=8080
247 **Step 3:** Go to the participant kubernetes directory
251 cd /clamp/participant/participant-impl/participant-impl-kubernetes
253 **Step 4:** Run he following command
257 mvn spring-boot:run -Dspring-boot.run.arguments=--server.port=8081
259 **Step 5:** Go to the participant policy directory
263 cd /clamp/participant/participant-impl/participant-impl-policy
265 **Step 6:** Run he following command
269 mvn spring-boot:run -Dspring-boot.run.arguments=--server.port=8082
271 **Step 7:** From the Main Menu Click on Instantiation Management
273 .. image:: images/16-gui.png
275 **Step 8:** Once the window for Manage Instance is open click on Create Instance
277 .. image:: images/17-gui.png
279 **Step 9:** With the Window Create Instance Properties Insert a Name and change the appropriate properties and click save
281 .. image:: images/18-gui.png
283 **Step 10:** After clicking save it should come with a green message saying "Instantiation Properties Success"
285 .. image:: images/19-gui.png
287 **Step 11:** To delete an instance repeat Step 7
289 .. image:: images/16-gui.png
291 **Step 12:** Once the window for Manage Instance is open click on Delete
293 .. image:: images/20-gui.png
295 * NOTE: The only way to delete the instance properties if the order state has to be UNINITIALISED
297 **Step 13:** To change the state click on Change in Manage Instances Window
299 .. image:: images/20-gui.png
301 **Step 14:** After clicking Change there should have a drop down with specific different ordered states
303 .. image:: images/21-gui.png
305 **Step 15:** From UNINITIALISED the user can only select Passive Ordered State
307 .. image:: images/22-gui.png
309 **Step 16:** Click on Save and a Message in Green "Ordered State Change Success"
311 .. image:: images/23-gui.png
313 * NOTE: Can't change from Passive to Running in a local developer machine, can only change in the production environment