[unfold.git] / portal / templates / slice-tab-experiment.html

<div class="col-md-10 col-md-offset-1">
        {% if ple_resources or iotlab_resources or nitos_resources or nitos_paris_resources%}
                <h2>How to access your reserved resources</h2>
        {% endif %}
        {% if ple_resources %}
        <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">
        {%for resource in ple_resources %}
                <b>Resource</b><br>
                $ ssh {{ple_slicename}}@{{resource}}<br>
        {%endfor%}
        </p>
        <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>
        <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':'onelab.upmc.express'}, 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>
        {% endif %}

        {% if iotlab_resources %}       
        <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>
                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 {{iot_login}}@fit3-dev.inrialpes.fr
        </p>
        {% endif %}
        {% if nitos_resources or nitos_paris_resources %}
        <h3>NITOS</h3>
        
        <p>
         NITOS resources are not directly accessible. You will need to log in on a gateway server and from there access the node.
         You will find the ssh commands to connect to NITOS nodes below:
        </p>

        {% if nitos_resources %}        
        <h4>NITLab</h4>
        <p class="command">
        $ ssh {{slicename}}@nitlab.inf.uth.gr
        </p>
        
        <p>For each of the reserved nodes, follo the steps given below:</p>
        <p class="command">
        {%for resource in nitos_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>
        {% endif %}

        {% 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">
        {%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>
        {%endif%}

        <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
                restart the OMF Resource Controller and finally execute the experiment:
        </p>
        <p class="command">
                $ omf exec --slice {{slicename}} your_exp.rb
        </p>
        <p>
        The complete tutorial is available at the following address:
        <a target="_blank" href="http://nitlab.inf.uth.gr/NITlab/index.php/testbed/instructions/basic-tutorial">NITOS basic tutorial</a>
        </p>
        <p>To learn more about OMF6, please click <a href="http://omf.mytestbed.net/projects/omf6/wiki/Wiki" 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>
        <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>
        <br>
        <p><img src="{{ STATIC_URL }}img/omf-logo.png" width="90"></p>
        <p>OMF is a Testbed Control, Measurement and Management Framework.</p>
        <p>
        OMF was originally developed for the ORBIT wireless testbed at Winlab, Rutgers University. Since 2007, OMF has been actively extended to operate on testbeds with many different type of network and resource technologies. It is now deployed and used on different testbeds in Australia, Europe, and in the U.S. OMF is currently being extended further to support exciting new features and technologies. This website is hosting this ongoing activity. OMF development is now conducted essentially within the TEMPO project at NICTA (Australia) in strong collaboration with Winlab (Rutgers University).
        </p>
        <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>