14:01:37 <andreykurilin> #startmeeting Rally
14:01:38 <openstack> Meeting started Mon Nov 14 14:01:37 2016 UTC and is due to finish in 60 minutes.  The chair is andreykurilin. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:39 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:01:41 <openstack> The meeting name has been set to 'rally'
14:01:43 <andreykurilin> o/
14:01:53 <astarove_> hi all
14:02:49 <amaretskiy> hi
14:03:00 <astudenov> hi
14:03:44 <andreykurilin> ok
14:03:46 <andreykurilin> let's start
14:04:22 <andreykurilin> #topic [andreykurilin] how to optimize db migration - https://review.openstack.org/#/c/297020/
14:04:39 <andreykurilin> I have a big database
14:04:44 <andreykurilin> 95k rally results
14:05:10 <andreykurilin> and I tried to use migration from 297020 patch
14:05:19 <andreykurilin> it took my resources...
14:05:41 <andreykurilin> let's discuss how we can optimize migration process
14:05:57 <amaretskiy> maybe suggest to create new db and use legacy rally (in another venv) for working with old results
14:06:20 <amaretskiy> this will save a lot of time
14:06:44 <amaretskiy> sometimes it is very useful to break compat
14:06:46 <andreykurilin> it is a solution, but it will add a pain when you will need to build trends reports
14:07:31 <amaretskiy> use old rally for some edge day and then upgrade rally and do not mix db resuts in reports
14:08:05 <andreykurilin> it is a wrong behaviour:) in such case, users will not update rally at all
14:08:15 <amaretskiy> i think that break compat in this specific case is much cheaper that try to keep one
14:08:26 <andreykurilin> heh
14:08:29 <amaretskiy> ok, just an idea :)
14:08:47 <amaretskiy> forget :)
14:08:52 <andreykurilin> lol
14:09:21 <amaretskiy> approach #2 - truncate DB
14:10:23 <andreykurilin> hm... truncase instead of delete should help
14:11:02 <amaretskiy> remove old records and keep recent ones (one month for example)
14:11:44 <amaretskiy> this requires running SQL by admins
14:11:50 <andreykurilin> ;(
14:12:06 <amaretskiy> db schema is simple so this i snot a problem
14:13:00 <amaretskiy> or prepare SQL script
14:13:04 <andreykurilin> ok, any other ideas?
14:13:17 <amaretskiy> nothing from me :)
14:14:14 <andreykurilin> ok:( unfortunately we do not have enough participants
14:14:19 <andreykurilin> let's move to next topic
14:14:38 <andreykurilin> #topic  new place for rally chat - gitter. plans&workflow
14:15:15 <astarove_> gitter looks very friendly for me
14:15:27 <amaretskiy> #vote +1 for gitter for all needs
14:15:46 <andreykurilin> As we discussed at previous meeting, I heard a lot of notes about irc and maybe moving to new messaging will help to involve more people
14:15:56 <andreykurilin> gitter is a messager from github
14:16:22 <andreykurilin> I created a public channel there https://gitter.im/rally-dev/Lobby
14:17:01 <andreykurilin> Also, it has irc tranc for those who like irc)
14:17:10 <andreykurilin> gitter will not fully replace our #openstack-rally channel
14:17:29 <andreykurilin> we need to add a bot to sync messages between these channels
14:17:47 <andreykurilin> so everyone will have ability to choose whatever they like way for communication
14:18:51 <andreykurilin> I chose gitter because it has uservriendly interface, uses github/twitter login for authentication
14:19:23 <andreykurilin> and allows to create a various channels with separate admins
14:19:41 <andreykurilin> I do not know when we will need more than one channel
14:20:10 <andreykurilin> but I want to try separate channel for status messages like statuses from gerrit and new bug-reports
14:20:28 <andreykurilin> folks, what do you think about separate channel for such messages?
14:20:30 <astarove_> also we need to set up some reminder which will notify users about new chat in gitter
14:20:38 <andreykurilin> yep
14:20:49 <andreykurilin> and update docs to include this info
14:21:38 <andreykurilin> ok... let's move to the next topic
14:21:39 <astarove_> one channel for features, one for issues
14:21:48 <astarove_> sounds good
14:21:53 <astudenov> i think link to gitter should be included in rally readme in github
14:22:07 <andreykurilin> +1
14:22:39 <andreykurilin> #topic trello board
14:23:07 <andreykurilin> unfortunately, I had not enough time last week, so I do not have a good progress in this topic
14:23:33 <andreykurilin> But I restored our old board and updated columns
14:23:36 <andreykurilin> https://trello.com/b/DoD8aeZy/rally
14:23:58 <andreykurilin> please join this board and share progress and work-items there
14:24:43 <andreykurilin> Also, it is a good place to share tasks&ideas for which you do not have enough time, but other contributors can be interested in
14:25:57 <amaretskiy> nice!
14:26:48 <andreykurilin> btw, we need a bot for trello :) to post changes to "status" chat. Maybe it can be helpful
14:27:32 <andreykurilin> ok
14:27:40 <andreykurilin> it looks like I have no more topics
14:27:48 <andreykurilin> #topic Open discussion
14:27:56 <andreykurilin> any topics to discuss?
14:28:01 <astarove_> no
14:28:02 <amaretskiy> nothing from me
14:28:26 <astudenov> no
14:28:42 <andreykurilin> okay
14:28:51 <andreykurilin> thanks for attention
14:28:55 <andreykurilin> #endmeeting