[backport v1.4] [ENHANCEMENT][GUI] Move enable CPU Pinning checkbox position in template config page

[harvesterhci-io-github-bot]

backport the issue #6879

[harvesterhci-io-github-bot]

Pre Ready-For-Testing Checklist

• If labeled: require/HEP Has the Harvester Enhancement Proposal PR submitted?
  The HEP PR is at:

• Where is the reproduce steps/test steps documented?
  The reproduce steps/test steps are at:

• Is there a workaround for the issue? If so, where is it documented?
  The workaround is at:

• Have the backend code been merged (harvester, harvester-installer, etc) (including backport-needed/*)?
  The PR is at:

  • Does the PR include the explanation for the fix or the feature?

  • Does the PR include deployment change (YAML/Chart)? If so, where are the PRs for both YAML file and Chart?
    The PR for the YAML change is at:
    The PR for the chart change is at:

• If labeled: area/ui Has the UI issue filed or ready to be merged?
  The UI issue/PR is at:

• If labeled: require/doc, require/knowledge-base Has the necessary document PR submitted or merged?
  The documentation/KB PR is at:

• If NOT labeled: not-require/test-plan Has the e2e test plan been merged? Have QAs agreed on the automation test case? If only test case skeleton w/o implementation, have you created an implementation issue?

  • The automation skeleton PR is at:
  • The automation test case PR is at:

• If the fix introduces the code for backward compatibility Has a separate issue been filed with the label release/obsolete-compatibility?
  The compatibility issue is filed at:

[a110605]

Backport PR merged. harvester/dashboard#1221

[TachunLin]

Verified fixed on v1.4-eaf3009a-head. (24/11/09). Close this issue.

Result

$\color{green}{\textsf{PASS}}$ Test enable CPU Pinning on the modified default virtual machine template $~~$

1. Modify the default template, check the Enable CPU Pinging

2. Launch instance from the newly created template

3. CPU Pinning vm can request specific core cpu on host for this VM

harv14-241110:~ # kubectl exec virt-launcher-test-modified-template-t74hr -- virsh dumpxml default_test-modified-template | awk "/<cputune>/,/<\/cputune>/"
  <cputune>
    <vcpupin vcpu='0' cpuset='1'/>
    <vcpupin vcpu='1' cpuset='2'/>
  </cputune>

$\color{green}{\textsf{PASS}}$ Test enable CPU Pinning when create a new virtual machine template $~~$

1. Create a new virtual machine template and check the Enable CPU Pinning in the Advanced Options
   

2. Create a new vm and select the newly create template
   

3. CPU Pinning vm can request specific core cpu on host to it's vcpu

harv14-241110:~ # kubectl exec virt-launcher-new-cpu-pinning-dmpkx -- virsh dumpxml default_new-cpu-pinning | awk "/<cputune>/,/<\/cputune>/"
  <cputune>
    <vcpupin vcpu='0' cpuset='1'/>
    <vcpupin vcpu='1' cpuset='2'/>
  </cputune>

$\color{green}{\textsf{PASS}}$ Test disable CPU Pinning when create a new virtual machine template $~~$

1. Create a new virtual machine template and do not check the Enable CPU Pinning in the Advanced Options

2. Create a new vm and select the newly create template

3. CPU Pinning vm don't request specific core cpu on host to it's vcpu

harv14-241110:~ # kubectl exec virt-launcher-non-cpu-pinning-wl56b -- virsh dumpxml default_non-cpu-pinning | awk "/<cputune>/,/<\/cputune>/"
harv14-241110:~ #

Test Information

• Test Environment: Single node kvm machine
• Harvester version: v1.4-eaf3009a-head. (24/11/09)

Verify Steps

Enable CPU Pinning on existing virtual machine template

1. Enable CPU Manager on the host menu item
   

2. Modify template to create a new version of raw-image-base-version
   

3. Check the Enable CPU Pinning in the Advanced Options and Save
   
   

4. Launch instance from the newly created template

5. Check the vm can started in Running

6. CPU Pinning vm can request specific core cpu on host to it's vcpu

harv14-241110:~ # kubectl exec virt-launcher-test-modified-template-t74hr -- virsh dumpxml default_test-modified-template | awk "/<cputune>/,/<\/cputune>/"
  <cputune>
    <vcpupin vcpu='0' cpuset='1'/>
    <vcpupin vcpu='1' cpuset='2'/>
  </cputune>

Enable CPU Pinning when create a new virtual machine template

1. Create a new virtual machine template

2. Check the Enable CPU Pinning in the Advanced Options and Save
   

3. Create a new vm and select the newly create template
   

4. Check the vm can started in Running

5. CPU Pinning vm can request specific core cpu on host to it's vcpu

harv14-241110:~ # kubectl exec virt-launcher-new-cpu-pinning-dmpkx -- virsh dumpxml default_new-cpu-pinning | awk "/<cputune>/,/<\/cputune>/"
  <cputune>
    <vcpupin vcpu='0' cpuset='1'/>
    <vcpupin vcpu='1' cpuset='2'/>
  </cputune>

Disable CPU Pinning when create a new virtual machine template

1. Create a new virtual machine template

2. Do not check the Enable CPU Pinning in the Advanced Options and Save

3. Create a new vm and select the newly create template

4. Check the vm can started in Running

5. CPU Pinning vm don't request specific core cpu on host to it's vcpu

harv14-241110:~ # kubectl exec virt-launcher-non-cpu-pinning-wl56b -- virsh dumpxml default_non-cpu-pinning | awk "/<cputune>/,/<\/cputune>/"
harv14-241110:~ #