Hi Chamila, We had to bring back "vm_type" because it is needed for bare Docker scenario. Please refer to the other thread on wso2-dev list for a detailed explanation.
I've also fixed Puppet Lint issues in all modules. There are 2 warnings remaining though, as follows; WARNING: class inherits across module namespaces WARNING: line has more than 80 characters We knew about class inheritance issue from the beginning and decided to go with it anyway. Line max length of 80 is being enforced by Lint. But that won't have a big impact I think. Thanks. On Mon, May 9, 2016 at 10:31 PM, Chamila De Alwis <chami...@wso2.com> wrote: > Hi, > > Let's finalize the wso2/puppet-modules [1] 2.0.0 release. Following are > the features and fixes implemented in this release. > > > - > > Updated Hiera data hierarchy to include deployment platform > - > > Kubernetes based workflow supported, based on wso2/kubernetes-artifacts > - > > system_file_list to copy files with scope outside of CARBON_HOME > - > > Platform specific configuration data sets for Kubernetes > - > > Kubernetes deployment-ready Puppet modules > - > > Data sources matching a distributed set of Kubernetes MySQL Services > - > > Streamlined Default platform YAML configuration data > - > > Optional update flags to control product pack and JDK cleanup > - > > Minor fixes on the Hiera data > - > > Issues in YAML file formatting > - > > Puppet templates for identity.xml added to relevant products > - > > Proxy Port values assigned to different products are streamlined > - > > Hostname entries streamlined in default deployment platform data set > - > > Pass Through Port Mapping for WSO2 ESB > - > > Fixing Thrift Server IP configuration for WSO2 MB > - > > SecureVault parameters made optional > - > > WSO2 API Manager Gateway Manager-Worker separate profiles in Hieradata > - > > WSO2 PPaaS Puppet module and Hiera data removed > - > > vm_type level in the Hiera hierarchy removed > - Improve Puppet Vagrant setup to use PUPPET_HOME environment variable > > > The Hiera hierarchy is incompatible with the 1.x.x releases, as new levels > are introduced with the features. > > Following are the tasks that should be completed to finalize the release. > > - Smoke test each product on the default platform for the default > profile > - Smoke test each product on the Kubernetes platform with clustering > - Fix minor issues found during testing the products > - Consistent structure of the YAML file > - Style corrections > - Missing values that are crucial for product functionality from a > Smoke test's point of view > - Improve and verify the README content > > Please refrain from implementing new features that are not fixing critical > issues. > > You can use the following style guide [2] for YAML files in > wso2/puppet-modules to streamline and format any YAML files that are > inconsistent. > > Furthermore, please share details on the work you are doing and update as > they are completed. > > [1] - https://github.com/wso2/puppet-modules > [2] - > https://docs.google.com/document/d/14fblI46ztAwFoq0YR5HjFeloj1jFVBxnuAl-aZ4Ropk/edit?usp=sharing > > > Regards, > Chamila de Alwis > Committer and PMC Member - Apache Stratos > Software Engineer | WSO2 | +94772207163 > Blog: code.chamiladealwis.com > > > -- Akila Ravihansa Perera WSO2 Inc.; http://wso2.com/ Blog: http://ravihansa3000.blogspot.com
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
