Just spit-balling here....
-
They do sell, but it isn't the massive market that you would imagine. The big money of SAN and NAS solutions is in their sales teams. If you aren't adding 100% markup so that you can take people to dinner and give away golf club memberships, people aren't buying your storage. Just because we CAN sell things at a fraction of the price doesn't mean that we can put a salesforce out there wining and dining the decision makers. That's how nearly all storage is sold.
-
@scottalanmiller who is selling the "home-brew" NAS units that are mentioned?
-
@DustinB3403 said:
@scottalanmiller who is selling the "home-brew" NAS units that are mentioned?
I would never associate terms like "home brew" or "DIY" to a SAM-SD approach. Remember this is the identical process to how all enterprise servers are handled. Would you call your domain controller "home brew" or your database server a "DIY"?
-
Sadly... with where I am employed at the moment I would call the DC and file servers Home Brew and DIY and DWTH (Disaster waiting to happen)
-
@DustinB3403 said:
Sadly... with where I am employed at the moment I would call the DC and file servers Home Brew and DIY and DWTH (Disaster waiting to happen)
But what about them makes them home brew? Did you write the OS in your space time? What makes them more or less "home brew" than any server in any enterprise? What makes them different than say a million dollar IBM mainframe? Expense, of course, and the quality and size of the parts, but the process of buying a server, installing an OS and setting it up is always the same. One is not more "home brew" than the other. This is a critical mindset that needs to be fixed as it is often used to sell low quality, overpriced appliances to management who get confused about how servers are deployed.
-
The OS is all Microsoft Server 2### so an Enterprise operating system. The equipment that this is installed onto is my concern its not much more than a consumer desktop.
Hopefully I can get this to change for the better in the immediate future.
-
@DustinB3403 said:
The OS is all Microsoft Server 2### so an Enterprise operating system. The equipment that this is installed onto is my concern its not much more than a consumer desktop.
Hopefully I can get this to change for the better in the immediate future.
But that isn't homebrew in the least, it's just junk. Unrelated concepts. You can say a BMW is an enterprise car and a Toyota is junk. But no matter how crappy your Toyota is, it doesn't become homemade until you start getting parts and putting your own car together. The amount that it is "manufactured" in the same style process as a BMW is 100%. Quality is not related to the concept of being made at home as a hobby project.
-
I disagree. Buying all of the components and putting it together is homebrew.
-
@JaredBusch said:
I disagree. Buying all of the components and putting it together is homebrew.
I would agree to some degree IF we are talking about whiteboxing. I'm not clear that that is what they have done.
Although, do you feel the same way if you get parts for a Proliant or a PowerEdge? What about self-assembly of a SuperMicro? It's a grey area as we almost always do some amount of assembly manually and almost always some is done for us. At what point, how many or which components, that we have to do ourselves does it switch from a "pre-made server" to a "homebrew"? Whitebox we know is when we assemble disassociated parts, but just assembling stuff at home doesn't imply that we are doing anything more "at home" than putting in a few screws.
The problem is, it implies so much more than is there. Even assembling a server from scratch (I've done this on a Proliant recently) I would never call that home brew. I think the term doesn't apply to servers. We have OEM and whitebox systems that cover the describable aspects. Homebrew makes people think of the IT guy "making" some aspect of the system himself (the OS, the application, the hardware... something) that goes above and beyond the existing concept of a whitebox.
At least that is how I hear it used - and people use the term to refer to Proliant and PowerEdge servers normally, not in the way that Dustin might be using it here. They actually use it on Spiceworks to mean "installing an OS yourself" being homebrew. Meaning every cloud system, every VM, every normal server is homebrew to those people.
-
I get that taking a bunch of spare parts laying around your house and assembling them into something that kind of works seems pretty home-brewish and I'd be okay if the term was being used when that happened and not just when someone has to install a server OS. But it shouldn't be linked to quality specifically, perhaps to support or something.
-
Here is another topic on a very close line to this one.
-
@DustinB3403 said:
Here is another topic on a very close line to this one.
That's whitebox vs. OEM, it sounds like.
-
@JaredBusch said:
I disagree. Buying all of the components and putting it together is homebrew.
Then every IBM/HP/Dell sever I've ever installed is homebrew I guess.
-
@JaredBusch said:
I disagree. Buying all of the components and putting it together is homebrew.
@Dashrender said:
Then every IBM/HP/Dell sever I've ever installed is homebrew I guess.
You buy the components and put them all together?
-
@JaredBusch said:
@JaredBusch said:
I disagree. Buying all of the components and putting it together is homebrew.
@Dashrender said:
Then every IBM/HP/Dell sever I've ever installed is homebrew I guess.
You buy the components and put them all together?
I buy the server and install the HDDs and RAM, and if needed, the second processor. Doesn't that qualify for what you are saying?
FYI, I'm also totally dogging you - I don't consider this homebrew in the least. Whiteboxes, things below SuperMicro are where homebrew comes to my mind.
The idea that @scottalanmiller mentions where people think that installing and OS suddenly makes a machine a homebrew is just ludicrous. That would make nearly every machine on the planet a homebrew, someone has to install it, or build the scripts, etc to do the install.
-
@scottalanmiller is the only one who called install the OS a homebrew. no one else did.
@Dashrender said:
I buy the server and install the HDDs and RAM, and if needed, the second processor. Doesn't that qualify for what you are saying?Honestly, it damn near does. Why are you not buying this server built to spec? How much are you saving doing it yourself? How much time are you spending researching things and choosing components, etc.
-
@JaredBusch said:
@Dashrender said:
I buy the server and install the HDDs and RAM, and if needed, the second processor. Doesn't that qualify for what you are saying?
Honestly, it damn near does. Why are you not buying this server built to spec? How much are you saving doing it yourself? How much time are you spending researching things and choosing components, etc.
Hold the phone - who specs your servers? Don't you do that? meaning you need to do all that research to know what parts you want in the box?
Now sure, I could pay CDW to put all of the components into the chassis, but frankly I enjoy that bit of down time in the mental process.
-
@JaredBusch said:
@scottalanmiller is the only one who called install the OS a homebrew. no one else did.
I thought he was quoting someone(s) from SW?
-
@JaredBusch said:
@scottalanmiller is the only one who called install the OS a homebrew. no one else did.
Was not me. I specifically say that this is never homebrew. I've only said the exact opposite.
-
@Dashrender said:
The idea that @scottalanmiller mentions where people think that installing and OS suddenly makes a machine a homebrew is just ludicrous. That would make nearly every machine on the planet a homebrew, someone has to install it, or build the scripts, etc to do the install.
The term that people in SW use for installing your own OS repeatedly is "DIY". It was only @DustinB3403 that I've ever seen use homebrew and he was using it to be "crappy", FWICT.
