[Openais] Query about Event Service and Notification Service

Hegde, Ramesh (STSD) rameshh at hp.com
Tue Nov 28 01:18:00 PST 2006


Thank you for your answers.  Regarding the localization support the info
is below
 
Localization is the process of translating software user interface from
one language to another. 

Example: If there is any mechanism inside Event Service to support
different language catalog. In this case, the event parsing will be
based on the catalog in place. If it is English catalog then the Event
Data will be displayed in English. If the catalog is in Chinese, then
the data will be displayed in Chinese. I am not sure whether this will
fall in the limit of event service in the SAF context. However I feel
this can also be part of event service. User just sends the data in the
form of numbers and parameters and the actual message will be extracted
from the catalog in place.


Regarding the support aspect, it is very critical for us when we deliver
the software to the end customer . As you know the customer may not
always like to migrate to the latest version and might need a patch on
top of particular version of openais. And also I am not sure how support
will be provided by openais when there is a customer centric critical
bugs. Because its always a question of priority and any bug reported
will be considered with same priority in the opensource world.

Regards

Ramesh


________________________________

From: Steven Dake [mailto:steven.dake at gmail.com] 
Sent: Tuesday, November 28, 2006 2:19 PM
To: Hegde, Ramesh (STSD)
Cc: openais at lists.osdl.org
Subject: Re: [Openais] Query about Event Service and Notification
Service




On 11/27/06, Hegde, Ramesh (STSD) <rameshh at hp.com > wrote: 

	Hello Steve,
	
	Sorry to disturb you again. I still have some more questions
	
	1.Do you have any localization support for event service? Like
catalog 
	support.

 
I have no idea what catalog support is.  Would you mind telling me?
 
We do not have localization support for messages from the event service
to the system log.  
 


	2.Do you have any performance data related to Event Service?

 
 
You can use the latest evtbench (to be published shortly) to see the
performance in your own network environment.  It measures event
throughput at the delivery for various event sizes.

I started evtbench on 3 nodes at the same time.  With a 3 node cluster
of 3ghz machines, Intel gige devices and SMC gige switch configured at
8900 mtu size and no encryption a 3 node cluster delivers the following
results (your results may be different): 

Note you can do the same thing with evsbench or ckptbench.  Evsbench on
my test cluster does about 40k messages per second, and this is about
the memory/cpu bandwidth of my systems that I use (ie: cpu bound).


[root at slickdeal test]# ./evtbench
66762 Writes     1 bytes per write  10.001 Seconds runtime  6675.271
TP/s   0.007 MB/s.
35334 Writes  1001 bytes per write  10.004 Seconds runtime  3532.048
TP/s   3.536 MB/s. 
26631 Writes  2001 bytes per write  10.006 Seconds runtime  2661.375
TP/s   5.325 MB/s.
22272 Writes  3001 bytes per write  10.005 Seconds runtime  2226.157
TP/s   6.681 MB/s.
19283 Writes  4001 bytes per write  10.003 Seconds runtime  1927.727
TP/s   7.713 MB/s.
18056 Writes  5001 bytes per write  10.004 Seconds runtime  1804.947
TP/s   9.027 MB/s.
16260 Writes  6001 bytes per write   9.999 Seconds runtime  1626.112
TP/s   9.758 MB/s.
15110 Writes  7001 bytes per write  10.001 Seconds runtime  1510.813
TP/s  10.577 MB/s.
13659 Writes  8001 bytes per write  10.003 Seconds runtime  1365.501
TP/s  10.925 MB/s.
12622 Writes  9001 bytes per write  10.002 Seconds runtime  1261.989
TP/s  11.359 MB/s.
12042 Writes 10001 bytes per write  10.002 Seconds runtime  1203.965
TP/s  12.041 MB/s.
11706 Writes 11001 bytes per write   9.999 Seconds runtime  1170.731
TP/s  12.879 MB/s.
11320 Writes 12001 bytes per write  10.002 Seconds runtime  1131.731
TP/s  13.582 MB/s.
11085 Writes 13001 bytes per write  10.001 Seconds runtime  1108.372
TP/s  14.410 MB/s.
10629 Writes 14001 bytes per write  10.001 Seconds runtime  1062.783
TP/s  14.880 MB/s.
10110 Writes 15001 bytes per write  10.001 Seconds runtime  1010.900
TP/s  15.165 MB/s.
 9467 Writes 16001 bytes per write  10.001 Seconds runtime   946.576
TP/s  15.146 MB/s.
 9039 Writes 17001 bytes per write  10.002 Seconds runtime   903.729
TP/s  15.364 MB/s.
 8993 Writes 18001 bytes per write  10.004 Seconds runtime   898.909
TP/s  16.181 MB/s.
 8892 Writes 19001 bytes per write   9.997 Seconds runtime   889.475
TP/s  16.901 MB/s.
 8601 Writes 20001 bytes per write  10.002 Seconds runtime   859.905
TP/s  17.199 MB/s.
 8503 Writes 21001 bytes per write  10.003 Seconds runtime   850.072
TP/s  17.852 MB/s.
 8312 Writes 22001 bytes per write   9.999 Seconds runtime   831.307
TP/s  18.290 MB/s.
 8056 Writes 23001 bytes per write  10.000 Seconds runtime   805.566
TP/s  18.529 MB/s.
 7930 Writes 24001 bytes per write  10.004 Seconds runtime   792.700
TP/s  19.026 MB/s.
 7373 Writes 25001 bytes per write  10.003 Seconds runtime   737.104
TP/s  18.428 MB/s.
 7560 Writes 26001 bytes per write  10.000 Seconds runtime   755.981
TP/s  19.656 MB/s.
 7355 Writes 27001 bytes per write   9.999 Seconds runtime   735.595
TP/s  19.862 MB/s.
 6991 Writes 28001 bytes per write  10.003 Seconds runtime   698.925
TP/s  19.571 MB/s.
 7103 Writes 29001 bytes per write  10.001 Seconds runtime   710.247
TP/s  20.598 MB/s.
 6732 Writes 30001 bytes per write  10.005 Seconds runtime   672.897
TP/s  20.188 MB/s.
 6735 Writes 31001 bytes per write   9.998 Seconds runtime   673.662
TP/s  20.884 MB/s.
 6450 Writes 32001 bytes per write  10.003 Seconds runtime   644.804
TP/s  20.634 MB/s.
 6497 Writes 33001 bytes per write   9.999 Seconds runtime   649.794
TP/s  21.444 MB/s.
 6491 Writes 34001 bytes per write  10.004 Seconds runtime   648.820
TP/s  22.061 MB/s.
 6306 Writes 35001 bytes per write   9.996 Seconds runtime   630.866
TP/s  22.081 MB/s.
 6305 Writes 36001 bytes per write  10.008 Seconds runtime   630.019
TP/s  22.681 MB/s.
 6173 Writes 37001 bytes per write   9.999 Seconds runtime   617.389
TP/s  22.844 MB/s.
 5913 Writes 38001 bytes per write   9.997 Seconds runtime   591.495
TP/s  22.477 MB/s.
 5930 Writes 39001 bytes per write  10.004 Seconds runtime   592.763
TP/s  23.118 MB/s.
 5801 Writes 40001 bytes per write   9.996 Seconds runtime   580.326
TP/s  23.214 MB/s.
 5814 Writes 41001 bytes per write  10.008 Seconds runtime   580.925
TP/s  23.819 MB/s.
 5698 Writes 42001 bytes per write  10.001 Seconds runtime   569.762
TP/s  23.931 MB/s.
 5540 Writes 43001 bytes per write   9.996 Seconds runtime   554.248
TP/s  23.833 MB/s.
 5456 Writes 44001 bytes per write  10.002 Seconds runtime   545.490
TP/s  24.002 MB/s.
 5504 Writes 45001 bytes per write  10.004 Seconds runtime   550.168
TP/s  24.758 MB/s.
 5475 Writes 46001 bytes per write   9.999 Seconds runtime   547.565
TP/s  25.189 MB/s.
 5339 Writes 47001 bytes per write  10.001 Seconds runtime   533.852
TP/s  25.092 MB/s.
 5283 Writes 48001 bytes per write  10.003 Seconds runtime   528.144
TP/s  25.351 MB/s.
 5067 Writes 49001 bytes per write  10.001 Seconds runtime   506.642
TP/s  24.826 MB/s.

 

	3.Any inbuilt security for distributed event service or it is
assumed
	that the event service will operate with in restricted network
area? 

 
openais uses HMAC/SHA1 for authentication of messages and SOBER128 to
encrypt messages if secauth is configured on.  There is no perfect
forward secrecy in the system meaning an eavesdropper could eventually
detect the keys if they could a) listen to network packets b) had alot
of time on their hands.  However, the algorithm is still fairly secure
and provides better security then plaintext IO.  Read SECURITY in the
source distribution to understand the security model and methods used
for authenticating and encrypting data.  As always, I'd recommend not
allowing port access for the UDP port you specify in your configuration
from outside your restricted network. 
 


	4. Can you name some of the commercial vendors from whom we can
buy
	support for OpenAIS? 


I want to keep the nature of this list non-commercial in nature.
However, I will contact the various distributions I am aware are
shipping openais and have them contact you about commercial support
options if you desire. 


Regards
-steve



	Note that I read some info on these topics on the web , still I
want to 
	make sure I am aligned and understood properly .
	
	Regards
	Ramesh
	
	-----Original Message-----
	From: Steven Dake [mailto: sdake at redhat.com
<mailto:sdake at redhat.com> ]
	Sent: Tuesday, November 28, 2006 12:05 AM 
	To: Hegde, Ramesh (STSD)
	Cc: openais at lists.osdl.org
	Subject: RE: [Openais] Query about Event Service and
Notification 
	Service
	
	responses inline
	
	On Thu, 2006-11-23 at 11:52 +0530, Hegde, Ramesh (STSD) wrote: 
	> Hi Steve,
	>
	> Thank you very much for your answers . My answers are inline
with some
	
	> more questions.
	>
	> Regards
	> Ramesh
	>
	> -----Original Message-----
	> From: Steven Dake [mailto: sdake at redhat.com]
	> Sent: Thursday, November 23, 2006 12:55 AM
	> To: Hegde, Ramesh (STSD)
	> Cc: openais at lists.osdl.org
	> Subject: Re: [Openais] Query about Event Service and
Notification
	> Service
	>
	> On Wed, 2006-11-22 at 15:25 +0530, Hegde, Ramesh (STSD) wrote:
	> > Hello,
	> >
	> > I am new  to the openais and I downloaded and installed
openais and 
	> > could run some of the tests related to Event Service.
	> >
	> > I have following doubts/questions related to mainly on Event
Service
	
	> > and Notification Service.
	> >
	> > 1. Is event Service is complete SAF complaint? i.e All Event
Service
	
	> > SAF APIs are supported? [ I could see the report which says
it is
	> > 100%
	>
	> > SAF compliant]
	> 
	> AIS EVT B.0.01 is supported completely in the event service
and has
	> 100% pass rate with SAF Test.  There may be areas where the
SAF Test
	> suite doesn't test appropriate compliance, but our opinion of
the 
	> tests is they do a very good job of testing compliance.
	>
	> [Ramesh] Thank you .
	>
	> > 2. Notification Service is implemented in openais? If not ,
any
	> > plans in the roadmap to implement the same ? 
	>
	> Not implemented, Will be implemented after 1.0 (Wilson) next
year.
	>
	> [Ramesh] Thank you
	>
	> > 3. Does the Event Service/Notification Service contains any
Java
	> > interfaces? 
	>
	> no.
	> [Ramesh] Thank you.
	>
	> > 4. Is is possible to use only Event Service/Notification
service
	> > from openais? (Is it a component which can be separated?)
	>
	> openais has a plugin infrastructure where only specified
plugins are 
	> loaded.  It would be possible to provide a configuration file
which
	> would only load the event service.  At the moment, all
services are
	> loaded by default.
	>
	> [Ramesh] I could download source rpm of openais-0.80.1-3. I am
able to
	
	> build the binary rpm for RHEL 4.  As you mentioned all the
services
	> are loaded by default.  How do I enable only Event Service? I
failed
	> to find any such configuration in /etc/ais/openais.conf also.
Cab you 
	> provide me any pointers/documents for the same?
	>
	> Each service consumes about 800k of ram so for low memory
systems,
	> this might make sense.
	>
	> > 5. What is the model for distributing this software? I am
not 
	> > finding any spec file or openais(runtime and Devel). Is it
worth to
	> > use it for
	>
	> > production environment for event service /Notification
service.
	>
	> The openais standards based cluster framework is available in
FC6 and 
	> several other distributions.  Please contact your distribution
	> provider and ask them to provide an openais rpm for you.  We
have RPM
	> spec files available for download in various RPM repos.
	> 
	> [Ramesh] Thanks . I am evaluating it for on of event products
to use
	> it as event service. What is the support model for this? Any
contact
	> person to discuss it further will help us to speedup this
activity. 
	> Also any cases where it is already in production environment?
	> As I understand there is one way which is by submitting a bug
to
	> opensource. Any other support contract possible?(like
supporting
	> particular version and bugs on top of it for lets say 5 years
from 
	> now]
	>
	>
	>
	
	Commercial support is available from various commercial vendors
that
	meet your 5 year requirements.  Support is also available free
via open
	source, but our main objective is stabalizing a branch and then
pushing 
	forward trunk.  At the moment we are stabalizing the 0.80 series
branch
	which is about complete.
	
	Openais 0.70 is used in production in a variety of environments
but I a
	not at liberty to discuss the nature of these deployments.
Perhaps 
	others on the list could talk about their experiences with
deployment.
	
	Regards
	-steve
	
	
	>
	>
	> >
	> >
	> > Please forgive me if I am asking some very basic silly
questions 
	> >
	>
	> good questions thanks for asking
	>
	> Regards
	> -steve
	>
	> > Thanks in advance
	> >
	> > Regards
	> > Ramesh
	> > _______________________________________________ 
	> > Openais mailing list
	> > Openais at lists.osdl.org
	> > https://lists.osdl.org/mailman/listinfo/openais 
	>
	
	
	_______________________________________________
	Openais mailing list
	Openais at lists.osdl.org 
	https://lists.osdl.org/mailman/listinfo/openais
	


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.linux-foundation.org/pipermail/openais/attachments/20061128/34499dde/attachment-0001.htm


More information about the Openais mailing list