Hi,
We finally merged the db-devel branch to trunk.
I can not tell that the codes on db-devel branch
are perfectly working for all the proposed oscar
database schema and installation but that they
work in the exactly same way the current oscar does.
But still I need to do some works for the database stuff.
1) Hardware information(cpu,lam,swap, cpu_num,
and units)of nodes are missing like the current "Nodes" table.
FYI, this is the new "Nodes" table.
mysql> desc Nodes;
+------------+--------------+------+-----+---------+----------------+
| Field | Type | Null | Key | Default | Extra |
+------------+--------------+------+-----+---------+----------------+
| cluster_id | int(11) | YES | | NULL | |
| cpu_num | int(11) | YES | | NULL | |
| cpu_speed | varchar(100) | YES | | NULL | |
| dns_domain | varchar(100) | YES | | NULL | |
| fqdn | varchar(100) | YES | | NULL | |
| group_id | int(11) | YES | | NULL | |
| hostname | varchar(100) | YES | | NULL | |
| id | int(11) | | PRI | NULL | auto_increment |
| image_id | int(11) | YES | | NULL | |
| installer | varchar(100) | YES | | NULL | |
| name | varchar(100) | YES | MUL | NULL | |
| ram | varchar(100) | YES | | NULL | |
| swap | varchar(100) | YES | | NULL | |
| units | varchar(100) | YES | | NULL | |
| virtual | varchar(100) | YES | | NULL | |
+------------+--------------+------+-----+---------+----------------+
15 rows in set (0.00 sec)
2) Group_Nodes table is not fully used for client nodes.
(Current DB has not used this feature at all).
3) lib/OSCAR/PackageInUn.pm is not converted.
(This is optional of the oscar installation. I can fix it in
one or 2 hrs).
4) I will put some more readable comment to the codes that I added
or edited.
5) I will prepare for a document of OSCAR Databa API (ODA) to have
all OSCAR developer have better understanding of ODA.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
The new config.xml for all the oscar packages made
some changes on their format.
- Use <binary-package-list>. No <rpmlist>.
- Within <binary-package-list> and </binary-package-list>
a. Define the filter according to the corresponding distro.
b. Use <pkg> tag for the related package instead of <rpm>.
For example,
</binary-package-list>
<filter>
<distribution>
<name>redhat</name>
<version>el4</version>
</distribution>
</filter>
<pkg>libaio</pkg>
<pkg>libaio-devel</pkg>
<pkg>lam-oscar</pkg>
<pkg>lam-oscar-modulefile</pkg>
<pkg>lam-switcher-modulefile</pkg>
</binary-package-list>
- <url> --> <uri>
- Use <package-specific-attributes> tag to display
the specific attributes of the given package.
For example, lam and mpich need to handle switcher
So, they use the above tag like this.
<package-specific-attributes>
<switcher>
<tag>mpi</tag>
<name>lam-7.0.6</name>
</switcher>
</package-specific-attributes>
For the complete example, I would like to refer to
$OSCAR_HOME/packages/lam/config.xml
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Finally, I would've merged the db-devel branch to trunk
after I fix the above five missing parts. But I think
it is more important to merge it to trunk so that
everyone can use the new DB schema ASAP.
Regards,
- DongInn
--------------------------------------------------------
OSL System administrator
[EMAIL PROTECTED]
Indiana University
Bloomington, IN
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Oscar-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oscar-devel
