Skip to content

GitLab

Commit 32315484 authored by Jay Lepreau's avatar Jay Lepreau
Browse files

snapshot before upload from laptop

parent 6efc4430
Hide whitespace changes
Inline Side-by-side
www/faq.html
View file @ 32315484
<html>
<head>
<title>
Utah Network Testbed - Web Interface FAQ
</title>
<link rel='stylesheet' href='tbstyle.css' type='text/css'>
<base href='https://plastic.cs.utah.edu/' target='dynamic'>
</head>
<body>
<h1>Utah Network Testbed - Web Interface FAQ</h1>
To protect any data you submit, SSL is used to encrypt data as it
is transfered accross the Internet. Therefore, you will need to
access these pages with a browser that supports SSL. We recommend
Netscape 4.0 or greater, and we also recommend a screen resolution
of at least 800x600 to avoid excessive scrolling.
<p>
<head>
<title>Utah Network Testbed - Web Interface FAQ</title>
<link rel='stylesheet' href='tbstyle.css' type='text/css'>
<base href='https://www.emulab.net/' target='dynamic'>
</head>
<ol>
<li><h3>What do I need to do to be able to use the Testbed?</h3>
<p>If you're here on your own, or you're the leader of a group
of people who want to use the Testbed, the first step is to
apply to <em>create</em> a <em>project</em>. A project is an
entity that has been approved to use the Testbed, and the
project leader is held responsible for the actions of members of
his/her project. The leader can allow users to join the project
and use the Testbed as a member of his/her project. To create a
project, click on the link in the side bar titled 'Start a
Project'. Fill out the requested information, and your request
will be submitted to the Testbed Approval Committee.
</p>
<li><h3>Someone told me to join their project. How do I do
that?</h3>
<p>The process of joining an existing project is quite
simple. Go to the 'Join a Project' page, fill out the
form, and wait for the project leader to approve you. Once
approved, you can log into the Testbed. Your project leader will
control how much access you have to Testbed resources, within
the limits given to the project as a whole.
</p>
<li><h3>I'm already a Testbed user, but I'm collaborating with
another project. Can I join that project too?</h3>
<p>Yes, if that project leader approves you.
Do the appropriate stuff on the 'Join a Project' page.
</p>
<li><h3>I've been approved. How do I use my account?</h3>
<p>The first step would be to come back here and log in to
the Web interface. That
will update list of options in the side bar.
<!-- You might be
authorized to start projects or experiments, or maybe just to
use the nodes in an experiment. Either way, your options will
show up in the side bar. -->
Those will normally include starting a new "experiment"
which leads to reserving a set of nodes, which leads to
automatic creation of Unix accounts on those nodes for all members in your
project. You will be able to use ssh to log into those machines.
<p>
You will also receive an
account on the "control" machine, and from there will be able to access
the test nodes' serial line consoles via 'tip' as well as access
console log files.
<body>
<h1>Utah Network Testbed - Web Interface FAQ</h1>
</p>
<li><h3>You still haven't answered my question. Who can I
ask?</h3>
<p>You can try the other web pages for the Testbed, located on the
<a href="http://www.cs.utah.edu/flux/testbed/"> Testbed
Homepage</a>, or in the
<a href="http://www.cs.utah.edu/flux/testbed/doc/"> Testbed
Documentation</a>. When all else fails, you can send e-mail
<a href="mailto:testbed-control@flux.cs.utah.edu">
Testbed Control (testbed-control@flux.cs.utah.edu)</a>.
</p>
</ol>
To protect any data you submit, SSL is used to encrypt data as it
is transfered accross the Internet. Therefore, you will need to
access these pages with a browser that supports SSL. We recommend
Netscape 4.0 or greater, and we also recommend a screen resolution
of at least 800x600 to avoid excessive scrolling.
<p>
</body>
</html>
\ No newline at end of file
<ol>
<li><h3>What do I need to do to be able to use the Testbed?</h3>
<p>
If you're here on your own, or you're the leader of a group
of people who want to use the Testbed, the first step is to
apply to <em>create</em> a <em>project</em>. A project is an
entity that has been approved to use the Testbed, and the
project leader is held responsible for the actions of members of
his/her project. The leader can allow users to join the project
and use the Testbed as a member of his/her project. To create a
project, click on the link in the side bar titled 'Start a
Project'. Fill out the requested information, and your request
will be submitted to the Testbed Approval Committee.
</p>
<li><h3>Someone told me to join their project. How do I do that?</h3>
<p>
Go to the 'Join a Project' page, fill out the
form, and wait for the project leader to approve you. When
approved you will receive an email message saying so,
and you can then log into the Testbed.
<!-- Not implemented:
Your project leader will
control how much access you have to Testbed resources, within
the limits given to the project as a whole.
-->
</p>
<li><h3>I'm already a Testbed user, but I'm collaborating with
another project. Can I join that project too?</h3>
<p>
Yes, if that project leader approves you.
Do the appropriate stuff on the 'Join a Project' page.
</p>
<li><h3>I've been approved. How do I use my account?</h3>
<p>
The first step would be to come back here and log in to the Web
interface. That will update the list of options in the side bar.
<!-- We don't support this fine granularity now. I hope.
You might be authorized to start projects or experiments, or
maybe just to use the nodes in an experiment. Either way, your
options will show up in the side bar.
-->
Those will normally include starting a new "experiment" which leads to
reserving a set of nodes, which leads to automatic creation of Unix
accounts on those nodes for all members in your project. You will be
able to use ssh to log into those machines.
<p>
You will also receive an account on the master control machine
"login.emulab.net", and from there will be able to access the test
nodes' serial line consoles via 'tip' as well as access console log
files.
</p>
<li><h3>You still haven't answered my question. Who can I ask?</h3>
<p>
You can try the other web pages for the Testbed, located on the
<a href="http://www.cs.utah.edu/flux/testbed/">Testbed
Homepage</a>, or in the
<a href="http://www.cs.utah.edu/flux/testbed/doc/"> Testbed
Documentation</a>. When all else fails, you may
<a href="mailto:testbed-ops@flux.cs.utah.edu">
send e-mail to Testbed Ops</a>(testbed-ops@flux.cs.utah.edu).
</p>
</ol>
</body>
</html>
www/welcome.html
View file @ 32315484
<html>
<head>
<title>Utah Network Testbed - Control Home</title>
<title>Utah Network Testbed - Operations Home</title>
<link rel='stylesheet' href='tbstyle.css' type='text/css'>
<base href='https://plastic.cs.utah.edu/' target='dynamic'>
<base href='https://www.emulab.net/' target='dynamic'>
</head>
<body>
<h1>Testbed Control</h1>
<h1>Testbed Operations</h1>
This is the operational Web interface to the testbed.
This is the Web-based operational interface to the testbed.
For information on the testbed itself, see the
<a href = "http://www.cs.utah.edu/flux/testbed/">base</a> and
<a href = "http://www.cs.utah.edu/flux/testbed/doc/">documentation</a> pages.
<p>
OUTLINE
Policy
Authorization Scheme
What is it?
Raw hardware and management and configuration tools.
In practice, provide some default software that many users
may want. But fundamentally, the software you run on it,
including all bits on the disks, is up to you.
What do users get?
Home dir on login node.
<h2>Overview of the authorization scheme and policy</h2>
<h2>Policy</h2>
<ul><b>Appropriate Use:</b>
In principle, almost any research or experimental use of the testbed
by experimenters that have a need for it is appropriate.
<p>
When our resources become oversubscribed we will be allocating
resources based on some currently vague function of perceived research
value, resources required (typically number of nodes and weirdness
of software), the testbed's uniqueness as a suitable platform for the
research,
sponsorship by our primary sponsors (currently NSF and Cisco),
affiliation with an academic institution, funded project,
and for commercial users, ability to pay.
Many commercial users would also be allowed
Use this set of pages
<ul>
<li> to gain authorization to use the testbed, either as
......@@ -34,7 +77,7 @@ receive email.
Briefly, you use the links at your left to create and join
<em>projects</em>. Typically, a project leader will request
permission from Testbed Control, via the web interface, to
permission from Testbed Ops, via the web interface, to
<em>create</em> a project. Then, people working on project
(students, staff, etc.) will request permission from the Project
Leader, also via the web interface, to <em>join</em> the project.
......@@ -43,18 +86,11 @@ receive email.
configuring nodes as necessary. More detailed information on this
process can be found in the <a href="faq.html">FAQ</a>.
<h2>Frequently Asked Questions</h2>
There is an extensive <a href="faq.html">FAQ</a> which will
hopefully answer other questions you have regarding the
Testbed.
<p>
<h2>How to contact Testbed Control</h2>
<h2>How to contact Testbed Ops</h2>
For questions or problems, send email to
<a href="mailto:testbed-control@flux.cs.utah.edu">
Testbed Control (testbed-control@flux.cs.utah.edu)</a>.
<a href="mailto:testbed-ops@flux.cs.utah.edu">
Testbed Ops (testbed-ops@flux.cs.utah.edu)</a>.
<p>
</body>
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment