I think we need to correct the diagram. Agents are publish data via thrift and in OC there is a thrift receiver. (not the CEP). These receiving data (we can also store in Cassandra/RDMS ..etc) can used in either BAM or CEP depending on the requirement.
On Wed, Apr 1, 2015 at 1:52 PM, Noel Yahan <[email protected]> wrote: > Hi Maninda, > > According to current architecture CEP only publish data to MB and any > other product can subscribe / publish to MB topics and get the data.If we > need publish data to BAM we can subscribe to MB topics and get the > data.Jax-Rs is for expose MB topics information in RESTful manner.The > gadgets are UES gadgets.We use RESTful APIs to display OC data in UES > dashboard with gadgets. > > Thanks. > > Noel Yahan > Software Engineering Intern - WSO2 > Mobile : +94 71-647-872-3 > Twitter <https://twitter.com/noelyahan> | LinkedIn > <http://lk.linkedin.com/pub/noel-yahan/48/186/a9b> | Google+ > <https://plus.google.com/+NoelYahan> > > On Wed, Apr 1, 2015 at 12:25 PM, Maninda Edirisooriya <[email protected]> > wrote: > >> How does the BAM comes into the picture of new design? Do the OC agents >> publish to both CEP and BAM, or does the data get published to BAM from MB? >> It is better if there is some unification among Gadgets in OC with the new >> dashboard components of new BAM (DAS) as it will be the unified UI we are >> going to ship with UES AFAIK. So we need to integrate Jax-Rs exposed from >> MB subscription with the new gadgets supported with DAS. >> >> Thanks. >> >> >> *Maninda Edirisooriya* >> Senior Software Engineer >> >> *WSO2, Inc.*lean.enterprise.middleware. >> >> *Blog* : http://maninda.blogspot.com/ >> *E-mail* : [email protected] >> *Skype* : @manindae >> *Twitter* : @maninda >> >> On Fri, Mar 27, 2015 at 11:22 PM, Noel Yahan <[email protected]> wrote: >> >>> Meeting Notes: >>> >>> >>> Participants: Sameera Jayasoma, Sameera Perera, Kasun, Jayanga, Manoj, >>> Kalpa, Noel, Chanaka, Shashika, Lakmal, Imesh, Kishanthan >>> >>> >>> In this meeting Jayanga explained the current architecture of OC M2 and >>> Lakmal explained Apache Stratos messaging architecture and how Stratos use >>> their agent to publish periodic status, topology, summarized status >>> messages and what are the problems in current OC messaging architecture and >>> how can OC improve, reuse their features and add new features. >>> >>> >>> >>> Current OC architecture >>> >>> >>> >>> - >>> >>> Default communication is the real time communication (Sends periodic >>> server information to OC Jax-Rs web app). >>> - >>> >>> Jax-Rs is exposing a RESTFul API about cluster, server information. >>> - >>> >>> Has a feature to plug any publisher like BAM, MB, CEP. >>> - >>> >>> Use the RESTful API and display different views using UES gadgets. >>> >>> >>> [image: oc current architecture.png] >>> >>> Problems in current architecture >>> >>> >>> >>> - >>> >>> There’s no way to persist real time data other than configure a new >>> BAM data publisher. >>> - >>> >>> If OC goes down dynamic data will be lost, because default real time >>> data is publishing to the Jax-Rs endpoint. >>> - >>> >>> To many requests to OC Jax-Rs >>> - >>> >>> When number of instances will increase, linearly number of >>> request to Jax-Rs will increase. >>> - >>> >>> Server commands (restart, shutdown) are sending through HTTP >>> response message >>> - >>> >>> If something goes wrong in HTTP communication, commands will >>> lost, specially in cluster-wise restart (round robin) >>> >>> >>> >>> New OC architecture >>> >>> >>> [image: oc new archi.png] >>> >>> >>> >>> - >>> >>> This is the new OC messaging architecture according to Apache >>> Stratos Pub-Sub communication. >>> - >>> >>> Real time server data should publish to CEP. >>> - >>> >>> Analyzed/Summarized real time data should publish to MB topics from >>> CEP. >>> - >>> >>> All OC Agents should subscribe to MB topics to get commands and >>> server informations from OC Jax-Rs. >>> - >>> >>> OC Jax-Rs should follow both publishing and subscribing part to >>> sending commands and getting analyzed real time server data from MB. >>> >>> >>> >>> New features that the OC should support >>> >>> >>> >>> - >>> >>> CEP should send alerts (sms, email, etc..) in critical scenario like >>> in server failures etc.. >>> - >>> >>> OC should able to publish lifecycle events to message broker topic >>> and all OC Agents should subscribe to that topic and act according to >>> their >>> events. >>> - >>> >>> Commands should publish to a message broker topic (eg: message >>> notifier topic). >>> - >>> >>> Install AS, MB, CEP features in a single pack with OC and should be >>> able to start with carbon profiling. >>> - >>> >>> OC should able incorporate with WSO2 Private PaaS. >>> >>> >>> >>> Concerns >>> >>> >>> >>> - >>> >>> Decouple the OC agent command handling part, machine level data >>> sending part from current running JVM. >>> - >>> >>> Current OC M2 version handles the commands (restart, shutdown) in >>> same JVM. >>> >>> >>> - >>> >>> Need to decide the implementation of this agent, python or java >>> currently Apache Stratos has the same agent with python implementation >>> and >>> OC M2 version has the java implementation with some feature. >>> - >>> >>> Deploy this agent per machine. >>> >>> >>> - >>> >>> If server is down it should start again by this external agent. >>> - Server commands (restart, shutdown) also should be handle by >>> this agent currently we are sending this commands with every response >>> message with commands json string. >>> >>> >>> Thanks, >>> Noel. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "WSO2 Engineering Group" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/a/wso2.com/d/optout. >>> >> >> > -- Lakmal Warusawithana Vice President, Apache Stratos Director - Cloud Architecture; WSO2 Inc. Mobile : +94714289692 Blog : http://lakmalsview.blogspot.com/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
