OpenSFS members are encouraged to submit new feature requests that will benefit their site and the larger Lustre community. The instructions below will outline how to submit a feature that will be tagged properly as an OpenSFS member submission. OpenSFS encourages members to use the tag to search and watch interesting features, as well as engage in discussion and provide input on feature submissions.
Pre-requisites:
- Submitter has a valid JIRA account: https://jira.whamcloud.com/
- If you do not have a JIRA acount – you can request one via [email protected]
- Submitter’s organization is a member of OpenSFS
- Submitter should confirm the feature is not already being worked on. This information can be found through the Lustre projects wiki page and/or a JIRA search for keywords related to the new request.
- If a feature already exists, follow steps to “watch” the LU ticket, email the ticket number to the Lustre Working Group (LWG), and offer assistance and/or input on the ticket.
If assistance is required with any of the ticket submission fields or you would like input, it is always a good idea to start with the OpenSFS Lustre Working Group mailing list ([email protected]).
Steps to submit a new feature or improvement request
- Create a new JIRA ticket at https://jira.whamcloud.com/
The following steps will describe how to fill in the appropriate fields for a successful feature request ticket. If a field isn’t described here it should be left blank. - Project: Select the appropriate project (likely LU or LUDOC). Use LUDOC for any documentation specific requests.
- Type: Select the appropriate issue type (likely feature request or improvement)
- Summary: Create a concise summary with key details included. This will be the title of the ticket. If possible, include the subsystem or tool that is impacted. An example is:
“LNET: Support IPv6” - Priority: Set the appropriate priority based on (https://jira.whamcloud.com/secure/ShowConstantsHelp.jspa?decorator=popup#PriorityLevels). It is likely major/minor.
- Description: Provide a detailed description of the feature or improvement you are requesting. The more specific details you can provide the easier it will be for others to understand the desired feature. An example description re-using the IPV6 example above:
“This improvement calls for fully supporting IPv6 throughout LNet and the LND’s. This will allow Lustre to run in IPV6 networks, in conjunction with related changes to any configuration and PtlRPC changes where NIDs are processed (e.g. config llog records, Imperative Recovery, etc.).” - Attachment: If you have pseudo code examples, diagrams, or other relevant details they can be uploaded to the ticket using the attachment button.
- Labels: Leave this blank during submission. However, it is important to note that this field will be set to “opensfs-feature” by the Lustre Working Group (LWG) to make the feature easily identifiable by LWG and OpenSFS members.
- Finalize by submitting via the create button
- Email the Lustre Working Group ([email protected] ) with the JIRA reference of the ticket
Next steps
- Once the LWG receives the JIRA reference via email, they will assign the “opensfs-feature” label after verifying all necessary information is included.
- These labeled features can be found by using this filter – https://jira.whamcloud.com/issues/?filter=17312
- OpenSFS members should use the JIRA “watch” functionality to watch the features they are most interested in.
- If you have input on a specific feature or would like further discussion beyond JIRA ticket communication, the LWG will facilitate these discussions.
- OpenSFS will track the top most watched feature requests and discuss these annually at the member meeting.
- Discussion will allow others to provide input and/or take on implementation.
- OpenSFS will present these as potential R&D topics to interested universities, companies, and community participants.
- The top 7 watched feature requests will be linked on the OpenSFS website.
- This list will be included as an agenda topic for all OpenSFS developer events.