#3801 NORM Untriag: Rainbow, Sugar, and the Datastore need to integrate to isolate Activities from the Datastore

[Zarro Boogs per Child]

#3801: Rainbow, Sugar, and the Datastore need to integrate to isolate Activities
from the Datastore
---------------------+------------------------------------------------------
  Reporter:  mstone  |       Owner:  jg                                            
      Type:  defect  |      Status:  new                                           
  Priority:  normal  |   Milestone:  Untriaged                                     
 Component:  distro  |     Version:                                                
Resolution:          |    Keywords:  security-integration, security, rainbow, sugar
  Verified:  0       |  
---------------------+------------------------------------------------------

Comment(by marco):

 I'd start by trying to address the basic interaction between activities
 and the datastore.

  * The user open a file from the datastore (or resume an activity)

    1. Journal inform rainbow that an activity should have access to a
 datastore object.
    2. The activity is started and it's given an object id.
    3. The activity call the datastore service to checkout the file.
    4. Datastore check with rainbow if the activity can access the file.
    5. If the activity has the right permissions the datastore returns the
 metadata and give access to the file to the Activity.
    6. Something similar to 3 - 5 happens when the activity needs to write
 changes to the file.

  * A new activity started and it creates a new object in the datastore

    1. The activity call the datastore to create the new file.
    2. The datastore gives permission assuming rate limiting criterias are
 respected.
    3. The activity can now read/write the object it created (not sure if
 we need to go through rainbow to ensure this).

 This my understanding of the interaction model from an irc discussion with
 Ivan. It's really rough and high level but I think it's completely
 compatible with the way journal and datastore are designed.

-- 
Ticket URL: <https://dev.laptop.org/ticket/3801#comment:3>
One Laptop Per Child <https://dev.laptop.org>
OLPC bug tracking system