17:00:50 <felipemonteiro> #startmeeting murano
17:00:51 <openstack> Meeting started Tue Mar 28 17:00:50 2017 UTC and is due to finish in 60 minutes.  The chair is felipemonteiro. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:52 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:55 <openstack> The meeting name has been set to 'murano'
17:00:56 <felipemonteiro> #topic Roll Call
17:01:03 <tovin07> hi felipemonteiro
17:01:07 <felipemonteiro> o/
17:01:13 <felipemonteiro> Hey tovin07
17:02:42 <pbourke_> o/
17:04:25 <felipemonteiro> I saw your commit for osprofiler. I haven't diagnosed the failing tests in murano (i.e. for tempest and murano-ci) to see if they're all related to your change.
17:05:22 <felipemonteiro> I do know, however, that there are a bunch of failing tests in murano dashboard that I'm going to have to fix, in part related to bad waiters, in part related to Horizon changes, and in part related to Glance changes.
17:07:50 <felipemonteiro> Hi pbourke_
17:08:00 <pbourke_> hi felipemonteiro
17:08:21 <pbourke_> just on a call for a few mins but i have one or two questions for you if you're free then :)
17:08:31 <felipemonteiro> Sure.
17:09:23 <felipemonteiro> #topic Open Discussion
17:11:03 <tovin07> I have a patch
17:11:23 <tovin07> About integrate OSprofiler into Murano
17:11:24 <tovin07> https://review.openstack.org/#/c/446316/
17:11:43 <tovin07> #link Integrate OSprofiler into Murano https://review.openstack.org/#/c/446316/
17:12:34 <tovin07> gate-tempest-dsvm-murano-api-ubuntu-xenial	FAILED with all test_cinder_volumes tests
17:13:20 <felipemonteiro> tovin07: Yes, I saw it. I saw the failures there as well.
17:13:47 <felipemonteiro> Either they're related to the changes in the patch, or have been introduced by Cinder changes in the last 10 days from what I can tell.
17:14:09 <tovin07> felipemonteiro: thank you
17:14:57 <tovin07> currently, I still have no idea why these tests fail
17:15:59 <felipemonteiro> Because there hasn't been a lot of recent commit activity in Murano, these bugs have all of a sudden appeared, as it were. I do know that there are legitimate test failures in murano dashboard. I'd need another hour or two to see what the issue is with murano.
17:16:42 <tovin07> oh, no problem
17:17:02 <tovin07> I will try some other ways to find out why
17:19:13 <felipemonteiro> tovin07: I'm rechecking #link https://review.openstack.org/#/c/441611/ which is effectively a noop (just api docs). If that passes, then it's your patch; if it also fails, then it's a greater problem.
17:20:23 <tovin07> Yes, I rather think that it’s my patch
17:21:09 <pbourke_> felipemonteiro: so, one question was, i noticed it's possible to create murano apps using heat templates directly
17:21:28 <pbourke_> felipemonteiro: is there any major advantage to using MuranoPL that people miss if creating apps that way?
17:24:39 <felipemonteiro> You'd lose murano dashboard integration, which is a big disadvantage for one
17:25:18 <pbourke_> oh, that sucks :(
17:25:34 <pbourke_> I somehow thought you could still get the dashboard if using it that way
17:26:47 <pbourke_> second question, it seems its not possible to create+attach volumes in MuranoPL currently
17:26:56 <pbourke_> am I correct in that?
17:27:58 <felipemonteiro> You need a ui yaml file in order to tell the dashboard how to dynamically create fields in order to populate the template with the right information
17:28:24 <pbourke_> ah that's right
17:28:47 <felipemonteiro> pbourke_: Not sure about the second question, something I've yet to try
17:28:51 <pbourke_> so you can use those + HOT to essentially get the same functionality
17:29:06 <pbourke_> ?
17:31:50 <felipemonteiro> Murano is a higher level of abstraction built on top of Heat. Murano can basically work with different deployment engines in principle. It could use Kubernetes as well as Heat.
17:32:05 <felipemonteiro> It depends what your needs are.
17:33:23 <pbourke_> makes sense, thanks felipemonteiro
17:36:21 <felipemonteiro> What exactly are you trying to do with Heat? Heat is mostly intended to orchestrate infrastructure creation and deployment, whereas Murano is intended to deploy complex applications within the infrastructure created by Heat.
17:37:20 <pbourke_> i haven't come across an example of a murano application that couldn't be done directly with heat
17:38:30 <pbourke_> or I should say, do you have an example?
17:38:30 <felipemonteiro> pbourke_: That's a legitimate concern. I'm not invested in Heat, so I don't want to unfairly compare the two projects.
17:39:37 <pbourke_> i think murano is a useful abstraction, what im really trying to do though is avoid having to create wrappers in MuranoPL for all the functionality that you get for free when using Heat directly
17:39:46 <pbourke_> as I'm finding MuranoPL cumbersome to write
17:40:03 <pbourke_> the cinder volumes are one such example
17:42:13 <felipemonteiro> If you have very nuanced questions regarding that, I'd reach out to Stan Lagun, who's the most experienced person that I know when it comes to MuranoPL.
17:55:49 <felipemonteiro> Anyone have anything else to discuss, otherwise we can end a bit early?
17:57:26 <pbourke_> im good, thanks again felipemonteiro
17:58:27 <felipemonteiro> pbourke_: Thanks for showing up :)
17:58:36 <felipemonteiro> #endmeeting