How to move from a (fresh) stock cf-release to a cf-release with diego globally enabled by default?

[djvdorp]

We have a fresh Cloud Foundry v238 (testing) installation, for which we have just changed cc.default_to_diego_backend to true. We were hoping this would be all steps needed to move our (fresh) stock cf-release to a cf-release with diego globally enabled by default, but there might be a bit more work involved.

For newcomers to the diego playing field, the steps to take might be a bit overwhelming and unclear, so we are wondering if there is an easy (step-by-step) guide available for this, to move from a stock cf-release to a cf-release with diego globally enabled by default?

We stumbled upon the diego-design-notes/migrating-to-diego.md documentation, but the starting point there seems to be that you already have a cf-release with diego deployed. This repository itself also contains an excellent guide to deploying diego to bosh lite and deploying diego in aws but it seems very complicated and not as clear on how to do this for an already deployed (fresh) stock cf-release on AWS.

We found related repositories with bosh-releases that we think we need to install, but some steps or guidance towards this would be greatly appreciated:

• https://github.com/cloudfoundry/diego-release
• https://github.com/cloudfoundry/cflinuxfs2-rootfs-release

[cf-gitbot]

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

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

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

[jfmyers9]

Hi @djvdorp,

We agree that there is missing documentation for that use case, and have added the following story to address this.

In order to generate a Diego deployment manifest you need to at least specify 3 values when generating a manifest.

• You will need to generate a host key for the ssh-proxy. This documentation covers how to do so.
• The CF manifest from your fresh install should be fine here. You do need to add the following properties specified in the first code example of this documentation in order to get cf ssh to work. You will need to add the ssh-proxy-host-key-fingerprint generated above.
• For the iaas-settings.yml, this template is a good example. You will need to replace the various spiff merges with corresponding identifiers from the aws resources that you will need to create. Specifically you will need to create 3 subnets for Diego's 3 availability zones, and 1 ELB for the ssh-proxy.
• For the property_overrides.yml, this template is a good example. Once again you will need to supply values from generating the ssh-proxy host-key. The certificates that you need to generate will be covered in [this documentation].

Hopefully those examples help. Is there anything that we can specifically help you with as you transition your CF deployment to be backed by Diego?

Best,

@jfmyers9 && @luan, CF Diego Team

[djvdorp]

Hi @jfmyers9 && @luan,

Sorry for the late reply -- Thanks a lot for this!
I am going to try this out tomorrow if all goes well.
I just checked the story you referred to and noticed this related commit, looks good!

I will post back here as soon as I get any errors, or even better, working results!

[djvdorp]

Hi @jfmyers9 && @luan,

I am currently in the process of trying out the steps above and/or the docs I found here, although it seems @ematpl is still working on them atm.

However, I noticed that the docs seem to use the minimal-aws.yml manifest stub as an entry point, while my particular setup on AWS has been done with the cf-stub.yml manifest stub from the CF Docs for AWS. The cf-release infrastructure setup also sends users over to the CF Docs and not towards the minimal-aws.yml file.

Is anybody here aware of the relationship between these two manifest stubs, since they don't seem completely in sync, but I am not sure which one would be 'better' or 'recommended' (I used the latter one a lot already).

EDIT: They seem unrelated. From the AWS deploying docs (about cf-stub.yml):

The following steps document an example procedure for deploying Cloud Foundry on AWS. The process includes several steps that may be expensive and time-consuming, such as provisioning AWS Relational Database Service (RDS) instances. For a simpler deployment, refer to the Minimal AWS instructions.

[djvdorp]

Hi @jfmyers9 && @luan,

The last link to the documentation you posted seems broken:

For the property_overrides.yml, this template is a good example. Once again you will need to supply values from generating the ssh-proxy host-key. The certificates that you need to generate will be covered in [this documentation].

Any chance you could point the [this documentation] link to a destination as well? I assume (for now) that this is the destination you meant: https://github.com/cloudfoundry/diego-release#generating-tls-certificates

Again, thanks for everything so far, I am following the steps as we speak.

[jvshahid]

I think @jfmyers9 was referring to this document.

Closing this issue given there is a new document here that addresses deploying diego alongside cf. Please don't hesitate to let us know if there is anything missing in the document.