Clean tabs and trailing blanks

Signed-off-by: guillaume.lambert <guillaume.lambert@orange.com> Change-Id: I82c3a2c26f02d9314fce8fa3f5b49c4a65ec8f75 (cherry picked from commit 7677c43)
opnfv · Mar 20, 2023 · a14593c · a14593c
1 parent 98889ad
commit a14593c
Show file tree

Hide file tree

Showing 15 changed files with 534 additions and 534 deletions.
diff --git a/commons/traffic-profile-guidelines.rst b/commons/traffic-profile-guidelines.rst
@@ -11,11 +11,11 @@ Introduction
 ------------
 
 In order to have consistent testing profiles, it has been suggested to define and store traffic profiles.
-These profiles shall be based on operator representative scenario. 
+These profiles shall be based on operator representative scenario.
 
-These reference profiles may be used by any test projects, unitary, functional or performance tests. 
-It is possible to adapt them to specific testcases. 
-It is recommended to use them in order to avoid getting as many profiles as tests. 
+These reference profiles may be used by any test projects, unitary, functional or performance tests.
+It is possible to adapt them to specific testcases.
+It is recommended to use them in order to avoid getting as many profiles as tests.
 It should be helpful to compare the results of test scenario.
 
 .. _howto:

diff --git a/docs/com/css/theme/OPNFV-Berlin.css b/docs/com/css/theme/OPNFV-Berlin.css
@@ -31,13 +31,13 @@ body {
   bottom: 1em;
   left: 1em;
   font-size: 0.5em;
-  
+
 	}
 
 .reveal .slides > section, .reveal .slides > section > section {
   line-height: 1.3;
   font-weight: inherit; }
- 
+
 .reveal .opnfv-title {
   background-image: url("../../img/title-bg-berlin.png" no-repeat);
 }
@@ -87,7 +87,7 @@ body {
 
 .reveal h1 {
   text-shadow: none; }
-  
+
 
 /*********************************************
  * OTHER

diff --git a/docs/com/css/theme/OPNFV.css b/docs/com/css/theme/OPNFV.css
@@ -30,13 +30,13 @@ body {
   bottom: 1em;
   left: 1em;
   font-size: 0.5em;
-  
+
 	}
 
 .reveal .slides > section, .reveal .slides > section > section {
   line-height: 1.3;
   font-weight: inherit; }
- 
+
 .reveal .opnfv-title {
   background-image: url("../../img/title-bg.png" no-repeat);
 }
@@ -83,7 +83,7 @@ body {
 
 .reveal h1 {
   text-shadow: none; }
-  
+
 
 /*********************************************
  * OTHER

diff --git a/docs/com/pres/Summit/Berlin-2016/conversation.html b/docs/com/pres/Summit/Berlin-2016/conversation.html
@@ -215,7 +215,7 @@ <h3>The test projects</h3>
 
 			</div>
             <div class='footer'>
-				 <img src="../../../img/logo-OPNFV-Berlin.png" alt="OPNFV logo"> 
+				 <img src="../../../img/logo-OPNFV-Berlin.png" alt="OPNFV logo">
 	        </div>
 		</div>
 

diff --git a/docs/com/pres/Summit/Berlin-2016/summit-Berlin.html b/docs/com/pres/Summit/Berlin-2016/summit-Berlin.html
@@ -81,7 +81,7 @@ <h5>OPNFV Design Summit, 20/6/2016, Berlin</h5>
 					</section>
 					<section data-markdown>
 						## so concretely...
-						* Validate scenarios for the release	
+						* Validate scenarios for the release
 						* Give confidence on OPNFV fresh releases
 						* Ensure consistancy towards installers
 						* Ensure End to End interoperability
@@ -135,7 +135,7 @@ <h5>OPNFV Design Summit, 20/6/2016, Berlin</h5>
 						* 2 installers: Foreman/Fuel
 						* Lots of manual operations (reporting, documentation)
 					</section>
-                </section>				
+                </section>
 				<section>
                     <section data-markdown>
 						# Brahmaputra
@@ -146,8 +146,8 @@ <h5>OPNFV Design Summit, 20/6/2016, Berlin</h5>
 						* 3 feature projects: doctor, promise, sdnvpn
 						* 13 Scenarios
 						* 4 Installers (Apex, Compass, Fuel, Joid)
-						* Test result collection 
-						* Automatic dashboard 
+						* Test result collection
+						* Automatic dashboard
 					</section>
 				<section>
 					<h3>Jiras</h3>
@@ -196,23 +196,23 @@ <h3>Brahmaputra Scenario matrix</h3>
 							</tr>
 						</tbody>
 					</table>
-                   * difference of duration due to POD and test suites 
+                   * difference of duration due to POD and test suites
 				</section>
 
 				<section data-markdown>
 					## Lessons learned
 					* Tempest/Rally
 					  * harmonizing installer related OpenStack configuration differences
 					  * creating customized test lists
-					  * main challenge was resolving SDN controller interworking problems 
+					  * main challenge was resolving SDN controller interworking problems
 					* vIMS
 					  * complete but complex test case
 					  * very interesting to automate (pre MANO, most of Telco needs met there)
 				</section>
 
 				</section>
 
-				<section>				
+				<section>
 					<section data-markdown>
 						# Colorado
 					</section>
@@ -221,7 +221,7 @@ <h3>Brahmaputra Scenario matrix</h3>
 						## What's new?
 						* New internal test cases: healthcheck, security
 						* New controler: OpenContrail?
-						* New feature projects (domino, multisites, movie, parser, moon, copper, models, onos-sfc...)						
+						* New feature projects (domino, multisites, movie, parser, moon, copper, models, onos-sfc...)
 						* ARM Support (congratulations to ENEA team!)
 						* Simplified feature project integration journey
 					</section>
@@ -255,19 +255,19 @@ <h3>Automatic reporting</h3>
 						* New VNFs (vEPC, vCDN, vWhatever...)
 						* Multi sites (e.g bgpvpn with different back ends)
 						* Better test coverage
-					</section>					
+					</section>
 					<section data-markdown>
 						## A Functional testing As a Service framework
 						* Scenario owner can select their relevant test cases
 						* Test duration estimation
 						* Agile dashboarding
 						* Analytics
-					</section>	
+					</section>
                     <section data-markdown>
 						## Upstream
 						* Rally: time to give back more
-						* Functest description for ETSI?   
-					</section>					
+						* Functest description for ETSI?
+					</section>
                 </section>
 
 				<section>

diff --git a/docs/com/pres/Summit/Berlin-2016/testapi.html b/docs/com/pres/Summit/Berlin-2016/testapi.html
@@ -69,7 +69,7 @@ <h5>OPNFV Design Summit, 20/6/2016, Berlin</h5>
 						* Test cases
 						* Results
 					</section>
-	
+
 					<section data-markdown>
 						## Status Currently
 						* From many projects
@@ -87,7 +87,7 @@ <h5>OPNFV Design Summit, 20/6/2016, Berlin</h5>
 						</aside>
 						</script>
 					</section>
-	
+
 					<section data-markdown>
 						## Help building
 						* Dashboards
@@ -135,8 +135,8 @@ <h2>Colorado refactoring</h2>
 						<li>Scripts to support databse backup/restore/update</li>
 						<li>Support installation</li>
                         <aside class='notes'>
-							So you can discover and understand the capabilities of the service without 
-                            access to source code, documentation, or through network traffic inspection, 
+							So you can discover and understand the capabilities of the service without
+                            access to source code, documentation, or through network traffic inspection,
                             and also you can interact with the TestAPI directly through swagger website.
                         </aside>
                         </ul>
@@ -148,12 +148,12 @@ <h2>Colorado refactoring</h2>
 					<section data-markdown>
 						# API Evoluation
 					</section>
-					
+
 					<section>
 						<h2> URI changes...</h2>
-						<div style="text-align:left""> 
+						<div style="text-align:left"">
 							<p> testresults.opnfv.org/<span style="color:lightblue">TestAPI</span> => <br>testresults.opnfv.org/<span style="color:yellow">test/api/v1</span> </p>
-			
+
 							<p> /test/api/v1/<b>pods</b></p>
 							<p> /test/api/v1/<b>projects</b></p>
 							<p> /test/api/v1/projects/qtip/<b>cases</b></p>
@@ -200,7 +200,7 @@ <h2> URI changes...</h2>
 					<section>
 						<h2>unit tests</h2>
 						<pre><code class="hljs" data-trim contenteditable>
-umry8364@umry8364-Latitude-E6400:~/Dev/OPNFV/releng/utils/test/result_collection_api$ ./run_test.sh 
+umry8364@umry8364-Latitude-E6400:~/Dev/OPNFV/releng/utils/test/result_collection_api$ ./run_test.sh
 Tests running...
 WARNING:tornado.general:404 GET /dashboard/v1/results?case=vPing&pod=zte-pod1&version=C&installer=fuel&period=5 (127.0.0.1): Project name missing
 WARNING:tornado.access:404 GET /dashboard/v1/results?case=vPing&pod=zte-pod1&version=C&installer=fuel&period=5 (127.0.0.1) 2.30ms

diff --git a/docs/com/pres/gambia/gambia.md b/docs/com/pres/gambia/gambia.md
@@ -85,7 +85,7 @@ the classical ONAP testing virtual machine (**> 1GB**).
   - all ONAP Robot Framework files retrieved from the original repositories
   - testcases.yaml describing the testcases
 
-[Orange-OpenSource/xtesting-onap-robot](https://github.com/Orange-OpenSource/xtesting-onap-robot/)  
+[Orange-OpenSource/xtesting-onap-robot](https://github.com/Orange-OpenSource/xtesting-onap-robot/)
 
 
 ###  What's new in Xtesting?