09:00:00 #startmeeting blazar 09:00:01 Meeting started Tue Dec 20 09:00:00 2016 UTC and is due to finish in 60 minutes. The chair is priteau. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:00:03 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:00:05 The meeting name has been set to 'blazar' 09:00:23 #chair masahito 09:00:23 Current chairs: masahito priteau 09:00:37 Hello 09:00:47 hello 09:01:03 Hi 09:01:16 #topic Roll call 09:01:44 hi 09:02:22 hi 09:02:29 pinging bauzas tejaswi janki 09:02:49 hkobayashi told me he is out of town this week. 09:02:59 OK 09:03:01 bertys and I are in a parallel meeting today. sorry, we will mainly listen today. 09:03:12 r-mibu is on #openstack-blazar but not here 09:03:26 anyone else? 09:04:32 hi 09:04:36 Hi tejaswi 09:05:00 can you pls post the link to the agenda 09:05:09 #link https://wiki.openstack.org/wiki/Meetings/Blazar#Agenda_for_December_20_2016 09:05:18 priteau: thanks 09:05:24 this is our agenda for today 09:05:50 Let's get started then 09:05:55 #topic Action items from last call 09:06:20 "Generate WSME doc for v2 API and check for differences with v1" 09:06:29 this was assigned to me 09:06:59 The WSME doc is generated with tox -e docs, and on each commit 09:07:10 e.g. http://docs-draft.openstack.org/66/406666/7/check/gate-blazar-docs-ubuntu-xenial/5ddde5e//doc/build/html/restapi/rest_api_v2.html 09:07:19 yeah 09:07:25 while v1 is here: http://docs-draft.openstack.org/66/406666/7/check/gate-blazar-docs-ubuntu-xenial/5ddde5e//doc/build/html/restapi/rest_api_v1.0.html 09:07:38 (sorry, I'm on a gate issue, very unlikely to be present here) 09:07:48 bauzas: no problem, thanks 09:07:59 I looked at the differences between the REST APIs 09:08:24 Just using the doc, I didn't have time to verify data sent on the wire 09:08:32 I identified these differences 09:08:39 V2: adds support for CRUD operations on "Before end" notifications (before_end_notification field in lease object) 09:08:39 v2: host extra capabilities may be handled differently: extra_capas in host object 09:08:39 v2: PUT requests have the ID as a parameter rather than in the URL? 09:09:30 The last one was unexpected 09:10:00 but overall not huge differences 09:10:37 it looks like there is only style difference. 09:11:00 and actually the last one I need to verify it in the code 09:11:47 Next step is to identify what was missing from client v2 patches 09:11:49 DELETE also doesn't have id in url, right? 09:12:27 masahito: you're right. I wonder if that's a doc issue though 09:12:46 I hope so :) 09:13:23 #action Verify where id is provided in PUT and DELETE requests for v2 API (priteau) 09:14:24 I believe we agreed that we would keep support for v1 API in the next Blazar release 09:15:10 If we can trust that v2 is working well and have it supported in the client, we could mark v1 as deprecated for this release 09:15:15 yes. 09:15:35 the goal being to minimize the amount of code to maintain 09:15:58 but I think at some point we will need a new API, probably with microversions 09:16:05 to support our new features 09:16:19 This brings us to the second action item 09:16:22 "investigate microversion support for Blazar API" 09:16:51 No one was assigned to this. I thought I could work on it but I didn't have much time for Blazar this past week. 09:17:24 Unless someone else has looked into it, I will reregister it 09:17:32 we should write down it in priorities after Ocata release 09:17:52 masahito: that's a good point 09:18:20 I added it at the end of our etherpad 09:18:40 we need to choose which version have microversioning, too. 09:18:49 like v1.1 or v2.1 09:18:59 v2.1 like Nova? ;-) 09:19:19 :-> 09:19:41 We will revisit later then 09:19:49 Third item was "masahito translates Promise requirement to blazar feature" 09:19:55 but some of us is absent here to discuss it now. let's keep it mind. 09:20:29 I'm still working on the item. sorry, not yet done. 09:20:39 no problem 09:20:51 I try to finish it by next meeting. 09:21:00 That's all for last week's action items 09:21:10 #topic Feedback on Project Teams Gathering (PTG) 09:21:33 masahito: I saw that you sent the email to openstack-dev. Did you get any feedback? 09:22:26 Unfortunately, I don't receive any feedback. 09:23:01 sorry. it is still undecided on our side whether one of us can join 09:23:18 I hope we can decide on this mid January 09:23:42 same for me, it will be clearer next month 09:24:05 no problem. 09:25:18 I'll be there to join another team meeting. so if we are there, we can meet. 09:25:24 OK 09:25:38 but I'm not forcing it. 09:26:14 And who is planning to be in Boston? 09:26:24 I will likely be there 09:27:22 It's very likely one of us will be there 09:27:23 I maybe there 09:28:05 For those who can't make the PTG that's another opportunity to meet 09:28:14 2.5 months later 09:28:31 good idea 09:29:27 Should we skip the next topic? "User story and gap analysis" 09:29:43 If it's not ready for discussion 09:29:54 somehow, it's good to meet together. 09:30:03 nothing from my side for PTG 09:30:33 I'll join PTG, i havn't get approval yet though 09:32:23 Hi r-mibu 09:32:25 related to the user story: I have drafted a OpenStack persona 09:32:30 your feedback is welcome on it 09:32:34 #topic User story and gap analysis 09:32:39 #link https://etherpad.openstack.org/p/osux-persona-nocengineer Draft NOC engineer proposal 09:33:01 That's great GeraldK 09:33:21 at the end there is a part that we'd like to propose for the user story update 09:34:38 #action Review capacity management use case https://etherpad.openstack.org/p/osux-persona-nocengineer 09:35:52 GeraldK: it looks quite detailed, thanks for contributing this 09:37:43 Anything else for use cases? 09:38:19 GeraldK: just quick question 09:38:39 GeraldK: are you going to add reservation use case into that etherpad page? 09:39:16 r-mibu: not sure what you mean? 09:39:52 r-mibu: make sure you scroll down in the etherpad, there is more content after "The organizational models" 09:39:53 r-mibu: at the end of the etherpad you have a list of reservation usage examples 09:39:56 i mean 'key tasks' seems not include reservation use cases 09:40:18 i see, sorry! 09:40:31 r-mibu: good point. I may be more specific in the key tasks on reservation 09:40:59 that includes enough detail! thanks! 09:42:07 i am not sure about the content for some sections. need feedback from UX team 09:42:38 this is partically independent from the update to the user story 09:43:00 we can do the update to the user story even if the NOC engineer persona is not there yet. 09:46:15 GeraldK: agree 09:46:27 GeraldK: are you talking about the capacity management user story? 09:47:28 GeraldK: what we need is to convince developers in OpenStack project. user story is just one of method 09:47:28 or another user story? 09:48:39 priteau: yes. capacity mgmt user story. 09:49:12 OK. Sorry, still haven't been able to review it. 09:49:19 priteau: I agree this is only one way of convicing developers. 09:50:02 #action Review capacity management user story (priteau) 09:50:05 and in addition this is a quite new method and we cannot know how successful it is. still, I'd like to also try that way. 09:51:01 #topic Discussion of new features 09:51:14 Anything to discuss about new features since last week? 09:53:01 We're mostly focusing on bug fixes and code cleanup at the moment 09:54:09 Probably a better topic for next year ;-) 09:54:20 ;-) 09:54:26 #topic Next meetings 09:54:45 It's going to be holiday season 09:55:09 I won't be able to join the next two meetings (Dec 27 and Jan 3) 09:55:41 me too. 09:55:43 I am not available Jan 3 09:56:12 Feel free to join without me of course 09:56:50 But if others have a similar holiday schedule, maybe we should have the next meeting on January 10 09:57:02 +1 09:58:04 Is that OK for others too? 09:58:54 +1 09:59:10 #agreed Next meeting on January 10 10:00:11 That's all for today then 10:00:19 #endmeeting