17:01:01 <katyafervent__> #startmeeting murano
17:01:02 <openstack> Meeting started Tue Jul  1 17:01:01 2014 UTC and is due to finish in 60 minutes.  The chair is katyafervent__. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:01:03 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:01:05 <openstack> The meeting name has been set to 'murano'
17:01:29 <katyafervent__> Hi Murano guys! Who is here?
17:01:37 <dteselkin> Hi :)
17:02:16 <dteselkin> Hmmm
17:02:32 <ativelkov> o/
17:02:33 <dteselkin> Can't believe there is nobody else
17:02:40 <katyafervent__> Let's wait for a couple minutes
17:02:42 <tsufiev> o/
17:04:11 <katyafervent__> We have no action items from the previous meeting
17:04:24 <katyafervent__> so let's go through the agenda
17:04:43 <katyafervent__> #topic horizon/dashboard/selenium tests research
17:05:15 <katyafervent__> That's on me and I realized it just now)
17:06:02 <katyafervent__> So let postpone it for the next week. We have plan to move our functional tests from murano ci to openstack Jenkins
17:06:54 <katyafervent__> #action Katya to provide an update on horizon/dashboard/selenium tests research
17:07:14 <katyafervent__> #topic Current state of Murano testing
17:07:25 <gokrokve> Hi. This is a short week in US. So a lot og guys just took PTO for the whole week.
17:07:39 <gokrokve> s/og/of
17:07:54 <katyafervent__> Ok. we do not have a lot of items in meeting agenda
17:08:17 <katyafervent__> so does anybody have something to say about unit test progress?
17:08:35 <tsufiev> katyafervent__, btw, I've starting to examine, how unit testing is done in openstack_dashboard
17:08:43 <stan_lagun> I have very good one. But nothing committed yet :)
17:08:44 <tsufiev> (today)
17:09:30 <katyafervent__> stan_lagun, tell us more about your powerful testing framework
17:09:32 <stan_lagun> Currently 63 tests with 84% coverage of dsl package
17:10:41 <stan_lagun> No that powerful. Just a set of helper classes that simplify building of Object Model and working with MuranoPL code like it was written in Python
17:10:47 <katyafervent__> tsufiev, ok let's cooperate on that tomorrow cause I also started to look)
17:11:24 <tsufiev> katyafervent__, sadly, it's a real mess :(
17:11:30 <katyafervent__> stan_lagun, so it would be easy to write tests while adding new classes to MuranoPL, right?
17:11:48 <tsufiev> i've spent about an hour (or more) trying to understand what's happening
17:12:28 <stan_lagun> Yes. It has special class loader that allows to combine Python Unit Tests with demo MuranoPL classes just for the test
17:12:29 <katyafervent__> tsufiev, that's sad
17:12:49 <tsufiev> katyafervent__, in 2 words: they mox everything except SUT (system under test)
17:12:57 <katyafervent__> stan_lagun, great!
17:13:56 <katyafervent__> #topic Current status of murano-ci
17:14:13 <tsufiev> katyafervent__, and this mox-ed things are spread into several classes, making them hard to grasp
17:14:18 <katyafervent__> tnurlygayanov, are you here? do have an update on murano-ci?
17:16:01 <katyafervent__> dteselkin, do you know about murano-ci update?
17:17:08 <dteselkin> Well, I know that we have some progress on moving CI but don't know what exactly  :(
17:17:27 <katyafervent__> As far as I know the update was made, but currently we don't know was it successful or not
17:17:54 <dteselkin> It's almost successful I would say
17:18:21 <katyafervent__> I believe so. All jobs finish without errors
17:18:41 <katyafervent__> #topic Current status of unit test coverage
17:19:17 <katyafervent__> stan_lagun, do you have percent of unit test coverage?
17:19:43 <stan_lagun> > Currently 63 tests with 84% coverage of dsl package
17:20:54 <katyafervent__> OK. Anything else?
17:21:47 <katyafervent__> #topic What can be improved?
17:22:37 <katyafervent__> We have in planes improving murano-dashboard testing
17:23:01 <katyafervent__> currently we have just one test unit for that module and that is very sad
17:23:35 <katyafervent__> the same goes for murano-client. I'm working on adding test for client shell
17:24:16 <tsufiev> kanzaros,  we could forbid commiting new fixes without tests :)
17:24:31 <tsufiev> oops
17:24:40 <tsufiev> katyafervent__, i meant to address you
17:24:53 <katyafervent__> tsufiev, we already have that rule!
17:25:18 <tsufiev> katyafervent__, weird... how did https://review.openstack.org/#/c/103502/ get approved :)?
17:25:47 <katyafervent__> in stackforge/murano that would never happen :)
17:26:37 <stan_lagun> No distributions at all found for yaql>=0.2.2,<0.3
17:26:45 <katyafervent__> tsufiev, what do you think, could we apply that rule for dashboard?
17:27:24 <stan_lagun> Do anyone know what happened to yaql?
17:27:39 <tsufiev> katyafervent__, given current amount of reviews in murano-dashboard, we could
17:27:55 <tsufiev> i mean, there not so many reviews there now
17:28:00 <katyafervent__> wrong chat) I guess it's something wrong with pypi
17:28:28 <stan_lagun> it is the reason why https://review.openstack.org/#/c/103502/ failed
17:28:37 <katyafervent__> #info Add tests for all changes in murano-dashboard
17:28:44 <stan_lagun> It was +1 from Jenkins when I clicked approved
17:29:27 <katyafervent__> stan_lagun, let's postpone that topic to open discussion
17:29:35 <katyafervent__> #topic Important bugs we need to fix
17:30:00 <katyafervent__> Are all important bugs in progress?
17:31:04 <katyafervent__> nobody knows
17:31:47 <katyafervent__> https://bugs.launchpad.net/murano <- knows
17:32:33 <katyafervent__> stan_lagun, please add all bugs that you found to the launchpad
17:32:49 <stan_lagun> sure
17:33:26 <katyafervent__> and we're waiting for sql cluster deployment
17:34:34 <katyafervent__> will we take Python muranoclient doesn't work with proxy that one?
17:36:42 <katyafervent__> #action "Python muranoclient doesn't work with proxy" need to be assigned
17:36:44 <katyafervent__> BTW
17:37:31 <katyafervent__> #info Bug triage will be held on the next Monday - the first Monday of a month
17:38:19 <katyafervent__> #action tnurlygayanov inform the community about bug scrub
17:39:11 <katyafervent__> Do you know other bugs that deserve our attention?
17:40:25 <tsufiev> katyafervent__, nope
17:40:35 <katyafervent__> #topic Open discussion
17:40:54 <katyafervent__> now we can discuss yaql and everything else
17:41:32 <tsufiev> speaking of bug https://review.openstack.org/#/c/99050/ ...
17:41:43 <tsufiev> I couldn't reproduce it on my machine
17:42:56 <tsufiev> katyafervent__, could you try to do it?
17:43:10 <katyafervent__> no, but I can
17:43:29 <katyafervent__> Actually, I noticed today that everything works faster
17:43:43 <katyafervent__> May be it connected with the horizon update
17:43:47 <tsufiev> katyafervent__, have you installed linux as host OS :)?
17:44:07 <katyafervent__> no :)
17:44:19 <tsufiev> katyafervent__, the datatables ajax refresh fix I was talking about hasn't yet landed in master
17:44:30 <tsufiev> so it must be some other changes...
17:45:38 <tsufiev> katyafervent__, so, if you're willing to give that bug a try, please take it https://bugs.launchpad.net/murano/+bug/1328512
17:45:39 <uvirtbot> Launchpad bug 1328512 in murano "Pressing "quick deploy" too quickly may cause an error" [High,In progress]
17:46:08 <tsufiev> hm, it's currently assigned to Brian
17:46:46 <btully> weird, it shouldn't be
17:46:48 <tsufiev> btully, did you encounter that bug on your machine?
17:47:01 <katyafervent__> #action katyafervent__ investigate https://bugs.launchpad.net/murano/+bug/1328512
17:47:03 <uvirtbot> Launchpad bug 1328512 in murano "Pressing "quick deploy" too quickly may cause an error" [High,In progress]
17:47:12 <tsufiev> btully, it's a standard gerrit - launchpad behaviour
17:47:13 <katyafervent__> btully, did you fix the commit message?
17:47:34 <tsufiev> once you send patchset to a commit with Closes-Bug reference, you're set as bug assignee
17:47:36 <katyafervent__> in that case bug owner changed in LP
17:47:55 <btully> i never encountered that bug on my machine, no
17:47:58 <katyafervent__> oh, true
17:48:25 <katyafervent__> commit message could be fixed on the web
17:48:26 <btully> i think i just added some visual indicators on top of the work you committed
17:48:47 <katyafervent__> well, that happens so move on
17:49:00 <tsufiev> ok, I think someone should reproduce it besides ativelkov, otherwise we should consider it invalid or won't fix
17:49:21 <btully> i think Steve wrote a comment that we shouldn't fix
17:50:04 <katyafervent__> any other topics?
17:51:07 <tsufiev> btully, true. i'll ping ativelkov about that issue, it was filed by him initially.
17:51:43 <tsufiev> katyafervent__, none that I know
17:51:48 <katyafervent__> ok, if we out of topics, let's have a dinner :)
17:52:11 <katyafervent__> Thanks everyone, see you next week
17:52:14 <tsufiev> katyafervent__, bon appetite :)
17:52:23 <IgorYozhikov> C u
17:52:23 <katyafervent__> #endmeeting