Hey Jeff, Can you describe the burden you're feeling from the monolithic deployment? We are actively working on splitting up *cf-release* into multiple smaller, reusable, composable *releases*, but

Openstack, cf 230 Following a manifest for 225, routing-api is part of the api_z instance. Generating the manifest for 230, routing-api is not included. Following on what worked, I added it. Api

that looks pretty good. i'd probably change the following: 8) Stop jobs on old database cluster 9) Validate CF is working and connected to new database 10) Validate old database files are not changed

Did you make sure to run "scripts/update" after cloning the cf-release repo? Can you run "find . -type d -maxdepth 2" from within the "src/loggregator" directory in cf-release and reply with what you

Thank you, Filip. Your information makes the situation clear. Now our team can go to the next step considering how to cope with the situation. Filip Hanik wrote ----- I'm not a ... noburou

Thanks, it worked! however the results (attached) does not show the precise start time of individual containers... For example the app "bend" goes directly from 16 instances to 26. I wanted to study

Yes, Keystone support was intentionally removed. There were no contributions, and the keystone repository kept changing making our continuous integration pipeline break, and there was no one

I suspect you're running into this: https://github.com/cloudfoundry-incubator/diego-design-notes/blob/master/migrating-to-diego.md#file-permission-modes What version of cf are you using? What is

Many thanks for the invitation

Thanks, I guessed this would be the recommendation. I was slightly surprised there is no function for this built in. The suggestion about adding routes In a system domain is good too although do you

Hi Hristo, Thank you so much. The script seems to be very useful to me. I will use it and report you if I get any errors. Thank you again. Best regards, Nanduni.

Hi Gwenn, Well I did not know about this 'microPCF'. I found something called MicroCloudFoundry, which I suppose is not available any more. Thank you very much for this valuable information. I will

Hi Hristo, Thank you so much. The script seems to be very useful for me. I will use it and report you if I get any errors. Thank you again. Best regards, Nanduni.

I use a script [1] for restoring my BOSH-lite after computer restart. Basically it starts the VM, adds routes and then targets bosh with specific deployment manifest so BOSH knows what to check

Hello Ramon, I think I remember having seen this message when we used an Local Traffic Manager (F5) as the entrypoint. I could not figure out the root cause, but there obviously went something wrong

Tim, Alternatively, if you don't want to have a separate system domain for whatever reason, I recommend you create a "system" org and space with the admin account and use create-route to reserve any

Hi, Do you have separate system & app domains in your manifest? E.g. properties:   domain: DOMAIN   system_domain: SYSTEM_DOMAIN   app_domains:    - APP_DOMAIN If so you would be able to push

Dr. Nic created the cloudfoundry-community github org but anyone who is a current member of the org can invite others. I've sent you an invite. Please keep in mind that org is not managed by the

Hi, Our application is started by a shell script. So we pushed our application with -c option. It works fine with dea. Application could be started successfully. But when I pushed the application

Hi I am working on cloud foundry and I could create a development bosh release of cloud foundry using the following source: git clone https://github.com/cloudfoundry/cf-release.git (added some rules