Custom Query (138 matches)

In a scenario where the slice expiration is set to "2013-03-26 00:00:00" it is possible to renew a sliver to a date beyond the slice expiration, (ex. Thu Mar 28 00:00:00 UTC 2013)

The slice expiration time:

$ omni.py renewslice lnexp "2013-03-26"
INFO:omni:Loading config file /home/lnevers/.gcf/omni_config
INFO:omni:Using control framework pg
INFO:omni.protogeni:Requesting new slice expiration '2013-03-26T00:00:00'
INFO:omni:Slice lnexp now expires at 2013-03-26 00:00:00 UTC
INFO:omni:Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexp expires on 2013-03-26 00:00:00 UTC
INFO:omni: ------------------------------------------------------------
INFO:omni: Completed renewslice:
  Options as run:
		framework: pg
  Args: renewslice lnexp 2013-03-26
  Result Summary: Slice lnexp now expires at 2013-03-26 00:00:00 UTC
Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexp expires on 2013-03-26 00:00:00 UTC 
INFO:omni: ============================================================

The sliver renewal:

$ omni.py renewsliver -a eg-gpo lnexp "2013-03-28" --devmode
INFO:omni:Loading config file /home/lnevers/.gcf/omni_config
INFO:omni:Using control framework pg
INFO:omni:Substituting AM nickname eg-gpo with URL https://bbn-hn.exogeni.net:11443/orca/xmlrpc, URN unspecified_AM_URN
INFO:omni:Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexp expires on 2013-03-26 00:00:00 UTC
WARNING:omni:Cannot renew sliver(s) in lnexp until 2013-03-28 00:00:00 UTC because it is after the slice expiration time 2013-03-26 00:00:00 UTC, but continuing...
INFO:omni:Renewing Sliver lnexp until 2013-03-28 00:00:00+00:00 (UTC)
INFO:omni:Substituting AM nickname eg-gpo with URL https://bbn-hn.exogeni.net:11443/orca/xmlrpc, URN unspecified_AM_URN
INFO:omni:Renewed sliver urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexp at unspecified_AM_URN (https://bbn-hn.exogeni.net:11443/orca/xmlrpc) until 2013-03-28T00:00:00+00:00 (UTC)
INFO:omni: ------------------------------------------------------------
INFO:omni: Completed renewsliver:

  Options as run:
		aggregate: ['eg-gpo']
		devmode: True
		framework: pg

  Args: renewsliver lnexp 2013-03-28

  Result Summary: Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexp expires on 2013-03-26 00:00:00 UTC
Renewed sliver urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexp at unspecified_AM_URN (https://bbn-hn.exogeni.net:11443/orca/xmlrpc) until 2013-03-28T00:00:00+00:00 (UTC)
 
INFO:omni: ============================================================

The resulting "orca_expires" is later than the slice expiration time:

$ omni.py sliverstatus -a eg-gpo lnexp
INFO:omni:Loading config file /home/lnevers/.gcf/omni_config
INFO:omni:Using control framework pg
INFO:omni:Substituting AM nickname eg-gpo with URL https://bbn-hn.exogeni.net:11443/orca/xmlrpc, URN unspecified_AM_URN
INFO:omni:Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexp expires on 2013-03-26 00:00:00 UTC
INFO:omni:Substituting AM nickname eg-gpo with URL https://bbn-hn.exogeni.net:11443/orca/xmlrpc, URN unspecified_AM_URN
INFO:omni:Status of Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexp:
INFO:omni:Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexp at AM https://bbn-hn.exogeni.net:11443/orca/xmlrpc has overall SliverStatus: ready
INFO:omni:Sliver status for Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexp at AM URL https://bbn-hn.exogeni.net:11443/orca/xmlrpc
INFO:omni:{
  "geni_status": "ready", 
  "geni_urn": "urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexp", 
  "geni_resources": [
    {
      "orca_expires": "Thu Mar 28 00:00:00 UTC 2013", 
      "geni_urn": "urn:publicid:IDN+exogeni.net:bbnvmsite+sliver+8556ef0b-4c03-4ecf-b028-24cc0bb7ba0a#VM-3", 
      "geni_error": "", 
      "geni_status": "Active"
    }, 
    {
      "orca_expires": "Thu Mar 28 00:00:00 UTC 2013", 
      "geni_urn": "urn:publicid:IDN+exogeni.net:bbnvmsite+sliver+8556ef0b-4c03-4ecf-b028-24cc0bb7ba0a#lan0", 
      "geni_error": "", 
      "geni_status": "Active"
    }, 
    {
      "orca_expires": "Thu Mar 28 00:00:00 UTC 2013", 
      "geni_urn": "urn:publicid:IDN+exogeni.net:bbnvmsite+sliver+8556ef0b-4c03-4ecf-b028-24cc0bb7ba0a#VM-4", 
      "geni_error": "", 
      "geni_status": "Active"
    }, 
    {
      "orca_expires": "Thu Mar 28 00:00:00 UTC 2013", 
      "geni_urn": "urn:publicid:IDN+exogeni.net:bbnvmsite+sliver+8556ef0b-4c03-4ecf-b028-24cc0bb7ba0a#VM-2", 
      "geni_error": "", 
      "geni_status": "Active"
    }, 
    {
      "orca_expires": "Thu Mar 28 00:00:00 UTC 2013", 
      "geni_urn": "urn:publicid:IDN+exogeni.net:bbnvmsite+sliver+8556ef0b-4c03-4ecf-b028-24cc0bb7ba0a#VM-1", 
      "geni_error": "", 
      "geni_status": "Active"
    }
  ]
}
INFO:omni: ------------------------------------------------------------
INFO:omni: Completed sliverstatus:
  Options as run:
		aggregate: ['eg-gpo']
		framework: pg
  Args: sliverstatus lnexp
  Result Summary: Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexp expires on 2013-03-26 00:00:00 UTC
Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexp at AM https://bbn-hn.exogeni.net:11443/orca/xmlrpc has overall SliverStatus: ready.
 Returned status of slivers on 1 of 1 possible aggregates. 
INFO:omni: ============================================================

Checking the software version via the omni getversion command and found the following:

BBN SM:         'orca_version': 'ORCA Camano: v.4.0-SNAPSHOT.build-${buildNumber}'}
FIU SM:         'orca_version': 'ORCA Camano: v.4.0-SNAPSHOT.build-${buildNumber}'}
ExoSM:          'orca_version': 'ORCA Camano: v.4.0-SNAPSHOT.build-5210'}
RENCI SM:       'orca_version': 'ORCA Camano: v.4.0-SNAPSHOT.build-${buildNumber}'}

Should ${buildNumber} be a version number for the local SM code tags?

The test case EG-ADM-7 checks for availability of ExoGENI rack documentation. This ticket captures the requirement to deliver documentation that captures ExoGENI Software Components Functional descriptions and defines how to access to ExoGENI source code.

Findings:

Source can be found at the ​https://geni-orca.renci.org, but it is not obvious how to map it to the ExoGENI rack components.

There is the components overview in the wiki.exogeni.net location in the ​ExoGENI Software page which provides a detailed overview of the ORCA components, but there are few pointers to source code:

• ​XMPP page provides pointer to the ​blowhole software, with instruction for installation and configuration.
• ​OpenFlow page provides pointers to FlowVisor, FOAM and FloodLight Controller which include source. Also available are pointers to download and modify ORCA 3.1 ​scripts to start and stop FloodLight.
• ​GMOC page provides link to ​blowhole code.

Missing:

A page (or set of pages) that maps all rack software components developed for ExoGENI to the sources code location.