Custom Query (98 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (16 - 18 of 98)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Ticket Resolution Summary Owner Reporter
#32 fixed Track 100 VM scenario findings somebody lnevers@bbn.com
Description

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.

#36 fixed the FQDN of an OpenVZ resource is not entered into DNS somebody chaos@bbn.com
Description

The full information about my experiment (from https://boss.utah.geniracks.net/showexp.php3?experiment=952#details) shows:

Virtual Node Info:
ID              Type         OS              Qualified Name
--------------- ------------ --------------- --------------------
phys1 (pc2)     pc           FEDORA15-STD    phys1.ecgtest.pgeni-gpolab-bbn-com.utah.geniracks.net
virt1 (pc3)     pcvm         OPENVZ-STD      virt1.ecgtest.pgeni-gpolab-bbn-com.utah.geniracks.net

Of those, the phys1 address is in DNS, and is a valid way to get into the node:

capybara,[~],08:19(0)$ host phys1.ecgtest.pgeni-gpolab-bbn-com.utah.geniracks.net
phys1.ecgtest.pgeni-gpolab-bbn-com.utah.geniracks.net is an alias for pc2.utah.geniracks.net.
pc2.utah.geniracks.net has address 155.98.34.12

However, the virt1 address is not in DNS:

capybara,[~],08:19(0)$ host virt1.ecgtest.pgeni-gpolab-bbn-com.utah.geniracks.net
Host virt1.ecgtest.pgeni-gpolab-bbn-com.utah.geniracks.net not found: 3(NXDOMAIN)

Should it be?

#43 fixed subscribe InstaGENI operators to response-team@geni.net ricci@cs.utah.edu chaos@bbn.com
Description

InstaGENI operators (either individually or as a list address) should subscribe to response-team@geni.net to receive notifications about GENI infrastructure outages, and as a way to be reached by non-InstaGENI GENI operators.

The mailman page for subscription is http://lists.geni.net/mailman/listinfo/response-team.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Note: See TracQuery for help on using queries.