Hi Thilina,

As explained offline. You can decouple the docker image creation logic from
the web app. But the image creation should be automated. Please have a look
at existing Docker file creation scripts.

Please let us know if you have more queries.

With Regards,
Yasassri

On Fri, Mar 31, 2017 at 3:51 PM, Thilina Manamgoda <maanafun...@gmail.com>
wrote:

> Hi Yasassri,
>
> What If we configure the web app such that we can add Deployment profiles
> as we go on. We can build this for existing profiles and if there is a
> profile we can build docker images and Kubernetes artifacts and configure
> them in the web app. Is this approach acceptable ?
>
> regards,
> Thilina
>
> On Fri, Mar 31, 2017 at 8:32 AM, Yasassri Ratnayake <yasas...@wso2.com>
> wrote:
>
>> On Thu, Mar 30, 2017 at 6:19 PM, Thilina Manamgoda <maanafun...@gmail.com
>> > wrote:
>>
>>> Hi Yasassri,
>>>
>>> I think if we can build docker files  for each profile and kept in a
>>> private registry it would be easy. If this is possible no need to build
>>> Docker images in web app. Also we need to build Kubernetes artifacts for
>>> those profile as well.
>>>
>>
>> What you need to take into cosideration is, that the pack (e.g : ESB
>> 4.9.0) is going to change, we are planning to use this to Test packs
>> released with WUM (WSO2 Update Manager) as well. WUM gives a new
>> distribution pack with the latest fixes. So we need to cater this as well.
>>
>>
>>>
>>> regards,
>>> Thilina
>>>
>>> On Mon, Mar 27, 2017 at 8:49 AM, Yasassri Ratnayake <yasas...@wso2.com>
>>> wrote:
>>>
>>>> Hi Thilina,
>>>>
>>>> On Sun, Mar 26, 2017 at 4:07 AM, Thilina Manamgoda <
>>>> maanafun...@gmail.com> wrote:
>>>>
>>>>> Hi Yasassri,
>>>>>
>>>>> Please find my comments inline.
>>>>>
>>>>> On Wed, Mar 22, 2017 at 8:12 PM, Yasassri Ratnayake <yasas...@wso2.com
>>>>> > wrote:
>>>>>
>>>>>> Hi Thilina,
>>>>>>
>>>>>> We have missed some requirements. Please consider the following as
>>>>>> well.
>>>>>>
>>>>>> 1. We need a Tomcat instance to host the Backends(Weapps) which are
>>>>>> required by the Test Scripts. So we need another instance spawned with
>>>>>> Tomcat. After spawning the instance you can deploy the prerequisite web
>>>>>> apps. (These web apps will be available in the Test-Repo under resources)
>>>>>>
>>>>>
>>>>>  Yes of course we can archieve this as well.
>>>>>
>>>>> 2. Also when deploying Jmeter we need to copy 3rd party Jars to
>>>>>> Jmeter. (These are also available in the repository)
>>>>>>
>>>>>
>>>>>
>>>>>> This can be done by copying these files to docker image in Jmeter
>>>>>> docker image building stage.
>>>>>>
>>>>>
>>>>>
>>>>>> Also answering your question about the Deployment profiles. We have
>>>>>> identified several components to make the scope manageable.
>>>>>>
>>>>>> *Products*
>>>>>> ESB | V4.9 & V5.0
>>>>>> APIM | V1.9 & V2.0
>>>>>>
>>>>>> *JDK*
>>>>>> JAVA | V1.7 & V1.8
>>>>>>
>>>>>> *DataBase*
>>>>>> MySQL
>>>>>>
>>>>>> *Third Party Servers*
>>>>>> Brokers | ActiveMQ 5.10 | WSO2 MB 3.1 (Only applicable when ESB is
>>>>>> used)
>>>>>>
>>>>>> So a Sample Profile would be, *ESB 4.9 + JAVA 1.7 + MYSQL + ActiveMQ*.
>>>>>> For now, you can concentrate on the above components when determining a
>>>>>> deployment profile. But your solution should be scalable.
>>>>>>
>>>>>> Is this a profile described here:https://docs.wso2.com/dis
>>>>> play/KA100/Clustered+Deployment+of+WSO2+Products+on+Kubernetes . If
>>>>> it is, then do I need to configure the product with third party servers or
>>>>> it's already done and I only have to deploy selected profile's servers 
>>>>> into
>>>>> kubernetes cluster. For example let's take the above profile, in order to
>>>>> run this delpoyment ESB should be configured with MYSQL and Active MQ API
>>>>> endpoints. Do i need to change the configuration files of ESB or it's
>>>>> already taken care of and deployment is done once i deploy Kubernetes
>>>>> artifacts under the selected profile.
>>>>>
>>>>
>>>> Existing scripts doesn't allow us to configure thirdparty dependencies
>>>> like Message Brokers. So yes we need to change ESB configurations depending
>>>> on the Broker, you can refer [1
>>>> <https://docs.wso2.com/display/ESB490/Configure+with+ActiveMQ>] for
>>>> ActiveMQ configurations.
>>>>
>>>>
>>>>>
>>>>> Is this a profile of ESB : https://github.com/wso2/kube
>>>>> rnetes-artifacts/tree/master/wso2esb ?
>>>>>
>>>>
>>>> Yes this script supports two profiles, default ESB profile and worker
>>>> manager profile, but as mentioned we neeed to tweek these scripts to
>>>> support mesage brokers as well.
>>>>
>>>>
>>>>> Also can't we have a private docker registry to hold our deplyment's
>>>>> images instead of building docker images via the web app ?.
>>>>>
>>>>>>
>>>>>>
>>>> We can use a private registry to store the docker images but you need
>>>> to comeup with some scripts to Auomate the process in that case.
>>>>
>>>>
>>>> [1] - https://docs.wso2.com/display/ESB490/Configure+with+ActiveMQ
>>>> --
>>>> Yasassri Ratnayake
>>>> Senior Software Engineer - QA
>>>> WSO2 Inc ; http://wso2.com
>>>> lean.enterprise.middleware
>>>> *Mobile : +94715933168 <+94%2071%20593%203168>*
>>>> *Blogs : http://yasassriratnayake.blogspot.com
>>>> <http://yasassriratnayake.blogspot.com/>*
>>>> *            http://wso2logs.blogspot.com
>>>> <http://wso2logs.blogspot.com>*
>>>>
>>>
>>>
>>
>>
>> --
>> Yasassri Ratnayake
>> Senior Software Engineer - QA
>> WSO2 Inc ; http://wso2.com
>> lean.enterprise.middleware
>> *Mobile : +94715933168 <+94%2071%20593%203168>*
>> *Blogs : http://yasassriratnayake.blogspot.com
>> <http://yasassriratnayake.blogspot.com/>*
>> *            http://wso2logs.blogspot.com <http://wso2logs.blogspot.com>*
>>
>
>


-- 
Yasassri Ratnayake
Senior Software Engineer - QA
WSO2 Inc ; http://wso2.com
lean.enterprise.middleware
*Mobile : +94715933168*
*Blogs : http://yasassriratnayake.blogspot.com
<http://yasassriratnayake.blogspot.com/>*
*            http://wso2logs.blogspot.com <http://wso2logs.blogspot.com>*
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to