X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=TODO;h=b5628f4785211c01dea8b5c5b9026609828525d9;hb=refs%2Fheads%2Ftrunk%4014639;hp=9c30bf5141d71268fae06d1a899ba41ae0076e2d;hpb=70cc55f3ae42ebb61805a4a62ef3a623152cda96;p=sfa.git diff --git a/TODO b/TODO index 9c30bf51..b5628f47 100644 --- a/TODO +++ b/TODO @@ -1,29 +1,20 @@ -- Tutorial - * make a tutorial for sfa - -- Tag +- Build/Tags * test rpm build/install -- Geni Aggregate - * are we going to deploy a geni aggregate - * test - -- Trunk -* use PLC shell instead of xmlrpc when communicating with local plc aggregate - -- Client - * update getNodes to use lxml.etree for parsing the rspec - - Stop invalid users * a recently disabled/deleted user may still have a valid cred. Keep a list of valid/invalid users on the aggregate and check callers against this list +- NM Plugin + * install the slice and node gid when the slice is created (create NM plugin to execute sfa_component_setup.py ?) + * test + - Component manager - * GetGids - make this work for peer slices - * GetTicket - must verify_{site,slice,person,keys} on remote aggregate + * install trusted certs when interface starts (component_manager_pl.init_server()) * Redeem ticket - RedeemTicket/AdminTicket not working. Why? - * install the slice and node gid when the slice is created (create NM plugin to execute sfa_component_setup.py ?) + ** This may be replaced by sfa + credentials - Registry +* fix legacy credential support * move db tables into db with less overhead (tokyocabinet?) - GUI/Auth Service @@ -32,20 +23,12 @@ * service manages users key/cert,creds * gui requires user's cred (depends on Auth Service above) -- SM call routing -* sfi -a option should send request to sm with an extra argument to - specify which am to contact instead of connecting directly to the am - (am may not trust client directly) - - Protogeni -* merger josh's branch with trunk -* agree on standard set of functon calls * agree on standard set of privs * on permission error, return priv needed to make call * cache slice resource states (if aggregate goes down, how do we know what slices were on it and recreate them? do we make some sort of transaction log) - Questions ========= - SM/Aggregate