18:02:30 #startmeeting ironic_ui 18:02:30 Meeting started Tue Apr 4 18:02:30 2017 UTC and is due to finish in 60 minutes. The chair is TheJulia. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:02:31 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:02:33 The meeting name has been set to 'ironic_ui' 18:03:26 Our agenda, as always https://wiki.openstack.org/wiki/Meetings/Ironic-ui 18:03:30 #link https://wiki.openstack.org/wiki/Meetings/Ironic-ui 18:03:55 #topic Announcements/Reminders 18:04:30 #info TheJulia will likely miss the meeting next week, and will be on vacation the following week. crushil has volunteered to run the meeting next week. 18:04:37 That is all I have, anyone else? 18:05:21 I know crushil was unable to make it today. 18:05:26 I am here 18:05:29 Just listening in 18:05:35 o/ 18:05:37 \o 18:05:37 Awesome 18:05:52 Okay, well, If there are no other announcements, I guess we shall proceed. 18:06:36 #topic Current Status 18:07:29 I had an item to look at jasmine unit test automation, and realized that our npm job was not actually firing any tests, although I don't know the details of how that works to fix it. 18:07:49 betherly: By chance, is that something you have any knowledge of? 18:08:38 TheJulia: hmm no i wasn't aware that was happening. I'll take a look 18:08:50 Thank you betherly 18:09:12 #info betherly to look at the unit test execution issues 18:09:14 TheJulia: I'll probably have a response tomorrow now as I'm slightly brain dead this evening lol 18:09:23 betherly: no worries! 18:09:54 Other than that issue, ppiela_ has a number of revisions to be rebased due to merge conflicts. 18:10:02 ppiela_: By chance, are you here today? 18:10:24 ppiela_: TheJulia: id be happy to help with the rebasing if it would be useful? 18:10:39 I am here 18:11:01 I can help out with rebasing too 18:11:36 ppiela_: Any objections for people to pickup some of the revisions and rebase them? 18:11:42 I got pulled off to work on other stuff 18:11:58 ppiela_: just let us know what you want us to do :) im very happy to help with that tomorrow but don't want duplicate work being done or to step on toes 18:12:19 ppiela_: it happens :) 18:12:31 I dont have a problem with that, but really want to understand what I did wrong 18:12:31 yup! 18:12:59 ppiela_: i can do it over a video call if that would be useful? 18:13:08 It's likely nothing you did wrong 18:13:16 Just things merging in weird order 18:13:27 I haven't looked into it yet though 18:13:29 ppiela_: oh, on the rebase you did? 18:14:06 Thanks. If it is not holding up others, I would like to make another pass before calling for the cavalry 18:14:20 ppiela_: I think ``git rebase -R`` would have prevented it instead of ``git rebase`` 18:14:22 ok. just ping me if you need a hand 18:14:31 thx 18:14:44 But anyway, we should back on track. 18:14:54 Anyone have any other statuses to report? 18:15:51 I guess not, moving on... 18:16:08 #topic Planning/Priorities 18:16:34 The only priority that I see right now is getting the outstanding revisions rebased, but even that is not an urgent activity. 18:17:02 I looked at launchpad earlier today and we had no new bugs. 18:18:09 Any questions or items regrant planning or priority? 18:19:25 * TheJulia hears crickets 18:20:00 Since we have no discussion items, we will just go to open discussion. 18:20:13 #topic Open Discussion 18:21:20 Anyone have anything they wish to discuss today? 18:21:31 Nothing here 18:22:02 I have a newbie question. Does ironic-ui relies on python-ironicclient or talks directly to ironic-api? 18:22:05 robcresswell: Out of curiosity, should we still expect testing guidelines around Pike-3? 18:22:21 soliosg: It uses python-ironicclient 18:22:57 soliosg: Requests are proxied through horizon 18:22:57 Thanks. I found that in requirements.txt, just wanted to confirm. 18:23:30 soliosg: Thank you for asking :) 18:23:44 Is there a plan to migrate to openstackclient in the future? 18:23:57 That's actually my manager's question ;) 18:24:34 soliosg: that has not been discussed 18:24:39 soliosg: so, we import python-ironicclient for the rest API client, and openstackclient actually federated out all OSC commands and api calls out to client libraries 18:24:51 openstackclient isn't a python SDK, right, just a CLI 18:25:33 Basically what jroll said too :) 18:26:23 soliosg: Was there a specific concern with invoking python-ironicclient? 18:26:53 Thank you 18:27:57 Oh, no concern actually 18:28:13 Okay, just wanted to make sure. :) 18:28:39 Excellent! Anything else to discuss today? Aside from using the ui to take over the world of course.... :) 18:30:05 I have do a style/philosophy question on the ironuc-ui api modules 18:30:51 To what extent should be trying to make them faithful 1:1 proxies of the client? 18:31:07 This is coming up in code reviews 18:31:23 For example, node_id versus node_ident 18:32:47 Should the api calls accept both node names and uuids even though the ui components will likely always have the uuid? 18:32:53 Internal style consistency is more important than the variable naming for a single value. If someone really feels strongly about it, it can be bulk changed in a revision, but I don't think naming is really a big deal. I'd be more concerned about including extra data in the reply from horizon to the web page 18:34:34 We kind of had the same discussion in shade, and I think we started leaning towards name_or_id for positional variable names 18:34:38 TheJulia: pike-1, so next week. 18:34:53 TheJulia: +1 18:34:54 Sorry, just out atm but reading the scrollback :) 18:35:06 robcresswell: awesome! 18:36:04 #info robcresswell reports that we should have some integration testing guidance from horizon next week. 18:36:58 ppiela_: if it is positional, it... really should not be a big deal. Hopefully that answers your question? :) 18:37:20 TheJulia: I agree on consistency. Let's see how things go 18:37:38 Sounds good! 18:37:38 TheJulia: yes it does 18:37:45 Anything else to discuss today? 18:39:11 * TheJulia hears crickets and thinks everyone can have twenty minutes back 18:39:26 Thank you! 18:39:54 Thanks everyone! 18:40:14 Thank you everyone! 18:40:16 #endmeeting