It does not actually solve the trickiness of managing large storage but relies on the backend (that is usually fs like zfs in small setups).

However, seems to be quite new project plus the risk, that the owning company takes it to bad direction, is there too.

https://github.com/versity/versitygw/

Nowadays supports 3D also, but that is recent feature and will definitely evolve for some time.

However, for VM orchestration. OpenStack has been my choice for long time, but about to check KubeVirt and (old and underappreciated?) Apache CloudStack.

If so, then the decision is more like, whether to use a public or private certificate for an internal service.

Probably, it could be end result of unconsistent design or bad technical choises. However, most likely it just means that there are multiple organizations and interest groups pushing changes and ideas to the project. This should be seen as a good thing. The downside is that there is no single source of best practices and this is confusing to newcomers. You just need to pick one distribution and trust the choises, or develop the competence and understanding.

And we could imagine that the userbase or the number of developers in single distribution (take OpenShift or Rancher) could be bigger that in Nomad itself.

Having said that, I still would like to see more stable Kubernetes landscape, and that has to happen eventually. The light distributions k3s and k0s are pushing things to nice direction.

OpenStack had similar, or maybe even worse, fragmentation and complexity issue when the hype was high. There were probably technically better alternatives (Eucalyptus?), but people (and companies) gathered around OpenStack and it won the round. However, comparing OpenStack to Kubernetes feels bad, as Kubernetes is technically far superior.

However, I would highlight, that it's ability to work in multi-monitor is huge selling point.

You would like to show something from an another screen, plug the cable, press suitable hotkey, and the workspace, that you were just working on, jumps to the new display. No need to move windows.

You go back to your desk and plug in the laptop. The workspaces will automatically jump to the monitors, per your config.

Next, you run to a meeting, the very same workspaces collapse back to laptop's monitor automatically.

There was no need to touch windows in any of these scenarios, And no more "I forgot the browser windows to the attached display" that has happened with some other systems.

Very welcome suprise! I was excited about pNFS four years ago, but couldn't find any open source system to play with. Finally it is time for some mirrored pNFS testing.

Plus, you can always switch between plain and FreeNAS installation.

I would favor older and more established project, but maybe I'm focusing too much in Document Management and haven't thought about the collaboration aspect. PaperNIC might be better there.

- packer, that is a really nice and simple image building tool. It saved lot's of headache compared to tools like oz, because packer fails fast and saves debugging time.

- terraform, that is comparable to OpenStack Heat or AWS CloudFormations. Each have their own issues. But terraform being platform agnostic is an advantage for me.

- vagrant is not modern anymore, but it's ubiquitous.

edit. And oh yes, the memory usage of the default installation is so low, that you can virtualize dozens of them on your laptop. This helps when you want to locally reproduce the stack you run in cloud.

Comments URL: https://news.ycombinator.com/item?id=11452738

Points: 2

# Comments: 0