Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [che-dev] A runner for the paas Cloud Foundry
Can you tell us more about what a bosh release is for CF?  

Having Che run automatically on CF would be ideal - each Che instance can support its own user.

I am not sure if it is interesting or not, but we will be making Codenvy On-Prem (single node and multi-node) free as well in about a quarter.  While Che is going to get the Docker plug-in packaged with it, Che itself is still single tenant.  Would there be interest in having the multi-tenanted Codenvy also installable on CF?  It would be cool to have both systems, but having Che run will be easier / faster / require fewer resources.

Please write me privately for a blog post about CF.  We will connect you with the right people and would be happy to sponsor the content from CF team.

Tyler Jewell | CEO | tyler@​codenvy.​com | 9​78​.8​84​.53​55


On Wed, Apr 22, 2015 at 7:13 AM, <arthur.halet@xxxxxxxxxx> wrote:

First, thank to you Eugene and Tyler to have a lot of interest for this.

 

@Eugene,

 

Yep you are absolutely right J

And no it was not intended so I’ve removed it.

 

@Tyler,

 

1.     I wanted to have a real runner which will automatic deployed my app, give me the logs and send me a nice url.

I worked on it to have a good first entry point to make codenvy works with cloud foundry like all your runner you did.

Another point is that codenvy/eclipse-che and cloud foundry community could be more linked to do the job all in a cloud environment so my intention is to make what we called a bosh release on cloud foundry to have an eclipse-che working on Cloud Foundry.

2.     Yep I could do a blog post for it’s a good idea just I don’t want to be tagged as an Orange contributor but as a Cloud Foundry community contributor (even if we thought to add this on our personal Cloud Foundry in my company)

3.     That’s really cool that you want to add my work thanks a lot J

 

De : che-dev-bounces@xxxxxxxxxxx [mailto:che-dev-bounces@xxxxxxxxxxx] De la part de Eugene Ivantsov
Envoyé : lundi 20 avril 2015 08:07
À : che developer discussions
Objet : Re: [che-dev] A runner for the paas Cloud Foundry

 

@Tyler,

 

May I try to answer the first question (as the one who stands behind our PaaS docs).

 

We provided a basic example on how to deploy an application to CF. No more, no less. 

 

Arthur's example (a nice one!!!) is an emulation of a real Runner. What he does there is deploy an app, then create a simple php script that is constantly getting app on CF, and the script is serving on 0.0.0.0:8080 in a container, thus when clicking on the app url in Codenvy, you should be redirected to a CF app instance.

 

In addition, app logs are retrieved to complement 'run experience' rather than deploy. So, when you hit run you get exactly what you are supposed to get when running an app in a container - the app itself (when clicking on the app URL) and application logs in the console.

 

@Arthur, just a quick question:

 

I have noticed there are 2 CMD commands in a Dockerfile with identical instructions:

 

 

 

 

Is it intended?

 

 

On Mon, Apr 20, 2015 at 4:58 AM, Tyler Jewell <tyler@xxxxxxxxxxx> wrote:

Arthur:

 

Thank you for making a contribution.

 

A couple of thoughts and questions:

1. Did you see the (more simplistic) example that we provide in the docs at Codenvy?  I am curious if you tried that and what were the needs that you had to write a more involved version.

 

2. Would you like to do a contributed blog post regarding how you went about authoring this runner?  We would consider doing one ourselves on this contribution, but if you wanted to do it, we can give you and your company visibility to our full user base.

 

3. We are working to package up our Docker elements for Che.  Right now we only support OS forking on the Che package itself, but once we have the Docker runner packaged to integrate with Che, then we will also package up built Docker images for different runner types.  We'll definitely consider adding this.

 

Tyler

Tyler Jewell | CEO | tyler@​codenvy.​com | 9​78​.8​84​.53​55

 

On Sun, Apr 19, 2015 at 4:04 AM, <arthur.halet@xxxxxxxxxx> wrote:


I've made a dockerfile to make possible runner for cloud foundry. I think it could interest you for a good start to make it as default runner in codenvy for example. See this repo: https://github.com/cloudfoundry-community/codenvy-cfrunner .

ArthurH
_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev

 


_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev



 

--

  | Eugene Ivantsov | Customer Support Manager | Codenvy.com 

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev


Back to the top