Conference azur::mcc

1595.0. "Messages on the effect of DME on EMA from the EMA Architects" by BLUMON::SYLOR (Architect = Buzzword Generator) Fri Oct 04 1991 00:17

    To:   EMA Interest
    From: EMA Architects

    We've had a number of questions from people inside Digital on how
    OSF's DME selection affects EMA.  Simpler answers to such questions
    are always better, so here are some simple but still correct "messages"
    that capture the essence of our strategy.  If you have other questions,
    just ask.  We have prepared a detailed response to factual errors in
    the DME Rationale, and copies of this are available through the OSF-DME
    VAXnotes conference.

    To everyone inside Digital:

    1   The key DME decision was made months ago when OSF based the DME
        RFT and the evaluation criteria on the same fundamental concepts
        as EMA, namely: management applications, a framework (i.e.
        directors), managed objects (entities), attributes, actions and
        notifications (events).  We could hardly ask for more than that.

    2   While the DME provides a general framework, that framework depends
        on the rich functionality of the OSF environment (DCE et.al.)
        and the applications and objects that OSF will deliver focus on
        management of that environment.  EMA has a broader applicability,
        and addresses the true integration of management, not just
        interoperability.  These requirements have not gone away.  We
        believe our best chance of success in Enterprise Management is
        to provide integrated solutions to real customers' needs.  The EMA
        architecture best addresses that problem.  We must do a better
        job of implementing that vision.

    To users and customers:

    3   Digital will integrate EMA and OSF DME such that your investment in
        today's EMA products will be protected.  In particular:

        -   EMA entities will be manageable from DME Systems
        -   DME objects will be manageable from EMA Directors.

    To managed object developers inside and outside Digital:

    4   As we have been recommending for some time, you should build your
        managed objects (entities) using the EMA Common Agent.  By doing so,
        your managed objects will be manageable via a number of standards,
        including SNMP, OSI and eventually, OSF DCE RPC.

    5   When the DME framework is available, as an OSF member Digital
        will be able to use that technology (including the source code)
        at very low cost.  Indeed, we will receive periodic snapshots of
        the DME as it is developed.  We intend to follow the DME
        development closely to ensure it is well integrated with EMA.
        In particular:

        a   We will sell OSF DME, and managed objects built on it.

        b   We will add DME support to the Common Agent.  Thus,
            managed objects built to the common agent interfaces will
            interoperate with a DME environment and be manageable from
            applications built to DME APIs.

        c   We may provide a veneer that maps the Common Agent API to the
            "vanilla" OSF DME APIs.  Thus, managed objects built to the
            Common Agent APIs will be portable to any OSF DME system.
            Whether or not we actually build this veneer depends on the
            success of OSF DME and the practicality of this approach.

    To management application developers inside and outside Digital:

    6   As we have been recommending for some time, you should build your
        management applications using DECmcc.  By doing so, your applications
        will be cleanly integrated with other applications developed by
        other groups.  DECmcc's AMs allow applications to manage more
        kinds of managed objects than any other framework technology.

    7   In the future, DECmcc's kernel and APIs will evolve into EMA/NAS
        management framework services and APIs.  We will provide backward
        compatibility to support existing applications.  We will add new
        services and capabilities to the framework as needed to support
        more and better management applications.  We will continue to
        improve the reliability, performance and functionality of
        existing services.

    8   When the DME framework is available, as an OSF member, Digital
        will be able to use that technology (including the source code)
        at very low cost.  Indeed, we will receive periodic snapshots of
        the DME as it is developed.  We intend to follow the DME
        development closely to ensure it is integrated with the rest of
        EMA.  In particular:

        a   We will sell OSF DME, and management applications built on it.

        b   We will provide the DME mechanisms and protocols as part of
            the EMA/NAS management framework in addition to those now
            supported by DECmcc.  Thus management applications built to
            the EMA/NAS framework APIs will interoperate with a DME
            environment and can manage any managed object built on DME.

        c   As part of the evolution of the EMA/NAS management framework,
            we will add any DME framework component or API that
            enhances the EMA/NAS management framework. This is
            consistent with our overall framework strategy to support
            standards and to provide whatever services and APIs are
            needed to build applications that solve our customers real
            needs.

        d   We could...

                build a veneer that maps the EMA/NAS management framework
                APIs onto the "vanilla" OSF DME APIs,

            or we could ...

                port the EMA/NAS management framework onto vanilla OSF/1.

            In either case, all management applications that are built
            on the EMA/NAS framework APIs would then be portable to any
            OSF platform.  Which we do (if either) depends on the success
            of OSF DME and a technical evaluation of its feasibility.

    Finally, to everyone within Digital:

    9   In the final analysis, it is management applications and managed
        objects that solve customers' needs.  The vast majority of our
        developers and resources must be applied to doing a good job in
        those areas, not the framework.  The EMA architects, the Director
        Framework developers and Common Agent developers are dedicated
        to providing the services application and object developers
        need.

    10  We should embrace standards, like OSF DME, not fear them. In that
        vein, we should recall a quote from FDR...

              "The only thing we have to fear, is fear itself!"