Hi, this email is related to the multiple adapters definition in SIS.
On http://home.arcor.de/efocht/oscar/ you will find a set of small tools building a SIS reload facility. It is just a start right now and offers the tools to load changes done to the SIS database from the cluster clients ("pull" the changes, so in line with the NEST ideas and very scalable, I hope). These tools could eliminate the need for directly accessing the ODA database from the client nodes, but I'm not insisting on this... The simplest example: you want to change the /etc/fstab file of each node. The correct way in OSCAR would be to : - modify the disktable file - insert the disktable file into the oscar image(s) - re-create the autoinstallscript - re-install the nodes (aaargh!!) This is bad if you simply wanted to add some additional NFS mounts and need to stop production. Of course you can edit an fstab copy, put it into the image and cpush it to all nodes. But then your autoinstallscript.conf in the image will be wrong. And the script, too. The command "sis_reload fstab" executed on a client node will query the master node for the current version of the fstab as freshly converted from the etc/systemimager/autoinstallscript.conf file. If this is different from the local version, the local version will be replaced. The command "sis_reload network" will do a similar thing with the network setup. It will query the master node for the current systemconfigurator input (as available in the autoinstall-script, but fresh). Then it will run systemconfigurator to reconfigure the network according to these settings. It is especially usefull when having defined multiple interfaces on the cluster nodes with the mksiadapter tool. These two commands could go into the autoinstall-script and make a regeneration of the script (when the SIS database changed) obsolete. Following components belong together: sisqd: the SIS query daemon. Needs to run on the master. Listens on port 10234 (changeable from the command line) for requests from the cluster nodes. It only replies to nodes which are defined in the SIS database. Logging goes to syslog. sisqc: the SIS query client. Called on the cluster client nodes. sis_reload: the reload script. Uses sisqc to talk to the master. Called on the client nodes for refreshing /etc/fstab or the network configuration. Any comments and improvement ideas are welcome... Best regards, Erich PS: sis_reload network will also change the hostname and throw away the domainname. You can change this, it's a script. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Sisuite-devel mailing list Sisuite-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-devel
