4 ms·
Nomad dev here. I'd love to hear unbiased answers to your question, but here are my biased thoughts. :) > Can anyone elaborate on what that immaturity consists
by schmichael 10y ago
Nomad dev here. I'd love to hear unbiased answers to your question, but here are my biased thoughts. :)
> Can anyone elaborate on what that immaturity consists of at the moment?
We're pre-1.0 for a reason. While you're right we leverage Consul for discovery and health checks and Vault for secrets, there are still quite a few gaps we plan to fill before hitting 1.0. We need a plugin infrastructure to support volume and network plugins. There's still resource constraints to be added (eg gpus) or improved upon (eg storage accounting). I'd personally love to get secure mTLS bootstrapping via Vault to be as painless as our server discovery via Consul. Lots to do, so expect regular improvements as we move toward 1.0.
tl;dr - The immaturity and pre-1.0 version are due to missing features, not instability or lots-of-breaking-changes.
- bogomipz 10y agoThanks for the reply, good to know. Is there a current roadmap anywhere I can view? I looked at the Google Group for Nomad but the last roadmap post I saw was 0.4.
- schmichael 10y agoWe have an internal one that we keep private mainly because it changes so often it would be more frustrating than useful to users. We should still do a better job of making issues for all major work items and probably publishing some sort of high level list of desired features for 1.0.
- bogomipz 10y agoI understand. Maybe you could post the high level list(that's actually what I meant in my other question) to the Nomad Google group? Do you have any ball park of how far off a 1.0 release might be? Cheers.