Received: by 10.58.210.198 with SMTP id mw6mr710229vec.22.1350015386212;
        Thu, 11 Oct 2012 21:16:26 -0700 (PDT)
X-BeenThere: vcap-...@cloudfoundry.org
Received: by 10.220.224.8 with SMTP id im8ls1911677vcb.4.gmail; Thu, 11 Oct
 2012 21:16:25 -0700 (PDT)
Received: by 10.52.100.229 with SMTP id fb5mr1455827vdb.103.1350015385565;
        Thu, 11 Oct 2012 21:16:25 -0700 (PDT)
Received: by 10.52.100.229 with SMTP id fb5mr1455826vdb.103.1350015385550;
        Thu, 11 Oct 2012 21:16:25 -0700 (PDT)
Return-Path: <pnoordh...@rbcon.com>
Received: from mail-vc0-f169.google.com (mail-vc0-f169.google.com [209.85.220.169])
        by mx.google.com with ESMTPS id u10si4186246vcv.77.2012.10.11.21.16.25
        (version=TLSv1/SSLv3 cipher=OTHER);
        Thu, 11 Oct 2012 21:16:25 -0700 (PDT)
Received-SPF: neutral (google.com: 209.85.220.169 is neither permitted nor denied by best guess record for domain of pnoordh...@rbcon.com) client-ip=209.85.220.169;
Authentication-Results: mx.google.com; spf=neutral (google.com: 209.85.220.169 is neither permitted nor denied by best guess record for domain of pnoordh...@rbcon.com) smtp.mail=pnoordh...@rbcon.com
Received: by mail-vc0-f169.google.com with SMTP id fl17so3520789vcb.0
        for <vcap-...@cloudfoundry.org>; Thu, 11 Oct 2012 21:16:25 -0700 (PDT)
        d=google.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding:x-gm-message-state;
        bh=HjePM3wEcFk1k7ZzCWVQYRhaLrMqPSIloisiYPI6iL0=;
        b=ZipXhNmOsnFWD0Ciwz2Z7YdqFB5YbaQLw5kjJMSsGfRU/ktTGS1eLd8eQ+6sZYgunU
         uOdU3Syd9TxSU/5WQ5urSRg5cQ6UZY8H7/BS/xwSoFCx7QNVB2jLK41QAX56ApCGCIml
         jggHt3D43I3FPO/+1e9qM5MQkA+6TmJJU91Sm9haDLRkH9NnsTReIEFUTZe7OcTkrwXJ
         py59IuN0RvAX8DyeGvL7+29PJttJaOmAq3vPvJe1jV4iPIpDf6mcFTH3KseeCYYxBTwn
         SpEn/SGh5vkx0ATGexJ9H02tJI0kGPVyElG3skHJ5bbvnmOI1KIlTd3BaEISNiw/wAUi
         B5iw==
MIME-Version: 1.0
Received: by 10.220.208.210 with SMTP id gd18mr1804876vcb.43.1350015385057;
 Thu, 11 Oct 2012 21:16:25 -0700 (PDT)
Received: by 10.58.75.231 with HTTP; Thu, 11 Oct 2012 21:16:24 -0700 (PDT)
In-Reply-To: <0f494b33-b491-4df6-8c69-e203874a5...@cloudfoundry.org>
References: <CAJH6TXgxshecocw9A4MStMic62tFgxP5AzxhrW-vkjRqa+-...@mail.gmail.com>
	<CAMHuaE64MdkiErFeYBv_Me6gMzv2DOGcTOy7iqCZCJjBy=2...@mail.gmail.com>
	<0f494b33-b491-4df6-8c69-e203874a5...@cloudfoundry.org>
Date: Thu, 11 Oct 2012 21:16:24 -0700
Message-ID: <CAMZyAZfgxPNp_p21=mTUYd88v8Gh+wFC9DoWLSrm0Amf_-E...@mail.gmail.com>
Subject: Re: [vcap-dev] Warden & DEA-ng
From: Pieter Noordhuis <pnoordh...@rbcon.com>
To: vcap-...@cloudfoundry.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQntf6DKfGYIhUeGmK1P0YMzgiyyCRkz1WMXO2Fopj2Map2rHrbYZ3fFjqs4RNWg1rnXP9xX

Hi Gandalf,

They cannot yet be considered 100% stable: we're still testing both
components. Both components need to be running on the same node. The
dea communicates with warden over a Unix domain socket. It's not just
this; there are other constraints that require them to be co-located.

I can't give you instructions on how to run them from dev_setup. The
easiest thing to do in my opinion, is to mimic how they are deployed
from the release repository (the repository we use to deploy CF with
BOSH, https://github.com/cloudfoundry/cf-release). The readme in the
warden repository also contains some setup instructions.

Cheers,
Pieter

On Wed, Oct 10, 2012 at 11:38 PM,  <gandalf.corvotempe...@gmail.com> wrote:
> Il giorno gioved=C3=AC 11 ottobre 2012 06:16:45 UTC+2, Jesse Zhang ha scr=
itto:
>>
>> yes
>>
>
> Any guide on how to install them from dev-setup?
> Both need to be installed on the DEA node, right? No other components are
> involved?