Participants - Sanjiva, Isabelle, Amila, Jayanga
Discussed about the architecture of the WSO2 Operations Center[1] and a
demo of the WSO2 Operations Center M1 implementation.
All the proposed features[2] of the WSO2 OC were discussed in the meeting.
Following were the new ideas that emerged in the discussion
1. Exposing all the features of the WSO2 OC as services.
- This feature will allow external (manual/automated) systems to
communicate with WSO2 OC
- Trigger functions externally. (eg: restart all the servers at
midnight)
2. Adding 'tag' feature to the WSO2 OC
- WSO2 OC will have a grouping mechanism to group nodes in the
system, based on the cluster details, by default
- Apart from that users will be able to tag nodes (eg. all the nodes
in data center 1)
3. Sending heartbeat message to the BAM.
- Heartbeat messages will be sent to the WSO2 OC from all the nodes in
the system.
- A copy of this message will be sent to the BAM
- So the information in the BAM can be used to calculate the system
downtime/availability etc.
4. Patch deployment
- Try to incorporate puppet features so the configuration changes can
also be automated.
- Feature to get a list of patches that were applied - WSO2 OC will
maintain a list of the patches that were applied. These
information will be
used to generate this report. So the user can get a complete report about
the patches in the system.
Please add, if I have missed anything and your comments are welcome.
Ref:
[1]
https://docs.google.com/a/wso2.com/presentation/d/1VIlXIctPMwGt9ftDi48SikbRrA0Hr70WS4rGDc7lZfo/edit?usp=sharing
[2]
https://docs.google.com/a/wso2.com/document/d/11PjYs6bJ8stEuM20ILG1zVhovRYjF_1OPg2VHfwTCmM/edit?usp=sharing
Regards,
*Jayanga Dissanayake*
Senior Software Engineer
WSO2 Inc. - http://wso2.com/
lean . enterprise . middleware
email: [email protected]
mobile: +94772207259
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
