--- /dev/null
+<p class="help-block">If your organization does not deploy a Fed4FIRE authority itself, you can use the<br> default one called "fed4fire.global".
+</p>
+
{% endif %}
</select>
</p>
- <p class="help-block">If your organization does not deploy a Fed4FIRE authority itself, you can use the<br> default one called "fed4fire.global".
- If your organization however does provide a<br> Fed4FIRE authority itself, please make sure to select it here. If you start typing<br> your organization's
- name, it will pop up.
+ {% include theme|add:"_authority_notListed.html" %}
</p>
</div>
</div>
</p>
</div>
</div>
+{% include theme|add:"_register_info.html" %}
<div class="row">
<div class="col-md-12">
<div id="register">
<h4 class="modal-title" id="myModalLabel">Terms & Conditions</h4>
</div>
<div class="modal-body">
- <p align="left">
-<div style="text-align: left;" class="mk-text-block "><h4>Fed4FIRE Umbrella Terms and Conditions</h4>
-<h4><span style="color: #f97352;">Purpose of this document</span></h4>
-<p>These Terms and Conditions are provided to inform the user (hereinafter ‘You’) about what constitutes acceptable and permitted use of testbed resources and tools (hereinafter ‘the Platform’) in the Fed4FIRE federation (hereinafter ‘Fed4FIRE’).</p>
-<p>The regulations are not intended to constrain You unnecessarily, but to make You aware and protect You, along with all the participating institutions, from the consequences of any misuse or illegal activity as far as is reasonable.</p>
-<p>It is important to understand that when You use the Platform You are bound by these global Fed4FIRE terms and conditions (as provided online at <a href="http://www.fed4fire.eu/terms">http://www.fed4fire.eu/terms</a>), and also by the ICT regulations of Your own institution and the Acceptable Use Policy of the network providers connecting You to the testbed and interconnecting the resources You use. Thus You must have read and understood these before using Platform resources.</p>
-<p>This policy may be updated as necessary. The current version in force will be available at <a href="http://www.fed4fire.eu/terms">http://www.fed4fire.eu/terms</a>.</p>
-<h4><span style="color: #f97352;">Context</span></h4>
-<p>Fed4FIRE provides an experimental platform for testing new ideas and technologies in the area of computer networking (<a href="http://www.fed4fire.eu">http://www.fed4fire.eu</a>). The federated facility consists of individual testbeds and tools, with different owners. The Fed4FIRE consortium is coordinated by iMinds.</p>
-<p>Fed4FIRE provides You with basic access (through a single account, common tools, support and documentation) to the Platform, while each individual testbed provider determines the specifics of this access in terms of available resources, access policies, etc.</p>
-<h4><span style="color: #f97352;">Scope</span></h4>
-<p>These Terms and Conditions apply to every user of the Platform.</p>
-<p>The Terms and Conditions apply to the use of all equipment connected to the Platform. This includes servers, network(s), and Your workstations (whether owned by You, a company or an institution) and any other equipment or facilities connected to the Platform.</p>
-<p>These Terms and Conditions apply to all use of the Platform.</p>
-<p>These Terms and Conditions apply to third parties using the Platform through services You have made available through the Platform as part of an experiment. You will have to inform these third parties of the Terms and Conditions.</p>
-<h4><span style="color: #f97352;">Limitation of Liability</span></h4>
-<p>No liability is assumed by service providers involved on the Platform or any member of the Fed4FIRE consortium in regards to interruption, corruption, loss or disclosure of the services, tools, processes and data hosted<strong>, </strong>unless it is explicitly mentioned otherwise.</p>
-<h4><span style="color: #f97352;">Service Provision</span></h4>
-<p>You are granted Resources within the Fed4FIRE testbed so that You can use the Platform for the purposes described in the experiment projects You are taking part in. These resources can not be used for any other purposes.</p>
-<p>Platform resource providers aim to provide a stable, high-quality service. If there is evidence that the actions of users are adversely impacting this, resource providers are empowered to take reasonable measures to terminate or reprioritise usage in order to protect the overall operation of their services. Implicated users will be contacted by testbed providers as early as is reasonable.</p>
-<h4><span style="color: #f97352;">Acceptable Usage Policy</span></h4>
-<p>You are granted an account solely for Your own and personal use. You should take appropriate measure to protect Your credentials and prevent their use by third parties. The information You provide when requesting an account should be correct to the best of Your knowledge. You shall be responsible for all loss or damages to any part of the Platform as a result of any use of Your credentials to access the Platform, whether they are authorised or unauthorised by You.</p>
-<p>You shall be liable for actions performed on the Platform, by You, at your request or at the request of any other user invited or permitted by You to use services running on Fed4FIRE. In case of any loss or damage to the Platform originating from Your account, You are responsible for repairing or compensating for all damages to the Platform. In addition, You must respect the regulations of the various testbed resources You use in Your work, as described at <a href="http://www.fed4fire.eu/terms">http://www.fed4fire.eu/terms</a>. Your need to do this arises from co-operative agreements that have been made between all the organisations participating in the Platform.</p>
-<p>You may not interfere with others’ work or attempt to invade their privacy.</p>
-<p>You may not attempt to disrupt the working of the Platform.</p>
-<p>You must respect all Copyright for any software and data used on the Platform.</p>
-<p>The terms of software and data licences must be respected.</p>
-<p>You are not entitled to move proprietary data to, from, or via Platform systems without the prior agreement of its owner.</p>
-<p>Once You have registered to use the Platform, it is Your responsibility to remain aware of these regulations and of any changes made to them, and your continued use of the Platform means that you shall abide by the latest version of these terms and conditions.</p>
-<p>In order to keep the Platform operating correctly in both the technical and legal senses, it may become necessary to investigate network traffic (including, for example, e-mails) as well as examine information held on systems that are, or have been, connected to the Platform. You are deemed to have agreed to this.</p>
-<p>You must ensure that all known or obvious threats and vulnerabilities of the systems You run are adequately addressed.</p>
-<p>Should Your usage imply giving access to the Platform to third parties, You understand You will need to gather explicit consent from the operators of the individual testbed providers You will use, and You agree to enforce any restrictions imposed by an individual testbed provider and accept to fulfil Your legal obligations regarding data protection and retention laws.</p>
-<p>The following are explicitly forbidden on the Platform:</p>
-<ul>
-<li>Any military usage, including the development and production of weapons of mass destruction.</li>
-<li>Any activity resulting in compromising the security or integrity of any sites or networks connected to the Fed4FIRE facility</li>
-<li>Distribution of documents or materials containing insults or defamation, racial hatred or revisionism, terrorism, advertising, or distribution of material in a way that infringes the copyright of another person.</li>
-<li>Any illegal activity.</li>
-</ul>
-<p>You must comply to any additional national regulations from the government of the operators of the local testbeds.</p>
-<h4><span style="color: #f97352;">Enforcement</span></h4>
-<p>Whenever You use the Platform, You are bound by all the regulations in the current form of these terms and conditions and the legislation in force at the time.</p>
-<p>The regulations and legislation which applies to You will be enforced by iMinds, as leader of the Fed4FIRE consortium, or/and by the affected testbed providers, even if a breach of either has been evidenced from elsewhere.</p>
-<p>Note that for breaches of some legislation, the law enforcement can be involved.</p>
-<p>Ignorance of regulations or legislation is not a defence.</p>
-<p>Penalties, as defined in the individual testbed regulations at <a href="http://www.fed4fire.eu/terms">http://www.fed4fire.eu/terms</a>, will be levied for confirmed breaches of regulations.</p>
-<p>Disciplinary and investigative processes may also involve any Fed4FIRE partners, users and testbed providers involved in or affected by Your actions.</p>
-<p>Note that all testbed providers have agreed to co-operate in investigating disciplinary cases.</p>
-<p>You agree that the testbed and network providers in Fed4FIRE may monitor the systems and traffic for vulnerabilities and conformance to the acceptable uses, and You will collaborate with Fed4FIRE and any third party involved should any violations or breaches be noticed. The testbed providers involved may suspend or stop systems or suspend network connectivity without notice if such violations are found or suspected. To fulfil legal and contractual requirements, they may communicate to authorized third parties the owner and user of any resource provisioned and connected to the internet.</p>
-<h4><span style="color: #f97352;">Non-research use of Platform resources</span></h4>
-<p>The Fed4FIRE federation Platform has been constructed for experiment-driven research activities, where experiment-driven research is defined as any activity that furthers the user’s knowledge and/or understanding of algorithms, complex data structures or user behaviour.</p>
-<p>If You wish to use the Platform for any other purpose this must be authorized in advance by the Fed4FIRE testbed providers You will use. You will be expected to provide detailed information in support of Your request.</p>
-<p>Experiments must obtain prior agreement from the providers of all resources (e.g. computers, software, data, networks, and any other facilities) before these are used for any purposes other than experiment-driven research activities.</p>
-<p>The use of Fed4FIRE to host commercial services is explicitly disallowed.</p>
-<p>Experimenters that wish to use additional resources also have to agree with the policies of the testbed providers that offer the requested resources (when applicable). The individual testbed policies can be found here:</p>
-<p><a href="http://www.fed4fire.eu/terms/" target="_blank">fed4fire testbeds</a></p>
-<div class="clearboth"></div></div>
- </p>
</div>
<div class="modal-footer">
--- /dev/null
+<p align="left">
+<div style="text-align: left;" class="mk-text-block "><h4>Fed4FIRE Umbrella Terms and Conditions</h4>
+<h4><span style="color: #f97352;">Purpose of this document</span></h4>
+<p>These Terms and Conditions are provided to inform the user (hereinafter ‘You’) about what constitutes acceptable and permitted use of testbed resources and tools (hereinafter ‘the Platform’) in the Fed4FIRE federation (hereinafter ‘Fed4FIRE’).</p>
+<p>The regulations are not intended to constrain You unnecessarily, but to make You aware and protect You, along with all the participating institutions, from the consequences of any misuse or illegal activity as far as is reasonable.</p>
+<p>It is important to understand that when You use the Platform You are bound by these global Fed4FIRE terms and conditions (as provided online at <a href="http://www.fed4fire.eu/terms">http://www.fed4fire.eu/terms</a>), and also by the ICT regulations of Your own institution and the Acceptable Use Policy of the network providers connecting You to the testbed and interconnecting the resources You use. Thus You must have read and understood these before using Platform resources.</p>
+<p>This policy may be updated as necessary. The current version in force will be available at <a href="http://www.fed4fire.eu/terms">http://www.fed4fire.eu/terms</a>.</p>
+<h4><span style="color: #f97352;">Context</span></h4>
+<p>Fed4FIRE provides an experimental platform for testing new ideas and technologies in the area of computer networking (<a href="http://www.fed4fire.eu">http://www.fed4fire.eu</a>). The federated facility consists of individual testbeds and tools, with different owners. The Fed4FIRE consortium is coordinated by iMinds.</p>
+<p>Fed4FIRE provides You with basic access (through a single account, common tools, support and documentation) to the Platform, while each individual testbed provider determines the specifics of this access in terms of available resources, access policies, etc.</p>
+<h4><span style="color: #f97352;">Scope</span></h4>
+<p>These Terms and Conditions apply to every user of the Platform.</p>
+<p>The Terms and Conditions apply to the use of all equipment connected to the Platform. This includes servers, network(s), and Your workstations (whether owned by You, a company or an institution) and any other equipment or facilities connected to the Platform.</p>
+<p>These Terms and Conditions apply to all use of the Platform.</p>
+<p>These Terms and Conditions apply to third parties using the Platform through services You have made available through the Platform as part of an experiment. You will have to inform these third parties of the Terms and Conditions.</p>
+<h4><span style="color: #f97352;">Limitation of Liability</span></h4>
+<p>No liability is assumed by service providers involved on the Platform or any member of the Fed4FIRE consortium in regards to interruption, corruption, loss or disclosure of the services, tools, processes and data hosted<strong>, </strong>unless it is explicitly mentioned otherwise.</p>
+<h4><span style="color: #f97352;">Service Provision</span></h4>
+<p>You are granted Resources within the Fed4FIRE testbed so that You can use the Platform for the purposes described in the experiment projects You are taking part in. These resources can not be used for any other purposes.</p>
+<p>Platform resource providers aim to provide a stable, high-quality service. If there is evidence that the actions of users are adversely impacting this, resource providers are empowered to take reasonable measures to terminate or reprioritise usage in order to protect the overall operation of their services. Implicated users will be contacted by testbed providers as early as is reasonable.</p>
+<h4><span style="color: #f97352;">Acceptable Usage Policy</span></h4>
+<p>You are granted an account solely for Your own and personal use. You should take appropriate measure to protect Your credentials and prevent their use by third parties. The information You provide when requesting an account should be correct to the best of Your knowledge. You shall be responsible for all loss or damages to any part of the Platform as a result of any use of Your credentials to access the Platform, whether they are authorised or unauthorised by You.</p>
+<p>You shall be liable for actions performed on the Platform, by You, at your request or at the request of any other user invited or permitted by You to use services running on Fed4FIRE. In case of any loss or damage to the Platform originating from Your account, You are responsible for repairing or compensating for all damages to the Platform. In addition, You must respect the regulations of the various testbed resources You use in Your work, as described at <a href="http://www.fed4fire.eu/terms">http://www.fed4fire.eu/terms</a>. Your need to do this arises from co-operative agreements that have been made between all the organisations participating in the Platform.</p>
+<p>You may not interfere with others’ work or attempt to invade their privacy.</p>
+<p>You may not attempt to disrupt the working of the Platform.</p>
+<p>You must respect all Copyright for any software and data used on the Platform.</p>
+<p>The terms of software and data licences must be respected.</p>
+<p>You are not entitled to move proprietary data to, from, or via Platform systems without the prior agreement of its owner.</p>
+<p>Once You have registered to use the Platform, it is Your responsibility to remain aware of these regulations and of any changes made to them, and your continued use of the Platform means that you shall abide by the latest version of these terms and conditions.</p>
+<p>In order to keep the Platform operating correctly in both the technical and legal senses, it may become necessary to investigate network traffic (including, for example, e-mails) as well as examine information held on systems that are, or have been, connected to the Platform. You are deemed to have agreed to this.</p>
+<p>You must ensure that all known or obvious threats and vulnerabilities of the systems You run are adequately addressed.</p>
+<p>Should Your usage imply giving access to the Platform to third parties, You understand You will need to gather explicit consent from the operators of the individual testbed providers You will use, and You agree to enforce any restrictions imposed by an individual testbed provider and accept to fulfil Your legal obligations regarding data protection and retention laws.</p>
+<p>The following are explicitly forbidden on the Platform:</p>
+<ul>
+<li>Any military usage, including the development and production of weapons of mass destruction.</li>
+<li>Any activity resulting in compromising the security or integrity of any sites or networks connected to the Fed4FIRE facility</li>
+<li>Distribution of documents or materials containing insults or defamation, racial hatred or revisionism, terrorism, advertising, or distribution of material in a way that infringes the copyright of another person.</li>
+<li>Any illegal activity.</li>
+</ul>
+<p>You must comply to any additional national regulations from the government of the operators of the local testbeds.</p>
+<h4><span style="color: #f97352;">Enforcement</span></h4>
+<p>Whenever You use the Platform, You are bound by all the regulations in the current form of these terms and conditions and the legislation in force at the time.</p>
+<p>The regulations and legislation which applies to You will be enforced by iMinds, as leader of the Fed4FIRE consortium, or/and by the affected testbed providers, even if a breach of either has been evidenced from elsewhere.</p>
+<p>Note that for breaches of some legislation, the law enforcement can be involved.</p>
+<p>Ignorance of regulations or legislation is not a defence.</p>
+<p>Penalties, as defined in the individual testbed regulations at <a href="http://www.fed4fire.eu/terms">http://www.fed4fire.eu/terms</a>, will be levied for confirmed breaches of regulations.</p>
+<p>Disciplinary and investigative processes may also involve any Fed4FIRE partners, users and testbed providers involved in or affected by Your actions.</p>
+<p>Note that all testbed providers have agreed to co-operate in investigating disciplinary cases.</p>
+<p>You agree that the testbed and network providers in Fed4FIRE may monitor the systems and traffic for vulnerabilities and conformance to the acceptable uses, and You will collaborate with Fed4FIRE and any third party involved should any violations or breaches be noticed. The testbed providers involved may suspend or stop systems or suspend network connectivity without notice if such violations are found or suspected. To fulfil legal and contractual requirements, they may communicate to authorized third parties the owner and user of any resource provisioned and connected to the internet.</p>
+<h4><span style="color: #f97352;">Non-research use of Platform resources</span></h4>
+<p>The Fed4FIRE federation Platform has been constructed for experiment-driven research activities, where experiment-driven research is defined as any activity that furthers the user’s knowledge and/or understanding of algorithms, complex data structures or user behaviour.</p>
+<p>If You wish to use the Platform for any other purpose this must be authorized in advance by the Fed4FIRE testbed providers You will use. You will be expected to provide detailed information in support of Your request.</p>
+<p>Experiments must obtain prior agreement from the providers of all resources (e.g. computers, software, data, networks, and any other facilities) before these are used for any purposes other than experiment-driven research activities.</p>
+<p>The use of Fed4FIRE to host commercial services is explicitly disallowed.</p>
+<p>Experimenters that wish to use additional resources also have to agree with the policies of the testbed providers that offer the requested resources (when applicable). The individual testbed policies can be found here:</p>
+<p><a href="http://www.fed4fire.eu/terms/" target="_blank">fed4fire testbeds</a></p>
+<div class="clearboth"></div></div>
+</p>
--- /dev/null
+<p>Organization not listed? <a href="/portal/join">Request its addition now.</a></p>
+
--- /dev/null
+<div class="row">
+ <div class="col-md-10">
+ <p>
+ <span class="glyphicon glyphicon-info-sign"></span>
+ If you are a <b>PlanetLab Europe</b> user, please fill in this form using the same email address that you
+ currently use for your PlanetLab Europe account.
+ Your existing credentials will be used to validate your OneLab account.
+ </p>
+ </div>
+</div>
<h1><img src="{{ STATIC_URL }}icons/user-xs.png" alt="User Registration" />User sign-up</h1>
</div>
</div>
+<div class="row">
+ <div class="col-md-12">
+ <p><strong>Questions? <a href="/contact" >Contact us.</a></strong></p>
+ </div>
+</div>
+
{% if errors %}
<div class="row">
<div class="col-md-12">
</div>
</div>
{% endif %}
- <form action="/register" class="cmxform form-horizontal" method="post" enctype="multipart/form-data">
+<form action="/register" class="cmxform form-horizontal" method="post" enctype="multipart/form-data">
<div class="row">
<div class="col-md-6">
<div>
</select>
</div>
<p></p>
- <p>Organization not listed? <a href="/portal/join">Request its addition now.</a></p>
+ {% include theme|add:"_authority_notListed.html" %}
</div>
</div>
- <div class="col-md-6">
- <h4>
- Questions? <a href="/contact" >Contact us.</a>
- </h4>
- </div>
</div>
<div class="row">
<label for="password" class="control-label">Authentication</label>
</p>
<p>
- <input type="password" id="password" name="password" class="form-control" style="width:250px" minlength="4" value="{{ password }}"
+ <input type="password" id="password" name="password" class="form-control" style="width:250px" minlength="8" value="{{ password }}"
title="Your password allows you to log in to this portal."
placeholder="Password" required />
</p>
<p>
- <input type="password" id="confirmpassword" name="confirmpassword" style="width:250px" minlength="4" class="form-control" value=""
+ <input type="password" id="confirmpassword" name="confirmpassword" style="width:250px" minlength="8" class="form-control" value=""
placeholder="Confirm password" required />
</p>
<p>
</p>
</div>
</div>
-<div class="row">
- <div class="col-md-10">
- <div id="register">
- <p>
- <span class="glyphicon glyphicon-info-sign"></span>
- If you are a <b>PlanetLab Europe</b> user, please fill in this form using the same email address that you
- currently use for your PlanetLab Europe account.
- Your existing credentials will be used to validate your OneLab account.
- Please be sure to specify a different password for your new OneLab account.
- </p>
- </div>
- </div>
-</div>
+{% include theme|add:"_register_info.html" %}
<div class="row">
<div class="col-md-12">
<div id="register">
<h4 class="modal-title" id="myModalLabel">Terms & Conditions</h4>
</div>
<div class="modal-body">
- <p align="left">
- for OneLab Basic level service
- <br/>
- Version 0.6 of 20 May 2014
- <br>
- <a href="/portal/terms" target="_blank">[Printable format]</a>
- </p>
- <h1 align="left">1 Context</h1>
- <h2 align="left">1.1 OneLab</h2>
- <p align="left">
- OneLab is an experimental facility for testing new ideas and new technologies in the area of computer networking. It consists of a variety of types of
- platforms, including:</p>
- <ul type="disc">
- <li>
- <strong>internet overlay testbeds</strong>
- , testbeds that offer virtual machines distributed across locations in different countries, allowing users to deploy overlays on the internet;
- </li>
- <li>
- <strong>wireless testbeds</strong>
- , testbeds that consist of clusters of computers that are within Wi-Fi communication range of each other, either in an office environment or in an
- isolated setting;
- </li>
- <li>
- <strong>internet of things testbeds</strong>
- , testbeds that consist of embedded computing nodes with sensor capabilities, communicating wirelessly in an isolated environment;
- </li>
- <li>
- <strong>emulation testbeds,</strong>
- computing clusters that offer virtual machines on servers that are interconnected by a high speed switch, enabling large scale network emulation.
- </li>
- </ul>
- <p align="left">
- This list of types of platforms is subject to change, and the current list, along with the identities of the specific platforms of each type, can be found
- on the OneLab website (onelab.eu).</p>
- <p align="left">
- Each platform has its own owners, and OneLab is the grouping of these platforms through a consortium of institutions. The OneLab consortium is coordinated
- by UPMC Sorbonne Universités. It operates on a not-for-profit basis.</p>
- <p align="left">
- Access to OneLab may also provide access to additional platforms that are not part of OneLab, due to a federation agreement between OneLab and the owners
- of those platforms.</p>
- <h2 align="left">1.2 Fee-free Basic level service</h2>
- <p align="left">These terms and conditions define and apply to OneLab's Basic level service, which is available free of charge.</p>
- <p align="left">
- Users who would like additional services are encouraged to contact support@onelab.eu. Some additional services require a written agreement, but are
- otherwise free. Others require the payment of fees or in-kind contributions. (An example of an in-kind contribution is the hosting of a PlanetLab Europe
- server node.)</p>
- <h2 align="left">1.3 Managers and standard users</h2>
- <p align="left">
- There are two classes of OneLab user: the manager and the standard user. OneLab grants access rights to managers, who, in turn, provide access rights to
- standard users. Examples are: for a small enterprise, an executive may be the manager and the employees may be standard users; for a research team, a
- senior scientist (faculty member or research scientist) may be a manager and doctoral students and other members of the team may be standard users; for a
- university course, a professor may be a manager and the students may be standard users.</p>
- <h2 align="left">1.4 These terms and conditions</h2>
- <p align="left">
- Acceptance of these terms and conditions is a condition of obtaining OneLab Basic level user service. They are posted to the OneLab portal site
- (portal.onelab.eu). They may be changed without other notice than the posting of a new version to the portal site.</p>
- <h1 align="left">2 Services provided by OneLab</h1>
- <h2 align="left">2.1 Access to the experimental facility</h2>
- <p align="left">
- OneLab provides users with access to the platforms that make up the experimental facility. Each platform owner determines the specifics of this access (for
- example, how many nodes are available to a user, what happens in case of oversubscription, etc.), with the proviso that Basic level service requires that
- users be able to conduct meaningful experiments on every OneLab testbed.</p>
- <p align="left">
- Basic level service may also provide access to platforms that are federated with OneLab, but such access depends upon the terms of the federation
- agreements with those platforms, which may require that the user have a higher level of service in order to gain access. For example, Basic level service
- provides access to PlanetLab Europe, a OneLab platform, without providing access to PlanetLab Central, a federated platform. Users wanting full access
- across the global PlanetLab system should contact support@onelab.eu to arrange to enter into a PlanetLab Europe membership agreement.</p>
- <p align="left">OneLab's role is to facilitate access to the platforms. Specifically, it provides each user with:</p>
- <ul>
- <li align="left">
- <strong>a single account,</strong>
- the credentials for which can be used to access all of the OneLab testbeds;
- </li>
- <li align="left">
- <strong>tools through which to access the testbeds</strong>
- , including, notably, a web-based portal (portal.onelab.eu) that allows a user to see the resources available on each testbed and to reserve them,
- along with a number of experiment control tools that a user can employ to deploy an experiment on those resources;
- </li>
- <li align="left">
- <strong>support</strong>
- , with documentation on how to use the tools, pointers to documentation for individual testbeds, and a helpdesk to respond to user questions.
- </li>
- </ul>
-<p align="left">
- Additional support, such as accompaniment through the design and deployment of experiments and the interpretation of their results, is available through
- higher levels of service.
-</p>
-<h2 align="left">
- 2.2 Best effort, without guarantees
-</h2>
-<p align="left">
- OneLab and the owners of the individual OneLab testbeds do their best to provide the services outlined here, with the understanding that Basic level
- service offers no guarantees. Users should clearly understand the following limitations.
-</p>
-<ul type="disc">
- <li>
- <strong>Reliability:</strong>
- OneLab does not provide any guarantees with respect to the reliability of the portal, of other tools, or of the individual nodes on platforms. These
- may be taken down for maintenance, rebooted, or reinstalled at any time. Reinstallation implies that disks are wiped, meaning that users should not
- consider a local disk to be a persistent form of storage.
- </li>
- <li>
- <strong>Fitness:</strong>
- OneLab does not guarantee that the platforms are suitable for the experiments that users intend to conduct. There may be limitations in the
- technologies that are offered that prevent certain types of experiments from being carried out.
- </li>
- <li>
- <strong>Privacy</strong>
- : OneLab does not guarantee the privacy of traffic generated on the platforms (e.g., wireless signals, packets). Unless otherwise specified by an
- individual platform owner, users should assume that traffic is monitored and logged. Such monitoring may be done intentionally, for example, to allow
- platform administrators as well as other users to investigate abuse.
- </li>
-</ul>
-<p align="left">
- Users who seek such guarantees are invited to consider a higher level of service.
-</p>
-<h2 align="left">
- 2.3 Limitedliability
-</h2>
-<p align="left">
- In no event shall the partners of the OneLab consortium be liable to any user for any consequential, incidental, punitive, or lost profit damages, or for
- any damages arising out of loss of use or loss of data, to the extent that such damages arise out of the activities of OneLab consortium partners, or any
- breach of the present terms and conditions, even if the consortium partner has been advised of the possibility of such damages.
-</p>
-<p align="left">
- Nothing contained in these terms and conditions shall be deemed as creating any rights or liabilities in or for third parties who are not Basic level users
- of OneLab.
-</p>
-<h1 align="left">
- 3 Acceptable use policy
-</h1>
-<h2 align="left">
- 3.1 Responsibilities of managers and standard users
-</h2>
-<p align="left">
- OneLab creates and administers accounts for managers and delegates to managers the responsibility for creating and administering accounts for standard
- users. Both managers and standard users are required to follow OneLab's acceptable use policy. In addition, managers are fully responsible for the
- activities of the standard users whose accounts they create.
-</p>
-<p align="left">
- A manager is expected to grant user access only an individual with whom he or she has a working relationship. In general, this means an individual who
- works for the same institution as the manager, or, in the case of higher education and research, an individual who is a student at the university where the
- manager works. Managers may also grant access to individuals from other institutions, provided that they are collaborating on a common project on OneLab.
- If there is a doubt, a manager should refer the question to support@onelab.eu.
-</p>
-<h2 align="left">
- 3.2 Types of use
-</h2>
-<p align="left">
- OneLab may be used by enterprise, by scientific researchers, and by educators.
-</p>
-<p align="left">
- OneLab may be used for pre-commercial research and development. In keeping with OneLab's not-for-profit status, it may not be used to deploy services that
- are designed to generate a commercial profit.
-</p>
-<p align="left">
- Not-for-profit use of OneLab to deploy services that are designed to generate revenue requires prior approval through a written agreement, and thus may not
- be carried out on a Basic level account. Interested users are invited to contact support@onelab.eu.
-</p>
-<p align="left">
- OneLab may be used for scientific research.
-</p>
-<p align="left">
- OneLab may be used to host lab exercises for university courses.
-</p>
-<p align="left">
- Questions about other types of use should be addressed to support@onelab.eu.
-</p>
-<h2 align="left">
- 3.3 Applicable laws and regulations
-</h2>
-<p align="left">
- OneLab is managed, and the portal is hosted, in France. Information regarding the countries in which individual testbeds are managed and hosted is
- available from those testbeds. Users are responsible for being aware of the countries in which their experiments are deployed and for ensuring that their
- use of OneLab fully conforms to the laws and regulations of those countries, as well as the laws and regulations of the country in which they themselves
- are present when conducting their experiments.
-</p>
-<p align="left">
- Above and beyond specific national laws, the activities email spamming, phishing through web services, and all types of Internet fraud are prohibited on
- OneLab.
-</p>
-<h2>
- 3.4 Security and accounting mechanisms
-</h2>
-<p align="left">
- Users are expected to respect the security and accounting mechanisms put in place by OneLab, its platforms, and federated platforms. For example, access to
- PlanetLab Europe is designed to take place through the SSH cryptographically-secured connection protocol, which uses public/private key pair
- authentication, and so users should not attempt to bypass this mechanism. As another example, OneLab's notion of a "slice" associates a set of resources
- with the group of users who have reserved those resources, and users should not attempt to obscure the identities of participants in a slice.
-</p>
-<p align="left">
- Hacking attempts against the OneLab portal and testbeds are not permitted. This includes "red team" (hacker test) experiments.
-</p>
-<h2>
- 3.5 Sharing of resources
-</h2>
-<p align="left">
- OneLab is intended for ambitious experiments. Large numbers of resources and extended leases on resources may legitimately be granted in order to carry
- these out. At the same time, OneLab and its testbeds are shared environments, and when there is contention for resources, limits must be imposed.
-</p>
-<p align="left">
- Each OneLab platform sets its own policies for handling resource contention. As a general rule, users are encouraged to design their experiments to use
- resources efficiently. In particular, spinning/busy-waiting techniques for extended periods of time are strongly discouraged. Some resource contention
- policies (e.g., PlanetLab Europe's) terminate the jobs that are using the most resources in the case of contention.
-</p>
-<h2>
- 3.6 Internet-connected platforms
-</h2>
-<p align="left">
- Some of OneLab's platforms allow experiments to take place on resources that have access to the public internet. These experiments can potentially generate
- traffic to, and receive traffic from, any host or router in the internet.<a></a><a id="_anchor_1" href="#_msocom_1" name="_msoanchor_1">[LB1]</a>
-</p>
-<p align="left">
- Furthermore, some internet-connected platforms (e.g., PlanetLab Europe) consist of servers that are hosted by a large number of member institutions.
-</p>
-<p align="left">
- The accessibility of internet-connected platforms and the distributed hosting model of some of these platforms imply certain responsibilities on the part
- of users, as detailed below.
-</p>
-<h3>
- 3.6.1 General guidance
-</h3>
-<p align="left">
- A good litmus test when considering whether an experiment is appropriate for such internet-connected platforms is to ask what the network administrator at
- one's own organisation would say about the experiment running locally. If the experiment disrupts local activity (e.g., uses more than its share of the
- site's internet bandwidth) or triggers complaints from remote network administrators (e.g., performs systematic port scans), then it is not appropriate for
- such internet-connected platforms.
-</p>
-<p align="left">
- It is the responsibility of the user and the user's manager to ensure that an application that will run on an internet-connected platform is tested and
- debugged in a controlled environment, to better understand its behaviour prior to deployment.
-</p>
-<h3>
- 3.6.2 Standards of network etiquette
-</h3>
-<p align="left">
- Internet-connected platforms are designed to support experiments that generate unusual traffic, such as network measurements. However, it is expected that
- all users adhere to widely accepted standards of network etiquette in an effort to minimise complaints from network administrators. Activities that have
- been interpreted as worm and denial-of-service attacks in the past (and should be avoided) include sending SYN packets to port 80 on random machines,
- probing random IP addresses, repeatedly pinging routers, overloading bottleneck links with measurement traffic, and probing a single target machine from
- many nodes.
-</p>
-<p align="left">
- For internet-connected platforms that have a distributed hosting model, each host institution will have its own acceptable use policy. Users should not
- knowingly violate such local policies. Conflicts between local policies and OneLab's stated goal of supporting research into wide-area networks should be
- brought to the attention of OneLab administrators at support@onelab.eu.
-</p>
-<h3>
- 3.6.3 Specific network usage rules
-</h3>
-<p align="left">
- It is not allowed to use one or more nodes of an internet-connected platform to generate a high number of network flows or flood a site with high traffic
- to the point of interfering with its normal operation. Use of congestion-controlled flows for large transfers is highly encouraged.
-</p>
-<p align="left">
- It is not allowed to perform systematic or random port or address block scans from an internet-connected platform.
-</p>
-<p align="left">
- For internet-connected platforms that use a distributed hosting model, it is not allowed to spoof or sniff traffic on a hosted server or on the network the
- server belongs to.
-</p>
-<p align="left">
- Access to a server on a distributed hosting platform may not be used to gain access to other servers or networked equipment that are not part of the
- testbed.
-</p>
-<h2>
- 3.7 Wireless platforms
-</h2>
-<p align="left">
- Wireless-connected platforms give users access to nodes that communicate via Wi-Fi and other wireless technologies. They may be capable of detecting
- wireless activity in the neighbourhood of those nodes: traffic generated by other users of the platform or by individuals not associated with the platform.
- In general, much of the traffic will be encrypted, with certain aspects (such as SSIDs) not encrypted, but it is also possible that there will be fully
- unencrypted traffic. They may also be capable of generating wireless activity that reaches equipment outside of the testbed.
-</p>
-<p align="left">
- Furthermore, some wireless-connected platforms may have built-in limitations to prevent them from generating signals at a strength that exceeds health and
- safety regulations.
-</p>
-<p align="left">
- These characteristics of wireless-connected platforms imply certain responsibilities on the part of users, as detailed below.
-</p>
-<h3>
- 3.7.1 Specific network usage rules
-</h3>
-<p align="left">
- Experimenters may make no attempt to defeat the encryption of encrypted third-party traffic. Furthermore, experimenters must treat with utmost discretion
- any unencrypted traffic. Limited metadata can be recorded for the bona fide purposes of an experiment, but under no case should third party communications
- be recorded.
-</p>
-<p align="left">
- No attempt may be made to reverse engineer traffic in order to learn the identities of the parties who have generated the traffic.
-</p>
-<p align="left">
- Wireless-connected platforms may not be used to gain access to any network equipment that is not part of the testbed itself.
-</p>
-<p align="left">
- It is not allowed to perform systematic or random scans of wireless networks that are not part of a wireless-connected platform. Similarly, it is not
- allowed to spoof or sniff wireless traffic of the institution that hosts a wireless-connected platform or of other networks in the proximity.
-</p>
-<p align="left">
- Care must be taken so that traffic on wireless-connected platforms does not interfere with the normal functioning of network equipment that is not part of
- the testbed itself.
-</p>
-<p align="left">
- No attempt may be made to defeat the mechanisms that limit signal strength on wireless-connected platforms.
-</p>
-<h2>
- 3.8 Handling suspected violations
-</h2>
-<p align="left">
- Suspected violations of the OneLab acceptable use policy should be reported to support@onelab.eu.
-</p>
-<p align="left">
- Upon notification or detection of a possible violation, OneLab management will attempt to understand if a violation has in fact occurred. To do so,
- management will freely communicate with the users concerned, the operators of the platforms concerned, as well as any third parties that might be involved.
- An example of a third party is a network operator who detects what they believe to be unauthorized traffic emanating from a OneLab platform.
-</p>
-<p align="left">
- The priority is to resolve any real or apparent violations amicably. However, if OneLab management believes that a violation may have occurred, it can, at
- its sole discretion, and without prior notice, apply any of the following measures:
-</p>
-<ul type="disc">
- <li>
- notification of the users of the concerned slice (set of resources);
- </li>
- <li>
- disabling of the concerned slice;
- </li>
- <li>
- disabling an individual user's account;
- </li>
- <li>
- reporting of the user's activity to his/her manager;
- </li>
- <li>
- disabling of the manager's account and all user accounts for which the manager is responsible;
- </li>
- <li>
- disabling of all accounts associated with the user's institution.
- </li>
-</ul>
-<p align="left">
- In the case of suspected illegal activity, OneLab management might need, without prior notice, to notify the relevant authorities.
-</p>
-
+ {% include theme|add:"_terms_and_conditions.html" %}
</div>
<div class="modal-footer">
<button type="button" class="btn btn-default" data-dismiss="modal">Close</button>
</div>
</div>
</div>
-
<script>
$(document).ready(function(){
- var availableTags = [
- {% if authorities %}
- {% for authority in authorities %}
- {% if authority.name %}
- {value:"{{ authority.authority_hrn }}",label:"{{authority.name}}"},
- // show hrn if we don't have the name
- {% else %}
- {value:"{{ authority.authority_hrn }}",label:"{{authority.authority_hrn}}"},
- {% endif %}
- {% endfor %}
- {% else %}
- {value:"",label:"No authority found !!!"}
- {% endif %}
- ];
- // sorting the list
-
- availableTags.sort(function(a,b){
- var nameA=a.value.toLowerCase(), nameB=b.value.toLowerCase();
- if (nameA < nameB) {
- return -1;
- }
- if (nameA > nameB) {
- return 1;
- }
- return 0;
- });
+
// auto-complete the form
jQuery("#org_name").combobox();
+
+ {% if theme == 'fed4fire' %}
+ //setting the default value in the org_list
+ var temp="fed4fire.global";
+ $("#org_name").val(temp);
+ {% endif %}
+
$('[title!=""]').qtip();
$("form").validate();
$("form").submit(function() {
});
</script>
{% endblock %}
-
--- /dev/null
+<p align="left">
+for OneLab Basic level service
+<br/>
+Version 0.6 of 20 May 2014
+<br>
+<a href="/portal/terms" target="_blank">[Printable format]</a>
+</p>
+<h1 align="left">1 Context</h1>
+<h2 align="left">1.1 OneLab</h2>
+<p align="left">
+OneLab is an experimental facility for testing new ideas and new technologies in the area of computer networking. It consists of a variety of types of
+platforms, including:</p>
+<ul type="disc">
+<li>
+<strong>internet overlay testbeds</strong>
+, testbeds that offer virtual machines distributed across locations in different countries, allowing users to deploy overlays on the internet;
+</li>
+<li>
+<strong>wireless testbeds</strong>
+, testbeds that consist of clusters of computers that are within Wi-Fi communication range of each other, either in an office environment or in an
+isolated setting;
+</li>
+<li>
+<strong>internet of things testbeds</strong>
+, testbeds that consist of embedded computing nodes with sensor capabilities, communicating wirelessly in an isolated environment;
+</li>
+<li>
+<strong>emulation testbeds,</strong>
+computing clusters that offer virtual machines on servers that are interconnected by a high speed switch, enabling large scale network emulation.
+</li>
+</ul>
+<p align="left">
+This list of types of platforms is subject to change, and the current list, along with the identities of the specific platforms of each type, can be found
+on the OneLab website (onelab.eu).</p>
+<p align="left">
+Each platform has its own owners, and OneLab is the grouping of these platforms through a consortium of institutions. The OneLab consortium is coordinated
+by UPMC Sorbonne Universités. It operates on a not-for-profit basis.</p>
+<p align="left">
+Access to OneLab may also provide access to additional platforms that are not part of OneLab, due to a federation agreement between OneLab and the owners
+of those platforms.</p>
+<h2 align="left">1.2 Fee-free Basic level service</h2>
+<p align="left">These terms and conditions define and apply to OneLab's Basic level service, which is available free of charge.</p>
+<p align="left">
+Users who would like additional services are encouraged to contact support@onelab.eu. Some additional services require a written agreement, but are
+otherwise free. Others require the payment of fees or in-kind contributions. (An example of an in-kind contribution is the hosting of a PlanetLab Europe
+server node.)</p>
+<h2 align="left">1.3 Managers and standard users</h2>
+<p align="left">
+There are two classes of OneLab user: the manager and the standard user. OneLab grants access rights to managers, who, in turn, provide access rights to
+standard users. Examples are: for a small enterprise, an executive may be the manager and the employees may be standard users; for a research team, a
+senior scientist (faculty member or research scientist) may be a manager and doctoral students and other members of the team may be standard users; for a
+university course, a professor may be a manager and the students may be standard users.</p>
+<h2 align="left">1.4 These terms and conditions</h2>
+<p align="left">
+Acceptance of these terms and conditions is a condition of obtaining OneLab Basic level user service. They are posted to the OneLab portal site
+(portal.onelab.eu). They may be changed without other notice than the posting of a new version to the portal site.</p>
+<h1 align="left">2 Services provided by OneLab</h1>
+<h2 align="left">2.1 Access to the experimental facility</h2>
+<p align="left">
+OneLab provides users with access to the platforms that make up the experimental facility. Each platform owner determines the specifics of this access (for
+example, how many nodes are available to a user, what happens in case of oversubscription, etc.), with the proviso that Basic level service requires that
+users be able to conduct meaningful experiments on every OneLab testbed.</p>
+<p align="left">
+Basic level service may also provide access to platforms that are federated with OneLab, but such access depends upon the terms of the federation
+agreements with those platforms, which may require that the user have a higher level of service in order to gain access. For example, Basic level service
+provides access to PlanetLab Europe, a OneLab platform, without providing access to PlanetLab Central, a federated platform. Users wanting full access
+across the global PlanetLab system should contact support@onelab.eu to arrange to enter into a PlanetLab Europe membership agreement.</p>
+<p align="left">OneLab's role is to facilitate access to the platforms. Specifically, it provides each user with:</p>
+<ul>
+<li align="left">
+<strong>a single account,</strong>
+the credentials for which can be used to access all of the OneLab testbeds;
+</li>
+<li align="left">
+<strong>tools through which to access the testbeds</strong>
+, including, notably, a web-based portal (portal.onelab.eu) that allows a user to see the resources available on each testbed and to reserve them,
+along with a number of experiment control tools that a user can employ to deploy an experiment on those resources;
+</li>
+<li align="left">
+<strong>support</strong>
+, with documentation on how to use the tools, pointers to documentation for individual testbeds, and a helpdesk to respond to user questions.
+</li>
+</ul>
+<p align="left">
+ Additional support, such as accompaniment through the design and deployment of experiments and the interpretation of their results, is available through
+ higher levels of service.
+</p>
+<h2 align="left">
+ 2.2 Best effort, without guarantees
+</h2>
+<p align="left">
+ OneLab and the owners of the individual OneLab testbeds do their best to provide the services outlined here, with the understanding that Basic level
+ service offers no guarantees. Users should clearly understand the following limitations.
+</p>
+<ul type="disc">
+ <li>
+ <strong>Reliability:</strong>
+ OneLab does not provide any guarantees with respect to the reliability of the portal, of other tools, or of the individual nodes on platforms. These
+ may be taken down for maintenance, rebooted, or reinstalled at any time. Reinstallation implies that disks are wiped, meaning that users should not
+ consider a local disk to be a persistent form of storage.
+ </li>
+ <li>
+ <strong>Fitness:</strong>
+ OneLab does not guarantee that the platforms are suitable for the experiments that users intend to conduct. There may be limitations in the
+ technologies that are offered that prevent certain types of experiments from being carried out.
+ </li>
+ <li>
+ <strong>Privacy</strong>
+ : OneLab does not guarantee the privacy of traffic generated on the platforms (e.g., wireless signals, packets). Unless otherwise specified by an
+ individual platform owner, users should assume that traffic is monitored and logged. Such monitoring may be done intentionally, for example, to allow
+ platform administrators as well as other users to investigate abuse.
+ </li>
+</ul>
+<p align="left">
+ Users who seek such guarantees are invited to consider a higher level of service.
+</p>
+<h2 align="left">
+ 2.3 Limitedliability
+</h2>
+<p align="left">
+ In no event shall the partners of the OneLab consortium be liable to any user for any consequential, incidental, punitive, or lost profit damages, or for
+ any damages arising out of loss of use or loss of data, to the extent that such damages arise out of the activities of OneLab consortium partners, or any
+ breach of the present terms and conditions, even if the consortium partner has been advised of the possibility of such damages.
+</p>
+<p align="left">
+ Nothing contained in these terms and conditions shall be deemed as creating any rights or liabilities in or for third parties who are not Basic level users
+ of OneLab.
+</p>
+<h1 align="left">
+ 3 Acceptable use policy
+</h1>
+<h2 align="left">
+ 3.1 Responsibilities of managers and standard users
+</h2>
+<p align="left">
+ OneLab creates and administers accounts for managers and delegates to managers the responsibility for creating and administering accounts for standard
+ users. Both managers and standard users are required to follow OneLab's acceptable use policy. In addition, managers are fully responsible for the
+ activities of the standard users whose accounts they create.
+</p>
+<p align="left">
+ A manager is expected to grant user access only an individual with whom he or she has a working relationship. In general, this means an individual who
+ works for the same institution as the manager, or, in the case of higher education and research, an individual who is a student at the university where the
+ manager works. Managers may also grant access to individuals from other institutions, provided that they are collaborating on a common project on OneLab.
+ If there is a doubt, a manager should refer the question to support@onelab.eu.
+</p>
+<h2 align="left">
+ 3.2 Types of use
+</h2>
+<p align="left">
+ OneLab may be used by enterprise, by scientific researchers, and by educators.
+</p>
+<p align="left">
+ OneLab may be used for pre-commercial research and development. In keeping with OneLab's not-for-profit status, it may not be used to deploy services that
+ are designed to generate a commercial profit.
+</p>
+<p align="left">
+ Not-for-profit use of OneLab to deploy services that are designed to generate revenue requires prior approval through a written agreement, and thus may not
+ be carried out on a Basic level account. Interested users are invited to contact support@onelab.eu.
+</p>
+<p align="left">
+ OneLab may be used for scientific research.
+</p>
+<p align="left">
+ OneLab may be used to host lab exercises for university courses.
+</p>
+<p align="left">
+ Questions about other types of use should be addressed to support@onelab.eu.
+</p>
+<h2 align="left">
+ 3.3 Applicable laws and regulations
+</h2>
+<p align="left">
+ OneLab is managed, and the portal is hosted, in France. Information regarding the countries in which individual testbeds are managed and hosted is
+ available from those testbeds. Users are responsible for being aware of the countries in which their experiments are deployed and for ensuring that their
+ use of OneLab fully conforms to the laws and regulations of those countries, as well as the laws and regulations of the country in which they themselves
+ are present when conducting their experiments.
+</p>
+<p align="left">
+ Above and beyond specific national laws, the activities email spamming, phishing through web services, and all types of Internet fraud are prohibited on
+ OneLab.
+</p>
+<h2>
+ 3.4 Security and accounting mechanisms
+</h2>
+<p align="left">
+ Users are expected to respect the security and accounting mechanisms put in place by OneLab, its platforms, and federated platforms. For example, access to
+ PlanetLab Europe is designed to take place through the SSH cryptographically-secured connection protocol, which uses public/private key pair
+ authentication, and so users should not attempt to bypass this mechanism. As another example, OneLab's notion of a "slice" associates a set of resources
+ with the group of users who have reserved those resources, and users should not attempt to obscure the identities of participants in a slice.
+</p>
+<p align="left">
+ Hacking attempts against the OneLab portal and testbeds are not permitted. This includes "red team" (hacker test) experiments.
+</p>
+<h2>
+ 3.5 Sharing of resources
+</h2>
+<p align="left">
+ OneLab is intended for ambitious experiments. Large numbers of resources and extended leases on resources may legitimately be granted in order to carry
+ these out. At the same time, OneLab and its testbeds are shared environments, and when there is contention for resources, limits must be imposed.
+</p>
+<p align="left">
+ Each OneLab platform sets its own policies for handling resource contention. As a general rule, users are encouraged to design their experiments to use
+ resources efficiently. In particular, spinning/busy-waiting techniques for extended periods of time are strongly discouraged. Some resource contention
+ policies (e.g., PlanetLab Europe's) terminate the jobs that are using the most resources in the case of contention.
+</p>
+<h2>
+ 3.6 Internet-connected platforms
+</h2>
+<p align="left">
+ Some of OneLab's platforms allow experiments to take place on resources that have access to the public internet. These experiments can potentially generate
+ traffic to, and receive traffic from, any host or router in the internet.<a></a><a id="_anchor_1" href="#_msocom_1" name="_msoanchor_1">[LB1]</a>
+</p>
+<p align="left">
+ Furthermore, some internet-connected platforms (e.g., PlanetLab Europe) consist of servers that are hosted by a large number of member institutions.
+</p>
+<p align="left">
+ The accessibility of internet-connected platforms and the distributed hosting model of some of these platforms imply certain responsibilities on the part
+ of users, as detailed below.
+</p>
+<h3>
+ 3.6.1 General guidance
+</h3>
+<p align="left">
+ A good litmus test when considering whether an experiment is appropriate for such internet-connected platforms is to ask what the network administrator at
+ one's own organisation would say about the experiment running locally. If the experiment disrupts local activity (e.g., uses more than its share of the
+ site's internet bandwidth) or triggers complaints from remote network administrators (e.g., performs systematic port scans), then it is not appropriate for
+ such internet-connected platforms.
+</p>
+<p align="left">
+ It is the responsibility of the user and the user's manager to ensure that an application that will run on an internet-connected platform is tested and
+ debugged in a controlled environment, to better understand its behaviour prior to deployment.
+</p>
+<h3>
+ 3.6.2 Standards of network etiquette
+</h3>
+<p align="left">
+ Internet-connected platforms are designed to support experiments that generate unusual traffic, such as network measurements. However, it is expected that
+ all users adhere to widely accepted standards of network etiquette in an effort to minimise complaints from network administrators. Activities that have
+ been interpreted as worm and denial-of-service attacks in the past (and should be avoided) include sending SYN packets to port 80 on random machines,
+ probing random IP addresses, repeatedly pinging routers, overloading bottleneck links with measurement traffic, and probing a single target machine from
+ many nodes.
+</p>
+<p align="left">
+ For internet-connected platforms that have a distributed hosting model, each host institution will have its own acceptable use policy. Users should not
+ knowingly violate such local policies. Conflicts between local policies and OneLab's stated goal of supporting research into wide-area networks should be
+ brought to the attention of OneLab administrators at support@onelab.eu.
+</p>
+<h3>
+ 3.6.3 Specific network usage rules
+</h3>
+<p align="left">
+ It is not allowed to use one or more nodes of an internet-connected platform to generate a high number of network flows or flood a site with high traffic
+ to the point of interfering with its normal operation. Use of congestion-controlled flows for large transfers is highly encouraged.
+</p>
+<p align="left">
+ It is not allowed to perform systematic or random port or address block scans from an internet-connected platform.
+</p>
+<p align="left">
+ For internet-connected platforms that use a distributed hosting model, it is not allowed to spoof or sniff traffic on a hosted server or on the network the
+ server belongs to.
+</p>
+<p align="left">
+ Access to a server on a distributed hosting platform may not be used to gain access to other servers or networked equipment that are not part of the
+ testbed.
+</p>
+<h2>
+ 3.7 Wireless platforms
+</h2>
+<p align="left">
+ Wireless-connected platforms give users access to nodes that communicate via Wi-Fi and other wireless technologies. They may be capable of detecting
+ wireless activity in the neighbourhood of those nodes: traffic generated by other users of the platform or by individuals not associated with the platform.
+ In general, much of the traffic will be encrypted, with certain aspects (such as SSIDs) not encrypted, but it is also possible that there will be fully
+ unencrypted traffic. They may also be capable of generating wireless activity that reaches equipment outside of the testbed.
+</p>
+<p align="left">
+ Furthermore, some wireless-connected platforms may have built-in limitations to prevent them from generating signals at a strength that exceeds health and
+ safety regulations.
+</p>
+<p align="left">
+ These characteristics of wireless-connected platforms imply certain responsibilities on the part of users, as detailed below.
+</p>
+<h3>
+ 3.7.1 Specific network usage rules
+</h3>
+<p align="left">
+ Experimenters may make no attempt to defeat the encryption of encrypted third-party traffic. Furthermore, experimenters must treat with utmost discretion
+ any unencrypted traffic. Limited metadata can be recorded for the bona fide purposes of an experiment, but under no case should third party communications
+ be recorded.
+</p>
+<p align="left">
+ No attempt may be made to reverse engineer traffic in order to learn the identities of the parties who have generated the traffic.
+</p>
+<p align="left">
+ Wireless-connected platforms may not be used to gain access to any network equipment that is not part of the testbed itself.
+</p>
+<p align="left">
+ It is not allowed to perform systematic or random scans of wireless networks that are not part of a wireless-connected platform. Similarly, it is not
+ allowed to spoof or sniff wireless traffic of the institution that hosts a wireless-connected platform or of other networks in the proximity.
+</p>
+<p align="left">
+ Care must be taken so that traffic on wireless-connected platforms does not interfere with the normal functioning of network equipment that is not part of
+ the testbed itself.
+</p>
+<p align="left">
+ No attempt may be made to defeat the mechanisms that limit signal strength on wireless-connected platforms.
+</p>
+<h2>
+ 3.8 Handling suspected violations
+</h2>
+<p align="left">
+ Suspected violations of the OneLab acceptable use policy should be reported to support@onelab.eu.
+</p>
+<p align="left">
+ Upon notification or detection of a possible violation, OneLab management will attempt to understand if a violation has in fact occurred. To do so,
+ management will freely communicate with the users concerned, the operators of the platforms concerned, as well as any third parties that might be involved.
+ An example of a third party is a network operator who detects what they believe to be unauthorized traffic emanating from a OneLab platform.
+</p>
+<p align="left">
+ The priority is to resolve any real or apparent violations amicably. However, if OneLab management believes that a violation may have occurred, it can, at
+ its sole discretion, and without prior notice, apply any of the following measures:
+</p>
+<ul type="disc">
+ <li>
+ notification of the users of the concerned slice (set of resources);
+ </li>
+ <li>
+ disabling of the concerned slice;
+ </li>
+ <li>
+ disabling an individual user's account;
+ </li>
+ <li>
+ reporting of the user's activity to his/her manager;
+ </li>
+ <li>
+ disabling of the manager's account and all user accounts for which the manager is responsible;
+ </li>
+ <li>
+ disabling of all accounts associated with the user's institution.
+ </li>
+</ul>
+<p align="left">
+ In the case of suspected illegal activity, OneLab management might need, without prior notice, to notify the relevant authorities.
+</p>
<p><strong>Questions? <a href="/contact" >Contact us.</a></strong></p>
</div>
</div>
+
{% if errors %}
<div class="row">
<div class="col-md-12">
</div>
</div>
{% endif %}
- <form action="/register" class="cmxform form-horizontal" method="post" enctype="multipart/form-data">
+<form action="/register" class="cmxform form-horizontal" method="post" enctype="multipart/form-data">
<div class="row">
- <div class="col-md-12">
- <div class="form-group">
+ <div class="col-md-6">
+ <div>
{% csrf_token %}
<label for="authority_hrn" class="control-label">Organization</label>
<p></p>
title="Choose your organization (company/university) from the list that apears when you click in the field and start to type.
Use the arrow keys to scroll through the list; type part of the name to narrow down the list. We will send an email to
the managers that we have on record for your organization, asking them to validate your sign-up request." required>
+ <option value="">select an organization</option>
{% if authorities %}
{% for authority in authorities %}
{% if authority.name %}
<option value="{{ authority.authority_hrn }}">{{authority.name}}</option>
{% else %}
<option value="{{ authority.authority_hrn }}">{{authority.authority_hrn}}</option>
- {% endif %}
{% endif %}
- {% endfor %}
+ {% endfor %}
{% else %}
<option value:"">No authority found !!!</option>
{% endif %}
</select>
</div>
<p></p>
- </div>
+ {% include theme|add:"_authority_notListed.html" %}
+ </div>
</div>
</div>
<div class="row">
<div class="col-md-6">
-
- <div class="form-group">
+ <p>
<label for="firstname" class="control-label">Personal information</label>
- <p></p>
+ </p>
+ <p>
<input type="text" name="firstname" class="form-control" style="width:350px" minlength="2" value="{{ first_name }}" placeholder="First name" required />
- </div>
- <div class="form-group">
+ </p>
+ <p>
<input type="text" name="lastname" size="25" class="form-control" style="width:350px" minlength="2" value="{{ last_name }}" placeholder="Last name" required />
- </div>
- <div class="form-group">
- <input type="email" name="email" size="25" class="form-control" style="width:350px" value="{{ email }}"
- title="Your e-mail address will be your identifier for logging in. We contact you to verify your account and then, occasionally, for important issues."
- placeholder="Email" required />
- </div>
+ </p>
+ <p>
+ <input type="email" name="email" size="25" class="form-control" style="width:350px" value="{{ email }}" title="Your e-mail address will be your identifier for logging in. We contact you to verify your account and then, occasionally, for important issues." placeholder="Email" required />
+ </p>
</div>
<div class="col-md-6">
- <div class="form-group">
+ <p>
<label for="password" class="control-label">Authentication</label>
- <p></p>
- <input type="password" id="password" name="password" class="form-control" style="width:250px" minlength="4" value="{{ password }}"
+ </p>
+ <p>
+ <input type="password" id="password" name="password" class="form-control" style="width:250px" minlength="8" value="{{ password }}"
title="Your password allows you to log in to this portal."
placeholder="Password" required />
- </div>
- <div class="form-group">
- <input type="password" id="confirmpassword" name="confirmpassword" style="width:250px" minlength="4" class="form-control" value=""
+ </p>
+ <p>
+ <input type="password" id="confirmpassword" name="confirmpassword" style="width:250px" minlength="8" class="form-control" value=""
placeholder="Confirm password" required />
- </div>
- <div class="form-group">
+ </p>
+ <p>
<select name="question" class="form-control" style="width:350px" id="key-policy"
title="Your public/private key pair allows you to access the testbeds." required >
<option value="generate">Generate my keys for me (recommended)</option>
<option value="upload">Upload my public key (advanced users only)</option>
</select>
- </div>
- <div class="form-group" style="display:none;" id="upload_key">
+ </p>
+ <div style="display:none;" id="upload_key">
<label for="file" class="control-label">Upload public key</label>
<input type="file" name="user_public_key" class="form-control" style="width:200px" id="user_public_key" />
<br />
</div>
<div class="row">
<div class="col-md-12">
- <div class="form-group">
- <p></p>
+ <p>
<input type="checkbox" name="agreement" value="agreement" required /> I agree to the
<a href="#" data-toggle="modal" data-target="#myModal">terms and conditions.</a>
- </div>
+ </p>
</div>
</div>
+{% include theme|add:"_register_info.html" %}
<div class="row">
<div class="col-md-12">
- <div class="form-group" id="register">
- <p></p>
+ <div id="register">
+ <p>
<input class="submit btn btn-onelab" type="submit" value="Sign up" />
+ </p>
</form>
</div>
</div>
<h4 class="modal-title" id="myModalLabel">Terms & Conditions</h4>
</div>
<div class="modal-body">
- <p align="left">
- To be added soon.
- </p>
-
+ {% include theme|add:"_terms_and_conditions.html" %}
</div>
<div class="modal-footer">
<button type="button" class="btn btn-default" data-dismiss="modal">Close</button>
</div>
</div>
</div>
-
<script>
$(document).ready(function(){
- var availableTags = [
- {% if authorities %}
- {% for authority in authorities %}
- {% if authority.name %}
- {value:"{{ authority.authority_hrn }}",label:"{{authority.name}}"},
- // show hrn if we don't have the name
- {% else %}
- {value:"{{ authority.authority_hrn }}",label:"{{authority.authority_hrn}}"},
- {% endif %}
- {% endfor %}
- {% else %}
- {value:"",label:"No authority found !!!"}
- {% endif %}
- ];
- // sorting the list
-
- availableTags.sort(function(a,b){
- var nameA=a.value.toLowerCase(), nameB=b.value.toLowerCase();
- if (nameA < nameB) {
- return -1;
- }
- if (nameA > nameB) {
- return 1;
- }
- return 0;
- });
+
// auto-complete the form
jQuery("#org_name").combobox();
+
+ {% if theme == 'fed4fire' %}
+ //setting the default value in the org_list
+ var temp="fed4fire.global";
+ $("#org_name").val(temp);
+ {% endif %}
+
$('[title!=""]').qtip();
$("form").validate();
$("form").submit(function() {
});
</script>
{% endblock %}
-
git://git.onelab.eu / unfold.git / commitdiff