What is WSO2 Private PaaS?

In this blog post, I'm going to briefly introduce the WSO2 Private PaaS, an upcoming product from WSO2.

WSO2 Private PaaS


Even though I'm writing about this now, the WSO2 Private PaaS term coined just few weeks after we donated WSO2 Stratos to Apache Foundation in June 2013.

Apache Stratos (incubating) and WSO2 Private PaaS


The WSO2 Private PaaS is built on top of the Apache Stratos (incubating) project, which is currently undergoing major architectural changes from the initial 3.0.0-incubating version.

Following are few major changes you can expect in the next Apache Stratos (incubating) release. i.e. 4.0.0-incubating version.


  • Using a message broker for communication among core Stratos components.
  • Auto scaling now analyze real time data from cartridges like in flight request count and load average. Currently this data is analyzed using WSO2 Complex Event Processor
  • Load Balancer is now a cartridge in Stratos
  • New Stratos Manager UI
  • Stratos Manager now has RESTful services
  • Improved CLI

Lakmal has written a great blog post on explaining all of these.

Why Private?


The main reason is that WSO2 Private PaaS will be distributed as a product and anyone will be able to set up an on-premise, enterprise ready PaaS.

So, what do you get in WSO2 Private PaaS?


In addition to core Stratos framework, the WSO2 Private PaaS will get all WSO2 products as cartridges.

This means that with all WSO2 middleware products as cartridges, the WSO2 Private PaaS will provide the most comprehensive PaaS for enterprises. This is also great considering all the advantages you can get from WSO2.

The WSO2 Private PaaS will also have improved billing and metering for enterprise requirements.

WSO2 will officially support following IaaS providers for WSO2 Private PaaS
  • Amazon Elastic Compute Cloud (EC2)
  • OpenStack
  • SUSE Cloud
  • VMware vCloud

Cartridge Architecture


All WSO2 product cartridges will be configured using Puppet, an automation software, which will help us to configure cartridges easily with the use of templates etc. 

The cartridge will contain the Java and an init script to the start the Puppet Agent. With the use of user-data feature provided by the IaaS, we will just pass the puppet master host and the product type to the cartridges. The Cartridge will then configure itself using Puppet.

There is a "Cartridge Agent" inside the cartridge to communication with other Stratos components.

I will write a more detailed blog post with examples once we have a stable release soon.

You can check WSO2 Private PaaS JIRA on the progress.

Comments

Post a Comment

Popular posts from this blog

Specifying a custom Event Settings file for Java Flight Recorder

Image
When you are using Java Flight Recorder (JFR), the JFR will use an event settings file to check which event types to record. By default in JFR, there are two settings, "default" and "profile". The default setting is recommended for Continuous Recordings as it has very low overhead (typically less than 1% overhead). The profile setting has more events and useful when profiling the application. As mentioned in my previous blog post regarding  Java Flight Recorder Continuous Recordings , we use following arguments to do a Continuous Recording. -XX:+UnlockCommercialFeatures -XX:+FlightRecorder -XX:FlightRecorderOptions=defaultrecording=true,disk=true,repository=./tmp,dumponexit=true,dumponexitpath=./ Note: According to the Oracle documentation on " java " command, we should be able to specify "settings" parameter to the -XX:FlightRecorderOptions. However, the settings parameter has no effect when used with the -XX:FlightRecorderOptions and
Read more

Flame Graphs with Java Flight Recordings

Flame Graphs Brendon D. Gregg , who is a computer performance analyst , has created  Flame Graphs to visualize stack traces in an interactive way. You must watch his talk at USENIX/LISA13 , titled Blazing Performance with Flame Graphs , which explains Flame Graphs in detail. There can be different types of flame graphs and I'm focusing on  CPU Flame Graphs  with Java in this blog post. Please look at the Flame Graphs Description  to understand the Flame Graph visualization. CPU Flame Graphs and Java Stack Traces As  Brendon  mentioned in his talk, understanding why CPUs are busy is very important when analyzing performance.  CPU Flame Graphs  is a good way to identify hot methods from sampled stack traces. In order to generate CPU Flame Graphs for Java Stack Traces , we need a way to get sample stack traces. Brendon has given examples to use jstack  and Google's lightweight-java-profiler . Please refer to his perl program on generating  CPU Flame G
Read more

Java CPU Flame Graphs

Update (September 14, 2015): Java 8 Update 60 was released on August 18, 2015. There are some recent changes to "perf-map-agent". There is no longer a script named "perf-java" and you should use "bin/create-java-perf-map.sh " Brendan Gregg shared an exciting news in his Monitorama talk: The " JDK-8068945 " is fixed in Java 8 Update 60 Build 19 ! Without this fix, it was not possible to see full stack in Java with Linux perf_events and standard JDK (without any patches). For more information, see Brendan's Java CPU Flame Graphs page. The Problem with Java and Perf First of all, let's see what's the problem with using current latest Java and perf. For this example, I used the same program explained in my previous blog post regarding FlameGraphs . java org.wso2.example.JavaThreadCPUUsage.App Then I sampled on-CPU functions for Java program using perf. (See Brendan's Perf Examples ) sudo perf record -F 99 -g -
Read more