Opened 11 years ago

Last modified 11 years ago

#1033 assigned

SCS should implement Getversion

Reported by: Aaron Helsinger Owned by: xyang@maxgigapop.net
Priority: minor Milestone:
Component: MAXSCS Version: SPIRAL5
Keywords: Cc: tlehman@maxgigapop.net
Dependencies:

Description (last modified by Aaron Helsinger)

The SCS should implement a method GetVersion, that advertises its version. This can also be used by GENI monitoring to check that the SCS is up and running

Change History (5)

comment:1 Changed 11 years ago by Aaron Helsinger

Description: modified (diff)

comment:2 Changed 11 years ago by xyang@maxgigapop.net

Cc: Aaron Helsinger added
Owner: changed from xyang@maxgigapop.net to ckotil@grnoc.iu.edu

Feature added to AM core code base.

Reassign to Chad to update the Java code.

comment:3 Changed 11 years ago by xyang@maxgigapop.net

Cc: ckotil@grnoc.iu.edu added; Aaron Helsinger removed
Owner: changed from ckotil@grnoc.iu.edu to Aaron Helsinger

Correction: nothing is required for Chad to update. Reassign to Aaron to test.

comment:4 Changed 11 years ago by Aaron Helsinger

Cc: ckotil@grnoc.iu.edu removed
Owner: changed from Aaron Helsinger to xyang@maxgigapop.net

Looks fine.

Suggestions:

  • Drop the top level geni_api return
  • Drop the geni_ad_rspec_versions tag
  • Do we need the geni_api_versions tag?
  • Do you have a commit tag you can use for code_tag?
  • Could the SCS report here something about the # of AMs for which it uses Ad RSpecs, or even which AMs it knows about?

I'm imagining something that you populate with an ls of the directory where you keep Ad RSpecs

  scs_known_ams: [
   <URL> = <Date of Ad RSpec>,
    ...
  ]

comment:5 Changed 11 years ago by xyang@maxgigapop.net

Priority: majorminor
Status: newassigned

Addressed the points in "Suggestions". However, scs_known_ams is not added.

XML-RPC API thread is separated from TEDB thread. Retrieving all the aggregates info requires some serious coding. We will leave it to low priority for now and revisit when we have a compelling use case.

Note: See TracTickets for help on using tickets.