[chef] Re: Re: Re: Re: Evaluating Chef for our company.


Chronological Thread 
  • From: Haim Ashkenazi < >
  • To:
  • Subject: [chef] Re: Re: Re: Re: Evaluating Chef for our company.
  • Date: Fri, 22 Oct 2010 05:58:07 +0200
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:mime-version:content-type:subject:date:in-reply-to:to :references:message-id:content-transfer-encoding:x-pgp-agent :x-mailer; b=oIU14DcRTFGUz1M6gyV9xf3lclJGhvyqLZQkTwPfy9aVwL0dHZowXzH6ra+1C6hA8l Ff8yi20mzZeGxH9TmchRerJaM3Miy9WEsjCgiTh+E3t8eBxajmoLK4eJeyFQ4ECJiu9v KFWUvavduOW9m09153CsKB3uiYtm/sgFv6EDo=

Hi

On Oct 22, 2010, at 5:16 AM, AJ Christensen wrote:

Yo,

On 21 October 2010 03:52, Haim Ashkenazi < "> > wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi

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.

I've seen multiple chef deployments fronted by reverse proxy through to multiple instances of the Chef server stack.

It's just a HTTP app :)
Thanks. 

My problem is not the frontend :) I don't need one front end for all customers, I'm not trying to compete with Opscode :)
I want to persuade some customers to move to chef without the need of taking care of their own server. For large customers it makes sense to use a server of their own, but it's a lot of overhead to use a dedicated server for a company with 6 production servers.

Bye

 

Thanks

Haim

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:
>
> http://lists.opscode.com/sympa/arc/chef/2010-10/msg00084.html
>
> The rest of it should not be a problem.
>
> Greetings.
>
> Jacobo García López de Araujo
> blog: http://robotplaysguitar.com
> http://workingwithrails.com/person/13395-jacobo-garc-a
>
>
>
>
> On Thu, Oct 21, 2010 at 11:21 AM,  < "> > wrote:
>> Hi
>>
>> 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
>>
>> Haim
>>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)

iEYEARECAAYFAkzAG2kACgkQhwMtGgRKzT3aygCeJoYRetMivvuarW5Nkh0iTYtL
DMEAni08agk6VwdFPbIDFk6VKnCEiltv
=Azvw
-----END PGP SIGNATURE-----


Attachment: PGP.sig
Description: This is a digitally signed message part




Archive powered by MHonArc 2.6.16.

§