Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.eso.org/projects/dfs/dfs-shared/NGAS-3_1_1.txt Дата изменения: Mon Jun 18 16:27:38 2007 Дата индексирования: Sat Oct 17 08:32:04 2009 Кодировка:

==> DFS COMPONENT NAME: NGAS

==> DFS COMPONENT RELEASE NUMBER: 3.1.1

==> DFS RELEASE TYPE: General patch.

==> DELIVERED BY: JKN ON: 2007-06-18

==> MAIN REASON OF THE DELIVERY:
Fixes the following issues:

- Improve the interfacing to the 3ware controller.
- Provide RESTORE Command to be able to put the SA->PA Restoring.
- Fix the ngamsServer init script.
- Remove compression ratio calculation from NGAS WEB pages (disk status) +
add operators in table.

==> DEADLINE FOR DELIVERY OUTSIDE DFS GROUP:
2007-06-18

==> CONFIGURATION REQUIRED FOR INTEGRATION TESTS:
See the NGAS documentation ...

==> LIST AND LOCATION OF SPECIFIC TEST DATA TO BE RETRIEVED AND USED FOR
INTEGRATION TESTS:
None.

==> POINTS ALREADY CHECKED DURING UNIT TESTS:
NG/AMS: - Functional Tests (automatic tests).
NGAS Utils: - No tests done.
Other modules: - No specific testing done.

==> POINTS TO BE CAREFULLY CHECKED DURING INTEGRATION TESTS:
All features according to Test Plan agreed upon.

==> COMPLETE LIST OF ACTION ITEMS/PROBLEMS REPORTS ADDRESSED BY THIS RELEASE:
The action remedy tickets implemented in connection with this patch
are:

=Interfacing to 3ware Controller(*):
DFS03070: Disks R and M have changed names? can not be seen on the webpage.
DFS03101: ngas website not reflecting actual contents of ngas disks
DFS03267: Disk Info not handled properly.
DFS03398: NGAS disk problem.
DFS03417: URGENT!!! Inconsistencies in the db and on the disks.....
DFS03418: #Label outside NGAS disks are not the same that NGAS recognize
DFS03859: NGAS server in wgsnau2 does not mount some disks.
DFS03948: NGAS disk not recognised by wgsnau1.
DFS03958: NGAS disk not recognised.
DFS04021: Disk recognition errors in wgsahu.

=RESTORE Command:
DFS03841: Add REARCHIVE Command (actually RESTORE Command).

=NG/AMS Server Init Script:
DFS03249: ngamsServer init script not behaving correctly.

=NGAS User Interfaces:
DFS03901: Compression ratio removal from Zope webpage.
DFS03411: Please add our new coleague to the Zope env.
DFS03770: Please add our new coleagues....


-----
*: Additional information to improvements implemented in the 3ware
interfacing:

=== The mapping from port to slot ID + device name should be done as follows:

- = + 1 (this is the way it is done
now).
- -> (e.g.: u ->
/dev/sd1, e.g.
u1 -> /dev/sdc1 (idx offset = "b").


=== If there are entries in the 3ware output where the "Unit" field is "-" and the "Status" is "OK", this is logged and that entry skipped


=== Rather than checking for "NOT-PRESENT" before accepting a line representing a port from the output, it should be checked explicitly if the status is "OK"


=== Support explicitly "SINGLE" disk (now it is supported by 'coincidence').


=== This kind of error messages:

2007-06-12T12:20:29.605:ngamsServer:init:1820:7947:MainThread:ERROR> NGAMS_ER_INIT_SERVER:3009:ERROR: Problems occurred initializing NG/AMS Server. Error message: -

- seems to be produced by this statement:

if ((diskInfo[1] != "NOT-PRESENT") and
(unitTypeDic[diskInfo[2]] == "JBOD")):
...

- whereby the line parsed is:

p1 NOT-PRESENT - - - -

- and the unit with ID "-" is not defined in the "unitTypeDic". In fact the parsing is interrupted. On wg0ngas11 only the first condition in the if-statement is executed (and fails) such that that the second, critical part does not give problems. It would be better though, to be more explicit here.


EOF