Update rfw_integration_on_lava.md

content/concepts/rfw_integration_on_lava.md

@@ -129,8 +129,8 @@ and once the test execution is completed the generated report will be sent back
 and send back to server. 
 
 # Impact analysis on Apertis distribution
+![Robot Framework on LAVA workflow](/images/rfw_on_LAVA_work_flow.png)
 ## Infrastructure
-
 Integrating Robot Framework on existing Apertis infrastructure will requires the following changes :
 - Integrating Docker container on worker, so worker setup should improved to meet the Docker requirement.
 - Storage area of worker should be increased to store all type of Robot Framework result.
@@ -152,7 +152,39 @@ Framework testcases to run on SDK and target devices running Fixed Function or H
 tests defined with the new Robot Framework test suites which will help to improve the test coverage.
 
 # Summary
-- Stable version of Robot Framework 4.1.2 and core library of `SSH` and `laxer` are integrated on SDK distribution from V2022dev1 release onwards.
-- Robot Framework on LAVA setup is completed with QEMU emulator and successfully executed the jobs.
-- Evaluation of RFS for Docker container setup on LAVA worker is ongoing
-- Above implementation is planed to host on cloud setup.
+•	End-End workflow 
+- LAVA pipelines can take care of 
+All test stages: power on-off, Flashing & booting image.
+loads tests from GIT, run tests, reporting.
+Parallel scheduling to no. of devices to reduce cycle time,
+- Can be configured to lock/reserve devices for specific tests or specific users. 
+
+•	Internet facing Web Service	 
+- One front end service (hosted by Central team) for all .Multiple teams can hook their DUT setup to the same service.
+
+Internet connected enabling collaboration with external partners.
+	remotely manage the DUTs- Configure, Power On/Off, boot via web service w/o needing access to DUTs
+		Users can login to run tests, view logs, reports (independent of Jenkins CI).  
+		Role based access permissions (Maintainer, Developer, Guest) 
+		Mail notifications/alerts
+
+•	ONE DUT TEST setup for all variants	
+o	One DUT setup can support.
+Linux, Android Tests on device variants and emulator
+All types of tests (with any test f/w) Interface/Functional/System
+Multiple teams can share/reuse the same DUT setups.
+
+•	Continuous testing	
+o	Easily hook LAVA to CI/CD setup for continuous testing
+o	reuse /trigger same LAVA tests in different CI/CD setups
+
+•	Handles inconsistency.	
+o	Configured to retry during initial(download) failures/timeout or test run failures.
+
+•	Inbuilt reporting dashboard
+o	Insight full metrics available in the inbuilt dashboard:
+		Test result report
+		Linkage to Test case definitions.
+		Test run timing statistics.
+o	Extensive Dashboard	
+		LAVA provides interfaces for integration to Project Dashboards