14:00:04 #startmeeting trove 14:00:05 Meeting started Wed Feb 27 14:00:04 2019 UTC and is due to finish in 60 minutes. The chair is dkrol. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:06 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:08 The meeting name has been set to 'trove' 14:00:14 Hello 14:00:35 Hello 14:00:43 Hello 14:00:57 Lets' wait few more minutes 14:01:04 Sure 14:06:28 Our new colleague is troubling with connection 14:06:34 "Too many user sessions" 14:06:42 :/ 14:06:53 Let's wait one more minute 14:06:59 Sure 14:08:29 hi all 14:08:37 Hi 14:08:52 Hi 14:11:12 Can we start? 14:11:30 Yes 14:11:39 He cannot log in 14:11:42 #topic recent changes 14:11:44 He will try another time 14:11:50 So what's up? 14:13:39 Well 14:14:18 The first change from Kasper regarding Redis logs has been already merged 14:14:26 I am very glad he joined the project 14:15:12 Yes, it is great 14:15:17 Soon he will add more changes 14:16:52 There is one thing that I would like to put under discussion 14:17:23 Please 14:17:28 We have several changes that introduce guest support for Cassandra 3.x 14:17:42 However, current guest implementation supports only 2.x 14:18:01 The question is: how do we approach datastore versioning? 14:18:16 Should we support multiple versions, in that case 2.x and 3.x 14:18:24 Or maybe we should only support the latest one 14:18:25 ? 14:18:42 Mmmmm.... 14:18:50 This is problematic in Trove since there is no defined approach 14:19:25 I believe we should support versioning 14:19:59 Guest agent has info about data stare version 14:20:34 Yes 14:20:48 So the problem is in loading correct python module based on the version 14:20:57 Also 14:21:09 Should we have a separate strategy class for each version? 14:21:37 Or provide "template" class with subclass for each version? 14:22:27 I'm not sure what do you mean by template class? 14:23:32 I mean 14:25:21 For example: BaseCassandraStrategy with basic flow using abstract methods for logic that differs between versions 14:25:39 That would be our "template" class 14:25:49 And then, we could have subclasses such as: 14:26:20 Cassandra2Strategy and Cassandra3Strategy inheriting by BaseCassandraStrategy and implementing abstract methods 14:27:31 By "flow" I mean the management flow (provisioning, backup, configuration etc.) 14:27:34 Is it clear now? 14:28:23 Ok, but it is a way of code sharing between classes supporting different versions 14:28:45 Yes 14:28:49 I'm not sure if this solves issue which class to load 14:28:57 It is not 14:29:11 Much work would have to be done in order to load appropriate strategies dynamically 14:30:33 I am wondering 14:30:42 I don't have an answer now so let's think about it and discuss approaches next time 14:30:56 Maybe we should just support the latest version? 14:31:16 It would be much easier to follow new versions of the engine 14:31:29 Until we find another solution to the problem and implement it into the code 14:32:25 My concern is you will be able to break trove deployment just by upgrading stuff 14:33:00 And most people will run more than one version of a database 14:33:58 Let's take a look at the code first 14:34:46 ok 14:35:22 I wanted to thank you for reviewing my documentation change 14:35:48 I committed a new version of it 14:36:13 Yes, I will take a look soon 14:36:14 Also there is another change related to documentation in Gerrit 14:36:28 A small update 14:37:34 Please take a look at it also 14:38:07 dkrol: yw, nice to see have such type of guide :) 14:38:48 Also I've created a page about rabbitmq throttling 14:39:04 You can find a link on trove general 14:39:16 It is related to security and ddos 14:39:58 I need to make some tests 14:40:34 I will try to check it out 14:41:01 I would be good to have some answers regarding this issue as it is a major concern 14:41:36 What about mailing list? 14:41:45 We could ask Lingxian Kong about his opinion 14:42:02 Once I will do tests 14:42:08 He seems to have production experience with Trove 14:42:22 And recently he is introducing security-related changes 14:43:09 Yes, he is working on production deployment of trove 14:43:31 We should help him in his problems :) 14:43:50 Please take a look and respond to his questions 14:43:55 Yes, we should too ;) 14:44:51 This is all from me this week 14:44:58 Do you have anything else? 14:46:16 Not from my side 14:46:17 But 14:47:03 Please, think about the datastore versioning so we could decide next week on how to procees 14:47:06 *proceed 14:47:29 Sure 14:47:32 Thanks 14:47:51 See you next time 14:47:54 See you 14:47:55 Bye 14:47:58 Bye 14:48:02 #endmeeting