Hi Dimuthu,
Yes we are using fabric8 java client library and not calling Kubernetes
REST API directly, since fabric8 simplify our effort.
Thanks,
Roshan Deniyage
Associate Technical Lead
WSO2, Inc: http://wso2.com
Mobile : +94 777636406 / +1 408 667 6254
Twitter : *https://twitter.com/roshku <https://twitter.com/roshku>*
LinkedIn : https://www.linkedin.com/in/roshandeniyage
On Fri, Dec 25, 2015 at 8:47 PM, Dimuthu Leelarathne <[email protected]>
wrote:
> Hi Roshan,
>
> More importantly, we are we going through fabric8 and not straight
> Kubernetes?
>
> thanks,
> Dimuthu
>
> On Fri, Dec 25, 2015 at 8:45 PM, Dimuthu Leelarathne <[email protected]>
> wrote:
>
>> Hi Roshan,
>>
>> When an application is created, we only create sample code (according to
>> the picture). Aren't we deploying a docker image of the sample app? I think
>> we have to change from that point onwards.
>>
>> Ideally we can even refrain from committing sample code to the repo,
>> until the developer starts cloning for the first time.
>>
>> thanks,
>> Dimuthu
>>
>> On Thu, Dec 10, 2015 at 9:17 PM, Roshan Deniyage <[email protected]>
>> wrote:
>>
>>> Hi All,
>>> As you know AppFac product is moving to use kubernetes and we are in
>>> the process of integrating kubernetes with fabric8 api for the first mile
>>> stone release.
>>>
>>> In this process we are changing some of the work flows and in later
>>> releases enhance it.
>>>
>>> When it comes to build the artifacts (artifact which appfactory users
>>> create and deploy), we used to have a stand alone Jenkins server to do the
>>> job earlier and push built artifact to our git repository which is consumed
>>> by the stratos for deployments.
>>>
>>> With the new architectural changes, we are going to change the jenkins
>>> generated artifact to "*docker image*" instead of generating *deplorable
>>> artifact (war / car etc)*. This new improvement will be the same in the
>>> future as well.
>>>
>>> But, when it comes to jenkins server itself, it will be moved to a
>>> jenkins build farm with docker support in future releases.
>>>
>>> For the next mile store release the build task workflow would be changed
>>> as follows. The detailed design is being shared later.
>>>
>>> Your valuable comment would be appreciated.
>>>
>>>
>>>
>>> [image: Inline image 1]
>>>
>>>
>>>
>>> Thanks,
>>> Roshan Deniyage
>>> Associate Technical Lead
>>> WSO2, Inc: http://wso2.com
>>>
>>> Mobile : +94 777636406 / +1 408 667 6254
>>> Twitter : *https://twitter.com/roshku <https://twitter.com/roshku>*
>>> LinkedIn : https://www.linkedin.com/in/roshandeniyage
>>>
>>>
>>> _______________________________________________
>>> Architecture mailing list
>>> [email protected]
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Dimuthu Leelarathne
>> Director
>>
>> WSO2, Inc. (http://wso2.com)
>> email: [email protected]
>> Mobile : 0773661935
>>
>> Lean . Enterprise . Middleware
>>
>
>
>
> --
> Dimuthu Leelarathne
> Director
>
> WSO2, Inc. (http://wso2.com)
> email: [email protected]
> Mobile : 0773661935
>
> Lean . Enterprise . Middleware
>
> _______________________________________________
> Architecture mailing list
> [email protected]
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
