Synaps/Architecture - Revision history

Ryan Lane: Text replace - "NOTOC" to ""

2013-02-17T23:31:17Z

Text replace - "__NOTOC__" to ""

JuneYi at 23:39, 18 October 2012

2012-10-18T23:39:20Z

JuneYi at 23:38, 18 October 2012

2012-10-18T23:38:43Z

JuneYi at 11:09, 15 October 2012

2012-10-15T11:09:26Z

JuneYi at 06:39, 15 October 2012

2012-10-15T06:39:05Z

JuneYi at 12:51, 13 October 2012

2012-10-13T12:51:02Z

JuneYi at 12:44, 13 October 2012

2012-10-13T12:44:33Z

New page

__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.

== Synaps Architecture ==
Synaps API is frontend of the system. It uses RabbitMQ for asynchronous processing requested messages. And 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. Any other notification system can interoperate with the queue.

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

Following is Architecture of Synaps.

[[Image: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.

[[Image:Synaps$$Architecture$IntegratedSystemOverview.jpg]]

following is an example of deployment.

[[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 ==

Synaps Storm is a topology implementation which is aimed to run on the Twitter Storm, real-time distributed stream processing system.

Following is simple diagram of Synaps Storm topology.

[[Image:Synaps$$Architecture$SynapsStorm-Topology.jpg]]

=== [[PutMetricData]] message processing ===

This function is the most important part of Synaps. When the [[PutMetricData]] message is received via RabbitMQ 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 [[PutMetricAlarm]] message is received via RabbitMQ 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 [[PeriodicMonitoring]] message every 1 minute. When the message is generated, it checks their alarms which are not evaluated recently by [[PutMetricData]] message.

[[Image:Synaps$$Architecture$SynapsStormPutMetricAlarm.jpg]]

← Older revision		Revision as of 23:31, 17 February 2013
Line 1:		Line 1:
−	~~__NOTOC__~~	+
	Note: This page is moved to http://spcs.github.com/synaps		Note: This page is moved to http://spcs.github.com/synaps

← Older revision		Revision as of 23:39, 18 October 2012
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
−	Note: This page is ~~move~~ to http://spcs.github.com/synaps	+	Note: This page is moved to http://spcs.github.com/synaps

← Older revision		Revision as of 23:38, 18 October 2012
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
−	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.~~	+	Note: This page is move to http://spcs.github.com/synaps
−
−	~~== 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 use Cassandra no-sql database to store persistent data.~~
−
−	~~Following is Architecture of Synaps.~~
−
−	~~[[Image:Synaps$$Architecture$SynapsSystemOverview.jpg]]~~
−
−	~~following is an example of an integrated system.~~
−
−	Externally, Synaps interoperates with agents which inputs metric data periodically, such as VMMON which can get information from VM Hyperisor. Synaps Notification is a program that can send E-mail, SMS.
−
−	~~[[Image~~:~~Synaps$$Architecture$IntegratedSystemOverview~~.~~jpg]]~~
−
−	~~following is an example of deployment.~~
−
−	~~[[Image:Synaps$$Architecture$SynapsDeployment~~.~~jpg]]~~

@@ Line 7: / Line 7: @@
 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.
+Both Synaps API and Synaps Storm use Cassandra no-sql database to store persistent data.
 Following is Architecture of Synaps.
@@ Line 13: / Line 13: @@
 [[Image:Synaps$$Architecture$SynapsSystemOverview.jpg]]
-following is an example of integration.
+following is an example of an integrated system.
-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.
+Externally, Synaps interoperates with agents which inputs metric data periodically, such as VMMON which can get information from VM Hyperisor. Synaps Notification is a program that can send E-mail, SMS.
 [[Image:Synaps$$Architecture$IntegratedSystemOverview.jpg]]

@@ Line 1: / Line 1: @@
 __NOTOC__
 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]]

@@ Line 5: / Line 5: @@
 == Synaps Architecture ==
-Synaps API is frontend of the system. It uses RabbitMQ for asynchronous processing requested messages. And the messages are passed to Synaps Strom.
+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. Any other notification system can interoperate with the queue.
+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 Storm programs are use Cassandra no-sql database to store persistent data.
+Both Synaps API and Synaps Storm are use Cassandra no-sql database to store persistent data.
 Following is Architecture of Synaps.
@@ Line 60: / Line 60: @@
 == Synaps Storm Subsystem description ==
 Following is simple diagram of Synaps Storm topology.
@@ Line 69: / Line 67: @@
 === [[PutMetricData]] message processing ===
-This function is the most important part of Synaps. When the [[PutMetricData]] message is received via RabbitMQ 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.
+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]]
@@ Line 75: / Line 73: @@
 === [[PutMetricAlarm]] message processing ===
-When the [[PutMetricAlarm]] message is received via RabbitMQ message queue, it find its metric and update its in-memory alarm data and update it into database.
+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]]
@@ Line 81: / Line 79: @@
 === [[PeriodicMonitoring]] message processing ===
-‘check_spout’ generates [[PeriodicMonitoring]] message every 1 minute. When the message is generated, it checks their alarms which are not evaluated recently by [[PutMetricData]] message.
+‘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]]