Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

Fixed doc links, tried to make all relative.

  • Loading branch information...
commit 25c97f1b8a133c3ec024e9de8a4fd92918f2e303 1 parent 4be8c85
@labisso labisso authored
Showing with 117 additions and 377 deletions.
  1. +1 −0  docs/m4/worksp.lib.m4
  2. +1 −1  docs/src/admin/index.html
  3. +1 −1  docs/src/admin/overview.html
  4. +7 −8 docs/src/admin/quickstart.html
  5. +6 −6 docs/src/admin/reference.html
  6. +2 −2 docs/src/admin/troubleshooting.html
  7. +51 −51 docs/src/changelog.html
  8. +3 −3 docs/src/clouds/appendix.html
  9. +5 −5 docs/src/clouds/cloudquickstart.html
  10. +1 −1  docs/src/clouds/clusters.html
  11. +3 −3 docs/src/clouds/clusters2.html
  12. +0 −126 docs/src/clouds/index.html
  13. +1 −1  docs/src/clouds/multicloud.html
  14. +0 −113 docs/src/clouds/nimbus.html
  15. +0 −9 docs/src/clouds/vpninstructions.html
  16. +6 −4 docs/src/dev/apis.html
  17. +1 −1  docs/src/dev/reference.html
  18. +0 −7 docs/src/doc/admin-index.html
  19. +3 −3 docs/src/doc/cloud.html
  20. +1 −1  docs/src/doc/metadata-quickstart.html
  21. +0 −7 docs/src/doc/user-index.html
  22. +2 −2 docs/src/elclients.html
  23. +7 −7 docs/src/features.html
  24. BIN  docs/src/img/warning.gif
  25. +1 −1  docs/src/index.html
  26. +2 −2 docs/src/interfaces/deployment.html
  27. +4 −4 docs/src/plugins/index.html
  28. +1 −1  docs/src/plugins/service-accounting.html
  29. +1 −1  docs/src/plugins/service-authz.html
  30. +1 −1  docs/src/plugins/service-network.html
  31. +1 −1  docs/src/plugins/service-prop.html
  32. +1 −1  docs/src/plugins/service-reqintake.html
  33. +1 −1  docs/src/plugins/service-sched.html
  34. +1 −1  docs/src/plugins/service-tasks.html
  35. +1 −1  docs/src/summary.html
View
1  docs/m4/worksp.lib.m4
@@ -1,6 +1,7 @@
m4_changequote(`[[[', `'')m4_dnl
m4_dnl
m4_define([[[_NIMBUS_WEBSITE',http://nimbus.mcs.anl.gov)m4_dnl
+m4_define([[[_SCIENCECLOUDS_WEBSITE',http://www.scienceclouds.org)m4_dnl
m4_define([[[_WORKSP_PREVIOUS_VM_VERSION', TP2.1)m4_dnl
m4_define([[[_WORKSP_CURRENT_VM_VERSION', TP2.2)m4_dnl
m4_define([[[_WORKSP_CURRENT_VM_VERSION_LONG', Technology Preview 2.0)m4_dnl
View
2  docs/src/admin/index.html
@@ -67,7 +67,7 @@
<p>
<a href="../doc/cloud.html">Cloud Guide</a> - Administrator
overview of the configurations necessary to set up installations
- compatible with the <a href="clouds/cloudquickstart.html">cloud
+ compatible with the <a href="../clouds/cloudquickstart.html">cloud
client</a>.
</p>
</li>
View
2  docs/src/admin/overview.html
@@ -10,7 +10,7 @@
<br />
<p>
- <img src="/img/warning.gif" alt="[warning]" />
+ <img src="../img/warning.gif" alt="[warning]" />
Apologies, this page is in the process of being updated. The information
here is accurate for TP2.2 but incomplete.
</p>
View
15 docs/src/admin/quickstart.html
@@ -154,7 +154,7 @@
<h4>* Acquire the AutoContainer: _NAMELINK(acquire-auto-container)</h4>
<p>
- On the <a href="/downloads/">downloads</a> page is a recent version of the
+ On the <a href="_NIMBUS_WEBSITE/downloads/">downloads</a> page is a recent version of the
AutoContainer.
</p>
@@ -255,7 +255,7 @@
<p>
You can test Xen with any Xen VM image, mostly. In this guide we will use a
small and simple VM image as an example. Look
- <a href="../../marketplace.html#other">here</a> for some
+ <a href="_SCIENCECLOUDS_WEBSITE/marketplace/#other">here</a> for some
ideas about where to find Xen VM images. You can also create them from
scratch of course, if you have the time.
</p>
@@ -269,7 +269,7 @@
<p>
You can download a tarball containg the image
- <a href="http://workspace.globus.org/downloads/ttylinux-xen.tgz">here</a>.
+ <a href="_NIMBUS_WEBSITE/downloads/ttylinux-xen.tgz">here</a>.
This directory should contain the following files:
</p>
<ul>
@@ -479,7 +479,7 @@
<h4>* Retrieve and unpack:</h4>
<p>
- Grab the main Nimbus archive from the <a href="/downloads">downloads</a>
+ Grab the main Nimbus archive from the <a href="_NIMBUS_WEBSITE/downloads">downloads</a>
page and unpack the archive:
</p>
@@ -565,7 +565,7 @@
<p>
For more information about what these things are, see the
- <a href="../../faq.html">FAQ</a>.
+ <a href="NIMBUS_WEBSITE/faq/">FAQ</a>.
</p>
<p>
You will not be able to run against the EC2 frontend until you have
@@ -1203,9 +1203,8 @@
<p>
Do not hesitate to contact the
- <a href="../../../contact.html">workspace-user</a> mailing list with
- problems. This quickstart is new and we have also not moved over some
- of the information from the <a href="../../TP1.3.3/doc/admin-index.html">old admin guide</a>.
+ <a href="_NIMBUS_WEBSITE/contact/">workspace-user</a> mailing list with
+ problems.
</p>
<p>
We plan to streamline some of the steps and also significantly add to the
View
12 docs/src/admin/reference.html
@@ -1582,8 +1582,8 @@
<h2>Two context broker implementations _NAMELINK(context-broker)</h2>
<p>
- The <a href="../../faq.html#ctxbroker">context broker</a> is used to
- enable <a href="/clouds/clusters.html">one click clusters</a>.
+ The <a href="_NIMBUS_WEBSITE/faq/#ctxbroker">context broker</a> is used to
+ enable <a href="../clouds/clusters.html">one click clusters</a>.
</p>
<p>
Before TP2.2, there was one implementation of the context broker and its
@@ -1618,8 +1618,8 @@
<h2>Configuring the OLD context broker _NAMELINK(context-broker-old)</h2>
<p>
- The <a href="../../faq.html#ctxbroker">context broker</a> is used to
- enable <a href="/clouds/clusters.html">one click clusters</a>.
+ The <a href="_NIMBUS_WEBSITE/faq/#ctxbroker">context broker</a> is used to
+ enable <a href="../clouds/clusters.html">one click clusters</a>.
</p>
<p>
To set up an OLD broker (see <a href="#context-brokers-two">above</a>)
@@ -1697,8 +1697,8 @@
<h2>Configuring the NEW context broker _NAMELINK(context-broker-new)</h2>
<p>
- The <a href="../../faq.html#ctxbroker">context broker</a> is used to
- enable <a href="/clouds/clusters.html">one click clusters</a>.
+ The <a href="_NIMBUS_WEBSITE/faq/#ctxbroker">context broker</a> is used to
+ enable <a href="../clouds/clusters.html">one click clusters</a>.
</p>
<p>
The new TP2.2 broker (see <a href="#context-broker">above</a>)
View
4 docs/src/admin/troubleshooting.html
@@ -13,7 +13,7 @@
Any questions can be posted to the workspace-user mailing list and will
likely be answered promptly by a member of the community. For instructions
on how to subscribe and post messages to this list, see the
- <a href="../../../contact.html">contact page</a>.
+ <a href="_NIMBUS_WEBSITE/contact/">contact page</a>.
</p>
<p>
@@ -150,7 +150,7 @@
</p>
<p>
An option here is to use
- <a href="/downloads/install-cert-1.tar.gz">this program</a> (source
+ <a href="_NIMBUS_WEBSITE/downloads/install-cert-1.tar.gz">this program</a> (source
included) to add the certificate. It will contact the endpoint,
retrieve the advertised certificate, and then give you an option to
create a new "keystore" with the old trusted certificates and the
View
102 docs/src/changelog.html
@@ -17,7 +17,7 @@
</p>
<a name="TP2.2"> </a>
-<h3><a href="./TP2.2/index.html">TP2.2</a> _NAMELINK(TP2.2)</h3>
+<h3>TP2.2</h3>
<i>Summary</i>
<ul>
@@ -179,7 +179,7 @@
</ul>
<a name="TP2.1"> </a>
-<h3><a href="./TP2.1/index.html">TP2.1</a> _NAMELINK(TP2.1)</h3>
+<h3>TP2.1</h3>
<i>Summary</i>
<ul>
@@ -230,8 +230,8 @@
<li>
<p>
Updated documentation.
- Added an <a href="TP2.1/plugins/index.html">extensibility guide</a>
- and <a href="TP2.1/admin/upgrading.html">upgrade guide</a>.
+ Added an <a href="plugins/index.html">extensibility guide</a>
+ and <a href="admin/upgrading.html">upgrade guide</a>.
</p>
</li>
<li>
@@ -250,7 +250,7 @@
run several validity tests.
</p>
<p>
- See <a href="TP2.1/admin/quickstart.html#part-IIb">this section</a> of
+ See <a href="admin/quickstart.html#part-IIb">this section</a> of
the administrator quickstart for more information.
</p>
</li>
@@ -262,7 +262,7 @@
</p>
<p>
It requires a separate download.
- See <a href="TP2.1/admin/quickstart.html#auto-container">this section</a>
+ See <a href="admin/quickstart.html#auto-container">this section</a>
of the administrator quickstart for more information.
</p>
</li>
@@ -270,13 +270,13 @@
<p>
Introduction of the "cloud-admin" program which will allow you
to very easily manage new users in a
- <a href="TP2.1/doc/cloud.html">cloud</a> configuration.
+ <a href="doc/cloud.html">cloud</a> configuration.
</p>
<p>
It is installed at the same time as the auto-configuration program,
installed as
<i>$GLOBUS_LOCATION/share/nimbus-autoconfig/cloud-admin.sh</i>,
- see <a href="TP2.1/doc/cloud.html#cloud-admin">this section</a>
+ see <a href="doc/cloud.html#cloud-admin">this section</a>
of the cloud guide for more information
</p>
</li>
@@ -413,13 +413,13 @@
<a name="TP2.0"> </a>
-<h3><a href="./TP2.0/index.html">TP2.0</a> _NAMELINK(TP2.0)</h3>
+<h3>TP2.0</h3>
<i>Summary</i>
<ul>
<li>
<p>
- Introduction of the <a href="faq.html">FAQ</a> which explains
+ Introduction of the FAQ which explains
many things you may already know, but it also includes new descriptions
of the component system now more clearly articulated in the Nimbus
TP2.0 release.
@@ -428,7 +428,7 @@
<li>
<p>
Introduction of the Java
- <a href="faq.html#rm-api">RM API</a> which is
+ RM API which is
a bridge between protocols and resource management implementations.
The resource managers can remain protocol/framework/security agnostic
(they can be "pure Java") and various protocol implementations
@@ -467,7 +467,7 @@
<li>
<p>
Introduction of the Java
- <a href="faq.html#rm-api">RM API</a> which is
+ RM API which is
a bridge between protocols and resource management work. The
resource managers below can remain protocol/framework agnostic
(they can be "pure Java") and various protocol implementations
@@ -613,7 +613,7 @@
<li>
<a href="http://www.springframework.org/">Spring</a> - just the
core dependency injection library. The
- <a href="faq.html#rm-api">RM API</a>
+ RM API
depends on Spring import statements but no other module has any
direct coupling to it.
</li>
@@ -683,15 +683,15 @@
<a name="TP1.3.3"> </a>
-<h3><a href="./TP1.3.3/index.html">TP1.3.3.1</a> _NAMELINK(TP1.3.3)</h3>
+<h3>TP1.3.3.1</h3>
<i>Summary</i>
<ul>
<li>
<p>
Introduction of support for contextualization with virtual
- clusters. See the <a href="/clouds/">clouds page</a> and the new
- <a href="/clouds/clusters.html">one-click clusters</a> page to see
+ clusters. See the <a href="clouds/">clouds page</a> and the new
+ <a href="clouds/clusters.html">one-click clusters</a> page to see
the various new features in action.
</p>
</li>
@@ -794,8 +794,8 @@
there).
</p>
<p>
- See the <a href="/clouds/">clouds page</a> and the new
- <a href="/clouds/clusters.html">clusters</a> page.
+ See the <a href="clouds/">clouds page</a> and the new
+ <a href="clouds/clusters.html">clusters</a> page.
</p>
</li>
<li>
@@ -812,7 +812,7 @@
<li>
<p>
Support for gzip via filename-sense. See cloud
- <a href="/clouds/clusters.html#compression">notes</a> on image
+ <a href="clouds/clusters.html#compression">notes</a> on image
compression/decompression. This can save a lot of time in cluster
launch situations since the gzip/gunzip happens on the VMMs
simultaneously, cutting transfer times (where there is contention)
@@ -856,7 +856,7 @@
<br />
<a name="TP1.3.2"> </a>
-<h3><a href="./TP1.3.2/index.html">TP1.3.2</a> _NAMELINK(TP1.3.2)</h3>
+<h3>TP1.3.2</h3>
<i>Summary</i>
<ul>
@@ -925,7 +925,7 @@
<ul>
<li>
<p>
- See the <a href="TP1.3.2/doc/cloud.html">Cloud Guide</a> for an overview
+ See the <a href="doc/cloud.html">Cloud Guide</a> for an overview
of a new set of configurations/conventions that allow for clients
to get up and running in minutes even from laptops on NATs.
Currently this comes at the cost of obscuring some features like
@@ -1084,9 +1084,9 @@
</p>
<p>
For more information on the client and setting up a configuration
- to support it, see the <a href="TP1.3.2/doc/cloud.html">Cloud Guide</a>.
+ to support it, see the <a href="doc/cloud.html">Cloud Guide</a>.
To see some examples of end-user commands, see the
- <a href="/clouds/">clouds</a> page.
+ <a href="clouds/">clouds</a> page.
</p>
</li>
<li>
@@ -1240,7 +1240,7 @@
<br />
<a name="TP1.3.1"> </a>
-<h3><a href="./TP1.3.1/index.html">TP1.3.1</a> _NAMELINK(TP1.3.1)</h3>
+<h3>TP1.3.1</h3>
<i>Summary</i>
<ul>
@@ -1323,9 +1323,9 @@
<p>
All remote interfaces (WSDLs/schemas) have been updated with at
least new namespaces. You can examine them directly online at the
- <a href="./TP1.3.1/examples/compact/index.html">WSDL and XSD files</a> page
+ WSDL and XSD files page
(or read the descriptions on the
- <a href="./TP1.3.1/interfaces/index.html">Interfaces</a> section). The main
+ Interfaces section). The main
difference is an extension to the factory create/deploy operation
and the addition of the ensemble service.
</p>
@@ -1451,7 +1451,7 @@
Note: a previously used TP1.2.3 or TP1.3 configuration file for
workspace-control will still work because of the nature of these
changes. See
- <a href="./TP1.3.1/doc/admin-index.html#migrating-workspaceVM">this
+ <a href="doc/admin-index.html#migrating-workspaceVM">this
migration section</a> of the administrator's guide for details.
</p>
</li>
@@ -1498,7 +1498,7 @@
<br />
<a name="TP1.3"> </a>
-<h3><a href="./TP1.3/index.html">TP1.3</a> _NAMELINK(TP1.3)</h3>
+<h3>TP1.3</h3>
<i>Summary</i>
<ul>
@@ -1543,14 +1543,14 @@
<p>
All remote interfaces, WSDLs/schemas, have been updated and also
have new namespaces. You can examine them directly online at the
- <a href="./TP1.3/examples/compact/index.html">WSDL and XSD files</a> page
+ <a href="examples/compact/index.html">WSDL and XSD files</a> page
(or read the descriptions on the
- <a href="./TP1.3/interfaces/index.html">Interfaces</a> section).
+ <a href="interfaces/index.html">Interfaces</a> section).
</p>
</li>
<li>
<p>
- The <a href="./TP1.3/interfaces/factory.html">Workspace Factory Service</a>
+ The <a href="interfaces/factory.html">Workspace Factory Service</a>
was extended to support starting a homogenous group of workspaces
in one deployment request. A global maximum group size can be
specified natively (without needing to use an authorization
@@ -1559,9 +1559,9 @@
</li>
<li>
<p>
- The <a href="./TP1.3/interfaces/groupservice.html">Workspace
+ The <a href="interfaces/groupservice.html">Workspace
Group Service</a> was added to manage groups after deployment.
- See the <a href="./TP1.3/interfaces/index.html#groupoverview">group
+ See the <a href="interfaces/index.html#groupoverview">group
overview</a> on the main interfaces page.
</p>
</li>
@@ -1579,7 +1579,7 @@
</li>
<li>
<p>
- The <a href="./TP1.3/interfaces/statusservice.html">Workspace
+ The <a href="interfaces/statusservice.html">Workspace
Status Service</a> was added, it allows a Grid client to consult
the usage statistics that the service has tracked about it.
See <a href="http://bugzilla.globus.org/globus/show_bug.cgi?id=5444">Bug 5444</a>.
@@ -1589,7 +1589,7 @@
<p>
Some configurations have been added, changed name or changed
location in the JNDI configuration file, see
- <a href="./TP1.3/doc/admin-index.html#migrating-workspaceVM">this
+ <a href="doc/admin-index.html#migrating-workspaceVM">this
migration section</a> of the administrator's guide for details.
</p>
</li>
@@ -1605,7 +1605,7 @@
<p>
Resource pool configurations can now be adjusted without
resetting the database, see
- <a href="./TP1.3/doc/admin-index.html#migrating-workspaceVM">this
+ <a href="doc/admin-index.html#migrating-workspaceVM">this
migration section</a> of the administrator's guide for details.
</p>
</li>
@@ -1613,7 +1613,7 @@
<p>
Networking address pool configurations can now be adjusted without
resetting the database, see
- <a href="./TP1.3/doc/admin-index.html#migrating-workspaceVM">this
+ <a href="doc/admin-index.html#migrating-workspaceVM">this
migration section</a> of the administrator's guide for details.
</p>
</li>
@@ -1695,7 +1695,7 @@
workspaces will be requested during the create operation. If
there is a NodeNumber element in a given deployment request file,
this argument will override that. For more about group support,
- see the <a href="./TP1.3/interfaces/index.html">Interfaces</a> section.
+ see the <a href="interfaces/index.html">Interfaces</a> section.
</p>
</li>
<li>
@@ -1750,7 +1750,7 @@
Note: a previously used TP1.2.3 configuration file for
workspace-control will still work because of the nature of these
changes. See
- <a href="./TP1.3/doc/admin-index.html#migrating-workspaceVM">this
+ <a href="doc/admin-index.html#migrating-workspaceVM">this
migration section</a> of the administrator's guide for details.
</p>
</li>
@@ -1830,14 +1830,14 @@
</ul>
<a name="TP1.2.3"> </a>
-<h3><a href="./TP1.2.3/index.html">TP1.2.3</a> _NAMELINK(TP1.2.3)</h3>
+<h3>TP1.2.3</h3>
<ul>
<li>
<p>
Significant documentation updates including the addition of a
- guided <a href="TP1.2.3/doc/user-index.html">User Quickstart</a>
- and the <a href="marketplace.html">Workspace Marketplace</a>.
+ guided <a href="doc/user-index.html">User Quickstart</a>
+ and the Workspace Marketplace.
</p>
</li>
<li>
@@ -1868,7 +1868,7 @@
staging. Included is the ability to provide checksums that
will be checked after the transfer as well as decompression
functionality. For more details, see the
- <a href="TP1.2.3/interfaces/optional.html">Optional parameters</a>
+ <a href="interfaces/optional.html">Optional parameters</a>
documentation.
(<a href="http://bugzilla.globus.org/globus/show_bug.cgi?id=5219">Bug 5219</a>)
</p>
@@ -1923,14 +1923,14 @@
</ul>
<a name="TP1.2.2"> </a>
-<h3><a href="./TP1.2.2/index.html">TP1.2.2</a> _NAMELINK(TP1.2.2)</h3>
+<h3>TP1.2.2 _NAMELINK(TP1.2.2)</h3>
<ul>
<li>
<p>
Added support for DHCP delivery of networking information. See
the administrator guide
- <a href="./TP1.2.2/doc/admin-index.html#workspaceVM-backend-config-invm-networking">DHCP
+ <a href="doc/admin-index.html#workspaceVM-backend-config-invm-networking">DHCP
overview and configuration section</a> which also includes a link
to a design document.
</p>
@@ -1945,7 +1945,7 @@
<li>
<p>
Streamlined the logistics section of metadata, see the
- <a href="./TP1.2.2/interfaces/metadata.html#logistics">logistics section</a>
+ <a href="interfaces/metadata.html#logistics">logistics section</a>
of the interfaces guide for more information.
</p>
</li>
@@ -1965,7 +1965,7 @@
</ul>
<a name="TP1.2.1"> </a>
-<h3><a href="./TP1.2.1/index.html">TP1.2.1</a> _NAMELINK(TP1.2.1)</h3>
+<h3>TP1.2.1</h3>
<ul>
<li>
@@ -2005,7 +2005,7 @@
</ul>
<a name="TP1.2"> </a>
-<h3><a href="./TP1.2/index.html">TP1.2</a> _NAMELINK(TP1.2)</h3>
+<h3>TP1.2</h3>
<ul>
<li>
@@ -2085,9 +2085,9 @@
</li>
</ul>
-<h3><a href="./TP1.1.1/index.html">TP1.1.1</a></h3>
+<h3>TP1.1.1</h3>
<a name="TP1.1.1"> </a>
-<h3><a href="./TP1.1.1/index.html">TP1.1.1</a> _NAMELINK(TP1.1.1)</h3>
+<h3>TP1.1.1</h3>
<ul>
<li>
@@ -2130,7 +2130,7 @@
</ul>
<a name="TP1.1"> </a>
-<h3><a href="./TP1.1/index.html">TP1.1</a> _NAMELINK(TP1.1)</h3>
+<h3>TP1.1</h3>
<ul>
<li>
View
6 docs/src/clouds/appendix.html
@@ -147,7 +147,7 @@
<li>
<p>
Check the
- <a href="http://workspace.globus.org/clouds/index.html#clouds">configuration
+ <a href="index.html#clouds">configuration
notes</a> for the cloud you want to use: they will point you to the
OpenVPN client configuration file to use. Download this file and
save it as something like "my/config/location" file.
@@ -270,7 +270,7 @@
<p>
To contextualize with EC2, you must use the cloud client #11 or later.
- It can be retrieved from our <a href="/downloads/archive.html">archive</a>.
+ It can be retrieved from our <a href="_NIMBUS_WEBSITE/downloads/archive.html">archive</a>.
</p>
<p>You must also have access to a broker service. You can run your own copy of
@@ -292,7 +292,7 @@
Nimbus cloud. The only major difference is that you must specify an AMI
name as the image of each workspace. An example cluster definition is
available
- <a href="http://workspace.globus.org/vm/TP2.2/examples/nimbus-ec2-basecluster.xml">here</a>
+ <a href="../examples/nimbus-ec2-basecluster.xml">here</a>
which references a public AMI we maintain.
</p>
View
10 docs/src/clouds/cloudquickstart.html
@@ -41,9 +41,9 @@
<p>
Download the
- <a href="/downloads/nimbus-cloud-client-013.tar.gz">latest
+ <a href="_NIMBUS_WEBSITE/downloads/nimbus-cloud-client-013.tar.gz">latest
nimbus cloud client</a> (16M), untar the file, and change to the
- cloud client directory (<i><a href="/downloads/archive.html#cloudclients">older
+ cloud client directory (<i><a href="_NIMBUS_WEBSITE/downloads/archive.html#cloudclients">older
versions of the cloud client</a></i>).
</p>
@@ -58,7 +58,7 @@
<p>
Make sure to subscribe to <i>workspace-user@globus.org</i> (see the
- <a href="../contact.html">contact</a> page for instruction on how
+ <a href="_NIMBUS_WEBSITE/contact.html">contact</a> page for instruction on how
to subscribe) to hear about client version updates.
</p>
@@ -177,7 +177,7 @@
upload an image to the cloud. To make it easy for you we already
uploaded many images to your personal repository directory that you
can launch. You can find more detailed descriptions of those images
- at the <a href="http://workspace.globus.org/vm/marketplace.html">Nimbus
+ at the <a href="_SCIENCECLOUDS_WEBSITE/marketplace/">Nimbus
marketplace</a>. To see what is available for running, list the images as
follows:
<p>
@@ -391,7 +391,7 @@
<p>
For questions (and to see others' questions answered), make sure to subscribe
to <i>workspace-user@globus.org</i> (see the
- <a href="../contact.html">contact</a> page for instruction on how to
+ <a href="_NIMBUS_WEBSITE/contact.html">contact</a> page for instruction on how to
subscribe).
</p>
View
2  docs/src/clouds/clusters.html
@@ -19,7 +19,7 @@
If you are already running on one of the <a href="index.html">science
clouds</a>, you could launch and use a cluster right this minute. Or you
could run your own cloud (the
- <a href="http://workspace.globus.org/downloads/index.html">software</a>
+ <a href="_NIMBUS_WEBSITE/downloads/index.html">software</a>
is free and open source).
</p>
View
6 docs/src/clouds/clusters2.html
@@ -19,7 +19,7 @@
If you are already running on one of the <a href="index.html">science
clouds</a>, you could launch and use a cluster right this minute. Or you
could run your own cloud (the
- <a href="http://workspace.globus.org/downloads/index.html">software</a>
+ <a href="_NIMBUS_WEBSITE/downloads/index.html">software</a>
is free and open source).
</p>
@@ -302,7 +302,7 @@
</p>
<ul>
- <li><a href="/downloads/nimbus-ctx-agent-2.2.tar.gz">nimbus-ctx-agent-2.2.tar.gz</a> (56K)</li>
+ <li><a href="_NIMBUS_WEBSITE/downloads/nimbus-ctx-agent-2.2.tar.gz">nimbus-ctx-agent-2.2.tar.gz</a> (56K)</li>
</ul>
<a name="agentdeps"> </a>
@@ -616,7 +616,7 @@
particular piece of software, one thing
you might try is asking on the <i>workspace-user@globus.org</i>
list for ideas since other cluster authors are lurking there (see the
- <a href="../contact.html">contact</a> page for
+ <a href="_NIMBUS_WEBSITE/contact/">contact</a> page for
instruction on how to subscribe).
</p>
View
126 docs/src/clouds/index.html
@@ -1,126 +0,0 @@
-m4_include(/mcs/m4/worksp.lib.m4)
-_NIMBUS_HEADER(Science Clouds)
-_NIMBUS_HEADER2(n,n,n,n,n,n,y)
-_NIMBUS_LEFT2_COLUMN
-
-_NIMBUS_LEFT2_CLOUDS1_SIDEBAR(y,n,n,n,n,n,n)
-
-_NIMBUS_LEFT2_COLUMN_END
-_NIMBUS_CENTER2_COLUMN
-
-<h2>Science Clouds</h2>
-
-<p>
-Science Clouds provide compute cycles in the cloud for
-scientific communities using <a href="http://workspace.globus.org">Nimbus</a>.
-</p>
-<p>
-The Nimbus cloud client allows you to provision
-customized compute nodes (that we call "workspaces") that you have
-full control over using a leasing model based on the Amazon's EC2
-service.
-
-</p>
-<p>
- The Science Clouds have two objectives: (1) to make it easy for
-scientific and educational projects to experiment with cloud computing
-and (2) to enable us to learn how to make cloud computing a useful
-tool for the scientific community.
-
-</p>
-<p>
- If you use any of these clouds, and have
-requests, comments, or suggestions please send them to us at <a
-href="mailto:workspace-user@globus.org">workspace-user@globus.org</a>
- (<a href="/contact.html">subscribe</a>). We
-will very much appreciate your feedback.
-
-<p>
-<a name="clouds"> </a>
-<h2> Available Science Clouds: </h2>
-
-<p>
-<b>To obtain access to a cloud, please contact the administrators of
-the clouds below. </b>Read cloud configuration notes carefully to ensure
-that you end up with the right software and configuration.
-<p>
-
-<ul>
-<li><b><a href="nimbus.html">Nimbus @ University of Chicago</a></b></li>
-<li><b><a href="http://www.acis.ufl.edu/vws/">Stratus @ University of Florida</a></b></li>
-<li><b><a href="http://www.rcac.purdue.edu/teragrid/resources/#wispy">Wispy @ Purdue University</a></b></li>
-<li><b><a href="http://meta.cesnet.cz/cms/opencms/en/docs/clouds">Kupa @ Masaryk University</a></b></li>
-</ul>
-
-<p>
-
-To get started follow the instructions in the
- <a href="cloudquickstart.html">cloud client quickstart guide</a>.
- Please subscribe to <a href="mailto:workspace-user@globus.org">workspace-user@globus.org</a>
- for updates on cloud status (<a href="/contact.html">subscribe</a>).
-<p>
-
-<hr />
-
-<br />
-
-<div style="float: left; width: 60px;"><a href="cloudquickstart.html"><img src="img/gnome-terminal.png" /></a></div>
-<p>
-<b> Use the science clouds as a client: </b> In a typical session you will make a request to
-deploy a workspace based on a specified VM image. You can either use
-one of the VM images already available on a cloud (the workspace cloud
-client provides a command that allows you to see what's already there)
-or upload your own VM image. On deployment, the image will be
-configured with an ssh public key you provide -- in this way once the
-workspace is deployed, you will be able to ssh into it and configure
-it further, upload data, or run your applications. Follow the
-<a href="cloudquickstart.html">quickstart</a> for specific instructions.
-</p>
-
-<div style="float: left; width: 60px;"><a href="clusters.html"><img src="img/network-receive.png" /></a></div>
-
-<p>
- <b>Launch one-click, auto-configuring clusters:</b> Once you have gotten
- a feel for things with one VM, head over to the
- <a href="clusters.html">clusters page</a>. Launch virtual clusters with one
- command! And no need to go configure anything: cluster configurations are
- automated with the workspace context broker. Each VM launches a very
- lightweight agent that greatly simplifies dealing with changing cluster
- topologies, identities, and credentials (no secrets need to reside on the
- image before booting). Useful sample clusters await you.
-</p>
-
-
-<div style="float: left; width: 60px;"><a href="../downloads/index.html"><img src="img/preferences-system.png" /></a></div>
-<p>
-<b> Build your own EC2-like cloud using the workspace service: </b>
-<a href="../downloads/index.html">Download the workspace service</a> to configure your own resources into a cloud. It accomodates a wide range of pre-existing cluster and network setups. See the current version's
-<a href="/vm/_WORKSP_CURRENT_VM_VERSION/doc/cloud.html">Cloud Guide</a>.
-</p>
-
-<br />
-
-<hr />
-<p>
- Be aware: Science clouds are a beta project deployed on a modest allocation
- of resources. Over the next few months we will be evolving the software
- in response to your requests and comments.
-</p>
-<p>
- Therefore, be aware that
- the client code may change frequently as new features, services and
- clouds become available.
-</p>
-<p>
- Each change will be announced on
- workspace-user@globus.org (<a href="/contact.html">subscribe</a>) and via
- <a href="/rss.xml">RSS</a>: keep an eye on those announcements to
- ensure that your client is up-to-date.
-</p>
-
-_NIMBUS_CENTER2_COLUMN_END
-_NIMBUS_FOOTER1
-_NIMBUS_FOOTER2
-_NIMBUS_FOOTER3
-
-
View
2  docs/src/clouds/multicloud.html
@@ -21,7 +21,7 @@
<ul>
<li>
Experimental support for this feature is present in
- <a href="../downloads/archive.html">cloud-client-012</a> and later.
+ <a href="_NIMBUS_WEBSITE/downloads/">cloud-client-012</a> and later.
</li>
<li>
You must have access to multiple <a href="index.html">Nimbus clouds</a>
View
113 docs/src/clouds/nimbus.html
@@ -1,113 +0,0 @@
-m4_include(/mcs/m4/worksp.lib.m4)
-_NIMBUS_HEADER(Science Clouds)
-_NIMBUS_HEADER2(n,n,n,n,n,n,y)
-_NIMBUS_LEFT2_COLUMN
-
-_NIMBUS_LEFT2_CLOUDS1_SIDEBAR
-
-_NIMBUS_LEFT2_COLUMN_END
-_NIMBUS_CENTER2_COLUMN
-
-<h2>Introduction to Nimbus @ UC</h2>
-
-<p>
-
-The University of Chicago Science Cloud, codenamed "Nimbus", provides
-compute capability in the form of <a href="http://xen.org/">Xen</a>
-virtual machines (VMs) that are deployed on physical nodes of the
-University of Chicago <a href="http://teraport.uchicago.edu/">TeraPort
-cluster</a> (currently 16 nodes) using the <a
-href="http://workspace.globus.org">Nimbus</a> software.
-
-<p>
-
-The Nimbus cloud is available to all members of the scientific community wanting to
-run in the cloud. To obtain access you will need to provide a
-justification (a few sentences explaining your science project) and a
-valid grid credential (If you don't have a credential, email us. We
-can help). Based on the project, you will be given an allocation on
-the cloud. Send your requests to Nimbus administrators at <a
-href="mailto:nimbus@mcs.anl.gov">nimbus@mcs.anl.gov</a>.
-
-<p>
-
-In a typical session you will make a request to deploy a workspace
-based on a specified VM image. You can either use one of the VM images
-already available on a cloud or upload your own VM image. On
-deployment, the image will be configured with an ssh public key you
-provide so that you can log into your VM once it is deployed. <b>Instructions on how to use the cloud are available
-<a href="cloudquickstart.html">here</a></b>. Have
-fun!
-
-<p>
-
-<h3> Important Configuration notes: </h3>
-
-<ul>
-<li>Nimbus provides public IP addresses for user's VMs. Thus, you will not need
-private network software to work with Nimbus.</li>
-<li>Nimbus works with version 10 or later of the workspace cloud client
- (see <a href="cloudquickstart.html#download">instructions</a> for download).</li>
-</ul>
-
-<p>
- To start using Nimbus download the workspace cloud client and follow
- the setup instructions. You will need the following:
-</p>
-
-<ul>
-<li><a href="cloud.properties">Nimbus configuration file</a></li>
-<li>A valid PKI X509 certificate</li>
-</ul>
-
-
-
-<!------------------------------------------------------------>
-<!------------------------------------------------------------>
-
-<br>
-<h3> EC2 clients: </h3>
-
-<p>
- To try the EC2 clients, download this
- <a href="http://s3.amazonaws.com/ec2-downloads/ec2-api-tools-1.3-24159.zip">EC2
- client</a> from Amazon.
-</p>
-
-<p>The specific URL to use:</p>
-
-_EXAMPLE_GENERICCMD_BEGIN
-export EC2_URL=https://tp-vm1.ci.uchicago.edu:8445/wsrf/services/ElasticNimbusService
-_EXAMPLE_CMD_END
-
-<p>
-</p>
-
-<p>
- See the <a href="../vm/_WORKSP_CURRENT_VM_VERSION/elclients.html">EC2 client notes</a> for more
- information. You will likely run into some of the EC2 client problems listed
- in the
- <a href="../vm/_WORKSP_CURRENT_VM_VERSION/admin/troubleshooting.html">troubleshooting</a> guide.
-</p>
-
-<p>
- These requests are not perpetual like on Amazon. The current running time
- requested from the backend scheduler and authorization system is
- three hours. You will not be "charged" for the whole amount if you use
- "terminate-instances" to destroy the VMs earlier than this.
-</p>
-
-<br>
-<br>
-<br>
-
-
-_NIMBUS_CENTER2_COLUMN_END
-_NIMBUS_FOOTER1
-_NIMBUS_FOOTER2
-_NIMBUS_FOOTER3
-
-
-
-
-
View
9 docs/src/clouds/vpninstructions.html
@@ -1,9 +0,0 @@
-m4_include(/mcs/m4/worksp.lib.m4)
-<script type="text/javascript" src="/redirect.js">
-</script>
-<script type="text/javascript">
- var redirect = new Redirect( "/clouds/appendix.html#vpn" );
- redirect.go();
-</script>
-
-
View
10 docs/src/dev/apis.html
@@ -22,14 +22,15 @@
implementations and semantics to be separate from one consistent
set of management operations. The implementing module governs how
and when callers get VMs, it assigns resources to use, and takes
- them away at the appropriate times, etc. See
- <a href="../../faq.html#rm-api">this faq entry</a>.
+ them away at the appropriate times, etc.
</p>
+<!--
<p>
You can see the API (javadocs) online
<a href="../doc/api/rm/overview-summary.html">here</a>
(version _WORKSP_CURRENT_VM_VERSION)
</p>
+-->
<br />
<h4>Pilot Program:</h4>
@@ -38,14 +39,15 @@
<p>
The workspace pilot program is the python program that runs under the
- local resource manager to secure resources. See
- <a href="../../faq.html#wpilot">this faq entry</a>.
+ local resource manager to secure resources.
</p>
+<!--
<p>
You can see the internal API (epydoc) online
<a href="../doc/api/pilot/index.html">here</a>
(version _WORKSP_CURRENT_VM_VERSION)
</p>
+-->
_NIMBUS_CENTER2_COLUMN_END
_NIMBUS_FOOTER1
View
2  docs/src/dev/reference.html
@@ -305,7 +305,7 @@
<p>
That's the bird's eye view. Ask questions about any of this on the
- <a href="/contact.html#dev">developer's list</a>.
+ <a href="_NIMBUS_WEBSITE/contact/#dev">developer's list</a>.
</p>
<br />
<br />
View
7 docs/src/doc/admin-index.html
@@ -1,7 +0,0 @@
-m4_include(/mcs/m4/worksp.lib.m4)
-<script type="text/javascript" src="/redirect.js">
-</script>
-<script type="text/javascript">
- var redirect = new Redirect( "../admin/index.html" );
- redirect.go();
-</script>
View
6 docs/src/doc/cloud.html
@@ -26,7 +26,7 @@
learn about it and configure the workspace service for it. This is
<b>not necessary for cloud users</b> to read and understand.</i> If you
are a cloud user just looking to understand how to launch and manage VMs
- on an existing cloud, start at the <a href="/clouds/">clouds page</a>.
+ on an existing cloud, start at the <a href="../clouds/">clouds page</a>.
</p>
<p>
@@ -222,7 +222,7 @@
<p>
You can see an example of a cluster cloud-client deployment on the
- <a href="/clouds/clusters.html">one-click clusters</a> page.
+ <a href="../clouds/clusters.html">one-click clusters</a> page.
</p>
<p>
@@ -256,7 +256,7 @@
that is included in the toplevel "conf" directory of the cloud-client
package. An example file is this
<a href="../examples/cloud.properties">cloud.properties file</a> which
- is currently distributed for the <a href="/clouds/">Nimbus</a> cloud.
+ is currently distributed for the Nimbus cloud.
</p>
<p class="indent">
View
2  docs/src/doc/metadata-quickstart.html
@@ -62,7 +62,7 @@
<p>
(It is possible to mount the VM's filesystem locally for inspection
and editing, for instructions see this
- <a href="../../offline-editing.html">offline editing guide</a>).
+ <a href="../offline-editing.html">offline editing guide</a>).
</p>
<h3>5. Make sure the networking is set up</h3>
View
7 docs/src/doc/user-index.html
@@ -1,7 +0,0 @@
-m4_include(/mcs/m4/worksp.lib.m4)
-<script type="text/javascript" src="/redirect.js">
-</script>
-<script type="text/javascript">
- var redirect = new Redirect( "../index.html" );
- redirect.go();
-</script>
View
4 docs/src/elclients.html
@@ -34,7 +34,7 @@
So <a href="http://s3.amazonaws.com/ec2-downloads/ec2-api-tools.zip">the
default client</a> may not always be the one to use. See a specific cloud's
documentation for the definitive tools URL (for example, the
- <a href="http://workspace.globus.org/clouds/nimbus.html">Nimbus cloud</a>).
+ <a href="_clouds/nimbus.html">Nimbus cloud</a>).
And see
<a href="http://bugzilla.globus.org/globus/show_bug.cgi?id=6558">enhancement 6558</a>.
</li>
@@ -88,7 +88,7 @@
</p>
<p>
For example, see the
- <a href="http://workspace.globus.org/clouds/nimbus.html">Nimbus cloud</a>
+ <a href="_SCIENCECLOUDS_WEBSITE/clouds/nimbus.html">Nimbus cloud</a>
docs for running EC2 clients.
</p>
<p>
View
14 docs/src/features.html
@@ -67,7 +67,7 @@
<p>
The workspace service is an implementation of a strong "pure Java"
- internal interface (see <a href="faq.html#rm-api">What is the RM
+ internal interface (see <a href="_NIMBUS_WEBSITE/faq/#rm-api">What is the RM
API</a>?) which allows multiple remote protocols to be supported as
well as differing underlying manager implementations.
</p>
@@ -140,7 +140,7 @@
<p>
Support for auto-configuration of these clusters (see the cloud
- <a href="/clouds/clusters.html">clusters</a> page).
+ <a href="clouds/clusters.html">clusters</a> page).
</p>
</li>
@@ -188,7 +188,7 @@
is provided to make adding and removing cloud users simple. This
includes adjusting authorization policies and creating repository
directories with sample images, etc. This is intended for the
- "<a href="faq.html#defcloudkit">cloudkit</a>" setup and requires
+ "<a href="_NIMBUS_WEBSITE/faq/#defcloudkit">cloudkit</a>" setup and requires
the group management authorization described in the
<a href="#ana">previous section</a>.
</p>
@@ -220,7 +220,7 @@
<h4>One-click clusters (contextualization) _NAMELINK(ctx)</h4>
<p>
- See the cloud <a href="/clouds/clusters.html">clusters</a> page for
+ See the cloud <a href="clouds/clusters.html">clusters</a> page for
how auto-configuration of entire clusters (contextualization)
is supported by the science clouds. This allows the cloud client
to launch "one-click" clusters whose nodes securely configure
@@ -253,7 +253,7 @@
<p>
See the <a href="/clouds/">clouds page</a> as well as a
behind-the-scenes overview of the service
- <a href="_WORKSP_CURRENT_VM_VERSION/doc/cloud.html">cloud
+ <a href="doc/cloud.html">cloud
configuration</a>.
</p>
</li>
@@ -380,8 +380,8 @@
<p>
For more details, see the current release's
- <a href="_WORKSP_CURRENT_VM_VERSION/index.html">documentation</a> and
- the Nimbus <a href="faq.html">FAQ</a>.
+ <a href="index.html">documentation</a> and
+ the Nimbus <a href="_NIMBUS_WEBSITE/faq/">FAQ</a>.
</p>
<!-- This page intentionally left blank -->
View
BIN  docs/src/img/warning.gif
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
View
2  docs/src/index.html
@@ -89,7 +89,7 @@
Chased by dragons?
</p>
<p>
- See the <a href="_NIMBUS_WEBSITE/contact.html">Getting Help</a> page
+ See the <a href="_NIMBUS_WEBSITE/contact/">Getting Help</a> page
to shoot you some troubles. It's a gentleman's sport.
</p>
</div>
View
4 docs/src/interfaces/deployment.html
@@ -36,7 +36,7 @@
<p>
Because a workspace can be deployed in the context of many different
resource allocations (for discussion, see the
- <a href="/papers/VW_ScientificProgrammingJournal06.pdf">Virtual
+ <a href="_NIMBUS_WEBSITE/files/VW_ScientificProgrammingJournal06.pdf">Virtual
Workspaces</a> paper, section 4),
a separate <a href="../examples/compact/negotiable.xsd">schema</a> is
used to both request and describe deployment-only parameters.
@@ -263,7 +263,7 @@
<p>
For a full discussion of the WorkspaceDeployment and its role in the
overall workspace architecture, see the
- <a href="/papers/VW_ScientificProgrammingJournal06.pdf">Virtual
+ <a href="_NIMBUS_WEBSITE/files/VW_ScientificProgrammingJournal06.pdf">Virtual
Workspaces</a> paper, sections 4 and 5.
</p>
View
8 docs/src/plugins/index.html
@@ -25,13 +25,13 @@
</p>
<p>
- The <a href="../../faq.html">Nimbus FAQ</a> is good prerequisite reading
+ The <a href="_NIMBUS_WEBSITE/faq/">Nimbus FAQ</a> is good prerequisite reading
for this section, especially
- <a href="../../faq.html#nimbus-main-components">this section</a>.
+ <a href="_NIMBUS_WEBSITE/faq/#nimbus-main-components">this section</a>.
</p>
<p>
- Each <a href="../../faq.html#nimbus-main-components">Nimbus component</a>
+ Each <a href="_NIMBUS_WEBSITE/faq/#nimbus-main-components">Nimbus component</a>
can be sanely replaced by something that implements the same interface
or protocol.
@@ -67,7 +67,7 @@
</p>
<p>
- The <a href="../../faq.html#workspace-service">workspace service</a> has
+ The <a href="_NIMBUS_WEBSITE/faq/#workspace-service">workspace service</a> has
the most of these internal "plug points" (around 50, all told, although
it would be esoteric to replace some of them).
</p>
View
2  docs/src/plugins/service-accounting.html
@@ -20,7 +20,7 @@
<h4>* Summary:</h4>
<p>
An internal module of the
- <a href="../../faq.html#workspace-service">workspace service</a>
+ <a href="_NIMBUS_WEBSITE/faq/#workspace-service">workspace service</a>
that governs if and how usage information is recorded. It is actually
split into two logically separate activities.
</p>
View
2  docs/src/plugins/service-authz.html
@@ -20,7 +20,7 @@
<h4>* Summary:</h4>
<p>
The <a href="service-reqintake.html">Creation</a> process in the
- <a href="../../faq.html#workspace-service">workspace service</a>
+ <a href="_NIMBUS_WEBSITE/faq/#workspace-service">workspace service</a>
makes an optional callout to authorize the request further than the basics.
</p>
<p>
View
2  docs/src/plugins/service-network.html
@@ -20,7 +20,7 @@
<h4>* Summary:</h4>
<p>
An internal module of the
- <a href="../../faq.html#workspace-service">workspace service</a>
+ <a href="_NIMBUS_WEBSITE/faq/#workspace-service">workspace service</a>
that governs what IP addresses (and associated settings) are assigned
to incoming requests.
</p>
View
2  docs/src/plugins/service-prop.html
@@ -20,7 +20,7 @@
<h4>* Summary:</h4>
<p>
An internal module of the
- <a href="../../faq.html#workspace-service">workspace service</a>
+ <a href="_NIMBUS_WEBSITE/faq/#workspace-service">workspace service</a>
that governs what mechanisms are used when file propagation (and
unpropagation) to and from the VMM nodes is triggered.
</p>
View
2  docs/src/plugins/service-reqintake.html
@@ -20,7 +20,7 @@
<h4>* Summary:</h4>
<p>
A set of internal modules of the
- <a href="../../faq.html#workspace-service">workspace service</a>
+ <a href="_NIMBUS_WEBSITE/faq/#workspace-service">workspace service</a>
that govern how creation requests are handled. You can alter the
logic entirely with the <b>Creation</b> interface. Or you can perform
surgery and just change a small part of the creation process with one of
View
2  docs/src/plugins/service-sched.html
@@ -20,7 +20,7 @@
<h4>* Summary:</h4>
<p>
An internal module of the
- <a href="../../faq.html#workspace-service">workspace service</a>
+ <a href="_NIMBUS_WEBSITE/faq/#workspace-service">workspace service</a>
that governs <i>when</i> and <i>where</i> the VMs will run.
</p>
View
2  docs/src/plugins/service-tasks.html
@@ -20,7 +20,7 @@
<h4>* Summary:</h4>
<p>
There is an internal module of the
- <a href="../../faq.html#workspace-service">workspace service</a>
+ <a href="_NIMBUS_WEBSITE/faq/#workspace-service">workspace service</a>
that governs what tasks are launched when a particular action is
required. For example, when the service engine determines that a
"Start" action is required, a particular implementation of a
View
2  docs/src/summary.html
@@ -14,7 +14,7 @@
<p>
If you want to learn more about the concepts underlying Nimbus, see the
- <a href="_NIMBUS_WEBSITE/faq.html">FAQ</a> and <a href="_NIMBUS_WEBSITE/papers/">Publications</a>
+ <a href="_NIMBUS_WEBSITE/faq/">FAQ</a> and <a href="_NIMBUS_WEBSITE/papers/">Publications</a>
section.
</p>
Please sign in to comment.
Something went wrong with that request. Please try again.