Received: by 10.66.84.38 with SMTP id v6mr4091799pay.7.1346795489876; Tue, 04 Sep 2012 14:51:29 -0700 (PDT) X-BeenThere: bosh-...@cloudfoundry.org Received: by 10.68.222.39 with SMTP id qj7ls99418pbc.2.gmail; Tue, 04 Sep 2012 14:51:29 -0700 (PDT) Received: by 10.68.132.3 with SMTP id oq3mr49709558pbb.58.1346795489045; Tue, 04 Sep 2012 14:51:29 -0700 (PDT) Received: by 10.68.132.3 with SMTP id oq3mr49709557pbb.58.1346795489034; Tue, 04 Sep 2012 14:51:29 -0700 (PDT) Return-Path: Received: from mail-pb0-f41.google.com (mail-pb0-f41.google.com [209.85.160.41]) by mx.google.com with ESMTPS id vn9si29303753pbc.287.2012.09.04.14.51.28 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 04 Sep 2012 14:51:28 -0700 (PDT) Received-SPF: neutral (google.com: 209.85.160.41 is neither permitted nor denied by best guess record for domain of mengl...@rbcon.com) client-ip=209.85.160.41; Authentication-Results: mx.google.com; spf=neutral (google.com: 209.85.160.41 is neither permitted nor denied by best guess record for domain of mengl...@rbcon.com) smtp.mail=mengl...@rbcon.com Received: by pbbro12 with SMTP id ro12so10882757pbb.0 for ; Tue, 04 Sep 2012 14:51:28 -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=R+fNltOXfOev9nYJd+X/Exs1Zt6QkUJsRj1LP2cX/M4=; b=NcKMrHwO71pBofRg3OWpggJsGjOA3N/zTq3g5fNxPoVLdtY5RVfbdlHuDLZgsNTeVq Mepf3ReMnGpMWb3//ZdIWSJP8dwKlAVjsV0MDfSj37QM35Juhm56zSEQ/Y0aE0zqnySu JbCgdtQRhsYpvVF2Lo5aJhNhawjblzvTFLzfkyep9CLZ+p8IkEoiu/kVALBSESqGsPrx 623x5lNmH/QXlFaJBq7UWdTaqceNF2B+7bRCzUCjfZV/jurq29aVxTNxeFZtcMCoxV8c xCHi2A0Yt2BW5ghgnoYISIl41rA/2J8KN9KV/aiVmeIyWSHMl+pio0p0JDq8F/3Mcw9G OzKw== MIME-Version: 1.0 Received: by 10.66.75.105 with SMTP id b9mr18385533paw.58.1346795488679; Tue, 04 Sep 2012 14:51:28 -0700 (PDT) Sender: mengl...@rbcon.com Received: by 10.66.10.195 with HTTP; Tue, 4 Sep 2012 14:51:28 -0700 (PDT) In-Reply-To: <4a9ac244-d912-43fc-ba9b-243425816...@cloudfoundry.org> References: <631c5e3b-e0fd-4e36-9e5c-e871de609...@cloudfoundry.org> <39912979-4b36-4294-b3ea-98eeadf67...@cloudfoundry.org> <4a9ac244-d912-43fc-ba9b-243425816...@cloudfoundry.org> Date: Tue, 4 Sep 2012 18:51:28 -0300 Message-ID: Subject: Re: [bosh-dev] Create micro-bosh with 'rake stemcell2[infrastructure,manifest,tar]' From: Martin Englund To: bosh-...@cloudfoundry.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkrdBqlP2wdjx/Arlpw0NGfDsqWccOgy6TBmkDnmXu+IkVCMNtyMOAraEzh/Fy/MDoiqc5Y On Tue, Sep 4, 2012 at 6:40 PM, Mike wrote: > It created the stemcell but added the aws_registry, should I add a job that > add my registry? > Yes, you need to create a package and a job for your registry, and you should also take a look at the jobs/micro_aws directory, as you'll need to create a similar one for your cloud. This is the job that will get setup for the micro bosh stemcell you create (based on the cpi you pass the build command). 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."