Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0


Test  Test Case ID

Test Name

Test Steps

Expected Results

Priority

Status 

Remarks Comment/Bugs 

1

Guest network default settings - public tagged - zone wide

Start a first   VM for the user. Go to the VMs host and xm   console to the VM. Verify that it got an ip address 10.1.1.2. Go to the domRs host and xm console to the   domR. Verify that it got 10.1.1.1 ip address

Default guest   network IPs begin with 10.1.1.1 (255.255.255.0 netmask), each new VM gets the   next IP address from the range.
   

P1

P3 PASS

 

2

Make sure that you can ping external web site from the VM - public tagged   - zone wide

1. Start a   VM.
2. Login to the VM and verify that you can   ping google.com

1. VM should be   able to reach external network via domain router

P1

PASS

 

3

Verify that ssh works from one VM to another inside the guest network.   VMs are running on the same host. Custom configured guest network settings - public tagged - zone wide

1. Create 2 VMs for the   user. Verify that they are started on the same computing/routing   host
2. Login to the first VM and ssh to the   second VM's ip address - 10.1.1.2

1. You should be   able to ssh from one VM to another one inside the same guest   network.
 

P1

PASS

 

4

Guest network default settings - public tagged - account specific

1.Start   
      <li>Configure guest ip   address 10.10.10.1 (modify server-setup.xml file)   <br></li><li>Start a first VM for the   user.<br></li><li>Go to the VMs host and xm console to the   VM. Verify that it got an ip address 10.101.101.2.   <br></li><li>Go
2. Go to the domRs host and xm console to the   domR.   Verify that it got 10.101.101.1 ip address<br></li>
   
    </ol>

<ol>
   
      <li> VM should get a   custom guest ip configured.<br></li>
   
    </ol>

P3

 

 

address

Default guest network IPs begin with 10.1.1.1 (255.255.255.0   netmask), each new VM gets the next IP address from the range.

P1

PASS

 

5

3

Make sure that you can ping external web site from the VM - public tagged   - zone wide account specific

1. Start a VM.
2. Login to   <br><ol>
      <li>Start a   VM.<br></li><li>Login to the VM and verify that you can   ping google.com<br></li></ol> ping a site/machine on the internet (eg:   www.google.com)

VM should be <ol>
      <li> VM should be   able to reach external network via domain router. <br></li>
    </ol>

P1

PASS P3

  

6

4

Verify that ssh works from one VM to another inside the guest network   (same account owner).   VMs are running on the same host. - public tagged - zone wide   account specific

1. Create <br><ol>
      <li>Create 2 VMs for the   user. Verify that they are   started on the same computing/routing   host<br></li><li>Login host
2. Login to the first VM and ssh to the   second VM's ip address - 10.1.1.2<br></li></ol> 2

You <ol>
      <li> You should be   able to ssh from one VM to another one inside the   same guest   network. <br></li>
    </ol>

P3

 

 

5

Verify that ssh works from one VM to another inside the guest network.   VMs are running on different hosts belonging to different pods - public   tagged - zone wide

<ol><li>Configure 2 PODs in the   system.</li><li>Manage to start 2 VMs in 2 different pods. VMs   belong to the same user.<br></li><li>Login to the first VM   and ssh to the second VM's ip address - 10.1.1.2<br></li></ol>

<ol>
   
      <li> You should be   able to ssh from one VM to another one across   pods.<br></li>
   
    </ol>

P3

P1

PASS