HGST Virident Profiler for Linux User Guide Version

Transcription

1 HGST Virident Profiler for Linux User Guide Version Document Number: Document Revision: 1.01 Revision Date: 1 August 2014 Warning: Printed copies of this document are considered current only on the date of print. Replacement and disposal of down-level versions is the responsibility of the document holder.

2 1 st Edition (Revision 1.01) 1 August 2014 The following paragraph does not apply to the United Kingdom or any country where such provisions are inconsistent with local law: HGST, INC., PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer or express or implied warranties in certain transactions, therefore, this statement may not apply to you. This publication could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of this publication. HGST may make improvements or changes in any products or programs described in this publication at any time. It is possible that this publication may contain reference to, or information about, HGST products (machines and programs), programming, or services that are not announced in your country. Such references or information must not be construed to mean that HGST intends to announce such HGST products, programming, or services in your country. Technical information about this product is available by contacting your local HGST representative or on the Internet at HGST may have patents or pending patent applications covering the subject matter in this document. The furnishing of this document does not give you any license to these patents HGST, Inc., All rights reserved. ii

3 END-USER LICENSE AGREEMENT FOR HGST VIRIDENT PROFILER SOFTWARE IMPORTANT: PLEASE READ THIS END USER LICENSE AGREEMENT CAREFULLY. DOWNLOADING, INSTALLING OR USING THE ACCOMPANYING SOFTWARE CONSTITUTES ACCEPTANCE OF THIS END USER LICENSE AGREEMENT. HGST, INC. AND ITS AFFILIATES (COLLECTIVELY, HGST ) IS WILLING TO LICENSE THE SOFTWARE ONLY IF YOU ACCEPT ALL OF THE TERMS CONTAINED IN THIS END USER LICENSE AGREEMENT (THE EULA ). 1. BY DOWNLOADING, INSTALLING OR USING THE SOFTWARE OR OTHERWISE EXPRESSING YOUR AGREEMENT TO THE TERMS CONTAINED IN THIS END USER LICENSE AGREEMENT AND THE BROADER AGREEMENT (AS DEFINED BELOW), YOU INDIVIDUALLY AND ON BEHALF OF THE ENTITY THAT YOU REPRESENT (COLLECTIVELY, LICENSEE ) CONSENT TO BE BOUND BY THIS EULA AND THE AGREEMENT. IF YOU DO NOT OR CANNOT AGREE TO THE TERMS CONTAINED IN THIS AGREEMENT, THEN YOU WILL NOT HAVE ACCESS TO THE SOFTWARE. Capitalized terms used, but not defined, herein shall have the meanings given such terms in the Agreement. 2. Overview No Sale. This EULA governs Licensee s use of and access to the Software (as defined below) for any Software first placed in use on or after the release date of this EULA (the Release Date ). Licensee agrees and acknowledges that all Software is licensed and not sold, and that all use of purchase or sell in connection with any Software shall be deemed to mean license. Any term in Licensee s purchase order or other document purporting to require the sale of Software instead of the license thereof is hereby rejected by HGST and is not part of the Agreement No Implied Licenses; Licensed Material. Nothing in this EULA shall be deemed to provide to Customer any right, title or interest in (i) any product sold by HGST or an authorized reseller of HGST (a Product ); (ii) any instance of a program, module, feature, function, service, application, operation or capability of the software HGST intentionally delivers under this EULA ( Software ); or (iii) any documentation related to any Software (the Documentation ), other than the express license rights set forth in Section 4 hereof. All rights not expressly granted to Licensee are reserved by HGST and its licensors Delivery. Unless otherwise stated by HGST, Software will be delivered electronically. Delivery is considered complete when HGST provides access to the Software download. For Users who purchase multiple licenses, delivery for all licenses is complete when HGST provides access to the first copy of the Software Fees. All fees paid are non-refundable. None of the fees paid will be deemed to be a license fee, royalty, or other charge for exercise of rights granted under GPL. 3. Definitions. In this EULA, the following capitalized terms shall have the meaning set forth below: 3.1. Agreement shall have the meaning set forth in Section Affiliate of a Party means such Party s parent corporation, an entity under the control of such Party s parent corporation at any tier or an entity controlled by such Party at any tier. For these purposes, control shall mean the power to direct or cause the direction of the management and policies of the entity, whether through the ownership of more than 50% of the outstanding voting interests in such entity or otherwise Commercial Software means software that HGST intends to be used by businesses Feature means an activity or class of activities that can be undertaken by the Software GPL means the GNU General Public License, Version 2 and any later version Party means either Licensee or HGST and Parties means both Licensee and HGST Software has the meaning set forth in Section Third Party means an individual or entity other than Licensee, Licensee s Affiliates, HGST and HGST s Affiliates. iii

4 3.9. Territory means the country in which Licensee received the Software, unless otherwise specified in a purchase order agreed to by HGST Update means a new release of the Software that incorporates substantial changes or additions that (i) provide additional value and utility; (ii) may be priced and offered separately as optional additions to the Software; and/or (iii) are not generally made available to HGST s customers without a separate charge. Upgrades are generally identified by HGST by a change to the version number to the left of the first decimal point (e.g., version 3.2 to 4.0) Upgrade means a new release of the Software that incorporates substantial changes or additions that (i) provide additional value and utility; (ii) may be priced and offered separately as optional additions to the Software; and/or (iii) are not generally made available to HGST s customers without a separate charge. Upgrades are generally identified by HGST by a change to the version number to the left of the first decimal point (e.g., version 3.2 to 4.0) User means an individual able to use or gain access to any Software functionality. 4. License Grant Grant. Subject to the terms and conditions of this Agreement, HGST hereby grants to Licensee, and Licensee accepts, upon delivery of the Software, a nonexclusive, perpetual, worldwide license to install and use each copy of the Software pursuant to the GPL. Licensee is permitted to run, copy, modify, and redistribute the Software, subject to the obligations provided in the GPL, both in source code and binary code forms, with the exception of certain binary only firmware components Network Usage. Licensee understands and agrees that HGST may use Licensee s internal network and Internet connection for the limited purpose of transmitting license-related data at the time of installation, registration, use or update of Software to a HGST-operated license server. At such time, HGST may validate the license-related data in order to protect HGST against unlicensed or illegal use of the Software Updates and Upgrades. (a) Upgrades. Upgrades to the Software may be made available to Licensee pursuant to a separate agreement between HGST and Licensee. Any Upgrade provided by HGST shall be licensed under the terms of the Software that is being upgraded by such Upgrade (b) No Obligation. Nothing in this EULA requires HGST to provide Updates or Upgrades to Licensee or Licensee to accept such Updates or Upgrades. The provision of any Upgrades shall be governed by a separate agreement between HGST and Licensee, or by a purchase order issued by Licensee and accepted by HGST, in HGST s sole discretion, and may require the payment of additional fees Third-Party Software. Portions of the Software may be owned by one or more Third Parties and licensed to HGST. HGST and Licensee intend and agree that Software owned by Third Parties and supplied hereunder is being sublicensed to Licensee, that such Third Parties retain ownership of and title to such Software, and that such Third Parties may directly enforce Licensee s obligations hereunder to protect their respective interests in such Software. The warranty and indemnification provisions set forth herein shall not apply to Software owned by Third Parties and supplied hereunder. If portions of the Software are owned by one or more Third Parties, the licenses/terms applicable to such Third Party licenses are set forth in Exhibit A. UNLESS OTHERWISE AGEED TO BY THE THIRD PARTY, TO THE MAXIMUM EXTENT PERMITTED BY LAW, THIRD PARTY SOFTWARE COMPONENTS AND DOCUMENTATION ARE PROVIDED AS IS. NEITHER HGST NOR THE THIRD PARTY PROVIDER MAKES ANY WARRANTY RELATED TO THE THIRD PARTY SOFTWARE COMPONENT, STATUTORY, EXPRESS OR IMPLIED, AND EACH SPECIFICALLY DISCLAIMS THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT WITH RESPECT TO THE SOFTWARE AND THE DOCUMENTATION. iv

5 4.5. Product-Specific Terms. (a) Commercial Software Audit. Licensee hereby grants to HGST, itself or using an independent third party auditor, the right to audit Licensee s books, records and systems during normal business hours upon seven (7) days prior written notice, no more often than once per annum regarding the usage of Commercial Software under the Agreement. In the event such audit identifies material non-compliance with this EULA or the Agreement between Licensee and HGST, Licensee shall pay HGST s costs of such audit. 5. Software Warranty. TO THE MAXIMUM EXTENT PERMITTED BY LAW, EXCEPT AS PROVIDED FOR IN THE AGREEMENT, THE SOFTWARE AND DOCUMENTATION ARE PROVIDED AS IS. HGST MAKES NO OTHER WARRANTIES, STATUTORY, EXPRESS OR IMPLIED, AND SPECIFICALLY DISCLAIMS THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT WITH RESPECT TO THE SOFTWARE AND THE DOCUMENTATION. IN ADDITION, HGST DOES NOT WARRANT THAT THE SOFTWARE S OPERATION WILL BE UNINTERRUPTED OR ERROR-FREE, OR THAT ALL DEFECTS WILL BE CORRECTED. 6. Exclusive Remedies and Limitation of Liability Definitions. For purposes of the exclusive remedies and limitations of liability set forth in this Section 8, HGST shall be deemed to include its directors, officers, employees, agents, representatives, shareholders, subcontractors, licensors and suppliers; and damages shall be deemed to refer collectively to all injury, damage, loss or expense incurred Maximum Liability. Except as may otherwise be provided in the Agreement, HGST s maximum aggregate liability arising from or relating to this EULA or the use of the Software and Products shall not exceed the total amount paid by Licensee to HGST for the applicable Software during the twelve (12) month period that immediately preceded the event that gave rise to the applicable claim Limitation of Liability. NOTWITHSTANDING ANY OTHER PROVISION OF THIS EULA BUT SUBJECT IN ALL RESPECTS TO THE AGREEMENT, TO THE MAXIMUM EXTENT PERMITTED BY LAW, HGST SHALL NOT BE LIABLE FOR INCIDENTAL, SPECIAL, EXEMPLARY, CONSEQUENTIAL OR OTHER INDIRECT DAMAGES, INCLUDING BUT NOT LIMITED TO THE COST OF PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES, LOSS OF DATA, LOSS OR INTERRUPTION OF USE, LOST PROFITS, SAVINGS OR REVENUES OF ANY KIND, WHETHER OR NOT HGST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THIS PROVISION SHALL APPLY EVEN IN THE EVENT OF THE FAILURE OF AN EXCLUSIVE REMEDY. 7. Miscellaneous Choice of Law; Jurisdiction. The Agreement shall be governed by the laws of the State of California, excluding (a) its conflicts of law rules that would result in the application of the law of any other jurisdiction; and (b) the United Nations Convention for the International Sale of Goods. The federal and state courts located in San Jose, California shall have exclusive jurisdiction with respect to any dispute arising under this Agreement Assignment. Either Party may assign this EULA to any Affiliate of the other or to an acquirer (by purchase, merger or otherwise) of all or substantially all of such Party s business or assets relating to this EULA, provided that the assignee agrees in writing to be bound by the terms and conditions of this EULA. Any attempted assignment other than as permitted shall be null and void Order of Precedence; Entire Agreement. To the extent of any conflict among this EULA, any additional terms in an agreement signed by Licensee and HGST, any HGST click-accept agreement, any terms on a purchase order and HGST s terms and conditions of sale, the order of precedence shall be (a) this EULA; (b) an agreement signed by Licensee and HGST; (c) a clickaccept agreement, including any agreement regarding the Features to be included as part of the Software; (d) HGST s terms and conditions of sale; and (e) HGST s purchase order acceptance (collectively, (a)-(e), after applying the order of precedence, the Agreement ). The terms and conditions contained in the Agreement supersede all prior oral or written understandings between v

6 the Parties and shall constitute the entire agreement between the Parties with respect to the subject matter of the Agreement. This Agreement shall not be modified or amended except by a writing signed by Licensee and HGST Construction; Severability. The headings used in this Agreement are for reference purposes only and will not be deemed to limit, expand or in any way affect the interpretation of any term or provision hereof. If any provision or part hereof shall be held to be invalid or unenforceable for any reason, then the meaning of such provision or part hereof shall be construed so as to render it enforceable to the extent feasible. If no feasible interpretation would save such provision or part hereof, it shall be severed herefrom, but without in any way affecting the remainder of such provision or any other provision contained herein, all of which shall continue in full force and effect unless such severance effects such a material change as to render the Agreement unreasonable. vi

7 EXHIBIT A The Software contains open source components. Please refer to the table below for the open source components and the associated license(s) for the terms and conditions for their use. The source code for the components listed in Table 1 below may be obtained from HGST. Please contact support@virident.com for further information. HGST may provide the open source code to you on a physical storage medium for a charge covering the cost of performing such distribution, such as the cost of media, shipping and handling. Table 1 License Component GPL v2.0 Flashcache; Pyinstaller 2.0 Please also be informed that the Software may contain other Third Party Software listed in the Table 2. Table 2 License Component Copyright Notice MIT mootools.js Copyright Valerio Proietti jquery-latest.js jquery min.js jquery.cookie.js jquery.jeegoocontext.min.js jquery.js jquery-ui-timepicker-addon.js Copyright 2011 John Resig Copyright 2011 The Dojo Foundation Copyright 2011 Klaus Hartl Copyright Erik van den Berg Copyright 2009 John Resig Copyright 2014 Trent Richardson Python 2.7 Python 2.7 Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006 Python Software Foundation; All Rights Reserved. BSD Django 1.3 Copyright (c) Django Software Foundation and individual contributors. CherryPy treestyler.js Copyright (c) CherryPy Team (team@cherrypy.org) See HGST product support web page Python Python-ldap See PyWin See vii

8 GNU GENERAL PUBLIC LICENSE Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. 51 Franklin Street, Fifth Floor, Boston, MA , USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software- -to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Lesser General Public License instead.) You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you". Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does. 1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy viii

9 of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. 2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.) These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. 3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.) The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code. ix

10 4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. 5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it. 6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License. 7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. 8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. 9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation. 10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. x

11 NO WARRANTY MIT -jquery 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Copyright 2012 jquery Foundation and other contributors Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Python 2.7 License This is the official license for the Python 2.7 release. A. HISTORY OF THE SOFTWARE Python was created in the early 1990s by Guido van Rossum at Stichting Mathematisch Centrum (CWI, see in the Netherlands as a successor of a language called ABC. Guido remains Python's principal author, although it includes many contributions from others. In 1995, Guido continued his work on Python at the Corporation for National Research Initiatives (CNRI, see in Reston, Virginia where he released several versions of the software. In May 2000, Guido and the Python core development team moved to BeOpen.com to form the BeOpen PythonLabs team. In October of the same year, the PythonLabs team moved to Digital Creations (now Zope Corporation, see In 2001, the Python Software Foundation (PSF, see was formed, a non-profit organization created specifically to own Python-related Intellectual Property. Zope Corporation is a sponsoring member of the PSF. xi

12 All Python releases are Open Source (see for the Open Source Definition). Historically, most, but not all, Python releases have also been GPL-compatible; the following table summarizes the various releases. Release Derived From Year Owner GPL-Compatible? (1) thru CWI Yes 1.3 thru CNRI Yes Footnotes: CNRI No BeOpen.com No CNRI Yes (2) PSF No PSF Yes PSF Yes PSF Yes PSF Yes PSF Yes PSF Yes PSF Yes PSF Yes PSF Yes PSF Yes PSF Yes PSF Yes PSF Yes PSF Yes PSF Yes PSF Yes PSF Yes PSF Yes PSF Yes PSF Yes 1. GPL-compatible doesn't mean that we're distributing Python under the GPL. All Python licenses, unlike the GPL, let you distribute a modified version without making your changes open source. The GPL-compatible licenses make it possible to combine Python with other software that is released under the GPL; the others don't. 2. According to Richard Stallman, is not GPL-compatible, because its license has a choice of law clause. According to CNRI, however, Stallman's lawyer has told CNRI's lawyer that is "not incompatible" with the GPL. Thanks to the many outside volunteers who have worked under Guido's direction to make these releases possible. xii

13 B. TERMS AND CONDITIONS FOR ACCESSING OR OTHERWISE USING PYTHON PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2 1. This LICENSE AGREEMENT is between the Python Software Foundation ("PSF"), and the Individual or Organization ("Licensee") accessing and otherwise using this software ("Python") in source or binary form and its associated documentation. 2. Subject to the terms and conditions of this License Agreement, PSF hereby grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use Python alone or in any derivative version, provided, however, that PSF's License Agreement and PSF's notice of copyright, i.e., "Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006 Python Software Foundation; All Rights Reserved" are retained in Python alone or in any derivative version prepared by Licensee. 3. In the event Licensee prepares a derivative work that is based on or incorporates Python or any part thereof, and wants to make the derivative work available to others as provided herein, then Licensee hereby agrees to include in any such work a brief summary of the changes made to Python. 4. PSF is making Python available to Licensee on an "AS IS" basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 6. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 7. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between PSF and Licensee. This License Agreement does not grant permission to use PSF trademarks or trade name in a trademark sense to endorse or promote products or services of Licensee, or any third party. 8. By copying, installing or otherwise using Python, Licensee agrees to be bound by the terms and conditions of this License Agreement. BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0 BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1 1. This LICENSE AGREEMENT is between BeOpen.com ("BeOpen"), having an office at 160 Saratoga Avenue, Santa Clara, CA 95051, and the Individual or Organization ("Licensee") accessing and otherwise using this software in source or binary form and its associated documentation ("the Software"). 2. Subject to the terms and conditions of this BeOpen Python License Agreement, BeOpen hereby grants Licensee a non-exclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use the Software alone or in any derivative version, provided, however, that the BeOpen Python License is retained in the Software, alone or in any derivative version prepared by Licensee. 3. BeOpen is making the Software available to Licensee on an "AS IS" basis. BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 4. BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT xiii

14 OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 5. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 6. This License Agreement shall be governed by and interpreted in all respects by the law of the State of California, excluding conflict of law provisions. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between BeOpen and Licensee. This License Agreement does not grant permission to use BeOpen trademarks or trade names in a trademark sense to endorse or promote products or services of Licensee, or any third party. As an exception, the "BeOpen Python" logos available at may be used according to the permissions granted on that web page. 7. By copying, installing or otherwise using the software, Licensee agrees to be bound by the terms and conditions of this License Agreement. CNRI LICENSE AGREEMENT FOR PYTHON This LICENSE AGREEMENT is between the Corporation for National Research Initiatives, having an office at 1895 Preston White Drive, Reston, VA ("CNRI"), and the Individual or Organization ("Licensee") accessing and otherwise using Python software in source or binary form and its associated documentation. 2. Subject to the terms and conditions of this License Agreement, CNRI hereby grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use Python alone or in any derivative version, provided, however, that CNRI's License Agreement and CNRI's notice of copyright, i.e., "Copyright (c) Corporation for National Research Initiatives; All Rights Reserved" are retained in Python alone or in any derivative version prepared by Licensee. Alternately, in lieu of CNRI's License Agreement, Licensee may substitute the following text (omitting the quotes): "Python is made available subject to the terms and conditions in CNRI's License Agreement. This Agreement together with Python may be located on the Internet using the following unique, persistent identifier (known as a handle): /1013. This Agreement may also be obtained from a proxy server on the Internet using the following URL: 3. In the event Licensee prepares a derivative work that is based on or incorporates Python or any part thereof, and wants to make the derivative work available to others as provided herein, then Licensee hereby agrees to include in any such work a brief summary of the changes made to Python CNRI is making Python available to Licensee on an "AS IS" basis. CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 5. CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 1.6.1, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 6. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 7. This License Agreement shall be governed by the federal intellectual property law of the United States, including without limitation the federal copyright law, and, to the extent such U.S. federal law does not apply, by the law of the Commonwealth of Virginia, excluding Virginia's conflict of law provisions. Notwithstanding the foregoing, with regard to derivative works based on Python that incorporate non-separable material that was previously distributed under the GNU General Public License (GPL), the law of the Commonwealth of Virginia shall govern this License Agreement only as to issues arising under or with respect to Paragraphs 4, 5, and 7 of this License xiv

15 Agreement. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between CNRI and Licensee. This License Agreement does not grant permission to use CNRI trademarks or trade name in a trademark sense to endorse or promote products or services of Licensee, or any third party. 8. By clicking on the "ACCEPT" button where indicated, or by copying, installing or otherwise using Python 1.6.1, Licensee agrees to be bound by the terms and conditions of this License Agreement. CWI LICENSE AGREEMENT FOR PYTHON THROUGH 1.2 Copyright (c) , Stichting Mathematisch Centrum Amsterdam, The Netherlands. All rights reserved. Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Stichting Mathematisch Centrum or CWI not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. BSD -Django Copyright (c) Django Software Foundation and individual contributors. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer in the documentation and /or other materials provided with the distribution. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Neither the name of Django nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. xv

16 CherryPy Copyright (c) , CherryPy Team All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of the CherryPy Team nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. xvi

17 Conventions The following icon and text conventions are used throughout this document to identify additional information of which the reader should be aware. Conventions Description CAUTION NOTE This icon denotes the use of extreme caution and the user must exercise good judgment according to previous experience before advancing to the next procedure. The icon also indicates the existence of a hazard that could result in equipment or property damage, or equipment failure if the instructions are not observed. This icon identifies information that relates to the safe operation of the equipment or related items. Bold. Text Used to indicate important technical notes. Bold Italic Text Used to indicate critical instructions. Light Blue Italic Text Used to indicate a hyperlink or jump to a related section or subsection. xvii

18 Table of Contents Introduction Audience Features Specifications Documentation Key Concepts and Terms What is a Cache Volume? HGST Virident ServerCache SSDs and SSAs Interfaces What is HGST Virident Profiler? Installation Prerequisites System Hardware Requirements HGST Virident Profiler Installation Uninstalling HGST Virident Profiler Starting HGST Virident Profiler Local Server Client System Desktop Icon Login Prompt Navigating the Web GUI Menus Side Menu Rescan Button Side Menu Icons Top Menu Tabs More Menu Getting Help Help Button ScreenTips Service Log File Basic Operations Home Page Configuration Settings General Settings Panel LDAP Settings Panel SSL Settings Panel Log Settings Panel Activity Log Settings Restarting HGST Virident Profiler Services Displaying the Volume Information Rescan Button Profiling an HDD Volume Schedule the Profiling Session Multiple SSD Type Selection SSD Usage Starting or Scheduling a Trace Operation Duration Recommend Best SSD xviii

19 SSD Type Custom SSD Options Start Trace Stop Trace Stop and Analyze Viewing the Trace Results Recommended Cache Configurations Response Time Improved Details I/O Statistics for the Profiled Source Volume Activity Logs Logging Out of HGST Virident Profiler Glossary FAQ Troubleshooting Contact Information General Information Technical Support Index xix

20 List of Figures Figure 1: HGST Virident Profiler Figure 2: Typical Caching Scheme Figure 3: HGST Virident ServerCache User Interaction Figure 4: Trace Results for a Profiled Source Volume Figure 5: Recommended Cache Configurations Figure 6: Charted I/O Profile Statistics Figure 7: Login Prompt Figure 8: HGST Virident Profiler Web GUI Figure 9: Top Menu Tabs Figure 10: The Home Page Figure 11: The Settings Page Figure 12: General Settings Panel Figure 13: LDAP Settings Panel Figure 14: SSL Settings Panel Figure 15: Log Settings Panel Figure 16: Activity Log Settings Panel Figure 17: Displaying the Volume Information Figure 18: Scheduling the Profiling Session Figure 19: Specifying the Trace Parameters Figure 20: Specifying a Custom SSD for Profiling Figure 21: Traced Information Figure 22: Recommended Cache Configurations Figure 23: Response Time Improved Details Figure 24: I/O Statistics for the Profiled Source Volume Figure 25: The Activity Logs Page Figure 26: Logging out of HGST Virident Profiler xx

21 List of Tables Table 1: Volume Icon Descriptions Table 2: Home Page Summary Items Table 3: General Settings Options Table 4: LDAP Settings Options Table 5: SSL Settings Options Table 6: Log Settings Options Table 7: Activity Log Settings Options Table 8: Volume Information Page Table 9: Activity Logs Options Table 10: Glossary of Terms xxi

22 Introduction Figure 1: HGST Virident Profiler Welcome to HGST Virident Profiler. HGST Virident Profiler allows you to forecast the overall SSD cache or the primary HDD storage performance improvement derived from the SSD Usage specified for the workload that occurs on a given HDD source volume. You can install HGST Virident Profiler before you use HGST Virident ServerCache to review recommendations on the required cache configurations or performance improvements according to the SSD Usage. While IT organizations have embraced the benefits of solid-state technology, many server environments cannot simply replace hard disk drives with SSDs to achieve increased performance and scalability. For these enterprise server environments, HGST Virident ServerCache is a solution that enables applications to utilize the performance benefits of SSDs and SSAs without the need for major IT infrastructure changes. HGST Virident ServerCache provides the ability to easily create, configure and analyze cached environments with cost-effective scalability using SSD and SSA devices. Each IT environment is unique, so the actual cache performance is dependent upon various runtime factors such as I/O subsystem configuration, number of OS threads engaged in I/O operations, compressibility of data, RAM size, and the cache configuration itself. 22

23 Audience This user guide is intended for system administrators, network administrators, and other IT professionals. It is therefore written specifically for a technically advanced audience. Features Feature Multiple SSD Type Selection Profiling with SSD as Cache Device Benefit Allows selection of multiple SSD Types for simultaneous profiling of the same workload running on a given primary storage device. This feature makes it easier to compare performance improvement predictions for different SSD Types with the same workload. Identifies opportunities for cache performance optimization and recommends cache configurations for specific workloads. Profiling with SSD as Primary Storage Identifies opportunities for primary storage performance improvements for specific workloads. Profiling Session Scheduling Low System Resource Utilization Allows user to schedule tracing and analysis phases at specific times depending upon the system workload. Integrates with existing environment with minimal impact on system resource utilization and has a low memory footprint. Specifications Specification HGST Virident Profiler Overview Solid State Device Compatibility Operating Systems Red Hat Enterprise Linux CentOS System RAM Utilization Supported Web Browsers Microsoft Internet Explorer Mozilla Firefox Google Chrome Description Software solution that is independent of hardware and provides profiling solution with recommendations for cache configurations or performance improvements on primary storage. Supports any SAS, Fibre Channel, PCIe and SATA solid-state device or drive. RHEL 6.0, 6.1, 6.2, 6.3, 6.4, 6.5; 64-Bit CentOS 6.0, 6.1, 6.2, , 6.5; 64-Bit 0.1% or 100MB for a 100GB SSD cache. Internet Explorer 9.x or higher Firefox 3.6 or higher Chrome 24.0 or higher Documentation Title Part Number Description Comprehensive user guide. 23

24 Key Concepts and Terms This section presents various concepts and terms that are important to understand before implementing HGST Virident Profiler in your system; hence, this section is a very broad in its scope. It is not possible to specifically cover every scenario or application that you may encounter. This section will present only the basic concepts within context to help provide an intuitive understanding of HGST Virident Profiler. What is a Cache Volume? A cache volume is a combination of low-latency solid-state devices used to temporarily store data and software that is used to create, monitor and manage the cache. The cache volume can increase the number of storage IOPs (especially reads) and reduce data access latency. A cache volume can transparently accelerate the performance of most applications. Figure 2 shows a typical hardware scenario deployed as a caching solution. The cache volume is created by mapping the source HDD volume to a SSD or SSA. Figure 2: Typical Caching Scheme In the preceding scenario, the application server will request data from the storage subsystem. The cache software will determine whether the requested data is in the cache. If the data is found in the cache, a cache hit occurs and the data is immediately served to the application; however, if a cache miss occurs (the data was not found in the cache), the data is fetched from the source HDD volume, which increases the data access time. If the application server writes data to the HDD volume, the cache behavior is dependent upon the supported cache mode. HGST Virident ServerCache supports write-through and write-back caching: Write-Through: The writes flow through the source HDD volume and the cache software will acknowledge a successful write to the application server once it receives a write-success status from the source HDD volume and SSD. Write-Back: Asynchronous writes are made to the cache and are written to the source HDD volume in the background. 24

25 HGST Virident ServerCache HGST Virident ServerCache provides the interface between the user and the cache. It is HGST Virident ServerCache that allows the user to create and manage the cache, and HGST Virident Profiler conducts real-time performance analysis. SSDs and SSAs Figure 3: HGST Virident ServerCache User Interaction SSDs and SSAs usually comprise the hardware components of a cache. SSDs and SSAs are considered low-latency devices, i.e., since these are solid-state devices, there are no moving parts. SSDs and SSAs have no actuator mechanisms, read/write heads, or rotating platters. There is no seek time or rotational latency. The access time may be affected by the operating system environment and storage capacity. Mechanical shock, vibration or gravitation forces do not affect the transaction throughput. The performance rates of SSDs and SSAs are dependent upon several factors. The interface (SAS, FC, SATA or PCIe), capacity, configuration parameters, traffic patterns and NAND type (MLC or SLC) all impact the performance, and you should be aware that an SSD or SSA of a specific capacity and configuration may result in lower or higher performance characteristics. 25

26 Interfaces As previously mentioned, SSDs and SSAs are available in a variety of interfaces, including SATA (Serial ATA), SAS (Serial-Attached SCSI), iscsi (Internet SCSI), FC (Fibre Channel) and PCIe (Peripheral Component Interconnect Express or PCI Express). Each interface has a different price and performance cost. A flexible caching solution provides the user with options to tradeoff solid-state performance and cost to meet application performance and budget requirements. What is HGST Virident Profiler? The HGST Virident Profiler, also known as Profiler, allows you to forecast the overall cache or primary storage performance improvement derived from the SSD Usage specified for the workload that is running on a given source volume. You can simultaneously forecast performance improvements for a given source volume for a set of SSD Types. For example, in Figure 4, Profiler was used to forecast the cache performance between a given source volume and an SSD (Virident FlashMAX II Performance PCIe) that will be used for the cache. A new trace and corresponding analysis were scheduled with a specific duration. The Traced Information includes the number of read/write operations and the number of bytes read/bytes written in gigabytes. Profiler will generate estimated recommendations according to the selected SSD Type(s) and specified SSD Usage (SSD as Cache Device or SSD as Primary Storage). Figure 4: Trace Results for a Profiled Source Volume Profiler uses device performance data to model the potential performance improvement of a device. The actual performance improvement for a device may vary from predictions made by Profiler, depending upon the operating environment and manner of use. 26

27 Figure 5 is an example of the Recommended Cache Configuration(s) that were extrapolated from a trace. The results can be analyzed as follows: Figure 5: Recommended Cache Configurations For each Cache Mode (Write Back or Write Through), there is a recommended Cache Size (GB), Block Size (KB)#, %Read Hits and %Write Hits. You can then extrapolate, according to the charts and suggested cache size, the best cache configuration, thereby allowing you to create a new cache volume for the selected source volume. Figure 6 shows the charts in the IO Statistics panel. These charts provide a visual reference of the profiled source volume. Figure 6: Charted I/O Profile Statistics 27

28 Prerequisites Installation This section addresses the issues regarding the compatibility, system requirements, installation and configuration of the software. The installation utility will prompt you to install the prerequisite software if it is not found on the system. The prerequisite software described below should be installed and configured before you install HGST Virident Profiler. Prerequisite Description Operating System Red Hat Enterprise Linux CentOS User Privileges RHEL 6.0, 6.1, 6.2, , 6.5; 64-Bit CentOS 6.0, 6.1, 6.2, 6.3, 6.4, 6.5; 64-Bit Root System Hardware Requirements Item CPU Memory HDD Requirements Optical Drive Network Display Peripherals Description Intel Xeon or equivalent 64-bit processor, 1.4GHz clock speed or higher. 512MB RAM minimum. 10GB available disk space minimum. CD-ROM/DVD-ROM drive optional. Internet connection required for downloads and upgrades. Super VGA (1024 x 768) or higher-resolution monitor. Keyboard and Mouse (Printer optional). 28

29 HGST Virident Profiler Installation The installation utility will install and configure HGST Virident Profiler. 1. Login to the system with root privileges. 2. Unpack the profiler_ _xxxx.tar.gz file using the tar command: #./tar -xvfz profiler_ _xxxx.tar.gz 3. When unpacked, the package creates a folder with the package name. Change the current directory to that folder. 4. Run the following script: #./profiler_setup.sh install. 5. The Press any key to continue prompt will appear. Press any key to continue. 6. The End-User License Agreement will appear. Press Enter until you scroll to the end of the EULA and the I accept the terms of the End-User License Agreement. (Yes/No) prompt appears. You must accept the terms of the license agreement to proceed with the installation. Press Y for Yes and then press Enter to continue. 7. The installer will perform a check for the required prerequisite software packages. 8. The following system message will appear: Checking For Required Packages 9. The following message will appear: [Install] HGST Virident Profiler. 10. You will be prompted for the port number. The default is Enter port number for Profiler Web GUI. ( ) [9001] 11. If you want a shortcut icon on the desktop, select the appropriate option; Y (Yes) or N (No) for the following question: Create shortcut to HGST Virident Profiler Web GUI on root/desktop/? (Yes/No) [Yes] 12. Press Y for Yes to continue. The installation process installs the executables in the /usr/sbin/ directory. 29

30 Uninstalling HGST Virident Profiler You can uninstall the software using the following steps: 1. Log onto the system with root privileges. 2. Change directory to /usr/share/virident/. 3. Run the following command: #./profiler_setup.sh uninstall. 4. Select all the default options to uninstall the software. 5. The uninstall process will delete all the installed files. Starting HGST Virident Profiler You can use the Local Server and Client System methods, or the Desktop Icon to start and Login to HGST Virident Profiler. Make sure to specify the correct <PORT NUMBER> in the URL. The Profiler Web GUI can be accessed from any other system on the network, provided the correct IP address is specified. Login to Profiler using administrator account credentials. If you have enabled SSL (Secure Sockets Layer), then you must use (Hypertext Transfer Protocol Secure or HTTPS) in the address. Local Server If you want to access Profiler remotely, make sure to add a firewall exception for the specified port. To access Profiler from the local server, point your browser to the server IP address, e.g., NUMBER> and then Login to HGST Virident Profiler. Client System To access Profiler from a network client, you must use the server IP address or hostname, e.g., NUMBER> or NUMBER> and then Login to HGST Virident Profiler. Desktop Icon A Profiler icon appears on the system desktop after a successful installation. You may double-click the desktop icon to launch the software and then Login to HGST Virident Profiler. 30

31 Login Prompt The Web GUI will appear in the default browser window after loading, and you are prompted to log into the system. Enter your Username and Password and then click the Login button to access HGST Virident Profiler. The Home page will appear after you login. Only administrators, LDAP users, and users that have root privileges are allowed to login. Figure 7: Login Prompt Users must be in the root group or have sudo access to login. For sudo RHEL support, the Defaults!requiretty line should be commented out in the file /etc/sudoers; however, you can choose to selectively override users/groups, rather than removing the!requiretty default for all users/groups. If you want to allow certain users/groups, then you would add: Defaults: user Defaults:%group!requiretty!requiretty 31

32 Navigating the Web GUI Figure 8: HGST Virident Profiler Web GUI The Web GUI of HGST Virident Profiler provides an intuitive interface for all user interaction with the system. You can profile volumes to determine the best cache configurations for your system using only a few steps and forecast the results according to each cache mode. 32

33 Menus The Web GUI is divided into two main elements: a Side menu containing volume icons and a Top menu that consists of a series of tabs. You want to select a volume icon in the Side menu first; the Top menu tabs are context-sensitive and will update to display the relevant pages for the selected volume. Side Menu The Side menu is comprised of a Volumes list along the left side of the interface and will display all the SSDs, SSAs and HDDs that are installed in the system and that were automatically detected by Profiler. The list is comprised of Device Names and Device Icons that indicate the volume type. Icons that appear grayed-out indicate that the device is unavailable for caching. See Rescan Button and Side Menu Icons. Rescan Button Side Menu Icons The Rescan button to the right of the Volumes label is used to update the list if there are any changes to the hardware configuration or the cache. As per the selection on the Side menu, the relevant Top menu tabs will update. The Side menu contains the following volume icons as shown in Table 1. Icons that appear grayed-out indicate that the device is unavailable for caching. Icon Volume Type Description Table 1: Volume Icon Descriptions HDD SSD/SSA Unsupported SSD Unsupported Volume An HDD (Hard Disk Drive). An SSD (Solid-State Drive or Solid-State Device) or SSA (Solid- State Accelerator). This grayed-out icon indicates that the SSD or SSD partition cannot be used as a cache volume. This grayed-out icon indicates that the source volume, for various reasons, cannot support cache creation. 33

34 Top Menu Tabs The Top menu will display context-sensitive tabs according to the volume type selected in the Side menu. The tabs provide you with the features to manage the profiling of the volume as per the volume type. All user actions, such as viewing the volume details, and profiling the volumes are available on the respective tabs. More Menu Figure 9: Top Menu Tabs The More Menu appears after the Help button in the menu bar. The drop-down menu allows for quick navigation through the interface. You can quickly view the Home page or Settings page, view the activity logs, or logout of the system. See: Home Page Activity Logs Settings Logout Getting Help If you require assistance, you can use the Help button, access the on-line user guide, or display the ScreenTips. Help Button ScreenTips Click the Help button to open the user guide. If you click the Help button while viewing a specific page, the related topic will open in the web browser. For example, if you are viewing the Settings page, and click the Help button, the user guide will open to the Configuration Settings topic. You can navigate the user guide like you would any HTML web page. You will notice ScreenTip icons in the Web GUI. If you hover the mouse pointer over a ScreenTip icon, the pointer becomes a hand icon and a ScreenTip will appear. Service Log File The Web Service maintains all service-related logs in the service.log file. The log file is located in the /var/log/virident/profiler folder. The log file is recreated whenever you start the Web Service. 34

35 Basic Operations This section describes the basic functionality of Profiler. You can determine how many volumes are installed in a system, the types of volumes, view statistical information, and profile the volumes. Home Page The Home page will appear after you login to Profiler. The Home page presents a summary of the volumes, profiling status, software and server details and links. Table 2 lists the information that appears in each of the panels. If necessary, you can select Home from the drop-down More Menu to display the page, or double-click the logo in the top right-hand corner of the Web GUI. Figure 10: The Home Page Table 2: Home Page Summary Items Panel Description Volumes Summary Number of available SSD volumes Number of available HDD volumes The number of available SSD volumes that can be used for caching installed in the server. The number of available HDD volumes that can be mapped to an SSD or SSA caching device installed in the server. Software and Server Details Version Server Name Operating System The current software version and build. The name of the server on which Profiler is currently running. The operating system version and build. 35

36 Profiler Status Device Phase The current status of profiling. The Profiler panel will list any profiles that you have performed. There are three columns within the Profiler Status panel: Device, Phase and % Completed. Lists the name of each device that is being profiled or was profiled. The current status of the trace. Tracing indicates that the system is currently undergoing analysis; Profiled indicates that the trace operation has finished and the results are available for analysis. Analyzing indicates that the system is currently performing analysis. % Completed Displays as a percentage the completion phase of the profile. Trace Data Click the Download hyperlink(s) in the Trace Data column to download the trace file for the profiled volume(s). Links HGST Virident Profiler Support Click this link to go to 36

37 Configuration Settings You can determine the current configuration using the Settings page. Select Settings from the drop-down More Menu to display the page The Settings page is divided into General Settings, LDAP Settings, SSL Settings, Log Settings, Activity Log Settings, and Graph Statistics Settings panels. If necessary, you can update the settings. See Restarting HGST Virident Profiler Services. For any field marked with a number sign or pound sign (#), you should restart the HGST Virident Profiler Service to apply the settings. For any field marked with an asterisk (*), a re-login is required for the changes to take effect. Figure 11: The Settings Page 37

38 General Settings Panel The General Settings panel allows you to specify the GUI Port, Session Timeout (minutes) and Profiler Trace File Path. Figure 12: General Settings Panel Table 3: General Settings Options Option GUI Port Session Timeout (minutes) Profiler Trace File Path Description The current port number appears in this field. The default is 9001, but you can enter any valid port number in the field. The default session timeout value of 30 minutes appears in this field. You can enter a value from 1 (one minute) to 20,160 minutes (14 days). The current (default) path of the trace file as generated by Profiler appears in this field. You can enter any valid path in the text box. 38

39 LDAP Settings Panel The LDAP (Lightweight Directory Access Protocol) Settings panel allows you to specify the Server Hostname, Server Port, Base DN (Base Domain Name), Domain, and Groups. You can also specify the user name and password, and test the LDAP configuration. Figure 13: LDAP Settings Panel Table 4: LDAP Settings Options Option Server Hostname Server Port Base DN Domain Groups Test LDAP Settings Username Password Description The name of the current LDAP Server appears in this field, but you can change it by entering any valid LDAP server name. The current port number for the LDAP server appears in this field, but you can enter any valid port number. The current base domain name for the LDAP server appears in this field, but you can enter any valid domain name. The current domain for the LDAP server appears in this field, but you can enter any valid domain name. You can enter LDAP group names in this field. Each group name must be separated by a comma. Place a check mark in the Test LDAP Settings check box if you plan to test the LDAP configuration. Enter the user name for the LDAP connection in this field. Enter the user password for the LDAP connection in this field. Click the Test Connection button to ensure the LDAP configuration is functioning. 39

40 SSL Settings Panel The SSL Settings panel allows you to enable SSL (Secure Sockets Layer) for HTTPS (Hypertext Transfer Protocol Secure) activation. You must specify the FQDN (Fully Qualified Domain Name), and the paths to the Certificate File and the Certificate Key File. Figure 14: SSL Settings Panel Table 5: SSL Settings Options Option SSL Enabled FQDN Certificate File Certificate Key File Description Place a check mark in the SSL Enabled check box to activate HTTPS. Type the Fully Qualified Domain Name in this text box. The path of the certificate file. The path of the certificate key file. 40

41 Log Settings Panel The Log Settings panel allows you to specify the logging level, the maximum size of the log files, and the maximum number of log files Profiler can generate. The default values are the recommended settings. Figure 15: Log Settings Panel Table 6: Log Settings Options Option Logging Level Description You can select one of five logging levels from the drop-down list: Verbose, Info, Warning, Notice and Error. Maximum Log File Size (KB) Number of Rotate Log Files Option Verbose Info Warning Notice Error Description Logs all messages. Logs all informational, warning, notice and error messages. This is the default level. It logs all warning, notice and error messages. Logs all notice and error messages. Logs only the error messages. Type the maximum file size for the log(s), in kilobytes (KB), in this field. The default is 1,024KB (kilobytes) with a maximum of 5MB (megabytes). Type the maximum number of log files that Profiler is allowed to generate and store on the server. The default is 5 (five) log files with a maximum of 100 log files. 41

42 Activity Log Settings The Activity Log Settings panel allows you to specify the maximum number of days to record the activity logs, the maximum number of log records, and the number of log records that can appear on the Activity Logs page. See Activity Logs. Figure 16: Activity Log Settings Panel Table 7: Activity Log Settings Options Option Maximum Number of Days Maximum Log Records Description Type the maximum number of days that the system is to record all the events. Type the maximum number of log records the system is to maintain. Note: Changes to the Maximum Number of Days and Maximum Log Records take effect when the database records are purged. This occurs at 12:00 AM or during a Profiler Web Server restart. Number of Records on a Page Type the maximum number of records that will be listed on the Activity Logs page. Restarting HGST Virident Profiler Services You will have to restart the service if you make changes to the configuration. To restart the service: 1. Login to the Linux server with root privileges. 2. Run the following command to restart the service: service hvprof_init restart 42

43 Displaying the Volume Information You can ascertain the volume information for a specific drive by selecting the respective HDD or SSD icon in the Side menu. The Volume Information page will become active. Table 8 lists the information that appears on the page. Figure 17: Displaying the Volume Information Table 8: Volume Information Page Item Name Volume Type Size File System Available for Caching Model Description Displays the name of the selected volume. Displays the device type, i.e., HDD or SSD. Displays the size of the selected volume. Displays the name of the type of file system deployed on the volume. If no file system is available, the No file system found message displays. Displays Yes or Not Available, depending whether the volume is available for caching. If the volume has a system partition, then it is unavailable for caching. Displays the model of the selected volume if the value is available. If the model information is unavailable, the field is hidden. Rescan Button Use the Rescan button if the hardware configuration changes and to detect any new SSDs or HDDs installed in the system. 43

44 Profiling an HDD Volume You can use Profiler to determine the best cache performance or primary storage alternative for any given HDD source volume according to the SSD Usage specified, i.e., SSD as Cache Device or SSD as Primary Storage. Select an HDD volume in the Side menu, and then click the Profiler tab in the Top menu. You need to start a new trace operation and specify its Duration. Schedule the Profiling Session If you are profiling a device partition then you cannot simultaneously profile the remaining partitions of the same device. Select the profiling session schedule by specifying the Tracer Start Time and Analyzer Start Time. The Calendar dialog allows you to select the specific date and time for the trace and analysis phases. Click in the Tracer Start Time and Analyzer Start Time fields respectively to open the Calendar dialog. Figure 18: Scheduling the Profiling Session Note: While you can set the Tracer Start Time and Analyzer Start Time independently of each other, the following restrictions will apply: 1. If neither the Tracer Start Time nor Analyzer Start Time is specified, then the tracing will begin immediately, with the analysis starting after the trace operation is completed. 2. If only the Tracer Start Time is specified, the tracing will start at the scheduled time, with the analysis starting after the trace operation is completed. 3. If only the Analyzer Start Time is specified, then the tracing will start immediately, will the analysis starting at the scheduled time. 4. If the Tracer Start Time and Analyzer Start Time are specified, then these phases will start at the specified scheduled time. 44

45 Multiple SSD Type Selection Select one or more SSD Type(s) from the drop-down list while holding the Ctrl key to profile multiple SSD types with the same workload running on an HDD source volume. SSD Usage Select either SSD as Cache Device or SSD as Primary Storage from the SSD Usage drop-down list. Starting or Scheduling a Trace Operation Profiler uses device performance data to model the potential performance improvement of a device. The actual performance improvement for a device may vary from predictions made by Profiler, depending upon the operating environment and manner of use. It is recommended to start or schedule the trace operation whenever critical applications are heavily utilizing the HDD source volume. Since the data is derived from the duration of the trace, Profiler will recommend the optimal cache volume size for the HDD volume if the SSD Usage is SSD as Cache Device. It is therefore important to ascertain the correct trace duration when running the profile. The options in the Start New Trace panel allow you to specify the parameters for the trace. Duration Figure 19: Specifying the Trace Parameters Use the Days, Hours or Minutes drop-down lists to specify the duration. Make sure to note the Estimated trace file size. Profiler will calculate the estimated trace log file size that will result during the trace and analyze process. Make sure that you have sufficient free disk space in the temporary folder for the trace log file. The trace log file is created under the /tmp/traces directory by default. 45

46 Recommend Best SSD If you place a check mark in the Recommend Best SSD check box, Profiler will trace the given workload and then after the analysis will recommend the best SSD from the available SSDs for your workload. If you remove the check mark, then you can choose a specific SSD or SSDs for consideration in the SSD Type list. If there is an SSD under your consideration that does not appear in the SSD Type list, then please refer to Custom SSD Options. SSD Type Custom SSD Options You can use the SSD Type scroll list to choose the SSD(s) you want for the trace analysis. Notice that the SSDs that appear in the list are HGST and Virident devices; the respective latency values will assist Profiler during the trace data analysis collected during the trace run. See Custom SSD Options. Select the Custom SSD option from the SSD Type drop-down list if your SSD are not among those that appear in the list. If you select this option, three additional three fields will appear, and you will have to specify the Custom SSD Name, the Custom Read Latency (µs), and the Custom Write Latency (µs). Click the Add button to add the custom SSD and its parameters to the SSD Type list. Figure 20: Specifying a Custom SSD for Profiling 46

47 Start Trace Click the Start button to initiate the trace process. A progress bar will display the progress of the trace process. Wait until the trace process completes. Stop Trace Click the Stop button if you want to terminate the trace process before the specified duration expires. Stop and Analyze Click the Stop and Analyze button if you wish to terminate the trace process and analyze the currently gathered data. 47

48 Viewing the Trace Results You can view the Traced Information panel after the successful run of the trace. This panel will display the trace start time, the trace duration, the SSD Type selected for the analysis, the number of read operations, the number of write operations, and the number of gigabytes read and written. Click the Download hyperlink in the Trace Data column to download the trace file for the profiled volume. Recommended Cache Configurations Figure 21: Traced Information The Recommended Cache Configuration panel will list the recommended configurations. For each Cache Mode (Write Back and Write Through), there is a recommended Cache Size (GB), a Block Size (KB), and the percentage of Read Hits/Write Hits expected. Figure 22: Recommended Cache Configurations Note: This panel is not shown if you specified the SSD Usage as SSD as Primary Storage. Response Time Improved Details The Response Time Improved Details panel will list the % Response Time Improved values for the different SSD Types that were selected prior to the trace operation. You can select a specific SSD Type from the drop-down list to view the % Response Time Improved values for the Write Back and Write Through cache modes for that SSD Type. Figure 23: Response Time Improved Details Note: This panel will not show the % Response Time Improved for the different cache modes if you specified the SSD Usage as SSD as Primary Storage. Each IT environment is unique so the actual cache performance depends on various runtime factors such as I/O subsystem configuration, number of OS threads performing I/O, compressibility of data, RAM size, and the cache configuration itself. 48

49 I/O Statistics for the Profiled Source Volume The IO Statistics panel will present an I/O Histogram, the Average Response Time, and the Disk Read and Read Hits and Disk Write and Write Hits of the profiled HDD source volume for the SSD Type selected from the drop-down list in the Response Time Improved Details panel. Figure 24: I/O Statistics for the Profiled Source Volume Note: Disk Read and Read Hits and Disk Write and Write Hits will not be shown if you specified the SSD Usage as SSD as Primary Storage. 49

50 Activity Logs The Activity Logs page is used to view all previously recorded profile operations and user actions. Select Activity Logs from the drop-down More Menu to display the page. The value specified in the Number of Records on a Page field in the Activity Log Settings panel determines the number of log records that display on this page. Figure 25: The Activity Logs Page Table 9: Activity Logs Options Option Description Click the Reload button to refresh the events. You can click the arrows to navigate through the log records. Type a page number in the Go to text box and press [Enter] to display a specific page. Click the Export button to export the log to the *.csv (Comma Separated Value) format. The filename includes a date and time stamp, i.e., activity_log_2014_10_01_14_20_50.csv. Click Download csv File in the Activity Logs page to download the activity log file to your local system. The log files are usually stored in the default Downloads folder of the web browser. 50

51 Logging Out of HGST Virident Profiler Select Logout from the More Menu to quit your current session. Use the Click here to re-login link to present the Login Prompt screen. Figure 26: Logging out of HGST Virident Profiler 51