You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The cloud native solutions along with containerized (dockerized) microservices are becoming more and more popular. Microservices nowadays usually run in the hybrid cloud environments inside Docker containers that can be orchestrated with Kubernetes, managed by RedHat OpenShift and so on.
We can join this flow too. This is currently just a proposition, but opera orchestrator or its parts could be available inside the Docker container. This would bring a lot of flexibility and would allow users to use opera better within their (cloud) apps, so they could use the orchestrator in the cloud every time they need. Thing that can currently be put in a Docker container are opera CLI and opera API. They can stand in separate container or could be joined in just one Docker image.
Steps
To realize this idea we could connect our opera GitHub repository with DockerHub (a new opera repository should be created there before that) and configure CI build that will build and push the opera Docker images to DockerHub every time that we create a new develop or production opera release (that's when we push on master branch or when a new git tag is created).
Current behaviour
Right now opera does not provide Docker images.
Expected results
To be able to use the opera TOSCA orchestrator from a Docker container.
The text was updated successfully, but these errors were encountered:
@cankarm to inform everyone - the first step towards this has been taken with #165 within the dev.sh bash script, where a local CI Docker container can be built for the testing of Pipfile packages installation (user can run ./dev.sh integration). We also added .dockerignore file which will ignore some unnecessary files when building Docker images.
In #135 we presented the idea of dockerizing xOpera tools. Now, we're
one step forward as we're adding Dockerfile so that every user can
build his own Docker image with opera. And for the future we'll try to
start publishing Docker images on Docker Hub.
Description
The cloud native solutions along with containerized (dockerized) microservices are becoming more and more popular. Microservices nowadays usually run in the hybrid cloud environments inside Docker containers that can be orchestrated with Kubernetes, managed by RedHat OpenShift and so on.
We can join this flow too. This is currently just a proposition, but opera orchestrator or its parts could be available inside the Docker container. This would bring a lot of flexibility and would allow users to use opera better within their (cloud) apps, so they could use the orchestrator in the cloud every time they need. Thing that can currently be put in a Docker container are opera CLI and opera API. They can stand in separate container or could be joined in just one Docker image.
Steps
To realize this idea we could connect our opera GitHub repository with DockerHub (a new opera repository should be created there before that) and configure CI build that will build and push the opera Docker images to DockerHub every time that we create a new develop or production opera release (that's when we push on master branch or when a new git tag is created).
Current behaviour
Right now opera does not provide Docker images.
Expected results
To be able to use the opera TOSCA orchestrator from a Docker container.
The text was updated successfully, but these errors were encountered: