17:00:17 #startmeeting Solum Team Meeting 17:00:18 Meeting started Tue Mar 8 17:00:17 2016 UTC and is due to finish in 60 minutes. The chair is devkulkarni. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:19 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:21 The meeting name has been set to 'solum_team_meeting' 17:00:34 #topic Roll Call 17:00:38 Devdatta Kulkarni 17:00:40 Ashish Jain 17:01:16 hi ashishjain.. lets wait for few minutes for others to join 17:01:38 in the mean time, here is the agenda for today: https://wiki.openstack.org/wiki/Meetings/Solum#Weekly_Solum_Team_Meeting 17:01:49 hi devkulkarni 17:03:00 btw I see we have released a new component solum guest agent 17:03:16 ashishjain: it is not new 17:03:27 we have it, but have never used it 17:03:29 o/ 17:03:35 hi vijendar 17:03:41 devkulkarni, okay 17:03:42 we have ashishjain with us as well 17:04:08 lets wait for another minute and then we can get started 17:04:16 hi vijendar 17:04:19 devkulkarni: Hi! 17:04:35 pt_15: hi 17:04:42 good to see you for the meeting 17:04:50 we have ashishjain and vijendar with us as well 17:05:29 pt_15 and ashishjain: I wanted to get you two introduced as you are in the same timezone (in India) 17:05:40 finally both of you are in the same meeting :) 17:06:08 pt_15 hi 17:07:05 it will be good to brainstorm and discuss between you two if you run into any issues 17:07:12 devkulkarni, agreed 17:07:19 alright, lets get started 17:07:28 here is the agenda: https://wiki.openstack.org/wiki/Meetings/Solum#Weekly_Solum_Team_Meeting 17:07:36 #topic Announcements 17:07:43 1) Our CI/CD talk has been accepted for the Austin summit 17:07:49 https://www.openstack.org/summit/austin-2016/summit-schedule/events/7842 17:07:54 congratulations ashishjain 17:07:55 ashishjain: Hi! 17:08:14 Sorry, my internet connection is a little slow today 17:08:17 Congratulations devkulkarni, excited to see this 17:08:28 yes, this is very exciting 17:08:29 congrats to ashishjain and devkulkarni 17:08:36 thanks vijendar 17:08:38 vijendar thanks 17:08:45 we all worked towards this actually 17:08:55 so congratulations to the entire team 17:08:58 yeah absolutely, 17:09:07 congrats to everyone 17:09:12 we now have official time and place to talk about solum 17:09:13 :) 17:09:38 lets work towards making this a great presentation now 17:09:39 absolutely 17:09:58 let's us know if we can help in any way to make this talk a success 17:10:11 +1 vijendar 17:10:18 surely vijendar 17:10:29 ashishjain: let us know if you need any help with Austin travel 17:10:48 we should be able to provide you with pointers to hotels etc. 17:10:57 I am sure the openstack summit website will have this info 17:10:58 devkulkarni, sure I am anyways coming to your city this time :D 17:11:04 yep 17:11:33 devkulkarni, My organisation will take care of this but will definitely get in touch with you guys for any pointers 17:11:43 sounds good 17:11:52 yeah, vijendar and I both are in Austin 17:11:56 This is my first US travel to so will definitely need lot of pointers :) 17:11:57 and dimtruck and mkam 17:12:02 oh okay 17:12:15 wow thats nice 17:12:18 best flight for you might be Bangalore - London - Austin 17:12:38 we can try to get together as Solum team for a dinner/lunch if folks are interested 17:12:44 cool, how much time does it take to US from Bangalore 17:13:12 16/17 hours of travel time. if you stop in europe it is roughly half each way 17:13:22 devkulkarni, that would be cool, I think last day when the summit ends could be a good day? 17:13:41 there are directly flights to Austin from London, New Jersey, Houston 17:13:45 ashishjain: sure 17:13:55 and openstack anyways provides lot of opportunities to have fun together 17:14:02 let me check with folks and see if we can do something 17:14:07 yes, that is true 17:14:29 devkulkarni, thanks for these flight stuff 17:14:45 ashishjain: if you direct flights from banglore to NJ or London, that will be the easiest route for you 17:14:57 How will weather be in austin, I think it would be pleasant as you pointed out sometime back 17:14:59 if not, then you might have to take two stop flights 17:15:08 yes, the weather will be very pleasant 17:15:21 aah okay, would see if I can get direct flight 17:15:23 you would not need to bring snow jacket or anything 17:15:39 a light sweater/jacket and a umbrella should be enough 17:15:56 okay, does it rain at this point of time there ? 17:16:15 it does occasionally. 17:16:20 okay 17:16:39 alright.. lets continue 17:16:53 we can discuss more about logistics in the open discussion or on solum irc channel 17:16:57 2) Solum library releases 17:17:03 http://lists.openstack.org/pipermail/openstack-announce/2016-March/000987.html 17:17:08 Solum library releases 17:17:13 http://lists.openstack.org/pipermail/openstack-announce/2016-March/000988.html 17:17:17 http://lists.openstack.org/pipermail/openstack-announce/2016-March/000986.html 17:17:44 congratulations to the complete team on these releases 17:17:46 last week the openstack-release team tagged releases for python-solumclient, solum-dashboard, and solum-infra-guestagent 17:18:00 yes, heartiest congratulations on the releases 17:18:10 the release for solum itself is also done 17:18:11 btw why is solum not listed on this? 17:18:27 I don't know why the email did not go out on the openstack-announce list 17:18:31 ^ 17:18:41 was planning to check with the release team about this 17:18:46 aah okay, so it has been released 17:18:55 solum-dashboard? 17:18:59 either that, or it will be released this week 17:19:02 solum guest agent? 17:19:20 devkulkarni, do we have more details on these 2 components 17:19:24 ashishjain: solum-dashboard is horizon plugin for solum 17:19:37 okay 17:19:41 we are trying to revive it these days 17:19:57 now that we have end-to-end app deployment working using cli 17:20:08 yeah 17:20:12 it will be great if we have the horizon plugin working before the summit 17:20:28 pt_15 is leading this effort 17:21:03 pt_15: do you want to share with the team what have you learnt so far wrt to the solum-dashboard? 17:21:03 pt_15 ohh wow, nice 17:21:45 pt_15 has slow internet connection 17:22:02 yeah 17:22:05 so while we wait to hear from her, let us continue 17:22:28 3) Mitaka global bug smash happening this week (March 7 - 9) 17:22:57 if any of you are participating, let me know what bugs you are working on 17:23:09 4) Updates on end-to-end application deployment in devstack 17:23:15 https://github.com/devdattakulkarni/solum-provenance/blob/master/steps-to-enable-solum-with-devstack 17:23:19 https://github.com/openstack/solum/blob/master/devstack/devstack-provenance 17:23:30 https://github.com/rackerlabs/vagrant-solum-dev 17:23:38 ashishjain: this update is especially for you 17:23:50 devkulkarni, yeah looking 17:23:51 let me give details about each of those links 17:23:59 yeah 17:24:18 the first link is compilation of steps to get to working solum setup in devstack 17:24:34 so now we need to follow these steps to build solum? 17:24:41 vijendar, pt_15, and I have all tried those steps and they work 17:24:51 ashishjain: not necessarily 17:24:57 so we no longer use vagrant? 17:25:00 you can also use vagrant 17:25:07 that is the third link above 17:25:13 okay but these steps are no longer valid 17:25:16 I have updated vagrant to use these steps as well 17:25:43 http://docs.openstack.org/developer/solum/getting_started/ 17:25:52 no the steps given in https://github.com/devdattakulkarni/solum-provenance/blob/master/steps-to-enable-solum-with-devstack are the steps that one can use to setup solum without vagrant 17:26:00 vagrant up --provision devstack? 17:26:06 ashishjain: that will also work 17:26:07 aah okay 17:26:11 cool 17:26:16 ashishjain: let me give some background 17:26:21 devkulkarni: ashishjain: wrt to the solum-dashboard one of the main things that needed to be done was rearranging of the folder since the new horizon plugin api requires a different structure than the current one 17:26:37 sure devkulkarni 17:27:02 couple of weeks back, former ptl of cinder asked us in our irc meeting if there are any steps to start solum in devstack without using vagrant 17:27:28 that led me to creating this: https://github.com/devdattakulkarni/solum-provenance/blob/master/steps-to-enable-solum-with-devstack 17:27:40 okay 17:27:45 of course, the main issue for us for the longest time has been that the app not becoming READY 17:27:54 I wanted to solve that as well 17:28:13 correct 17:28:17 how did you solve it? 17:28:27 after lot of trial and error and googling, I realized that the issue is with neutron and IPv6 17:28:34 so the solution is this: 17:28:54 in local.conf we have set variables to make neutron not create IPv6 subnets at all 17:29:15 https://github.com/devdattakulkarni/solum-provenance/blob/master/local.conf#L24 17:29:20 https://github.com/devdattakulkarni/solum-provenance/blob/master/local.conf#L25 17:29:30 that is all 17:29:42 this causes neutron to only create ipv4 subnets 17:30:00 nice, so earlier was neutron only creating ipv6? 17:30:10 and this in turn allows nova and docker to correctly use ipv4 addresses 17:30:22 no, neutron was creating both ipv6 and ipv4 17:30:38 okay 17:30:41 what was happening was, randomly nova would get ipv6 address from neutron 17:30:57 okay 17:31:05 and that was causing issues for docker 17:31:16 it is explained in this link: 17:31:42 http://blog.oddbit.com/2015/02/11/installing-novadocker-with-devstack/ 17:31:51 check the comment by nindate 17:32:01 that comment was the clue 17:32:14 so ashishjain 17:32:23 if you currently have devstack vm 17:32:36 I would suggest add those two configuration variables in local.conf 17:32:43 and then try unstack and stack 17:33:10 if you don't have devstack vm, I would suggest to pull latest Vagrantfile from vagrant repo 17:33:17 and then try vagrant up —provision 17:33:34 ashishjain: about the liberasurecode issue 17:33:38 devkulkarni, just updated the vagrant source, will that help? 17:33:56 yes, that should help 17:34:03 aaah ya that should help 17:34:04 I have fixed the liberarurecode issue in Vagrantfile 17:34:07 https://github.com/rackerlabs/vagrant-solum-dev/blob/master/Vagrantfile#L263 17:34:43 actually I tried manually installing this library .. liberasurecode-dev somehow it fails all th time 17:35:03 anyways thanks for these fixes devkulkarni 17:35:06 ashishjain: most likely it is failing because it it not finding in sources 17:35:13 will try it out and let you know my feedback 17:35:17 liberasurecode-dev is available in trusty-backports 17:35:29 we need to add it to sources 17:35:34 devkulkarni, aah okay I was adding main universe 17:35:40 echo "deb http://archive.ubuntu.com/ubuntu trusty-backports main restricted universe multiverse" >> /etc/apt/sources.list 17:35:47 echo "deb-src http://archive.ubuntu.com/ubuntu trusty-backports main restricted universe multiverse" >> /etc/apt/sources.list 17:36:06 check lines 263-268 in Vagrantfile 17:36:13 devkulkarni, yeah it is there in the Vagrantfile 17:36:27 ashishjain: definitely try it and let me know if it works for you or not 17:36:39 devkulkarni, sure 17:36:48 cool 17:36:53 thanks pt_15 17:37:07 alright 17:37:11 lets move next topic 17:37:19 #topic Action Items 17:37:26 (done) Sending space request to summit organizers. Have requested for 1 fishbowl session and 1 work session OR 1 fishbowl session. 17:37:59 By last friday all the projects were required to submit request for the space required at the Austin summit to the summit organizers 17:38:01 devkulkarni, what is fishbowl session 17:38:22 ashishjain: the same kind of session that we had in Tokyo 17:38:38 okay and what about design summit 17:38:45 basically a session to provide overall project details etc. 17:38:58 devkulkarni, okay 17:39:05 ashishjain: fishbowl and worksessions are part of the design summit 17:39:09 fishbowls are meant to be discussion sessions 17:39:12 the difference between the two is this 17:39:23 worksessions are meant to be like a code sprint session 17:39:28 yes 17:39:44 it is mainly meant for the contributors 17:39:47 anteaya, thanks 17:39:50 welcome 17:40:09 to come together and discuss about next items to work on etc. 17:40:12 okay so we have only 1 design session 17:40:29 ashishjain: we have requested for 1 work session and 1 fishbowl session 17:40:40 I think that should be enough for us 17:40:40 devkulkarni, okay 17:41:06 if we don't get work session (due to space constraints), then we have requested for 1 fishbowl session 17:41:25 this time around there are several new projects and the space is limited 17:41:26 okay 17:41:35 cool 17:41:38 what are the new projects devkulkarni 17:42:01 ashishjain: there were quite a few accepted into the the big tent. don't remember off the top of my head 17:42:10 can find out before the next meeting 17:42:14 devkulkarni, sure let us discuss on out channgel 17:42:22 sounds good 17:42:23 *our channel 17:42:38 lets quickly go through the next topics 17:42:50 #topic Patches for Review 17:42:57 1) Solum dashboard 17:43:01 https://review.openstack.org/#/q/project:openstack/solum-dashboard+status:open,n,z 17:43:05 https://review.openstack.org/#/c/277197/ 17:43:19 these are patches on the solum-dashboard repo 17:43:45 looks like all of them are failing due to similar issues 17:43:56 pep8 is failing because of some pbr issue 17:44:20 if any of you have time, check out the errors and see if you get any ideas 17:44:31 what is going on with https://review.openstack.org/#/c/263624/ 17:44:33 I will also spend some time today looking at these 17:44:44 vijendar: yes, good point 17:44:48 all gates are failing for this 17:45:00 vijendar: I was looking into it this morning 17:45:10 for pep8, it looks to be a pbr issue 17:45:11 http://logs.openstack.org/24/263624/2/check/gate-solum-dashboard-pep8/10f7137/console.html 17:45:31 http://logs.openstack.org/24/263624/2/check/gate-solum-dashboard-pep8/10f7137/console.html#_2016-03-08_09_56_52_882 17:45:57 same thing for the docs gate 17:45:58 http://logs.openstack.org/24/263624/2/check/gate-solum-dashboard-docs/57b6f45/console.html#_2016-03-08_09_54_13_383 17:46:03 ok 17:46:34 same for py27 17:46:35 http://logs.openstack.org/24/263624/2/check/gate-solum-dashboard-python27/a64902e/console.html#_2016-03-08_09_53_19_706 17:47:03 and for pypy 17:47:04 http://logs.openstack.org/24/263624/2/check/gate-solum-dashboard-pypy/2bc79c1/console.html#_2016-03-08_09_55_06_928 17:47:06 None of these links seems to be working http://git.openstack.org/cgit/stackforge/solum-infra-guestagent 17:47:16 https://bugs.launchpad.net/solum-infra-guestagent 17:47:37 ashishjain: where did you get these links? 17:47:53 devkulkarni, the guest agent announcement 17:47:59 vijendar: I am suspecting that fixing that pbr issue will unblock all the other patches as well 17:48:04 ashishjain: oh ok 17:48:05 http://lists.openstack.org/pipermail/openstack-announce/2016-March/000986.html 17:48:06 let me check 17:48:09 ok 17:49:10 ashishjain: hmm.. strange 17:49:17 I will check with the release team about this 17:49:21 thanks for catching it 17:49:50 I haven't looked at the other announcement emails 17:49:56 will be good to check those as well 17:50:18 solum-dashboard mail does not have any links 17:50:31 how about python-solumclient 17:50:52 that too does not have any links 17:51:00 about source, or other details 17:51:12 ok, so it is just the solum guest agent 17:51:28 let me check with the release team about this 17:51:39 ideally announcements will not have any links? 17:52:05 seems like some announcements have links some others don't 17:52:24 probably, the first announcement of a project might have links in that annoucement 17:52:42 since this was probably the first announcement for guest agent, hence it had links 17:52:43 ok 17:52:57 I don't remember if we had released it before 17:53:06 cool 17:53:17 we have just about 7 minutes 17:53:28 let me skip over to open discussion 17:53:36 the bugs which I have listed are from last week 17:53:48 no new bug has been filed in this week 17:54:09 vijendar: I saw that you had updated the separate app data and param data bug description with details 17:54:13 thanks for that 17:54:21 #topic Open discussion 17:54:30 1) Push to move away from WSME 17:54:34 http://lists.openstack.org/pipermail/openstack-dev/2016-March/088658.html 17:54:50 there was an email this morning about wsme 17:55:16 basically, wsme seems to be not well maintained and folks are suggesting projects to move away from it if possible 17:55:22 we use wsme and pecan 17:55:37 it will be good for us to figure out what will it take to move away from wsme 17:55:53 2) Keystone single sign-on research 17:55:58 http://lists.openstack.org/pipermail/openstack-dev/2016-March/088674.html 17:56:05 This came out today as well. 17:57:16 3) Configuration management tool for OpenStack 17:57:19 http://lists.openstack.org/pipermail/openstack-dev/2016-March/088518.html 17:57:47 ashishjain: I thought you might be able to provide feedback on this thread based on your use of kolla and openstack-ansible 17:58:00 4) New API guidelines for review 17:58:05 http://lists.openstack.org/pipermail/openstack-dev/2016-March/088568.html 17:58:13 there are new API guidelines for review 17:58:36 I had some comments regarding header definitions 17:58:47 devkulkarni, OpenStack CM 17:58:59 if you have interest, I would encourage you to check the patch and provide any feedback 17:59:16 ashishjain: yeah, openstack configuration management 17:59:36 that is all I had in open discussion 17:59:39 anything else that we should discuss today? 18:00:09 alright.. it is top of the hour 18:00:21 thanks vijendar, ashishjain, pt_15 for joining today's meeting 18:00:23 thanks devkulkarni 18:00:35 see you next week (and in solum irc channel before that) 18:00:39 #endmeeting