We're going to introduce the central server that is responsible for spawning remote processes (takes care of what we "manually" do in the echo64spawner example). For now only fargate task descriptions will be accepted as images.
The idea is flexi provides a ctl file and accepts (and expects) a task definition to be written to it (example https://github.com/jecoz/flexi/blob/cd4fe7e4e102b0b66473b1718da3ddf6d611c2e2/testdata/input.1.json). It takes the description, validates it, spawnes a remote process, mounts its service inside a local directory and presents it through its own file system tree. The mount operation will require users to have a 9p driver installed, either using 9port or natively on plan9.
Implementation discussion has been carried at https://github.com/droyo/styx/issues/25#issue-647982087.
We're going to introduce the central server that is responsible for spawning remote processes (takes care of what we "manually" do in the
echo64spawnerexample). For now only fargate task descriptions will be accepted as images.The idea is
flexiprovides actlfile and accepts (and expects) a task definition to be written to it (example https://github.com/jecoz/flexi/blob/cd4fe7e4e102b0b66473b1718da3ddf6d611c2e2/testdata/input.1.json). It takes the description, validates it, spawnes a remote process, mounts its service inside a local directory and presents it through its own file system tree. The mount operation will require users to have a 9p driver installed, either using 9port or natively on plan9.