On Thu, Aug 18, 2016 at 7:56 PM, Osura Rathnayake <osura...@gmail.com> wrote:
> Hi Imesh, > > Yes now I understand that creating VM images for each product profile will > not going to work out. > > Can you please give me a step by step guideline on what I should do to > achieve this? > Please refer [1] and [2]. [1] https://github.com/wso2/puppet-modules [2] https://docs.wso2.com/display/PM210/WSO2+Puppet+Modules+Documentation Thanks . > Thank you, > > On Wed, Aug 17, 2016 at 10:41 PM, Imesh Gunaratne <im...@wso2.com> wrote: > >> >> >> On Wed, Aug 17, 2016 at 10:19 PM, Imesh Gunaratne <im...@wso2.com> wrote: >>> >>> >>> There are many spelling mistakes on this file [2], please review it >>> again. >>> >> >> Correction: s/on this file/in this file/g >> >> Thanks >> >> >> >>> Overall I see very less attention to detail in this repository and the >>> membership scheme implementation. >>> >>> >>>> There I mentioned the things that should be kept in mind while >>>> configuring wso2 AS and did not go in to detail on hot to configure as it >>>> can be found in the wso2 documentation. Would that be okay? >>>> >>> >>> I don't think this is helpful. Without having detailed steps users >>> might not be able to do a complete deployment. >>> >>> Few questions: >>> >>> - How do you create a distributed deployment >>> >>> of AS or any other product (say for an example WSO2 API-M) with >>> this approach? As I explained earlier creating a VM image per product >>> profile is an unnecessary overhead (time consumption, disk space needed, >>> maintenance, etc). >>> >>> - What would be the approach of applying >>> a patch or do >>> ing >>> a configuration change in a such deployment? >>> >>> IMO it is really important to understand the concepts well and solve >>> problems with the most efficient manner. Otherwise the outcome of this >>> project might not be usable. >>> >>> [2] https://github.com/osuran/azure-artifacts/issues/2 >>> >>> Thanks >>> >>> >>>> user do not need to change anything in template.json, so should I >>>> explain the parameters in that too? >>>> >>>> in the paramters.json, except for the vm_image parameter, all of the >>>> parameters are just for the naming of the elements that you find in a VM, >>>> for an example, the name of the network interface. Therefore I have given >>>> instructions on how to set the vm_image parameter. >>>> >>>> current progress: The script which was generated by Azure does not have >>>> the capability to add a custom VM image. I modified it so that now it has >>>> that capability. Normally when you login to azure from CLI, it needs web >>>> interaction to authenticate. I modified deploy.sh in a way that it >>>> authenticates the user without web interaction, this will be useful if we >>>> run deploy.sh in a minimal version of linux. >>>> >>>> currently I'm working on adding deployment patterns to deploy.sh and >>>> undeploy.sh >>>> >>>> >>>> [1] https://github.com/osuran/azure-artifacts/tree/master/wso2as >>>> >>>> thank you, >>>> >>>> On Tue, Aug 16, 2016 at 10:10 AM, Isuru Haththotuwa <isu...@wso2.com> >>>> wrote: >>>> >>>>> Hi Osura, >>>>> >>>>> Can you please send an update on the current status? >>>>> >>>>> On Mon, Aug 15, 2016 at 10:11 AM, Isuru Haththotuwa <isu...@wso2.com> >>>>> wrote: >>>>> >>>>>> Hi Osura, >>>>>> >>>>>> Few comments regarding the README: >>>>>> >>>>>> 1. Need to mention how to configure the VM with the product pack >>>>>> and JDK for Azure >>>>>> 2. There are lot of parameters in the template and parameters >>>>>> json files; please explain what a user needs to change there. >>>>>> 3. The deploy script should be able to handle both standalone and >>>>>> distributed deployment pattern for the product. Refer to K8s >>>>>> repository as >>>>>> a reference [1] >>>>>> 4. Highlights the commands that a user needs to issue clearly >>>>>> >>>>>> Please note a user should be able to deploy a WSO2 product in Azure >>>>>> by following the README. If we provide abstract and incomplete >>>>>> instructions, user experience will not be good. >>>>>> >>>>>> On Mon, Aug 15, 2016 at 9:05 AM, Osura Rathnayake <osura...@gmail.com >>>>>> > wrote: >>>>>> >>>>>>> Hi Imesh /Isuru, >>>>>>> >>>>>>> Please accept my apologies for the delayed response. >>>>>>> >>>>>>> There is a MySQL instance in the Azure marketplace, we can >>>>>>> straightaway deploy that. It's a Ubuntu 16.04.1 LTS with MySQL >>>>>>> installed. I >>>>>>> think it's better to use it as there won't be licensing issues with it. >>>>>>> >>>>>>> Please find the updated readme file in [1] which includes steps on >>>>>>> how to deploy WSO2 AS in Azure. >>>>>>> >>>>>> >>>>>>> About the undeploy.sh, should it remove the VM entirely or just the >>>>>>> WSO2 AS instance? >>>>>>> >>>>>> Ideally we should be able to re-use the VM, so IMHO removing only the >>>>>> instance is ok. >>>>>> >>>>>> [1]. https://github.com/wso2/kubernetes-artifacts/tree/master/wso2as >>>>>> >>>>>>> >>>>>>> [1] https://github.com/osuran/azure-artifacts >>>>>>> >>>>>>> Thank you, >>>>>>> >>>>>>> On Sun, Aug 14, 2016 at 10:06 AM, Isuru Haththotuwa <isu...@wso2.com >>>>>>> > wrote: >>>>>>> >>>>>>>> Hi Osura, >>>>>>>> >>>>>>>> I see that you have updated the repo [1] with a deploy script for >>>>>>>> wso2as. Additionally we would need an undeploy script as well. What >>>>>>>> are the >>>>>>>> steps that I need to follow to deploy WSO2 AS on Azure? Can you please >>>>>>>> provide me a documentation link? >>>>>>>> >>>>>>>> [1]. https://github.com/osuran/azure-artifacts >>>>>>>> >>>>>>>> On Thu, Aug 11, 2016 at 10:22 AM, Isuru Haththotuwa < >>>>>>>> isu...@wso2.com> wrote: >>>>>>>> >>>>>>>>> Hi Osura, >>>>>>>>> >>>>>>>>> Can you give an update on the latest status? I checked the github >>>>>>>>> repositories under your account, but still can find only the >>>>>>>>> membership >>>>>>>>> scheme and a couple of templates. Did you add the scripts to >>>>>>>>> deploy/undeploy the products? As we saw, its just a matter of copy >>>>>>>>> pasting >>>>>>>>> from the Azure management portal since the deployment script is auto >>>>>>>>> generated. >>>>>>>>> >>>>>>>>> On Fri, Aug 5, 2016 at 10:56 AM, Imesh Gunaratne <im...@wso2.com> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> On Fri, Aug 5, 2016 at 9:07 AM, Osura Rathnayake < >>>>>>>>>> osura...@gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Hi Mentors, >>>>>>>>>>> >>>>>>>>>>> This is the progress so far. >>>>>>>>>>> >>>>>>>>>>> I have created a template, using which you can deploy 3 VMs, >>>>>>>>>>> manager node, worker node and a DB. This template can be used in >>>>>>>>>>> any azure >>>>>>>>>>> subscription, you only have to do a template deployment using that >>>>>>>>>>> template. You have to pass the relevant VM images at the time of >>>>>>>>>>> deployment >>>>>>>>>>> so for that I have created 5 VM images, >>>>>>>>>>> >>>>>>>>>>> 1. WSO2 AS as manager >>>>>>>>>>> 2. WSO2 AS as worker >>>>>>>>>>> 3. WSO2 ESB as manager >>>>>>>>>>> 4. WSO2 ESB as worker >>>>>>>>>>> 5. DB >>>>>>>>>>> >>>>>>>>>>> Are you running a database server on a VM? On Azure it would be >>>>>>>>>> better to use their database service for creating databases otherwise >>>>>>>>>> managing databases on VMs would be difficult. >>>>>>>>>> >>>>>>>>>> These VM images are in my azure storage account so that prior to >>>>>>>>>>> the deployment, they have to be copied to the storage account of the >>>>>>>>>>> customer. Each VM image is approx 30 GB in size. Once you copied the >>>>>>>>>>> images, you can start the deployment using the template. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Ideally we should have a configuration management system in >>>>>>>>>> place to manage this. It's an overhead to work with multiple VM >>>>>>>>>> images. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Thanks >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> *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, >>>>>>>>> >>>>>>>>> Isuru H. >>>>>>>>> +94 716 358 048* <http://wso2.com/>* >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Thanks and Regards, >>>>>>>> >>>>>>>> Isuru H. >>>>>>>> +94 716 358 048* <http://wso2.com/>* >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Regards, >>>>>>> Osura Rathnayake >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Thanks and Regards, >>>>>> >>>>>> Isuru H. >>>>>> +94 716 358 048* <http://wso2.com/>* >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Thanks and Regards, >>>>> >>>>> Isuru H. >>>>> +94 716 358 048* <http://wso2.com/>* >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Regards, >>>> Osura Rathnayake >>>> >>> >>> >>> >>> -- >>> *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 >>> >>> >> >> >> -- >> *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 >> >> > > > -- > Regards, > Osura Rathnayake > -- *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
