-
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 28 days (the time period specified by
the administrator of this Tracker).
2010-01-06 02:20:11 UTC by sf-robot
-
Fixed in 2.3.3 and 2.4.
2010-01-06 02:12:13 UTC by wanghuaz
-
Fixed in 2.3.3 and 2.4.
2010-01-06 02:11:24 UTC by wanghuaz
-
Ok, now for the bad news: we don't have the ID manpower to maintain different versions of the docs for different releases of xcat. In fact, we have no ID headcount at all (talk to our managment team). The developers do all of their own documentation (which probably explains a few things). So we made the decision at the beginning of xcat that we would only maintain one copy of each doc and...
2010-01-05 18:21:17 UTC by bp-sawyers
-
I am adding to the documentation to check the Sensor and condition and response generated files to check for reliance on CSM code. Those Sensors, conditions and response either should be removed or the code will have to be ported to xCAT. I am also providing a list of the predefined sensors, conditions and responses that are already in xCAT and those should also not be migrated from CSM...
2010-01-05 15:44:41 UTC by lissav
-
Can we change the doc to not create NodeNameList at all by changing the example to say lsrsrc -i IBM.Sensor | grep -v NodeNameList > /tmp/xcat/IBM.Sensor.rdef as we did in the following creation of the condition and response. The script is owned by rsct and cannot be changed. From my testing all the commands are not going to exist on the xCAT MN ( they are in CSM), so we need to discuss...
2010-01-05 12:51:45 UTC by lissav
-
there might be two ways to solve this bug:
1. change the documents and add one remark to "change the NodeNameList to current xCAT MN
2. change the script which create the file and let the NodeNameList blank.
2010-01-05 07:44:00 UTC by caoli
-
In the 1.14Migrating the CSM Monitoring setup to xCAT part, we follow the steps to migrate the monitor from CSM to xCAT：
1. we create one IBM.Sensor.rdef file on CSM MS, the command is:
lsrsrc -i IBM.Sensor > /tmp/xcat/IBM.Sensor.rdef
the format like:
resource 6:
Name = "AIXSyslogSensor"
Command = "/opt/csm/csmbin/monaixsyslog"
UserName.
2010-01-05 04:06:29 UTC by caoli
-
A date would certainly help. But as time goes on, there will be docs for xCAT version 2.4, 2.5, 3.0, etc. Some of the newer docs may not be applicable to older versions which customers may have installed. How do you plan on handling that? I would hope the older versions stay around as long as the xCAT version is supported if not longer.
It's not too early to start thinking about...
2010-01-04 20:58:44 UTC by ranck
-
i'm concerned that over time, some developers will forget to change the revision # when they change a doc. Having a wrong revision # is worse than having no revision #.
I have a suggestion and a compromise.
Suggestion: always use the docs on the web (http://xcat.svn.sourceforge.net/viewvc/xcat/xcat-core/trunk/xCAT-client/share/doc/index.html) and then you will never have to wonder if you...
2010-01-04 20:48:24 UTC by bp-sawyers
