Alarms Feature requires Dynamic UVEs

[Anish Mehta]

For the Alarms feature, we will need to raise alarms based on user-configured rules.
The alarm name would also be user-configured; there will be no sandesh file for this.

Also, we need to raise alarms based on config-operational mismatch.
Generated code is used for config objects in ApiServer, but is not sandesh-based.

To satisfy these cases, we need the ability to Send UVEs/Alarms based on a python dict, instead of requiring generated code from a sandesh file.

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/14354
Submitter: Sundaresan Rajangam (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/14354
Committed: http://github.org/Juniper/contrail-sandesh/commit/829d64033120618196c4d42ebcb2c59d321a18fe
Submitter: Zuul
Branch: master

commit 829d64033120618196c4d42ebcb2c59d321a18fe
Author: Sundaresan Rajangam <email address hidden>
Date: Sun Oct 11 10:30:31 2015 -0700

Dynamic sandesh UVE implementation

Added a new sandesh type named "dynamicuve".
Defined sandesh of type "dynamicuve" in sandesh_dynamic_uve.sandesh
All dynamic UVEs would be derived from this base class defined in
sandesh_dynamic_uve.sandesh
The newly added sandesh type "dynamicuve" is only for parsing/code
generation. Dynamic UVEs are sent to collector with same type as sandesh
UVE. Therefore, dynamic UVEs are processed in the same way as sandesh
UVEs in the collector/analytics-api and hence there is no difference in
the interpretation of dynamic UVEs from sandesh UVEs from the user stand
point.

Related change:
Presently, _SANDESH_REQUEST_LIST, _SANDESH_UVE_LIST and
_SANDESH_ALARM_LIST contain the class name as string. Modified these
lists to contain class object instead of class name. pysandesh library
would store the class object instead of the class name and corresponding
module.

Change-Id: I9f15ff6613e4f2a23334291f165e7bcdd4bf6c62
Closes-Bug: #1469966