Received: by 10.66.85.71 with SMTP id f7mr4044295paz.39.1346790914623;
        Tue, 04 Sep 2012 13:35:14 -0700 (PDT)
X-BeenThere: bosh-...@cloudfoundry.org
Received: by 10.68.194.202 with SMTP id hy10ls23308964pbc.0.gmail; Tue, 04 Sep
 2012 13:35:13 -0700 (PDT)
Received: by 10.68.221.70 with SMTP id qc6mr49336992pbc.92.1346790913594;
        Tue, 04 Sep 2012 13:35:13 -0700 (PDT)
Received: by 10.68.221.70 with SMTP id qc6mr49336973pbc.92.1346790913418;
        Tue, 04 Sep 2012 13:35:13 -0700 (PDT)
Return-Path: <mengl...@rbcon.com>
Received: from mail-pz0-f41.google.com (mail-pz0-f41.google.com [209.85.210.41])
        by mx.google.com with ESMTPS id mr7si29132646pbb.11.2012.09.04.13.35.13
        (version=TLSv1/SSLv3 cipher=OTHER);
        Tue, 04 Sep 2012 13:35:13 -0700 (PDT)
Received-SPF: neutral (google.com: 209.85.210.41 is neither permitted nor denied by best guess record for domain of mengl...@rbcon.com) client-ip=209.85.210.41;
Authentication-Results: mx.google.com; spf=neutral (google.com: 209.85.210.41 is neither permitted nor denied by best guess record for domain of mengl...@rbcon.com) smtp.mail=mengl...@rbcon.com
Received: by dadi14 with SMTP id i14so4840487dad.0
        for <bosh-...@cloudfoundry.org>; Tue, 04 Sep 2012 13:35:13 -0700 (PDT)
        d=google.com; s=20120113;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type
         :x-gm-message-state;
        bh=U4EZgiiRGjWEYkAHUokUuFmJvAJIvdDpXZTXGmgTPfQ=;
        b=i8A5zCpeh8JNu1ltUMh2mW24bKXRt3cpCluapicRPzaCHJ0wa99S56ZaisjdKbO85I
         7gi9GaSQ6PJpt2hYP9nqc49nixQr0s87i2wN34xJn6dgAzR21SRz0mrgqfDUhcPbPlIb
         Ag2+N3nR/NBCtq+WcOt7ghSviNVpG3bt/ATu5hWPRCsB14akeHMjf4qJlQU3hGGiD8B0
         4dhZ/x9bTee3kNzFpt5mIas1cHEaefgfYPkquTyOVb9G/XHExZ6qawZ6bgT//UYIfhp+
         rw2/E1f2ps6/OZWS177NNKukSY6pB07Yk/MreIivK5b+pCHdTKTid32gD9qcU2VchzQq
         i6EQ==
MIME-Version: 1.0
Received: by 10.66.9.2 with SMTP id v2mr43529998paa.65.1346790913229; Tue, 04
 Sep 2012 13:35:13 -0700 (PDT)
Sender: mengl...@rbcon.com
Received: by 10.66.10.195 with HTTP; Tue, 4 Sep 2012 13:35:13 -0700 (PDT)
In-Reply-To: <631c5e3b-e0fd-4e36-9e5c-e871de609...@cloudfoundry.org>
References: <631c5e3b-e0fd-4e36-9e5c-e871de609...@cloudfoundry.org>
Date: Tue, 4 Sep 2012 17:35:13 -0300
Message-ID: <CAJ5kZZuKkccoPf80gjeJfgoQ=sW3OSd92V+rnSwazkRZ4kH...@mail.gmail.com>
Subject: Re: [bosh-dev] Create micro-bosh with 'rake stemcell2[infrastructure,manifest,tar]'
From: Martin Englund <mengl...@vmware.com>
To: bosh-...@cloudfoundry.org
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQnQyGkN1TVGmb4H7LXJ5k6Jrejpz3RuA1wd9UTiISjAdM3FGJddthzQkZoJZllPffExTi90

Hi Mike!

On Tue, Sep 4, 2012 at 4:48 PM, Mike <impresenta...@gmail.com> wrote:

> I'm working in a new CPI for BOSH, it is my understanding that the way to go
> is to use the micro bosh to install a bosh.
>
> To do so I must, and I did, create an agent that I must embed in the
> stemcells. Must I add this agent to the micro-bosh?
>
Yes, if you want to be able to use micro bosh on the new cloud you're
adding support for, you need to build a micro bosh for it.

> If so, I understand the parameters of infrastructure and manifest (MF file).
> But what is that tar path that I must add?
>
The tarball you generate with:
git clone g...@github.com:cloudfoundry/bosh-release.git
cd bosh-release
bosh create release --with-tarball
which will output a .tgz in the dev_release directory

Good luck and let me know if you run into any problems...

cheers,
/Martin
-- 
Martin Englund, Staff Engineer, Cloud Foundry, VMware Inc.
"The question is not if you are paranoid, it is if you are paranoid enough."