{"id":654127,"date":"2013-04-24T09:05:36","date_gmt":"2013-04-24T13:05:36","guid":{"rendered":"http:\/\/gigaom.com\/?p=633895"},"modified":"2013-04-24T09:05:36","modified_gmt":"2013-04-24T13:05:36","slug":"joyent-says-chef-support-will-make-cloud-workloads-mobile","status":"publish","type":"post","link":"https:\/\/mereja.media\/index\/654127","title":{"rendered":"Joyent says Chef support will make cloud workloads mobile"},"content":{"rendered":"

Opscode is having a pretty good run. the devops-focused toolset. In February, Amazon launched application life cycle management console<\/a>\u00a0based on Opscode Chef. On Wednesday, Joyent said it\u2019s add full support and integration of Chef into the Joyent Cloud.<\/a><\/p>\n

Expect more pledges of support and woo to come out of Opscode\u2019s annual conference<\/a> kicking off tomorrow in San Francisco. Tools like Chef, and Puppet Labs\u2019 Puppet (see disclosure) ease the creation and management of\u00a0system configurations. One key benefit is that once the associated scripts of a deployment are created, they can be deployed regardless of the underlying operating system or, in this case, cloud. At least in theory.<\/p>\n

In Opscode parlance, Chef configurations are deployed and managed via a \u201ccookbook.\u201d Joyent\u2019s support of Chef means it will be easier, going forward, for customer to move cloud deployments to and from any cloud, said Joyent CTO Jason Hoffman in a recent interview.<\/p>\n

\u201cChef, rather than the bare APIs, thus becomes the abstraction layer,\u201d Hoffman told me. \u201cBy supporting Chef we make workloads more mobile. If Amazon calls an instance M1 why don\u2019t we have one?\u201d If that nomenclature is standard across clouds, the various scripts will work more easily anywhere.<\/p>\n

That means, in Hoffman\u2019s view, that folks who\u2019ve deployed workloads in AWS but want better and more explicit service level agreements or other contractual terms that AWS may not grant, they can move the whole kit-and-kaboodle over to Joyent or, truth be told, vice versa.<\/p>\n

As to why Chef appears to be gaining so much traction over CF Engine and Puppet? Hoffman thinks it\u2019s because Opscode is more aligned with developers whereas Puppet targets admins, or the \u201cops\u201d constituency of devops. In January, Puppet received an additional $30 million investment from VMware<\/a>, funding which leads some to see Puppet falling into the VMware camp \u2014 a contention that Puppet CEO Luke Kanies denied at the time of the deal, pledging to continue support for heterogeneous hypervisors and environments.<\/p>\n

Joyent, along with the various OpenStack-allied vendors are all hoping to take business from Amazon which, to be fair, isn\u2019t taking that potential threat lying down. AWS has been adding more enterprise-friendly features and services while its competitors add more services. Later on Wednesday, we\u2019ll hear about how the EMC and VMware-backed Pivotal Initiative<\/a> plans to take on AWS and other cloud competitors. And, to further muddy the waters, VMware said on its earnings call Tuesday night that it will launch its public-cloud take \u2014 which it calles VMware Hybrid Cloud Service<\/a>\u00a0on May 21. We\u2019re going to need a score card.<\/p>\n

No doubt we\u2019ll hear more about Hoffman\u2019s vision of mobile cloud workloads and the increasingly competitive cloudscapewhen he takes the stage at Structure 2103<\/a> in San Francisco on June 19<\/p>\n

Disclosure<\/strong>:\u00a0Puppet Labs is backed by True Ventures, a venture capital firm that is an investor in the parent company of this blog, Giga Omni Media. Om Malik, founder of Giga Omni Media, is also a venture partner at True.<\/em><\/p>\n

\"\"<\/p>\n

<\/a><\/p>\n

Related research and analysis from GigaOM Pro:<\/strong>
Subscriber content. Sign up for a free trial<\/a>.<\/p>\n