[ad_1]
Cloud Foundry, the open source platform project as a service used by more than half of Fortune 500 companies to help them design, test and deploy their applications, launched well before the existence of Kubernetes. For this reason, the team has created Diego, its own container management service. Unsurprisingly, given the popularity of Kubernetes, which has become somehow the de facto standard for container orchestration, a number of Cloud Foundry ecosystem companies have begun to look for how to use Kubernetes to replace Diego.
The result is the Eirini project, first proposed by IBM. As the Cloud Foundry Foundation announced today, Project Eirini is now pbading the core functional tests that the team runs to validate the software versions of its application environment, the core Cloud Foundry service that deploys and manages the applications (if it confuses you, Think of the fact that there is also a Cloud Foundry Container runtime environment, which already uses Kubernetes, but which is mainly intended to give businesses a unique platform for running their own applications and preconstructed containers from third party suppliers).
"It's a very important step," said Chip Childers, chief technology officer at the Cloud Foundry Foundation. "The project team must now move to a mode where they are working to strengthen the solution and make it a little more ready for production. But at this point, the first users are also starting to deploy this technology. [new] architecture."
Childers pointed out that while the project was incubated by IBM, who has long supported the global Cloud Foundry project, Google, Pivotal and others are also contributing and have full-time engineers working on the project. In addition, SUSE, SAP and IBM are also actively involved in the development of Eirini.
Eirini started as an incubation project and, although few doubted the success of this project, there was a bit of confusion about how Cloud Foundry would progress now that it had essentially two engines. container to perform its main service. At the time, there was even a fear that the project would come to fruition. "At that time, I reacted by saying no, this is the natural exploration process that open source communities have to undergo," Childers said. "What we see now is that Pivotal and Google intervene, it is a very clear sign that it will be the architecture of tomorrow for the future runtime of the Cloud Foundry application. "
By the way, a few months ago, Kubernetes still lacked some crucial elements that the Cloud Foundry ecosystem needed to make that change. Childers specifically noted that support for Windows – what project business users really need – remains problematic and lacks some important features. In recent releases, the Kubernetes team has solved most of these issues and improved its support for Windows, making these issues irrelevant.
What does it all mean for Diego? Childers noted that the community is not at a point where it will develop this tool. However, at some point, it seems likely that the community will decide that it is time to start the transition period and officially switch to Kubernetes.
It should be noted that IBM today announced its own preview of Eirini in its Cloud Foundry Enterprise environment and that the latest version of SUSE's Cloud Foundry-based application platform also includes similar insights.
In addition, the Cloud Foundry Foundation, which is hosting its biannual developer conference in Philadelphia this week, also announced the certification of its first certification to system integrators, Accenture and HCL, as part of its recently launched certification program for companies working in the ecosystem Cloud Foundry. at least ten certified developers from their teams.
Source link
