-
Notifications
You must be signed in to change notification settings - Fork 50
Clouder self-installation and autonomous #182
Comments
Are we considering server orchestration in this scope (docker, etc)? Or is this the deploy of the master Clouder controller server, basically an Odoo instance with the right modules and configs? |
Mainly 2nd I guess, this concern the easier deploy of the master Clouder controller server, but still using docker. |
For the first step, here is what I can purpose. Please help to make it better |
I have some trouble with https://github.com/pasgou/odoo-clouder.git branch master It makes error in building and do not understand why (https://hub.docker.com/r/pasgou/odoo-clouder/builds/bvwxxywqfkzktp8xezwzmku/) |
You dont have gcc installed, install build-essential package to see if it works. |
@amon-ra Resolved 👍 |
About infrastructure deployment, did you read this : Awesome |
I think discussion about terraform is off-topic, but it catch my attention earlier. What's really interesting is the fact that terraform is full CLI, it's more comparable to Docker Swarm than Kubernetes or Openshift and thus may be easier to integrate in Clouder. Probably need a deeper look, but I'd like it to gain more momentum we don't hear of it that often yet. Also : it may be a really interesting solution to improve the libcloud support to AWS/Google Engine/Azure etc... and may add a strong added value to Clouder, comparatively to Kubernetes/Openshift. I'm really gonna keep it in mind. |
Yes, I agree it's off-topic, but it was for information. |
Terraform is a TIL for me. Looks sexy though, for sure. |
I found this in discovering |
Currently deploying a Clouder is not so easy, at least one which it itself easily accessible through proxy and backuped reliably.
To give you an idea, on our main site we have a not backuped initialisation Clouder, which deploy and backup goclouder.net, which itself deploy and backup the others websites. We need to find a way for Clouder to be easier to deploy and autonomous.
Clouder itself shall be deployed through a simple one-line command. To achieve this we should
First we need to create a docker compose which will deploy all needed containers (only postgres and odoo containers are needed), so we have an Odoo instance up and running. This docker compose call Clouder images, no need to reinvent the wheel and have redundant code.
Then, we shall make sure this compose file automatically create an Odoo base for the specified domain, and configure Clouder modules in it. At this point, we'll have a Clouder up and running with a single Docker command
Finally, we have to make sure this Clouder can be aware of himself. This means that the infrastructure it will deploy can be configure to know himself :
This last point require improvement in Clouder core.
The text was updated successfully, but these errors were encountered: