Hi Parker, >From the minutes of this week's TSC call: http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/opnfv-meeting.2018-08-21-12.52.html they've deferred the agreement till next week.
Assuming there is an agreement, and LaaS is open to all LFN members, I agree we will run into a scarcity of resources if we don't set some restrictions upon users/projects. So the question is, should this restriction be on a per-user, per-group, per-lfn-project basis, or some combination thereof? With 48 x86 and 14 aarch64 machines, we can have in total 8 Pharos compliant PODs (6 servers) booked at once (with 4 extra servers). Perhaps we restrict bookings to 1 per-user, 4 per-lfn-project, with a max of 2-weeks per-booking? You would have to do some calculations of which groups/projects a user belongs to in order to figure out when the quota is reached. This will also be somewhat hard as the limit might depend on either the number of servers in total, or the number of PODs and that would have to be a separate calculation I'm not sure what the answer is here, but I wanted to respond to at least keep the discussion rolling. Regards, Trevor Bramwell On Fri, Aug 24, 2018 at 10:58:28AM -0400, Parker Berberian wrote: > Hi all, > > As the release of LaaS 2.0 (info here > <https://wiki.opnfv.org/display/INF/LaaS+Timeline>) nears, we need to come > to a conclusion on how we are going to limit access to the Lab as a Service. > > Background info: > > LaaS usage is currently around 50-80%. As we open LaaS to all of LFN and as > we allow users to book multiple servers together as one "POD", we expect to > have a resource scarcity. > > We need some way of policing who is allowed to book how many machines, and > for how long. > > > The infra call this monday has been cancelled, and we need to try and come > to a conclusion on this soon. > > Thank you, > Parker > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#21841): https://lists.opnfv.org/g/opnfv-tech-discuss/message/21841 Mute This Topic: https://lists.opnfv.org/mt/24945176/21656 Mute #laas: https://lists.opnfv.org/mk?hashtag=laas&subid=2783016 Mute #infra: https://lists.opnfv.org/mk?hashtag=infra&subid=2783016 Group Owner: [email protected] Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
signature.asc
Description: PGP signature
