17:00:08 #startmeeting murano 17:00:09 Meeting started Tue Aug 25 17:00:08 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:11 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:13 The meeting name has been set to 'murano' 17:00:17 o/ 17:00:30 o/ 17:01:01 o/ 17:01:24 Hi 17:01:34 Hi 17:01:35 Agenda for today's meeting can be found here: https://wiki.openstack.org/wiki/Meetings/MuranoAgenda 17:01:42 hi 17:02:45 #link https://wiki.openstack.org/wiki/Meetings/MuranoAgenda/Archive/2015-08-25/ 17:04:38 #topic Action Items Review 17:04:52 #1 fix yaql legacy mode and release yaql rc3 after successful deployment 17:05:09 I believe it's done :) We even have 1.0.0 release ready :) 17:05:31 #2 kzaitsev_mb sum-up the UX concerns about the public/non-public packages on Package Definitions in ML 17:06:10 sergmelikyan: yep, done. I believe we even have a commit, that fixes the ux issues 17:06:37 kzaitsev_mb: link? 17:06:46 #link https://review.openstack.org/#/c/216720/ 17:06:49 was looking up =) 17:07:02 hm 17:07:07 and haven't reviewed it 17:07:19 it actually doesn't do what we agreed to do 17:07:29 I thought we agreed to remove the filter completely.. 17:07:41 kzaitsev_mb: and looks like commit needs to be rebased 17:08:46 sergmelikyan: everything needs to be rebased right now =) 17:08:54 kzaitsev_mb: I would appreciate your feedback on this commit 17:08:59 kzaitsev_mb: yaql? 17:09:20 I mean, have you seen the queue? 17:09:36 not yet :) It's morning here :) 17:09:40 we have like a dozen of patches red, that should turn green, since yaql landed 17:09:53 I caught a cold on a weekend, so was sleeping until hour ago :( 17:10:21 fever and sore throat... I hate it %) 17:10:35 bummer 17:10:46 get well soon =) 17:10:51 kzaitsev_mb: thx :) 17:11:17 I bought a ton of different stuff for cold, let's how it's working :) 17:11:27 #3 verify that https://review.openstack.org/#/c/211608/ don't break anything then produce next steps with UI 17:11:48 I don't see reviews on latest patch-sets... 17:12:22 and it also need to be rebased to new engine code 17:12:23 katyafervent & kzaitsev_mb have folks checked this commit? 17:13:01 StanLagun: I propose to discuss next steps regarding yaql that we need to take after commits were landed 17:13:24 sergmelikyan: hmmm, I think I haven't will look into it sooner this week 17:13:54 mm? 17:14:01 * sergmelikyan didn't get the sentence 17:14:38 sergmelikyan: this is not about yaql. It is just that environment support is in merge conflict 17:15:47 I mean I haven't looked into the patch, but will do this week 17:16:34 kzaitsev_mb: thx! 17:16:47 #topic Migrating to yaql 1.0 status 17:16:58 StanLagun: so where we are regarding yaql? 17:17:56 is it logging api? i think we need unit tests for that 17:18:09 katyafervent2: mmm? 17:18:13 yaql 1.0.0 has been released, new python-muranoclient as well. New engine with yaql 1.0 was landed today. Dashboar support for 1.0 is waiting in zuul queue for dwsm job to become green 17:18:18 * sergmelikyan feels stupid 17:18:51 there might be some regressions. One known regression is that congress dwsm job is red. The fixxing commit is also waiting in zuul 17:19:11 just commit to the dashboard left to merge 17:19:13 i've updated it today 17:19:33 so we can finally remove this item from our weekly meetings! =) 17:19:43 dashboard is stack in zuul for 2 hours already 17:20:36 *stuck* 17:21:00 And we should retrigger all the things! ) 17:21:11 StanLagun: it's just waiting it's turn to be checked or something is wrong? 17:21:17 kzaitsev_mb: lol :) 17:21:44 as for now 4/5 jobs are green one in queued 17:23:01 let's move to the next topic? 17:23:07 #topic Artifact (glance v3) transition status update 17:23:50 sorry, my internet is slow 17:24:22 since ativelkov is not here, Serg, can you maybe tell us few words about the procedure of migrating towards artifacts? 17:24:52 From what I know — 1) we're going to copy-paste some of v3 client functionality into muranoclient 17:25:14 kzaitsev_mb: I believe latest update on the mailing list, we agreed to develop new glance client functionality in future branch and copy to murano client for now 17:26:09 support for Artifact Repository should be considered experimental for Liberty 17:28:40 #topic Add support for heat environments status 17:29:08 #link https://review.openstack.org/#/c/211608/ 17:29:12 mgershen: I see that we need to wait until commit is going to be re-checked :) 17:29:56 yes, but from what I hear here, I am optimistic :) 17:30:26 StanLagun: You need to check out this commit :) Looks good for me, but I may be missing something :) 17:30:28 also there were good feedbacks, even with jenkins and murano-ci giving -1 17:30:33 mgershen: please rebase it first 17:30:38 mgershen: yep, new engine forze almoust everything for a couple of days, but since it landed we're going to review the patches faster, hopefully +) 17:31:02 StanLagun: OK I will 17:31:15 yeah, ping us in irc if needed 17:31:26 kzaitsev_mb: +1 for that :) 17:32:02 katyafervent2: you are so kind, I will 17:32:47 I think we should be able to close it by the feature freeze 17:33:11 I believe so 17:34:15 I have no more updates :) 17:34:29 #topic Open Mitaka spec branch? (kzaitsev_mb) 17:35:29 I think we can create folder for Mitaka specs in murano-specs 17:35:42 isn't it too early? 17:35:45 I think we have a couple of specs and/or bps that we're definitelly not going to land in L 17:35:55 I'm a little bit out of dates :( 17:36:03 Nikolay_St: I would say it's kinda late 17:36:26 so opening M specs looks like a nice idea, to continue that work 17:36:34 i have one spec for M 17:36:41 see! =) 17:36:50 kzaitsev_mb: go ahead and create folder for Mitaka in murano-specs :) 17:36:57 we can start contributing early =) 17:36:59 i can do the commit tommorow 17:37:02 and feature freeze is next week, so +1 17:37:17 #agreed open M spec folder 17:37:21 will do =) 17:37:25 by the way will there be a spec freeze in M? 17:38:21 mgershen: we didn't yet introduced spec freeze for our project 17:38:48 OK, so never mind 17:38:55 mgershen: Well, if we start early — we might actually have all the specs in place in time =) 17:41:08 #topic Open Discussion 17:42:28 sergmelikyan: Thanks. I just wanted to thank those who reviewed the latest tosca support spec (https://review.openstack.org/#/c/194422) and kindly ask for a few more reviews so we can finalize it and start coding asap :) 17:44:29 vahidh: not merged spec technically doesn't block from coding, though I agree - this spec requires more reviews given a lot's of comments from StanLagun previously 17:44:58 vahidh, you can start coding already) 17:44:58 i think there will be no more major comments 17:45:41 sure, I just wanted to make sure Stan has no major disagreement with what's in there 17:48:11 StanLagun: can you take a look? 17:48:36 vahidh: I haven't reviewed last spec version. Sorry. Though I don't expect any issues since we have agreed already 17:49:40 StanLagun: we spent some time with vahidh few weeks ago going through spec, it would be awesome if you would take a look. 17:49:44 1 week to HCF is a tough time :) HCF is coming... (c) :) 17:49:56 :D 17:49:56 StanLagun: great. I'll move on with learning the code and taking on the action items. thanks :) 17:50:33 since it is not going to land in L can we postpone it until HCF? 17:51:07 I mean the implementation is not ready 17:51:23 we can merge spec for M 17:51:47 StanLagun: sure, but since my boss is pushing for it, I'll start with the coding and wait for your review when you get a chance 17:53:34 promise to review everything on the gerrit. Just lets leave things that doesn't have to land before HCF until HCF happens. Which is just one week away 17:54:30 great, thank you. I understand. 17:56:31 #endmeeting