Warden & DEA-ng

146 views
Skip to first unread message

Gandalf Corvotempesta

unread,
Oct 10, 2012, 3:56:19 PM10/10/12
to vcap...@cloudfoundry.org
Are warden and dea-ng considered stable? I've seen that latest commit
to dea-ng is 1 month old.

Jesse Zhang

unread,
Oct 11, 2012, 12:16:23 AM10/11/12
to vcap...@cloudfoundry.org
yes

gandalf.co...@gmail.com

unread,
Oct 11, 2012, 2:38:37 AM10/11/12
to vcap...@cloudfoundry.org
Il giorno giovedì 11 ottobre 2012 06:16:45 UTC+2, Jesse Zhang ha scritto:
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? 

Pieter Noordhuis

unread,
Oct 12, 2012, 12:16:24 AM10/12/12
to vcap...@cloudfoundry.org
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

gandalf.co...@gmail.com

unread,
Oct 13, 2012, 8:12:52 AM10/13/12
to vcap...@cloudfoundry.org
Il giorno venerdì 12 ottobre 2012 06:16:26 UTC+2, Pieter Noordhuis ha scritto:
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.

Ok, this is not an issue for us.
If I understood properly, with dea_ng + warden, dea_ng will receive the request
from cloud controller, then it will route the request to warden.
This is ok.
 
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.

Is BOSH ready to deploy Cloudfoundry with dea_ng/warden?
Do you think is better to use BOSH or Chef? 

Any ETA about a 'stable' release of dea_ng/warden and their includion in dev_setup?
Reply all
Reply to author
Forward
0 new messages