Author: johnmark

  • On the Gluster vs Ceph Benchmarks

    If you’ve been following the Gluster and Ceph communities for any length of time, you know that we have similar visions for open software-defined storage and are becoming more competitive with each passing day. We have been rivals in a similar space for some time, but on friendly terms – and for a couple of simple reasons: 1.) we each have common enemies in the form of proprietary big storage and 2.) we genuinely like each other. I’m a Sage Weil fan and have long been an admirer of his work. Ross Turk and Neil Levine are also members of the Inktank clan whom I respect and vouch for on a regular basis. There are others I’m forgetting, and I hope they don’t take it personally!

    So you can imagine the internal debate I had when presented with the first results of a Red Hat Storage comparison with Ceph in a set of benchmarks commissioned by the Red Hat Storage product marketing group (for reference, they’re located here). If you saw my presentations at the OpenStack Summit in Hong Kong, then you know I went with it, and I’m glad I did. While the Ceph guys have been very good about not spouting FUD and focusing instead on the bigger picture – taking down EvilMaChines, for example – others in the clan of OpenStack hangers-on have not been so exemplary.

    I don’t know who, exactly, the Red Hat Storage marketing group was targeting with the benchmarks, but I am targeting a very specific audience, and it isn’t anyone associated with Inktank or the Ceph project. I am targeting all the people in the OpenStack universe who wrote us off and wanted to declare the storage wars over. I’m also a bit tired of the inexplicable phrase that “Ceph is faster than Gluster”, often said with no qualification, which I’ve known for sometime was not true. It’s that truism, spouted by some moustachioed cloudy hipsters at an OpenStack meetup, that rankles me – almost as much as someone asking me in a public forum why we shouldn’t all ditch Gluster for Ceph. The idea that one is unequivocally faster or better than the other is completely ridiculous – almost as ridiculous as the thought that hipsters in early 20th century drag are trusted experts at evaluating technology. The benchmarks in question do not end any debates. On the contrary, they are just the beginning.

    I felt uneasy when I saw Sage show up at our Gluster Cloud Night in Hong Kong, because I really didn’t intend for this to be an “In yo’ face!” type of event. I did not know beforehand that he would be there, but even if I had, I wouldn’t have changed my decision to show the results. The “Ceph is faster” truism had become one of those things that everyone “knows” without the evidence to support it, and the longer we let it go unopposed, the more likely it was to become a self-fulfilling prophecy. Also, while we may have common enemies, it has become increasingly clear that the OpenStack universe would really prefer to converge around a single storage technology, and I will not let that happen without a fight.

    We’ve radically improved GlusterFS and the Gluster Community over the last couple of years, and we are very proud of our work. We don’t have to take a back seat to anyone; we don’t have to accept second place to anyone; and we’re not going to. In the end, it’s very clear who the winners of this rivalry will be. It won’t be Ceph, and it won’t be Gluster. It will be you, the users and developers, who will benefit from the two open source heavyweights scratching and clawing their way to the top of the heap. Rejoice and revel in your victory, because we work for you.

    To see the benchmark results for yourself, see the Red Hat Storage blog post on the subject.

    To see the VAR Guy’s take, see this article.

  • Gluster Community Congratulates OpenStack Developers on Havana Release

    The Gluster Community would like to congratulate the OpenStack Foundation and developers on the Havana release. With performance-boosting enhancements for OpenStack Block Storage (Cinder), Compute (Nova) and Image Service (Glance), as well as a native template language for OpenStack Orchestration (Heat), the OpenStack Havana release points the way to continued momentum for the OpenStack community. The many storage-related features in the Havana release coupled with the growing scope of typical OpenStack deployments demonstrate the need for scale-out, open software-defined storage solutions. The fusion of GlusterFS open software-defined storage with OpenStack software is a match made in cloud heaven.

    Naturally, the Gluster Community would like to focus on OpenStack enhancements that pertain directly to our universe:

    • OpenStack Image Service (Glance)
      • OpenStack Cinder can now be used as a block-storage back-end for the Image Service. For Gluster users, this means that Glance can point to the same image as Cinder, which means it is not necessary to copy the entire image before deploying, saving some valuable time.
    • OpenStack Compute (Nova)
      • OpenStack integration with GlusterFS utilizing the QEMU/libgfapi integration reduces the kernel space to user space context switching to significantly boost performance.
      • When connecting to NFS or GlusterFS backed volumes, Nova now uses the mount options set in the Cinder configuration. Previously, the mount options had to be set on each Compute node that would access the volumes. This allows operators to more easily automate the scaling of their storage platforms.
      • QEMU-assisted snapshotting is now used to provide the ability to create cinder volume snapshots, including GlusterFS.
    • OpenStack Orchestration (Heat)
      • Initial support for native template language (HOT). For OpenStack operators, this presents an easier way to orchestrate services in application stacks.
    • OpenStack Object Storage (Swift)
      • There is nothing in the OpenStack Havana release notes pertaining to GlusterFS and Swift integration but we always like to talk about the fruits of our collaboration with Swift developers. We are dedicated to using the upstream Swift project API/proxy layer in our integration, and the Swift team has been a pleasure to work with, so kudos to them.
    • OpenStack Data processing (Savanna)
      • This incubating project enables users to easily provision and manage Apache Hadoop clusters on OpenStack. It’s a joint project between Red Hat, Mirantis and HortonWorks and points the way towards “Analytics as a Service”. It’s not an official part of OpenStack releases yet, but it’s come very far very quickly, and we’re excited about the data processing power it will spur.

    To give an idea of the performance improvements in the GlusterFS-QEMU integration that Nova now takes advantage of, consider the early benchmarks below published by Bharata Rao, a developer at IBM’s Linux Technology Center.

     

    FIO READ numbers

    aggrb (KB/s) minb (KB/s) maxb (KB/s)
    FUSE mount 15219 3804 5792
    QEMU GlusterFS block driver (FUSE bypass) 39357 9839 12946
    Base 43802 10950 12918

    FIO WRITE numbers

    aggrb (KB/s) minb (KB/s) maxb (KB/s)
    FUSE mount 24579 6144 8423
    QEMU GlusterFS block driver (FUSE bypass) 42707 10676 17262
    Base 42393 10598 15646

     

    “Base” refers to an operation directly on a disk filesystem.

    Havana vs. Pre-Havana

    This is a snapshot to show the difference between the Havanna and Grizzly releases with GlusterFS.

    Grizzly Havana
    Glance – Could point to the filesystem images mounted with GlusterFS, but had to copy VM image to deploy it Can now point to Cinder interface, removing the need to copy image
    Cinder – Integrated with GlusterFS, but only with Fuse mounted volumes Can now use libgfapi-QEMU integration for KVM hypervisors
    Nova – No integration with GlusterFS Can now use the libgfapi-QEMU integration
    Swift – GlusterFS maintained a separate repository of changes to Swift proxy layer Swift patches now merged upstream, providing a cleaner break between API and implementation

     

    The Orchestration feature we are excited about is not Gluster-specific, but has several touch points with GlusterFS, especially in light of the newly-introduced Manila FaaS project for OpenStack (https://launchpad.net/manila). Imagine being able to orchestrate all of your storage services with Heat, building the ultimate in scale-out cloud applications with open software-defined storage that scales with your application as needed.

    We’re very excited about the Havana release and we look forward to working with the global OpenStack community on this and future releases. Download the latest GlusterFS version, GlusterFS 3.4, from the Gluster Community at gluster.org, and check out the performance with a GlusterFS 3.4-backed OpenStack cloud.

  • Some Thoughts on Gluster Community Governance

    tl;dr
    – This is a long description designed to elicit constructive discussion of some recent Gluster Community governance initiatives. For all things related to Gluster Community Governance, see gluster.org/Governance

    The recent initiatives around GlusterFS development and project governance have been quite amazing to witness – we have been making steady progress towards a “real” open source model for over a year now, and the 3.5 planning meetings are a testament to that.

    You may have also noticed recent announcements about organizations joining the Gluster Community and the formation of a Gluster Community Board. This is part of the same process of opening up and making a better, more active community, but there is a need to define some of the new (and potentially confusing) terminology.

    – Gluster Community: What is the Gluster Community? It is a group of developers, users and organizations dedicated to the development of GlusterFS and related projects. GlusterFS is the flagship project of the Gluster Community, but it is not the only one – see forge.gluster.org to get a sense of the scope of the entire ecosystem. Gluster Community governance is different from GlusterFS project governance.

    – Gluster Community Board: This consists of individuals from the Gluster Community, as well as representatives of organizations that have signed letters of intent to contribute to the Gluster Community.

    – Letter of Intent: document signed by organizations who wish to make material contributions to the Gluster Community. These contributions may take many forms, including code contributions, event coordination, documentation, testing, and more. How organizations may contribute is listed at gluster.org/governance

    – Gluster Software Distribution: with so many projects filling out the Gluster Community, there is a need for an incubation process, as well as a need for criteria that determine eligibility for graduating from incubation into the GSD. We don’t yet know how we will do this and are looking for your input.

    We realized some time ago that there was quite a demand for contributing to and growing the community, but there was no structure in place to do it. The above is our attempt to create an inclusive community that is not solely dependent on Red Hat and enlists the services of those who view the Gluster Community as a valuable part of their business.

    All of this is in-process but not yet finalized. There is an upcoming board meeting on September 18 where we will vote on parts or all of this.

    For all links and documents regarding Gluster Community governance, you can always find the latest here: gluster.org/Governance

  • New Release Cycle (and deadlines) for GlusterFS 3.5

    As you may have already heard, the GlusterFS 3.5 release planning cycle is well underway. The deadline is this Thursday, August 14. If you have a feature or patchset you’ve been working on and want to include it in the GlusterFS 3.5 release, please update the page and add your feature proposal to the list. […]
  • The Summer of Gluster is Here!

    I wanted to take a moment and share all the things that are going on in the Gluster Community. It really has been an amazing year, and we’re only halfway through. Here’s a recap for those of you watching from home: Launched the Gluster Community Forge in early May – http://forge.gluster.org/ as of now, there […]
  • GlusterFS portability on full view – ARM 64

    Today at Red Hat Summit, Jon Masters, Red Hat’s chief ARM architect, demonstrated GlusterFS replicated on two ARM 64 servers, streaming a video. This marks the first successful demo of a distributed filesystem running on ARM 64. Video and podcast to come soon.    
  • GlusterFS is Ready for OpenStack

    Amidst the madness of the OpenStack Summit a couple of weeks ago, you could be forgiven for not seeing a Red Hat announcement about GlusterFS being “OpenStack-ready”. You may wonder, what exactly do we mean by “OpenStack-ready”? The first thing to understand is that storage in OpenStack is multifaceted. It could mean applications storing objects […]
  • Introducing the Gluster Community Forge

    Today, I’m happy to finally unveil something that we’ve been working on for a couple of months now: the Gluster Community Forge. We noticed some time ago that there were several projects out on the internet that extended GlusterFS, and we thought it would be nice to give them a home, where users could find […]
  • The Death of Proprietary Software

    Whenever I give talks at conferences, there’s always one particular topic I make sure to bring up. I’ll ask the audience, “Quick, name a new proprietary enterprise software product to have gained ubiquity in the data center over the last 12 months.” I’ll wait a few seconds, and then, “Ok, 24 months.” After a brief […]
  • The Business of Open Source

    As the Gluster Community Lead, I deal with quite a number of moving parts on a daily basis: mailing lists, web sites, groups of volunteers, workshop schedules, budgets and team members. As we go through our community restructuring (more detail on that Real Soon Now), it occurred to me that managing a large open source community looks a lot like any other upper level management or executive role. I am ultimately responsible for determining strategic direction, writing a business plan that marshalls the resources in pursuit of that strategic direction, winning over support and resources to implement said strategy, and then executing on a plan to reach the strategic goals. It’s part sales job, part taskmaster, part cheerleader, and part captain of the ship.

    Gone are the days when managing a community meant taking a low-risk job with low expectations. These days, leading a community comes with deliverables and a ton of responsibility, as well as the sense that you are directly responsible for future revenue and sales. Hey, no pressure! And if you screw it up, your employer and/or the community you represent takes a public hit to the face, sometimes at the hands of an angry mob. Don’t get me wrong, I wouldn’t trade this job for the world. I’m not complaining, just cognizant of how important community leadership has become over the years. Really, it’s very much in line with running a startup, except without having to deal with VCs.

    It didn’t used to be that way. For most companies, the community guy was an afterthought, some guy you paid less than your other people to look after some forums and keep the web site running. And even then, there was a good chance that executives above you didn’t see the point of your existence, not understanding why they couldn’t just toss the code over the wall and “let the community take care of it.” If you were lucky, you got a small budget for web site design or maybe to buy some adwords keywords. Now, those executives who didn’t get it are usually no longer with the company, or if they are, they’re not so far removed from you in the org chart. And chances are, there are enough people around who understand what you’re doing without your having to explain it to them over and over again. Now, we have budgets that rival many other departments – all because of one thing: if a company invests in an open source community, it is strategically important. Now, there are many more companies who understand the leverage game, as in, if you have the leading technology in a given area, your leverage increases significantly. And one of the best ways to win leverage? Show leadership in an open source community.

    Look around you – open source communities are used by companies to make a statement and put themselves on the map. Netflix, Twitter, Facebook, and many others use open source participation as a means to several ends, including recruiting, employee retention, industry disruption and coalition building (frenemies FTW!)

    This is the way business is conducted now, and it’s a far cry from when I started. While the risks are greater, it’s especially gratifying to be an equal at the adult table.