16:00:05 #startmeeting blazar 16:00:06 Meeting started Thu Oct 24 16:00:05 2019 UTC and is due to finish in 60 minutes. The chair is priteau. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:07 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:10 The meeting name has been set to 'blazar' 16:00:40 #topic Roll call 16:02:31 hello 16:02:37 Hi jakecoll 16:03:36 Meeting agenda: 16:03:40 PTG Team Photos 16:03:40 PTG meeting preparation 16:03:40 AOB 16:04:06 #topic PTG Team Photos 16:04:57 At every PTG the Foundation takes pictures of the team 16:05:23 The Blazar team is scheduled to be taken at 11:40-11:50 on Friday, November 8 16:05:35 sounds good 16:05:36 As a contributor you're welcome to join them 16:05:45 Will do 16:05:52 I think we had someone from Heat on the picture one year 16:06:09 #topic PTG meeting preparation 16:06:36 Thanks for adding content to the Etherpad at https://etherpad.openstack.org/p/blazar-ptg-ussuri 16:06:55 At least I assume it was you? 16:07:00 Yea, it was me 16:07:25 added some of the things we didn't get through and some refactoring to maintenance 16:07:25 I am curious about the Refactor api/rpc/service calls item, I don't think it has come up before 16:07:44 Is it to make it more object oriented? 16:07:56 I think this convention of plugin.list_plugin creates a lot of redundant code 16:08:46 Removing redundant code sounds like a good idea :) 16:09:32 I am adding more items around allocations 16:10:48 Do you think you would be able to revisit your calendar implementation with the optimized database queries? 16:11:51 That would allow us to identify other potential blockers early in the cycle. 16:11:52 depends on timeline. We're going to prioritize upgrading to Train. Then that should be on my table 16:12:07 Fair enough. 16:12:21 So probably not before the PTG meeting, but maybe by end of year? 16:12:28 (calendar year) 16:12:33 Yea, that should be more than doable 16:14:57 I will look in previous Etherpads for other ideas that are still relevant 16:15:05 This looks like a good priority list for now 16:16:36 Anything else to mention? 16:17:33 I don't think so. No real big feature ideas on our end 16:18:12 At some point we were thinking about some kind of meta-scheduler to manage multi-site reservations. Is this still on the agenda? 16:18:35 oh right, that was your brainchild 16:18:54 We would really like that 16:19:20 We trying to move to a federated user login 16:20:16 oh wait, I was think of your policy-based usage enforcement 16:20:56 What is the advantage of the meta-scheduler for multiple sites? 16:21:07 Yeah, the meta-reservations thing are from past discussions I had with Kate. 16:21:40 I haven't heard her or jason mention it 16:21:40 Well, it was something to allow a user to say "I want a meta reservation for X compute at UC and Y storage at TACC and a VLAN linking both" 16:22:03 It was just at the idea stage. 16:22:15 Anyway, good reminder about usage enforcement. I will add it to the list 16:22:51 Yea, we might be able to help with that if we go down the road of migrating off TAS 16:24:22 Meta-scheduler sounds like a lot of work to give users a few less clicks. Not sure it would be high priority on our end. 16:24:51 OK 16:25:03 It also sounds very specific to chameleon's setup 16:25:47 #topic AOB 16:25:59 Nothing special from me to share this week 16:26:30 Nor I 16:26:44 Enjoy the PTG then! 16:26:51 Have a safe trip. 16:26:57 Thanks! 16:27:00 #endmeeting