Hi Chamila, Yes we can use custom buildpacks to deploy on Cloud Foundry. I am not familiar with all WSO2 products, but I suppose that we need to run shell files in most cases. So we can customize or build our own buildpack to detect those files.
Diego is a separate approach. It is a new run time that replaces DEA in Cloud Foundry. With Diego, we can use Docker images to push applications to Cloud Foundry, But there are some limitations. We need the images to be available in Docker Hub publicly. But I found that there's something new called 'Private Docker Registry' in Diego that enables to use private Docker images where users are prompted for credentials during staging the app. I was unable to run Diego as it requires administrator privileges to enable docker support for me. Also there is a cf-docker buildpack that detects Docker images. It also has the above mentioned limitations. I am not sure if we can customize that buildpack to detect private images as well. They say that it is just a proof of concept. I have tried to get help from cf-dev mailing lists as well. They suggest that I need to have administrator privileges to resolve above scenarios. Best Regards, Nanduni *Nanduni Nimalsiri* Software Engineering Intern, WSO2 Inc. (http://wso2.com) email : nand...@wso2.com blog : http://nanduni.blogspot.com/ mobile : +94714114256 On Tue, Feb 9, 2016 at 12:01 PM, Chamila De Alwis <chami...@wso2.com> wrote: > Hi Nanduni, > > Wouldn't writing a custom buildpack (for each product) [1] allow us to > deploy a given artifact on CloudFoundry? We'd have to write the detect, > compile, and release scripts separately. > > Is there any difference between that approach and using Docker images? > > [1] - https://docs.cloudfoundry.org/buildpacks/custom.html > > > Regards, > Chamila de Alwis > Committer and PMC Member - Apache Stratos > Software Engineer | WSO2 | +94772207163 > Blog: code.chamiladealwis.com > > > > On Mon, Feb 8, 2016 at 9:00 AM, Nanduni Nimalsiri <nand...@wso2.com> > wrote: > >> Hi all, >> >> By now, I have managed to deploy applications in Cloud Foundry via, >> 1. bosh-lite ( a vagrant VM that comes with pre-installed BOSH server or >> Director) >> 2. Hosted solutions such as Pivotal web services (pivotal.io) >> >> I deployed Tomcat server in Cloud Foundry as well. But I was not able to >> deploy Docker in Cloud Foundry via Diego. It gives me some errors regarding >> admin permissions. >> I found that there are Heroku buildpacks on Docker and they are perfectly >> compatible with Cloud Foundry too. >> >> [1] https://github.com/duglin/cf-docker >> [1] is another buildpack that supports Docker, but there are several >> limitations as this buildpack requires that you have a Docker host >> available for it to access, and you need to also have a Docker container >> manager app (cf-docker) running that will sync the Cloud Foundry runtime >> with the Docker containers. >> >> My blog in the following link will be useful for any one to get an idea >> on deploying applications in Cloud Foundry. >> http://nanduni.blogspot.com/ >> >> Best regards, >> Nanduni. >> >> >> >> *Nanduni Nimalsiri* >> Software Engineering Intern, WSO2 Inc. (http://wso2.com) >> email : nand...@wso2.com >> blog : http://nanduni.blogspot.com/ >> mobile : +94714114256 >> >> >> On Sun, Feb 7, 2016 at 11:49 PM, Malmee Weerasinghe <mal...@wso2.com> >> wrote: >> >>> Hi Imesh, >>> >>> I have done a background research on Cloud Foundry and the blog under >>> the following link contains the documentation of the research. I will >>> include more posts on deploying Cloud Foundry with bosh lite and running >>> simple applications on it, as I have studied so far. >>> >>> >>> http://malmeeweerasinghe.blogspot.com/2016/02/introduction-to-cloud-foundry.html >>> >>> Thanks >>> >>> On Fri, Feb 5, 2016 at 10:31 PM, Imesh Gunaratne <im...@wso2.com> wrote: >>> >>>> Hi All, >>>> >>>> Shall we summarize the research work we have done so far and our >>>> approach towards $subject? >>>> >>>> I know some of us have already done below, it might be better to >>>> document this: >>>> >>>> - PaaS features of CF >>>> - Steps for setting up a local environment with Vagrant >>>> - Running a hello world sample >>>> - Running a JVM using a standalone framework >>>> >>>> Next we might need to check following: >>>> >>>> 1. The ability to use Docker on CF >>>> 2. The process of creating and managing Warden container images >>>> 3. Find a mechanism to discover the member list of a cluster and >>>> implement a Carbon membership scheme >>>> 4. Create standalone frameworks for Carbon products >>>> 5. Find a way to apply patches and software updates >>>> 6. Find a way to implement a centralized logging solution >>>> 7. Check whether there is a way to monitor the health of the containers >>>> (similar to cAdvisor and Cockpit UI in Kubernetes) >>>> 8. Create artifacts required for deploying a Carbon server on CF and >>>> prepare a guideline. >>>> >>>> [1] >>>> https://github.com/wso2/kubernetes-artifacts/tree/master/common/kubernetes-membership-scheme >>>> >>>> >>>> Thanks >>>> >>>> -- >>>> *Imesh Gunaratne* >>>> Senior Technical Lead >>>> WSO2 Inc: http://wso2.com >>>> T: +94 11 214 5345 M: +94 77 374 2057 >>>> W: http://imesh.io >>>> Lean . Enterprise . Middleware >>>> >>>> >>> >>> >>> -- >>> Malmee Weerasinghe >>> WSO2 Intern >>> mobile : (+94)* 71 7601905* | email : <dehan.vith...@aiesec.net> >>> mal...@wso2.com >>> >> >> >> _______________________________________________ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> >
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
