From: jparsons@sourceware.org <jparsons@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] conga/luci/docs user_manual.html
Date: 15 Jan 2007 20:03:46 -0000 [thread overview]
Message-ID: <20070115200346.10520.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: conga
Changes by: jparsons at sourceware.org 2007-01-15 20:03:45
Modified files:
luci/docs : user_manual.html
Log message:
final manual additions for bz201394
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/conga/luci/docs/user_manual.html.diff?cvsroot=cluster&r1=1.12&r2=1.13
--- conga/luci/docs/user_manual.html 2007/01/15 19:57:22 1.12
+++ conga/luci/docs/user_manual.html 2007/01/15 20:03:45 1.13
@@ -324,14 +324,29 @@
is on the node list page.
<h4>Add a Node</h4>
Below is a screenshot of the Add a Node page:
- <img src="./clus5.png"/><br/>
+ <img src="./addnode_11.png"/><br/>
<b>Figure #10: Add a Node Page</b>
<p/>
<p/>
The Add a Node page is similar in look and function to the Add a System
page available in the Homebase tab. The system hostname of IP Address is
entered in the appropriate field along with the password for the
- system. Multiple nodes may be added at once. When the submit button is
+ system. Multiple nodes may be added at once. The user is offered the
+ chance to verify the certificate for the new node to be added, just as
+ they were when adding a system on the home base tab.
+ <p/>
+ Two other options are available to the user when adding a node: They are
+ presented with a pair of radio buttons that allow for a choice of either
+ pulling the necessary packages from the configured Yum repository for
+ the system (The very latest packages are always selected with this option),
+ or packages already installed on the system are used. If any packages
+ are missing, an error message is returned and the node is not added.
+ <p/>
+ The other option available to the user is a checkbox for Shared Storage
+ support. Checking this box will install and initially configure the
+ CLVM (Clustered Logical Volume Management) packages and the GFS clustered file system packages. In a cluster environment, this box will almost always need to
+ be checked.
+ When the submit button is
clicked, the following takes place:
<ul>
<li>Contact is made with each future nodes ricci agent. If this contact fails
next reply other threads:[~2007-01-15 20:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 20:03 jparsons [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-25 19:27 [Cluster-devel] conga/luci/docs user_manual.html jparsons
2007-01-15 21:43 jparsons
2007-01-15 21:41 jparsons
2007-01-15 21:23 jparsons
2007-01-15 20:33 rmccabe
2007-01-15 20:26 rmccabe
2007-01-15 19:57 rmccabe
2007-01-15 19:46 jparsons
2007-01-15 16:00 jparsons
2006-10-10 18:31 rmccabe
2006-10-09 5:47 jparsons
2006-09-26 13:35 jparsons
2006-09-26 12:36 jparsons
2006-09-26 12:12 jparsons
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070115200346.10520.qmail@sourceware.org \
--to=jparsons@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).