[GitHub] [openwhisk] style95 commented on issue #4580: [Discussion] Action Versioning

[GitBox <gi...@apache.org>]

style95 commented on issue #4580: [Discussion] Action Versioning
URL: https://github.com/apache/openwhisk/issues/4580#issuecomment-519791452
 
 
   My initial thought is as follow:
   
   
   ### 1. An action should be uniquely identified with versions.
   With the fact that many databases do not support such versioning functionality, we may need to redefine the id for documents.
   
   ```
   ex) "_id": "guest/hello/0.0.1",
   ```
   
   ### 2. Users should be able to specify versions at least when reading/invoking an action.
   A version header or URL parameter can be options to specify versions.
   I think it is a minimum requirement to support reading and invoking with a specific version.
   Regarding deleting/updating, it can be controversial.
   
   ### 3. A way to handle spatial quota.
   
   Currently, OW does not limit the storage quota. Users can create as many actions as they want.
   As we introduce the versioning feature, storage usage can increase drastically.
   It implies the need to manage/limit spatial quota.
   A simple way can be to limit the number of versions for an action to recent 5 ~ 10 versions.
   
   We may define a more complicated method to handle it.
   
   ### 4. Treat an action with different versions as different.
   
   This is related to the reuse of action containers.
   We need to treat them just like different actions as underlying action codes can be different.
   So only if activations with the same action version will reuse action containers.
   
   Also, if we would support some kinds of routing features as I mentioned above, we may need a way to correlate them with a single URL, and control the scheduling ratio between them as well.
   
   
   Sharing your thinking about this feature, requirements, and any use cases would be appreciated.
   
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services