-----BEGIN PGP SIGNED MESSAGE-----
Thanks for the quick response. This is not good news though
How much of a hassle it is to use the same resources (couchdb, solr, etc) and only use multiple instances of chef server on the same physical server (on different ports)? Provided of course that I will have to write the web-ui myself? I’m afraid running full (virtual) machine as a server for each customer might be too much overhead.
On Oct 21, 2010, at 12:27 PM, Jacobo García wrote:
Managing many companies with one server is difficult, the exception is
to use opscode platform which already has support for different
companies, see this recent thread for a more in depth explanation:
The rest of it should not be a problem.
Jacobo García López de Araujo
On Thu, Oct 21, 2010 at 11:21 AM, email@example.com wrote:
I have an operation consulting company, and I want to start using Chef to
manage all our customer’s production servers. I’m trying to figure out if this
is the right project for my use case. Can someone please tell me which of the
requirements below is included in Chef and which are not:
Manage many companies on one server with restricting ACL, No company should
even know of the existence of the other companies. On the other hand, each
company should be able to manage it’s resources.
Have a web-ui to manage the setup above.
Each customer should be able to get his chef repository (all scripts,
cookbooks, etc) from us and choose another company (like Opscode) as their
server without much trouble.
From what I understood from the little I’ve read, I can do most of it, but I
want to be sure before I dig too deep.
Thanks in advance
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
-----END PGP SIGNATURE-----