notification configuration info model

[Andy Bierman <ietf@andybierman.com>]

Hi,

Here is a simple "info model" for the notification data model.
This actually allows OR expressions to be processed correctly.


Filter Table - key: filterIndex

  filterIndex : Unsigned32 (1 .. max)

  filterDescr : string

  filterType : string ( andExpr, orExpr )

    # and-expr means all <filterPart> elements form a
    #   logical AND expression
    # or-expr means all <filterPart> elements form a
    #   logical OR expression

  filterPart : Component List (table) - key: filterPartIndex

       # nested table is just 'maxOccurs="unbounded"' in XML
       # 1 or more of these elements is needed to create a
       # meaningful filter

       filterPartIndex : Unsigned32 ( 1 .. max)

         # index is needed to avoid merge problem
         # entries will be evaluated in ascending order
         # sparse numbering is allowed

       filterPartType : string ( subtree, xpath, eventClass )

       filterPartVal : string



Profile Table - key: profileIndex

 profileIndex : Unsigned32 (1 .. max)

 profileDescr : string

 profileFilter : filterIndex

  # optional : if present then this filter entry is used
  #            A missing filter is the same as no filter



Target Table - key: targetName

 # this needs lots more work; it should be a generalized config
 # for all callhome purposes, not just agent-initiated notifications
 # this table is not used by the manager-session interface

 targetName : Name

 targetAddress : InetAddress

 targetUserName : string

 targetUserCredType : string

 targetUserCredential : string


--------------------------------

Example config:

<notifications>

 <filters>
   <filter>
     <filterIndex>1</filterIndex>
     <filterDescr>Filter for config or fault event types</filterDescr>
     <filterType>orExpr</filterType>
     <filterPart>
        <filterPartIndex>1</filterPartIndex>
        <filterPartType>eventClass</filterPartType>
        <filterPartVal>config</filterPartVal>
     </filterPart>
     <filterPart>
        <filterPartIndex>2</filterPartIndex>
        <filterPartType>eventClass</filterPartType>
        <filterPartVal>fault</filterPartVal>
     </filterPart>
   </filter>
  </filters>

  <profiles>
    <profile>
      <profileIndex>1</profileIndex>
      <profileDescr>Send only config and fault event classes</profileDescr>
      <profileFilter>1</profileFilter>
    </profile>
  </profiles>

</notifications>

-------------------------------------


For managers:

 <rpc>
   <start-notifications>
     <profile>1</profile>
   </start-notifications>
 </rpc>

For agents:

 - many issues very TBD like target priority,
   multiple targets, target fail-over
 - agent uses callhome mechanism to connect to manager;
   manager checks capabilities (need to figure out how
   the manager knows why the agent is connecting);
   manager uses <start-notifications> RPC to initiate
   notification generation.



    

Andy


--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>