Skip to content
GitLab
Menu
Projects
Groups
Snippets
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
emulab
emulab-devel
Commits
ef79aa94
Commit
ef79aa94
authored
Nov 08, 2004
by
Robert Ricci
Browse files
Change the instructions for adding ops to the database, to use the
new newclient/newnode code that can handle ops.
parent
1c722709
Changes
1
Hide whitespace changes
Inline
Side-by-side
doc/UPDATING
View file @
ef79aa94
...
...
@@ -226,13 +226,14 @@ earliest time one of the steps needs to occur.
* Create the emulab-ops/opsnode experiment. Do this the same way
that hwdown is created in setup-db.txt.
* Create a node_types entry for ops. This is mostly just a stub
entry so that tmcd will recognize it and so that other parts of
the system are happy. Be sure that you get the interface correct,
and set the Default OSID to emulab-ops-OPSNODE-BSD. The type is
ops and the class is misc.
* Create the ops node nodes table entry ...
* Make sure your source tree on ops is updated. Then, from that source
tree, run 'install/newclient -o'. (Note: You will probably have to
turn on the 'executable bit' for this script before running it, with
'chmod a+x install/newclient'.) This will allow ops to check into the
testbed.
* On boss, run: 'wap /usr/testbed/libexec/newnode ops' to actually add
ops to the database.
* Place the ops node into the above experiment:
...
...
Write
Preview
Supports
Markdown
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