Skip to content

Remove remaining mentions of fog. #224

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
stephanme wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Remove remaining mentions of fog. #224

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions cc-blobstore.html.md.erb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,8 +39,8 @@ binary large object (blob) files:
</tr></tbody>
</table>

<%= vars.app_runtime_abbr %> blobstores use the [Fog](http://fog.io/) Ruby gem to store blobs in
services like Amazon S3, WebDAV, or the NFS filesystem. The file system location of an internal blobstore is `/var/vcap/store/shared`.
<%= vars.app_runtime_abbr %> blobstores use the [storage-cli](https://github.com/cloudfoundry/storage-cli) tool to store blobs in
services like Amazon S3, Google Cloud Storage, Azure Blobstorage, Alibaba Cloud Object Storage Service, or WebDAV.

A single blobstore typically stores all five types of blobs, but you can configure the Cloud Controller to use separate blobstores for each type.
This topic references staging and treats all blobstores as generic object stores.
Expand Down Expand Up @@ -165,7 +165,7 @@ Parallel BOSH deployments of Diego Cells can also generate significant read load

## <a id='blobstore-timeouts'></a> Blobstore interaction timeouts

Cloud Controller inherits default blobstore operation timeouts from Excon.
Excon defaults to 60 second read, write, and connect timeouts.
Cloud Controller inherits default blobstore operation timeouts from the IaaS provider SDKs used by [storage-cli](https://github.com/cloudfoundry/storage-cli).
Typical defaults are 60 second read, write, and connect timeouts.

For more information, see the [excon](https://github.com/excon/excon) repository on GitHub.
For more information, see the IaaS specific README.md files in the [storage-cli](https://github.com/cloudfoundry/storage-cli) repository on GitHub.