Commit ba5fef54 authored by Robert Ricci's avatar Robert Ricci

Merge branch 'chef-tutorial'

parents 7deca689 6bcce376
Pipeline #508 passed with stage
This diff is collapsed.
......@@ -52,4 +52,5 @@ Take a look at the @seclink["status-notes"]{status notes}, and then
@include-section["hardware.scrbl"]
@include-section["planned.scrbl"]
@include-section["cloudlab-tutorial.scrbl"]
@include-section["cloudlab-chef-tutorial.scrbl"]
@include-section["getting-help.scrbl"]
......@@ -39,7 +39,7 @@ This tutorial assumes that:
@include-section["tutorial-login-common.scrbl"]
@section[#:tag "tutorial-body"]{Building Your Own OpenStack Cloud}
@section[#:tag "openstack-tutorial-body"]{Building Your Own OpenStack Cloud}
Once you have logged in to @(tb), you will ``instantiate'' a @seclink["profiles"]{``profile''}
to create an @seclink["experiments"]{experiment}. (An experiment in @(tb) is similar
......@@ -236,7 +236,7 @@ freedom and control in the private experiment network, and sets up a clean
environment for @seclink["repeatable-research"]{repeatable research}.
@subsection[#:tag "tutorial-list-view"]{List View}
@subsection[#:tag "openstack-tutorial-list-view"]{List View}
The list view tab shows similar information to the topology view, but in a
different format. It shows the identities of the nodes you have been
......@@ -266,7 +266,7 @@ directly from this manifest; it is parsed and laid out in-browser.}
@screenshot["tutorial/experiment-manifest.png"]
@subsection[#:tag "tutorial-actions"]{Actions}
@subsection[#:tag "openstack-tutorial-actions"]{Actions}
In both the topology and list views, you have access to several actions that
you may take on individual nodes. In the topology view, click on the node to
......@@ -275,13 +275,13 @@ access this menu; in the list view, it is accessed through the icon in the
and re-loading it with a fresh copy of its disk image (destroying all data on
the node). While nodes are in the process of rebooting or re-imaging, they
will turn yellow in the topology view. When they have completed, they will
become green again. The @seclink["tutorial-web-shell"]{shell} and
@seclink["tutorial-console"]{console} actions are described in more detail
become green again. The @seclink["openstack-tutorial-web-shell"]{shell} and
@seclink["openstack-tutorial-console"]{console} actions are described in more detail
below.
@screenshot["tutorial/experiment-actions.png"]
@subsection[#:tag "tutorial-web-shell"]{Web-based Shell}
@subsection[#:tag "openstack-tutorial-web-shell"]{Web-based Shell}
@(tb) provides a browser-based shell for logging into your nodes, which is
accessed through the action menu described above. While this shell is
......@@ -305,7 +305,7 @@ Two things of note:
@screenshot["tutorial/experiment-shell.png"]
@subsection[#:tag "tutorial-console"]{Serial Console}
@subsection[#:tag "openstack-tutorial-console"]{Serial Console}
@(tb) provides serial console access for all nodes, which can be used
in the event that normal IP or @(ssh) access gets intentionally or
......@@ -325,7 +325,7 @@ the access menu, and the same caveats listed above apply as well. In addition:
@screenshot["tutorial/experiment-console.png"]
@section[#:tag "tutorial-instances"]{Bringing up Instances in OpenStack}
@section[#:tag "openstack-tutorial-instances"]{Bringing up Instances in OpenStack}
Now that you have your own copy of OpenStack running, you can use it just like
you would any other OpenStack cloud, with the important property that you have
......@@ -506,7 +506,7 @@ modify or replace any piece of your own copy of OpenStack.
If you want to watch what's going on with your copy of OpenStack, you can use
@(ssh) to log into any of the hosts as described above in the
@secref["tutorial-list-view"] or @secref["tutorial-web-shell"] sections. Don't
@secref["openstack-tutorial-list-view"] or @secref["openstack-tutorial-web-shell"] sections. Don't
be shy about viewing or modifying things; no one else is using your cloud,
and if you break this one, you can easily get another.
......@@ -594,14 +594,14 @@ watch it through the serial console.
@itemlist[#:style 'ordered
@instructionstep["Open the serial console for cp1"]{
On your experiment's @(tb) status page, use the action menu as
described in @secref["tutorial-actions"] to launch the console.
described in @secref["openstack-tutorial-actions"] to launch the console.
Remember that you may have to click to focus the console window and hit
enter a few times to see activity on the console.
}
@instructionstep["Reboot the node"]{
On your experiment's @(tb) status page, use the action menu as
described in @secref["tutorial-actions"] to reboot @tt{cp1}. Note
described in @secref["openstack-tutorial-actions"] to reboot @tt{cp1}. Note
that in the topology display, the box around @tt{cp1} will turn
yellow while it is rebooting, then green again when it has booted.
}
......
......@@ -15,8 +15,8 @@ an account at one of its federated facilities, like
If you have signed up for an account at the @(tb) website, simply
open @url[apt-base-url]in your browser, click the ``Log In'' button,
enter your username and password, and @bold{@seclink["tutorial-body"]{skip to
the next part of the tutorial}}.
enter your username and password, and @bold{skip to
the next part of the tutorial}.
@screenshot["tutorial/front-page.png"]
......
Markdown is supported
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