Hi, Comments inline:
----- [email protected] wrote: > Hi, > > a (obviously understood less than I thought ) +b. > > I understood that the PLM is able to identify the managed Hardware > entities and monitor their state via the HPI, alongside with changing > their admin state. It is worth noting that PLM also enables you to perform the admin operations as listed in the section 5.4 of the PLM spec. The SAF PLM framework enables these admin operations carried out in a coordinated manner (across different layers i.e. HPI->OS->middleware->application) by involving CLM, AMF and the applications themselves via the track callbacks. > But somehow I thought that I will be able to control the > functionality of the Hardware using the PLM by propagating > configuration commands via the Broker. > > But the HPI itself is able to more than just identify and report the > status of the controlled HW. > It is also able to configure the HW as I intend. Am I right? HPI indeed defines interfaces for configuration(generalized) of the HW and these interfaces are on the style of IPMI. So, it can be said that - generally on systems that have IPMI support it would be straightforward to map (to the HPI model) the configuration commands. In your case, it appears that you want to perform some configuration operations specific to your hardware logic. You might be requiring to setup one of those plugins(ipmi, snmp_bc, soap, etc) suited for your hardware. The broker/application would have to implement the logic for your configuration commands. The broker would inturn then call corresponding HPI APIs (as defined in SaHpi.h). If there are no equivalent HPI API, then obviously your 'broker/application' has to implement the logic for your proprietary admin or configuration commands. > > I wrote an implementer function that Upon configuring CCbs via Immcfg > is able to configure My Hw through my callbacks. > Is it possible to do so via the HPI? Yes, this seems to be the right approach atleast to start with! i.e. Your Broker will process the CCB callbacks and invoke corresponding HPI API. Cheers, Mathi. > > > Thanks a lot, > Idan > > > Idan Migemi > Embedded Software Team Leader > > PTT - Embedded Software > Global Technology Division > > phone/fax: > +972.3.926.6112 > E-mail: > [email protected] > > www.ecitele.com > > > > > -----Original Message----- > From: Mathivanan Naickan Palanivelu [mailto:[email protected]] > > Sent: Thursday, October 22, 2015 6:31 PM > To: Idan Migemi; [email protected]; Jonas Arndt > ([email protected]) > Cc: Haymi Shalom > Subject: RE: [users] Hardware configuration using OpenSAF > > Hi, > > Ofcourse, OpenSAF cannot directly modify the board's configuration! > There appears to be a disconnect here. > > Here is one example of how one can integrate their hardware with > OpenSAF for HA! > http://webdefence.global.blackspider.com/urlwrap/?q=AXicJcq9DcIwEEDhW4FB_BMFgaFCQgJRpKSiOpKDOLJ9kW1isQcjMQPzEMFXPr3FHi4fgNcbILqnrq4yxUl6tK7lkCM72bKHvGkO58ex6KWpdQ2nDoNs7J283VFrMzn6bX3O41apUopMznaUeowkA2XFI4WENzXNlUVHnsXAAROuqpkwdWXM2sDfF2wrL0Y&Z > (a) Also, Have you been able to read SAForum PLM - Platform management > Interface specifications? > > (b) Having said that, your goal seems to be to write an application > that uses OpenSAF IMM to store that application's configuration. And > this application would then do things like > - create a pseudowire service > - invoking any functionality on the board > - change the board/functionality configuration Etc. In which case, yes > ofcourse this application has to become the Implementer and not PLM Is > this your goal? > > Could you confirm (a) and (b) above? > > Mathi. > > > -----Original Message----- > > From: Idan Migemi [mailto:[email protected]] > > Sent: Thursday, October 22, 2015 8:14 PM > > To: Mathivanan Naickan Palanivelu; > [email protected] > > Cc: Haymi Shalom > > Subject: RE: [users] Hardware configuration using OpenSAF > > > > Hi, > > > > Suppose I define my Broadcom card as an HE, I still can't understand > I > > could I invoke any functionality on the board and change it's > configuration. > > Say, create a pseudowire/service etc.... > > > > In addition I couldn't quite understand the sentence (from the > first > > response) : > > " Define the HE (Hardware entity) objects information based on the > > > HPI enums defined for your hardware." > > > > Your help is highly appreciated. > > > > Thanks In Advance, > > Idan > > > > Idan Migemi > > Embedded Software Team Leader > > > > PTT - Embedded Software > > Global Technology Division > > > > phone/fax: > > +972.3.926.6112 > > E-mail: > > [email protected] > > > > www.ecitele.com > > > > > > > > > > -----Original Message----- > > From: Mathivanan Naickan Palanivelu > [mailto:[email protected]] > > Sent: Thursday, October 22, 2015 3:36 PM > > To: Idan Migemi; [email protected] > > Cc: Haymi Shalom > > Subject: RE: [users] Hardware configuration using OpenSAF > > > > And in case you have already done these steps. > > Then please note that PLM will be the implementer of all > HE(Hardware > > entity) objects(typically the FRUs) that you modelled in OpenSAF. > > So, you just have to define those objects in OpenSAF imm.xml > > > > Once you do that and power on the hardware discovery(entity-type > > matching) and validation (FRU information) will be done by OpenSAF. > > Admin operations will have to be done through PLM admin operations > > (using OpenSAF 'immadm' command on PLM HE or EE objects). > > > > Let know if this is what you are tyring to do? > > > > Mathi. > > > > > -----Original Message----- > > > From: Mathivanan Naickan Palanivelu > > > Sent: Thursday, October 22, 2015 5:12 PM > > > To: Idan Migemi; [email protected] > > > Cc: Haymi Shalom > > > Subject: Re: [users] Hardware configuration using OpenSAF > > > > > > Hi, > > > > > > Iam not sure if I understood your requirement correctly, but I > > > suggest you to do the following to integrate your hardware with > > > OpenSAF PLM (using HPI entity information). > > > > > > May be you want to try bringing up OpenSAF without PLM/HPI support > > > > on your board, but do the following if you want to enable PLM and > > > > HPI in OpenSAF > > > > > > 1) build opensaf as below (see also > osaf/services/saf/plmsv/README) > > > $ HPI_CFLAGS="-I/path/to/openhpi headers" > > > $ HPI_LIBS="-L/path/to/openhpi/lib -lopenhpimarshal -lopenhpiutils > - > > > lopenhpi" > > > > > > $ ./configure CFLAGS="<your options" --enable-ais-plm > --enable-hpi > > > --with- openhpi --with-hpi-interface=B03 $ make rpm > > > > > > 2) install opensaf rpms (and hpi rpms ofcourse) > > > 3) Create an .xml file with objects defined for your hardware, say > > > > for > > > eg:- osaf_bcm_config.xml Define the HE (Hardware entity) objects > > > information based on the HPI enums defined for your hadware. > > > You can refer to > > > osaf/services/saf/plmsv/config/plmsv_objects.xml.atca > > > OR > > > osaf/services/saf/plmsv/config/plmsv_objects.xml.hp > > > > > > These files contain examples of how to model(add objects) an ATCA > > > > chassis/blade OR a HP hardware/blade to the OpenSAF information > model. > > > You would similairly model your board as HE and EE in your > > > osaf_bcm_config.xml > > > > > > See also README in osaf/services/saf/plmsv/config directory. > > > > > > 4) Once you are done adding your objects in the > osaf_bcm_config.xml > > > $/usr/share/opensaf/immxml/immxml-merge /etc/opensaf/imm.xml > > > /my_dir/osaf_bcm_config.xml -o /etc/opensaf/new_imm.xml > > > > > > $cp /etc/opensaf/new_imm.xml /etc/opensaf/imm.xml > > > > > > 5) start opensaf on your board. > > > If there are problems in starting, > > > uncomment the following line in /etc/opensaf/plmd.conf, try > starting > > > opensaf again and share the /var/log/opensaf/osafplmd file and the > > > > syslog > > > > > > $immfind | grep -i plm > > > > > > > > > Thanks, > > > Mathi. > > > > > > > -----Original Message----- > > > > From: Idan Migemi [mailto:[email protected]] > > > > Sent: Thursday, October 22, 2015 4:04 PM > > > > To: [email protected] > > > > Cc: Haymi Shalom > > > > Subject: [users] Hardware configuration using OpenSAF > > > > > > > > Hi, > > > > > > > > We wish to integrate OpenSAF HA platform in our new line of > > > > Metro-Core products . > > > > Our first goal is to go through a basic Proof Of Concept based > on > > > > OpenSAF and a Broadcom evaluation board. > > > > > > > > Create a basic tunnel object via ImmCfg and download this > > > > configuration into the BCM board. > > > > > > > > We managed to define a class with the relevant configuration > > > > attributes, set the implementer as an external applier (a simple > > > > > main we created) and wish to use the HPI interface to configure > > > > > the > > actual HW. > > > > > > > > Should we use our applier as implementer or the PLM? > > > > What is the proper way? > > > > > > > > And anyhow how do I call the relevant HW api (Broadcom SDK) > using > > > > the HPI interface? > > > > > > > > > > > > > > > > Idan Migemi > > > > > > > > Embedded Software Team Leader > > > > > > > > PTT - Embedded Software > > > > Global Technology Division > > > > > > > > > > > > phone/fax: > > > > > > > > +972.3.926.6112 > > > > > > > > E-mail: > > > > > > > > [email protected]<mailto:[email protected]> > > > > > > > > > > > > > > > > www.ecitele.com<http://www.ecitele.com/> > > > > > > > > [cid:[email protected]] > > > > > > > > > > > > > > > > > > > -------------------------------------------------------------------- > > > -- > > > -------- _______________________________________________ > > > Opensaf-users mailing list > > > [email protected] > > > https://lists.sourceforge.net/lists/listinfo/opensaf-users ------------------------------------------------------------------------------ _______________________________________________ Opensaf-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-users
