Upgrading to OneFS Target Code

NOTE: This topic is part of the Uptime Information Hub.


Your organization might be considering upgrading from your current version of OneFS to a later release so as to take advantage of serviceability and supportability enhancements. We understand that many customers can upgrade only once or twice a year. We want to ensure that when you upgrade, you can upgrade with confidence. EMC Isilon designates proven OneFS releases as Target Code to provide guidance to customers who are upgrading to a later version of OneFS. If you are considering upgrading, we encourage you to move to one of the OneFS versions designated as Target Code.


Each supported OneFS family typically has one version designated as Target Code. We designate these releases as Target Code so you know that the code has met the EMC criteria for success, and so that you can plan an appropriate upgrade path. Review the code fixes that are available in our release notes and evaluate the value of these fixes and enhancements to determine which OneFS family to upgrade to.


Our OneFS release test process


All OneFS releases are thoroughly tested. EMC Isilon has a three-phase process for testing customer bugs that we find internally:

  • We write a fix and test the functionality of the fix.
  • We reproduce the issue and test the fix against the reproduced issue.
  • We test that fix, along with other fixes that have gone through that process, through a final certification run for two weeks.


For more information about OneFS and our release test processes, see the article OneFS MRs and how we drive continuous improvement with QA.


Target code criteria


Every OneFS release is developed with the intent that it will become Target Code after it meets certain usage criteria. After a OneFS version is released, it is designated as Target Code when it meets benchmarks such as the following:


  • The number of clusters that the code is installed on
  • A minimum number of runtime hours
  • The number of clusters in small, medium, and large configurations
  • Clusters using each compatible node type
  • Clusters with each licensed OneFS feature enabled
  • Field stability
  • Low defect density


For each OneFS family, the Target Code table on the Uptime Information Hub shows:


  • The current Target Code release version
  • The total number of customers running the specified version of Target Code
  • The total number of clusters running the specified version of Target Code
  • The percentage of our overall install base that has adopted the specified version of Target Code


We strongly encourage you to upgrade to Target Code to benefit from the latest serviceability and supportability enhancements and fixes available. A OneFS release later than a Target Code release will not have accumulated enough runtime to qualify as Target Code. However, the release will have key functionality enhancements that may be valuable in your environment. A newer release might eventually become Target Code and supersede the previous Target Code version in a OneFS family once it has had enough runtime. You will need to weigh the advantages of the fixes and enhancements in a non-Target Code release versus a release designated as Target Code to determine if that release might benefit your organization.


For more information, see the OneFS Release Notes and MR Release Notes for the OneFS family that meets your organization's needs, and the Current Isilon Software Releases document. (To access these documents, you must log on to the EMC Online Support site.) Contact your account team if you have questions about what release to upgrade to.