Re: [Dev] [puppet] Setting up puppet home from script
Hi Vishanth, I have fixed the issue. Please take a pull. Regards, Anuruddha On Wed, Sep 21, 2016 at 10:38 PM, Vishanth Balasubramaniam < vishan...@wso2.com> wrote: > Hi, > > That probably be the reason. And yes it should be fixed. > > Regards, > Vishanth > > On Wed, Sep 21, 2016 at 11:06 AM, Anuruddha Liyanarachchi < > anurudd...@wso2.com> wrote: > >> Hi Vishanth, >> >> "Declare -A" option is not working in mac os because bash version of mac >> os is not supporting declaring associate arrays [1]. Associative array >> support is available from shell version 4 and upwards, and mac os shell >> version is 3.2.57. >> >> I am currently looking into an alternative method without using >> associative arrays. >> >> [1] http://stackoverflow.com/questions/6047648/bash-4-associ >> ative-arrays-error-declare-a-invalid-option >> >> On Tue, Sep 20, 2016 at 5:23 PM, Vishanth Balasubramaniam < >> vishan...@wso2.com> wrote: >> >>> Hi Akila, >>> >>> With those changes, whatever product I specify it is setting up wso2das. >>> >>> For example, when I give *./setup.sh -p esb*, it is setting up wso2das >>> module. >>> >>> Probably the declaration is not properly functioning. >>> >>> Regards, >>> Vishanth >>> >>> On Mon, Sep 19, 2016 at 1:59 PM, Akila Ravihansa Perera < >>> raviha...@wso2.com> wrote: >>> Hi, I've improved the Puppet-Home setup script by introducing two map; product_code_to_name_map and product_name_to_module_repo_map. With this approach we can handle cases where product name and product code is different. For eg: API Manager code is "apim" while product name is "wso2am". Also I've added platform support for Hiera data as well. You can use "setup.sh -p -l " to setup Puppet Home with Hiera data for a specific platform. If none given it will default to 'default' platform. The relevant platform repo for the given product should contain a hieradata directory which will be symlink'd to PUPPET_HOME/hieradata. For eg: wso2esb kubernetes platform - https://github.com/wso2/kube rnetes-esb should contain a "hieradata" directory at the repo root level; https://github.com/wso2/kubernetes-esb/tree/master/hieradata Thanks. On Thu, Sep 8, 2016 at 9:59 AM, Anuruddha Liyanarachchi < anurudd...@wso2.com> wrote: > Hi Pubudu, > > +1 for the platform support. > I will add the platform support once we finalized the platform > hieradata structure. > > On Thu, Sep 8, 2016 at 3:44 AM, Imesh Gunaratne > wrote: > >> >> >> On Wed, Sep 7, 2016 at 10:09 PM, Pubudu Gunatilaka >> wrote: >> >>> >>> I think we need to include the platform as well. If we consider the >>> big picture, ideally any user should be able to use this script and >>> create >>> a puppet home for building docker images for Kubernetes, Mesos, or any >>> other platforms. As we have separate repos for platform hieradata, we >>> need >>> to copy those hieradata to the puppet home repo. >>> >> >> +1 >> >> >>> >>> Thank you! >>> >>> >>> On Wed, Sep 7, 2016 at 8:21 PM, Imesh Gunaratne >>> wrote: >>> On Wed, Sep 7, 2016 at 6:24 PM, Anuruddha Liyanarachchi < anurudd...@wso2.com> wrote: > Hi Imesh, > > I have now added the ability to configure multiple products using > comma separated product list. > Also included '-p all' option which configures all the products. > > Ex: ./setup.sh -p as > Ex: ./setup.sh -p as,esb,bps > Ex: ./setup.sh -p all > Great! Nice to hear that! > > On Wed, Sep 7, 2016 at 12:46 AM, Imesh Gunaratne > wrote: > >> Great work Anuruddha! The bash script works well! >> >> Shall we add the ability to install multiple product modules in >> one go? Maybe we can use a comma separated product list with -p. >> >> Thanks >> >> On Tue, Sep 6, 2016 at 6:26 PM, Anuruddha Liyanarachchi < >> anurudd...@wso2.com> wrote: >> >>> Hi, >>> >>> We have created separate GitHub repos for Puppet modules so >>> that the Puppet module can be shipped as part of a product release. >>> >>> Since modules are distributed we have introduced a script to >>> generate PUPPET_HOME. The script will work as following. >>> >>> 1. Check puppet_home folder exists. >>> >>> 2. Create folder structure required for puppet_home. >>> ├── hiera.yaml >>> ├── hieradata >>> ├── manifests >>> └── modules >>> >>> 3. Create a symlink to manifest/site.pp file. >>> >>> 4. Clone wso2base puppet module into /modules >
Re: [Dev] [puppet] Setting up puppet home from script
Hi, That probably be the reason. And yes it should be fixed. Regards, Vishanth On Wed, Sep 21, 2016 at 11:06 AM, Anuruddha Liyanarachchi < anurudd...@wso2.com> wrote: > Hi Vishanth, > > "Declare -A" option is not working in mac os because bash version of mac > os is not supporting declaring associate arrays [1]. Associative array > support is available from shell version 4 and upwards, and mac os shell > version is 3.2.57. > > I am currently looking into an alternative method without using > associative arrays. > > [1] http://stackoverflow.com/questions/6047648/bash-4- > associative-arrays-error-declare-a-invalid-option > > On Tue, Sep 20, 2016 at 5:23 PM, Vishanth Balasubramaniam < > vishan...@wso2.com> wrote: > >> Hi Akila, >> >> With those changes, whatever product I specify it is setting up wso2das. >> >> For example, when I give *./setup.sh -p esb*, it is setting up wso2das >> module. >> >> Probably the declaration is not properly functioning. >> >> Regards, >> Vishanth >> >> On Mon, Sep 19, 2016 at 1:59 PM, Akila Ravihansa Perera < >> raviha...@wso2.com> wrote: >> >>> Hi, >>> >>> I've improved the Puppet-Home setup script by introducing two map; >>> product_code_to_name_map and product_name_to_module_repo_map. With this >>> approach we can handle cases where product name and product code is >>> different. For eg: API Manager code is "apim" while product name is >>> "wso2am". >>> >>> Also I've added platform support for Hiera data as well. You can use >>> "setup.sh -p -l " to setup Puppet Home with >>> Hiera data for a specific platform. If none given it will default to >>> 'default' platform. >>> >>> The relevant platform repo for the given product should contain a >>> hieradata directory which will be symlink'd to PUPPET_HOME/hieradata. For >>> eg: wso2esb kubernetes platform - https://github.com/wso2/kubernetes-esb >>> should >>> contain a "hieradata" directory at the repo root level; >>> https://github.com/wso2/kubernetes-esb/tree/master/hieradata >>> >>> Thanks. >>> >>> On Thu, Sep 8, 2016 at 9:59 AM, Anuruddha Liyanarachchi < >>> anurudd...@wso2.com> wrote: >>> Hi Pubudu, +1 for the platform support. I will add the platform support once we finalized the platform hieradata structure. On Thu, Sep 8, 2016 at 3:44 AM, Imesh Gunaratne wrote: > > > On Wed, Sep 7, 2016 at 10:09 PM, Pubudu Gunatilaka > wrote: > >> >> I think we need to include the platform as well. If we consider the >> big picture, ideally any user should be able to use this script and >> create >> a puppet home for building docker images for Kubernetes, Mesos, or any >> other platforms. As we have separate repos for platform hieradata, we >> need >> to copy those hieradata to the puppet home repo. >> > > +1 > > >> >> Thank you! >> >> >> On Wed, Sep 7, 2016 at 8:21 PM, Imesh Gunaratne >> wrote: >> >>> >>> >>> On Wed, Sep 7, 2016 at 6:24 PM, Anuruddha Liyanarachchi < >>> anurudd...@wso2.com> wrote: >>> Hi Imesh, I have now added the ability to configure multiple products using comma separated product list. Also included '-p all' option which configures all the products. Ex: ./setup.sh -p as Ex: ./setup.sh -p as,esb,bps Ex: ./setup.sh -p all >>> >>> Great! >>> Nice to hear that! >>> On Wed, Sep 7, 2016 at 12:46 AM, Imesh Gunaratne wrote: > Great work Anuruddha! The bash script works well! > > Shall we add the ability to install multiple product modules in > one go? Maybe we can use a comma separated product list with -p. > > Thanks > > On Tue, Sep 6, 2016 at 6:26 PM, Anuruddha Liyanarachchi < > anurudd...@wso2.com> wrote: > >> Hi, >> >> We have created separate GitHub repos for Puppet modules so that >> the Puppet module can be shipped as part of a product release. >> >> Since modules are distributed we have introduced a script to >> generate PUPPET_HOME. The script will work as following. >> >> 1. Check puppet_home folder exists. >> >> 2. Create folder structure required for puppet_home. >> ├── hiera.yaml >> ├── hieradata >> ├── manifests >> └── modules >> >> 3. Create a symlink to manifest/site.pp file. >> >> 4. Clone wso2base puppet module into /modules >> directory. >> >> 5. Create a symlink to wso2base common.yaml hiera-file. >> >>> /modules/wso2base/hieradata/wso2/common.yaml -> >>> /hieradata/dev/wso2/ >> >> >> 6. Clone wso2 puppet module into /modules >> directory. >> >> 7.
Re: [Dev] [puppet] Setting up puppet home from script
Hi Vishanth, "Declare -A" option is not working in mac os because bash version of mac os is not supporting declaring associate arrays [1]. Associative array support is available from shell version 4 and upwards, and mac os shell version is 3.2.57. I am currently looking into an alternative method without using associative arrays. [1] http://stackoverflow.com/questions/6047648/bash-4-associative-arrays-error-declare-a-invalid-option On Tue, Sep 20, 2016 at 5:23 PM, Vishanth Balasubramaniam < vishan...@wso2.com> wrote: > Hi Akila, > > With those changes, whatever product I specify it is setting up wso2das. > > For example, when I give *./setup.sh -p esb*, it is setting up wso2das > module. > > Probably the declaration is not properly functioning. > > Regards, > Vishanth > > On Mon, Sep 19, 2016 at 1:59 PM, Akila Ravihansa Perera < > raviha...@wso2.com> wrote: > >> Hi, >> >> I've improved the Puppet-Home setup script by introducing two map; >> product_code_to_name_map and product_name_to_module_repo_map. With this >> approach we can handle cases where product name and product code is >> different. For eg: API Manager code is "apim" while product name is >> "wso2am". >> >> Also I've added platform support for Hiera data as well. You can use >> "setup.sh -p -l " to setup Puppet Home with >> Hiera data for a specific platform. If none given it will default to >> 'default' platform. >> >> The relevant platform repo for the given product should contain a >> hieradata directory which will be symlink'd to PUPPET_HOME/hieradata. For >> eg: wso2esb kubernetes platform - https://github.com/wso2/kubernetes-esb >> should >> contain a "hieradata" directory at the repo root level; >> https://github.com/wso2/kubernetes-esb/tree/master/hieradata >> >> Thanks. >> >> On Thu, Sep 8, 2016 at 9:59 AM, Anuruddha Liyanarachchi < >> anurudd...@wso2.com> wrote: >> >>> Hi Pubudu, >>> >>> +1 for the platform support. >>> I will add the platform support once we finalized the platform >>> hieradata structure. >>> >>> On Thu, Sep 8, 2016 at 3:44 AM, Imesh Gunaratne wrote: >>> On Wed, Sep 7, 2016 at 10:09 PM, Pubudu Gunatilaka wrote: > > I think we need to include the platform as well. If we consider the > big picture, ideally any user should be able to use this script and create > a puppet home for building docker images for Kubernetes, Mesos, or any > other platforms. As we have separate repos for platform hieradata, we > need > to copy those hieradata to the puppet home repo. > +1 > > Thank you! > > > On Wed, Sep 7, 2016 at 8:21 PM, Imesh Gunaratne > wrote: > >> >> >> On Wed, Sep 7, 2016 at 6:24 PM, Anuruddha Liyanarachchi < >> anurudd...@wso2.com> wrote: >> >>> Hi Imesh, >>> >>> I have now added the ability to configure multiple products using >>> comma separated product list. >>> Also included '-p all' option which configures all the products. >>> >>> Ex: ./setup.sh -p as >>> Ex: ./setup.sh -p as,esb,bps >>> Ex: ./setup.sh -p all >>> >> >> Great! >> Nice to hear that! >> >>> >>> On Wed, Sep 7, 2016 at 12:46 AM, Imesh Gunaratne >>> wrote: >>> Great work Anuruddha! The bash script works well! Shall we add the ability to install multiple product modules in one go? Maybe we can use a comma separated product list with -p. Thanks On Tue, Sep 6, 2016 at 6:26 PM, Anuruddha Liyanarachchi < anurudd...@wso2.com> wrote: > Hi, > > We have created separate GitHub repos for Puppet modules so that > the Puppet module can be shipped as part of a product release. > > Since modules are distributed we have introduced a script to > generate PUPPET_HOME. The script will work as following. > > 1. Check puppet_home folder exists. > > 2. Create folder structure required for puppet_home. > ├── hiera.yaml > ├── hieradata > ├── manifests > └── modules > > 3. Create a symlink to manifest/site.pp file. > > 4. Clone wso2base puppet module into /modules > directory. > > 5. Create a symlink to wso2base common.yaml hiera-file. > >> /modules/wso2base/hieradata/wso2/common.yaml -> >> /hieradata/dev/wso2/ > > > 6. Clone wso2 puppet module into /modules > directory. > > 7. Create a symlink to wso2 hiera-files. > >> /wso2/hieradata/dev/wso2/wso2 >> -> ../hieradata/dev/wso2/ > > > Once the setup.sh completes, users can copy product pack and jdk > distribution for relevant folders and run vagrant setup against > above-created puppet home. >
Re: [Dev] [puppet] Setting up puppet home from script
Hi Akila, With those changes, whatever product I specify it is setting up wso2das. For example, when I give *./setup.sh -p esb*, it is setting up wso2das module. Probably the declaration is not properly functioning. Regards, Vishanth On Mon, Sep 19, 2016 at 1:59 PM, Akila Ravihansa Perera wrote: > Hi, > > I've improved the Puppet-Home setup script by introducing two map; > product_code_to_name_map and product_name_to_module_repo_map. With this > approach we can handle cases where product name and product code is > different. For eg: API Manager code is "apim" while product name is > "wso2am". > > Also I've added platform support for Hiera data as well. You can use > "setup.sh -p -l " to setup Puppet Home with > Hiera data for a specific platform. If none given it will default to > 'default' platform. > > The relevant platform repo for the given product should contain a > hieradata directory which will be symlink'd to PUPPET_HOME/hieradata. For > eg: wso2esb kubernetes platform - https://github.com/wso2/kubernetes-esb > should > contain a "hieradata" directory at the repo root level; > https://github.com/wso2/kubernetes-esb/tree/master/hieradata > > Thanks. > > On Thu, Sep 8, 2016 at 9:59 AM, Anuruddha Liyanarachchi < > anurudd...@wso2.com> wrote: > >> Hi Pubudu, >> >> +1 for the platform support. >> I will add the platform support once we finalized the platform >> hieradata structure. >> >> On Thu, Sep 8, 2016 at 3:44 AM, Imesh Gunaratne wrote: >> >>> >>> >>> On Wed, Sep 7, 2016 at 10:09 PM, Pubudu Gunatilaka >>> wrote: >>> I think we need to include the platform as well. If we consider the big picture, ideally any user should be able to use this script and create a puppet home for building docker images for Kubernetes, Mesos, or any other platforms. As we have separate repos for platform hieradata, we need to copy those hieradata to the puppet home repo. >>> >>> +1 >>> >>> Thank you! On Wed, Sep 7, 2016 at 8:21 PM, Imesh Gunaratne wrote: > > > On Wed, Sep 7, 2016 at 6:24 PM, Anuruddha Liyanarachchi < > anurudd...@wso2.com> wrote: > >> Hi Imesh, >> >> I have now added the ability to configure multiple products using >> comma separated product list. >> Also included '-p all' option which configures all the products. >> >> Ex: ./setup.sh -p as >> Ex: ./setup.sh -p as,esb,bps >> Ex: ./setup.sh -p all >> > > Great! > Nice to hear that! > >> >> On Wed, Sep 7, 2016 at 12:46 AM, Imesh Gunaratne >> wrote: >> >>> Great work Anuruddha! The bash script works well! >>> >>> Shall we add the ability to install multiple product modules in one >>> go? Maybe we can use a comma separated product list with -p. >>> >>> Thanks >>> >>> On Tue, Sep 6, 2016 at 6:26 PM, Anuruddha Liyanarachchi < >>> anurudd...@wso2.com> wrote: >>> Hi, We have created separate GitHub repos for Puppet modules so that the Puppet module can be shipped as part of a product release. Since modules are distributed we have introduced a script to generate PUPPET_HOME. The script will work as following. 1. Check puppet_home folder exists. 2. Create folder structure required for puppet_home. ├── hiera.yaml ├── hieradata ├── manifests └── modules 3. Create a symlink to manifest/site.pp file. 4. Clone wso2base puppet module into /modules directory. 5. Create a symlink to wso2base common.yaml hiera-file. > /modules/wso2base/hieradata/wso2/common.yaml -> > /hieradata/dev/wso2/ 6. Clone wso2 puppet module into /modules directory. 7. Create a symlink to wso2 hiera-files. > /wso2/hieradata/dev/wso2/wso2 -> > ../hieradata/dev/wso2/ Once the setup.sh completes, users can copy product pack and jdk distribution for relevant folders and run vagrant setup against above-created puppet home. We are planning to automate the copying of product pack, jdk distribution and starting vagrant setup as well. Setup.sh can be found at [1]. Please share your suggestions towards this approach. [1] https://github.com/wso2/puppet-common/blob/master/setup.sh -- *Thanks and Regards,* Anuruddha Lanka Liyanarachchi Software Engineer - WSO2 Mobile : +94 (0) 712762611 Tel : +94 112 145 345 a nurudd...@wso2.com >>> >>> >>> >>> -- >>> *Imesh Gunaratne* >>> Software Architect >>> WSO2 Inc: http://wso2.com >>> T: +94 11 214 5345 M: +94 77
Re: [Dev] [puppet] Setting up puppet home from script
Hi, I've improved the Puppet-Home setup script by introducing two map; product_code_to_name_map and product_name_to_module_repo_map. With this approach we can handle cases where product name and product code is different. For eg: API Manager code is "apim" while product name is "wso2am". Also I've added platform support for Hiera data as well. You can use "setup.sh -p -l " to setup Puppet Home with Hiera data for a specific platform. If none given it will default to 'default' platform. The relevant platform repo for the given product should contain a hieradata directory which will be symlink'd to PUPPET_HOME/hieradata. For eg: wso2esb kubernetes platform - https://github.com/wso2/kubernetes-esb should contain a "hieradata" directory at the repo root level; https://github.com/ wso2/kubernetes-esb/tree/master/hieradata Thanks. On Thu, Sep 8, 2016 at 9:59 AM, Anuruddha Liyanarachchi wrote: > Hi Pubudu, > > +1 for the platform support. > I will add the platform support once we finalized the platform > hieradata structure. > > On Thu, Sep 8, 2016 at 3:44 AM, Imesh Gunaratne wrote: > >> >> >> On Wed, Sep 7, 2016 at 10:09 PM, Pubudu Gunatilaka >> wrote: >> >>> >>> I think we need to include the platform as well. If we consider the big >>> picture, ideally any user should be able to use this script and create a >>> puppet home for building docker images for Kubernetes, Mesos, or any other >>> platforms. As we have separate repos for platform hieradata, we need to >>> copy those hieradata to the puppet home repo. >>> >> >> +1 >> >> >>> >>> Thank you! >>> >>> >>> On Wed, Sep 7, 2016 at 8:21 PM, Imesh Gunaratne wrote: >>> On Wed, Sep 7, 2016 at 6:24 PM, Anuruddha Liyanarachchi < anurudd...@wso2.com> wrote: > Hi Imesh, > > I have now added the ability to configure multiple products using > comma separated product list. > Also included '-p all' option which configures all the products. > > Ex: ./setup.sh -p as > Ex: ./setup.sh -p as,esb,bps > Ex: ./setup.sh -p all > Great! Nice to hear that! > > On Wed, Sep 7, 2016 at 12:46 AM, Imesh Gunaratne > wrote: > >> Great work Anuruddha! The bash script works well! >> >> Shall we add the ability to install multiple product modules in one >> go? Maybe we can use a comma separated product list with -p. >> >> Thanks >> >> On Tue, Sep 6, 2016 at 6:26 PM, Anuruddha Liyanarachchi < >> anurudd...@wso2.com> wrote: >> >>> Hi, >>> >>> We have created separate GitHub repos for Puppet modules so that >>> the Puppet module can be shipped as part of a product release. >>> >>> Since modules are distributed we have introduced a script to >>> generate PUPPET_HOME. The script will work as following. >>> >>> 1. Check puppet_home folder exists. >>> >>> 2. Create folder structure required for puppet_home. >>> ├── hiera.yaml >>> ├── hieradata >>> ├── manifests >>> └── modules >>> >>> 3. Create a symlink to manifest/site.pp file. >>> >>> 4. Clone wso2base puppet module into /modules >>> directory. >>> >>> 5. Create a symlink to wso2base common.yaml hiera-file. >>> /modules/wso2base/hieradata/wso2/common.yaml -> /hieradata/dev/wso2/ >>> >>> >>> 6. Clone wso2 puppet module into /modules >>> directory. >>> >>> 7. Create a symlink to wso2 hiera-files. >>> /wso2/hieradata/dev/wso2/wso2 -> ../hieradata/dev/wso2/ >>> >>> >>> Once the setup.sh completes, users can copy product pack and jdk >>> distribution for relevant folders and run vagrant setup against >>> above-created puppet home. >>> >>> We are planning to automate the copying of product pack, jdk >>> distribution and starting vagrant setup as well. >>> >>> Setup.sh can be found at [1]. Please share your suggestions towards >>> this approach. >>> >>> [1] https://github.com/wso2/puppet-common/blob/master/setup.sh >>> >>> -- >>> *Thanks and Regards,* >>> Anuruddha Lanka Liyanarachchi >>> Software Engineer - WSO2 >>> Mobile : +94 (0) 712762611 >>> Tel : +94 112 145 345 >>> a nurudd...@wso2.com >>> >> >> >> >> -- >> *Imesh Gunaratne* >> Software Architect >> WSO2 Inc: http://wso2.com >> T: +94 11 214 5345 M: +94 77 374 2057 >> W: https://medium.com/@imesh TW: @imesh >> lean. enterprise. middleware >> >> > > > -- > *Thanks and Regards,* > Anuruddha Lanka Liyanarachchi > Software Engineer - WSO2 > Mobile : +94 (0) 712762611 > Tel : +94 112 145 345 > a nurudd...@wso2.com > -- *Imesh Gunaratne* Software Architect WSO2 Inc: http://wso2.com T: +94 11 214 5345 M: +94 77 374 2057 W: https://medium.com/@ime
Re: [Dev] [puppet] Setting up puppet home from script
Hi Pubudu, +1 for the platform support. I will add the platform support once we finalized the platform hieradata structure. On Thu, Sep 8, 2016 at 3:44 AM, Imesh Gunaratne wrote: > > > On Wed, Sep 7, 2016 at 10:09 PM, Pubudu Gunatilaka > wrote: > >> >> I think we need to include the platform as well. If we consider the big >> picture, ideally any user should be able to use this script and create a >> puppet home for building docker images for Kubernetes, Mesos, or any other >> platforms. As we have separate repos for platform hieradata, we need to >> copy those hieradata to the puppet home repo. >> > > +1 > > >> >> Thank you! >> >> >> On Wed, Sep 7, 2016 at 8:21 PM, Imesh Gunaratne wrote: >> >>> >>> >>> On Wed, Sep 7, 2016 at 6:24 PM, Anuruddha Liyanarachchi < >>> anurudd...@wso2.com> wrote: >>> Hi Imesh, I have now added the ability to configure multiple products using comma separated product list. Also included '-p all' option which configures all the products. Ex: ./setup.sh -p as Ex: ./setup.sh -p as,esb,bps Ex: ./setup.sh -p all >>> >>> Great! >>> Nice to hear that! >>> On Wed, Sep 7, 2016 at 12:46 AM, Imesh Gunaratne wrote: > Great work Anuruddha! The bash script works well! > > Shall we add the ability to install multiple product modules in one > go? Maybe we can use a comma separated product list with -p. > > Thanks > > On Tue, Sep 6, 2016 at 6:26 PM, Anuruddha Liyanarachchi < > anurudd...@wso2.com> wrote: > >> Hi, >> >> We have created separate GitHub repos for Puppet modules so that the >> Puppet module can be shipped as part of a product release. >> >> Since modules are distributed we have introduced a script to generate >> PUPPET_HOME. The script will work as following. >> >> 1. Check puppet_home folder exists. >> >> 2. Create folder structure required for puppet_home. >> ├── hiera.yaml >> ├── hieradata >> ├── manifests >> └── modules >> >> 3. Create a symlink to manifest/site.pp file. >> >> 4. Clone wso2base puppet module into /modules >> directory. >> >> 5. Create a symlink to wso2base common.yaml hiera-file. >> >>> /modules/wso2base/hieradata/wso2/common.yaml -> >>> /hieradata/dev/wso2/ >> >> >> 6. Clone wso2 puppet module into /modules >> directory. >> >> 7. Create a symlink to wso2 hiera-files. >> >>> /wso2/hieradata/dev/wso2/wso2 -> >>> ../hieradata/dev/wso2/ >> >> >> Once the setup.sh completes, users can copy product pack and jdk >> distribution for relevant folders and run vagrant setup against >> above-created puppet home. >> >> We are planning to automate the copying of product pack, jdk >> distribution and starting vagrant setup as well. >> >> Setup.sh can be found at [1]. Please share your suggestions towards >> this approach. >> >> [1] https://github.com/wso2/puppet-common/blob/master/setup.sh >> >> -- >> *Thanks and Regards,* >> Anuruddha Lanka Liyanarachchi >> Software Engineer - WSO2 >> Mobile : +94 (0) 712762611 >> Tel : +94 112 145 345 >> a nurudd...@wso2.com >> > > > > -- > *Imesh Gunaratne* > Software Architect > WSO2 Inc: http://wso2.com > T: +94 11 214 5345 M: +94 77 374 2057 > W: https://medium.com/@imesh TW: @imesh > lean. enterprise. middleware > > -- *Thanks and Regards,* Anuruddha Lanka Liyanarachchi Software Engineer - WSO2 Mobile : +94 (0) 712762611 Tel : +94 112 145 345 a nurudd...@wso2.com >>> >>> >>> >>> -- >>> *Imesh Gunaratne* >>> Software Architect >>> WSO2 Inc: http://wso2.com >>> T: +94 11 214 5345 M: +94 77 374 2057 >>> W: https://medium.com/@imesh TW: @imesh >>> lean. enterprise. middleware >>> >>> >> >> >> -- >> *Pubudu Gunatilaka* >> Committer and PMC Member - Apache Stratos >> Software Engineer >> WSO2, Inc.: http://wso2.com >> mobile : +94774078049 <%2B94772207163> >> >> > > > -- > *Imesh Gunaratne* > Software Architect > WSO2 Inc: http://wso2.com > T: +94 11 214 5345 M: +94 77 374 2057 > W: https://medium.com/@imesh TW: @imesh > lean. enterprise. middleware > > -- *Thanks and Regards,* Anuruddha Lanka Liyanarachchi Software Engineer - WSO2 Mobile : +94 (0) 712762611 Tel : +94 112 145 345 a nurudd...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [puppet] Setting up puppet home from script
On Wed, Sep 7, 2016 at 10:09 PM, Pubudu Gunatilaka wrote: > > I think we need to include the platform as well. If we consider the big > picture, ideally any user should be able to use this script and create a > puppet home for building docker images for Kubernetes, Mesos, or any other > platforms. As we have separate repos for platform hieradata, we need to > copy those hieradata to the puppet home repo. > +1 > > Thank you! > > > On Wed, Sep 7, 2016 at 8:21 PM, Imesh Gunaratne wrote: > >> >> >> On Wed, Sep 7, 2016 at 6:24 PM, Anuruddha Liyanarachchi < >> anurudd...@wso2.com> wrote: >> >>> Hi Imesh, >>> >>> I have now added the ability to configure multiple products using comma >>> separated product list. >>> Also included '-p all' option which configures all the products. >>> >>> Ex: ./setup.sh -p as >>> Ex: ./setup.sh -p as,esb,bps >>> Ex: ./setup.sh -p all >>> >> >> Great! >> Nice to hear that! >> >>> >>> On Wed, Sep 7, 2016 at 12:46 AM, Imesh Gunaratne wrote: >>> Great work Anuruddha! The bash script works well! Shall we add the ability to install multiple product modules in one go? Maybe we can use a comma separated product list with -p. Thanks On Tue, Sep 6, 2016 at 6:26 PM, Anuruddha Liyanarachchi < anurudd...@wso2.com> wrote: > Hi, > > We have created separate GitHub repos for Puppet modules so that the > Puppet module can be shipped as part of a product release. > > Since modules are distributed we have introduced a script to generate > PUPPET_HOME. The script will work as following. > > 1. Check puppet_home folder exists. > > 2. Create folder structure required for puppet_home. > ├── hiera.yaml > ├── hieradata > ├── manifests > └── modules > > 3. Create a symlink to manifest/site.pp file. > > 4. Clone wso2base puppet module into /modules directory. > > 5. Create a symlink to wso2base common.yaml hiera-file. > >> /modules/wso2base/hieradata/wso2/common.yaml -> >> /hieradata/dev/wso2/ > > > 6. Clone wso2 puppet module into /modules > directory. > > 7. Create a symlink to wso2 hiera-files. > >> /wso2/hieradata/dev/wso2/wso2 -> >> ../hieradata/dev/wso2/ > > > Once the setup.sh completes, users can copy product pack and jdk > distribution for relevant folders and run vagrant setup against > above-created puppet home. > > We are planning to automate the copying of product pack, jdk > distribution and starting vagrant setup as well. > > Setup.sh can be found at [1]. Please share your suggestions towards > this approach. > > [1] https://github.com/wso2/puppet-common/blob/master/setup.sh > > -- > *Thanks and Regards,* > Anuruddha Lanka Liyanarachchi > Software Engineer - WSO2 > Mobile : +94 (0) 712762611 > Tel : +94 112 145 345 > a nurudd...@wso2.com > -- *Imesh Gunaratne* Software Architect WSO2 Inc: http://wso2.com T: +94 11 214 5345 M: +94 77 374 2057 W: https://medium.com/@imesh TW: @imesh lean. enterprise. middleware >>> >>> >>> -- >>> *Thanks and Regards,* >>> Anuruddha Lanka Liyanarachchi >>> Software Engineer - WSO2 >>> Mobile : +94 (0) 712762611 >>> Tel : +94 112 145 345 >>> a nurudd...@wso2.com >>> >> >> >> >> -- >> *Imesh Gunaratne* >> Software Architect >> WSO2 Inc: http://wso2.com >> T: +94 11 214 5345 M: +94 77 374 2057 >> W: https://medium.com/@imesh TW: @imesh >> lean. enterprise. middleware >> >> > > > -- > *Pubudu Gunatilaka* > Committer and PMC Member - Apache Stratos > Software Engineer > WSO2, Inc.: http://wso2.com > mobile : +94774078049 <%2B94772207163> > > -- *Imesh Gunaratne* Software Architect WSO2 Inc: http://wso2.com T: +94 11 214 5345 M: +94 77 374 2057 W: https://medium.com/@imesh TW: @imesh lean. enterprise. middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [puppet] Setting up puppet home from script
Hi Anuruddha, Great work Anuruddha! I think we need to include the platform as well. If we consider the big picture, ideally any user should be able to use this script and create a puppet home for building docker images for Kubernetes, Mesos, or any other platforms. As we have separate repos for platform hieradata, we need to copy those hieradata to the puppet home repo. Thank you! On Wed, Sep 7, 2016 at 8:21 PM, Imesh Gunaratne wrote: > > > On Wed, Sep 7, 2016 at 6:24 PM, Anuruddha Liyanarachchi < > anurudd...@wso2.com> wrote: > >> Hi Imesh, >> >> I have now added the ability to configure multiple products using comma >> separated product list. >> Also included '-p all' option which configures all the products. >> >> Ex: ./setup.sh -p as >> Ex: ./setup.sh -p as,esb,bps >> Ex: ./setup.sh -p all >> > > Great! > Nice to hear that! > >> >> On Wed, Sep 7, 2016 at 12:46 AM, Imesh Gunaratne wrote: >> >>> Great work Anuruddha! The bash script works well! >>> >>> Shall we add the ability to install multiple product modules in one go? >>> Maybe we can use a comma separated product list with -p. >>> >>> Thanks >>> >>> On Tue, Sep 6, 2016 at 6:26 PM, Anuruddha Liyanarachchi < >>> anurudd...@wso2.com> wrote: >>> Hi, We have created separate GitHub repos for Puppet modules so that the Puppet module can be shipped as part of a product release. Since modules are distributed we have introduced a script to generate PUPPET_HOME. The script will work as following. 1. Check puppet_home folder exists. 2. Create folder structure required for puppet_home. ├── hiera.yaml ├── hieradata ├── manifests └── modules 3. Create a symlink to manifest/site.pp file. 4. Clone wso2base puppet module into /modules directory. 5. Create a symlink to wso2base common.yaml hiera-file. > /modules/wso2base/hieradata/wso2/common.yaml -> > /hieradata/dev/wso2/ 6. Clone wso2 puppet module into /modules directory. 7. Create a symlink to wso2 hiera-files. > /wso2/hieradata/dev/wso2/wso2 -> > ../hieradata/dev/wso2/ Once the setup.sh completes, users can copy product pack and jdk distribution for relevant folders and run vagrant setup against above-created puppet home. We are planning to automate the copying of product pack, jdk distribution and starting vagrant setup as well. Setup.sh can be found at [1]. Please share your suggestions towards this approach. [1] https://github.com/wso2/puppet-common/blob/master/setup.sh -- *Thanks and Regards,* Anuruddha Lanka Liyanarachchi Software Engineer - WSO2 Mobile : +94 (0) 712762611 Tel : +94 112 145 345 a nurudd...@wso2.com >>> >>> >>> >>> -- >>> *Imesh Gunaratne* >>> Software Architect >>> WSO2 Inc: http://wso2.com >>> T: +94 11 214 5345 M: +94 77 374 2057 >>> W: https://medium.com/@imesh TW: @imesh >>> lean. enterprise. middleware >>> >>> >> >> >> -- >> *Thanks and Regards,* >> Anuruddha Lanka Liyanarachchi >> Software Engineer - WSO2 >> Mobile : +94 (0) 712762611 >> Tel : +94 112 145 345 >> a nurudd...@wso2.com >> > > > > -- > *Imesh Gunaratne* > Software Architect > WSO2 Inc: http://wso2.com > T: +94 11 214 5345 M: +94 77 374 2057 > W: https://medium.com/@imesh TW: @imesh > lean. enterprise. middleware > > -- *Pubudu Gunatilaka* Committer and PMC Member - Apache Stratos Software Engineer WSO2, Inc.: http://wso2.com mobile : +94774078049 <%2B94772207163> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [puppet] Setting up puppet home from script
On Wed, Sep 7, 2016 at 6:24 PM, Anuruddha Liyanarachchi wrote: > Hi Imesh, > > I have now added the ability to configure multiple products using comma > separated product list. > Also included '-p all' option which configures all the products. > > Ex: ./setup.sh -p as > Ex: ./setup.sh -p as,esb,bps > Ex: ./setup.sh -p all > Great! Nice to hear that! > > On Wed, Sep 7, 2016 at 12:46 AM, Imesh Gunaratne wrote: > >> Great work Anuruddha! The bash script works well! >> >> Shall we add the ability to install multiple product modules in one go? >> Maybe we can use a comma separated product list with -p. >> >> Thanks >> >> On Tue, Sep 6, 2016 at 6:26 PM, Anuruddha Liyanarachchi < >> anurudd...@wso2.com> wrote: >> >>> Hi, >>> >>> We have created separate GitHub repos for Puppet modules so that the >>> Puppet module can be shipped as part of a product release. >>> >>> Since modules are distributed we have introduced a script to generate >>> PUPPET_HOME. The script will work as following. >>> >>> 1. Check puppet_home folder exists. >>> >>> 2. Create folder structure required for puppet_home. >>> ├── hiera.yaml >>> ├── hieradata >>> ├── manifests >>> └── modules >>> >>> 3. Create a symlink to manifest/site.pp file. >>> >>> 4. Clone wso2base puppet module into /modules directory. >>> >>> 5. Create a symlink to wso2base common.yaml hiera-file. >>> /modules/wso2base/hieradata/wso2/common.yaml -> /hieradata/dev/wso2/ >>> >>> >>> 6. Clone wso2 puppet module into /modules >>> directory. >>> >>> 7. Create a symlink to wso2 hiera-files. >>> /wso2/hieradata/dev/wso2/wso2 -> ../hieradata/dev/wso2/ >>> >>> >>> Once the setup.sh completes, users can copy product pack and jdk >>> distribution for relevant folders and run vagrant setup against >>> above-created puppet home. >>> >>> We are planning to automate the copying of product pack, jdk >>> distribution and starting vagrant setup as well. >>> >>> Setup.sh can be found at [1]. Please share your suggestions towards this >>> approach. >>> >>> [1] https://github.com/wso2/puppet-common/blob/master/setup.sh >>> >>> -- >>> *Thanks and Regards,* >>> Anuruddha Lanka Liyanarachchi >>> Software Engineer - WSO2 >>> Mobile : +94 (0) 712762611 >>> Tel : +94 112 145 345 >>> a nurudd...@wso2.com >>> >> >> >> >> -- >> *Imesh Gunaratne* >> Software Architect >> WSO2 Inc: http://wso2.com >> T: +94 11 214 5345 M: +94 77 374 2057 >> W: https://medium.com/@imesh TW: @imesh >> lean. enterprise. middleware >> >> > > > -- > *Thanks and Regards,* > Anuruddha Lanka Liyanarachchi > Software Engineer - WSO2 > Mobile : +94 (0) 712762611 > Tel : +94 112 145 345 > a nurudd...@wso2.com > -- *Imesh Gunaratne* Software Architect WSO2 Inc: http://wso2.com T: +94 11 214 5345 M: +94 77 374 2057 W: https://medium.com/@imesh TW: @imesh lean. enterprise. middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [puppet] Setting up puppet home from script
Hi Imesh, I have now added the ability to configure multiple products using comma separated product list. Also included '-p all' option which configures all the products. Ex: ./setup.sh -p as Ex: ./setup.sh -p as,esb,bps Ex: ./setup.sh -p all On Wed, Sep 7, 2016 at 12:46 AM, Imesh Gunaratne wrote: > Great work Anuruddha! The bash script works well! > > Shall we add the ability to install multiple product modules in one go? > Maybe we can use a comma separated product list with -p. > > Thanks > > On Tue, Sep 6, 2016 at 6:26 PM, Anuruddha Liyanarachchi < > anurudd...@wso2.com> wrote: > >> Hi, >> >> We have created separate GitHub repos for Puppet modules so that the >> Puppet module can be shipped as part of a product release. >> >> Since modules are distributed we have introduced a script to generate >> PUPPET_HOME. The script will work as following. >> >> 1. Check puppet_home folder exists. >> >> 2. Create folder structure required for puppet_home. >> ├── hiera.yaml >> ├── hieradata >> ├── manifests >> └── modules >> >> 3. Create a symlink to manifest/site.pp file. >> >> 4. Clone wso2base puppet module into /modules directory. >> >> 5. Create a symlink to wso2base common.yaml hiera-file. >> >>> /modules/wso2base/hieradata/wso2/common.yaml -> >>> /hieradata/dev/wso2/ >> >> >> 6. Clone wso2 puppet module into /modules >> directory. >> >> 7. Create a symlink to wso2 hiera-files. >> >>> /wso2/hieradata/dev/wso2/wso2 -> >>> ../hieradata/dev/wso2/ >> >> >> Once the setup.sh completes, users can copy product pack and jdk >> distribution for relevant folders and run vagrant setup against >> above-created puppet home. >> >> We are planning to automate the copying of product pack, jdk distribution >> and starting vagrant setup as well. >> >> Setup.sh can be found at [1]. Please share your suggestions towards this >> approach. >> >> [1] https://github.com/wso2/puppet-common/blob/master/setup.sh >> >> -- >> *Thanks and Regards,* >> Anuruddha Lanka Liyanarachchi >> Software Engineer - WSO2 >> Mobile : +94 (0) 712762611 >> Tel : +94 112 145 345 >> a nurudd...@wso2.com >> > > > > -- > *Imesh Gunaratne* > Software Architect > WSO2 Inc: http://wso2.com > T: +94 11 214 5345 M: +94 77 374 2057 > W: https://medium.com/@imesh TW: @imesh > lean. enterprise. middleware > > -- *Thanks and Regards,* Anuruddha Lanka Liyanarachchi Software Engineer - WSO2 Mobile : +94 (0) 712762611 Tel : +94 112 145 345 a nurudd...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [puppet] Setting up puppet home from script
Great work Anuruddha! The bash script works well! Shall we add the ability to install multiple product modules in one go? Maybe we can use a comma separated product list with -p. Thanks On Tue, Sep 6, 2016 at 6:26 PM, Anuruddha Liyanarachchi wrote: > Hi, > > We have created separate GitHub repos for Puppet modules so that the > Puppet module can be shipped as part of a product release. > > Since modules are distributed we have introduced a script to generate > PUPPET_HOME. The script will work as following. > > 1. Check puppet_home folder exists. > > 2. Create folder structure required for puppet_home. > ├── hiera.yaml > ├── hieradata > ├── manifests > └── modules > > 3. Create a symlink to manifest/site.pp file. > > 4. Clone wso2base puppet module into /modules directory. > > 5. Create a symlink to wso2base common.yaml hiera-file. > >> /modules/wso2base/hieradata/wso2/common.yaml -> >> /hieradata/dev/wso2/ > > > 6. Clone wso2 puppet module into /modules directory. > > 7. Create a symlink to wso2 hiera-files. > >> /wso2/hieradata/dev/wso2/wso2 -> >> ../hieradata/dev/wso2/ > > > Once the setup.sh completes, users can copy product pack and jdk > distribution for relevant folders and run vagrant setup against > above-created puppet home. > > We are planning to automate the copying of product pack, jdk distribution > and starting vagrant setup as well. > > Setup.sh can be found at [1]. Please share your suggestions towards this > approach. > > [1] https://github.com/wso2/puppet-common/blob/master/setup.sh > > -- > *Thanks and Regards,* > Anuruddha Lanka Liyanarachchi > Software Engineer - WSO2 > Mobile : +94 (0) 712762611 > Tel : +94 112 145 345 > a nurudd...@wso2.com > -- *Imesh Gunaratne* Software Architect WSO2 Inc: http://wso2.com T: +94 11 214 5345 M: +94 77 374 2057 W: https://medium.com/@imesh TW: @imesh lean. enterprise. middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [puppet] Setting up puppet home from script
Hi, We have created separate GitHub repos for Puppet modules so that the Puppet module can be shipped as part of a product release. Since modules are distributed we have introduced a script to generate PUPPET_HOME. The script will work as following. 1. Check puppet_home folder exists. 2. Create folder structure required for puppet_home. ├── hiera.yaml ├── hieradata ├── manifests └── modules 3. Create a symlink to manifest/site.pp file. 4. Clone wso2base puppet module into /modules directory. 5. Create a symlink to wso2base common.yaml hiera-file. > /modules/wso2base/hieradata/wso2/common.yaml -> > /hieradata/dev/wso2/ 6. Clone wso2 puppet module into /modules directory. 7. Create a symlink to wso2 hiera-files. > /wso2/hieradata/dev/wso2/wso2 -> > ../hieradata/dev/wso2/ Once the setup.sh completes, users can copy product pack and jdk distribution for relevant folders and run vagrant setup against above-created puppet home. We are planning to automate the copying of product pack, jdk distribution and starting vagrant setup as well. Setup.sh can be found at [1]. Please share your suggestions towards this approach. [1] https://github.com/wso2/puppet-common/blob/master/setup.sh -- *Thanks and Regards,* Anuruddha Lanka Liyanarachchi Software Engineer - WSO2 Mobile : +94 (0) 712762611 Tel : +94 112 145 345 a nurudd...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev