21:12:18 <adrian_otto> #startmeeting Solum Team Meeting
21:12:19 <openstack> Meeting started Tue Dec 23 21:12:18 2014 UTC and is due to finish in 60 minutes.  The chair is adrian_otto. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:12:20 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:12:22 <openstack> The meeting name has been set to 'solum_team_meeting'
21:12:27 <adrian_otto> #topic Roll Call
21:12:37 <adrian_otto> Adrian Otto
21:12:38 <devkulkarni> devdatta kulkarni
21:12:38 <muralia> murali allada
21:12:55 <keyvan_> keyvan sadeghi
21:12:58 <akshayc> Akshay Chhajed
21:14:03 <adrian_otto> #link https://wiki.openstack.org/wiki/Meetings/Solum Our Agenda
21:14:12 <adrian_otto> (updating that, one moment)
21:15:02 <adrian_otto> #topic Announcements
21:15:10 <adrian_otto> agenda updated, reload.
21:15:27 <adrian_otto> no announcements prepared. Any announcements form team members?
21:15:48 <adrian_otto> Since we changed the meeting time I've been having trouble with my calendar entry
21:16:06 <adrian_otto> I thought I had it fixed, but I missed the meeting reminder again this week
21:16:21 <adrian_otto> please accept my deepest apologies for my late arrivals.
21:16:36 <adrian_otto> I'll be sure that's resolved and that we begin on time next week.
21:16:58 <adrian_otto> next week we are scheduled to meet on 2014-12-30 at 2100 UTC
21:17:05 <akshayc> ok
21:17:06 <adrian_otto> will that work for everyone?
21:17:19 <keyvan_> fine for us
21:17:47 <muralia> yes
21:18:01 <adrian_otto> ok, the week after would be 2015-01-06 at the same time — 2100 UTC
21:18:13 <adrian_otto> so there is no reason to cancel meetings for holidays, correct?
21:18:23 <devkulkarni> right
21:18:28 <adrian_otto> ok, cool.
21:18:38 <devkulkarni> unless folks want to cancel next week's meeting
21:18:41 <adrian_otto> #topic New Contributors
21:18:58 <adrian_otto> welcome to keyvan_ and akshayc
21:19:09 <keyvan_> thanks adrian
21:19:14 <adrian_otto> would you like to give a quick introduction to the team?
21:19:40 <adrian_otto> perhaps about where you reside, and a description of your interest in Solum
21:20:05 <keyvan_> sure, Keyvan Sadeghi, 26, current loc: Iran, graduated Artificial Intelligence from Southampton
21:20:29 <akshayc> hi. I am Akshay. I have used Openstack part of my master's project at NJIT (graduated)
21:20:45 <akshayc> i am located in NJ.
21:21:00 <keyvan_> CEO of the yet to be named startup trying to create the Heroku of Iran
21:21:14 <adrian_otto> we are thrilled to have you join us. I understand you also have a couple of other team members who may also participate?
21:21:15 <devkulkarni> cool. nice to know your backgrounds!
21:21:57 <keyvan_> yes, _ramin, who just ran out off allowed internet traffic
21:22:05 <keyvan_> and back :)
21:22:15 <adrian_otto> welcome _ramin
21:22:16 <_ramin> sry
21:22:23 <_ramin> I'm back
21:23:07 <keyvan_> ramin would you like give an intro?
21:23:13 <_ramin> well
21:23:28 <keyvan_> age, location, why you are interested in solum?
21:23:33 <_ramin> me and keyvan are trying to start startup
21:23:37 <_ramin> here in Iran
21:24:21 <_ramin> and we can use Solum and Openstack combined power and promise for our platform
21:24:38 <adrian_otto> so if you need a little help getting started, please find us in #solum, and you can always reach out to me individually if there is something I can do to lend a hand.
21:24:57 <_ramin> sure, will do
21:25:00 <muralia> welcome guys. this is exciting.
21:25:01 <adrian_otto> I'm sure keyvan_ has my contact details
21:25:01 <keyvan_> sure thing, thanks adrian
21:25:06 <keyvan_> i do
21:25:22 <adrian_otto> #topic Review Action Items
21:25:52 <_ramin> tnx muralia
21:25:55 <adrian_otto> any open items to check from last week?
21:27:13 <keyvan_> do we just reference bug numbers like #1308690 in here?
21:27:49 <adrian_otto> keyvan_: just a moment, we will get there in just a moment
21:27:59 <keyvan_> sorry
21:28:20 <adrian_otto> there were no actions last week
21:28:35 <adrian_otto> #topic Blueprint/Task Review
21:28:55 <adrian_otto> keyvan_: this is where we cover specific work items like bugs and blueprints that require team discussion
21:29:05 <keyvan_> nice
21:29:20 <keyvan_> and the referencing convention is?
21:29:24 <adrian_otto> you put in #link http://url/to/item Title Here
21:29:32 <adrian_otto> and we can cover each one
21:29:37 <muralia> heres the bug keyvan_ is talking about. #link https://bugs.launchpad.net/solum/+bug/1308690
21:29:40 <uvirtbot> Launchpad bug 1308690 in solum "Improvement: Add a Dockerfile for deploying Solum" [Wishlist,Confirmed]
21:30:09 <keyvan_> yes, thanks, that is the one
21:30:32 <adrian_otto> irc://irc.freenode.net:6667/#link https://bugs.launchpad.net/solum/+bug/1308690 Improvement: Add a Dockerfile for deploying Solum
21:30:35 <adrian_otto> ack
21:30:58 <adrian_otto> #link https://bugs.launchpad.net/solum/+bug/1308690 Improvement: Add a Dockerfile for deploying Solum
21:30:59 <uvirtbot> Launchpad bug 1308690 in solum "Improvement: Add a Dockerfile for deploying Solum" [Wishlist,Confirmed]
21:31:09 <adrian_otto> ok, that's what we needed for it to be recorded in the minutes
21:31:16 <adrian_otto> keyvan_:  how are things going with this?
21:31:40 <keyvan_> what i did was to set up a dev environment
21:32:05 <keyvan_> i have a vmware ubuntu 14.04 box with devstack installed
21:32:29 <keyvan_> i believe next step is to decode vagrantfile and re-write it in docker
21:32:56 <keyvan_> that is, do what setup.py does via docker, if im right
21:33:25 <keyvan_> am I?
21:33:40 <devkulkarni> sort of..
21:33:48 <devkulkarni> let me pull up the details..
21:34:04 <devkulkarni> here is what I have in mind for that bug: #link https://review.openstack.org/#/c/87782/
21:34:38 <devkulkarni> the Vagrantfile sets everything up
21:35:00 <devkulkarni> to start all the solum services and the other openstack services required by solum
21:35:07 <adrian_otto> #link https://review.openstack.org/87782 Make solum buildable into docker container
21:35:08 <keyvan_> well, above was my understanding of your comment
21:35:18 <devkulkarni> it uses local.conf.vm/local.conf.docker
21:35:40 <keyvan_> right
21:35:44 <devkulkarni> and also sets things up using the scripts from here https://github.com/stackforge/solum/tree/master/contrib/devstack
21:35:46 <devkulkarni> right
21:35:57 <muralia> devkulkarni: your suggestion mentions running all services in one container. do we want to do that or run them in separate containers?
21:36:18 <_ramin> well, that's sth that we wanted to ask here
21:36:21 <keyvan_> aha, that was something i actually wanted to ask
21:36:27 <devkulkarni> muralia: we might need both. simpler would be to start with all in one probably
21:36:43 <devkulkarni> at least that is what I think. could be wrong
21:36:52 <devkulkarni> keyvan_:
21:36:58 <muralia> sure, the right thing would be to use separate containers. thats the docker model.
21:37:07 <devkulkarni> I think whether to do it in a single setup or separate could be done as part of the investigation
21:37:12 <devkulkarni> sure
21:37:24 <muralia> but i get what you are saying, it should be easy to run all services in one go.
21:37:38 <muralia> so maybe a script to run different containers and hook them up would be nice
21:38:03 <_ramin> should we chack for the existaqnce of the required services?
21:38:11 <devkulkarni> depends on what is the easier path as the first step
21:38:25 <_ramin> cuz u know, they might be available already
21:38:26 <keyvan_> and in the different containers, we don't just invoke setup.py for the module, like the previous patch, right?
21:39:10 <muralia> yes, the dockerfile will start the right service with 'Docker run'
21:39:12 <keyvan_> i mean, connecting bits and pieces from different services shall be done in docker?
21:39:34 <keyvan_> and do the dockerfiles for different services exist?
21:39:39 <devkulkarni> if we are going with separate container per service
21:39:56 <devkulkarni> then the connection bits would be outside of Docker, right?
21:40:08 <keyvan_> seems so
21:40:13 <devkulkarni> no, they don't exist for different services. — at least not for solum services
21:40:32 <devkulkarni> there might be Dockerfiles for Heat etc.
21:40:42 <devkulkarni> but we haven't looked into them
21:41:03 <devkulkarni> so one approach could be we define separate Dockerfiles for each service
21:41:34 <devkulkarni> in this, we will need DFs for: solum-api, solum-builder-api, solum-worker, solum-conductor, solum-deployer, heat, keystone, glance, neutron
21:41:41 <devkulkarni> nova
21:41:59 <devkulkarni> rabbit and mysql could be in their own DF
21:42:00 <keyvan_> so in this case, we decode setup.py for each service, heat, keystone, etc first, ack?
21:42:06 <devkulkarni> ask
21:42:08 <devkulkarni> ack
21:42:30 <keyvan_> ok
21:42:48 <devkulkarni> the main connecting bits actually are
21:42:48 <keyvan_> that might be somthing to benefit these projects as well
21:43:02 <devkulkarni> to connect each solum service to rabbit and mysql
21:43:13 <devkulkarni> connect solum-deployer to heat
21:43:19 <adrian_otto> there is a project that has all the regular OpenStack services working in docker containers
21:43:20 <devkulkarni> connect heat to nova
21:43:26 <akshayc> we should try to sepearate devstack step and solum step
21:43:27 <adrian_otto> it's the greek word for "Glue"
21:43:34 <adrian_otto> starts with K
21:44:16 <akshayc> so we isolate the problems….
21:44:22 <adrian_otto> Lolla
21:44:27 <adrian_otto> #link https://github.com/stackforge/kolla Kolla
21:44:30 <_ramin> I've to agree with akshayc
21:44:33 <keyvan_> nice K there :)
21:44:41 <devkulkarni> keyvan_: yes — that should be helpful to other projects as well
21:44:52 <adrian_otto> so you might look at that in terms of getting the basic OpenStack environment in docker
21:45:03 <adrian_otto> and then see how Solum could be fit into it
21:45:12 <_ramin> we need to diffrentiate between an openstack install and a solum install somehow
21:46:14 <adrian_otto> and for development purposes, nobody really wants to run a whole bunch of containers
21:46:38 <adrian_otto> they probably just one one for the equivalent of devstack, and one for solum
21:46:40 <keyvan_> ok, after seeing if Kolla fits, we continue to solum's setup.py?
21:46:50 <adrian_otto> or one for all of it combined.
21:47:22 <keyvan_> and try to convert that to docker?
21:47:45 <devkulkarni> keyvan_: yeah, that could work as well.. so you are saying
21:47:48 <keyvan_> didn't get that las bit adrian, could you ellaborate?
21:48:08 <devkulkarni> that you will use kolla for setting up heat, keystone, mysql, rabbit, etc. in one or more containers
21:48:34 <devkulkarni> and then use a single container that has just the solum services which are installed using setup.py
21:49:10 <keyvan_> alright, so the mentioned task has already been done by kolla for other services, ack?
21:49:38 <adrian_otto> yes
21:49:39 <devkulkarni> keyvan_: I think we need to investigate that..
21:49:43 <keyvan_> and setup.py is where silum connects to rabbit and mysql?
21:49:50 <adrian_otto> ok, let's open this up for any discussion now
21:50:00 <devkulkarni> keyvan_: yes
21:50:12 <adrian_otto> any other bps or bugs for group discussion before I proceed to Open Discussion?
21:50:29 <keyvan_> devkulkarni: sure, i can do that
21:50:33 <akshayc> dev env
21:50:58 <adrian_otto> #topic Open Discussion
21:51:24 <devkulkarni> akshayc: dev environment — is it not working for you?
21:51:49 <akshayc> no…. it aint
21:52:08 <akshayc> should we work on fixing vagrant first?
21:52:20 <akshayc> or start with docker?
21:52:21 <devkulkarni> akshayc: yes, we should
21:52:47 <devkulkarni> akshayc: you mean starting on the docker-based setup? those are different concerns,
21:53:01 <adrian_otto> let's fix what's there now first
21:53:15 <adrian_otto> and we can scope docker as a separate effort
21:53:41 <devkulkarni> sure.. but if folks want to start on docker-based setup, I think that should be okay
21:53:54 <akshayc> ok… we need a way to ensure vagrant builds correctly
21:54:07 <devkulkarni> akshayc_: let me share with you a bug in which I have some commit ids that I have been using for bunch of projects
21:54:16 <devkulkarni> which allow me to consistently spin up devstack
21:54:28 <akshayc> ok
21:55:26 <akshayc> i am seeing different bugs…. yesterday was #link https://bugs.launchpad.net/tripleo/+bug/1405187 …. similar one in minstral
21:55:27 <uvirtbot> Launchpad bug 1405187 in tripleo "Can't find  SQLAlchemy<=0.8.99,<=0.9.99,>=0.8.4,>=0.9.7" [Critical,Triaged]
21:55:44 <akshayc> causing vagrant dev to fail
21:56:10 <devkulkarni> akshayc: in my experience, our vagrant setup always pulls in the latest code for different services
21:56:22 <devkulkarni> that many times causes the setup to fail
21:56:33 <devkulkarni> one option is to pin to specific commit ids
21:56:49 <akshayc> ok....
21:56:52 <devkulkarni> for the dependent services. agreed that it may cause us integration issues later on.. but
21:57:03 <devkulkarni> at least we are able to move forward with our daily development work
21:57:11 <devkulkarni> at least that is the compromise that I have landed on
21:57:17 <akshayc> hmmm….. ok
21:57:22 <devkulkarni> *still trying to find the bug*
21:57:49 <devkulkarni> #link https://bugs.launchpad.net/solum/+bug/1390246
21:57:51 <akshayc> can we get a stable working dev on last stable openstack release?
21:57:52 <uvirtbot> Launchpad bug 1390246 in solum "No valid host found when trying to run coreos template through Heat" [Undecided,New]
21:58:04 <devkulkarni> akshayc: that's a good point.
21:58:29 <akshayc> with pinned commits
21:58:50 <akshayc> so it just works and i can roll back to that
21:58:59 <devkulkarni> we could do that.. pin to juno for example..
21:59:27 <akshayc> yep…. that will be good
21:59:50 <devkulkarni> akshayc: do you want to lead that effort for us? we all will pitch in but you can take charge of it probably?
22:00:00 <akshayc> ok….
22:00:05 <devkulkarni> cool!!
22:00:34 <devkulkarni> thanks akshayc. having a consistently working devstack is a must for development work
22:01:09 <akshayc> i have been trying to setup one here #link https://github.com/akshaychhajed/vagrant-solum-dev/tree/solum_temp_changes
22:01:36 <devkulkarni> cool
22:01:51 <devkulkarni> I know that ed cranford has some changes
22:01:57 <devkulkarni> and I have some changes as well
22:02:06 <akshayc> ok…
22:02:20 <devkulkarni> all these can be combined and then we can test with juno commits
22:03:15 <akshayc> yep…. i hope to bring it to the point where the examples work
22:03:38 <devkulkarni> that will be awesome!!
22:03:50 <devkulkarni> feel free to ping me on #solum anytime
22:04:04 <devkulkarni> if you want to discuss details about the vagrant setup
22:04:20 <akshayc> ok. thanks!
22:11:52 <_ramin> so, if there are not anythin else to discuss, can I ask if anyone is working on completing the wiki?
22:12:16 <adrian_otto> thanks everyone
22:12:19 <adrian_otto> #endmeeting