| *** btully has quit IRC | 00:02 | |
| *** gyee has quit IRC | 01:35 | |
| *** yaawang has quit IRC | 01:42 | |
| *** yaawang has joined #openstack-horizon | 01:43 | |
| *** btully has joined #openstack-horizon | 01:47 | |
| *** btully has quit IRC | 01:52 | |
| *** yaawang has quit IRC | 02:45 | |
| *** yaawang has joined #openstack-horizon | 02:46 | |
| openstackgerrit | Akihiro Motoki proposed openstack/horizon master: Define periodic jobs https://review.opendev.org/737686 | 03:27 |
|---|---|---|
| openstackgerrit | Akihiro Motoki proposed openstack/horizon master: Add plugin cross jobs https://review.opendev.org/737891 | 03:29 |
| openstackgerrit | Merged openstack/horizon stable/stein: Fix horizon-nodejs jobs https://review.opendev.org/737577 | 04:06 |
| *** mugsie has quit IRC | 04:53 | |
| *** mugsie has joined #openstack-horizon | 04:57 | |
| *** vishalmanchanda has joined #openstack-horizon | 05:23 | |
| *** btully has joined #openstack-horizon | 05:25 | |
| *** btully has quit IRC | 05:29 | |
| *** yaawang has quit IRC | 05:45 | |
| *** yaawang has joined #openstack-horizon | 05:45 | |
| *** yaawang has quit IRC | 06:43 | |
| *** yaawang has joined #openstack-horizon | 06:51 | |
| *** yaawang has quit IRC | 06:55 | |
| *** yaawang has joined #openstack-horizon | 06:56 | |
| *** rcernin has quit IRC | 07:02 | |
| *** rcernin has joined #openstack-horizon | 07:04 | |
| *** btully has joined #openstack-horizon | 07:13 | |
| openstackgerrit | Martin Gerhard Loschwitz proposed openstack/horizon master: Set type for volumes from snapshots and volumes https://review.opendev.org/738308 | 07:16 |
| *** btully has quit IRC | 07:18 | |
| *** rcernin has quit IRC | 07:30 | |
| *** jtomasek has quit IRC | 07:36 | |
| *** tosky has joined #openstack-horizon | 07:40 | |
| *** jtomasek has joined #openstack-horizon | 07:40 | |
| *** rcernin has joined #openstack-horizon | 07:49 | |
| *** e0ne has joined #openstack-horizon | 07:58 | |
| *** ChanServ sets mode: +o e0ne | 07:58 | |
| *** rcernin has quit IRC | 08:06 | |
| *** rdopiera has joined #openstack-horizon | 08:09 | |
| *** kevko has joined #openstack-horizon | 08:35 | |
| *** yaawang has quit IRC | 08:46 | |
| *** yaawang has joined #openstack-horizon | 08:47 | |
| openstackgerrit | Martin Gerhard Loschwitz proposed openstack/horizon master: Set type for volumes from snapshots and volumes https://review.opendev.org/738308 | 08:47 |
| *** jtomasek_ has joined #openstack-horizon | 09:05 | |
| *** jtomasek has quit IRC | 09:07 | |
| *** yaawang has quit IRC | 09:30 | |
| *** yaawang has joined #openstack-horizon | 09:31 | |
| *** tkajinam has quit IRC | 09:59 | |
| openstackgerrit | Martin Gerhard Loschwitz proposed openstack/horizon master: Set type for volumes from snapshots and volumes https://review.opendev.org/738308 | 10:46 |
| *** btully has joined #openstack-horizon | 10:51 | |
| *** btully has quit IRC | 10:56 | |
| *** priteau has joined #openstack-horizon | 11:02 | |
| vishalmanchanda | amotoki: hi around? | 12:01 |
| amotoki | vishalmanchanda: hi | 12:03 |
| vishalmanchanda | amotoki: I want to discuss the UI for this patch https://review.opendev.org/#/c/734161/ | 12:05 |
| vishalmanchanda | amotoki: I have replied on your comments. Could you take a look. | 12:06 |
| vishalmanchanda | e0ne: ^^ | 12:06 |
| amotoki | vishalmanchanda: I see two orthogonal points in your reply | 12:08 |
| amotoki | vishalmanchanda: the one is whether a volume detail has messages on its snapshot(s) | 12:09 |
| amotoki | vishalmanchanda: the other is where messages should be shown, in a tab or as part of the detail page. | 12:09 |
| amotoki | vishalmanchanda: so, I could not reply quickly when I saw your reply. | 12:10 |
| amotoki | vishalmanchanda: I think two discussion points are mixed and am not sure what you would like to discuss. | 12:10 |
| vishalmanchanda | amotoki: I want to discuss first one "volume detail has messages on its snapshot(s)". | 12:12 |
| amotoki | vishalmanchanda: what do you think from user perspective? | 12:12 |
| amotoki | vishalmanchanda: if a user would like to check what happens in his/her snapshot? do they need to go to a corresponding volume detail to check messages on the snapshot? | 12:13 |
| amotoki | vishalmanchanda: your proposed patch might make sense if a user would like to see messages on a volume itself. | 12:14 |
| vishalmanchanda | amotoki: hmm. | 12:14 |
| amotoki | vishalmanchanda: what user scenarios do you consider? it is the most important thing. | 12:14 |
| vishalmanchanda | amotoki: what if we add a new panel for the messages which shows all the user-messages. | 12:15 |
| vishalmanchanda | amotoki: I am also confused. | 12:15 |
| amotoki | vishalmanchanda: I have not heard any on this and see a patch proposed directly. | 12:16 |
| *** irclogbot_1 has quit IRC | 12:16 | |
| amotoki | vishalmanchanda: what confuses you? | 12:16 |
| *** irclogbot_3 has joined #openstack-horizon | 12:17 | |
| vishalmanchanda | amotoki: I mean I am agree with you that I shouldn't show the snapshot messages in volume detail tab. | 12:18 |
| vishalmanchanda | amotoki: but in future if more resources like backup, volume_group have these user-messages then again we have to add a tab for them as well. | 12:19 |
| amotoki | vishalmanchanda: future is okay, but I believe we are discussing how to support cinder messages in volume and snapshot, right? | 12:20 |
| vishalmanchanda | amotoki: yeah. | 12:21 |
| amotoki | vishalmanchanda: hot to supportr messages on volume and snapshot is worth exploring first. | 12:21 |
| amotoki | vishalmanchanda: at least I haven't got any information from your comment here. | 12:21 |
| amotoki | vishalmanchanda: I am not familiar with cinder messages in detail and just see the API reference, so perhaps you may know more. | 12:22 |
| amotoki | like use cases. | 12:22 |
| vishalmanchanda | amotoki:ok, then I will remove snapshot messages from volume messages tab. | 12:23 |
| amotoki | vishalmanchanda: I think you first discuss/propose the design direction before proposing a patch. | 12:23 |
| amotoki | vishalmanchanda: I am not sure what is a better way. | 12:24 |
| vishalmanchanda | amotoki: ok. I will check with Ivan first as he purpose this bp. | 12:24 |
| amotoki | vishalmanchanda: when I implement some feature, what I need are (1) first to understand the feature, (2) explore user scenarios on how/when to use it from POV of GUI and then (3) implement it. | 12:26 |
| *** jhesketh has quit IRC | 13:22 | |
| *** jhesketh has joined #openstack-horizon | 13:24 | |
| *** dklyle has quit IRC | 13:35 | |
| openstackgerrit | Martin Gerhard Loschwitz proposed openstack/horizon master: Set volume type for creating volumes from snapshots/volumes https://review.opendev.org/738308 | 13:51 |
| *** dave-mccowan has quit IRC | 14:22 | |
| *** dave-mccowan has joined #openstack-horizon | 14:25 | |
| *** btully has joined #openstack-horizon | 14:29 | |
| *** btully has quit IRC | 14:33 | |
| *** dklyle has joined #openstack-horizon | 14:49 | |
| *** ChanServ sets mode: +o dklyle | 14:49 | |
| *** dklyle sets mode: -o dklyle | 14:51 | |
| *** dave-mccowan has quit IRC | 15:08 | |
| *** dave-mccowan has joined #openstack-horizon | 15:11 | |
| *** dcapone2004 has joined #openstack-horizon | 15:38 | |
| dcapone2004 | all....not sure if this is a horizon bug or if it is an issue elsewhere....but I am having an issue with the hw_vif_model glance image property when setting it on a glance image. When first added, the proper list of options is shown and I am able to select virtio. However, when I go back, the dropdown only shows the options for VMWare when WMWare | 15:45 |
| dcapone2004 | is no where in my environment | 15:45 |
| vishalmanchanda | adding a new panel which shows cinder-user messages for all resource also looks a good option to me. | 16:02 |
| e0ne | +1 | 16:02 |
| e0ne | it will simplify user's workflow | 16:03 |
| vishalmanchanda | We can add a new panel name "Event Viewer" which shows all these messages. | 16:05 |
| amotoki | it works for really small deployments. | 16:07 |
| amotoki | does it work if a single project has 100 volumes and each volume has 10 snapshots (or 10 backups)? | 16:07 |
| e0ne | it's not supposed to have a lot of messages | 16:07 |
| vishalmanchanda | amotoki: We can add filter on the table. | 16:07 |
| e0ne | also, cinder messages have short TTL | 16:07 |
| amotoki | this is just an example :) | 16:08 |
| amotoki | if it is intended to be short TTL, it looks better to associate them with individual resources. | 16:08 |
| amotoki | ehy, my request to create a snapshot but it fails. a regular user would check the detail of the snapshot or the corresponding volume. | 16:09 |
| amotoki | s/ehy/hey/ :) | 16:09 |
| e0ne | https://github.com/openstack/cinder/blob/master/cinder/message/api.py#L25 | 16:09 |
| e0ne | amotoki: user should check snapshot details | 16:10 |
| amotoki | so doesn't it make sense to include messages in the snapshot detail? | 16:10 |
| e0ne | sorry, I'm not sure that I understood you correctly | 16:11 |
| e0ne | error message could appear on snapshot details page (1) or user should be able to find it in the 'messages' page (2) by snapshot uuid | 16:13 |
| amotoki | e0ne: do you mean that only messages within message_ttl (1 month by default) are stored and users can check them in the message viewers? | 16:13 |
| amotoki | if filtering with resource ID works well, it should work. | 16:14 |
| e0ne | amotoki: yes, messages will be deletead by a periodic task | 16:15 |
| *** kevko has quit IRC | 16:15 | |
| amotoki | the default of message_ttl 2592000 secs means 30days (1 month), so I don't think the number of messages is small enough as the current table size (20 or some) is. | 16:15 |
| e0ne | any message means some error occures | 16:16 |
| e0ne | so I don't expect a lot of them | 16:16 |
| amotoki | agree | 16:16 |
| amotoki | perhaps server-side filtering is needed. | 16:17 |
| amotoki | I am not sure client-side filtering works. | 16:17 |
| e0ne | +1 | 16:18 |
| vishalmanchanda | amotoki: e0ne : what is our final agreement on this? | 16:19 |
| amotoki | vishalmanchanda: I have no final solution yet. what do you think is best/better? | 16:20 |
| vishalmanchanda | I will remove snapshot messages from volume_detail 'Meassages' tab. | 16:20 |
| amotoki | vishalmanchanda: then what? | 16:20 |
| vishalmanchanda | then I will add a new tab in Snapshot details for Snapshot Meassgaes. | 16:21 |
| amotoki | IIUC, we discussed two options | 16:21 |
| amotoki | the one is to have messages in a detail page of a corresponding resource | 16:21 |
| vishalmanchanda | but a single snapshot or volume can have multiple messages. | 16:22 |
| amotoki | and the other is to have a new panel like "message viewer" (and perhaps add link to it from a detail page) | 16:22 |
| amotoki | you mentioned it by "Event Viewer" | 16:23 |
| vishalmanchanda | I have one more option | 16:23 |
| e0ne | btw, I just checked messages in our internal cloud in a tenant with ~50: only one message exists. but this tenant works during last few years | 16:24 |
| e0ne | so we'd got more than 50 volumes | 16:25 |
| vishalmanchanda | We can add "Messages Tab" in SnapShot detail view like I have done for volumes. | 16:25 |
| vishalmanchanda | amotoki: Did you get what I am trying to say? | 16:26 |
| amotoki | e0ne: nice to hear that :) | 16:26 |
| amotoki | vishalmanchanda: I think so. (I was just replying other neutron thread :p) | 16:27 |
| e0ne | the pretty same situation in other tenants I've got an access | 16:27 |
| * e0ne will be AFK during next 30 minutes | 16:27 | |
| amotoki | i have one question to e0ne | 16:28 |
| e0ne | amotoki: just ask it :) | 16:28 |
| amotoki | for example, when a user fails to create a vol snapshot, do they need to check messages on a corresponding volume? | 16:28 |
| amotoki | or are messages on a volume snapshot enough in most cases? | 16:29 |
| amotoki | I think it affects user scenarios. | 16:29 |
| -amotoki- thinks we don't need a conclusion JUST NOW | 16:30 | |
| amotoki | let's contineu the discussion | 16:30 |
| e0ne | I understad what you mean | 16:30 |
| e0ne | according to the code, it should be enough to check only snapshot-related messages | 16:31 |
| amotoki | I see. if so, a tab on the snapshot detail sounds good. | 16:31 |
| amotoki | today is already long to me from 6am to 130am. good night | 16:32 |
| vishalmanchanda | amotoki: e0ne good night:). | 16:33 |
| vishalmanchanda | thanks for the discsusion. | 16:33 |
| *** kevko has joined #openstack-horizon | 16:45 | |
| openstackgerrit | Merged openstack/horizon master: Define periodic jobs https://review.opendev.org/737686 | 16:57 |
| *** kevko has quit IRC | 17:07 | |
| *** mvkr has quit IRC | 17:15 | |
| *** jmccrory has quit IRC | 17:15 | |
| *** jmccrory has joined #openstack-horizon | 17:18 | |
| *** mvkr has joined #openstack-horizon | 17:19 | |
| *** jtomasek_ has quit IRC | 17:26 | |
| *** tsmith2 has quit IRC | 17:26 | |
| *** irclogbot_3 has quit IRC | 17:28 | |
| *** gyee has joined #openstack-horizon | 17:29 | |
| *** jtomasek_ has joined #openstack-horizon | 17:29 | |
| *** tsmith2 has joined #openstack-horizon | 17:29 | |
| *** irclogbot_1 has joined #openstack-horizon | 17:29 | |
| *** hoonetorg has quit IRC | 17:40 | |
| *** hoonetorg has joined #openstack-horizon | 17:52 | |
| *** e0ne has quit IRC | 17:59 | |
| *** dasp_ has quit IRC | 18:39 | |
| *** dasp has joined #openstack-horizon | 18:41 | |
| *** dcapone2004 has quit IRC | 18:50 | |
| *** dklyle has quit IRC | 18:54 | |
| *** dklyle has joined #openstack-horizon | 19:02 | |
| *** ChanServ sets mode: +o dklyle | 19:02 | |
| *** dklyle sets mode: -o dklyle | 19:02 | |
| *** josephillips has joined #openstack-horizon | 19:20 | |
| *** rdopiera has quit IRC | 19:41 | |
| *** mkowalski has quit IRC | 19:45 | |
| *** vishalmanchanda has quit IRC | 19:47 | |
| *** mkowalski has joined #openstack-horizon | 19:49 | |
| *** btully has joined #openstack-horizon | 19:55 | |
| *** spatel has joined #openstack-horizon | 19:55 | |
| *** btully has quit IRC | 19:59 | |
| *** e0ne has joined #openstack-horizon | 20:20 | |
| *** ChanServ sets mode: +o e0ne | 20:20 | |
| *** pbing19 has joined #openstack-horizon | 20:25 | |
| pbing19 | Hi guys, When i tried to change rescue policy to admin_api in nova_policy.json, it didnt work | 20:26 |
| pbing19 | is this the bug? | 20:26 |
| pbing19 | or anybody has any workaround | 20:26 |
| *** spatel has quit IRC | 20:29 | |
| *** spatel has joined #openstack-horizon | 20:30 | |
| *** spatel has quit IRC | 20:30 | |
| *** ircuser-1 has quit IRC | 21:03 | |
| *** e0ne has quit IRC | 21:07 | |
| *** priteau has quit IRC | 21:21 | |
| *** btully has joined #openstack-horizon | 21:44 | |
| *** btully has quit IRC | 21:48 | |
| *** gregwork has joined #openstack-horizon | 22:09 | |
| *** rcernin has joined #openstack-horizon | 22:36 | |
| *** tkajinam has joined #openstack-horizon | 22:46 | |
| *** rcernin has quit IRC | 22:47 | |
| *** rcernin has joined #openstack-horizon | 22:47 | |
| *** spatel has joined #openstack-horizon | 22:58 | |
| *** spatel has quit IRC | 23:07 | |
| *** hoonetorg has quit IRC | 23:08 | |
| *** hoonetorg has joined #openstack-horizon | 23:12 | |
| *** tosky has quit IRC | 23:16 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!