13:59:51 <devkulkarni> #startmeeting Solum Team Meeting
13:59:53 <openstack> Meeting started Wed Jun  8 13:59:51 2016 UTC and is due to finish in 60 minutes.  The chair is devkulkarni. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:59:54 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:59:56 <openstack> The meeting name has been set to 'solum_team_meeting'
14:00:02 <devkulkarni> #topic Roll Call
14:00:07 <devkulkarni> Devdatta Kulkarni
14:00:41 <Ablu> Hi
14:00:48 <devkulkarni> hi Ablu
14:02:01 <zhurong> 0/
14:02:07 <devkulkarni> hi zhurong
14:02:25 <zhurong> hi devkulkarni
14:02:37 <devkulkarni> nice to see you and Ablu
14:02:51 <devkulkarni> hopefully others will join in
14:03:01 <devkulkarni> in the meanwhile here is the agenda for today: https://wiki.openstack.org/wiki/Meetings/Solum#Weekly_Solum_Team_Meeting
14:03:36 <devkulkarni> please feel free to add to it if you want to discuss any specific thing
14:03:57 <devkulkarni> otherwise we can just discuss those items during our open discussion
14:04:32 <Ablu> hi zubchick
14:04:34 <Ablu> eh
14:04:37 <Ablu> sorry
14:04:41 <Ablu> hi zhurong
14:04:51 <zhurong> hi Ablu
14:05:19 <devkulkarni> #topic Announcements
14:05:41 <devkulkarni> I don't know have new announcements for this week. The two listed in the agenda are from last week
14:05:57 <devkulkarni> 1) New meeting time and channel. 1400 UTC on Wednesday in openstack-meeting-alt
14:06:21 <devkulkarni> We have already started on this as today is our second meeting at new time and in new channel
14:06:35 <devkulkarni> how is it working out for you folks?
14:06:47 <Ablu> a lot better
14:07:01 <devkulkarni> cool.. really glad to know that
14:07:23 <devkulkarni> folks in Austin are still getting used to it I think
14:07:24 <Ablu> I can stay at university till 16:00
14:07:34 <devkulkarni> nice
14:07:34 <Ablu> 19:00 was a bit late
14:08:16 <devkulkarni> yeah, it was late. especially for zhurong caowei and pt_15
14:08:50 <zhurong> now is 22:00 in CST time
14:08:53 <devkulkarni> hopefully as time goes by folks will start remembering about this new time and will join
14:09:22 <zhurong> I think they will :)
14:09:34 <devkulkarni> zhurong: so it is still bit late for you, may be it is cutting into your dinner time
14:10:02 <devkulkarni> but an even earlier time would not work for US folks
14:10:07 <zhurong> this time is so good to me, devkulkarni
14:10:24 <zhurong> we usually have dinner at 19:00
14:10:29 <devkulkarni> that is very good to hear to zhurong
14:10:32 <devkulkarni> oh perfect
14:10:53 <devkulkarni> nice nice
14:11:06 <devkulkarni> good to know that new time is convenient for our current members
14:11:57 <devkulkarni> I like to keep meeting times aligned with what works for the folks who are active.. earlier we used to have meetings on tuesday at 2200 UTC
14:12:16 <devkulkarni> at that time the only active folks were from US ..
14:12:27 <devkulkarni> we then changed it to tuesday 1700 UTC
14:12:35 <devkulkarni> and now wednesday 1400 UTC
14:13:15 <devkulkarni> I think we our current time we might have hit perfect timing that works for most of the timezones
14:13:21 <devkulkarni> alright
14:13:39 <devkulkarni> the second announcement, which I am repeating from last time, is about the Barcelona summit
14:13:44 <zhurong> yes, I think so
14:13:52 <devkulkarni> 2) Barcelona summit submissions are now open https://www.openstack.org/summit/barcelona-2016/faq/
14:13:52 <devkulkarni> •	Deadline: July 13, 2016
14:14:31 <devkulkarni> let me know if you want to submit something to Barcelona summit and need any help
14:15:05 <devkulkarni> some of the ideas that vijendar and I have been considering to submit are listed in this etherpad:
14:15:06 <devkulkarni> https://etherpad.openstack.org/p/solum-barcelona-2016
14:15:57 <devkulkarni> for the Austin summit, I collaborated with folks from Wipro for the CI/CD talk, which was accepted
14:16:41 <devkulkarni> so if you have any ideas that you would like to brainstorm, or need help with solum side implementation to validate them, then let me know
14:17:31 <devkulkarni> hi caowei
14:18:03 <devkulkarni> alright.. so those were announcements that I had
14:18:14 <devkulkarni> do any of you have any announcements for the rest of us?
14:18:52 <zhurong> just no for me
14:18:53 <devkulkarni> ok
14:19:01 <devkulkarni> thanks zhurong
14:19:02 <caowei> sorry， my wifi is broken just now
14:19:11 <devkulkarni> caowei: :) no worries
14:19:39 <devkulkarni> #topic Discussion
14:19:47 <devkulkarni> Solum configurations: https://wiki.openstack.org/wiki/Solum/configurations
14:20:08 <devkulkarni> In the last meeting caowei had requested this
14:20:50 <devkulkarni> basically, solum can be configured to deploy containers directly (using nova-docker), or deploying them on a VM
14:21:23 <devkulkarni> Above document talks about these two configurations and how to enable them
14:22:03 <devkulkarni> note that the deploy-container-on-vm option needs some work to get it working in devstack
14:22:38 <devkulkarni> essentially a VM image needs to be loaded in glance
14:22:51 <devkulkarni> currently the devstack plugin does not do this
14:23:01 <devkulkarni> it has to be done manually
14:23:09 <caowei> Deploying DU on VM
14:23:21 <devkulkarni> caowei: yep
14:23:23 <caowei> I'm not clear for this
14:23:37 <devkulkarni> caowei: which part is not clear?
14:23:52 <Ablu> DU = distribution unit iirc
14:23:57 <devkulkarni> I wrote it very late last night, so it is possible that the content is not clear
14:24:13 <devkulkarni> DU = deployment unit
14:24:25 <devkulkarni> that is the term we use to call an 'application container'
14:24:52 <caowei> devkulkarni: I can't deploy it
14:24:56 <devkulkarni> if it is confusing, you can just mentally map DU to application container
14:25:51 <Ablu> ah... right
14:26:07 <devkulkarni> caowei: can you elaborate? did you try to follow the steps for deploying container on VM? did you make all the changes that I have listed in the document?
14:27:08 <caowei> In nova's /etc/nova/nova.conf, set the compute_driver value to 'libvirt.LibvirtDriver'.
14:27:20 <devkulkarni> caowei: as I was mentioning ealier, you will need to load a image in Glance
14:27:48 <devkulkarni> caowei: once you set that option you need to restart nova services
14:27:57 <devkulkarni> I will add that to the document
14:28:25 <Ablu> hi pt_15
14:28:38 <pt_15> hi Ablu!
14:29:05 <devkulkarni> hi pt_15
14:29:15 <pt_15> hi devkulkarni!
14:29:26 <caowei> devkulkarni : If i need to install the Libvirt steps ?
14:29:27 <devkulkarni> good to see you in the meeting
14:29:56 <pt_15> glad to be here, hope I'm not too late?
14:29:57 <devkulkarni> caowei: I am updating the document right now.. give me a minute .. after that let me know if things are clear
14:30:19 <devkulkarni> pt_15: we are half way in the meeting
14:31:34 <Ablu> pt_15: log so far: http://sprunge.us/YRZK
14:33:00 <pt_15> oh ok cool, thanks Ablu! :)
14:33:29 <devkulkarni> caowei: https://wiki.openstack.org/wiki/Solum/configurations#Deploying_DU_on_VM
14:33:50 <devkulkarni> caowei: I have added instructions for how to restart nova services
14:35:04 <caowei> OK
14:35:17 <devkulkarni> caowei: in addition to changing the config and restarting services, you will need to first load a VM image in Glance
14:35:18 <devkulkarni> as I was mentioning earlier, our devstack plugin does not do this yet
14:36:00 <devkulkarni> caowei: let me know how your testing goes
14:36:47 <devkulkarni> caowei: btw, when is your blog post due?
14:38:22 <devkulkarni> caowei: hopefully you are able to test it end-to-end before that
14:38:48 <devkulkarni> #topic Patch Reviews
14:39:39 <devkulkarni> I have been looking at getting the github webhook functionality working again
14:39:51 <devkulkarni> I have submitted two patches — one for the api and one for the cli
14:39:59 <devkulkarni> the way this works is as follows:
14:40:33 <devkulkarni> you can setup a github webhook when you register an app with solum
14:40:53 <devkulkarni> (this is done by passing in —setup-trigger flag with solum app create)
14:40:57 <caowei> devkulkarni : I tried to change local.conf
14:41:25 <devkulkarni> caowei: you should not need to change anything in local.conf
14:42:00 <caowei> Yes, I was wrong
14:42:10 <devkulkarni> caowei: ok
14:42:28 <devkulkarni> caowei: the only changes that you will need are in /etc/nova/nova.conf and /etc/solum/solum.conf
14:43:06 <devkulkarni> caowei: I will add/improve the document later today if I think of anything that might be missing
14:43:27 <devkulkarni> caowei: will be good if you are able to get it working in devstack setup
14:43:39 <devkulkarni> I  have been wanting that for a while
14:43:55 <devkulkarni> the setup works in our internal deployment at rackspace
14:44:40 <devkulkarni> ok, so going back to the github trigger functionality..
14:45:12 <devkulkarni> once a webhook has been registered for a repository, anytime you create a new pull request, or you update an existing pull request, a trigger is sent to Solum
14:45:23 <caowei> I try it again.
14:45:26 <devkulkarni> specifically to Solum API
14:45:32 <devkulkarni> caowei: sounds good
14:46:25 <devkulkarni> Solum then executes the workflow steps that have been configured for that app (some combination of unittest, build, deploy)
14:47:04 <devkulkarni> here are the two patches:
14:47:13 <devkulkarni> (Github webhook handling) https://review.openstack.org/#/c/326224/
14:47:13 <devkulkarni> (Github webhook setup) https://review.openstack.org/#/c/326222/
14:47:23 <devkulkarni> currently they have -1 from Jenkins
14:47:36 <devkulkarni> I will be addressing that today
14:47:59 <devkulkarni> I have also updated README with how to test the github functionality
14:48:10 <devkulkarni> it is in this patch
14:48:19 <devkulkarni> https://review.openstack.org/#/c/326224/5/examples/apps/README
14:48:37 <devkulkarni> if any of you have some time to test the patches that would be awesome
14:48:48 <caowei> No module named libvirt
14:48:50 <devkulkarni> btw, I don't know if I shared how to test a patch
14:49:16 <caowei> If i need to install the Libvirt steps ?
14:51:01 <devkulkarni> the way to test a patch is to download it (by clicking on the download link on the review) and restarting solum services (only required for api side patches)
14:51:21 <devkulkarni> caowei: hmm .. may be the location of the driver changed
14:51:52 <devkulkarni> caowei: lets continue after the meeting in solum channel
14:52:06 <caowei> OK
14:52:16 <devkulkarni> alright, so its 10 minutes to the end
14:52:30 <devkulkarni> #topic Open Discussion
14:52:40 <devkulkarni> Ablu, pt_15: how are things going for you?
14:52:52 <devkulkarni> Ablu: how is your tool research coming along?
14:53:05 <Ablu> I am writing a heat plugin at the moment
14:53:08 <devkulkarni> pt_15: have you prepared the google doc?
14:53:11 <devkulkarni> Ablu: cool
14:53:15 <Ablu> that is working 99%
14:53:16 <pt_15> devkulkarni: things going alright, still working on the languagepack thing
14:53:24 <Ablu> but i cannot pass the result back to nova somehow
14:53:30 <Ablu> trying to debug it at the moment...
14:53:39 <Ablu> but remote debugging heat is not that nice
14:53:50 <devkulkarni> pt_15: please submit your patches as you work on them
14:53:56 <devkulkarni> it will be easy to review
14:54:07 <devkulkarni> also you don't want to create one big patch
14:54:17 <devkulkarni> Ablu: I see
14:54:43 <devkulkarni> Ablu: have you reached out to folks from heat team
14:54:57 <pt_15> devkulkarni: ok, cool, i thought i would submit a patch once i managed to get the basic functionality for languagepack working
14:54:58 <devkulkarni> also you can ping vijendar on solum channel
14:55:23 <devkulkarni> pt_15: you can keep on submitting as many revisions on a patch as you like
14:55:40 <Ablu> devkulkarni: i am talking to them on #heat this very second
14:55:42 <devkulkarni> for example, see how I have submitted several revisions of my patches
14:55:50 <devkulkarni> Ablu: cool
14:56:18 <devkulkarni> pt_15: submitting patches early allows rest of the team to know what the patch author is working on
14:56:53 <devkulkarni> this can help in doing course correction if the direction in which the author is headed may not be correct
14:57:20 <devkulkarni> pt_15: btw, have you figured out how to test your patches?
14:57:50 <devkulkarni> please find that out before you do lot of work..
14:58:12 <devkulkarni> testing means — how to load the new code in horizon, how to set a breakpoint and debug, etc.
14:58:42 <devkulkarni> hopefully horizon team will be able to provide you with pointers on these
14:59:04 <pt_15> yes, i did talk to the horizon team regarding loading the new code
14:59:36 <devkulkarni> pt_15: ok good.. as I had mentioned earlier, please keep good notes of all the suggestions that you get from horizon team
14:59:47 <pt_15> so testing the code is not a problem at all :)
14:59:50 <devkulkarni> add those either to the etherpad that we have earlier created, or to the doc
15:00:01 <devkulkarni> pt_15: ok
15:00:04 <devkulkarni> alright..
15:00:11 <devkulkarni> we are at the end of our meeting time
15:00:17 <devkulkarni> thanks for joining the meeting today
15:00:20 <devkulkarni> see you next week
15:00:23 <pt_15> devkulkarni: ok, i'll add the notes to the etherpad too :)
15:00:24 <devkulkarni> #endmeeting