https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-2064 Lustre <p>This is for patches landing to master</p> LU-2064

HSM - Changes to Test Framework - Landing to Master

Story Critical Resolved Fixed Jodi Levi Jodi Levi HSM Mon, 1 Oct 2012 09:17:13 +0000 Mon, 12 Aug 2013 18:13:25 +0000 Mon, 12 Aug 2013 18:13:25 +0000 Lustre 2.5.0 Lustre 2.5.0 0 8 <p>This document describes at a high level the changes required to support HSM. <a href="https://jira.hpdd.intel.com/secure/attachment/11767/HSM-16.pdf" class="external-link" target="_blank" rel="nofollow noopener">https://jira.hpdd.intel.com/secure/attachment/11767/HSM-16.pdf</a></p> <p>I think this can be broken down into two parts; Changes to autotest and changes to the framework.</p> <p>The link between them that will be in the config file will look like this;</p> <p>CPTCOUNT=2<br/> CPT1_HOST=node_23<br/> CPT2_HOST=node_24<br/> CPT1DEV0=/dev/sdr1<br/> CPT2DEV0=/dev/sde3</p> <p>Note; I have changed from AGT (Agent which is a generic term) to CPT (copytool which is more specific)</p> <p>I'm not sure what AGTSINGLE means so have not replicated it.</p> <p>I also prepose the CPTxDEVy format so we can have multiple copy tools with multiple devices if need be. Although this might cause problems in autotest/lustre because the presumption is that for all OSSs for example (the devices are the same so they have OSTDEV1, OSTDEV2 which must be true for all OSS's. i.e. OSS must be identical for test.</p> <p>I will ask Jacques-Charles for the source of the document so we can edit it.</p> <p>The steps moving forwards will be for Yu Jian and I to discuss implementation whilst ensuring CEA are completely in the loop about the details. We have a meeting planned for the week starting 8th July 2013.</p> Related LU-3608 Development Project Rank 1|hzv4tb: Rank (Obsolete) 4313