14:03:23 <tobberydberg> #startmeeting publiccloud_wg
14:03:24 <openstack> Meeting started Thu Jul 19 14:03:23 2018 UTC and is due to finish in 60 minutes.  The chair is tobberydberg. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:03:25 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:03:27 <openstack> The meeting name has been set to 'publiccloud_wg'
14:03:29 <zaneb> tobberydberg: I was hoping to chat about adjutant a bit. but also on another call simultaneously, so maybe towards the end of the agenda :)
14:03:45 <aprice> o/
14:03:51 <tobberydberg> sounds good zaneb
14:03:55 <tobberydberg> welcome aprice
14:04:08 <tobberydberg> Agenda at https://etherpad.openstack.org/p/publiccloud-wg as usual
14:05:12 <tobberydberg> Please put your name there as well
14:05:49 <tobberydberg> #topic 1. Additional meeting slot
14:06:39 <tobberydberg> danny and allison ... you just added yourself to last meeting =)
14:07:27 <tobberydberg> so, talked to a few people in Vancouver that wasn't really happy with the afternoon UTC time
14:07:38 <danny> whoops
14:07:41 <danny> thanks : )
14:08:19 <tobberydberg> My proposal here will be that we try to have a meeting on even weeks as well, at 0700 UTC ... which works better for APAC
14:10:07 <tobberydberg> Also, we start doing this as more of test slot and see how many people will be there and what action we can get there
14:10:24 <tobberydberg> Any questions or thoughts around that?
14:11:45 <mriedem> that's how we try to run the nova meeting,
14:11:51 <mriedem> alternating times to cover EU/APAC
14:12:02 <mriedem> still not great for APAC for the nova meeting, but one is better than the other
14:13:24 <tobberydberg> yes, I know ... time chosen in communication with a Catalyst cloud so that it is okay for them, but at the same time ok for europe so we can cover that as well
14:14:03 <tobberydberg> ButOk ... not much questions, so I'll go ahead and add that and give it a try
14:14:51 <tobberydberg> #topic 2. Passport program - spec approval
14:15:05 <tobberydberg> #link https://review.openstack.org/#/c/583529/
14:15:44 <tobberydberg> Made a patch with the v2 content as we worked out together in the last meetings
14:16:17 <pilgrimstack> it's an additionnal meeting or it's to replace that one ?
14:16:39 <tobberydberg> would be good if we get thoughts, +1 and -1 on that, together with comments appreciated or inline comments
14:17:08 <tobberydberg> not replace, additional ... so we have one every week
14:17:39 <aprice> danny reached out to the existing passport program members so hopefully we see more participation in there
14:18:18 <tobberydberg> saw that, thanks danny and aprice
14:18:40 <tobberydberg> Please reach out to me if you get any feedback in that channel
14:18:47 <danny> i also reached out to 6 prospects that have showed interest
14:18:57 <tobberydberg> perfect danny
14:19:02 <aprice> of course - is there a time when you are hoping to have all feedback in?
14:19:12 <tobberydberg> yesterday? ;-)
14:19:51 <tobberydberg> well ... would be good to have the voting done by the meeting in 2 weeks
14:20:01 <aprice> haha
14:20:05 <aprice> yes, i think that's doable
14:20:41 <tobberydberg> for my self its no hurry, leaving for vacation .. .well try to do the meetings, but will not be much else done during the upcoming 4 weeks from my side
14:21:41 <tobberydberg> So, pilgrimstack rmart04 adriant (and others that represent members of the PP ... please take your time to read the spec and comment.
14:22:36 <tobberydberg> As I said, whats in that spec have been worked out during the last couple of metings and what was said during the meetings in Vancouver
14:23:23 <tobberydberg> questions, thoughts, something else about that?
14:25:27 <tobberydberg> then we proceed
14:25:33 <tobberydberg> #topic 3. Global loadbalancer feedback
14:25:56 <tobberydberg> Last meeting we were introduced to a proposal from Memset
14:26:20 <tobberydberg> not sure how many that have seen the drafted document that they wrote after last meeting
14:27:07 <tobberydberg> is anyone from memset here? (ping rmart04)
14:27:17 <rmart04> Howdy Howdy!
14:27:27 <rmart04> Sorry, let me catch up
14:28:15 <tobberydberg> not sure that document was shared at the mailing list...
14:31:21 <tobberydberg> not sure how much you are involved in that initiative rmart04 - but at this stage I think that we need to make it publicly available (mailing list) and ask the community for feedback
14:31:56 <aprice> +1
14:32:25 <rmart04> Cool, Just quickly grabbed Nick, he sais the document is still in draft and they hope to have somthing to share soon. I’m not too involved at this stage, but I mentioned the mailing list could be a good place to share it.
14:32:42 <tobberydberg> ok, lets postpone then
14:32:56 <rmart04> Sorry!
14:33:04 <tobberydberg> no problem
14:33:19 <tobberydberg> #topic 4. Draft spec for Missing features
14:33:22 <pilgrimstack> tobberydberg: added in my todo to review the specs
14:33:31 <tobberydberg> thanks pilgrimstack
14:33:36 <rmart04> as for 0700 UTC thats a bit early for me to be honest! I’m not sure there are enough of us to warrent 2 different time zones bi-weekly!
14:34:15 <tobberydberg> no need rmart04 - this time slot will still be here
14:34:40 <rmart04> Ah OK :)
14:35:46 <tobberydberg> So, spec for missing features - suggestion from my side is to draft a spec for the "missing features" project, like we did for Passport
14:36:11 <mriedem> it's going to be a project?
14:36:32 <tobberydberg> should have had that between "
14:36:34 <mriedem> right now the progress was moving the items from the mega spreadsheet into LP bugs right?
14:36:35 <tobberydberg> "project"
14:36:40 <tobberydberg> not sure what to call it
14:37:17 <mriedem> https://bugs.launchpad.net/openstack-publiccloud-wg
14:37:30 <tobberydberg> More of a definition spec how we work with "missing features list" etc etc
14:37:37 <tobberydberg> yes
14:37:44 <mriedem> oh
14:37:49 <mriedem> like a project guide?
14:37:52 <tobberydberg> will be kept like that
14:39:13 <tobberydberg> a more structured definition of what that list is about and how we work with it, so that is clear for everyone that will help out in some way
14:39:32 <mriedem> maybe a tangent,
14:39:40 <mriedem> but is it ok to mark some of these as incomplete, like https://bugs.launchpad.net/openstack-publiccloud-wg/+bug/1771591 ?
14:39:40 <openstack> Launchpad bug 1771591 in OpenStack Public Cloud WG "Nova resize filter" [Undecided,New] - Assigned to Paweł Suder (sudix)
14:39:43 <mriedem> where it needs investigation
14:40:14 <tobberydberg> absolutely
14:41:02 <tobberydberg> and exactly that question should be super clear in some documentation for the workflow of this list
14:42:15 <tobberydberg> I will make  etherpad draft for this as we did with PP and we can have more discussions around it, but the content of that will be based upon the discussions we had in Vancouver
14:43:53 <tobberydberg> mriedem: hopefully pasuder will get a ping about that and confirm from his side as well!
14:44:12 <tobberydberg> regarding  1771591
14:45:42 <mriedem> ack
14:46:22 <tobberydberg> #topic 5. Upcoming meetings
14:47:13 <tobberydberg> How does it look with vacations and stuff? Will people be away or working the upcoming 4 weeks?
14:49:30 <tobberydberg> everyone have already left for vacation... ;-)
14:49:44 <aprice> I will be around if there are things that need to move forward :)
14:50:15 <tobberydberg> Good to know!
14:50:40 <tobberydberg> We will probably have some PP discussion at least
14:50:52 <danny> so will I : )
14:51:10 <tobberydberg> #topic 6. Other topics
14:51:39 * zaneb is off the phone now
14:52:00 <tobberydberg> See that you mriedem have added som stuff there and would like to get some feedback as well
14:52:20 <mriedem> yeah first just an fyi on https://review.openstack.org/#/q/topic:bug/1469179+(status:open+OR+status:merged)
14:52:40 <mriedem> a series of changes to fix the long known issue where nova reports and filters hosts on root_gb even if doing boot from volume
14:53:06 <mriedem> only applies to the FilterScheduler (not CachingScheduler)
14:53:12 <mriedem> but CachingScheduler should be gone in Stein anyway
14:53:18 <tobberydberg> ++
14:53:32 <mriedem> we have data migration tools in rocky for people using CachingScheduler to get over to FilterScheduler
14:53:37 <mriedem> mgagne has helped test those out
14:53:39 <pilgrimstack> a bad news from OVH: we disabled (temporary) the passport program because of too many frauders
14:53:57 <mriedem> i'm talking about the heal_allocations CLI https://docs.openstack.org/nova/latest/cli/nova-manage.html#placement
14:54:38 <mriedem> the other thing i posted was a couple of previously approved specs in nova which huawei might be picking up again in stein, so was trying to gauge interest on those since they aren't in the 'missing features' LP bug list
14:54:52 <mriedem> doesn't have to be done during this meeting though, the links are in the etherpad
14:55:11 <tobberydberg> Thanks for that
14:55:21 <mriedem> that's it from me
14:55:28 <tobberydberg> will look into them
14:56:03 <zaneb> so, good news, Adjutant will be an official project starting with the Stein release
14:56:14 <zaneb> #link https://review.openstack.org/553643
14:56:17 <tobberydberg> whoop whoop
14:56:34 <zaneb> there was some discussion in there about adoption or lack of it
14:56:48 <zaneb> it seems like people are holding off until it is finished
14:57:22 <zaneb> but also they're not getting much feedback on the design because people are holding back until they've adopted it
14:57:45 <mriedem> catch 22
14:57:56 <tobberydberg> exactly
14:57:58 <rmart04> pilgrimstack: Do you do any fraud checking with a card provider before enabling the OpenStack project for the user?
14:58:28 <zaneb> my concern is that because only one team in involved, we could end up in a situation where it doesn't meet other companies' needs due to lack of feedback
14:58:40 <zaneb> so anything we can do to try to bootstrap that feedback loop would be helpful
14:58:48 <tobberydberg> zaneb: I personally can't help out much in the testing since we are not using horizon
14:59:07 <tobberydberg> But, I assume that there is plenty in here that does ?
14:59:17 <zaneb> like if we could encourage people to take a look at the APIs and point out any holes or whatever, that would be great
15:00:03 <tobberydberg> We can if nothing else do a shout out in the mailing list and potentially other places for feedback
15:00:03 <zaneb> anyway, I just wanted to publicise that a little bit within this group
15:00:09 <zaneb> +1
15:00:33 <zaneb> I'm sure adriant would like to be here to do that but it's currently 3am for him so I am filling in :)
15:00:57 <tobberydberg> Looking at the apis and feature design spec is probably something that I can help out with since I've build our own system for this =)
15:01:19 <zaneb> tobberydberg: that would be fantastic :)
15:01:35 <tobberydberg> what is why wednesdays even weeks at 0700 UTC will be better for him =)
15:01:59 <tobberydberg> do you know if he will be in Denver?
15:02:14 <zaneb> not sure actually
15:02:18 <tobberydberg> I can probably ask him myself in an email though =)
15:02:27 <tobberydberg> ok ok
15:03:29 <tobberydberg> Lets try to do some kind out shout out within the group and publiccloud-wg tag in mailing list for a start (know adriant already done that though)
15:03:43 <tobberydberg> Anything else?
15:03:51 <tobberydberg> know we are out of time
15:05:22 <tobberydberg> then thanks for today everyone - and stay tuned for new meetings in the upcoming weeks!
15:06:18 <tobberydberg> #endmeeting