[Dev] WSO2 PPaaS v4.1.0-ALPHA released

2015-09-08 Thread Akila Ravihansa Perera 
Hi,

The WSO2 Private PaaS community is pleased to announce the release of the
WSO2 Private PaaS 4.1.0-ALPHA. This release includes following bug-fixes,
improvements and features.

Known Issues

   - [PAAS-77 ] - Validated result of
   cartridge subscription should display on web console
   - [PAAS-83 ] - BAM metering
   dashboard error
   - [PAAS-87 ] - Load Balancer
   Rewrites Location Headers Irrespective of Location Header URL Host
   - [PAAS-88 ] - Multi-tenant
   cartridge doesn't clean up the GIT repository inside the Cartridge
   instances when unsubscribing
   - [PAAS-92 ] - Subscribed
   cartridge groups show all the subscribed cartridge informations instead of
   group's information
   - [PAAS-93 ] - CEP stat publisher
   have a hardcoded username and paasword
   - [PAAS-104 ] - PHP, Tomcat and
   MySQL cartridges are not working properly
   - [PAAS-107 ] - Filter logs in
   Centralized Log Viewer dashboard according to services
   - [PAAS-108 ] - http > https
   redirection does not work in Load Balancer
   - [PAAS-112 ] - BAM dashboard
   compilation error
   - [PAAS-123 ] - Private PaaS
   Metering Toolbox having hardcoded credentials
   - [PAAS-126 ] - Unable to trigger
   TenantCreatedEvent when the tenant is not there in TenantManager
   - [PAAS-148 ] - Production Setup
   - Stratos instances spawn exceeding max limit
   - [PAAS-152 ] - Stratos LB mix up
   members of different multi-tenant clusters in 10x10 concurrency
   - [PAAS-155 ] - Server is started
   twice in cartridge instance
   - [PAAS-158 ] - Instances are not
   getting removed from the topology
   - [PAAS-164 ] - Logs do not print
   any information if the activemq instances are down, while the stratos
   services are running
   - [PAAS-167 ] - CEP sends very
   large values for gradient and second derivative of load average
   - [PAAS-169 ] - Member
   termination flow retry in the case of the failure
   - [PAAS-176 ] - CEP went OOM
   after long running
   - [PAAS-179 ] - The Tomcat
   catridge deployed is having 0 running instances
   - [PAAS-198 ] - Cluster not
   scaling down - member stats contexts are not removed from AS when an
   obsolete member is getting timeout
   - [PAAS-199 ] - ReadyToShutdown
   Members are not getting removed from topology for a long time

Improvements

   - [PAAS-50 ] - Handle LB member
   termination event
   - [PAAS-168 ] - Calculate more
   accurate memory consumption and load average values
   - [PAAS-173 ] - Applying Secure
   Vault to passwords used in Cartridge Agent's stratos.sh file
   - [PAAS-185 ] - Support graceful
   shutdown for the cartridges when termination happens
   - [PAAS-202 ] - Refactor POM
   structure of product-private-paas

New Features

   - [PAAS-84 ] - Domain Mapping
   Improvements

Tasks

   - [PAAS-194 ] - Create IS VM
   Cartidge
   - [PAAS-216 ] - Create
   API-Manager 1.9.0 Cartridge
   - [PAAS-217 ] - Create Identity
   Server (IS) 5.0.0 Cartridge
   - [PAAS-220 ] - Create
   Application Server (AS) 5.2.1 Cartridge
   - [PAAS-236 ] - Upgrade
   automation framework engine version to 4.4.2

Sub-tasks

   - [PAAS-192 ] - Create ESB 4.8.1
   VM Cartridge
   - [PAAS-193 ] - Create AS 5.2.1
   VM Cartridge
   - [PAAS-203 ] - Create IS 5.0.0
   VM Cartridge
   - [PAAS-204 ] - Create API-M
   1.9.0 VM Cartridge
   - [PAAS-209 ] - Create ESB 4.8.1
   Docker Image
   - [PAAS-210 ] - Create AS 5.2.1
   Docker Image
   - [PAAS-211

Re: [Dev] WSO2 PPaaS v4.1.0-ALPHA released

2015-09-08 Thread Imesh Gunaratne 
Hi,

Please note that the list of issues mentioned above under "Known Issues"
are actually bugs that were fixed in this release and they are not known
issues.

Known issues can be found below:

   - [PAAS-213 ] - Autoscaling is
   not working in super-tenant if an artifact repo is given
   - [PAAS-226 ] - Application Sign
   Up is Enabled before Activating the Application
   - [PAAS-228 ] - Applications can
   be un-deployed even there is tenant application sign ups
   - [PAAS-229 ] - Tenant can
   un-deploy a multi tenant application
   - [PAAS-230 ] - Cannot Un-sign up
   from Management Console UI
   - [PAAS-231 ] - Remove sign up
   does not completely remove all the artifacts
   - [PAAS-232 ] - Artifact git repo
   password cannot have @ sign
   - [PAAS-233 ] - PCA git repo
   artifact delete does delete the artifact from git
   - [PAAS-234 ] - PPaaS 4.1.0
   Carbon UI has Stratos branding
   - [PAAS-235 ] - Application name
   cannot have lengthy strings


JIRA Query:
project = PAAS AND resolution = Unresolved AND affectedVersion =
"4.1.0-Alpha"

Thanks

On Tue, Sep 8, 2015 at 2:59 PM, Akila Ravihansa Perera 
wrote:

> Hi,
>
> The WSO2 Private PaaS community is pleased to announce the release of the
> WSO2 Private PaaS 4.1.0-ALPHA. This release includes following bug-fixes,
> improvements and features.
>
> Known Issues
>
>- [PAAS-77 ] - Validated result
>of cartridge subscription should display on web console
>- [PAAS-83 ] - BAM metering
>dashboard error
>- [PAAS-87 ] - Load Balancer
>Rewrites Location Headers Irrespective of Location Header URL Host
>- [PAAS-88 ] - Multi-tenant
>cartridge doesn't clean up the GIT repository inside the Cartridge
>instances when unsubscribing
>- [PAAS-92 ] - Subscribed
>cartridge groups show all the subscribed cartridge informations instead of
>group's information
>- [PAAS-93 ] - CEP stat
>publisher have a hardcoded username and paasword
>- [PAAS-104 ] - PHP, Tomcat and
>MySQL cartridges are not working properly
>- [PAAS-107 ] - Filter logs in
>Centralized Log Viewer dashboard according to services
>- [PAAS-108 ] - http > https
>redirection does not work in Load Balancer
>- [PAAS-112 ] - BAM dashboard
>compilation error
>- [PAAS-123 ] - Private PaaS
>Metering Toolbox having hardcoded credentials
>- [PAAS-126 ] - Unable to
>trigger TenantCreatedEvent when the tenant is not there in TenantManager
>- [PAAS-148 ] - Production
>Setup - Stratos instances spawn exceeding max limit
>- [PAAS-152 ] - Stratos LB mix
>up members of different multi-tenant clusters in 10x10 concurrency
>- [PAAS-155 ] - Server is
>started twice in cartridge instance
>- [PAAS-158 ] - Instances are
>not getting removed from the topology
>- [PAAS-164 ] - Logs do not
>print any information if the activemq instances are down, while the stratos
>services are running
>- [PAAS-167 ] - CEP sends very
>large values for gradient and second derivative of load average
>- [PAAS-169 ] - Member
>termination flow retry in the case of the failure
>- [PAAS-176 ] - CEP went OOM
>after long running
>- [PAAS-179 ] - The Tomcat
>catridge deployed is having 0 running instances
>- [PAAS-198 ] - Cluster not
>scaling down - member stats contexts are not removed from AS when an
>obsolete member is getting timeout
>- [PAAS-199 ] - ReadyToShutdown
>Members are not getting removed from topology for a long time
>
> Improvements
>
>- [PAAS-50 ] - Handle LB member
>termination event
>- [PAAS-168