14:00:05 <dkrol> #startmeeting trove
14:00:06 <openstack> Meeting started Wed Dec 12 14:00:05 2018 UTC and is due to finish in 60 minutes.  The chair is dkrol. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:07 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:09 <openstack> The meeting name has been set to 'trove'
14:00:19 <dkrol> Hello
14:00:35 <mpiwowarczy> hi all
14:00:39 <dkrol> Hello
14:00:44 <cezary_zukowski_> hi
14:00:51 <dkrol> How are you all?
14:01:44 <cezary_zukowski_> not bad, much work before christmas :)
14:01:50 <mpiwowarczy> dkrol: thanks, fine - i'm already on christmas holidays :)
14:01:55 <cezary_zukowski_> and you?
14:02:42 <dkrol_> Hi
14:03:00 <dkrol_> Can we start?
14:03:36 <mpiwowarczy> dkrol: fine by me
14:04:11 <dkrol_> I have some problems with connectivity :/
14:04:21 <dkrol_> #topic recent changes
14:04:50 <dkrol_> I would like to start with info about new changes and commit
14:05:11 <mpiwowarczy> yeah, there are not many
14:05:21 <dkrol_> I saw only a few commits in the last week and I was able to review most of them
14:06:20 <dkrol_> Do you still have time to work on trove during business hours?
14:06:55 <bzurkowski> Hello
14:06:58 <mpiwowarczy> in last time almost entirely
14:07:22 <mpiwowarczy> we have a very busy schedule for internal requirements
14:07:35 <mpiwowarczy> bzurkowski: hi
14:07:41 <cezary_zukowski_> yeah, true :(
14:07:55 <dkrol_> Hmmm... So do you mean you have time or not? :)
14:08:41 <bzurkowski> Sorry guys, I'm late... What is the context?
14:08:46 <mpiwowarczy> not for community work :)
14:08:55 <dkrol_> Ok,
14:09:28 <dkrol_> My question was do you have time to work on trove during business hours?
14:09:42 <bzurkowski> Mmm
14:10:08 <bzurkowski> Tough question
14:10:19 <dkrol_> And second question is - will it change in the next week's?
14:10:47 <dkrol_> Context is that there was not so many changes/commits in the last week
14:10:59 <bzurkowski> Yea, I am also very sad about it
14:11:14 <mpiwowarczy> dkrol: next week's? I don't think so
14:11:28 <bzurkowski> Next week will not be better than this one
14:11:45 <bzurkowski> I have a suggestion
14:11:48 <bzurkowski> Guys
14:12:13 <bzurkowski> There are only 5 of us at the moment
14:12:24 <dkrol_> Second week of January is Stein milestone 2
14:12:30 <bzurkowski> We all have very limited time for contribution
14:13:37 <bzurkowski> I cannot see much progress in working on multiple changes in parallel
14:13:40 <bzurkowski> Individually
14:13:52 <bzurkowski> Maybe we should decide on one change to focus on during the next week
14:14:00 <bzurkowski> And put all resources on delivering this change
14:14:26 <bzurkowski> Otherwise we are opened in many different changes
14:14:31 <bzurkowski> No time for reviews and patches
14:14:42 <dkrol_> This is good idea but I think we should have one change per person
14:15:06 <bzurkowski> E.g. this week we could focus on pushing through Darek's work on Devstack or Marcin's work on Python 3 support
14:15:16 <dkrol_> As it is hard to work on the same change
14:15:26 <mpiwowarczy> dkrol: why do you ask all this? are there any requirements on milestone 2
14:15:55 <bzurkowski> dkrol: Good point
14:16:10 <cezary_zukowski_> I am wondering about authorship issues if working on a sole change
14:16:14 <dkrol_> I'm asking because I see slower pace than before
14:16:17 <bzurkowski> Then maybe we should put cumulative focus in terms of reviews?
14:16:37 <dkrol_> And I would like to have some features implemented in Stein release :)
14:16:44 <mpiwowarczy> dkrol: I see
14:17:12 <dkrol_> I agree we can focus only on few changes regarding reviews
14:17:31 <dkrol_> I see 2 main open changes right know
14:17:51 <dkrol_> Python 3 support and devstack image
14:17:55 <bzurkowski> Yes
14:18:07 <bzurkowski> Let's close at least one in the upcoming week
14:18:23 <mpiwowarczy> both are almost done
14:18:36 <dkrol_> And we have 2 core reviews for each
14:19:01 <dkrol_> Yesterday I thought python 3 is done :)
14:19:26 <bzurkowski> It is very ready at the moment :)
14:19:41 <bzurkowski> Quick glance and it can be merged
14:20:01 <dkrol_> Ok, I will add review today
14:20:03 <bzurkowski> I propose to focus on this one in the first place
14:20:19 <mpiwowarczy> dkrol: I saw your +2, I have added small change according to bzurkowki comments
14:21:11 <dkrol_> Great
14:21:30 <dkrol_> My second question is related to milestones and release
14:22:16 <dkrol_> We don't have so much time till release giving our current paste
14:22:46 <dkrol_> And I would be much more happy knowing that you have more time during the day to work on trove :)
14:23:08 <dkrol_> Paste - >pace
14:23:37 <dkrol_> Python 3 is definitely the main focus
14:23:47 <dkrol_> Then there is devstack image
14:24:05 <dkrol_> As it is already implemented
14:24:33 <dkrol_> And then I see the next goal - pre upgrade checks
14:24:34 <bzurkowski> Pre-upgrade checks?
14:24:41 <bzurkowski> The second goal
14:24:45 <dkrol_> But this is something for 1 person
14:24:49 <mpiwowarczy> there is already implemented skeleton
14:24:56 <mpiwowarczy> we just need to add procedures
14:25:01 <dkrol_> I was thinking to start working on it
14:25:19 <dkrol_> Do you have anything else started?
14:25:27 <dkrol_> Besides documentation? :)
14:25:58 <bzurkowski> Not from my side
14:26:03 <cezary_zukowski_> no update on docs compared with past week :)
14:26:09 <mpiwowarczy> nothing
14:26:19 <bzurkowski> Pure sadness...
14:26:46 <dkrol_> Hmm... So maybe something on the horizon?
14:27:14 <bzurkowski> Well
14:27:38 <bzurkowski> We should definitely plan further work according to goals that we presented at Summit
14:27:59 <bzurkowski> In particular the ones reported by operators
14:28:19 <mpiwowarczy> +1
14:28:25 <dkrol_> Operators?
14:28:33 <bzurkowski> https://www.openstack.org/assets/presentation-media/Trove-Project-Update-Final.pdf
14:28:54 <bzurkowski> dkrol: We had discussions with people at Summit regarding issues in Trove
14:29:05 <dkrol_> List of priorities has osc migration, migrate to user data, tempest
14:29:09 <bzurkowski> Main concern was related to building guest images and security
14:29:26 <bzurkowski> What about Nova deprecation issue?
14:29:31 <bzurkowski> What is the deadline for this?
14:29:53 <bzurkowski> If Nova drops personality files before we migrate to user data Trove will be in trouble
14:30:19 <dkrol_> Not sure, but not this release
14:30:29 <bzurkowski> We must be sure :)
14:30:41 <bzurkowski> There is a spec for this migration
14:30:57 <mpiwowarczy> can anyone check it?
14:31:10 <mpiwowarczy> or I will do that
14:31:26 <bzurkowski> Fast way would be to ask in their IRC channel
14:31:37 <bzurkowski> They are big, they should be responsive
14:31:54 <bzurkowski> Maybe they will suggest better alternative
14:32:15 <dkrol_> I cannot find it right know
14:32:22 <mpiwowarczy> ok, I will ask
14:32:29 <dkrol_> There is suggestion
14:32:31 <bzurkowski> mpiwowarczy: Great, thank you
14:32:44 <dkrol_> There is everything besides implementation :)
14:33:42 <bzurkowski> Nova deprecation issue is one thing
14:33:50 <dkrol_> There is even a page on trove documentation about it
14:34:00 <bzurkowski> There is whole spec
14:34:02 <dkrol_> This is point 2 on my list
14:34:34 <bzurkowski> The second feature worth considering is new communication channel between guest agent and control plane
14:34:37 <bzurkowski> Many people were asking about it
14:34:56 <bzurkowski> Do you remember?
14:35:18 <bzurkowski> Communication channel similar to Octavia
14:35:22 <dkrol_> Yes, but I remember I didn't understand security implication of it
14:35:41 <dkrol_> Thats why I was hesitant about its priority
14:35:46 <bzurkowski> The implication is that guestm in its configuration, has full cvredentials to message broker
14:36:04 <bzurkowski> It can communicate with any OpenStack service
14:36:46 <dkrol_> Hmm... But it can have a different user on rabbit mq with access to only one queue
14:37:20 <dkrol_> You can configure user and password in guest agent
14:37:25 <bzurkowski> I'm not sure it is as easy as that
14:37:39 <bzurkowski> What about communication with Swift for backups?
14:37:44 <dkrol_> And on the rabbit mq you can add also configuration
14:37:44 <mpiwowarczy> guys, I think it's not the time for technical details :)
14:38:31 <dkrol_> This is not related to rabbitmq
14:38:43 <bzurkowski> This is RPC
14:38:51 <bzurkowski> All RPC happens via MB
14:39:15 <dkrol_> But backup upload is direct with swift client right?
14:39:34 <bzurkowski> Need to check
14:39:40 <mpiwowarczy> dkrol_: yes
14:39:41 <dkrol_> Maybe we could have a call about it? :)
14:39:44 <bzurkowski> Anyway
14:39:47 <mpiwowarczy> directly to swift endpoint
14:39:51 <dkrol_> Anyway
14:39:55 <bzurkowski> We should drink some beers and have longer discussion ;)
14:40:02 <bzurkowski> Trove beer meeting
14:40:06 <dkrol_> Agree
14:40:18 <dkrol_> We should call it trove meet up
14:40:46 <bzurkowski> 4 more points in the agenda
14:40:49 <dkrol_> Anyway this is a topic for another person
14:40:56 <bzurkowski> Let's listen to mpiwowarczy and move on
14:41:33 <dkrol_> Ok but python 3 and the last item are done :)
14:41:44 <dkrol_> #topic unstable integration tests
14:41:49 <dkrol_> What about it?
14:42:02 <mpiwowarczy> yes, this is what I have added to the agenda
14:42:20 <mpiwowarczy> I have noticed today we have unstable all integration tests
14:42:41 <mpiwowarczy> this is caused by upgraded devstack to Ubuntu Bionic version - this is commit from yesterday https://github.com/openstack-dev/devstack/commit/5b5cf9dd31a3c01602e4ea7bf7a1a4c63c89e96d
14:42:47 <dkrol_> We can't we use previous Ubuntu version?
14:43:06 <mpiwowarczy> dkrol_: trovestack is not compatible with Bionic
14:43:31 <dkrol_> I mean - let's use previous Ubuntu version
14:43:45 <mpiwowarczy> yeah
14:43:53 <mpiwowarczy> this is one possible solution
14:44:09 <bzurkowski> Can we?
14:44:16 <bzurkowski> Do we have a choice? :p
14:44:17 <mpiwowarczy> but before we need find a way how to execute devstack on Xenial as it was all the time
14:44:28 <mpiwowarczy> don't know
14:44:42 <mpiwowarczy> there is run-devstack ansible role
14:44:45 <dkrol_> Probably we need to set some env variable
14:45:18 <mpiwowarczy> maybe
14:45:36 <mpiwowarczy> better solution is to add compatybility for Bionic
14:45:58 <dkrol_> Sure, but we lack time :/
14:46:28 <dkrol_> So I recommend to stick to previous version if possible
14:46:34 <mpiwowarczy> sooner or later we will have to do that
14:46:47 <mpiwowarczy> hmm
14:47:00 <bzurkowski> Yea, it would be nice to have it compatible now
14:47:05 <bzurkowski> But I agree with Darek
14:47:08 <bzurkowski> First things first
14:47:14 <mpiwowarczy> if I will find some time I will have a look is this possible
14:47:50 <mpiwowarczy> ok
14:48:00 <dkrol_> Ok, let's check how to have running tests even if it means using previous Ubuntu
14:48:33 <mpiwowarczy> dkrol_: ok
14:48:43 <dkrol_> Next topic is python 3 support
14:48:54 <dkrol_> #topic python 3
14:49:03 <mpiwowarczy> we have partialy cover this topic before
14:49:06 <dkrol_> I assume we discussed it already
14:49:18 <bzurkowski> mpiwowarczy: Are we done with this one after we merge https://review.openstack.org/#/c/604816/ ?
14:49:22 <mpiwowarczy> one more thing - I have updated etherpad
14:49:26 <mpiwowarczy> progress looks very positive - https://etherpad.openstack.org/p/trove-pytho
14:49:56 <dkrol_> Good
14:50:10 <dkrol_> We will need to update wiki after merge
14:50:11 <mpiwowarczy> bzurkowsk: with trove - yes
14:50:35 <mpiwowarczy> but wi will have to update wiki tracking page
14:50:36 <bzurkowski> mpiwowarczy: Looks great, good job!
14:50:52 <dkrol_> Awesome!
14:50:54 <mpiwowarczy> in the coming days, I will have to make research, how to update wiki
14:51:23 <dkrol_> Will you have time?
14:51:50 <dkrol_> Anyway
14:51:59 <mpiwowarczy> hard to say
14:52:04 <dkrol_> #topic documentation
14:52:15 <dkrol_> Cezary said there is no progress
14:52:30 <dkrol_> Anything to add?
14:52:39 <cezary_zukowski_> yeah, this week I didn't touch the subject
14:52:40 <mpiwowarczy> nothing
14:52:57 <dkrol_> #topic next actions
14:53:20 <dkrol_> This was related to my first questions
14:53:57 <dkrol_> What to do to have more contributions in Stein than in Rocky :)
14:54:13 <dkrol_> I suppose we have issues with finding time for contribution
14:54:22 <bzurkowski> We must have more contributors...
14:54:41 <dkrol_> So my question is about your prediction what will happen in the next 2-3 months?
14:55:18 <dkrol_> This is 8-12 weeks only :/
14:55:44 <dkrol_> I have to relogin
14:56:40 <dkrol> Any last thought?
14:56:45 <bzurkowski> Yes
14:56:53 <bzurkowski> From the beginning of the next year there should be a noticable increase in contributions to Trove
14:57:11 <dkrol> Is it a wish or a plan?
14:57:16 <bzurkowski> Concrete plan
14:57:27 <dkrol> Great
14:57:33 <bzurkowski> Plan to do massive upstreaming of Samsung internal changes
14:57:41 <bzurkowski> We will have resources to accomplish that
14:57:57 <bzurkowski> This is what I can say at this point
14:57:58 <dkrol> Wonderful
14:58:14 <dkrol> Leta finish with this
14:58:33 <dkrol> And think about trove meetup :)
14:58:40 <bzurkowski> Will keep it in mind ;)
14:58:41 <dkrol> See you
14:58:42 <bzurkowski> Great talk guys
14:58:45 <bzurkowski> Take care!
14:58:47 <mpiwowarczy> bye
14:58:50 <cezary_zukowski_> see you
14:58:56 <dkrol> #endmeeting