17:00:53 #startmeeting Murano 17:00:53 Meeting started Tue May 12 17:00:53 2015 UTC and is due to finish in 60 minutes. The chair is sergmelikyan. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:54 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:56 The meeting name has been set to 'murano' 17:01:09 Hi folks :) 17:01:11 o/ 17:01:20 * sergmelikyan feeling tension before the summit 17:01:30 hi 17:01:47 hi 17:02:26 hi 17:04:43 I left same agenda as for previous meeting, because Summit is on the next week, and I feel we have yet things to discuss. 17:05:18 As proven on previous meeting summit discussions may take whole meeting, so if you have topics to discuss please propose, and we will discuss them first. 17:05:50 I have 1n concern, that I wanted to leave untill open discussion =) 17:05:59 i just wanted to give heads up on what i've been doing with CLI tests for muranoclient 17:06:22 kzaitsev, naughty boy :) 17:06:33 #topic CLI Tests for Murano 17:06:37 all the CLI tests are going to be moved under python-muranoclient repo and will run as a separate job 17:07:12 running them will be easy: deploy your openstack, source openrc, run 'tox -e functional' 17:07:16 ruhe, previously we were running them against each commit to murano repo to ensure that they are working with change in API (if any), will it be possible? 17:07:23 s/openstack/devstack 17:07:59 sergmelikyan: yes, it's possible. let's get them working on muranoclient and then enable for commit to murano 17:08:41 excellent :) I remember times when API was in active development and client was always behind :) 17:08:57 ruhe, thank you for jumping on and fixing them! 17:09:14 They broke after we updated requirements to tempest_lib? 17:09:29 actually there were 3 problems :) 17:09:40 1. tempest_lib changed API for CLI tests 17:09:50 2. devstack no longer installs nose (which we rely on) 17:10:02 my patches migrate tests from nose to testr 17:10:22 3. in stable/kilo we had incorrect version in setup.cfg 17:10:32 for tempest_lib? 17:10:46 * sergmelikyan updated requirements right before release :( 17:10:54 no, this one https://github.com/openstack/murano/blob/master/setup.cfg#L18 17:11:06 requirements are ok 17:11:49 Ah... 17:11:49 somehow we managed to have incorrect version in murano-dashboard. AFAIK kzaitsev is working on that 17:12:51 i do not recall myself doing this patch, so i blame evil ghosts 17:12:58 Yep. I guess my commits to s/kilo would only pass after commit in murano is merged? 17:13:23 kzaitsev: correct. we need this one to land first https://review.openstack.org/#/c/182279/ 17:14:11 I see "# FIXME: see how it's done in saharaclient" is it going to be fixed in the next commit? 17:14:33 Oh. I can actually depend them on it, So that the tests should pass at the very least 17:14:45 sergmelikyan: we'll have to backport my patches to muranoclient 17:15:01 to get rid of that "FIXME" 17:15:38 one lesson i learned from all this 17:16:07 ruhe, I think we need to backport them despite stable/kilo is now supported release and we usually only critical fixes porting there 17:16:17 we should pay closer attention to what's going on in mailing list. Joe Gordon provided excellent instructions to move CLI tests to clients on Feb 13: http://lists.openstack.org/pipermail/openstack-dev/2015-February/056916.html 17:16:29 I vote for perfectly working CI on stable/* branches 17:16:39 :( 17:16:46 sergmelikyan: we will *have to* backport this changes 17:16:47 I've missed his e-mail... 17:17:35 I need to configure filter on tempest related e-mails - we heavily depend on devstack & tempest, and any change in tempest may break CI 17:17:45 ruhe, thank you! 17:18:00 well, sometimes we ignore those message because murano was in stackforge, but even if you're in stackforge and not "integrated" it's better to keep up with community 17:18:29 It's not usually ignorance, but the storm of e-mails each day... 17:19:08 yes, that too 17:19:43 Any other topics to discuss? 17:19:49 i think we covered this topic enough 17:19:52 So. With almous every core developer attending summit (except for katyafervent I suppose?) I would like to ask you guys to look at review.openstack.org every once in a while =)) Otherwise reviews would pile up =))) 17:20:17 kzaitsev: absolutely agree 17:21:08 +1 17:21:54 #topic Design Summit 17:22:32 I've updated our schedule with links to etherpads, please take a look: libertydesignsummit.sched.org/type/design+summit/Murano 17:23:31 We have pretty open schedule for Contributors Meet-up for now, but I think it will be quickly populated with items 17:23:54 Anything that you folks feel we should discuss there? 17:25:41 StanLagun, hi :) 17:25:59 sergmelikyan, hi!. Sorry fir being late 17:26:19 I have an idea to have a virtual mini-summit after the actual Liberty summit for contributors that are not able to joins us in the Vancouver 17:26:48 +many 17:26:54 I heard nice feedback about them from Glance team, that had that thing not so long ago 17:27:16 +1 17:28:13 I will start preparation right after the Vancouver, I think it should be somewhere in beginning of June, we can't delay to long 17:28:39 1-3 days, depending on number of topics that we would have to discuss 17:29:56 StanLagun, since you here, can you take a look at https://etherpad.openstack.org/p/murano-liberty-work-session-2 ? 17:30:11 What do you think we should also include there? 17:30:14 I'll be on vocation after Vancouver till 5th of June 17:30:37 StanLagun: ha! we'll design everything without you! ;) 17:30:42 #info Stan is going to be on vacation till 5th of June 17:31:18 #info mini-design summit will be held in the beginning of the June 17:31:39 sergmelikyan, where? 17:31:50 StanLagun, you mean which tool? 17:32:31 sergmelikyan, I thought it is going to be IRL 17:33:29 I think we can add agent authentication to the https://etherpad.openstack.org/p/murano-liberty-work-session-2 17:33:31 StanLagun, most probably no - it's hard to gather people from around the globe in the same place, and if people missed summit in Vancouver, most probably they will not be able to attend mini design Summit 17:34:13 I remember we had plans to hold it in Poland 17:34:21 StanLagun, do you think we should mix to topics? Each session is 40m, I'm afraid that we will not have time to cover both of them 17:34:31 *s/to/two 17:35:07 StanLagun, let's include agent authentication here: https://etherpad.openstack.org/p/murano-liberty-contributors-meetup 17:35:45 sergmelikyan, I thing that agent is more important topic and might be more interesting for audience as it is a good topic for collaboration and cross-project activity 17:37:08 StanLagun, do you think we should swap work-session #2 with discussion about agent authentication? 17:37:39 sergmelikyan, I'd say it is a good idea 17:38:18 we can vote 17:38:55 fwiw i don't strong preferences about order of sessions 17:39:26 Discussions on work-session are limited by time, and may have up to 50 participats 17:39:50 contributors meetup will be limited by 10 people at max 17:40:31 btw may I add problem #3 to the murano-liberty-work-session-1 ? 17:40:35 So topic that require more input from audience is preferred choice for discussing on work session 17:40:52 StanLagun, sure, if it's related to the topic of the session 17:41:33 StanLagun, do you feel that we will implement agent authentication in Liberty and it's need to be discussed? 17:42:07 sergmelikyan, I'd say this is the first thing we need to implement. This is a must 17:42:17 I feel that it will be more interesting topics for work-session, but I am not sure that it will not be wasted if we are not going to work on agent authentication 17:42:53 there is ongoing discussing on this in ML 17:42:55 #startvote Should we discuss agent authentication on the work-session #2? Yes, No 17:42:55 Begin voting on: Should we discuss agent authentication on the work-session #2? Valid vote options are Yes, No. 17:42:56 Vote using '#vote OPTION'. Only your last vote counts. 17:43:13 #vote yes 17:43:36 #vote yes 17:44:21 #vote yes 17:44:34 #vote yes 17:45:14 #vote yes 17:45:17 #endvote 17:45:18 Voted on "Should we discuss agent authentication on the work-session #2?" Results are 17:45:19 Yes (5): freerunner, aderyugin, StanLagun, DmytroDovbii, sergmelikyan 17:45:50 StanLagun, can you update etherpad accordingly, and move previous topic to contributors meetup? 17:46:45 sergmelikyan, I'll do it 17:47:06 #action StanLagun update etherpad for work-session #2 17:47:56 StanLagun, I will send them to ML once you will update etherpad 17:48:09 Moving to Open Discussion? 17:49:15 #topic Open Discussion 17:50:08 We will not have a meeting on the next week due to OpenStack Summit :) I will update our agenda for the next meeting :) 17:50:44 on a related note "Bayern Munich vs Barcelona" starts in less than an hour, so i'd prefer to close the meeting as early as possible :) 17:51:33 ruhe, you need a hour to prepare? :) 17:52:57 StanLagun, beer and other stuff need to be bought? 17:53:08 #endmeeting