How does nscale relate to apparatus/fuge?

[Analect]

@mcollina
Just wondering if nscale development has been superseded by work on fuge .. and if nscale will become a subset of fuge? ... or is it planned to keep them separate.

... have the orchestration tools native to docker superseded the need for nscale ... or has further development of nscale been put on hold for a while?

Thanks.

[mcollina]

Hi @Analect, one of our biggest mistake in nscale is its design: we tried to build a tool that does too much. We are splitting its functionality into pieces, so it is easier to develop and maintain.

We are already working in the build step for fuge, see oast. A deployer for that output will come soon.

[Analect]

Thanks @mcollina for the quick response.
Could you elaborate a little?
I was looking through Peter's presentation on fuge again.

So, at the moment, fuge expects images that are already built to be referenced in a docker-compose.yml, whereas oast will introduce a capability to build these locally from a dockerfile and push to a public/private registry?

The third tool you mentioned - for deployment .. will then extend fuge's capabilities beyond a local machine ... in terms of deploy potentially one service (or more) per container in a cloud environment. Will that tool leverage on some of the improvements that have come in docker around networking etc... or will it borrow more from how nscale was set up ... which from recollection relies on more of a home-made messaging protocol between containers running services.

Maybe this isn't the right place for a high-level description ... but having something to reference, perhaps back over on the fuge repo would be really valuable.

Thanks.

[mcollina]

@Analect basically yes. fuge is for dev, oast is to build them for prod usage. The new tool will support docker-swarm out of the box, plus the way nscale was set up (no advanced networking, just exposed ports). It will be also easy to extend the system.
What will probably be missing is all of the AWS automation.

There will be docs when all of this is done :D.

[Analect]

Great. Thanks for the update. Let me know if I should close this issue out ... or if there's some value to having it around for others to happen upon.

[mcollina]

Let's keep it open for the time being :)