Bernd Krannich

SAP Technology & Innovation

SAP SE

Dietmar-Hopp-Allee 16, 69190 Walldorf, Germany

E bernd.krannich@...

Pflichtangaben/Mandatory Disclosure Statement: www.sap.com/impressum

Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank.

This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.

From: cf-dev@... <cf-dev@...> on behalf of Andrew Wittrock <awittrock@...>
Date: Tuesday, 5. October 2021 at 02:17
To: cf-dev@... <cf-dev@...>
Subject: [cf-dev] SIG Meeting: Cloud Foundry for Kubernetes updates

Hello everyone! I’m sharing some news regarding the SIG Meeting: Cloud Foundry for Kubernetes. First of all, a huge thanks to Bernd Krannich, who has been running the meetings. He expressed interest in having someone carry the torch forward, and I have volunteered to do so. Starting tomorrow, October 5, 2021, I’ll be leading the meetings in that time slot.

Additionally, we have some changes in format. I’d like to expand the meeting beyond a focus on the cf-for-k8s project to include all CF on Kubernetes projects. It would be great to have the people working in this space come together to ensure we can build useful products for each other. To that end, we are drafting a proposal for a new Working Group to oversee the development of the new cf-k8s API and controllers as the latest approach for a CF experience deeply integrated with Kubernetes. We envision that that group could even take over this meeting’s time slot for its periodic public discussion forum, should it be approved.

Please join us at one of the biweekly meetings! The floor is pretty much open, but we’ll be discussing the current nascent cf-k8s-api and cf-k8s-controllers projects as we build out a more Kubernetes-native CF experience.

- Andrew

From: cf-dev@... <cf-dev@...> on behalf of Chris L <chris@...>
Date: Friday, September 3, 2021 at 8:50 AM
To: cf-dev@... <cf-dev@...>
Subject: Re: [cf-dev] Cloudfoundry deployment error on vanilla Openstack Wallaby cloud #cf

I was reading up on the neutron LBaaS deprecation and wondering if that is an issue here.  I thought the policy was to support the latest 3 openstack versions….  Could that be the issue? Cloudfoundry does not support Octavia and thus wouldent support anything after Queens?  I guess I could try deploying as Kubernetes…

https://github.com/cloudfoundry-attic/bosh-openstack-environment-templates/cf-deploymnet-tf/cf.tf

https://github.com/cloudfoundry/cf-deployment/cf-deployment.yml

runuser -l stack -c  "cd /opt/stack; \
                  bbl print-env -s /opt/stack > /tmp/bbl_env.sh; \
                  chmod 700 /tmp/bbl_env.sh; \
                  source /tmp/bbl_env.sh; \
                  bosh -d cf deploy -o /tmp/cf-deployment/operations/use-external-blobstore.yml \
                  -o /tmp/cf-deployment/operations/use-swift-blobstore.yml \
                  -o /tmp/cf-deployment/operations/openstack.yml \
                  -o /tmp/cf-deployment/operations/scale-to-one-az.yml \
                  -o /tmp/cf-deployment/operations/use-compiled-releases.yml \
                  --vars-store /tmp/vars/deployment-vars.yml \
                  /tmp/cf-deployment/cf-deployment.yml \
                  -v system_domain=$DOMAIN_NAME \
                  -v auth_url=https://$EXTERNAL_VIP_DNS:5000/v3 \
                  -v openstack_project=cloudfoundry \
                  -v openstack_domain=default \
                  -v openstack_username=$OPENSTACK_CLOUDFOUNDRY_USERNAME \
                  -v openstack_password=$OPENSTACK_CLOUDFOUNDRY_PWD \
                  -v openstack_temp_url_key=$SWIFT_KEY \
                  -v app_package_directory_key=app_package_directory \
                  -v buildpack_directory_key=buildpack_directory \
                  -v droplet_directory_key=droplet_directory \
                  -v resource_directory_key=resource_directory \
                  -n"

The information transmitted is intended for the person or entity to which it is addressed and may contain confidential, privileged or copyrighted material. If you receive this in error, please contact the sender and delete the material from any computer. Any views or opinions expressed are those of the author and do not necessarily represent those of Fidelity International. All e-mails may be monitored. FIL Investments International (Reg. No.1448245), FIL Investment Services (UK) Limited (Reg. No. 2016555), FIL Pensions Management (Reg. No. 2015142), Financial Administration Services Limited (Reg. No. 1629709) and FIL Wealth Management Limited (Registered. No. 06121251) are authorised and regulated in the UK by the Financial Conduct Authority. FIL Life Insurance Limited (Reg No. 3406905) is authorised in the UK by the Prudential Regulation Authority and regulated in the UK by the Financial Conduct Authority and the Prudential Regulation Authority. Registered offices at Beech Gate, Millfield Lane, Lower Kingswood, Tadworth, Surrey KT20 6RP.

From: cf-dev@... <cf-dev@...> on behalf of Conner UK, Jim via lists.cloudfoundry.org <jim.conner=fil.com@...>
Date: Friday, September 3, 2021 at 3:01 AM
To: cf-dev@... <cf-dev@...>
Subject: Re: [cf-dev] Cloudfoundry deployment error on vanilla Openstack Wallaby cloud #cf

I don’t think the Octavia endpoints are the same as the old Neutron lbaas ones were.

:path          => "/v2.0/lbaas/pools"

''OpenStack API NotFound Expected(200) <=> Actual(404 Not Found)

The API docs for Octavia seem to indicate that the path would be /v2/lbaas (rather than /v2.0)

I’ve no idea how to fix the issue, but I think that explains why the error is happening.

Cheers,

Jim

All,

I am receiving this error while attempting to deploy Cloudfoundry on a vanilla Openstack Wallaby cloud:

https://github.com/cloudfoundry-attic/bosh-openstack-environment-templates/cf-deploymnet-tf/cf.tf

https://github.com/cloudfoundry/cf-deployment/cf-deployment.yml

runuser -l stack -c  "cd /opt/stack; \
                  bbl print-env -s /opt/stack > /tmp/bbl_env.sh; \
                  chmod 700 /tmp/bbl_env.sh; \
                  source /tmp/bbl_env.sh; \
                  bosh -d cf deploy -o /tmp/cf-deployment/operations/use-external-blobstore.yml \
                  -o /tmp/cf-deployment/operations/use-swift-blobstore.yml \
                  -o /tmp/cf-deployment/operations/openstack.yml \
                  -o /tmp/cf-deployment/operations/scale-to-one-az.yml \
                  -o /tmp/cf-deployment/operations/use-compiled-releases.yml \
                  --vars-store /tmp/vars/deployment-vars.yml \
                  /tmp/cf-deployment/cf-deployment.yml \
                  -v system_domain=$DOMAIN_NAME \
                  -v auth_url=https://$EXTERNAL_VIP_DNS:5000/v3 \
                  -v openstack_project=cloudfoundry \
                  -v openstack_domain=default \
                  -v openstack_username=$OPENSTACK_CLOUDFOUNDRY_USERNAME \
                  -v openstack_password=$OPENSTACK_CLOUDFOUNDRY_PWD \
                  -v openstack_temp_url_key=$SWIFT_KEY \
                  -v app_package_directory_key=app_package_directory \
                  -v buildpack_directory_key=buildpack_directory \
                  -v droplet_directory_key=droplet_directory \
                  -v resource_directory_key=resource_directory \
                  -n"

This email has been scanned by Inbound Shield™.

From: <cf-dev@...> on behalf of Chris L <chris@...>
Reply to: "cf-dev@..." <cf-dev@...>
Date: Thursday, 2 September 2021 at 14:40
To: "cf-dev@..." <cf-dev@...>
Subject: [cf-dev] Cloudfoundry deployment error on vanilla Openstack Wallaby cloud #cf

[2021-09-02T01:29:55.856730 #882] [task:40] DEBUG -- DirectorJobRunner: (0.001265s) (conn: 47027669444740) INSERT INTO "events" ("parent_id", "timestamp", "user", "action", "object_type", "object_name", "error", "task", "deployment", "instance", "context_json") VALUES (342, '2021-09-02 01:29:55.852077+0000', 'admin', 'update', 'deployment', 'cf', 'CPI error ''Bosh::Clouds::CloudError'' with message ''OpenStack API NotFound Expected(200) <=> Actual(404 Not Found)

excon.error.response

  :body          => "{\"NeutronError\": {\"type\": \"HTTPNotFound\", \"message\": \"The resource could not be found.\", \"detail\": \"\"}}"

  :cookies       => [

  ]

  :headers       => {

    "content-length"            => "103"

    "content-type"              => "application/json"

    "date"                      => "Thu, 02 Sep 2021 01:29:32 GMT"

    "strict-transport-security" => "max-age=31536000;"

    "x-openstack-request-id"    => "req-fbfa7aa1-1f13-46c6-8385-5f0fde847b08"

  }

  :host          => "openstack-external.lyonsgroup.family"

  :local_address => "10.0.1.6"

  :local_port    => 45952

  :path          => "/v2.0/lbaas/pools"

  :port          => 9696

  :reason_phrase => "Not Found"

  :remote_ip     => "174.54.141.197"

  :status        => 404

  :status_line   => "HTTP/1.1 404 Not Found\r\n"

.

Check task debug log for details.'' in ''create_vm'' CPI method (CPI request ID: ''cpi-184472'')', '40', 'cf', NULL, '{"before":{"releases":["loggregator-agent/6.3.3","metrics-discovery/3.0.6","bpm/1.1.13","bosh-dns-aliases/0.0.4","bosh-dns/1.29.0","binary-buildpack/1.0.39","capi/1.112.0","cf-networking/2.38.0","cf-smoke-tests/41.0.2","cflinuxfs3/0.251.0","credhub/2.9.0","diego/2.51.0","dotnet-core-buildpack/2.3.32","garden-runc/1.19.29","go-buildpack/1.9.34","java-buildpack/4.41","loggregator/106.6.0","nats/40","nginx-buildpack/1.1.30","r-buildpack/1.1.20","nodejs-buildpack/1.7.57","php-buildpack/4.4.44","pxc/0.37.0","python-buildpack/1.7.43","routing/0.221.0","ruby-buildpack/1.8.43","silk/2.38.0","staticfile-buildpack/1.5.24","statsd-injector/1.11.16","uaa/75.6.0","log-cache/2.11.1","cf-cli/1.32.0"],"stemcells":["bosh-openstack-kvm-ubuntu-xenial-go_agent-raw/621.125"]},"after":{"releases":["loggregator-agent/6.3.3","metrics-discovery/3.0.6","bpm/1.1.13","bosh-dns-aliases/0.0.4","bosh-dns/1.29.0","binary-buildpack/1.0.39","capi/1.112.0","cf-networking/2.38.0","cf-smoke-tests/41.0.2","cflinuxfs3/0.251.0","credhub/2.9.0","diego/2.51.0","dotnet-core-buildpack/2.3.32","garden-runc/1.19.29","go-buildpack/1.9.34","java-buildpack/4.41","loggregator/106.6.0","nats/40","nginx-buildpack/1.1.30","r-buildpack/1.1.20","nodejs-buildpack/1.7.57","php-buildpack/4.4.44","pxc/0.37.0","python-buildpack/1.7.43","routing/0.221.0","ruby-buildpack/1.8.43","silk/2.38.0","staticfile-buildpack/1.5.24","statsd-injector/1.11.16","uaa/75.6.0","log-cache/2.11.1","cf-cli/1.32.0"],"stemcells":["bosh-openstack-kvm-ubuntu-xenial-go_agent-raw/621.125"]}}') RETURNING *

I do have the Octavia project installed and a loadbalancer is created and running.  I use the terraform script here to prepare the Openstack cloud for cloudfoundry:

https://github.com/cloudfoundry-attic/bosh-openstack-environment-templates/cf-deploymnet-tf/cf.tf

This creates a loadbalancer, security groups, networks, etc.

It completes successfully and I do see the cf-lb loadbalancer created, running, in active state, and a whole lot of ports and pools that exist under it.  I then execute the BOSH deploy of cloudfoundry using this repo:

https://github.com/cloudfoundry/cf-deployment/cf-deployment.yml

My deployment line looks like this:

runuser -l stack -c  "cd /opt/stack; \
                  bbl print-env -s /opt/stack > /tmp/bbl_env.sh; \
                  chmod 700 /tmp/bbl_env.sh; \
                  source /tmp/bbl_env.sh; \
                  bosh -d cf deploy -o /tmp/cf-deployment/operations/use-external-blobstore.yml \
                  -o /tmp/cf-deployment/operations/use-swift-blobstore.yml \
                  -o /tmp/cf-deployment/operations/openstack.yml \
                  -o /tmp/cf-deployment/operations/scale-to-one-az.yml \
                  -o /tmp/cf-deployment/operations/use-compiled-releases.yml \
                  --vars-store /tmp/vars/deployment-vars.yml \
                  /tmp/cf-deployment/cf-deployment.yml \
                  -v system_domain=$DOMAIN_NAME \
                  -v auth_url=https://$EXTERNAL_VIP_DNS:5000/v3 \
                  -v openstack_project=cloudfoundry \
                  -v openstack_domain=default \
                  -v openstack_username=$OPENSTACK_CLOUDFOUNDRY_USERNAME \
                  -v openstack_password=$OPENSTACK_CLOUDFOUNDRY_PWD \
                  -v openstack_temp_url_key=$SWIFT_KEY \
                  -v app_package_directory_key=app_package_directory \
                  -v buildpack_directory_key=buildpack_directory \
                  -v droplet_directory_key=droplet_directory \
                  -v resource_directory_key=resource_directory \
                  -n"

Is there anything anyone could see as to what would cause the error at the beginning of the post?  I can get any other logs that would help, I could grant access to the env, anything that would give anyone an idea.