| *** openstackgerrit has quit IRC | 00:01 | |
| *** openstackgerrit has joined #openstack-freezer | 00:01 | |
| *** reldan has quit IRC | 01:22 | |
| *** szaher has quit IRC | 02:12 | |
| *** dschroeder has quit IRC | 02:57 | |
| *** smekel has quit IRC | 04:07 | |
| *** smekel has joined #openstack-freezer | 04:08 | |
| *** szaher has joined #openstack-freezer | 07:49 | |
| *** reldan has joined #openstack-freezer | 08:22 | |
| *** reldan has quit IRC | 08:22 | |
| *** reldan has joined #openstack-freezer | 08:47 | |
| *** jonaspf has quit IRC | 09:00 | |
| *** jonaspf has joined #openstack-freezer | 09:02 | |
| *** nullvariable has joined #openstack-freezer | 10:17 | |
| *** jonaspf has quit IRC | 10:19 | |
| *** jonaspf has joined #openstack-freezer | 10:22 | |
| *** vannif has quit IRC | 10:26 | |
| *** jonaspf has quit IRC | 11:25 | |
| *** jonaspf has joined #openstack-freezer | 11:26 | |
| openstackgerrit | Eldar Nugaev proposed stackforge/freezer: Test coverage improvments: Validator and Utils https://review.openstack.org/231469 | 11:28 |
|---|---|---|
| openstackgerrit | Eldar Nugaev proposed stackforge/freezer: Test coverage improvments: Validator and Utils https://review.openstack.org/231469 | 11:31 |
| *** jonaspf has quit IRC | 11:41 | |
| *** jonaspf has joined #openstack-freezer | 11:45 | |
| openstackgerrit | Eldar Nugaev proposed stackforge/freezer: Test coverage improvments: Validator and Utils https://review.openstack.org/231469 | 12:12 |
| *** jonaspf has quit IRC | 12:14 | |
| *** jonaspf has joined #openstack-freezer | 12:18 | |
| *** vannif has joined #openstack-freezer | 13:22 | |
| *** marzif has joined #openstack-freezer | 13:23 | |
| *** marzif has quit IRC | 13:41 | |
| *** marzif has joined #openstack-freezer | 13:41 | |
| *** marzif has quit IRC | 14:00 | |
| *** marzif has joined #openstack-freezer | 14:01 | |
| *** marzif has quit IRC | 14:02 | |
| *** jonaspf has quit IRC | 14:37 | |
| *** dschroeder has joined #openstack-freezer | 14:43 | |
| *** jonaspf has joined #openstack-freezer | 14:45 | |
| openstackgerrit | Memo Garcia proposed stackforge/freezer-web-ui: Add Freezer dashboard to Admin dashboard https://review.openstack.org/232581 | 15:00 |
| m3m0 | Hey guys are you ready for the meeting? | 15:01 |
| m3m0 | #startmeeting | 15:01 |
| freezerBot` | m3m0: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee' | 15:01 |
| openstack | m3m0: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee' | 15:01 |
| reldan | ready | 15:01 |
| m3m0 | #startmeeting Thu 08/ 10 | 15:01 |
| freezerBot` | Meeting started Thu Oct 8 15:01:45 2015 UTC and is due to finish in 60 minutes. The chair is m3m0. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:01 |
| freezerBot` | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:01 |
| freezerBot` | The meeting name has been set to 'thu_08__10' | 15:01 |
| openstack | Meeting started Thu Oct 8 15:01:45 2015 UTC and is due to finish in 60 minutes. The chair is m3m0. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:01 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:01 |
| openstack | The meeting name has been set to 'thu_08__10' | 15:01 |
| m3m0 | as always, notes about the meeting are available here... https://etherpad.openstack.org/p/freezer_meetings | 15:02 |
| m3m0 | please update your information | 15:02 |
| m3m0 | vannif, you are first to go | 15:03 |
| vannif | hi all. | 15:04 |
| vannif | working on integration tests. | 15:04 |
| vannif | to install freezer-api as a devstack plugin | 15:05 |
| vannif | and freezer-web-ui as well as soon as the freezer-api installs flawlessly | 15:05 |
| vannif | I've also to finish some more evoluted integration tests for lvm | 15:06 |
| m3m0 | do we have a blueprint that we can review or comment for this task? | 15:06 |
| *** marzif has joined #openstack-freezer | 15:06 | |
| vannif | hmmm not specifically for devstack plugins, they are part of a broader effort to provide integration tests | 15:06 |
| marzif | I'm late, sorry | 15:06 |
| vannif | that is pretty much all for me atm | 15:07 |
| m3m0 | is this internal or external effort? this will be commited upstream? | 15:07 |
| vannif | yes. upstream. | 15:07 |
| m3m0 | cool, if you need help with reviews let us know | 15:08 |
| vannif | actually it's a /devstack folder in the freezer-api project tree wich contains scripts to install the api | 15:08 |
| vannif | in the end the user will only need a single line in the local.conf | 15:08 |
| vannif | which triggers the git clone and install scripts | 15:09 |
| m3m0 | I assume the README cover this procedure right? | 15:09 |
| vannif | that is the "framework" for the integration tests | 15:09 |
| vannif | yes, it will contain instructions for that | 15:09 |
| m3m0 | nice :) | 15:10 |
| vannif | but htanks for the remainder ;) | 15:10 |
| vannif | reminder | 15:10 |
| m3m0 | no problem :) | 15:10 |
| m3m0 | do you have anything else to say? or do you need help with anything? | 15:11 |
| vannif | nothing mush to say. Fausto is giving me some help with the devstack dependencies installation | 15:12 |
| vannif | s/mush/much | 15:12 |
| m3m0 | perfect :), thanks a lot | 15:12 |
| vannif | thank you | 15:12 |
| m3m0 | reldan you're next | 15:12 |
| reldan | Thank you | 15:13 |
| reldan | Last week I mostly was improving code coverage. Cannot say that I improved it drastically, but a couple of percentages. | 15:14 |
| reldan | I also should make changes in cofig - for parallel backup, but going to do it after release | 15:14 |
| m3m0 | that's great news | 15:14 |
| m3m0 | about what exactly? | 15:14 |
| reldan | About 2.0 I assume | 15:15 |
| reldan | That should be in couple of weeks | 15:15 |
| reldan | I also would like to refactor lvm/shadow | 15:16 |
| m3m0 | I agree with the refactor | 15:16 |
| m3m0 | the interface should be the same | 15:16 |
| reldan | Because now for example we cannot do windows shadow with mysql | 15:16 |
| reldan | only lvm | 15:16 |
| reldan | And it seems not very right | 15:16 |
| m3m0 | that's true, it should be decouple | 15:17 |
| reldan | Also lvm is the last place that heavily uses backup_dict | 15:17 |
| m3m0 | but are we going to use the exec command? or do you have anything in mind for that? | 15:17 |
| reldan | And not only read from this dictionary, but makes writes to dictionary and even replaces | 15:18 |
| reldan | Sorry, what is exec command? | 15:18 |
| m3m0 | shadow code also has the same behaviour | 15:18 |
| m3m0 | is for pre and post script execution | 15:18 |
| reldan | Yes, and let’s imagine that we would like to support postreSql | 15:19 |
| reldan | Yes, we should create some classes here and decouple, making snapshot shoudn’t know anything about mysql, sqlserver, mongo or anything | 15:19 |
| reldan | I was trying to refactor it - but it seems to be a very big refactor, so I just postponed it until the release | 15:20 |
| m3m0 | and how will we manage the release of the databases after the snapshot creation? | 15:21 |
| m3m0 | how is develop right now is that it blocks the db and then create a snapshot and then relase the db, is that behaviuor going to change? | 15:21 |
| m3m0 | or this is an early talk? | 15:22 |
| reldan | let’s say we have an Application - it may by Mongo, Mysql, Postgres and it should have stop and start. And Snaphsot engine (Shadow, Lvm) with create and remove | 15:22 |
| reldan | So we should have application.stop(); snapshot.create(); application.start(); snapshot.remove() | 15:23 |
| m3m0 | I like this kind of interface | 15:23 |
| marzif | reldan, you are referring to the object interface, but not on stopping the service itself right? | 15:23 |
| marzif | I think it's good | 15:24 |
| marzif | we can do something like application.flush() | 15:24 |
| reldan | You, know probably it is not a good name. But as far as I know for mssql - we actually stop service | 15:24 |
| reldan | marzif: +1 | 15:24 |
| marzif | yes | 15:24 |
| m3m0 | yes | 15:24 |
| m3m0 | until we find a better way | 15:24 |
| marzif | application.stop if we stop make sense :) | 15:24 |
| marzif | for mysql we can use app.flush | 15:24 |
| reldan | let’s say flush | 15:25 |
| reldan | and recover | 15:25 |
| vannif | what about context managers ? | 15:25 |
| m3m0 | I have a question | 15:25 |
| reldan | What is a context manager? | 15:25 |
| m3m0 | if a new application will be supported as a plugin, should we add an interface to extend the arguments for that application? | 15:25 |
| vannif | for example: | 15:25 |
| vannif | with db.lock: | 15:25 |
| vannif | do things | 15:26 |
| reldan | m3m0: If we have a pluggable mechanism - probably we can just search it by name | 15:26 |
| vannif | well, we can discuss it in a deep dive | 15:26 |
| reldan | Yes, anyway we can provide application to snapshot, if we actually need it | 15:27 |
| reldan | like snapshot.create(application) | 15:27 |
| reldan | snapshot.remove(application) | 15:27 |
| m3m0 | mmm do we actually need to pass the application? | 15:28 |
| marzif | let's write a bp for this | 15:28 |
| reldan | I have no idea, but if it is necessery - we can do this way | 15:28 |
| reldan | Additional small comment - I suppose we should return from a job some result | 15:28 |
| m3m0 | +1 for the bp | 15:28 |
| reldan | And don’t work with backup_dict | 15:29 |
| reldan | Let’s have backup_dict at least read_only | 15:29 |
| szaher | vannif that what we were discussing today ? | 15:29 |
| reldan | And after the release, we should integrate rsync | 15:30 |
| m3m0 | but we return a result | 15:30 |
| reldan | It everything I had | 15:30 |
| m3m0 | at least with the api isn't | 15:30 |
| m3m0 | ? | 15:30 |
| marzif | reldan, backup_dict I think will be removed with Cliff | 15:30 |
| reldan | marzif: Yes! And it means that we should return something new instead of dict | 15:31 |
| reldan | And we shouldn’t have a writes to dict | 15:31 |
| marzif | after oslo.log implementation we can proceed with Cliff, yep | 15:31 |
| vannif | szaher, before lunch ? no, it was configuration file support. removing the backup_opt_dict is something that we discuss about in regard to many aspects, not just because of oslo.config | 15:31 |
| vannif | they are related of course | 15:32 |
| szaher | vannif, no what me, you and pierrer pluggable arch. for storage and agent | 15:32 |
| vannif | but I think reldan is talking about how to refactor the snapshot and db-locking code | 15:32 |
| szaher | vannif, no what me, you and pierre were discussing before that | 15:33 |
| reldan | Ok, let’s discuss it later - because it already takes so long | 15:33 |
| szaher | Ok, sorry guys | 15:33 |
| vannif | moving responsibilities to specific objects | 15:33 |
| reldan | I have nothing to add now | 15:33 |
| m3m0 | thanks reldan | 15:33 |
| reldan | Thank you m3m0 | 15:33 |
| m3m0 | and let us know if you need reviews or help with anything | 15:34 |
| reldan | https://review.openstack.org/#/c/231469/ | 15:34 |
| marzif | reldan, there are two reviews that needs to be +Aed right? | 15:34 |
| m3m0 | marzif you're next | 15:34 |
| marzif | ok | 15:34 |
| reldan | https://review.openstack.org/#/c/229467/ | 15:34 |
| reldan | Yes | 15:34 |
| marzif | I've been helping vannif with the integrated tests, doing code review, some arch meeting | 15:35 |
| marzif | nothing really concrete lol | 15:35 |
| marzif | I think we should move to cliff after oslo.log | 15:35 |
| m3m0 | I agree with that | 15:35 |
| marzif | and rethink the cli in a way that is backward compatible for a while | 15:36 |
| marzif | and create the python-freezerclient module | 15:36 |
| marzif | also I'm following up the move of the stackforge/freezer* repos to openstack namespace | 15:36 |
| m3m0 | szaher said that we should deprecate freezerc | 15:36 |
| m3m0 | and start using freezer | 15:36 |
| marzif | we should use freezer-agent | 15:37 |
| marzif | explicitally | 15:37 |
| m3m0 | but not get rid of freezerc until the next release | 15:37 |
| marzif | and freezer for the freezer client | 15:37 |
| marzif | freezerc is not a big issue, we can just create a symlink | 15:37 |
| marzif | when we install the python egg | 15:37 |
| marzif | anyway, we can dive deep on this after the oslo log implementation | 15:38 |
| m3m0 | and +2 for python-freezerclient | 15:38 |
| marzif | also we need to change the way we tag the releases across our 3 repos | 15:38 |
| m3m0 | is oslo.log planned for 2.0? | 15:38 |
| marzif | nope | 15:38 |
| marzif | Saad write the code | 15:39 |
| marzif | but it won't be in | 15:39 |
| marzif | as soon 2.0 is released we'll merge the oslo.log stuff | 15:39 |
| marzif | also we need to use a common version | 15:39 |
| marzif | like 2015.10.08 for the 3 packages | 15:39 |
| sc | marzif: I can help with logging but after work, it's difficult to schedule work on freezer for me other wise | 15:40 |
| marzif | otherwise we don't know which freezer-api works for sure the freezer-scheduler and so on | 15:40 |
| marzif | same for the web-ui | 15:40 |
| sc | szaher: do you mind some after dinner sessions? | 15:40 |
| m3m0 | and are we going to create branches for openstack relases? | 15:41 |
| m3m0 | like stable/liberty? | 15:41 |
| marzif | if we can yes | 15:41 |
| marzif | we have to | 15:41 |
| m3m0 | or are we going to move differently? | 15:41 |
| marzif | stable/release_name | 15:41 |
| marzif | but I was referring to the release naming convention | 15:41 |
| marzif | for the python eggs we upload to pypi | 15:41 |
| marzif | while the repo branching/tagging is exactly as you said | 15:42 |
| m3m0 | and is there any difference once we move from stackforge to openstack? | 15:43 |
| *** szaher_ has joined #openstack-freezer | 15:43 | |
| marzif | we probably needs less interaction with infra | 15:44 |
| marzif | but it will be all the same | 15:44 |
| m3m0 | and do you need help with anything? | 15:44 |
| marzif | not for now | 15:45 |
| marzif | ty | 15:45 |
| marzif | that's all from me | 15:45 |
| m3m0 | cool, thanks :) | 15:45 |
| m3m0 | szaher zsaher_ you're next | 15:45 |
| reldan | I don’t see him | 15:46 |
| m3m0 | thanks :) | 15:47 |
| m3m0 | I'll go next | 15:47 |
| m3m0 | I've been working on the ui | 15:47 |
| m3m0 | some commits are merged that help with the interaction of the newer versions of the api | 15:47 |
| m3m0 | and fix some bugs | 15:47 |
| m3m0 | now I'm working on the UX part of the ui | 15:48 |
| m3m0 | and soon on the testing, the thing is that besides unittesting I'll need to implement selenium testing | 15:48 |
| m3m0 | as part as the UX enhancements | 15:48 |
| m3m0 | the job window will be enough for a new user to create jobs with actions and managing sessions | 15:49 |
| m3m0 | but if they want, they can manage those items individually in their on page | 15:49 |
| *** szaher_ has quit IRC | 15:50 | |
| m3m0 | I'm also adding a CRUD page for actions | 15:50 |
| m3m0 | and a list of clients to interact with | 15:50 |
| m3m0 | and a kind of big re factoring in the code because most of the code is boilerplate and it's been repeated over and over | 15:50 |
| m3m0 | and I have this commit in progress https://review.openstack.org/#/c/232581/ | 15:51 |
| m3m0 | which enable freezer dashboard on the admin panel | 15:51 |
| m3m0 | but I have a question marzif | 15:51 |
| m3m0 | do we want freezer to be on it's own panel but only visible to admins | 15:52 |
| m3m0 | or do we want freezer to be included on the admin panel itself | 15:52 |
| m3m0 | the first one is very very easy to implement | 15:52 |
| m3m0 | the second one is a little bit more tricky | 15:53 |
| m3m0 | and lastly for the ui | 15:53 |
| m3m0 | I'm working on a installation script to make things easier for automation | 15:53 |
| m3m0 | regarding windows, I haven't work on that for a while | 15:53 |
| m3m0 | and I need to rebase the changes for freezer-agent on windows | 15:53 |
| m3m0 | and complete the scheduler for windows as well | 15:54 |
| m3m0 | that's it for me at the moment | 15:54 |
| m3m0 | szaher, you're next | 15:54 |
| szaher | Okay | 15:55 |
| szaher | Actually I was working on bug fixing | 15:55 |
| szaher | I fixed some and we need to test them on windows first | 15:55 |
| szaher | not all but this one specially https://review.openstack.org/#/c/229467/ | 15:56 |
| szaher | plz review and If it's Okay approve | 15:56 |
| szaher | m3m0 vannif we need to approve after m3m0 test on windows | 15:56 |
| szaher | sorry this is the correct one https://review.openstack.org/#/c/231398/ | 15:57 |
| szaher | I will be working on making freezer use oslo libraries for now it will be logging | 15:58 |
| szaher | that is it for me, fixing bugs and this blueprint :) | 15:59 |
| szaher | thanks m3m0 | 15:59 |
| m3m0 | nice, thanks a lot szhare | 16:00 |
| m3m0 | do you have anything more to say | 16:00 |
| m3m0 | #endmeeting | 16:00 |
| freezerBot` | Meeting ended Thu Oct 8 16:00:43 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:00 |
| freezerBot` | Minutes: http://meetbot.stefanocanepa.it/freezer/openstack-freezer/2015/openstack-freezer.2015-10-08-15.01.html | 16:00 |
| freezerBot` | Minutes (text): http://meetbot.stefanocanepa.it/freezer/openstack-freezer/2015/openstack-freezer.2015-10-08-15.01.txt | 16:00 |
| freezerBot` | Log: http://meetbot.stefanocanepa.it/freezer/openstack-freezer/2015/openstack-freezer.2015-10-08-15.01.log.html | 16:00 |
| openstack | Meeting ended Thu Oct 8 16:00:43 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:00 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/thu_08__10/2015/thu_08__10.2015-10-08-15.01.html | 16:00 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/thu_08__10/2015/thu_08__10.2015-10-08-15.01.txt | 16:00 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/thu_08__10/2015/thu_08__10.2015-10-08-15.01.log.html | 16:00 |
| marzif | m3m0, sorry I didn't see your questions | 16:06 |
| marzif | :( | 16:06 |
| marzif | it will be for admin and normal users | 16:08 |
| *** marzif has quit IRC | 16:08 | |
| *** marzif has joined #openstack-freezer | 16:08 | |
| marzif | so we can manage infrastructure nodes from the admin, and backup as a service from the user panel | 16:09 |
| marzif | also the disaster recovery can be helpful from the admin | 16:09 |
| marzif | it's good question we need to understand what make sense for admin and what not | 16:09 |
| marzif | I think for now it's worth to have it in both places | 16:09 |
| marzif | anyone can review this https://review.openstack.org/#/c/231469/ | 16:28 |
| *** reldan has quit IRC | 17:03 | |
| *** reldan has joined #openstack-freezer | 17:22 | |
| *** subscope has joined #openstack-freezer | 17:25 | |
| *** marzif has quit IRC | 17:35 | |
| *** reldan has quit IRC | 18:17 | |
| *** reldan has joined #openstack-freezer | 18:26 | |
| *** ig0r_ has joined #openstack-freezer | 20:58 | |
| *** ig0r_ has quit IRC | 21:03 | |
| *** ig0r_ has joined #openstack-freezer | 21:05 | |
| *** ig0r_ has quit IRC | 21:10 | |
| *** m3m0 has quit IRC | 23:07 | |
| *** m3m0 has joined #openstack-freezer | 23:10 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!