Posted in devops
Docker Inc. plans to give customers the option to deploy one of several open-source serverless computing frameworks on top of the Docker Enterprise Edition (EE) container-as-a-service (CaaS) environment. Rather than attempting to lock customers into a specific serverless computing framework, IT organizations should be free to choose from multiple frameworks that can be deployed on-premises or in one of several public clouds, says Docker Inc. founder and CT Salomon Hykes.
At the DockerCon Europe 2017 conference, Docker Inc. announced it has made the Kubernetes container orchestration engine an equal citizen to Docker Swam within the context of Docker Enterprise Edition (EE) container-as-a-service (CaaS) platform. David Messina, senior vice president of marketing for Docker Inc., says IT organizations now have the option to decide as they deploy a containerized application if they want to deploy it on Docker Swarm or Kubernetes, noting the container orchestration engine is now an optional feature of the CaaS environment.
Chef has made good on a promise to deliver an instance of its Habitat IT automation framework delivered as cloud service that is optimized for container environments. Previewed earlier this year at a ChefConf 2017 event, the general availability of Habitat Builder makes it possible to package Docker, rkt or Mesos artifacts consistently to enable IT operations teams to deploy applications based on them to Docker Swarm, Kubernetes or platform-as-a-service (PaaS) environment based on Cloud Foundry, says Marc Holmes, vice president of marketing for Chef.
A newly rebranded Kong Inc., formerly known as Mashape, this week announced the availability of Kong Enterprise Edition, a version of the companys open-source application programming interface (API) management platform that has been designed from the ground up to support microservices based on containers. Kong Inc. CEO Augusto Marietti says the enterprise edition of Kong differs from the open-source edition in that it scales to support more API calls.
Devops is in many ways a modern evolution born out of the old way of doing things. Waterfall development methodologies were too slow, deployments to production were too infrequent, and the traditional separation of developers and operators was an obstacle to change.
Devops and cloud are the inescapable words of the decade for IT professionals, and with good reason: making the shift to digitally transform under these models can result in a business-defining transformation with increased speed, reduced costs, and better control and quality much simpler for companies to achieve. And statistics show that these models are taking off.
Managing storage in a container environment presents some unique challenges: Not only is there more data being created faster, the number of microservices trying to call the same data increases exponentially. To enable IT organizations to rise to both challenges, Red Hat has updated Red Hat Cloud-Native Storage software to increase the number of applications accessing a storage cluster by a factor of three while also enabling IT organizations, via a technology preview, to make use of the S3 API to store data on an Amazon Web Services (AWS) public cloud.
The Cloud Foundry Foundation (CFF), at a Cloud Foundry Summit Europe conference, announced it will make the Cloud Foundry Container Runtime (CFCR) the default runtime for deploying applications on Kubernetes clusters, using the BOSH lifecycle management tools it developed to manage the components that make up the foundations open-source platform-as-a-service (PaaS) environment. Abby Kearns, executive director of the CFF, says DevOps teams now can choose between CFCR, formerly known as Kubo, to deploy applications on Kubernetes or continue to use Application Runtime, previously Elastic Runtime, which CFF also provides for deploying applications.