GENI-NSF / geni-portal

A UI for a GENI clearinghouse
Other
3 stars 8 forks source link

Sliver status output needs sorting to group resources by site and by resource type #787

Open luisanevers opened 9 years ago

luisanevers commented 9 years ago

Currently the results of the sliver status in the portal show results as received which makes it difficult for the user to determine each site's FOAM and compute resource status. It would be helpful to group output by site. Additionally, if both ExoGENI and InstaGENI resources are available at the site, the resource types should be considered in grouping output.

Below is an example of the current output for an OpenFlow experiment that uses 3 sites (GPO IG, GPO EG, and Utah DDC):


Status  Aggregate
ready   GPO ExoGENI
    Status  Resource
    ready   urn:publicid:IDN+exogeni.net:bbnvmsite+sliver+b34aec46-6e0d-4dc4-862b-c0637319c264:VM
Status  Aggregate
ready   GPO InstaGENI
    Status  Resource
    ready   gpo-ig
ready   gpo-ig2
Status  Aggregate
ready   UtahDDC InstaGENI OpenFlow
    Status  Resource
    ready   urn:publicid:IDN+ch1.gpolab.bbn.com:ln-prj+slice+GPF-T1:e04e2a2d-b720-4650-90df-66891345e892
Status  Aggregate
ready   GPO OpenFlow
    Status  Resource
    ready   urn:publicid:IDN+ch1.gpolab.bbn.com:ln-prj+slice+GPF-T1:a173fcc1-c087-4c03-be46-ef78a2c0e747
Status  Aggregate
ready   GPO InstaGENI OpenFlow
    Status  Resource
    ready   urn:publicid:IDN+ch1.gpolab.bbn.com:ln-prj+slice+GPF-T1:39ef6071-63f9-48c8-b776-0f687cf6e476
Status  Aggregate
ready   UtahDDC InstaGENI
    Status  Resource
    ready   utahddc-ig
Status  Aggregate
ready   Internet2 OpenFlow
    Status  Resource
    ready   urn:publicid:IDN+ch1.gpolab.bbn.com:ln-prj+slice+GPF-T1:0581a83f-5013-47de-ac3f-b3936b0f49cb
Status  Aggregate
ready   UEN OpenFlow
    Status  Resource
    ready   urn:publicid:IDN+ch1.gpolab.bbn.com:ln-prj+slice+GPF-T1:dc22ca3f-cc52-4daf-af84-500a1c4843ba
Status  Aggregate
ready   GPO ExoGENI OpenFlow
    Status  Resource
    ready   urn:publicid:IDN+ch1.gpolab.bbn.com:ln-prj+slice+GPF-T1:814bdb6a-d344-4049-9a25-2a140965f1d2

Imported from trac ticket #787, created by lnevers on 09-07-2013 at 08:27, last modified: 07-15-2014 at 14:58

luisanevers commented 9 years ago

Similar issue in the output for listresources, although not as important since experimenters will most likely only go to this page after all slivers are ready and at this point will only be interested in the login information.

Note: In the ticket description "resource type" is describing "rack type".

Trac comment by lnevers (github user: luisanevers) on 09-07-2013 at 08:34