How do I know my cloud foundry has enabled Diego ?

[mailtokun]

Which command or config file can finger out this ?

Thanks!!!

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/134053621

The labels on this github issue will be updated when the story is started.

[MissingRoberto]

+1

This would help tremendously during the migration process

But probably it's something that would make more sense inside capi-release.

[jenspinney]

Hi @mailtokun,

It depends what you mean by 'enabled'. If you want to know whether Diego is the default backend for all apps deployed to CF, then you can see or set this value via the cc.default_to_diego_backend property in the bosh deployment manifest for Cloud Foundry. When this property is true, all apps will use Diego unless otherwise specified. If this property is set to true, and Diego has not been deployed to your bosh environment, the default push behavior for any apps will fail.

It is also possible to use Diego in an environment where Diego is not the default backend. If Diego is available, it will show up as a separate deployment in your bosh environment. When you run bosh deployments, you should see a deployment specific to Diego in the list. For example, our bosh lite environment has the following deployments listed:

Acting as user 'admin' on 'Bosh Lite Director'

+-----------------+--------------------------+----------------------------------------------------+--------------+
| Name            | Release(s)               | Stemcell(s)                                        | Cloud Config |
+-----------------+--------------------------+----------------------------------------------------+--------------+
| cf-warden       | cf/245+dev.2             | bosh-warden-boshlite-ubuntu-trusty-go_agent/3262.2 | none         |
+-----------------+--------------------------+----------------------------------------------------+--------------+
| cf-warden-diego | cf/245+dev.2             | bosh-warden-boshlite-ubuntu-trusty-go_agent/3262.2 | none         |
|                 | cflinuxfs2-rootfs/1.38.0 |                                                    |              |
|                 | diego/0.1487.0+dev.6     |                                                    |              |
|                 | etcd/78                  |                                                    |              |
|                 | garden-runc/1.0.0        |                                                    |              |
+-----------------+--------------------------+----------------------------------------------------+--------------+

Deployments total: 2

To verify that Diego is up and running successful and you have the cc.default_to_diego_backend property set to true, just try to push an app to verify that the system is working.

If that property is set to false, you'll need to enable Diego on that specific app using the Diego-Enabler plugin for the cf cli. For example:

cf push my-app --no-start
cf enable-diego my-app
cf start my-app

One last thing you can do to verify that an app was actually staged and run using Diego is to look at the logs. If you push an app using the old DEAs, you'll see log lines containing the tag "[DEA]", but if the app is running on Diego, you'll see log lines with "[CELL]" instead.

Hope that answers your question.

• @jenspinney && @mailtokun

[mailtokun]

@jenspinney
Thanks . That's very helpful for me.