tag:blogger.com,1999:blog-4503292949532760618.post1905389825804653156..comments2024-03-28T13:39:27.601-07:00Comments on DSHR's Blog: Seagate's Ethernet Hard DrivesDavid.http://www.blogger.com/profile/14498131502038331594noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-4503292949532760618.post-79211809258868868332013-11-01T23:12:44.028-07:002013-11-01T23:12:44.028-07:00For the drive connector: I know of no IP restricti...For the drive connector: I know of no IP restricting the connector only to only be used for SAS. <br /><br />As for a second source: We are fully aware that many customers want a second source and we hope that one comes along. (which is another comment I made at Basho-Ricon meeting)jameshttps://www.blogger.com/profile/08598704171240240252noreply@blogger.comtag:blogger.com,1999:blog-4503292949532760618.post-31251083903926624162013-10-31T10:38:01.440-07:002013-10-31T10:38:01.440-07:00James, thanks for the corrections. Kinetic seems t...James, thanks for the corrections. Kinetic seems to suffer from some poor choices of name. It wasn't clear to me from the Javadoc that "Tag" meant integrity token, and I agree with Jeff Darcy when he says "That's fine for a key/value store or a deep archival store (the very opposite of "kinetic" BTW)" but I disagree with most of the rest of his post since he seems not to realize that the target market for this technology is precisely "a key/value store or a deep archival store".<br /><br />One other issue I forgot to raise is the question of the drive connector. The storage media market has a long history of great benefits from non-proprietary media connectors. I assume that the re-purposing of the SAS connector is not encumbered with IP protection. But I for one would feel a lot better about adopting this technology for long-term storage if there were a second source for the media. And there's only one viable second source for Seagate's hard drives.David.https://www.blogger.com/profile/14498131502038331594noreply@blogger.comtag:blogger.com,1999:blog-4503292949532760618.post-90240110814425743162013-10-31T00:34:35.905-07:002013-10-31T00:34:35.905-07:001) The wire protocol will be released in the open....1) The wire protocol will be released in the open. It is our goal to make this available to the community.<br /><br />2) The Library software will be released open source. <br /><br />(I made these statements publicly at the Basho Ricon-West conference yesterday).<br /><br />3) Sorry, the API does have the ability to put a Tag field in the "EntryMetaData". This field is both preserved and checked by the drive on a regular basis. This is documented in the javadoc.jameshttps://www.blogger.com/profile/08598704171240240252noreply@blogger.comtag:blogger.com,1999:blog-4503292949532760618.post-5205152622208251882013-10-30T10:43:09.929-07:002013-10-30T10:43:09.929-07:00This is a very interesting move in the storage spa...This is a very interesting move in the storage space. Unfortunately, Jeff Darcy pointed out some significant problems with this particular implementation:<br />http://pl.atyp.us/2013-10-comedic-open-storage.htmlChris Adamshttps://www.blogger.com/profile/06132981126518774942noreply@blogger.com