Building interoperable Windows File System products is complex. This is due to several factors, some of which we’ve enumerated in this paper, but all of which interact to further complicate the problem. The result is that interoperability problems are an inherent part of creating a Windows File System product. It’s just the way the world is. It’s why Microsoft spends so much money every year hosting Plugfest sessions.
In dealing with FESF interoperability issues, OSR’s policies and recommendations are as follows:
•Establish customer expectations that interoperability problems may occur. When you DO have an interoperability issue, get us the bug report as soon as you can and collect all the data that we need. And remember: The last product that was installed before a bug was discovered is not necessarily the product that’s at fault.
•When you experience any interop issue, collect as much relevant data for us as you can up front. Always send us a description of the behaviors you’re seeing at the Windows file system level. Send us multiple crash dumps.
•When you have a Windows interoperability problem, be sure to get us specific versions. We’ll automatically prioritize the issue, and you should typically expect a resolution in the next release of FESF.
•When you contact us about an interoperability problem concerning a non-Microsoft component, get us as much data as possible when the initial problem is reported. Expect that, unless our initial triage yields a clear problem and solution, we will handle this on a “time available” basis. If interoperating with this third-party software is critical to your company, let us know. We can usually arrange to escalate an issue at an additional cost on a per-incident basis.
•When you report an interoperability problem involving a third-party product to us, always file a bug on the third-party’s product and get us the case number. Also get us any other supporting information that you can provide.
In addition to the above, when dealing with interoperability issues with Cloud Storage products, OSR’s policy and recommendations are as follows:
•We test a variety of Cloud Storage products and have qualified them to work with FESF at different levels. The “level” (L1, L2, L3) indicates the capabilities of FESF with respect to files stored by the Cloud Storage product.
•We strive to ensure that all common Cloud Storage products can coexist on the same system as FESF, and thereby achieve L1 interoperability.
•Interoperability at any given level cannot always be achieved for every product. This is because the way Cloud Storage products are implemented varies widely.
•It may take detailed analysis of a product’s behavior before you’re able to determine a workable strategy and policy for your Solution.
•OSR will provide guidance in terms of how we achieved a given level of interoperability in our testing. However, determining how your Solution can best support a given Cloud Storage product is ultimately up to you.
•We are interested to hear which Cloud Storage products are important in your market. We are open to adding additional Cloud Storage products to our interoperability testing list.