Release Note - WSO2 Stratos 2.0 Foundation - Beta 3

WSO2 Stratos2 team is pleased to announce the release of WSO2 Stratos 2.0
Beta 3.

WSO2 Stratos 2.0 Beta 3 comes with a very easy to configure demo setup that
can be run on Amazon EC2 and it can be found at [1]. Please refer to
the *Getting
Started* section of the *User Guide* for more information.

Please note that as of now this AMI [1] is only available in *Asia Pacific
(Singapore)* region. We are in the process of uploading the AMI into the
other regions.

Stratos 2.0 Command Line Interface (CLI) Tool can be downloaded from [2]
and Stratos 2.0 Documentation is available to be downloaded at [3].

WSO2 Stratos 2.0 is the next major version of WSO2 Stratos 1.x, the most
complete, enterprise-grade, open PaaS, with support for more core services
than any other available PaaS today.

Following are the Key features available in Stratos 2.0.

*Key Features *


   - Artifact Distribution Coordinator (ADC) with support for external Git
   and GitHub repositories.
   - Plug-able architecture support for adding new cartridges
   - Support for PHP and MySQL and WSO2 Carbon cartridges (AS, BPS etc)
   - Support for puppet based cartridge creation for WSO2 Carbon cartridges
   - Elastic Load Balancer (ELB) with Cartridge support
   - Multiple IaaS support (EC2, Openstack, vCloud) through jclouds APIs
   - Autoscaling into different IaaSes
   - S2 Cloud Controller
   - Git based deployment synchronizer
   - Interactive CLI Tool for tenants to manage subscriptions
   - UI for tenants to manage subscriptions
   - Custom domain mapping support
   - Documentation (User Guide, Architecture Guide)
   - Demo Ready Public Amazon EC2 Stratos 2.0 setup


The Beta release includes following improvements and bug fixes.
New Features

   - [SPI-111 <https://wso2.org/jira/browse/SPI-111>] - [CLI Tool]
   Remembering previous commands issued by User.
   - [SPI-218 <https://wso2.org/jira/browse/SPI-218>] - Add an option to
   manual pull the GIT repository

Improvements

   - [SPI-192 <https://wso2.org/jira/browse/SPI-192>] - Cartridge alias
   must be validated from the back-end service
   - [SPI-206 <https://wso2.org/jira/browse/SPI-206>] - For Multi-tenant
   WSO2 Carbon cartridges, we may have to allow the user to subscribe only once
   - [SPI-215 <https://wso2.org/jira/browse/SPI-215>] - Display minimum and
   maximum number of instances of the cartridge in GUI and CLI
   - [SPI-223 <https://wso2.org/jira/browse/SPI-223>] - Add cartridge alias
   in payload for logging in non carbon cartridges
   - [SPI-224 <https://wso2.org/jira/browse/SPI-224>] - Terminate the
   instances if they failed to join ELB, even after 'server_startup_delay' time
   - [SPI-234 <https://wso2.org/jira/browse/SPI-234>] - CLI Tool
   Improvements
   - [SPI-240 <https://wso2.org/jira/browse/SPI-240>] - CLI Tool should use
   a single '-' for short option names and '--' for longer option names
   - [SPI-241 <https://wso2.org/jira/browse/SPI-241>] - CLI Tool should use
   -u / --username and -p / --password approach and prompt for password if it
   isn't present. The characters at password prompt should be masked
   - [SPI-246 <https://wso2.org/jira/browse/SPI-246>] - Use a policy to
   define auto-scaling parameters
   - [SPI-248 <https://wso2.org/jira/browse/SPI-248>] - Use a datasource to
   access databases
   - [SPI-249 <https://wso2.org/jira/browse/SPI-249>] - Using prepared
   statements in SQL queries

Bug Fixes

   - [SPI-107 <https://wso2.org/jira/browse/SPI-107>] - When a new
   cartridge deployment fail, it should be gracefull handled
   - [SPI-146 <https://wso2.org/jira/browse/SPI-146>] - Subscription
   commands with No repository URLs should only be limit to DEMO setup
   - [SPI-188 <https://wso2.org/jira/browse/SPI-188>] - Warning in CC
   malformed image: null, but still the instance is getting started up
   - [SPI-198 <https://wso2.org/jira/browse/SPI-198>] - Non carbon
   cartridge logs should show the correct time in the log viewer
   - [SPI-208 <https://wso2.org/jira/browse/SPI-208>] - Stratos manager
   should be renamed with Stratos Controller in the layered architecture
   diagram
   - [SPI-210 <https://wso2.org/jira/browse/SPI-210>] - In Openstack setup
   AppServer left cluster infrequently
   - [SPI-216 <https://wso2.org/jira/browse/SPI-216>] - Issues in the Non
   Carbon Cartridge Init Script for Data Publisher
   - [SPI-217 <https://wso2.org/jira/browse/SPI-217>] - ServerKey is Set to
   Incorrect Value in Carbon.xml
   - [SPI-219 <https://wso2.org/jira/browse/SPI-219>] - Failed to retrieve
   pending instance count for domain error in ELB in S2 setup
   - [SPI-220 <https://wso2.org/jira/browse/SPI-220>] - Error: Failed to
   start an instance in ec2. Hence, will try to start in another IaaS if
   available.
   - [SPI-221 <https://wso2.org/jira/browse/SPI-221>] - Never ending
   joining messages printed in SC.
   - [SPI-222 <https://wso2.org/jira/browse/SPI-222>] - Issues with
   subscribing to AS multiple times per tenant.
   - [SPI-225 <https://wso2.org/jira/browse/SPI-225>] - ELB does not start
   expected node count defined in cartridges in S2.
   - [SPI-229 <https://wso2.org/jira/browse/SPI-229>] - Nullpointer
   Exception occurs in Openstack folsom
   - [SPI-231 <https://wso2.org/jira/browse/SPI-231>] - ERROR
   {org.apache.axis2.rpc.receivers.RPCMessageReceiver} - Method is not
   annotated as either http or provider method: public abstract
   com.google.common.util.concurrent.ListenableFuture
   org.jclouds.ec2.services.AvailabilityZoneAndRegionAsyncClient.descr
   - [SPI-233 <https://wso2.org/jira/browse/SPI-233>] - Unsubscription
   doesn't remove the group management agent from ELB and SC
   - [SPI-238 <https://wso2.org/jira/browse/SPI-238>] - UI doesn't allow me
   to specify minimum instance count as 0
   - [SPI-242 <https://wso2.org/jira/browse/SPI-242>] - Unsubscription
   doesn't remove the service topology
   - [SPI-243 <https://wso2.org/jira/browse/SPI-243>] - Incorrect data is
   displayed if subscribed using a previously used alias

Sub-task

   - [SPI-193 <https://wso2.org/jira/browse/SPI-193>] - External URL must
   be validated from the back-end and it should be checked based on a
   configuration property


Known Issues

Known issues of this release can be found at:
https://wso2.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=11005

Report Issues
You can report issues at [4].

Deliverables

[1] - Public Amazon EC2 Stratos 2.0 setup : *ami-bc2769ee* Asia Pacific
(Singapore) Region

[2] - CLI Tool :
http://dist.wso2.org/downloads/stratos/2.0.0/beta3/wso2s2cli-1.0.1.zip

[3] - Documentation :
http://dist.wso2.org/downloads/stratos/2.0.0/beta3/stratos2_docs.zip

[4] - Issue Tracker : https://wso2.org/jira/browse/SPI


*-- WSO2 Stratos2 Team --*
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to