Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
T
testbed-manual
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
1
Issues
1
List
Boards
Labels
Service Desk
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Incidents
Environments
Packages & Registries
Packages & Registries
Container Registry
Analytics
Analytics
CI / CD
Repository
Value Stream
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
emulab
testbed-manual
Commits
98a6613b
Commit
98a6613b
authored
Mar 06, 2016
by
Robert Ricci
Browse files
Options
Browse Files
Download
Plain Diff
Merge remote-tracking branch 'origin/chef-tutorial'
parents
f916ca91
7b804861
Pipeline
#521
passed with stage
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
11 additions
and
6 deletions
+11
-6
cloudlab-chef-tutorial.scrbl
cloudlab-chef-tutorial.scrbl
+11
-6
No files found.
cloudlab-chef-tutorial.scrbl
View file @
98a6613b
...
...
@@ -35,7 +35,7 @@ In the process of taking this tutorial, you will learn to:
This
tutorial
will
demonstrate
how
experiments
can
be
managed
on
@
(
tb
)
,
as
well
as
show
how
experiment
resources
can
be
administered
using
Chef
.
By
following
the
instructions
provided
below
,
you
will
learn
how
to
take
advatage
of
the
powerful
features
of
Chef
By
following
the
instructions
provided
below
,
you
will
learn
how
to
take
adva
n
tage
of
the
powerful
features
of
Chef
for
configuring
multi-node
software
environments
.
The
exercises
included
in
this
tutorial
are
built
around
simple
but
realistic
configurations
.
In
the
process
of
recreating
these
configurations
on
nodes
running
...
...
@@ -357,7 +357,7 @@ components that we don't use in this tutorial, it is worth noting the following:
@item
{
@bold
{
Recipes
}
,
shown
next
to
cookbooks
on
the
workstation
,
are
the
"building blocks"
from
which
cookbooks
are
assembled
.
Recipes
can
be
viewed
as
individual
scripts
accomplishing
specific
fine-grained
tasks
,
such
as
create
a
user
,
install
a
package
,
clone
a
re
s
pository
,
configure
a
network
interface
,
etc
.
fine-grained
tasks
,
such
as
create
a
user
,
install
a
package
,
clone
a
repository
,
configure
a
network
interface
,
etc
.
Cookbooks
,
which
include
one
or
more
recipes
,
are
responsible
for
"bigger"
tasks:
install
and
configure
a
database
,
install
and
run
a
web
server
,
and
so
on
.
}
...
...
@@ -715,7 +715,7 @@ executed as @italic{root}). Run the commands described below in that shell.
@itemlist
[
#:style
'ordered
@instructionstep
[
"Add
a
role
to
the
head
's
run
list"
]{
Issue
s
the
command
in
bold
(
the
rest
is
the
expected
output
)
:
Issue
the
command
in
bold
(
the
rest
is
the
expected
output
)
:
@verbatim
{
@bold
{
knife
node
run_list
add
head
"role[apache2]"
}
head:
...
...
@@ -725,7 +725,7 @@ executed as @italic{root}). Run the commands described below in that shell.
}
}
@instructionstep
[
"Add
two
roles
to
the
node-0
's
run
list"
]{
Run
the
two
@code
{
knife
}
commands
listed
below
to
assign
two
roles
to
@tt
{
node-0
}
:
Run
the
two
@code
{
knife
}
commands
listed
below
(
also
on
@tt
{
head
})
in
order
to
assign
two
roles
to
@tt
{
node-0
}
:
@verbatim
{
@bold
{
knife
node
run_list
add
node-0
"role[apache2]"
}
run_list:
...
...
@@ -788,6 +788,11 @@ executed as @italic{root}). Run the commands described below in that shell.
of
replacing
@code
{
pdsh
}
,
the
Parallel
Distributed
Shell
utility
,
that
is
often
used
on
computing
clusters
.
The
output
that
is
similar
to
the
one
above
indicates
that
both
@code
{
apache2
}
web
servers
are
running
.
The
command
that
you
have
just
issued
uses
@code
{
netstat
}
,
a
command-line
tool
that
displays
network
connections
,
routing
tables
,
interface
statistics
,
etc
.
Using
@code
{
knife
}
,
you
have
run
@code
{
netstat
}
in
combination
with
a
Linux
pipe
and
a
@code
{
grep
}
command
for
filtering
output
and
displaying
the
information
only
on
the
port
@code
{
8080
}
.
}
@instructionstep
[
"Check
benchmarking
results
on
node-0"
]{
...
...
@@ -825,7 +830,7 @@ executed as @italic{root}). Run the commands described below in that shell.
for
one
of
its
attributes
.
In
the
console
,
click
on
the
Policy
tab
at
the
top
of
the
page
,
choose
`
`Roles
''
in
the
panel
on
the
left
,
and
select
`
`apachebench
''
in
the
displayed
list
o
r
roles
.
and
select
`
`apachebench
''
in
the
displayed
list
o
f
roles
.
Select
the
Attributes
tab
in
the
middle
of
the
page
.
At
the
bottom
of
the
page
,
you
should
now
see
a
panel
called
`
`Override
Attributes
''.
Click
the
`
`Edit
''
button
inside
that
panel:
...
...
@@ -915,7 +920,7 @@ are available for many common administrative needs. You can refer to the
@link
[
"https://docs
.
chef
.
io/resources
.
html#resources"
]{
list
of
supported
Chef
resources
}
and
see
examples
of
how
they
can
be
used
.
Another
item
that
is
worth
mentioning
i
n
i
s
the
Another
item
that
is
worth
mentioning
is
the
`
`@code
{
ignore_failure
true
}
''
attribute
used
in
some
of
the
resources
.
It
allows
the
recipe
to
continue
execution
even
when
something
does
not
go
as
expected
(
shell
command
fail
,
necessary
files
do
not
exist
,
etc
.
)
.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment