I worked with Linux RAC configuration, used Oracle CRSS to configure Oracle Application Server high available configuration, and as I am reading, Sun Cluster Software is much the same... We have several distinct systems (cluster node), which are configured separately and only different services migrate between these nodes... So, as I understand, when I want to install new version of package A in cluster, I have to install it on each system (e.g., having N nodes in a cluster I have to install package A N times), configure it as cluster service (N times). When I change, e.g. pam.conf, I have to change it N times and so on... And there is no way to use, e.g., the following layout: /global_root - / of each node /custom/<mac-0>/etc/hostname.bnx0 - to override /etc/hostname.bnx0 of node with mac mac-0 /custom/<mac-1>/etc/project - to override /etc/project of node with mac mac-1 /custom/<mac-2>/etc/svc/repository.db - to override /etc/svc/repository.db of node with mac mac-2
So, to install package, I could install it in /global_root, make some alterations of /costom/*/etc files, maybe start service on each node and it would be ready... This configuration would allow to maintain several identical nodes, maybe apply patches only to global_root, - e.g., create new boot environment on base of /global_root, patch it and sequentially to reboot each node to this boot environment... -- This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
