Hi all,

As mentioned in the design meeting minutes, I've added a new ticket in git.lavasoftware.org regarding the new authorization model in LAVA: https://git.lavasoftware.org/lava/lava/issues/201

The main goal is to optimize the device access authorization, but also replace(if proved feasable) the current authorization model which relies on django-restricted-resource (https://git.lavasoftware.org/lava/django-restricted-resource) dependency. The most important thing to note is that the migration to the new model **must** be properly implemented and thoroughly tested so that the current permission model is preserved.

Any suggestions/comments to the ticket are welcome.

Thanks,

On 1/16/19 6:08 PM, Steve McIntyre wrote:

Hi folks,

We held our regular weekly design meeting today via Hangout. Brief summary of discussion:

• LAVA 2019.01 release

  • Tentatively planned for 24th January

  • Neil normally does the functional release tests, may need to take those over if he's still ill.

  • What should be included? Quick discussion of open Merge Requests:

    • !336 Milosz still testing
    • !333 - merge, looks good
    • !331 - merge, definitely needed
    • !328 - looks good
    • !324 - needs review
    • !323, !321 will wait
    • !309 - check and review
    • !302 - review
    • !295 will wait for discussion
    • !294 needs more work

• BKK19 presentations?

  • lavafed/meta-lava "LAVA community enabled testing"
  • LAVA user forum Already requested
  • Bootloader testing (with Loïc Poulain) Would be great

• Inviting community to the design meeting?

  • We've been talking about doing this for a while, but never actually got round to it. It's time we did! See below for details.

  • Agreed to send mail to lava-devel each week with summary of the minutes, with a link to the HO for the meeting itself [Steve]

  • Mail to -announce describing this [Steve]

  • If we ever overflow what hangouts will deal with, worry about it then

  • If we ever need private meetings, we can have those as needed

• Access rights improvement

  Stevan is looking into revamping how access controls are implemented, to make things simpler/cleaner/faster. He'll add a ticket at git.lavasoftware.org and mail the -devel list with more details.

• Decoupling scheduler from the frontend

  We were planning on discussing this at the sprint this week before it was postponed. Hoping to re-organise it soon...

The LAVA design meeting is held weekly, every Wednesday at 13:00 to 14:00 UTC using Google Hangouts Meet: https://meet.google.com/qre-rgen-zwc Feel free to comment here or join us directly in the meeting.

Cheers,