create sliver for 4 raw-pc node ring topology generates Mapper error

[lnevers@bbn.com]

Using an Rspec that has 4 raw-pc type nodes in a ring topology:

pc1<-lan0->pc2<-lan1->pc4<-lan2->pc5<-lan3->pc1

The RSpec is attached as 4raw-pc-ring-c.rspec.

Creating a sliver with this topology results in the following error:

  Result Summary: Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+insta2node expires within 1 day(s) on 2012-05-02 01:09:36 UTC
Asked https://boss.utah.geniracks.net/protogeni/xmlrpc/am/2.0 to reserve resources. No manifest Rspec returned. *** ERROR: mapper: Reached run limit. Giving up.
seed = 1335910606
Physical Graph: 6
Calculating shortest paths on switch fabric.
Virtual Graph: 8
Generating physical equivalence classes:3
Type precheck:
Type precheck passed.
Node mapping precheck:
Node mapping precheck succeeded
Pruning pclasses.
pclass pruning complete: removed 2 pclasses, 1 remain.
Type precheck:
Type precheck passed.
Policy precheck:
Policy precheck succeeded
Annealing.
Adjusting dificulty estimate for fixed nodes, 4 remain.
Doing melting run
Reverting: forced
Reverting to best solution
Done
   BEST SCORE:  10.1 in 17000 iters and 0.005772 seconds
With 12 violations
Iters to find best score:  0
Violations: 12
  unassigned:  4
  pnode_load:  0
  no_connect:  8
  link_users:  0
  bandwidth:   0
  desires:     0
  vclass:      0
  delay:       0
  trivial mix: 0
  subnodes:    0
  max_types:   0
  endpoints:   0
Nodes:
pc1 pc1
pc2 pc2
pc4 pc4
pc5 pc5
unassigned: tbdelay0
unassigned: tbdelay1
unassigned: tbdelay2
unassigned: tbdelay3
End Nodes
Edges:
linksdelaysrc/lan0/pc2:0,pc1:0 Mapping Failed
linksdelaydst/lan0/pc1:0,pc2:0 Mapping Failed
linksdelaysrc/lan1/pc4:0,pc2:1 Mapping Failed
linksdelaydst/lan1/pc2:1,pc4:0 Mapping Failed
linksdelaysrc/lan2/pc4:1,pc5:0 Mapping Failed
linksdelaydst/lan2/pc5:0,pc4:1 Mapping Failed
linksdelaysrc/lan3/pc1:1,pc5:1 Mapping Failed
linksdelaydst/lan3/pc5:1,pc1:1 Mapping Failed
End Edges
End solution
ASSIGN FAILED:
Type precheck passed.
Node mapping precheck succeeded
Pruning pclasses.
pclass pruning complete: removed 2 pclasses, 1 remain.
Type precheck passed.
Policy precheck succeeded
Annealing.
Adjusting dificulty estimate for fixed nodes, 4 remain.
Doing melting run
Reverting: forced
Reverting to best solution
Done
   BEST SCORE:  10.1 in 17000 iters and 0.005772 seconds
  unassigned:  4
  pnode_load:  0
  no_connect:  8
  link_users:  0
  bandwidth:   0
  desires:     0
  vclass:      0
  delay:       0
  trivial mix: 0
  subnodes:    0
  max_types:   0
  endpoints:   0
 
INFO:omni: ============================================================

[lnevers@bbn.com]

On 5/1/12 5:08 PM, Leigh Stoller wrote:

Using an Rspec that has 4 raw-pc type nodes in a ring topology:

pc1<-lan0->pc2<-lan1->pc4<-lan2->pc5<-lan3->pc1

The RSpec is attached as 4raw-pc-ring-c.rspec.

And in this case, you are specifying 100Mb bandwidth for 1Gb links ... Maybe the right idea is to not specify any bandwidths and let the mapper tell you what you got.

Lbs

Modified the RSpec to remove all capacity, but all nodes are no longer available. Will try again tomorrow.

[lnevers@bbn.com]

After removing capacity, was able to successfully set up a sliver, also verified that flack no longer adds capacity for this topology. Closing ticket.