Scope:

The purpose of this page is to provide a process for submitting requests to Product Management to determine next steps, request inclusion in the product, or escalate for further approval. Requests will be submitted in a standard format (illustrated below) to the Product Manager, at which time they will be added to the agenda of the Product Management Meeting. Please make sure to include any stakeholders that will be impacted, as well as those necessary for reaching a clear decision.

Template:

Title	Improved Readability of OST Rebalance Chart
Type	Feature Request (Feature, Bug, Proof of Concept)
Description	The OST Balance chart in IML becomes difficult to read when the number of OST's exceeds 16. Deployments exceeding 16 OST's are officially supported (reference doc) and (reference customers) have requested this functionality. The chart will need to be redesigned to facilitate readability for deployments up to and exceeding 128 OST's.
Purpose	What benefit does this feature provide?
Next Steps	What action is needed?
Priority	Medium (High, Medium, Low)
Creator	Micah Bhakti
Required Attendees	Bryon Neitzel, Mark Rogers
Status	Open, On Hold, Closed

This template will be submitted to the Product Manger via email (micah@intel.com).

TBA

Title	SAM (Service Assurance Management) integration for IML
Type	Proof of Concept
Description	Service Assurance Management is designed to provide QoS monitoring, metering, and performance analysis of nodes on a number of metrics (CPU, memory, IO) using a common platform node agent when used with IA platforms.
Purpose	Provides increased feature set when used with Intel hardware, as well as giving more data about bottlenecks and server usage.
Next Steps	Allocate a resource to work with the SAM team to setup a SAM scheduler and Node Collectors on an IEEL system and test basic functionality. Intended outcome would be to gather information about the usefulness of the data and potention benefits to IEEL product line.
Priority	Low
Creator	Micah Bhakti
Required Attendees	Micah Bhakti, Mrittika Ganguli (SAM team), Dan Ferber (or SE team resource)
Status	Open

Title	Xeon Phi Supported Lustre Client
Type	Feature
Description	Xeon Phi uses an embeded Linux OS on the card. We would like to add support for the Phi to access the Lustre FS based on Phi addoption in HPC as well as the Enterprise Technical Computing potential. To do this we will either need to support the Lustre client on the Phi Linux OS, or on the host and allow client Phi's to access the FS through the host.
Purpose	Provides Lustre FS access to Xeon Phi co-processors.
Next Steps	Lustre 2.4 working on Phi with Ethernet (MPSS 2.1), IB support waiting on new OFED stack (WW39). TT-1346 will enable automatic Lustre build with RPM's, under review now. Performance is still not where we want through virtual ethernet.
Priority	High
Creator	Micah Bhakti
Required Attendees	Micah Bhakti, Dmitry Eremin, Oleg Droken, Peter Jones
Status	Open