Community mailing list archives

Re: Can I use Odoo to build a SaaS business apps? Can Odoo support multiple subdomains?

Ermin Trevisan
- 04/26/2016 05:24:05
> The point here is the requirement for different modules. If you put
> several databases on a single service, all databases use the same
> modules. So my answer.

Understood. As we are targeting small local vendors, we do offer
standardized and preconfigured verticals. We do not offer individual
customer-specific modules for the same functionality.
> Now from a generic stand-point, the more separate Odoo services are,
> the more secure/stable it is.
> Some very demanding instances of mines, run a single database on a
> single service on a single virtual server on the customer's dedicated
> physical server.
> On the other end of the range, like, many customers
> use many databases on many services on many virtual servers on many
> dedicated servers.
> For education, evaluation, test, replay backups, it's OK. For
> production, users are invited (but not forced) to use separate
> services if they need several databases.
> Multi-tenant, aka multi-service, consists in running several Odoo
> services on the same server. For instance, a basic virtual server from
> SISalp runs three different copies of Odoo called production, taining
> and test. Multi-tenancy is a compromise to manage internal training
> and updates, but can also be used to save resources for a large number
> of services. For example, French University Mooc about ERPs in
> november 2015 needed 7000+ simulations for 7000+ students. System was
> designed for 10000 capacity, based on 25 virtual servers running 225
> Odoo services with 32 databases each.

At the moment I run different virtual servers for production, testing
and training, but each of them multi-tenant (in my sense), means one
Odoo instance, one Postgres instance, separate databases for each customer.
> In SISalp's multi-tenant solution, every service must be isolated in
> its own system user, its own home directory and its own postgresql
> role. Critical files cannot be read from other users.

In my deployment the customer has no SSH access, (of course) no Odoo
Superuser access (database manager) and not even admin access on his own
database. The customer is not allowed to install modules and has only
"editor", but no "design" access to his own website.
The reason for these restrictions is mainly to protect the customer from
harming himself.

> If you wish to see it in action for a full virtual server running
> several services, all different and independent, you can check
> and connect with "admin"
> password "admin"
> This dashboard manages our demo center. You can try and click
> everywhere and break everything here ;-).
> If you are interested by a single service view (for example Odoo
> version 8.0 demo service), connect with "version80" password "admin"
> Clouder achieves similar functions but isolates services in Docker
> instances whose management is centralized at clouder level, while, at
> SISalp, every virtual server is an independent administration unit
> managed locally. The aim of SISalp's hosting is to be able to delegate
> administration of each virtual server to the user or his local service
> provider. I think it is the main point that differentiates the two
> approaches, more than old-school/new-school technology.

Thank you for your information and the test access. I will try it as
soon as possible.

twanda AG
Ermin Trevisan
Artherstrasse 19
CH-6318 Walchwil
T    +41 41 758 1515
M    +41 79 208 7373