OWL- Open Wireless Lab
- Martin Skorupski
Analytics
Table of Contents
Child Pages
Scope
This page provides information about the O-RAN Software Community Lab at Rutgers University’s Winlab/Orbit-Lab/COSMOS-Lab.
O-RAN-SC Access and Use Policy
In general, tasks should be automated as much as possible to reduce manual overhead. However, automation requires clearly defined policies. The following questions and their answers provide guidance on how things should work.
Who approves accounts?
All users with a Linux Foundation ID and a valid email address should have access to O-RAN-SC servers and resources. Due to previous negative experiences, Linux Foundation identities using @gmail.com addresses are not approved, and accounts cannot be created with these addresses.
The OAuth approach with Linux Foundation Identity Services proved too complex, so a hybrid method involving both automated and manual approvals is now used.
Based on the current primary contributors to O-RAN-SC projects, identities with email addresses from the following domains are automatically approved:
*@att.com
*@est.tech
*@ericsson.com
*@flux.utah.edu
*@hcl.com
*@highstreet-technologies.com
*@radisys.com
*@linuxfoundation.org
*@*.ntust.edu.tw
*@nec.com
*@nokia.com
*@openairinterface.org
*@windriver.com
*@winlab.rutgers.edu
NO!!!! @gmail.com
For cases requiring manual approval, the project team leads (PTLs) [2] or the O-RAN-SC ToC Co-Chairs [3] will review and approve account identities.
Who creates OWL-projects and access groups?
OWL-Projects, which define the scope and content for resource allocation, are created by the O-RAN-SC PTLs [2]. Each project must be assigned to a specific O-RAN-SC release [4]
Who approves timelines?
Timelines are established through the release planning conducted by the O-RAN-SC RSAC. Each O-RAN-SC release has a defined timeline. Once a maintenance release concludes, the associated OWL-projects must be concluded, and the servers may be wiped.
Who resolves (equipment) conflicts?
Conflict resolution is a manual process that requires rapid communication and coordination between the OWL-Projects and O-RAN-SC Projects. The O-RAN-SC RSAC Slack is used for quick communication, and any conflicts are further discussed in O-RAN-SC RASC meetings.