X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=portal%2Ftemplates%2Fslice-tab-experiment.html;h=bfa9cee9f3ca7ef35f07a6c314fbc7c256d771b8;hb=d861dbcfe1188ec46ff2006f812eaf0055b74ea2;hp=b6c7c5c4c2d84a9916da2e406c935fc0e1b73cac;hpb=f7ab045626ced984daefc7467f691f285141bb04;p=unfold.git

diff --git a/portal/templates/slice-tab-experiment.html b/portal/templates/slice-tab-experiment.html
index b6c7c5c4..bfa9cee9 100644
--- a/portal/templates/slice-tab-experiment.html
+++ b/portal/templates/slice-tab-experiment.html
@@ -1,95 +1,217 @@
-<div class="col-md-2">
+<div class="col-md-10 col-md-offset-1">
+<script type="text/javascript">
+    $(document).ready(function() {
+        console.log('{{platforms}}');
+	    {% for platform in platforms %}
+        // /sfa/Describe?hrn=onelab.upmc.projectx.slicex&platform[]={{platform}}&type=slice
+        $.post("/sfa/Describe",{'hrn':'{{slicename}}', 'type':'slice', 'platform':['{{platform}}']}, function( data ) {
+            if('parsed' in data['{{platform}}'] && 'rspec' in data['{{platform}}']['parsed']){
+                rspec = data['{{platform}}']['parsed']['rspec'];
+                if('node' in rspec){
+                    jQuery.each( rspec['node'], function( i, node ) {
+                        render_node('{{platform}}',node);
+                    });
+                }
+            }
+        });
+	    {% endfor %}
+    });
+    
+    function render_node(platform, node){
+        console.log(platform,node);
+        if('@component_manager_id' in node){
+            // urn:publicid:IDN+ple+authority+cm
+            t_urn = node['@component_manager_id'].split('+');
+            //if(t_urn[1].indexOf(":") > -1)
+            testbed = t_urn[1];
+            if(!$('#'+testbed).length){
+                testbed = 'default';
+            }
+        }else{
+            testbed = 'default';
+        }
+        if('services' in node && 'login' in node['services']){
+            console.log(node['services']['login']);
+            login = node['services']['login'];
+            if('@port' in login && login['@port']!='22'){
+                $('#'+testbed).append("<p class='command'>$ ssh "+login['@username']+"@"+login['@hostname']+" -p "+login['@port']+"</p>");
+            }else{
+                $('#'+testbed).append("<p class='command'>$ ssh "+login['@username']+"@"+login['@hostname']+"</p>");
+            }
+	
+        }else if('@component_name' in node){
+            console.log(node['@component_name']);
+        }else{
+            console.log(node);
+        }
+        $("#access").show();
+
+        $('#'+testbed).show();
+        if($('#'+testbed+'_header').length){
+            $('#'+testbed+'_header').show();
+        }
+        if($('#'+testbed+'_footer').length){
+            $('#'+testbed+'_footer').show();
+        }
+    }
+</script>
+<div id="access" style="display:none;">
+    <h2>How to access your reserved resources</h2>
+</div>
+<div id="default">
 </div>
-<div class="col-md-8">
-	<h2>How to access your slice</h2>
+<div id="ple_header" style="display:none;">
 	<h3>PlanetLab Europe</h3>
 	
 	<p>
 		PlanetLab Europe resources are accessible directly via SSH. Your SSH public key is deployed automatically
 		on the reserved nodes. To access your slice on a resource just type the following command:
 	</p>
-	<p class="command">
-		$ ssh {{ple_slicename}}@planetlab-resource.hostname.com
-	</p>
-	<p><strong>NOTE:</strong> Your typical slicename <b>{{slicename}}</b> has been converted to PlanetLab specific format <b>{{ple_slicename}}</b> in order to do SSH.</p>
-	<p>Please note that the first '.' is replaced by number 8 and the rest of the dot/s are replaced by underscore/s.</p>
+</div>
+<div id="ple" style="display:none;">
+</div>
+<div id="ple_footer" style="display:none;">
+	<p><strong>NOTE:</strong> Your original slicename <b>{{slicename}}</b> has been converted to PlanetLab specific format <b>{{ple_slicename}}</b> in order to do SSH.</p>
 	<p>
 		Be aware that after you reserve a PlanetLab Europe resource your slice will be deployed with a delay of about 15 minutes, 
 		after witch you will be able to access the resource.
 	</p>
-	
+    <div id="initscript">
+        <div>
+            <h4>Init Script on PLE</h4>
+            <i>This bash script will be deployed on all PLE nodes of your slice</i>
+        </div>
+        <textarea style="width:100%; height:100px;" id="initscript_code"></textarea><br>
+<!-- TODO !!!
+        <div>
+            <select>
+                <option>All</option>
+                <option>node1</option>
+                <option>node2</option>
+            </select>
+        </div>
+-->
+        <button name="deploy" class="btn btn-success btn-sm" onclick="deploy('{{slicename}}');">Deploy</button>
+        <button name="delete" class="btn btn-danger btn-xs" onclick="del('{{slicename}}');">Delete</button>
+    </div>
+    <script type="text/javascript">
+    $(document).ready(function() {
+        $.post("/initscript/get/",{'slice_hrn':'{{slicename}}'}, function( data ) {
+            console.log(data);
+            jQuery('#initscript_code').val(data['initscript_code']);
+        });
+    });
+    function deploy(slice_hrn){
+        console.log("deploy = "+slice_hrn);
+        var initscript_code = jQuery('#initscript_code').val()
+        $.post("/initscript/update/",{'slice_hrn':slice_hrn, 'initscript_code':initscript_code}, function( data ) {
+            console.log(data);
+            if (data['ret'] == 0) {
+                mysliceAlert('Success: initscript deployed','success', true);
+            }else{
+                mysliceAlert('Rest Error for: '+data.error,'warning', true);
+            }
+            //jQuery('#initscript_code').val(data['initscript_code']);
+        });
+    }
+    function del(slice_hrn){
+        console.log("delete");
+        $.post("/initscript/delete/",{'slice_hrn':slice_hrn}, function( data ) {
+            console.log(data);
+            if (data['ret'] == 0) {
+                mysliceAlert('Success: initscript deleted','success', true);
+                jQuery('#initscript_code').val('');
+            }else{
+                mysliceAlert('Rest Error for: '+data.error,'warning', true);
+            }
+
+        });
+    }
+    </script>
+    <br>
+</div>
+<div id="iotlab_header" style="display:none;">
 	<h3>FIT IoT-Lab</h3>
-	<p>FIT IoT-Lab resources are accessible directly via SSH and <a href="https://devgrenoble.senslab.info/testbed/" target="_blank">web GUI.</a>
+	<p>FIT IoT-Lab resources are accessible directly via SSH and <a href="https://www.iot-lab.info/testbed/" target="_blank">web GUI.</a>
 		To acess IoT-Lab resources using web GUI, use the same login and  password of OneLab portal. To acess Iot-Lab resources using SSH type
 		the following command:
 	</p>
-	<p class="command">
-		ssh {{username}}@fit3-dev.inrialpes.fr
-	</p>
-	
-	<h3>NITOS</h3>
+</div>
+<div id="iotlab" style="display:none;">
+</div>
+<div id="nitos_header" style="display:none;">
+	<h3>NITOS Volos (Greece)</h3>
 	
 	<p>
 	 NITOS resources are not directly accessible. You will need to log in on a gateway server and from there access the node.
-	 The NITOS server address is nitlab.inf.uth.gr, so to connect to the NITOS server:
-	</p>
-	<p class="command">
-	$ ssh {{slicename}}@nitlab.inf.uth.gr
-	</p>
-	
-	<p>
-	<!-- In order to connect to NITOS server he has to upload his public key on the server. 
-	For now we do it this way: http://nitlab.inf.uth.gr/NITlab/index.php/your-ssh-keys. 
-	I think this is a procedure that needs to be done at the registration phase of the user, 
-	through myslice, Broker etc. but I will answer you in a couple of days for sure. -->
+	 You will find the ssh commands to connect to NITOS nodes below:
 	</p>
-
-	<p>
-		You will then need to prepare the resource by loading an OMF image on it:
-	</p>
-	
+	<h4>NITLab</h4>
 	<p class="command">
-		$ omf load -i baseline_grid.ndz -t omf.nitos.node016
-	</p>
-
-	<p>
-		Turn on the node:
-	</p>
-	
+	    $ ssh {{slicename}}@nitlab.inf.uth.gr #nodes 001-040<br>
+        $ ssh {{slicename}}@nitlab2.inf.uth.gr #nodes 041-049<br>
+        $ ssh {{slicename}}@nitlab3.inf.uth.gr #nodes > 049
+    </p>
+</div>
+<div id="nitos" style="display:none;">
+	<p>Loading an OMF-compatible image on your resource:</p>
 	<p class="command">
-		$ omf tell -a on -t omf.nitos.node016
-	</p>
-	<p>
-		And finally ssh on the node:
+		<b>Resource</b><br>
+        $ omf6 stat -t {{resource}} #check the status of the node<br>
+        $ omf6 tell -a on -t {{resource}}  #turn on/off the node <br>
+    	$ omf6 load -i baseline.ndz -t {{resource}}  #for orbit-like node (002-009) use "baseline_orbit.ndz"<br>
 	</p>
+</div>
+<div id="nitos_footer" style="display:none;">
+    <p><b>NOTE:</b> Nodes 002-009 are orbit-like nodes. For these nodes use "baseline_orbit.ndz". All these images come with OMF5.4 resource controller. To do OMF6 experiments use "baseline_omf6_1_1.ndz" and  "baseline_orbit_omf6_1_1.ndz" for grid nodes and orbit nodes respectively. </p>
+</div>
+	{% if nitos_paris_resources %}
+	<h4>FIT NITOS-Lab Paris</h4>
+	 <p class="command">
+ 		$ ssh {{slicename}}@griffin.ipv6.lip6.fr
+	 </p>
+	<p>For each of the reserved nodes, follo the steps given below:</p>
 	<p class="command">
-		$ ssh root@node016
+	{%for resource in nitos_paris_resources %}
+		<b>Resource</b><br>
+    	$ omf load -i baseline_grid.ndz -t {{resource}}  #loading OMF image on the node<br>
+    	$ omf tell -a on -t {{resource}}  #turn on the node <br>
+    	$ ssh root@{{resource}}  #ssh to the node<br><br>
+	{%endfor%}
 	</p>
+
 	<p>
-		On the node itself you will have to modify the file /etc/omf-resctl-5.3/omf-resctl.yaml according to your slice settings and then
+		On the node itself you will have to modify the file /etc/omf-resctl-5.3/omf-resctl.yaml (OMF5.4 only) according to your slice settings and then
 		restart the OMF Resource Controller and finally execute the experiment:
 	</p>
 	<p class="command">
-		$ omf exec --slice slice_name your_exp.rb
+		$ omf exec --slice {{slicename}} your_exp.rb
 	</p>
 	<p>
-	The complete tutorial is available at the following address:
+	The complete tutorial on NITOS nodes:
 	<a target="_blank" href="http://nitlab.inf.uth.gr/NITlab/index.php/testbed/instructions/basic-tutorial">NITOS basic tutorial</a>
 	</p>
-	
-	<br />
+    <p>OMF based experiments' tutorials are available <a href="http://nitlab.inf.uth.gr/NITlab/index.php/testbed/instructions/omf-tutorials-scenarios" target="_blank">here.</a></p> 
+	<p>To learn more about OMF, please click <a href="http://omf.mytestbed.net/projects/omf/wiki/OMF_Main_Page" target="_blank">here.</a></p>
+
+	{% endif %}
 	
 	<h2>Available Tools</h2>
 	<p><img src="{{ STATIC_URL }}img/terminal_icon.png" width="50"> <b>SSH</b></p>
 	<p>
 	Secure Shell (SSH) is a cryptographic network protocol for secure data communication, remote command-line login, remote command execution, and other secure network services between two networked computers that connects, via a secure channel over an insecure network, a server and a client (running SSH server and SSH client programs, respectively). The protocol specification distinguishes between two major versions that are referred to as SSH-1 and SSH-2.
 	</p>
-	<p> More Info: <a href="http://en.wikipedia.org/wiki/Secure_Shell" target="_blank">http://en.wikipedia.org/wiki/Secure_Shell</a></p>
+	<p> More info: <a href="http://en.wikipedia.org/wiki/Secure_Shell" target="_blank">http://en.wikipedia.org/wiki/Secure_Shell</a></p>
 	<br>
+	<p><img src="{{ STATIC_URL }}img/putty-logo.png" width="50"> <b>PuTTY</b></p>
+	<p>
+		PuTTY is an SSH and telnet client, developed originally by Simon Tatham for the Windows platform. PuTTY is open source software that is available with source code and is developed and supported by a group of volunteers.
+	</p>
+	<p>More info: <a href="http://www.putty.org/" target="_blank">http://www.putty.org/</a></p>	
 	<br>
 	<p><img src="{{ STATIC_URL }}img/nepi_logo.png" width="90"></p>
 	<p>NEPI, the Network Experimentation Programming Interface, is a life-cycle management tool for network experiments. The idea behind NEPI is to provide a single tool to design, deploy, and control network experiments, and gather the experiment results. Going further, NEPI was specially conceived to function with arbitrary experimentation platforms, so researchers could use a single tool to work with network simulators, emulators, or physical testbeds, or even a mixture of them. To accomplish this, NEPI provides a high-level interface to describe experiments that is independent from any experimentation platform, but is able to capture platform specific configurations. Experiment definitions can be stored in XML format to be later reproduced, and modified according to experimentation needs. Experiment execution is orchestrated by a global experiment controller, that is platform independent, and different platform-dependent testbed controllers, creating a control hierarchy that is able t adapt to platform specific requirements while providing an integrated control scheme.</p>
-	<p> More Info: <a href="http://nepi.inria.fr" target="_blank">http://nepi.inria.fr</a></p>
+	<p> More info: <a href="http://nepi.inria.fr" target="_blank">http://nepi.inria.fr</a></p>
 	<br>
 	<p><img src="{{ STATIC_URL }}img/omf-logo.png" width="90"></p>
 	<p>OMF is a Testbed Control, Measurement and Management Framework.</p>
@@ -99,5 +221,3 @@
 	<p>In addition to the main OMF software, this site also hosts OMF sub-projects addressing various related aspects of a testbed's control, measurement, and management.</p>
 	<p>More Info: <a href="http://mytestbed.net/projects/omf" target="_blank">http://mytestbed.net/projects/omf</a></p>
 </div>
-<div class="col-md-2">
-</div>