Hi all,

As part of the WSO2 middleware installation artifacts, we are planning to
provide resources for WSO2 product deployments in Pivotal CloudFoundry
(PCF) [1] infrastructure. CloudFoundry (CF) BOSH [2] releases are expected
to be used for provisioning WSO2 product deployments in PCF.

For WSO2 Identity Server, we had implemented a CF BOSH release for single
node deployment, prior to this effort.

With the growing demand, it was decided to build upon the existing BOSH
release implementation, to construct CF BOSH releases for newly refined
WSO2 Identity Server deployment patterns. as described in [3].


Following are the changes and new features that were introduced when
constructing BOSH releases for WSO2 Identity Server deployment patterns,
using the existing BOSH implementation.

   1. *BOSH releases with High Availability (HA) clustered deployments*:
   Introduces HA clustered deployments for WSO2 Identity Server and Identity
   Server Analytics profiles as part of the deployment patterns.
   2. *Removal of bash scripts used for managing the BOSH release*: In the
   previous implementation, a set of bash scripts were used to manage the
   BOSH release. These scripts concentrated on managing the BOSH release in a
   local BOSH Lite [4] environment. Ideally, a BOSH release can be created and
   deployed on any infrastructure supported by CF BOSH. Upon analysis of
   existing BOSH release implementations, it was identified that general
   instructions for BOSH release management on any infrastructure have been
   provided in readme documentation. Hence, it was identified that users are
   more familiar with following instructions provided in readme documentation
   than using a script, for managing the BOSH release. As a result, it was
   decided to remove the bash scripts. Please see [5] for an example readme
   3. *Refinements to existing implementation*: The existing implementation
   of the BOSH release needed significant refinements. Please see [6] for
   GitHub issues specifying these refinements.
   4. Currently, the releases have been tested in a local BOSH environment
   (e.g. BOSH Lite). Testing on a cloud environment (e.g. an AWS BOSH
   environment) is in progress.

The following diagram depicts the BOSH release deployment of WSO2 Identity
Server deployment pattern 2 [7]. As depicted in the below diagram, during a
deployment the BOSH release, deployment manifest and the stemcell will be
provided to the BOSH Director (via the BOSH CLI), which in turn will
perform the deployment [8].

You will be able to try out the latest BOSH release for WSO2 Identity
Server deployment patterns from [9].

Your ideas and concerns are highly appreciated.

[1]: https://pivotal.io/platform
[2]: http://bosh.io/
[3]: https://docs.wso2.com/display/IS541/Deployment+Patterns
[4]: https://bosh.io/docs/bosh-lite
[5]: https://github.com/wso2/pivotal-cf-is/blob/master/patte
[6]: https://github.com/wso2/pivotal-cf-is/issues?q=is%3Aissue+is%3Aclosed
[7]: https://docs.wso2.com/display/IS541/Setting+Up+Deployment+Pattern+2
[8]: https://bosh.io/docs/deployment.html
[9]: https://github.com/wso2/pivotal-cf-is

Yours sincerely,

*Chiranga Alwis*
Software Engineer | WSO2

*Mobile : *+94775930497
*Email: *chirangaal...@gmail.com
*LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9
*Medium:* https://medium.com/@chirangaalwis

Architecture mailing list

Reply via email to