Gerd Aschemann and Roger Kehr. Towards a Requirements-based Information Model for Configuration Management. In Proceedings of 4th International Conference on Configurable Distributed Systems (ICCDS'98), pages 181--189. IEEE Computer Society Press, May 1998.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....and not on ensuring system reliability. Some reliability work has begun, such as the Simplex architecture for upgrading real time controllers [38] analyzing the impacts of reconfiguration at an architectural level [29] checking whether a given or new configuration meets requirements constraints [2], and extending semantic analysis on variants of components to the pre deployment phase [13] 2.2 Self Checking Systems Self checking systems employ a type of run time specification checking, where formal assertions about the state of the software or the values of inputs and outputs are checked ....

G. Aschemann and R. Kehr. Towards a Requirements-based Information Model for Configuration Management. In Proceedings of the Fourth International Conference on Configurable Distributed Systems, pages 181--188. IEEE Computer Society Press, May 1998.

No context found.

Gerd Aschemann and Roger Kehr. Towards a Requirements-based Information Model for Configuration Management. In Proceedings of 4th International Conference on Configurable Distributed Systems (ICCDS'98), pages 181--189. IEEE Computer Society Press, May 1998.

....implemented prior to the final definition of the overall architecture. In this section we focus on some details which we consider to be of major interest, in particular the integration of existing components. 6. 1 Integration of the Configuration Service With the System Configuration Tool (SCOT) [5] we had defined and implemented a repository for configuration information. SCOT provides both a Web interface for human users and a CORBA interface to access configuration data by management applications [7] and enhanced user interfaces, i.e. Java applets. SCOT has been integrated with the ....

....in a plain Jini system. Looking at the event model, we find that FMA uses the Jini RMI communication model and only extends it by an event multiplexer. We demonstrated a similar solution by the integration of a CORBA event channel. In contrast to FMA, our architecture provides an information model [5] which is largely based on the requirements of configuration management but which is also usable in other functional areas of distributed systems management through its integration with CORBA and the mapping to HTML or XML. However, it is important to note that FMA is backed by some vendors in ....

Gerd Aschemann and Roger Kehr. Towards a Requirements-based Information Model for Configuration Management. In Proceedings of 4th International Conference on Configurable Distributed Systems (ICCDS'98), pages 181--189. IEEE Computer Society Press, May 1998.

....but extensible interface. This allows for arbitrary implementations, e.g. a more or less static configuration within the boundaries of DHCP as well as highly dynamic configurations that are based on knowledge of local policies, network topology, current resource utilization, etc. With SCOT [1] we have proposed such a repository which can be easily integrated into the Jini management federation. SNMP Gateway. A generic gateway for SNMP may translate remote method calls (Java RMI or CORBA based) into SNMP requests and return the SNMP replies. SNMP traps may be converted to Jini ....

Gerd Aschemann and Roger Kehr. Towards a Requirements-based Information Model for Configuration Management. In Proceedings of 4th International Conference on Configurable Distributed Systems, pages 181--189. IEEE Computer Society Press, May 1998.

....and is only parameterized with the actual values, i.e. host name and port of the real service. However, these proxies must be registered with the Jini Lookup Service. Since proper parameterization is necessary we have left this task to an extended version of our Scot con guration repository [2], which is used to maintain service location within a network. It could easily be replaced by another mechanism, ranging from a simple service using le based con guration information up to an arbitrary complex service using relational databases or other repositories. For some services we can ....

Gerd Aschemann and Roger Kehr. Towards a Requirements-based Information Model for Conguration Management. In Proceedings of 4th International Conference on Congurable Distributed Systems (ICCDS'98), pages 181-189. IEEE Computer Society Press, May 1998.

....available through CORBA. Both (GOM and Liaison) do not care about making the exact SNMP MIB specifications available by translating the MIB to an IDL description. They only provide access to SNMP variables by a generic mapping of strings to variable names. 4 Integration of SNMP and SCOT In [1] we introduced our System Configuration Tool (SCOT) It provides an object repository based upon the prototype instance model [10] which allows for value sharing among objects. Managed objects are described within repository objects as a list of slot objects. A slot is a tuple S = name; value; ....

G. Aschemann and R. Kehr. Towards a Requirements-based Information Model for Configuration Management. In Proceedings of 4th International Conference on Configurable Distributed Systems, pp. 181--189. IEEE Computer Society Press, May 1998.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC