I think MVP does not mean "crappy product". MVP means just a version of product (which is working, tested, etc.) which can collect the maximum amount of validated learning with the least effort. In other words, my understanding is that MVP should cover main use case in order to validate if that is what your potential customers want (as my mentor was saying "it must not suck"). So, in your example, if scaling up to 100TB is the key value proposition then you have to have it. On the other hand, CLI, nice GUI, nice installation, etc. are not probably part of your MVP.