14:02:10 <dkrol> #startmeeting trove
14:02:11 <openstack> Meeting started Wed Nov 21 14:02:10 2018 UTC and is due to finish in 60 minutes.  The chair is dkrol. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:02:12 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:02:15 <openstack> The meeting name has been set to 'trove'
14:02:17 <bzurkowski> Hello everybody
14:02:22 <dkrol> Hello
14:02:46 <dkrol> Let's wait for a few minutes for the rest
14:02:52 <pgodek> Hi All
14:03:10 <dkrol> Hi
14:04:11 <dkrol> #topic openstack summit summary
14:04:28 <dkrol> Maybe let's start since I need to leave very soon
14:04:48 <dkrol> Our first topic is related to openstack cummit
14:05:17 <dkrol> Can you summarize what happened and do we have any conclusions?
14:05:23 <bzurkowski> Yes
14:05:27 <bzurkowski> Great party
14:05:29 <pgodek> 1. Project Update gather a lot of audience and we have made several very interesting conversations
14:06:16 <dkrol> Anything specific for the project?
14:06:33 <pgodek> 2. Project Onbording was also kind of sucess - at least two new potentialy involved
14:07:16 <pgodek> 3. OVH announced they will introduce Trove on their public cloud
14:07:57 <dkrol> Do they have any feature requests?
14:08:03 <pgodek> On Project Update we have identified two issues that have to resolved in order to make trove trustfull
14:08:56 <pgodek> First is security risk - communication between data and contol plain
14:09:16 <pgodek> Second - Way to update guest agent code with no DB downtime
14:10:03 <dkrol> What do you mean by the first issue?
14:10:12 <dkrol> What kind of security risk?
14:10:21 <pgodek> first of two identified and needed to be fixed
14:10:32 <pgodek> Using conductor is not dafe
14:10:35 <pgodek> *safe
14:11:11 <pgodek> or rather .... we have user and password to queue in config file
14:11:26 <dkrol> Hmmm... I'm not sure if I know why
14:11:39 <pgodek> because guest agent writes to queue
14:11:50 <dkrol> Hmmm... I'm not sure if I know why
14:11:55 <dkrol> Maybe we should create a bug or etherpad about it?
14:12:05 <pgodek> AFAIR there is already buleprint for this issue
14:12:43 <pgodek> #link https://blueprints.launchpad.net/trove/+spec/octavia-way-communication-between-api-and-guestagent
14:13:32 <dkrol> I'm not sure if it explains why
14:13:58 <dkrol> I'm not sure if it explains why
14:14:48 <dkrol> I believe we need to explain it if we want to introduce such a big change
14:15:34 <pgodek> if you are able to send events on queue, you can destroy all instances
14:16:53 <pgodek> Everyone we was talking with and who have done trove evaluation was aware of this issue and it is named as security risk
14:17:29 <pgodek> and it is a reason why trove is not on any big public cloud
14:18:09 <pgodek> Does it explains why we need to start work on this issue ?
14:18:30 <dkrol> Ok, maybe I just don't understand when it is less secure then http communication
14:19:02 <dkrol> Maybe let's try to explain it better in the blueprint?
14:19:10 <dkrol> And we can move forward
14:19:41 <dkrol> Anything else from the summit?
14:19:59 <dkrol> And did ovh resolve these issues?
14:20:01 <pgodek> Yep, better blueprint is needed
14:20:25 <pgodek> No, OVH don't have trove team established yet
14:21:24 <dkrol> How about your last session?
14:22:05 <pgodek> It was well received.
14:22:45 <dkrol> It received very good marks
14:23:04 <dkrol> Was there any people interesting in this kind of deployments?
14:23:21 <dkrol> I mean to be supported by trove somehow?
14:24:05 <dkrol> And was there any discussion about database scaling up or out?
14:24:06 <pgodek> I think @b.zurkowski had few conversation about it
14:24:27 <pgodek> No - there was no discussion about scaling DB
14:24:29 <bzurkowski> dkrol: There was no such interes
14:24:35 <bzurkowski> *interest
14:25:10 <pgodek> But there was a question ( during onboarding ) about trove vs Containers ( via Operators framework )
14:25:23 <dkrol> Hmmm... How about integration with Mistral to schedule some tasks?
14:27:17 <pgodek> I don't recall conversation about any synergy between trove/mistral. But we had nice chat with Vitrage team.
14:28:29 <dkrol> Nice, you did some contribution to vitrage
14:28:50 <pgodek> Bartek have pushed some code
14:29:42 <dkrol> Did you make some notes eg on etherpad about features that people would like to have in trove?
14:30:05 <bzurkowski> pgodek obligated to write down all issues and ideas discussed during Summit and publish them via etherpad
14:30:31 <dkrol> Great
14:30:33 <pgodek> yep, will do that
14:30:59 <dkrol> Would like to share anything else about summit?
14:32:12 <pgodek> It looks like project have quite an intrest
14:32:35 <bzurkowski> If we want to revitalize Trove we must take advantage of the momentum
14:33:09 <dkrol> True
14:33:53 <dkrol> So should we adjust our focus for Stein?
14:35:19 <bzurkowski> We could put more priority to "new communication channel between guest and control plane"
14:35:42 <bzurkowski> Since that was one of the major issues reported by potential users
14:36:06 <bzurkowski> And we already have draft in trove specs
14:36:08 <pgodek> plus upgrade agent code
14:36:19 <bzurkowski> This one is too big for now
14:36:22 <bzurkowski> In my opinion
14:36:32 <dkrol> Sounds good, so maybe let's describe what we now about both issues
14:37:13 <dkrol> So it is clear why and what we should do and that there is no alternative
14:37:26 <pgodek> @bzurkowski - first of all we need proper blueprints for both
14:38:58 <dkrol> I agree
14:39:08 <dkrol> Unfortunately I have to go
14:39:13 <dkrol> Sorry for this
14:39:28 <dkrol> Please continue with rest of the topics for today
14:39:35 <dkrol> I will read it later
14:39:48 <dkrol> Thanks for the summit and take care
14:39:56 <bzurkowski> dkrol: No problem, take care, bye
14:40:40 <bzurkowski> #topic python3 support
14:41:23 <bzurkowski> As far as I know there was not much activity in this area
14:41:42 <pgodek> I don't have knowledge about progress python3
14:42:50 <bzurkowski> #link https://etherpad.openstack.org/p/trove-python-3
14:43:26 <bzurkowski> Progress with accomplishing this goal looking nice in the pad
14:45:04 <bzurkowski> One change needs to be merged in order to close it for Trove core repository: https://review.openstack.org/#/c/604816/
14:45:32 <bzurkowski> #topic documentation
14:46:26 <bzurkowski> I guess there is not much to discuss in this topic neither
14:47:09 <bzurkowski> Recent effort was put mostly on the Summit
14:47:42 <pgodek> indeed
14:47:55 <bzurkowski> But
14:48:25 <bzurkowski> We had great discussion during Summit with Peter from DBAStorage
14:48:51 <bzurkowski> He was interested in helping us with improving documentation
14:49:29 <bzurkowski> As well as reviewing DB procedures implemented in Trove code base
14:49:41 <pgodek> I was expecting him today
14:49:51 <bzurkowski> So was I
14:50:05 <bzurkowski> I will contact him this week to keep the things going
14:50:12 <pgodek> good move
14:50:23 <bzurkowski> His expertis would be valuable for the project
14:52:22 <bzurkowski> I think we can finish for today
14:52:29 <bzurkowski> Any more comments?
14:52:39 <pgodek> not from my side
14:52:52 <pgodek> and since it looks like there is only two of us ...
14:56:41 <pgodek> do we have any other topic ?
14:56:54 <bzurkowski> Nope
14:57:02 <bzurkowski> Thank you all then
14:57:06 <pgodek> so thanks
14:57:09 <bzurkowski> And goodbye!
14:57:12 <pgodek> have good day!
14:57:15 <bzurkowski> #endmeeting
14:58:40 <bzurkowski> #chair bzurkowski
14:58:48 <bzurkowski> #endmeeting
14:59:49 <Dk> #endmeeting
15:00:23 <e0ne> afair, only chairs can add new chairs and end meetings
15:00:46 <bzurkowski> e0ne: Sorry for delay
15:01:09 <e0ne> bzurkowski: np, we'll wait
15:01:19 <e0ne> @!
15:01:19 <_pewp_> e0ne ( *՞ਊ՞*)ﾉ
15:01:45 <dkrol> #endmeeting