#7 Runtime image creation

open
nobody
None
Bug
My-Java-Component
2016-10-04
2016-10-03
Yazid
No

When using the tutorial of image creation

at the step :
* Create the runtime from the new image and manifest

$ ./runtime-tool.sh bundle -i c2netproject.eu/runtime/mongodb:1_0_0 -m manifest.json

My question: Openpaas is javascript code + legacy software dependencies.
1- I create an image containing only the dependencies base on eslap /....nodejs
2_ I create an image containing 1 + openpaas code , this image will run openpaas. In this case, I can modify the code of openpaas without creating again the image with dependencies.
3- I create a container from 2
4- I run 3

so do I use the image 1 or image 2 to create the runtime?

To resume, did the runtime will contains the running code + legacy softwares , or just the legacy. so I can use it to compile my code?

Thanks

Discussion

  • Josep Maria Bernabe
    Josep Maria Bernabe
    2016-10-04

    First of all, in my understanding, OpenPaaS is a Component, not a runtime. So, the process should be:

    1) Install the c2netproject nodejs image (eslap://c2netproject.eu/runtime/nodejs/1_0_0).
    2) Create a new image on the top of eslap://c2netproject.eu/runtime/nodejs/1_0_0 by using, for example, a Dockerfile.
    3) Register the image in the cloud platform. Right now, only us can do that, so, you have to send us the image.
    4) Convert OpenPaaS in a PaaS4SLA component. That means that OpenPaaS should extend the Component class and overwrite, at least, the "run" method. See the Manual
    5) Test your component.

    Of course, the OpenPaaS component can be coded using directly JavaScript. CoffeeScript and Javascript modules are full compatible. In the manual the interface is described in CoffeeScript. You only have to translate it to JavaScript syntax.

     
    Link