Re: Stateless Builds

te needs/tasks running pio commands outside of the > engine directory? no, not the engine specific commands, obviously some already work outside the engine directory. > > Thanks, > Chan > > On Sun, Dec 11, 2016 at 1:35 PM, Mars Hall <m...@heroku.com> wrote: > >> Pa

Re: Stateless Builds

35 PM, Mars Hall <m...@heroku.com> wrote: > >> Pat, >> >> Since I represent one of the containerized platforms (Heroku) that needs >> stateless builds (specifically the ability to run a build without a >> database attached) to deploy PIO at its ful

Re: Stateless Builds

immediate needs/tasks running pio commands outside of the engine directory? Thanks, Chan On Sun, Dec 11, 2016 at 1:35 PM, Mars Hall <m...@heroku.com> wrote: > Pat, > > Since I represent one of the containerized platforms (Heroku) that needs > stateless builds (specifically

Re: Stateless Builds

OK, so that was too much detail. My immediate question is how to train on one machine and deploy on several others—all referencing the same instance data (model)? Before it was by copying the manifest, now there is no manifest. On Dec 7, 2016, at 5:43 PM, Pat Ferrel

Re: Stateless Builds

My first question is how to train on an ephemeral machine to swap models into an already deployed prediction server, because this is what i do all the time. The only way to do this now is train first on dummy data then deploy and re-train as data comes in, but there are other issues and

Stateless Builds

Hi all, I am moving the discussion of stateless build ( https://github.com/apache/incubator-predictionio/pull/328) here. Replying Pat: > BTW @chanlee514 @dszeto Are we thinking of a new command, something like pio register that would add metadata to the metastore? This would need to be run every