Menu
▾
▴
Re: [xcat-user] contribution : cfm like
|
From: Lissa V. <li...@us...> - 2010-03-31 11:16:58
|
We have provide a cfm2xcat migration script that will convert you entire CFM setup on CSM, to files that are usable by the xdcp -F <sysclist> feature. Did you see all the options available for syncing files in the SyncList HowTo : http://xcat.svn.sourceforge.net/viewvc/xcat/xcat-core/trunk/xCAT-client/share/doc/xCAT2SyncFilesHowTo.pdf I would like to understand the features that are missing in xdcp that you need? See what the cfm2xcat script does, it does handle somethings like .group extentions and it will copy the .pre and .post scripts to the nodes, although it does not do all the extra work that cfmupdate did to automatically run them. I would be interested in your design there, because we required a CFM client on the nodes to handle this function in CSM, and we cannot put xCAT code on the nodes. I think the experience you have doing this and analyzing our current file sync support is invaluable to us, but we really need to build on our current design so if you would like to open a Feature to tell us what we are missing, it would really help. Using the /cfmroot directory for syncfiles as in CSM, does not fit into the current design for syncing files to the node during install or running updatenode. We had hoped the migration script would help to ease the move of the CSM CFM users data to the equivalent xCAT data paths. As far as integrating it with xCAT, it could be put with our other shared tools in /opt/xcat/share/xcat/tools. Lissa K. Valletta 414/3-8 Poughkeepsie, NY 12601 (tie 293) 433-3102 From: Antoine Migeon <ant...@u-...> To: xca...@li... Date: 03/31/2010 06:45 AM Subject: [xcat-user] contribution : cfm like Hello, Because I need to migrate from CSM to xCat, and because xdcp do not have enough features, I wrote a Perl script that has the same functionality as "cfmupdatenode" (IBM CSM). Here are the features : Synchronise and copy files from /xcfmroot to nodes. Preserve permissions, owners and mtime for files and directories. Symbolic links are not transferred, the target link will be transferred. Support pre and post execution scripts (suffixed .pre et .post). Support for nodes suffixes, like ._node or ._group for files and directories. By default, compares files and synchronize only what is necessary. Work in parallel. -a --all For all nodes -b --backup Preserve existing configuration file (on nodes) as filename.OLD -d --dummy Create scripts but do nothing in nodes -f --filename <file> Only update the given filename(s), separated by comma -F --force Force synchronization without verification -M --max-child-process <integer> Set the number of nodes to update concurrently, default=32 -n --node_list <node> For specified nodes (format : see noderange(3)) -q --query Only check if files need to be synchronized -v --verbose Like xdcp, it use rsync for final transfer. At this time, it does not support diskless or rootimg path, and not support SN. My script work with xCat, use several modules (noderange), but it is not really integrated and does not respect the xCat Developer Guide (no client/server model for example). Are you interested in this script ? Is there a chance that my script will be integrated in xCat project ? If yes, I can work and adapt my script to xCat Developper Guide. Antoine -- Antoine Migeon Université de Bourgogne Centre de Ressources Informatiques - Centre de Calcul tel : 03 80 39 52 70 Site du CCUB : http://www.u-bourgogne.fr/cri-ccub ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ xCAT-user mailing list xCA...@li... https://lists.sourceforge.net/lists/listinfo/xcat-user |