By 2019, 67 percent of software programmers will primarily be developing in the cloud, up from 18 percent today, predicted Evans Research.
Evans prediction in the tail-end of this piece on IBM going SaaS
By 2019, 67 percent of software programmers will primarily be developing in the cloud, up from 18 percent today, predicted Evans Research.
Evans prediction in the tail-end of this piece on IBM going SaaS
By 2019, 67 percent of software programmers will primarily be developing in the cloud, up from 18 percent today, predicted Evans Research.
Evans prediction in the tail-end of this piece on IBM going SaaS
Mirantis navigates changing OpenStack market, growth with 4.0 release (451 Report)
My team has a new report up on Mirantis, with updates on their momentum and an overview of what’s in their 4.0 OpenStack distro release.
Here’s the 451 take, our brief opinion on the news:
Mirantis reported more bookings in the last quarter of 2013 than all of 2012 – its growth by revenue, employees and overall business highlights the company as a leader among OpenStack pure-play vendors. Mirantis seems well positioned for an evolving OpenStack ecosystem and market, but the transition from services and support, which has been its specialty, to product subscription models may be challenging.
Mirantis navigates changing OpenStack market, growth with 4.0 release (451 Report)
My team has a new report up on Mirantis, with updates on their momentum and an overview of what’s in their 4.0 OpenStack distro release.
Here’s the 451 take, our brief opinion on the news:
Mirantis reported more bookings in the last quarter of 2013 than all of 2012 – its growth by revenue, employees and overall business highlights the company as a leader among OpenStack pure-play vendors. Mirantis seems well positioned for an evolving OpenStack ecosystem and market, but the transition from services and support, which has been its specialty, to product subscription models may be challenging.
Mirantis navigates changing OpenStack market, growth with 4.0 release (451 Report)
My team has a new report up on Mirantis, with updates on their momentum and an overview of what’s in their 4.0 OpenStack distro release.
Here’s the 451 take, our brief opinion on the news:
Mirantis reported more bookings in the last quarter of 2013 than all of 2012 – its growth by revenue, employees and overall business highlights the company as a leader among OpenStack pure-play vendors. Mirantis seems well positioned for an evolving OpenStack ecosystem and market, but the transition from services and support, which has been its specialty, to product subscription models may be challenging.
Secondly, when evaluating new IT hardware and software assets for potential adoption, you need to institute a much stronger requirement for programmability and open APIs. Complete automation of your infrastructure requires programmatic access, and it’s simply insufficient to only have control via graphical interfaces. This isn’t just about provisioning and configuration support via such APIs, you also need to ensure that vendors are providing reliable APIs to get sufficiently detailed status. A core tenet of DevOps is the ability to measure the state of your infrastructure for future improvement and this really needs to be automated programmatically. Ideally these APIs for automation and measurement are simple, easy to adopt, and accessible to people who aren’t full-time software engineers. Thus, beware of complex, language-specific APIs, and strongly lean towards vendors using simple HTTP or REST APIs and standard, easily parsable data formats like JSON.
–Nigel Kersten, Puppet Lab’s CIO. Also, see this interview I did with Nigel way back in 2008 when Nigel was using Puppet to manage the Mac desktops (!) at Google.
Secondly, when evaluating new IT hardware and software assets for potential adoption, you need to institute a much stronger requirement for programmability and open APIs. Complete automation of your infrastructure requires programmatic access, and it’s simply insufficient to only have control via graphical interfaces. This isn’t just about provisioning and configuration support via such APIs, you also need to ensure that vendors are providing reliable APIs to get sufficiently detailed status. A core tenet of DevOps is the ability to measure the state of your infrastructure for future improvement and this really needs to be automated programmatically. Ideally these APIs for automation and measurement are simple, easy to adopt, and accessible to people who aren’t full-time software engineers. Thus, beware of complex, language-specific APIs, and strongly lean towards vendors using simple HTTP or REST APIs and standard, easily parsable data formats like JSON.
–Nigel Kersten, Puppet Lab’s CIO. Also, see this interview I did with Nigel way back in 2008 when Nigel was using Puppet to manage the Mac desktops (!) at Google.
Secondly, when evaluating new IT hardware and software assets for potential adoption, you need to institute a much stronger requirement for programmability and open APIs. Complete automation of your infrastructure requires programmatic access, and it’s simply insufficient to only have control via graphical interfaces. This isn’t just about provisioning and configuration support via such APIs, you also need to ensure that vendors are providing reliable APIs to get sufficiently detailed status. A core tenet of DevOps is the ability to measure the state of your infrastructure for future improvement and this really needs to be automated programmatically. Ideally these APIs for automation and measurement are simple, easy to adopt, and accessible to people who aren’t full-time software engineers. Thus, beware of complex, language-specific APIs, and strongly lean towards vendors using simple HTTP or REST APIs and standard, easily parsable data formats like JSON.
–Nigel Kersten, Puppet Lab’s CIO. Also, see this interview I did with Nigel way back in 2008 when Nigel was using Puppet to manage the Mac desktops (!) at Google.
Finally, I have discovered a horrible, rather brutal method that I recommend only to men of excessive vigor, men with thick black hair and skin covered with liver spots, men with big square hands and legs shaped like bowling pins. It is a question of using finely pulverized, dense coffee, cold and anhydrous, consumed on an empty stomach. This coffee falls into your stomach, a sack whose velvety interior is lined with tapestries of suckers and papillae. The coffee finds nothing else in the sack, and so it attacks these delicate and voluptuous linings; it acts like a food and demands digestive juices; it wrings and twists the stomach for these juices, appealing as a pythoness appeals to her god; it brutalizes these beautiful stomach linings as a wagon master abuses ponies; the plexus becomes inflamed; sparks shoot all the way up to the brain. From that moment on, everything becomes agitated. Ideas quick-march into motion like battalions of a grand army to its legendary fighting ground, and the battle rages. Memories charge in, bright flags on high; the cavalry of metaphor deploys with a magnificent gallop; the artillery of logic rushes up with clattering wagons and cartridges; on imagination’s orders, sharpshooters sight and fire; forms and shapes and characters rear up; the paper is spread with ink - for the nightly labor begins and ends with torrents of this black water, as a battle opens and concludes with black powder.