Hi everyone, I have some queries regarding persistent storage of application logs and cf component logs . As per my understanding -->For application logs: we can send the application logs to doppler w

Run add-route script under bin folder of bosh-lite directory.

Hello, you can add the timeout in your manifest itself. https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html#timeout Thanks Ronak -- View this message in context: http://cf-dev.70369.x6.na

same query for the component logs -- View this message in context: http://cf-dev.70369.x6.nabble.com/cf-dev-More-reliable-way-to-collect-user-application-logs-tp1214p1273.html Sent from the CF Dev mai

Hello All, I have a resource pool , let say small_z1 - name: small_z1 network: cf1 stemcell: stemcell-xyz cloud_properties: instance_type: m1.small availability_zone: zone1 and a Job , router having t

Hi Dies, App auto-scaling is much needed feature for CF OSS , lot of users want to use this functionality . Once on the incubator, roadmap can be discussed. Hope to to see it soon on cf incubator . Re

Can possibly package anything but that way application will run inside a vm rather than on platform.

Hi kayode, You can take a look at cf plugin repo , there is already a plugin for no downtime deployment which is designed based on what simon described . Ronak Banka Rakuten, Inc.

Checkout auto pilot plugin here https://plugins.cloudfoundry.org/ui/

you can do bosh cck , you can select options from there when it will check the status for that router machine, either restart the vm or recreate vm using last known spec. Refer: https://bosh.io/docs/s

On router vm , after getting to root user try "sv stop agent && sv start agent" wrote:

Check "df -h" on your local system from where you are uploading the release.

Gwenn, If I'm not wrong Application sec rules are for restricting outbound traffic from application side , no? Ronak

Check this out https://github.com/cloudfoundry-incubator/diego-release/blob/develop/README.md

Hello , I am running diego env on my workstation with following releases and everything works fine. +--------------+-----------+-------------+ | Name | Versions | Commit Hash | +--------------+-------

I checked at very starting with cf docker-push my-app cloudfoundry/lattice-app wrote:

Hello , As of now with the "upstream buildpack" there is a restriction for stack name with which one can push a application (cflinuxfs2) Use case is to place applications on different sets of DEA's ,

Hi Parthiban, In your manifest , there is a global property block nfs_server: address: 192.168.33.53 allow_from_entries: - null - null share: null allow from entries are provided for cc individual pro

Subnet ranges on which your other components are provisioned. allow_from_entries: - 192.168.33.0/24 wrote:

Hi Rexxar, We are thinking to do this using the stack property for application placement on certain set of DEA's with that stack . http://cf-dev.70369.x6.nabble.com/cf-dev-Using-stack-names-as-placeme