-- Build/Tags
-* test rpm build/install
-
-- 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
+SM
+ * connect SM to ProtoGeni Aggregates
+SFACE
+ * attribute management
+ * aggregate manager checks role of user managing attributes
+
+Unit Tests
+ * fix tests in tests/ directory
+
+Build/Tags
+ * test rpm build/install
-- Aggregate/SM
-* Why do some aggregate managers fail implement all Slice operations (delete, stop, etc)
+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
+Component manager
+ * install trusted certs when interface starts (component_manager_pl.init_server())
* Redeem ticket - RedeemTicket/AdminTicket not working. Why?
** This may be replaced by sfa + credentials
- * install the slice and node gid when the slice is created (create NM plugin to execute sfa_component_setup.py ?)
-
-- SFI
-* Update sfi to use the new methods. I've left this for last because its been useful to make sure the old methods are forwarding the request to the new methods correctly. Once Im sure there are no more changes to be made, ill update sfi to use the new methods.
-- Registry
+Registry
* fix legacy credential support
* move db tables into db with less overhead (tokyocabinet?)
-- GUI/Auth Service
+GUI/Auth Service
* develop a simple service where users auth using username/passord and
receive their cred
* service manages users key/cert,creds
* 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
git://git.onelab.eu / sfa.git / blobdiff