> When OpenSAF powers up at the first time, it reads its configuration from > XML files: NCSSystemBOM.xml, AppConfig.xml etc.. Now we hope to add part of > OpenSAF's configuration from another source, such as from IMMS service. Most > of the configuration is still from XML files. But another part of > configuration should be read from IMMS service, and then be stored in > OpenSAF just like from XML files. Let's assume that we know how to read > configuration from IMMS. The problem is how to store it into OpenSAF (when > OpenSAF powers up at the first time)? > 1. May be we can use SNMP protocol to set MIB values. But it seems that > OpenSAF has not fully powered up, SNMP interface does not work. Function as > "snmpset" won't work, is this right? > 2. So we have to add some codes in OpenSAF source files (the less the > better). It seems that the procedure of parsing XML file is complex, and the > parsed configuration is stored into PSSv. So what is the good method to > store configuration from IMMS to PSSv (or MIB value)? Or what API functions > should be used? Or is there any documentation of such API functions? > 3. By the way, will OpenSAF support IMMS? Or when will it support IMMS ?
The easiest way to do it is to have a program that reads the values out of your IMM implementation and writes them to a BOM that OpenSAF understands. Then when OpenSAF has an IMM implementation you can throw that converter tool away and just go on using IMM. OpenSAF will have IMM. There is no official opensaf roadmap yet so there is no date that somebody could say "when". Probably late 2008 or early 2009 though. Chad _______________________________________________ Users mailing list [email protected] http://list.opensaf.org/maillist/listinfo/users
