DISCLAIMER:\u00a0 I’m not the official gatekeeper of xCAT, and I don’t work for IBM. But as a large contributor to the xCAT project, as well as a user, I figured I had just as much authorization to write about what happened to xCAT in 2010 as anyone else does.\u00a0 And the best part is:\u00a0 I’m not tied to a large corporation that monitors what I can or can not say.\u00a0 So I can say, and will say anything I want to :-).\u00a0 So anyway, what I say here represents my opinions and views and don’t represent the opinions or views of the priests at IBM nor of the greater xCAT community.\u00a0 So tell your lawyers to go away.<\/p>\n
So If nothing else, this is to give you something to read about while you’re recovering from your new years eve party.\u00a0 I present:\u00a0 The xCAT 2010 Year in review:<\/p>\n
To start off with, I just want to thank all the users and developers that I’ve been able to work with this year. It’s been nothing short of incredibly amazing.\u00a0 We’ve been working on tough problems.\u00a0 The xCAT user base has some of the most talented, passionate, and dedicated people in the industry.\u00a0 (And in most cases are smarter than us developers)\u00a0 It was great to work with all of them this year.\u00a0 I am thankful for your insites and criticism.\u00a0 We hope people become more critical of xCAT and don’t sugar coat anything.\u00a0 I didn’t work with one person this year on xCAT problems that I didn’t walk away from thinking: “Hmm, that <dude|lady> is pretty smart”.\u00a0 So the talent inside the xCAT users group is fantastic.\u00a0 You can tell that by the types of comments that come into the mailing list.\u00a0 They’re much different than what you might see on other open source projects.\u00a0 So the biggest story of 2010 for xCAT:\u00a0 The users moved mountains, and helped make xCAT better.<\/p>\n
Enough flattery.\u00a0 As far as releases, xCAT went from the 2.3.4 release in March and culminated with 2.5.1 that was released Dec 11th.\u00a0 Its nice to see the releases coming so rapidly.\u00a0 I don’t anticipate this will be the case in 2011.\u00a0 I think we’ll see slower major release cycles and minor release cycles will just coincide with OS updates (VMware’s updates, RHEL6 stuff, SLES, etc.)\u00a0 Most of the reason I think things may slow down is because xCAT is pretty feature complete.\u00a0 It can do lots of things.\u00a0 It could use lots of clean up work, but nobody seems to be interested in doing that.\u00a0 Most developers I think just accept that no error messages are printed when XYZ happens, and look at it as a learning opportunity for you to become acquainted with the xCAT code.\u00a0 That’s too bad in my opinion.<\/p>\n
There lots of features added to xCAT that made its awesomeness ooze even more than ever.\u00a0 As usual, I usually skip all the awesomeness that was added to xCAT’s IBM’s AIX and SystemP functionality, since I don’t ever work on that aspect of xCAT, and usually just complain about the table pollution the AIX tables cause. (You know who you are: ppc, ppcdirect, pchcp, nimimage, etc) However, from what little I do know they’ve been pretty busy with it this year and I am glad to work with them on some small scale on this great product.<\/p>\n
VMware Support<\/strong> – VMware ESX support has been in xCAT for a long time.\u00a0 But this year we added better stateless ESXi support (The first ever) and also ESXi kickstart support with ESXi 4.1 (I think we’re the only project that has that).\u00a0 We also added cloning, thin or thick, and lots of other cool features to support VMware virtual machines.<\/p>\n On the KVM<\/strong> front, we did the same if not better.\u00a0 So if you’re running VMware or KVM on your nodes, xCAT doesn’t care, it looks the same.<\/p>\n imgimport\/imgexport<\/strong> – We started the ability to import or export images (stateless and stateful) into xCAT.\u00a0\u00a0 This is still not as mainstream as I’d like it to be, but we hope to add more to this in 2011.\u00a0 I still dream of Sumavi.com supporting some type of physical machine image store.<\/p>\n Dynamic DNS<\/strong> – Dynamic DNS was added to xCAT and I don’t think used as often.\u00a0 But it assigns discovered nodes static IP addresses so that\u00a0 you don’t need to predefine them in \/etc\/hosts.\u00a0 This is great and a step further to making automagic discovery even more magical.<\/p>\n Statelite<\/strong> – xCAT has had stateless (RAM root in tmpfs ) support since 2005.\u00a0 It’s also had a type of hybrid with NFS.\u00a0 But now we’ve made statelite:\u00a0 This allows stateless, with NFS root, with a real hard drive for statefull files.\u00a0 Its wild.\u00a0 Give it a try.\u00a0 It probably offers the most extreme way to manage a system.\u00a0 The coolness of the hierarchical tree support is frightening.<\/p>\n Sumavisor<\/strong> – This isn’t xCAT proper, but a nice Web Interface to xCAT has finally been added by Sumavi.\u00a0 (More on that in the next section)<\/p>\n I think a big highlight is the emergence of a company that is dedicated to bringing xCAT to the masses and is not afraid to invest in it.\u00a0 This is my company, Sumavi<\/a> , founded Feb 2010 :-).\u00a0 We have done very well this year with service engagements with some big time accounts.\u00a0 In addition we’ve made some great partners, turned out some solid documentation<\/a> and made a really nice GUI front end to xCAT that we’ve branded ‘The Sumavisor’.\u00a0 And its not just a GUI.\u00a0 It does much more than that, enhancing xCAT to make it look polished and add control and insight that you can’t get on the command line.\u00a0 It also does a lot to cut the learning curve down and adds commercial support to all xCAT installations regardless of what hardware they are running on.<\/p>\n As far as the community goes, I had a rant on xCAT’s documentation problem.\u00a0 Others at IBM have attempted to make the xCAT documentation more usable.\u00a0 You can see it here<\/a>.\u00a0 It’s definitely better than it was and is a step in the right direction, but I feel like the Sumavi documentation<\/a> is much more usable.\u00a0 But you tell me.<\/p>\n In other news, we rolled out xCAT in banks, credit card companies, and the usual blend of government and university accounts.\u00a0 But the most exciting is to see xCAT venture into corporations that are not focused on HPC.\u00a0 This year we installed the Lego Universe MMOG environment using xCAT.\u00a0 It was an all Windows environment too!\u00a0 We did some cool stuff all over the place.\u00a0 Even while not at IBM I was able to talk to developers at IBM and from all over the world.<\/p>\n In addition, we really broke out and started supporting hardware from Dell, HP, and other whiteboxes.\u00a0 I even started developing the Cisco UCS xCAT module.\u00a0 I haven’t finished it yet… I’ll wait for Cisco to cough up some support dollars for that.\u00a0 You hearing me Cisco?<\/p>\n 2011 I hope we will continue to see xCAT do more outside of HPC. I hope to get into more cloud deployments.\u00a0 We’ve already done a bunch.\u00a0 But we’d like to have more packaged products.\u00a0 I see us coming out with EC2 support. (not based on anything but Amazon APIs (sorry, but we heard too many complaints about the open source version of Eucalyptus)), I also see more appliance based models, like Hadoops.<\/p>\n As more people want to drive xCAT, ad Web Services API is in the works.\u00a0 Right now you can perform xCAT calls via XML messages to port 3001 with xCAT, but this needs to be more robust.\u00a0 We’ve done that with the Sumavisor, but there is more that needs to be done.\u00a0 Hopefully that will be out in the first half of the year.<\/p>\n And finally, the biggest thing about cloud is that its all about the applications.\u00a0 How will we deal with making applications more agile?\u00a0 I see this as a major focus for our group.\u00a0 Creating virtual machines, etc is great, but how do we help, or is it even our role to help with the creation of the contents of those machines?\u00a0 We seem to be in that world already.\u00a0 But where or should we draw the line between xCAT and things like RightScale.\u00a0 Where or should we draw the line between xCAT and Chef, Puppet, etc?<\/p>\n I don’t know yet and I can’t wait to find out.<\/p>\n Anyway, I hope you had a wonderful 2010 and I hope 2011 is just as wild for you!<\/p>\n","protected":false},"excerpt":{"rendered":" DISCLAIMER:\u00a0 I’m not the official gatekeeper of xCAT, and I don’t work for IBM. But as a large contributor to the xCAT project, as well as a user, I figured I had just as much authorization to write about what happened to xCAT in 2010 as anyone else does.\u00a0 And the best part is:\u00a0 I’m…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[916],"tags":[],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/benincosa.com\/index.php?rest_route=\/wp\/v2\/posts\/319"}],"collection":[{"href":"https:\/\/benincosa.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/benincosa.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/benincosa.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/benincosa.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=319"}],"version-history":[{"count":4,"href":"https:\/\/benincosa.com\/index.php?rest_route=\/wp\/v2\/posts\/319\/revisions"}],"predecessor-version":[{"id":2801,"href":"https:\/\/benincosa.com\/index.php?rest_route=\/wp\/v2\/posts\/319\/revisions\/2801"}],"wp:attachment":[{"href":"https:\/\/benincosa.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=319"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/benincosa.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=319"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/benincosa.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=319"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Non Technological Highlights<\/h2>\n
Predictions for 2011<\/h2>\n