21:00:09 <devkulkarni> #startmeeting Solum Team Meeting
21:00:10 <openstack> Meeting started Tue Sep 22 21:00:09 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:12 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:00:15 <openstack> The meeting name has been set to 'solum_team_meeting'
21:00:26 <devkulkarni> #topic Roll Call
21:00:28 <devkulkarni> Devdatta Kulkarni
21:00:28 <james_li> james li
21:00:32 <muralia> o/
21:00:34 <datsun180b> ed cranford
21:00:46 <devkulkarni> our agenda for today: #link https://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2015-09-22_2100_UTC
21:00:52 <devkulkarni> hi james_li, muralia, datsun180b
21:01:00 <james_li> Hi devkulkarni
21:01:06 <muralia> hey
21:01:09 <adrian_otto> Adrian Otto
21:01:13 <devkulkarni> hi adrian_otto
21:01:17 <adrian_otto> hello
21:01:22 <devkulkarni> good to see you all :)
21:01:44 <devkulkarni> #topic Announcements
21:01:55 <devkulkarni> I don't have any prepared announcement
21:02:10 <devkulkarni> Anyone from the team would like to has anything to share?
21:02:28 <adrian_otto> I will be working to transition PTL duties to Devdatta for the M release cycle.
21:02:49 <muralia> nice
21:02:55 <adrian_otto> I asked him to chair this meeting as part of that effort. He has already been setting the agendas, so this makes sense to start now.
21:02:57 <devkulkarni> adrian_otto: I will reach out to you to understand what all things need to be addressed
21:03:11 <adrian_otto> devkulkarni: cool
21:03:21 <devkulkarni> adrian_otto: the setup that we have in place is great
21:03:29 <devkulkarni> I will mostly follow the template that we have
21:04:01 <devkulkarni> ok, moving on to the next topic
21:04:04 <devkulkarni> #topic Review Action Items
21:04:19 <devkulkarni> we did not have any action items from last time (or a few meetings before that)
21:04:55 <devkulkarni> #topic Blueprint/Bug Review and Discussion
21:05:09 <devkulkarni> (devkulkarni): Porting trigger resource to apps
21:05:14 <devkulkarni> so an update on this..
21:05:33 <devkulkarni> I have now started porting/migrating our trigger functionality to apps
21:05:47 <devkulkarni> looking for reviews on:
21:05:50 <james_li> that makes sense
21:05:59 <devkulkarni> #link https://review.openstack.org/#/c/224918/
21:06:09 <devkulkarni> and #link https://review.openstack.org/#/c/226081/1
21:06:21 <devkulkarni> first one is the api patch (actually a series of patches)
21:06:25 <devkulkarni> second one is the cli patch
21:06:47 <devkulkarni> whenever you get a chance, please take a look at both
21:07:13 <devkulkarni> if possible, I am looking to getting these merged in next couple of days
21:07:19 <adrian_otto> what is this?
21:07:19 <adrian_otto> https://review.openstack.org/#/c/224918/3/functionaltests/api/common/__init__.py
21:07:28 <devkulkarni> oh
21:07:30 <devkulkarni> I removed it
21:07:33 <devkulkarni> in the following patch
21:07:41 <devkulkarni> check patch set 3
21:08:06 <devkulkarni> oh may be not
21:08:07 <adrian_otto> that is in patchset 3
21:08:08 <devkulkarni> I will remove it
21:08:12 <adrian_otto> ok
21:08:35 <devkulkarni> it got created by Pycharm
21:09:13 <adrian_otto> sorry, I have to leave early (call from school nurse's office. I have to take one of my children home)
21:09:29 <devkulkarni> sounds good adrian_otto
21:09:34 <devkulkarni> will see you later
21:09:46 <devkulkarni> the second one for review/discussion is this:
21:09:49 <devkulkarni> (devkulkarni): Moving logs resource from assembly to workflow
21:09:57 <devkulkarni> #link https://bugs.launchpad.net/solum/+bug/1498147
21:09:58 <openstack> Launchpad bug 1498147 in Solum "add-logs-to-workflow-resource" [High,New] - Assigned to Vijendar Komalla (vijendar-komalla)
21:10:04 <devkulkarni> #link https://bugs.launchpad.net/python-solumclient/+bug/1498181
21:10:05 <openstack> Launchpad bug 1498181 in python-solumclient "connect-app-logs-to-use-workflow-instead-of-assembly" [High,New] - Assigned to Vijendar Komalla (vijendar-komalla)
21:10:26 <devkulkarni> datsun180b, james_li: could you take a moment to look at those bug descriptions
21:10:33 <devkulkarni> vijendar: ping
21:10:43 <vijendar> devkulkarni:  I am going to start working on that
21:10:46 <devkulkarni> vijendar has volunteered to take those bugs
21:10:54 <devkulkarni> that will be awesome vijendar
21:10:56 <datsun180b> Likely due to the the more strict cli parsing I imagie
21:11:07 <datsun180b> oh wrong bug
21:11:31 <devkulkarni> datsun180b: oh yeah
21:11:35 <devkulkarni> I will come to those in a bit
21:11:48 <devkulkarni> right now discussing logs related bugs
21:12:00 <datsun180b> sorry, still getting used to different copypaste shortcuts
21:12:12 <devkulkarni> datsun180b: not a mac?
21:12:49 <datsun180b> not anymore, no
21:13:51 <devkulkarni> datsun180b: does the bug description for the logs api make sense?
21:15:16 <datsun180b> sure, makes sense
21:15:41 <devkulkarni> cool.. datsun180b one of the things that we need to keep in mind is the id vs uuid change
21:15:52 <datsun180b> the userlog table is weakly bound to assemblies anyway, changing the column name should be the hardest part of that change
21:16:03 <devkulkarni> the loggers are written with the assumption that the 'resource' has a uuid
21:16:06 <devkulkarni> datsun180b: sure
21:17:07 <devkulkarni> james_li, muralia: what do you guys think? does the bug description captures enough details for vijendar to tackle it?
21:17:17 <james_li> link?
21:17:29 <devkulkarni> james_li: https://bugs.launchpad.net/solum/+bug/1498147
21:17:31 <openstack> Launchpad bug 1498147 in Solum "add-logs-to-workflow-resource" [High,New] - Assigned to Vijendar Komalla (vijendar-komalla)
21:18:19 <muralia> yes, i think there enough detail
21:18:31 <devkulkarni> muralia: cool
21:18:46 <james_li> looks ok
21:18:51 <devkulkarni> awesome
21:19:08 <vijendar> devkulkarni muralia james_li  will ping you guys if I need any help
21:19:14 <devkulkarni> vijendar: +1
21:19:16 <muralia> sure
21:19:32 <devkulkarni> ok, moving on to the next one
21:19:47 <devkulkarni> (devkulkarni): Looking for volunteers for some bugs
21:20:15 <devkulkarni> in last couple of days I was doing bugs cleanup
21:20:20 <devkulkarni> in our launchpad
21:20:38 <devkulkarni> I have also added few new bugs which I encountered recently
21:20:48 <devkulkarni> I am thinking that going forward
21:21:04 <devkulkarni> I will make it a point to bring these bugs in our meetings
21:21:16 <devkulkarni> to discuss and design solutions for
21:21:27 <devkulkarni> today I have these three:
21:21:36 <devkulkarni> #link https://bugs.launchpad.net/python-solumclient/+bug/1498209
21:21:38 <openstack> Launchpad bug 1498209 in python-solumclient "created-at-in-solum-app-list" [Medium,New]
21:21:47 <devkulkarni> #link https://bugs.launchpad.net/python-solumclient/+bug/1424836
21:21:48 <openstack> Launchpad bug 1424836 in python-solumclient "Typo in language pack creation" [Undecided,New]
21:21:57 <devkulkarni> #link https://bugs.launchpad.net/solum/+bug/1498056
21:21:57 <openstack> Launchpad bug 1498056 in Solum "Fix oslo imports in solum-infra-guest-agent" [Low,New]
21:22:25 <james_li> we don't need solum-infra-guest-agent repo do we?
21:22:26 <devkulkarni> please check out the bugs
21:22:35 <devkulkarni> james_li: good question
21:22:47 <devkulkarni> so numergy folks had added it
21:22:58 <james_li> yeah and it is not complete
21:23:05 <devkulkarni> when we were thinking of creating a infra nodes for building dus
21:23:05 <devkulkarni> yes
21:23:14 <devkulkarni> the problem is, there is one patch on it which is failing
21:23:35 <devkulkarni> it was brought to our attention by someone from the infra team
21:23:52 <devkulkarni> i think in the context of creating liberty release
21:24:07 <devkulkarni> so the bug is just to fix the failing gate issue
21:24:21 <devkulkarni> I think datsun180b has identified it already on that patch
21:24:45 <james_li> if we fix it this time, will we see other failures later on?
21:25:01 <devkulkarni> james_li: most likely not
21:25:09 <devkulkarni> as this one time is for the oslo change
21:25:24 <devkulkarni> if nothing gets added to that repo then ideally it should not fail
21:25:29 <devkulkarni> but we never know
21:25:38 <devkulkarni> I understand your concern about maintaining it
21:25:43 <james_li> just don't want it to distract people
21:25:49 <devkulkarni> james_li: good point
21:26:20 <devkulkarni> I thought about it when we were migrating the repos from stackforge to openstack
21:26:52 <devkulkarni> at that time my thinking was, if in the future if we do decide to implement a build farm, then having this around might be good starting point
21:27:14 <devkulkarni> so this bug is not blocker for us
21:27:35 <devkulkarni> I don't think it was a blocker for the infra team either
21:27:40 <devkulkarni> it was just that
21:27:47 <james_li> if we find a good isolation approach we can just build on worker hosts just fine
21:28:14 <devkulkarni> james_li: agreed. we need to land your patches which will give us that isolation
21:28:50 <devkulkarni> james_li, datsun180b, muralia, vijendar: thoughts on other two bugs?
21:29:33 <james_li> think the solum client bugs make sense
21:30:45 <muralia> both seem straight forward
21:31:19 <devkulkarni> ok, if anyone of you have some b/w (which probably you don't), it would be awesome if you can take one of those
21:31:28 <datsun180b> i don't at present have an environment to work even straightforward client bugs
21:31:37 <devkulkarni> datsun180b: oh!
21:31:49 <devkulkarni> datsun180b: vagrant setup not working for you?
21:32:20 <datsun180b> it's a matter of having hardware on hand
21:32:52 <devkulkarni> datsun180b: hmm.. not enough memory I suppose on your machine
21:33:04 * adrian_otto back
21:33:07 <james_li> datsun180b: your cell phone is a hardware
21:33:07 <datsun180b> the only machine i have that could do it has 2 gigs of ram
21:33:16 <devkulkarni> adrian_otto: nice to see you back
21:34:03 <devkulkarni> datsun180b: I see. Yeah, that is not sufficient for our vagrant setup. although I have never tried it with less than 4 G
21:34:12 <devkulkarni> james_li: :D
21:34:22 <datsun180b> i used to give it 10 gigs
21:34:34 <devkulkarni> datsun180b: yes, that's what I do
21:35:45 <devkulkarni> datsun180b: no worries. if you get around to taking up one of those cli bugs that would be nice.
21:35:57 <devkulkarni> but I understand that you all are pretty busy
21:36:19 <devkulkarni> just want to see you all involved :)
21:36:37 <devkulkarni> ok, moving on to next topic
21:36:43 <devkulkarni> #topic Open Discussion
21:36:54 <devkulkarni> I have two for this. I am going to take the second one first.
21:37:01 <devkulkarni> (devkulkarni): Changing meeting time to Tuesday mornings
21:37:07 <devkulkarni> So let me give some background on this
21:37:24 <devkulkarni> Our meeting time conflicts with the cross-project meeting
21:37:37 <devkulkarni> which is happening right now in openstack-meeting channel
21:38:10 <devkulkarni> I would like to ocassionally attend that meeting to keep up with any cross-project discussions/decisions etc.
21:38:27 <devkulkarni> second is that, recently noorul seems to be back
21:38:36 <devkulkarni> he has been reviewing some of our recent patches
21:38:46 <james_li> he will sign on for those two client bugs :)
21:38:57 <devkulkarni> james_li: ha ha. yes. good point
21:39:03 <devkulkarni> I can check with him
21:39:11 <devkulkarni> so, going back
21:39:17 <james_li> I am +1 on changing our time
21:39:25 <muralia> im good with that too
21:39:34 <devkulkarni> cool
21:39:48 <devkulkarni> datsun180b, adrian_otto, vijendar: what do you guys think?
21:40:07 <datsun180b> I'm not categorically opposed, but I'm not certain what the new proposed time is
21:40:23 <devkulkarni> datsun180b: I don't know what are the open slots.
21:40:36 <devkulkarni> in fact, I need to figure out how to find open slots
21:40:49 <devkulkarni> datsun180b: I was hoping that we switch to morning times
21:41:00 <vijendar> devkulkarni: I am OK with morning time
21:41:01 <devkulkarni> to give folks in India, like noorul, an opportunity to participate
21:41:15 <devkulkarni> right now, its 2.30am in India
21:41:33 <devkulkarni> our earlier time of 11.00am would be 9.30pm in India
21:41:52 <devkulkarni> so some time on or before 11.00am should work for both sides
21:42:06 <devkulkarni> vijendar: cool
21:42:30 <adrian_otto> I have no objections as long as we don't select the same time as the Magnum team meeting
21:42:39 <devkulkarni> adrian_otto: yes, makes sense
21:42:43 <adrian_otto> avoid 1600 UTC
21:42:45 <datsun180b> tuesday mornings should be fine
21:42:45 <devkulkarni> I believe magnum meetings are at 11.00
21:42:55 <devkulkarni> on every alternate tuesdays, right?
21:43:07 <devkulkarni> datsun180b: cool
21:43:11 <muralia> yes
21:43:14 <devkulkarni> ok
21:43:19 <adrian_otto> yes, and we are currently discussing doing all of them at 1600 UTC instead of alternating
21:43:29 <devkulkarni> adrian_otto: oh okay. good to know
21:43:37 <devkulkarni> so 11.00am is not an option
21:43:48 <devkulkarni> may be 10.00am or noon
21:44:00 <adrian_otto> noon is better for me
21:44:11 <devkulkarni> which one will work for all of you?
21:44:18 <devkulkarni> adrian_otto: ok
21:44:24 <devkulkarni> sorry, I am referring to central times
21:44:34 <devkulkarni> so yeah, 10.00am is too early for you adrian_otto
21:44:49 <james_li> noon is fine with me
21:44:51 <muralia> why dont u start a doodle pool. we can vote
21:45:02 <devkulkarni> muralia: sure, I can do that
21:45:09 <muralia> noon austin time is good for me too
21:45:15 <devkulkarni> muralia: ok
21:45:33 <devkulkarni> vijendar, datsun180b: how does Tuesday noon sound to you?
21:46:05 <devkulkarni> adrian_otto: how to check if a particular time slot is available or not?
21:46:10 <datsun180b> keep in mind that Austin is in CDT (UTC-5), and will shift to CST (UCT-6) on the first of November
21:46:11 <devkulkarni> in a channel?
21:46:33 <devkulkarni> datsun180b: yes
21:47:00 <devkulkarni> datsun180b: so right now, our majority of contributors are in US time zones
21:47:01 <datsun180b> so it'll be noon tuesday for a few months, and then it'll move over an hour
21:47:14 <datsun180b> devkulkarni: but openstack works off zulu time
21:47:21 <devkulkarni> datsun180b: good point
21:47:37 <adrian_otto> that means the chosen time will appear to be one hour sooner
21:48:07 <adrian_otto> so 1600 UTC now is 11:00 am CDT, and will be 9:00 am CST after DST ends.
21:48:08 <devkulkarni> adrian_otto: so after November 1st, it will be 11.00am. (And magnum will be at 10.00am), right?
21:48:19 <adrian_otto> yes
21:48:35 <devkulkarni> ok. (always hard to keep those things straight in my head)
21:48:45 <adrian_otto> wait, What I wrote was not right
21:48:53 <datsun180b> yeah that's a two hour swing
21:48:54 <adrian_otto> try that again:
21:48:59 <adrian_otto> so 1600 UTC now is 11:00 am CDT, and will be 10:00 am CST after DST ends.
21:49:13 <devkulkarni> ok, that makes sense
21:49:30 <devkulkarni> so then I am proposing 1700 UTC for our meeting
21:49:47 <datsun180b> so noon or 11am central time
21:49:51 <devkulkarni> which will be noon CDT, and 11.00am CDT after DST ends
21:49:57 <datsun180b> that sounds dandy
21:49:59 <devkulkarni> +1 datsun180b
21:50:31 <devkulkarni> so in fact, noon will be only for few more meetings (if we do change it before DST ends)
21:50:45 <devkulkarni> ok
21:50:54 <vijendar> devkulkarni:  works for me
21:50:55 <devkulkarni> but all of this will depend on whether the channel is available at that time
21:50:59 <devkulkarni> vijendar: cool
21:51:17 <devkulkarni> adrian_otto: how to check if this channel is available at above times?
21:52:26 <datsun180b> alternately, we can create and petition for the annexation of #openstack-meeting-double-secret-clubhouse
21:52:52 <devkulkarni> datsun180b: :D
21:53:00 <adrian_otto> https://wiki.openstack.org/wiki/Meetings
21:53:20 <devkulkarni> adrian_otto: thanks
21:53:23 <devkulkarni> looking
21:53:50 <adrian_otto> http://git.openstack.org/cgit/openstack-infra/irc-meetings/tree/meetings
21:54:19 <devkulkarni> murano is at 1700 UTC
21:55:15 <devkulkarni> we could use different channel, or look for other time
21:55:28 <devkulkarni> let me do some research on what is available
21:55:39 <devkulkarni> will come back with a suggestion for our next meeting
21:56:07 <devkulkarni> we are just about at the end
21:56:18 <devkulkarni> I have one more topic for open discussion
21:56:34 <adrian_otto> and http://git.openstack.org/cgit/openstack-infra/irc-meetings/tree/meetings/solum-team-meeting.yaml needs the description to be updated to remove the mention of alternating meetings.
21:57:05 <devkulkarni> adrian_otto: oh okay
21:57:23 <devkulkarni> adrian_otto: I guess need to submit a patch. will do that
21:57:43 <devkulkarni> (devkulkarni): Figuring out details of the Solum Fishbowl session at Tokyo (when, where, what)
21:57:53 <devkulkarni> I don't have details of this yet
21:58:03 <devkulkarni> was hoping to join the cross-project meeting today to find this out
21:58:09 <devkulkarni> but could not do so
21:58:18 <devkulkarni> will try to find details about this by our next meeting
21:59:18 <devkulkarni> ok, we are in the last minute for today
21:59:38 <devkulkarni> thanks datsun180b, vijendar, muralia, james_li, adrian_otto for joining today
21:59:46 <muralia> o/
21:59:51 <devkulkarni> #endmeeting