while deploying windows stack using bosh

[vijaay]

C:\Users\wwtadmin\Desktop\tam>generate.exe -outputDir=.\ -boshUrl=https://hm-use r:hU6eI4J7gf04bWDFVyF4A@10.0.0.9:25555 -machineIp=10.0.48.4 BOSH Director does not have exactly one deployment containing a cf and diego rel ease.

please help me to resolve the issue

[cf-gitbot]

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

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

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

[vijaay]

zurecfbosh@ocfdev-azurebosh:~$ bosh releases Acting as user 'admin' on 'bosh'

+-------------------+-----------+-------------+ | Name | Versions | Commit Hash | +-------------------+-----------+-------------+ | cf | 231* | f67ebb73+ | | | 239* | e53f998d+ | | cflinuxfs2-rootfs | 1.18.0* | 292eac2e+ | | | 1.25.0 | 62a32ebf+ | | | 1.26.0 | ddc7ebac+ | | consul | 80 | 907dca9f+ | | diego | 0.1460.0* | 02b2bb8a | | | 0.1480.0* | 89496125 | | etcd | 38* | af52789b+ | | | 60* | bf327393+ | | | 65 | c0627ad5+ | | | 66 | b074858e+ | | garden-linux | 0.334.0* | 88f7ec39 | | | 0.339.0* | 545d890b | | | 0.341.0 | 6edce831 | | | 0.342.0 | b03a9abc | +-------------------+-----------+-------------+

[aminjam]

@vijaay What's the output of bosh deployments?

[aminjam]

Closing this issue due to inactivity. Let us know if you still encounter a problem.

[malichishti]

Hi, I'm having the same issue. Please find the info asked to the OP below: Regards, Ali

[sunjayBhatia]

@malichishti is it possible for you to move to using BOSH to deploy your windows cells? the Azure stemcell is publicly available on bosh.io: http://bosh.io/stemcells/bosh-azure-hyperv-windows2012R2-go_agent

(the diego windows MSI has been deprecated in favor of BOSH windows deployed with garden-windows-bosh-release)

[malichishti]

Do you have instructions for that? I have been following instructions below:

https://github.com/cloudfoundry-incubator/bosh-azure-cpi-release/blob/master/docs/get-started/via-arm-templates/deploy-bosh-via-arm-templates.md https://github.com/cloudfoundry-incubator/bosh-azure-cpi-release/blob/master/docs/get-started/via-arm-templates/deploy-cloudfoundry-via-arm-templates.md https://github.com/cloudfoundry-incubator/bosh-azure-cpi-release/tree/master/docs/advanced/push-your-first-net-application-to-cloud-foundry-on-azure

[sunjayBhatia]

@malichishti The methods described in that document are outdated (particularly the third link), you are now able to add a windows cell and deploy it with BOSH, not the MSI installer as that document describes as the MSI has been deprecated.

Going forward, Cloud Foundry is moving towards using cf-deployment as the preferred deployment strategy which offers an easy way to generate manifests, rotate credentials, etc. cf-deployment offers an operations file (like an optional configuration file) that you can use to add a Windows cell to your deployment. If you are unable to use cf-deployment for some reason, you can follow the template in the linked opsfile and add a Windows cell to your deployment with the proper configuration.

[malichishti]

@sunjayBhatia Thank you, i have added the windows cell, what should i do next in order to host an ASP.Net App?

[sunjayBhatia]

@malichishti that looks like you just uploaded the stemcell and have not deployed a VM from it yet (there is no * next to the version signifying that it is in use)

You need to create a deployment manifest to deploy the required BOSH jobs onto a cell:

• garden-windows -> garden-windows BOSH release
• rep_windows -> diego release
• consul_agent_windows -> consul release
• metron_agent_windows -> loggregator release