18:01:18 #startmeeting ironic_ui 18:01:19 Meeting started Tue May 16 18:01:18 2017 UTC and is due to finish in 60 minutes. The chair is TheJulia. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:01:20 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:01:23 The meeting name has been set to 'ironic_ui' 18:01:34 Greetings everyone! 18:01:52 Our agenda this week can be found at: https://wiki.openstack.org/wiki/Meetings/Ironic-ui 18:01:54 #link https://wiki.openstack.org/wiki/Meetings/Ironic-ui 18:02:14 #topic Announcements/Reminders 18:03:11 I have no announcements this week, does anyone have anything this week? 18:03:27 nothing from me 18:04:19 Well, then I guess we will mov on if nobody has anything else. 18:04:26 #topic Current Status 18:05:09 Presently https://review.openstack.org/#/c/437419/11 is in need of a second review. It is holding up some of ppiela's other work. We can discuss reviews in general later on. 18:05:10 I am starting to look at portgroups 18:05:23 ppiela: \o/ 18:05:41 #info ppiela is beginning to look at implementing port groups 18:06:29 Also, it looks like https://review.openstack.org/#/c/463852/ just needs a quick re-review. 18:06:54 Yes, I will +2 it 18:06:57 #link https://review.openstack.org/#/c/437419/11 18:07:07 #link https://review.openstack.org/#/c/463852/ 18:07:10 Awesome 18:07:27 I think that is it for current status, unless anyone else has anything? 18:08:35 do we have weekly priorities to review like we do for ironic? 18:09:05 anupn: sort of, although we're not tracking on an ether pad, it is more of a "what is outstanding" question, which we sort of just went over 18:09:22 TheJulia: yup cool 18:09:24 #topic Priorities 18:09:54 That being said, it is not set in stone 18:10:47 Also, I need to go through launchpad, and reconcile/check everything outstanding. We could use that for priority review if there are people looking for suggestions of what they might work on to contribute? 18:11:07 #info TheJulia will go through the ironic-ui launchpad bug list early next week. 18:11:57 sounds great 18:13:11 Anyone have any other priority items? 18:13:27 Not me 18:14:02 Okay 18:14:07 Easy enough :) 18:14:08 #info Priorities for this week are the outstanding review items noted in Current Status 18:14:18 Onward to the discussion! 18:14:46 #topic Discussion 18:15:41 I sent out an email to the mailing list about reducing the review threshold for ironic-ui in order to allow us to iterate faster. 18:15:44 #link http://lists.openstack.org/pipermail/openstack-dev/2017-May/116690.html 18:16:09 Thanks for doing that, I am in agreement 18:16:22 I saw the PTL replied with positive feedback, but I wanted to give meeting attendees a chance to object or ask questions. 18:16:43 I am good. Thanks for sending out the post 18:17:35 If we run into problems we can re-evaluate 18:17:38 Well, if there are no objections, I'll mark it as being agreed upon. 18:17:42 ppiela: exactly! :) 18:17:51 Hi TheJulia, I picked up https://bugs.launchpad.net/ironic-ui/+bug/1648553 and https://bugs.launchpad.net/ironic-ui/+bug/1671567 18:17:53 Launchpad bug 1648553 in Ironic UI "UI lacks the ability to set the raid configuration" [Medium,Confirmed] - Assigned to Ramamani Yeleswarapu (ramamani-yeleswarapu) 18:17:54 Launchpad bug 1671567 in Ironic UI "UI has no way to get/set a node's current boot device" [Wishlist,In progress] - Assigned to Ramamani Yeleswarapu (ramamani-yeleswarapu) 18:18:44 Depending on the priority, I can start on one; which one is of higher priority? 18:18:49 Support for boot-device was done by mgould 18:19:00 I believe 18:19:17 Get boot device was done and then it was not assigned to anyone after that, ppiela 18:20:40 I meant, set boot device part is still outstanding. 18:20:42 rama_y: I think that is fine. Setting the boot device should be a good first step and then raid device configuration with may require a little more complexity 18:20:50 rama_y: Thank you! 18:21:03 TheJulia: thanks, sounds good. 18:21:50 rama_y and others. It's great to have your contributions. Thanks! 18:21:50 #agreed The meeting attendees are in agreement to lowering the review requirement as noted in the mailing list email. We will re-evaluate and change as needed if the need or issue arises. 18:22:16 I guess we're basically in Open Discussion now :) 18:22:17 Thanks, good to be part of ironic-ui. 18:22:24 #topic Open Discussion 18:22:25 :) 18:22:37 TheJulia, I assigned driver composition bug https://bugs.launchpad.net/ironic-ui/+bug/1672729 to myself 18:22:39 Launchpad bug 1672729 in Ironic UI "UI is unaware of driver composition node *_interface fields." [Undecided,New] - Assigned to Anup (anup-d-navare) 18:22:39 So! What else shall we talk about? 18:22:49 Just a general reminder that we need to work on our unit tests 18:22:50 anupn: Awesome! Thank you 18:23:03 are there any notes already discussed on how driver interfaces should be seen in UI? 18:23:22 Yes, we do need to work on our unit tests. betherly are you on? 18:23:23 I mean it should go under node correct? 18:23:50 anupn: Yes, it should go under the node. It is kind of like the driver, except they are the interfaces that make up a driver that can now be set 18:24:00 so, I guess under a node makes sense.... 18:24:20 Truthfully, I've not thought about it much more than the data model 18:24:51 TheJulia, np, just came up to my mind when going over the bug 18:25:13 anupn: it is a great question to ask 18:25:40 ppiela: Do you have any feelings/preferences towards placement/view? 18:25:59 Under the node makes sense. The node-details configuration page is getting quite big, and could be split into separate tabs, but I finding that having th info on one page is useful. 18:26:30 I guess we could get it in and shuffle it around later if it makes sense 18:26:32 I have done prototype splits, and not been happy with the results 18:26:36 TheJulia, ppiela: ++ 18:26:56 TheJulia, ppiela: may be under driver_info under node_configuration 18:27:18 anupn: except that would be misleading since that is a distinct field under a node 18:27:18 I am hoping for some actual operator feedback to guide us 18:28:04 Until then I think we should follow the existing patterns. I am open to any suggestions. 18:28:33 That sounds good to me. 18:28:56 Sounds good 18:29:09 Is there anything else to discuss today? 18:29:31 Good here 18:29:39 nothing from me 18:29:43 nothing more from me 18:29:58 nothing more from me 18:30:32 Awesome, well then, seems like we all get a half hour back! 18:30:39 Thank you everyone, and have a wonderful week! 18:30:46 thanks. \o 18:30:53 Thanks all! 18:30:56 #endmeeting