Verify CycleCloud deployment

[marrobi]

A number of recent and future workspace services, such as, CycleCloud and Cromwell require additional ports opening. These were missed of the PR.

Port 22 is required from the Resource Processor subnet to the workspace to allow files to be provisioned onto workspace VMs

Ports 111 (TCP and UDP) and 2049 (TCP and UDP) are needed within the workspace services subnet to allow NFS communication.

[BiologyGeek]

Hello @marrobi,

Is this still an open issue? To have Azure CycleCloud functional, should some ports be manually opened?

[jpROC1]

Hi, I am also facing issues with CyleCloud and am interested in this fix

[tim-allen-ck]

I believe there is a problem with there 4 lines in the porter.yaml file in the cyclecloud folder

arm_client_id: ${ bundle.credentials.azure_client_id }
arm_client_secret: ${ bundle.credentials.azure_client_secret }
arm_tenant_id: ${ bundle.credentials.azure_tenant_id }
arm_use_msi: ${ bundle.parameters.arm_use_msi }

they need removing, then try to build and publish the service.

[jpROC1]

@tim-allen-ck I have cyclecloud deployed the issue is with networking, the compute nodes can not communicate with the CycleCloud machine and I have to add firewall rules manually to allow CycleCloud to access required Azure addresses.

[tim-allen-ck]

@jpROC1 Think those Firewall rules need adding into the repo