Custom Query (98 matches)

This ticket is being written to capture the findings for the planned IG-EXP-3 InstaGENI Single Site 100 VM Test. All issues captured are known and require no action at this time.

These are the 100 VM scenarios planned for testing:

Scenario 1: 1 Slice with 100 VMs Scenario 2: 2 Slices with 50 VMs each Scenario 3: 4 Slices with 25 VMS each Scenario 4: 50 Slices with 2 VMs each Scenario 5: 100 Slices with 1 VM each Scenario 6: 10 slices with 10 VM each (note 1)

(note 1) This scenario was not in the original test plan, but it is being added based on input from Leigh Stroller.

=> Scenario 1: 1 Slice with 100 VMs in a grid topology

Results: FAILED due to:

 100 nodes of type pcvm requested, but only 50 available nodes of type pcvm found

=> Scenario 2: 2 Slices with 50 VMs each, each sliver uses grid topology

Results: FAILED

Two test runs were completed. 1st try:

• Created first 50 node experiment, no error reported.
• Sliver status reported "resource is busy; try again later" for about 5 minutes,
• then sliverstatus reported error:

    Failed to get SliverStatus on 2exp-50vm at AM https://boss.utah.geniracks.net/protogeni/xmlrpc/am/2.0: 
<Fault -32600: 'Internal Error executing SliverStatus'>

Results 2nd test run:

1. Creatsliver first 50 node sliver which completes without error
2. Sliver status is busy approximately 5 minutes reporting "resource is busy; try again later"
3. Slivestatus eventually fails with "<Fault -32400: 'XMLRPC Server Error'>"

Additional tests results will also be captured as completed.

In testing IG-MON-3 step 5, i found that the manifest cached for each ProtoGENI experiment reports dataplane IP addresses and MAC addresses (or at least it should do so fully once [instaticket:26] has been resolved). However, the only way i was easily able to find control IPs assigned to VMs was the interfaces table:

mysql> select * from interfaces where IP="172.17.3.1";
+---------+------+------+--------------+------------+-----------+-------------+----------------+-------+------+---------------+--------+--------+----------+------+-------+--------------------------------------+---------+
| node_id | card | port | mac          | IP         | IPaliases | mask        | interface_type | iface | role | current_speed | duplex | rtabid | vnode_id | whol | trunk | uuid                                 | logical |
+---------+------+------+--------------+------------+-----------+-------------+----------------+-------+------+---------------+--------+--------+----------+------+-------+--------------------------------------+---------+
| pcvm3-1 |    0 |    1 | 000000000000 | 172.17.3.1 | NULL      | 255.240.0.0 | generic        | eth0  | ctrl | 0             | full   |      0 | NULL     |    0 |     0 | e5b9ad51-a379-11e1-af1c-00009b6224df |       1 | 
+---------+------+------+--------------+------------+-----------+-------------+----------------+-------+------+---------------+--------+--------+----------+------+-------+--------------------------------------+---------+
1 row in set (0.00 sec)

This table appears to contain IPs only for running experiments, and does not appear to contain real MAC addresses.

1. How can i find what control IPs were assigned to what VMs belonging to now-terminated experiments?
2. How can i find out MAC address assignments for these VMs?

Nodes which are successfully booted from the images FEDORA15-STD and FEDORA15-OPENVZ-STD in utah.geniracks.net, appear not to work with the iLO remote console. The java console app reports "No Video".

I've corroborated this just now, on:

• 155.98.34.104, iLO for pc3, which is running FEDORA15-OPENVZ-STD for the experiment emulab-ops/shared-nodes
• 155.98.34.105, iLO for pc4, which is running FEDORA15-STD for the experiment pgeni-gpolab-bbn-com/ecgtest

During testing of IG-ADM-1, i successfully used the remote consoles for pc3 and pc4 at other times. So i believe this is not working right now because of the fedora images, rather than because of a connectivity problem with those particular hosts.