21:00:04 <devkulkarni> #startmeeting Solum Team Meeting
21:00:05 <openstack> Meeting started Tue Sep 29 21:00:04 2015 UTC and is due to finish in 60 minutes.  The chair is devkulkarni. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:00:08 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:00:13 <openstack> The meeting name has been set to 'solum_team_meeting'
21:00:13 <devkulkarni> #topic Roll Call
21:00:16 <devkulkarni> Devdatta Kulkarni
21:00:23 <datsun180b> Ed Cranford
21:01:26 <devkulkarni> #link https://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2015-09-29_2100_UTC Our Agneda
21:01:37 <devkulkarni> looks like its just you and me today datsun180b
21:01:51 <devkulkarni> hopefully others are trickling in
21:02:00 <datsun180b> i don't guess they thought it had already moved?
21:02:17 <devkulkarni> no, I don't think so
21:02:26 <devkulkarni> james_li had asked me this morning about it
21:02:42 <devkulkarni> and I had mentioned to him that today we are still at the original time
21:02:45 <james_li> james li
21:03:08 <devkulkarni> hi james_li
21:03:19 <james_li> Hi devkulkarni
21:03:35 <devkulkarni> good that two cores are here :)
21:03:43 <devkulkarni> I need to get few patches in
21:03:53 <devkulkarni> welcome swati_9
21:03:55 <datsun180b> looking at trigger changes now
21:04:12 <devkulkarni> datsun180b, james_li: swati_9 is new member of our team
21:04:14 <swati_9> devkulkarni: hi, thanks
21:04:25 <datsun180b> glad to have you swati_9
21:04:30 <devkulkarni> swati_9: would you like to introduce yourself to datsun180b and james_li
21:04:39 <swati_9> datsun180b: thanks :)
21:04:45 <swati_9> yes, sure
21:05:07 <swati_9> Hey everyone, my name is Swati
21:05:24 <swati_9> I am a 3rd year student studying CS
21:05:56 <devkulkarni> thanks for the introduction swati_9
21:06:07 <swati_9> devkulkarni: :)
21:06:18 <devkulkarni> datsun180b: swati_9 was running into issues with vagrant setup
21:06:38 <devkulkarni> may be you have some insight.. we can discuss about it during open discussion
21:06:43 <datsun180b> sounds good
21:06:48 <devkulkarni> let me proceed with today's agenda
21:07:07 <devkulkarni> so the first item today is to change our meeting time.
21:07:09 <devkulkarni> Changing meeting time to 1700 UTC
21:07:22 <devkulkarni> #link http://lists.openstack.org/pipermail/openstack-dev/2015-September/075611.html
21:07:32 <adrian_otto> o/
21:07:38 <devkulkarni> hi adrian_otto
21:07:46 <devkulkarni> we just got started
21:07:50 <adrian_otto> sorry I am late
21:08:03 <adrian_otto> glad you got started
21:08:18 <devkulkarni> adrian_otto: we have a new team member — swati_9
21:08:32 <james_li> Hi swati_9, welcome
21:08:48 <devkulkarni> ok, so the first item on agenda is changing meeting time
21:08:54 <swati_9> james_li: hi :)
21:09:18 <devkulkarni> please vote on the review: https://review.openstack.org/#/c/228441/
21:09:48 <devkulkarni> this was based on our discussion from last week's meeting
21:10:39 <datsun180b> Of note is the change in IRC channel, too, to #openstack-meeting-3 instead of -alt as it is now
21:10:49 <devkulkarni> yes, that is correct datsun180b
21:11:05 <devkulkarni> this channel is busy at that hour. murano has their team meeting
21:11:25 <devkulkarni> I am proposing that we move to new time starting next week's meeting
21:11:53 <devkulkarni> alright
21:12:23 <devkulkarni> I will remove WIP once most of the active members have voted (or by thursday) whichever is latest
21:12:43 <devkulkarni> hopefully no other team chooses that time slot and channel before our changes get merged!
21:13:10 <devkulkarni> next item on agenda is
21:13:16 <devkulkarni> Glance bug affecting our Devstack environment
21:13:24 <devkulkarni> #link http://lists.openstack.org/pipermail/openstack-dev/2015-September/075409.html
21:13:50 <devkulkarni> so last week I started noticing that image uploads to glance (languagepacks) started failing
21:13:56 <devkulkarni> in our devstack environment
21:14:20 <devkulkarni> turns out there was a bug in glance client, which has been fixed now
21:14:37 <devkulkarni> just wanted to bring it everyone's attention
21:15:32 <james_li> looks like the bug was fixed and merged
21:15:47 <devkulkarni> till that bug fix is ported to liberty, we might have to set glance client repo and branch when starting up vagrant
21:16:04 <devkulkarni> james_li: yes, but don't think it has been back-ported to liberty yet.
21:16:11 <devkulkarni> they had two patches
21:16:11 <james_li> ok
21:16:33 <devkulkarni> I haven't restarted my vagrant vm, so haven't tried setting the glance client repo and branch
21:17:01 <devkulkarni> but, there variables inside stackrc for glance client which we need to override when we start the vagrant v
21:17:05 <devkulkarni> vagrant vm
21:17:32 <devkulkarni> probably similar to the way we use to override novadocker
21:17:44 <devkulkarni> right, datsun180b, james_li?
21:18:04 <datsun180b> spinning plates, catching up
21:18:12 <devkulkarni> datsun180b: sure
21:19:50 <devkulkarni> so that was just a fyi
21:20:06 <datsun180b> we've pinned before
21:20:09 <devkulkarni> if you run into issues related to glance upload, that will be the reason
21:20:13 <devkulkarni> datsun180b: yes
21:20:24 <datsun180b> and we still have the mechanism to pin via environment variables
21:20:51 <devkulkarni> datsun180b: yep, thats what I am thinking we need to do
21:21:03 <devkulkarni> set the environment variables before doing 'vagrant up'
21:21:54 <devkulkarni> ok, so just be aware of this bug. that is all on that topic
21:22:05 <devkulkarni> let me move to the next one
21:22:09 <devkulkarni> Porting trigger resource to apps
21:22:19 <devkulkarni> #link https://review.openstack.org/#/c/224918/
21:22:27 <devkulkarni> #link https://review.openstack.org/#/c/226081/1
21:22:42 <devkulkarni> datsun180b: thanks for +2 on the API patch
21:22:52 <devkulkarni> james_li: I have addressed your comments
21:23:08 <datsun180b> looked good to me, that's what +2 is for
21:23:16 <devkulkarni> +1 datsun180b :)
21:23:29 <james_li> I can look
21:23:39 <devkulkarni> these have been around for more than a week now.. would like to get them merged soon
21:23:44 <devkulkarni> thanks james_li
21:23:57 <datsun180b> no arguments from me
21:24:18 <devkulkarni> btw, datsun180b probably you missed an intermediate patch which got merged couple days back
21:24:39 <devkulkarni> it was about adding uniqueness constraint to the workflow object model
21:24:53 <datsun180b> i saw mention of it
21:25:03 <devkulkarni> datsun180b: yeah
21:25:17 <adrian_otto> I like these too
21:25:23 <adrian_otto> I am going to approve them for merge now
21:25:33 <devkulkarni> adrian_otto: awesome!!
21:25:52 <devkulkarni> *feeling happy*
21:25:58 <devkulkarni> :)
21:26:10 <adrian_otto> done
21:26:17 <devkulkarni> thanks adrian_otto
21:26:17 <datsun180b> well that was easy
21:26:48 <devkulkarni> james_li: if you had any other comments, would be happy to address them in a follow up patch
21:27:11 <devkulkarni> ok, moving to next item
21:27:32 <devkulkarni> which, actually is not on the agenda as I just realized I had forgotten about it
21:27:51 <devkulkarni> it is about several patches submitted by stannier for python3
21:28:00 <james_li> saw them
21:28:03 <devkulkarni> #link https://review.openstack.org/#/q/project:openstack/solum+status:open,n,z
21:28:21 <devkulkarni> james_li, datsun180b: I think you guys will be perfect to weigh in on them
21:28:40 <devkulkarni> I had already requested randallburt to look through them
21:28:56 <devkulkarni> he has given his +1 for a few and a -1 for one
21:29:06 <devkulkarni> there are few he has not looked at
21:29:28 <james_li> should we expect to see our py34 gate pass with his patches?
21:29:29 <devkulkarni> james_li: did you get a chance to look at any of them?
21:29:43 <devkulkarni> jame_li: good question
21:29:53 <devkulkarni> the patches seem to be failing on py34
21:29:58 <devkulkarni> #link https://review.openstack.org/#/c/227757/
21:30:05 <james_li> but I am still seeing failures
21:30:13 <devkulkarni> so just these changes may not be enough
21:30:22 <devkulkarni> james_li: yes
21:30:59 <devkulkarni> I can check with Victor to understand what would be required to make it so that py34 gate will start passing
21:32:02 <datsun180b> I think we can work it out, I imagine the gate will only pass when all of the changes are in
21:32:07 <devkulkarni> james_li: but even though the gate check is still not passing, the current set of changes might be in line to where eventually we can have a green gate
21:32:18 <devkulkarni> datsun180b: oh
21:32:25 <devkulkarni> datsun180b: may be that is the case
21:33:14 <devkulkarni> in any case, please review those patches whenever you get a chance
21:33:31 <devkulkarni> seems like good contribution to me
21:33:39 <datsun180b> maybe we can check the logs to make sure that each change in order at least decreases the number of problems the py34 gate has
21:34:06 <devkulkarni> are the changes interdependent?
21:34:21 <datsun180b> so it would seem, they're all fairly well scoped
21:35:16 <devkulkarni> datsun180b: that is a good idea .. to check the logs of the gate failure
21:35:34 <datsun180b> I mean, it's our job, right
21:35:56 <adrian_otto> http://logs.openstack.org/57/227757/2/check/gate-solum-python34/b9cda5b/console.html#_2015-09-28_08_20_30_772
21:36:13 <adrian_otto> "ImportError: No module named 'urlparse'"
21:36:45 <datsun180b> One of Victor's changes moved our use of urlparse to a six urllib borrow, IIRC
21:36:53 <datsun180b> or, it would, if it merged
21:37:14 <devkulkarni> so for that patch, we should not see above error
21:38:02 <adrian_otto> so we can merge the other one and then order a recheck on this one to prove it?
21:38:08 <devkulkarni> #link http://logs.openstack.org/98/227398/1/check/gate-solum-python34/fd362a6/console.html.gz
21:38:21 <devkulkarni> adrian_otto: yes, that makes sense
21:38:28 <adrian_otto> https://review.openstack.org/227398
21:39:00 <adrian_otto> ok, I approve that one
21:39:05 <adrian_otto> +d
21:39:21 <devkulkarni> ok..do we have to wait till it merges?
21:39:33 <devkulkarni> or could we retrigger the other one now?
21:39:45 <adrian_otto> only if you want to know for sure if that clears the gate error
21:39:49 <datsun180b> judging from how long the solumclient review took to merge, I wouldn't imagine it'll take that long
21:40:15 <adrian_otto> should know in like 5 mins
21:40:29 <devkulkarni> ok.. we can keep an eye out on solum irc channel.. we will get a notification there
21:41:21 <devkulkarni> so the next two items on the agenda are copied over from last time
21:41:30 <devkulkarni> - Moving logs resource from assembly to workflow
21:42:00 <devkulkarni> this is probably the last thing we need to complete before calling old api to new api migration done
21:42:21 <devkulkarni> vijendar is going to be looking at this
21:43:10 <devkulkarni> I have created two bugs (one for api and another for cli) and assigned them to vijendar
21:43:24 <devkulkarni> will check with him if he needs any help
21:44:19 <devkulkarni> next item is some new bugs for which I am looking for volunteers
21:44:29 <devkulkarni> this is the same list that I had last time
21:45:28 <devkulkarni> swati_9: once you get your devstack + solum environment working, we can look at if you might be able to pick up one of these
21:45:52 <devkulkarni> I think #link https://bugs.launchpad.net/python-solumclient/+bug/1498209 might be a good one
21:45:52 <openstack> Launchpad bug 1498209 in python-solumclient "created-at-in-solum-app-list" [Medium,New]
21:46:46 <devkulkarni> ok, so that is all I had for reviews/discussion topic
21:46:52 <devkulkarni> moving to open discussion
21:47:07 <devkulkarni> #topic Open Discussion
21:47:24 <devkulkarni> I have two items for this today.
21:47:37 <devkulkarni> First one is: Figuring out details of the Solum Fishbowl session at Tokyo (when, where, what)
21:47:53 <devkulkarni> there was this email some time back #link http://lists.openstack.org/pipermail/openstack-dev/2015-September/073654.html
21:48:25 <devkulkarni> yesterday (or day before), an etherpad was shared as well #link https://etherpad.openstack.org/p/infra-mitaka-summit-planning
21:49:10 <devkulkarni> so looks like the planning of various sessions and workdays is now going to start soon
21:49:33 <devkulkarni> hopefully we will hear about when is solum's fb session
21:50:08 <devkulkarni> will let everyone know as soon as I find out
21:50:13 <swati_9> devkulkarni: yes, definitely, sounds good
21:50:23 <devkulkarni> swati_9: cool
21:52:00 <devkulkarni> the second topic was related to recent email chain on magnum
21:52:39 <devkulkarni> adrian_otto: I am was following the discussion on http://lists.openstack.org/pipermail/openstack-dev/2015-September/075763.html
21:53:19 <devkulkarni> and was intrigued to read your response that some of the current abstractions, like replication controller, pods, services, would not have been in magnum had it started now
21:54:05 <devkulkarni> my interest is to know — then should solum not be considering using these abstractions when interfacing with magnum?
21:54:32 <adrian_otto> good question
21:54:38 <adrian_otto> my advice is to simply use bay
21:54:47 <adrian_otto> and to interface with the bay using its native API
21:55:15 <adrian_otto> so if you plan to use a kubernetes bay, then create your resources usingthe ku8 v1 api
21:55:23 <adrian_otto> s/ku8/k8s/
21:55:43 <devkulkarni> adrian_otto: I see
21:55:46 <adrian_otto> if you are creating swarm bays (probably makes more sense for solum) then just use the docker API
21:56:08 <devkulkarni> oh okay
21:56:22 <adrian_otto> the advantagethere is if you want to start using new features in Docker, you can get them sooner than waiting for magnum to implement them
21:56:31 <devkulkarni> btw, for using swarm bays, each bay node will have a docker registry on it, right?
21:56:43 <devkulkarni> sure, makes sense
21:57:02 <devkulkarni> I saw your comment on that bp
21:57:14 <devkulkarni> and also saw a patch which got merged
21:57:43 <adrian_otto> yes, so you will be able to use localhost as your registry endpoint
21:57:52 <adrian_otto> that code may still be in review, but it's close
21:58:15 <devkulkarni> ok.. I will be starting with investigating magnum integration next
21:58:29 <devkulkarni> now that the triggers work is done
21:58:31 <adrian_otto> for example, you might want: https://review.openstack.org/225400
21:58:57 <devkulkarni> oh okay. thanks for sharing
21:59:11 <devkulkarni> I believe the initial patch which adds a registry was merged
21:59:59 <devkulkarni> may be not
22:00:03 <adrian_otto> https://review.openstack.org/#/q/status:merged+project:openstack/magnum+branch:master+topic:bp/registryv2-in-master,n,z
22:00:05 <devkulkarni> but this is the bp https://blueprints.launchpad.net/magnum/+spec/registryv2-in-master
22:00:08 <adrian_otto> those are the two that merged
22:00:17 <devkulkarni> ok cool
22:00:20 <devkulkarni> thanks adrian_otto
22:00:27 <devkulkarni> its top of the hour
22:00:33 <devkulkarni> will end the meeting now
22:00:37 <adrian_otto> tx!!
22:00:44 <devkulkarni> thanks everyone for joining today
22:00:48 <devkulkarni> #endmeeting