2 * sfa_componet_config needs to define SFA_CM_SLICE_PREFIX
5 * methods should support urn or hrn arguments
6 * create a module that converts urn to hrn so we can continue using
8 * add get_urn() method to GID object
9 * urn is the standard over the wire format
12 * sfa.plc.api.SfaAPI.fill_record_pl_info() should add the sites PIs to a slice records researchers list
13 * update call should attempt to push updates to federated peers if
14 the peer has a record for an object that is updated locally
15 * api.update_membership() shoudl behave more like resolve when looking up records (attempt to resolve records at federated registeries) instead of only looking in the local registry
16 * support generic registry records (dont depend on postgres!)
18 - sfa-clean-peer-records
19 * instead of resolving each peer record one by one, use one reslove call to resolve a list of hrns (requires updated registry.resolve() method)
22 * sfa.plc.slices.verify_site() should check if site['max_slices'] needs to be updated
23 * sfa.plc.slices.verify_slice() should check if slice['expires'] needs to be updated
26 * install the slice and node gid when the slice is created (create NM plugin to execute sfa_component_setup.py ?)
30 * sfi -a option should send request to sm with an extra argument to
31 specify which am to contact instead of connecting directly to the am
32 (am may not trust client directly)
34 - Initscripts on sfa / geniwrapper
35 * should sfa have native initscript support or should we piggyback off of myplc?
37 - Fully integrate SOAP (need to throw either soap or xmlrpc exceptions depending on the client)
38 * started but not finished
41 * error messages should be easier to understand
42 * (failing to connect to plcapi shoudl return a helpful message, not a generic internal server error)