-
Notifications
You must be signed in to change notification settings - Fork 0
Minutes 2016 08 31
ericvoit edited this page Sep 2, 2016
·
3 revisions
| Meeting Materials | Attending |
|---|---|
| WebEx Recording password: Yb9Jpt8j | Andy Bierman, Ambika Prasad Tripathy, Alexander Clemm, Alberto Gonzalez Prieto, Eric Voit, Susan Hares, Tim Jenkins, Yan Gang, Balazs Lengyel, Walker, Sharon Chisholm, Kent Watsen |
- General consensus
- Configured subscription have IDs provided by the network Management system (as config='True' when the subscription is created.)
- We were limited from more elegant config='false' solutions as OpState isn't done, and the alternative would still require to be a unique identifier coordinated among the Publisher/Subscriber/Receiver.
- For dynamic subscriptions, subscription ID is generated on the Publisher.
- Tim has proposed additional text so that suggests how to partition configured and dynamic subscription ID space. Check you email box shortly.
- Discussion between annotation and deviation: Two open question:
- Question #1: Should this information be in the main file, or a separate file
- Some people liked separate administration of different files
- Other people wanted the flexibility to simply change/augment the main model with this info
- Question #2: Should we use annotations of deviations
- There was some good discussion that annotations could be rules added to a base model, and deviations be subtractions from the model. This could simplify management rules on when they should be applied.
- Balazs to drive this question to closure on the threads.
- Other considerations:
- Different Filters could impact whether something is on-change subscribable. I.e., threshold filters for CPU Temp or Voltage might go on-change when a threshold is exceeded. So a simple on-change-not supported flag is not sufficient.
- Conversation started via email.