[Discussion] Discuss Deployment Architecture

[aslotte]

As we get started with deployment functionality, I thought it would be good if we could discuss how we envision our underlying foundation to be structured. I'm envisioning the following entities to make our architecture flexible (with some modifications). Would love to have your input on what you all think and what we may be missing.

[aslotte]

@AnoojNair / @dcostea / @lqdev / @Brett-Parker would love your input on this.

[AnoojNair]

@aslotte , just curious how will a deployment be trigerred, would it be a user action on a particular run from the client?
Also, the Deployment environments show azure storage, s3 , as the models are already stored there. Would it be just a pointer to the existing model repo? Or is it used in a different way in this context?

[aslotte]

Regarding the first question, in my view the deployment would be triggered by a user action, e.g. right not by running a script to call methods that we expose, and maybe later via a CLI tool that we create or the UI from the client that we're looking into.

For the second question, yep, I'm thinking that we keep the models in our current model repositories. The idea I have is that we create a container/folder for each deployment target if we do file deployment (e.g. a container called Test) and then expose that with a URI. We still need to think about the container deployment but that can come later