14:00:37 <devkulkarni> #startmeeting Solum Team Meeting
14:00:38 <openstack> Meeting started Wed Jan 18 14:00:37 2017 UTC and is due to finish in 60 minutes.  The chair is devkulkarni. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:39 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:41 <openstack> The meeting name has been set to 'solum_team_meeting'
14:01:22 <zhurong> devkulkarni hi
14:01:26 <devkulkarni> hi zhurong
14:01:42 <devkulkarni> lets wait for a minute to see if avnish or caowei join us as well
14:01:54 <devkulkarni> Ablu informed me that he won't be able to join today
14:02:14 <Ablu> Hi, atm I am still there. But I need to leave any second
14:02:23 <devkulkarni> zhurong: in the mean time you can take a look at the agenda
14:02:25 <Ablu> But I have nothing to contribute I fear
14:02:29 <devkulkarni> https://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2017-01-18_1400_UTC
14:02:33 <devkulkarni> Ablu: ack
14:02:51 <devkulkarni> good to have you chime in as that way your presence/participation gets recorded in the meeting logs
14:03:02 <devkulkarni> Ablu: you also can browse through the agenda
14:03:17 <Ablu> I do atm :P
14:04:16 <devkulkarni> alright, lets begin
14:04:24 <devkulkarni> #topic Announcements
14:04:34 <devkulkarni> devkulkarni to attend Atlanta PTG - February 20 - February 22
14:04:48 <devkulkarni> I will be attending PTG
14:04:57 <zhurong> cool
14:05:07 <devkulkarni> I remember we had started an etherpad for the PTG
14:05:34 <devkulkarni> if any of you have it handy somewhere (bookmarked) then can you share that
14:05:47 <devkulkarni> if not, I will go through the logs and find it out later
14:06:10 <devkulkarni> we should keep on adding/updating that etherpad about things that we want to accomplish at PTG
14:06:49 <devkulkarni> my main goal is going to be to work with the release team to understand various goals for Pike
14:07:00 <devkulkarni> and figure out what would it take for us to achieve those
14:07:46 <devkulkarni> apart from that, probably touch base with magnum and/or zun team to understand what their next priorities are so that we can figure out how that may affect our roadmap
14:08:26 <devkulkarni> zhurong, Ablu: any other points that you think we should consider to achieve at the PTG?
14:08:34 <zhurong> agree
14:09:01 <zhurong> np at this moment
14:09:06 <devkulkarni> ok
14:09:07 <Ablu> sorry. I do not really think I can contribute to that. I do not know all the other targets
14:09:12 <Ablu> i mean from open stack in general
14:09:19 <devkulkarni> we still have time till the PTG
14:09:23 <devkulkarni> Ablu: sure
14:09:42 <devkulkarni> are there any other announcements?
14:10:36 <zhurong> np
14:10:45 <devkulkarni> alright. lets move to discussion items
14:10:50 <devkulkarni> #topic Discussion
14:11:04 <devkulkarni> 1) PTL Elections  Nominations: Jan 18 - Jan 29 https://governance.openstack.org/election/
14:11:25 <devkulkarni> PTL nomination period is about to open in few hours
14:12:51 <zhurong> you should be the right man :)
14:13:24 <devkulkarni> I plan to submit nomination for upcoming cycle to keep the continuity. But if any of you interested in taking up this role in the future, lets work on it in this cycle so that for the next one you would be ready to take it up
14:13:28 <devkulkarni> zhurong: :)
14:15:30 <devkulkarni> zhurong: just let me know if you are ever interested in the role. would be happy to help you to get towards it
14:15:31 <zhurong> devkulkarni did you submit topic to boston summit?
14:15:54 <Ablu> I need to leave now... Have a nice day :)
14:16:10 <devkulkarni> zhurong: I had it on my list to things to do, but have not submitted it. Is the deadline for submission over?
14:16:35 <devkulkarni> Ablu: see you
14:16:43 <zhurong> I think next cycle I can not do it, I should learn more to let myself to fit with the role.
14:17:13 <zhurong> 12AM PST (0800 UTC), FEBRUARY 6, 2017!
14:17:38 <devkulkarni> zhurong: I can understand.
14:17:53 <devkulkarni> cool, thanks for sharing the date
14:18:07 <devkulkarni> lets work on it in next couple of weeks
14:18:16 <zhurong> hope for next cycle I can take over the role. :D
14:18:29 <devkulkarni> +1 :)
14:18:35 <devkulkarni> definitely
14:18:57 <devkulkarni> I would be more than happy to help you getting ready for the role in the Pike cycle
14:19:12 <devkulkarni> then in the following cycle you can take over the role
14:19:39 <zhurong> devkulkarni thx
14:20:02 <devkulkarni> great
14:20:29 <devkulkarni> so the next discussion topic is the ocata release
14:21:05 <devkulkarni> 2) Ocata release deadline Feb 16:  https://etherpad.openstack.org/p/solum-release-actions
14:22:04 <devkulkarni> zhu, so one of the things that needs to be done in the PTL role is to track emails about releases and then work with the release team to cut a release
14:23:04 <devkulkarni> on the etherpad above I have added link to the relevant email which states the deadline for project like ours that follow release-with-intermediary release model
14:23:12 <devkulkarni> the deadline is Feb 16
14:23:34 <devkulkarni> do you want to take a shot at working on this release this time?
14:24:14 <zhurong> sure, I can do this
14:24:23 <devkulkarni> awesome!
14:25:17 <devkulkarni> I can help you if there are any blockers
14:26:28 <devkulkarni> zhurong: I have added you to the solum-release group https://review.openstack.org/#/admin/groups/231,members
14:26:34 <zhurong> that's cool, with your help I think I can do it well :D
14:26:42 <devkulkarni> :)
14:27:39 <devkulkarni> on our wiki, there is a section "OpenStack related things"
14:27:40 <devkulkarni> https://wiki.openstack.org/wiki/Solum
14:27:51 <devkulkarni> under that there is a subsection 'Cutting a release'
14:28:08 <devkulkarni> essentially, you need to follow the steps listed there
14:29:06 <zhurong> sure, I will
14:29:19 <devkulkarni> there might have been recent changes to the process. you can reach out to folks on openstack-release channel to understand the latest requirements
14:29:31 <devkulkarni> but it should be straightforward
14:30:08 <zhurong> cool, If I have questions, I will ping you. :D
14:30:17 <devkulkarni> perfect. was about to say exactly that :)
14:31:20 <devkulkarni> ok, lets move to other topics.. I have three listed in the agenda -- Pike goal (python 3 support), python 3.5 for dsvm jobs, and replacing nova-docker with zun.. which one you want to talk about first?
14:31:45 <zhurong> python 3.5 for dsvm jobs this had done
14:32:07 <zhurong> and I tried add enable zun in the jobs
14:32:19 <zhurong> in python 3.5 for dsvm jobs
14:32:39 <devkulkarni> listening..
14:33:20 <zhurong> something wrong in install python-zunclient
14:33:49 <devkulkarni> have you pinged zun team about it?
14:33:56 <zhurong> I don't sure wether this just happen in py3.5
14:34:41 <zhurong> I asked in there IRC channel, but they haven't seen the error
14:35:01 <devkulkarni> I see. do you have stack trace of the error?
14:35:34 <devkulkarni> we can document that in a bug report for solum
14:35:35 <zhurong> python-zunclient do not have a release version, so just install from git
14:35:52 <zhurong> http://logs.openstack.org/24/416224/14/check/gate-solum-devstack-dsvm-py35-ubuntu-xenial-nv/3cd6c4c/logs/devstacklog.txt.gz#_2017-01-17_08_48_53_093
14:36:40 <zhurong> In my devstack env, using py2.7, that can install successful
14:37:27 <devkulkarni> did you share that with the zun team? what did they say?
14:37:47 <zhurong> they haven't seen this error
14:37:57 <zhurong> maybe they just using py2.7
14:38:03 <devkulkarni> even in python3.5?
14:38:12 <devkulkarni> probably you are right
14:38:34 <zhurong> but we py3.5 dsvm job is red
14:38:54 <devkulkarni> so imo there are two different things.. one is for us to move to using zun and second is to have py3.5 dsvm non-voting job
14:39:29 <devkulkarni> if with py27 zun will work then we should not worry about py3.5 dsvm job being red
14:39:38 <devkulkarni> because we can document the issue
14:39:49 <zhurong> I want to add enable zun to py27 job
14:39:59 <devkulkarni> and say that our ability to satisfy the goal would depend on zun working with py3.5
14:40:13 <zhurong> but I not sure this will be green, that's will cause block the gate
14:40:14 <devkulkarni> yes, that's what I am thinking too
14:40:49 <devkulkarni> we should enable zun with py2.7, which should be our main voting dsvm job (xenial)
14:41:07 <devkulkarni> we should add another non-voting dsvm job for python 3.5
14:41:13 <devkulkarni> and let that be red
14:41:32 <zhurong> non-voting dsvm job for python 3.5 this is already done
14:42:01 <devkulkarni> you are right http://logs.openstack.org/24/416224/14/check/gate-solum-devstack-dsvm-py35-ubuntu-xenial-nv/3cd6c4c/
14:42:27 <devkulkarni> in that case, lets enable zun in our voting dsvm job (keeping it python 2.7)
14:42:47 <devkulkarni> see the main thing we want to have is a replacement for nova-docker in place
14:42:55 <devkulkarni> with zun we will be able to do that
14:43:10 <devkulkarni> having a voting py3.5 dsvm job is another thing
14:43:54 <zhurong> yep, voting py3.5 dsvm job is not in a hurry
14:43:56 <devkulkarni> and our ability to achieve that goal will depend on how quickly zun team will ensure python3.5 support
14:44:01 <devkulkarni> yep
14:44:23 <devkulkarni> but having a replacement for nova-docker is something that we need to do sooner than later
14:45:04 <devkulkarni> so if you testing with using zun is working, I would say please go ahead and enable zun in our gate jobs
14:45:21 <devkulkarni> and also in plugin.sh, local.conf, etc.
14:45:43 <devkulkarni> please also add a section to the solum wiki
14:46:18 <devkulkarni> you can add a new section to https://wiki.openstack.org/wiki/Solum/solum-development-setup
14:46:39 <zhurong> sure, I submit enable zun in py27 job right now, If failed we should fix this
14:47:04 <zhurong> I will add after test successfully
14:47:11 <devkulkarni> makes sense
14:47:40 <devkulkarni> btw, you were able to test end-to-end using zun, right? i.e., creating a languagepack, creating and deploying an app, checking logs, etc.?
14:48:06 <devkulkarni> my devstack setup is currently broken so I am not in a position to test it end-to-end right now
14:49:20 <zhurong> I will finish the test in few days
14:49:26 <devkulkarni> sounds good
14:49:53 <devkulkarni> we should try to get the zun setup working before the PTG
14:50:34 <zhurong> If the add enable zun to py2.7 job, and the gate is green, I think it can work well
14:51:35 <devkulkarni> it will be a big achievement for us as currently because of our dependency on nova-docker, we have had to peg our devstack setup for specific commits of nova and neutron. all of that will go away. we will be able to work with their stable branches
14:51:54 <devkulkarni> zhurong: just to confirm, you do have a setup where you are able to test end-to-end, right?
14:52:00 <zhurong> yep, definitely
14:52:08 <devkulkarni> perfect
14:52:31 <devkulkarni> one of these days I will work on my end-to-end setup as well
14:52:43 <devkulkarni> will ping you in case I run into any issues
14:53:09 <devkulkarni> cool,
14:53:30 <devkulkarni> one last topic is that of the Pike goal regarding Python 3 support
14:54:04 <devkulkarni> this is the etherpad where we are collecting the artifacts related to this goal: https://etherpad.openstack.org/p/solum-python35-goal
14:54:57 <devkulkarni> what we should do sometime is to go through each our our repositories and one by one check if we satisfy  all the requirements related to the goal
14:55:02 <zhurong> seems all done
14:55:09 <devkulkarni> I think we are pretty close
14:55:21 <devkulkarni> yes, I also think we are done
14:56:08 <devkulkarni> but it will be good if we just tabulate against each requirement, how we are satisfying it (either list the patch which was submitted, or where in our code the requirement is already getting satisfied)
14:56:36 <devkulkarni> such a table would be required when we submit a patch to claim that we have satisfied the goal
14:56:55 <devkulkarni> again, if we can achieve this before the PTG that would be super
14:57:28 <devkulkarni> cool, we are almost at the end of our meeting time
14:57:41 <devkulkarni> anything else that we should discuss?
14:58:14 <zhurong> we can discuss in the channel
14:58:48 <devkulkarni> sure
14:58:54 <devkulkarni> lets continue in the channel then
14:59:00 <devkulkarni> I will end the meeting now
14:59:20 <devkulkarni> thanks zhurong Ablu for joining today. see you next week
14:59:24 <devkulkarni> #endmeeting