17:04:18 <kzaitsev_mb> #startmeeting murano
17:04:19 <openstack> Meeting started Tue Jan 10 17:04:18 2017 UTC and is due to finish in 60 minutes.  The chair is kzaitsev_mb. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:04:20 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:04:22 <openstack> The meeting name has been set to 'murano'
17:04:28 <kzaitsev_mb> oops =) missed the thing by 4 mins =)
17:04:33 <kzaitsev_mb> #topic rollcal
17:04:34 <kzaitsev_mb> o/
17:04:41 <antananarivo> \o/
17:04:47 <learnmore_> o/
17:04:57 <sergmelikyan> o/
17:05:18 <antananarivo> sorry folks, have no idea how to rename my login in this client back to `osh` (:
17:05:36 <kzaitsev_mb> antananarivo: lol )
17:06:02 <kzaitsev_mb> thought you're somewhere from madagaskar ;)
17:06:50 <learnmore_> Any topics for discussion?
17:07:12 <antananarivo> well, publicity of my IP doesn't let me to do such trick :D
17:07:47 <antananarivo> + to learnmore_, want to know some hot news in murano-life!
17:08:05 <kzaitsev_mb> learnmore_: not much, nobody added anything to agenda
17:08:07 <kzaitsev_mb> #link https://wiki.openstack.org/wiki/Meetings/MuranoAgenda
17:08:09 <kzaitsev_mb> so
17:08:15 <kzaitsev_mb> #topic Open Discussion
17:08:38 <kzaitsev_mb> sergmelikyan: saw your letter and your commit. about the licensing issues
17:08:43 <kzaitsev_mb> thanks a lot =)
17:09:01 <kzaitsev_mb> actually wanted to get the thing done today, but your beat me to it
17:09:02 <sergmelikyan> np, was actually super easy to do - took me a 10m... just was so hard to start :)
17:09:12 <learnmore_> what is murano-life??
17:09:24 <kzaitsev_mb> murano-life?
17:10:03 <learnmore_> Anyways, I do have a topic for discussion.  I have a problem with device names in Murano.  I know there is a device name field in for volumes but it is not what I really need.
17:10:54 <learnmore_> That device name is only for Murano's use and not what the actual device name will be once an instance is created and the volumes are attached.
17:11:18 <sergmelikyan> murano life is like thug-life :)
17:11:33 * sergmelikyan puts his black glasses
17:12:02 <kzaitsev_mb> I heard you liked yaql, so I put yaql into yaql, so you can yaql while you yaql =)
17:12:14 <sergmelikyan> learnmore_: this is common for many other resources too - I guess related to uniqness of the names in the cloud
17:12:22 <kzaitsev_mb> learnmore_: let's take a look at how Volumes are used then )
17:12:44 <learnmore_> When the instance is created, I can see this from the nova view in horizon:  murano-inyjxixrq43971-vol-d69b26c7-f901-4a67-b018-4f0fd1a35273-i43syflrb5mt on /dev/xvda
17:12:47 <kzaitsev_mb> learnmore_: although I still don't get what you want to do =)
17:13:04 <learnmore_> So my app needs to get the device name, /dev/xvda.
17:14:33 <learnmore_> Ok.  Do you want me to describe why my murano db app needs these names?  There are several reasons.
17:15:09 <kzaitsev_mb> learnmore_: nope =) I didn't understand what you want in the first place
17:15:30 <kzaitsev_mb> you want to be able to set device-name for volumes?
17:15:59 <learnmore_> No, I don't want to set these names.  I want to be able to get them once the instance is created.
17:16:35 <kzaitsev_mb> learnmore_: if it's available from the heat template — you should be able to get it in your app too
17:16:36 <learnmore_> Say, in my ui.yaml file, I create 3 volumes.  Once the instance is created, I want to know the device names of all 3 volumes.
17:19:02 <learnmore_> I know that the boot volume will always be /dev/xvda.  The other 2 volumes will contain the database and swap space.
17:19:02 <felipemonteiro> kzaitsev_mb: Hi, is there still a need for "Improve log browsing for deployments" wishlist bug? I started working on it, but had a few questions.
17:20:17 <learnmore_> But I can't figure out how to get the info from Murano to see if the database volume is named /dev/xvdb or /dev/xvdc.
17:20:32 <kzaitsev_mb> felipemonteiro: well it's always better to not have any bugs ;)
17:21:32 <kzaitsev_mb> learnmore_: is the mountpoint property what you're looking for?
17:22:05 <felipemonteiro> kzaitsev_mb: It's not really a "bug" per se. It's just a new murano dashboard view for showing all the deployments across the environments for a tenant. Right now you can only see deployments for each environment, so you have to do a lot of clicking to see all the deployments.
17:22:53 <kzaitsev_mb> #link https://github.com/openstack/murano/blob/master/meta/io.murano/Classes/resources/Volume.yaml#L55
17:23:26 <StanLagun> learnmore_: Except for the boot devices, the device name is a part of the input. In other words you provide it
17:25:02 <jose-phillips> hey well sorry im getting late to the meeting i have a point i want to discuss.
17:25:15 <kzaitsev_mb> StanLagun: and which property holds it? )
17:25:46 <kzaitsev_mb> felipemonteiro: ah. yeah. sounds more like an enhancement
17:26:06 <learnmore_> Perhaps, mountpoint.  I'll take a closer look.
17:26:08 <kzaitsev_mb> felipemonteiro: well if it's smth you need — I don't think anyone will be against it being implemented )
17:26:31 <StanLagun> kzaitsev_mb: https://github.com/openstack/murano/blob/master/meta/io.murano/Classes/resources/Instance.yaml#L73
17:26:41 <StanLagun> the keys are the mountpoints
17:26:46 <learnmore_> StanLagun:  the device name you are referring to is for murano only.  It is not the actual device name on the instance.
17:27:44 <StanLagun> learnmore_: there is nothing for murano only there. All of the data is put into the Heat template. Murano doesn't have any names for its own
17:28:42 <felipemonteiro> kzaitsev_mb: Someone else created that enhancement about a year ago: https://bugs.launchpad.net/murano/+bug/1497261 But I just had 2 questions: 1) Is it necessary to create a new API call -- /deployments which gets all deployments...or is it better to fire off multiple API calls, i.e. foreach env: get deployments(). 2) If it is necessary to create new API, is it useful to expose it in the muranoclient CLI?
17:28:42 <openstack> Launchpad bug 1497261 in Murano "Improve log browsing for deployments" [Wishlist,In progress] - Assigned to Felipe Monteiro (fm577c)
17:28:42 <StanLagun> it is just that we have two types of volumes - volume attachments and boot devices
17:30:34 <StanLagun> for boot devices the name can be provided in https://github.com/openstack/murano/blob/master/meta/io.murano/Classes/resources/Instance.yaml#L77, however it is optional and if not provided it will be generated automatically down the stack. We have no output property to retrieve it. However AFAIK it is always predictable
17:31:02 <learnmore_> StanLagun:  What is the difference between volumes and boot devices?  Perhaps that is my problem.  I have created my volumes as boot devices.  When only 1 is a bootable device.
17:31:53 <learnmore_> StanLagun:  If I create my database volume under volumes, that might solve my problem.  I'll try that.
17:33:26 <kzaitsev_mb> felipemonteiro: let me see what API endpoint for deployments we have right now )
17:33:27 <StanLagun> learnmore_: I hardly understand it by myself. boot devices generate http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Nova::Server-prop-block_device_mapping_v2, volumes generate VolumeAttachment resources
17:34:31 <StanLagun> learnmore_: block devices are used for boot devices or to add a CD-ROM drive
17:34:40 <learnmore_> StanLagun_:  Thanks :)
17:35:07 <StanLagun> I guess you need to check it with cinder guys
17:35:36 <kzaitsev_mb> felipemonteiro: yeah, looks like a new api endpoint is required if you want to expose all the deployments of all the envs. this should be policy-controlled and admin-only be default (i.e. there's no reason we should allow user1 see user2's deployments, there might be sensible info there)
17:36:13 <learnmore_> StanLagun:  In my blockDevice list, I do use  a deviceName of foo for one of the volumes just to see what would happen.  No error, the deploy works fine, but of course, there is no device named foo.
17:36:55 <learnmore_> StanLagun_:  That is why I thought that the device name was only for Murano's use.
17:37:18 <StanLagun> according to the Heat documentation: A device name where the volume will be attached in the system at /dev/device_name. This value is typically vda.
17:37:30 <kzaitsev_mb> jose-phillips: thought you had smth to ask? =)
17:37:43 <felipemonteiro> kzaitsev_mb: Ok, thanks. I can create a blueprint for it if necessary. Otherwise I will just push code up.
17:37:45 <StanLagun> it should be vd-something. Otherwise cinder will ignore it
17:38:54 <learnmore_> StanLagun_:  Ok.  I guess I have more testing to do.
17:39:33 <kzaitsev_mb> felipemonteiro: a bp would be nice to have all the things tracked nicely and correctly in git/gerrit =)
17:41:00 <felipemonteiro> kzaitsev_mb. Np, will do. Do you know if Murano will be at the Atlanta PTG? Latest details I see doesn't have Murano meetings scheduled.
17:41:14 <learnmore_> On a different topic, the dynamic UI where the ui.yaml file goes away.  Some work has been done on this and I assume it has been checked in.  Yes?
17:41:51 <StanLagun> felipemonteiro: Kirill and myself are going to be in Atlanta for the Murano
17:42:19 <kzaitsev_mb> yeah that was smth I wanted to discuss +)
17:42:26 <kzaitsev_mb> you guys going to PTG? =)
17:43:02 <kzaitsev_mb> I know we do not have a separate room (that is intentional), but we're still going to the ptg )
17:43:11 <kzaitsev_mb> StanLagun: btw, hae you bought a ticket?
17:43:36 <felipemonteiro> StanLagun: I have to be able to tell my supervisor that Murano will be there...or else I probably can't go =( I looked at the schedule on openstack.org/ptg and it basically shows which teams will be there which days. Murano isn't listed.
17:43:45 <kzaitsev_mb> #link https://www.eventbrite.com/e/project-teams-gathering-tickets-27549298694
17:44:13 <StanLagun> kzaitsev_mb: yes
17:44:15 <kzaitsev_mb> there's like 146 available or so. so if you guys haven't bought one — you'd better hurry =)
17:45:21 <learnmore_> What discussion on Murano will take place at this PTG?
17:45:22 <kzaitsev_mb> felipemonteiro: Murano haven't booked a room, because there would not be that much to discuss for a whole room a whole day, but we'll be there =)
17:45:41 <kzaitsev_mb> if you want — I (as current PTL) can write you some formal letter ;)
17:46:48 <kzaitsev_mb> learnmore_: don't know at this moment tbh =) it's still more than a month away. Even for Atlanta I haven't had plans that early )
17:47:30 <felipemonteiro> kzaitsev_mb: They did, but they want to prioritize who goes based on which teams will be there, who is core, stuff like that. I appreciate that...I just need to talk to my supervisor first.
17:48:25 <StanLagun> learnmore_: ui.yamls are not gone. The only thing that was added is an API call to generate JSON-schema from the MuranoPL class which can be used instead of UI.yaml
17:49:59 <kzaitsev_mb> felipemonteiro: ping me if you'll need some/any explanations or some letter or smth. I'm planning to spend a bunch of time with the App Catalog session and honestly I feel that it would be a good place to meet anyone interested in murano
17:50:00 <learnmore_> StanLagun_:  So basically Murano supports both the ui.yaml and the generated JSON-schema based on the class file.  Yes?
17:50:43 <StanLagun> yes
17:50:49 <felipemonteiro> kzaitsev_mb: Thanks again! I'll use these logs as a starting point lol.
17:51:36 <kzaitsev_mb> felipemonteiro: also think about securing a ticket asap =) they might run out, there's only 146 left
17:51:42 <learnmore_> StanLagun_:  Does the CLI use this new API?  I assume horizon does not.  Just wondering if the CLI does.
17:51:49 <StanLagun> learnmore_: but murano-dashboard doesn't make any use of the JSON-schema API
17:54:06 <StanLagun> learnmore_: there is a CLI for that
17:55:23 <StanLagun> https://review.openstack.org/#/c/334651/
17:56:11 <learnmore_> StanLagun_:  Perfect.  Now I can play with it :)
17:56:52 <StanLagun> also please check https://github.com/openstack/murano/blob/master/murano/tests/unit/dsl/test_schema_generation.py
17:57:16 <StanLagun> and https://github.com/openstack/murano/blob/master/murano/tests/unit/dsl/meta/TestSchema.yaml
17:57:54 <learnmore_> StanLagun_:  Thanks .  Appreciate the info.
17:59:20 <kzaitsev_mb> we're almost out of time
17:59:28 <kzaitsev_mb> thanks everyone for participating
18:00:08 <kzaitsev_mb> see you in #murano =) also I've restored all my scripts, so I'll be able to respond real fast ))
18:00:23 <kzaitsev_mb> thanks for participating again!
18:00:28 <kzaitsev_mb> #endmeeting