#solum

Swati Dewan proposed openstack/solum-dashboard: Add the languagepack create functionality to the dashboard https://review.openstack.org/342380

good morning / good evening

Hey devkulkarni :)

hi devkulkarni pt_15

Hi Ablu

hi pt_15

hi Ablu

we will have our weekly irc meeting in 10 minutes

here is our agenda: https://wiki.openstack.org/wiki/Meetings/Solum#...

vijendar: good morning

we are having weekly irc meeting in openstack-meeting-alt

devkulkarni1: sorry…forgot about that :(

no worries, its still going on

devkulkarni1: thanks for hosting

Hi devkulkarni1

hi shivaSR

Got a minute?

sure

Thanks. So in the build-app script that you pointed me to, I notice that in the final stage of creating the docker file there is a script called build.sh. I can't seem to figure out where this script comes into play and its purpose.

ah right

that was the part about languagepack contract which I said yesterday that I will talk about later, but forgot

oh, lol.

so that script is part of the lp contract of required by solum .. it is to be provided in the repository of the lp.. let me show an example which will make it clear

look at this repo: https://github.com/rackspace-solum-samples/solu...

the build.sh contains the command 'pip install -r requirements.txt'

the build.sh will be executed at the application build time when app requirements have become known

so this contract allows us to separate generic requirements from application specific requirements

the generic requirements (i.e. libraries/tools etc.) which are required by all apps (say, all python apps) would be defined in the Dockerfile

on the other hand, application-specific requirements are typically defined in application-specific way (requirements.txt in python, package.json in nodejs, pom.xml for java)

so build.sh is the mechanism that allows installing of application requirements at application build time (only after application requirements have become known)

let me show other examples

cool. So, then would is be good practice for a unikernel language pack to contain instructions required to compile an application after installing the requirements? or should this be done in a separate script?

so both would work, only that the approach of separating the compilation of the application into a script would follow closely the philosophy of solum's application build step

may be you can first try that

anyways you will have to define build.sh in your lp repository..

application compilation would be last step in build.sh

similar to the java languagepack, where mvn package is the last command in its build.sh

that will install the requirements *and* create application war file

cool. seems very clear to me now...I notice in the examples for nodejs and java build.sh is in a subdirectory ./bin while the python example had it in the same directory as the docker file. is there any reason for this difference?

either should work.. copying of the build.sh or the bin directory is last step in Dockerfile. (checking build-app to double check if there is any difference) ..

all, will be back after lunch

pt_15: your still around?

devkulkarni1: yeah

pt_15: I am getting error in creating languagepack. filling bug now

you can take a look at it tomorrow as it is very late for you today

Oh cool, alright, I will :)

pt_15: https://bugs.launchpad.net/solum/+bug/1607087

list, show, and delete worked for me

pt_15: also, once we have merged lp and app patches, one of the quick things that you should do is submit patches to get rid of Assemblies from the dashboard code

devkulkarni1: oh OK cool, I'll do that :)

I'll take a look at the bug you're encountering tomorrow :)

yep, I was going to suggest that you prioritize that over app patches

that way, we can keep on the target of merging lp patches this week

Yeah exactly what I was thinking too :)

pt_15: also, I would encourage you to write a blog post on how to do horizon related development — include things like - where are logs stored, how to debug the code, how to restart apache, and any other general setup things that you had to do. it will be helpful for anyone who wants to start working on horizon either in Solum or other projects

devkulkarni1: yes, sure, I'll work on that :)

yeah.. I would encourage treating it as not something as a todo item, but more as your way to share your understanding/work so that others will benefit from it

Yeah I had actually been thinking of something along these lines, and had thought of perhaps working on it over the weekend

Good, take your time. As I said, I don't want you think of it as an item that you have to complete, but treat it as an opportunity to share your knowledge. That is how value gets added to an open community. Also, you will be able to point others to this blog post who might be getting started on horizon development. In the future you can become someone who is knowledgeable about horizon and solum and can help out others in horizon

Yes, i completely understand. I will make sure i think of the blog as a way of sharing my knowledge and a way of helping people who are getting started, rather than something that needs to be done.