Difference between revisions of "Synaps/Architecture"

Revision as of 06:39, 15 October 2012

Note: This page is to share architectural information of Synaps temporarily. When the Synaps is open sourced, this page will be moved into its documentation page.

Synaps Architecture

Synaps API is frontend of the system. It uses RabbitMQ for asynchronous processing. The messages are passed to Synaps Strom.

Synaps Storm is a topology implementation which is aimed to run on the Twitter Storm, real-time distributed stream processing system. Synaps Storm is based on the message driven architecture. Most of the messages are came from RabbitMQ. It notifies using Notification Queue so that other notification system can interoperate with the queue.

Both Synaps API and Synaps Storm are use Cassandra no-sql database to store persistent data.

Following is Architecture of Synaps.

File:Synaps$$Architecture$SynapsSystemOverview.jpg

following is an example of integration.

Externally, Synaps interoperates with agents which inputs metric data periodically, such as VMMON which can get information from VM Hyperisor with libvirt library and Nova API, and custom agent also.

Synaps Notification is a program to send E-mail or SMS.

File:Synaps$$Architecture$IntegratedSystemOverview.jpg

following is an example of deployment.

File:Synaps$$Architecture$SynapsDeployment.jpg

@@ Line 1: / Line 1: @@
 __NOTOC__
-<<[[TableOfContents]]()>>
 Note: This page is to share architectural information of Synaps temporarily. When the Synaps is open sourced, this page will be moved into its documentation page.
@@ Line 26: / Line 24: @@
 [[Image:Synaps$$Architecture$SynapsDeployment.jpg]]
-== Synaps API Subsystem description ==
-Synaps API is WSGI based Web Server which provides AWS [[CloudWatch]] compatible API.
-=== Asynchrous request processing ===
-Requests below are processed asynchrously.
-* Delete''''''Alarms
-* Put''''''Metric''''''Alarm
-* Put''''''Metric''''''Data
-For example,
-[[Image:Synaps$$Architecture$SynapsAPI-PutMetricData.jpg]]
-=== Synchrous request processing ===
-Requests below are processed synchrously.
-* Describe''''''Alarm''''''History
-* Describe''''''Alarms
-* Describe''''''Alarms''''''For''''''Metric
-* Disable''''''Alarm''''''Actions
-* Enable''''''Alarm''''''Actions
-* Get''''''Metric''''''Statistics
-* List''''''Metrics
-* Set''''''Alarm''''''State
-For example,
-[[Image:Synaps$$Architecture$SynapsAPI-GetMetricStatistics.jpg]]
-== Synaps Storm Subsystem description ==
-Following is simple diagram of Synaps Storm topology.
-[[Image:Synaps$$Architecture$SynapsStorm-Topology.jpg]]
-=== [[PutMetricData]] message processing ===
-This is the most important part of Synaps. When the Put''''''Metric''''''Data message is received via message queue, it reads its in-memory sliding windows or database to aggregate its datapoints and evalutate status of its alarms. If the status is changed, it sends action message to notification queue.
-[[Image:Synaps$$Architecture$SynapsStorm-[[PutMetricData]].jpg]]
-=== [[PutMetricAlarm]] message processing ===
-When the Put''''''Metric''''''Alarm message is received via message queue, it find its metric and update its in-memory alarm data and update it into database.
-[[Image:Synaps$$Architecture$SynapsStormPeriodicMonitoring.jpg]]
-=== [[PeriodicMonitoring]] message processing ===
-‘check_spout’ generates Periodic''''''Monitoring message every 1 minute. When the message is generated, it checks their alarms which are not evaluated recently by Put''''''Metric''''''Data message.
-[[Image:Synaps$$Architecture$SynapsStormPutMetricAlarm.jpg]]