You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by Jeremy Daggett <no...@github.com> on 2014/03/31 23:34:31 UTC
[jclouds-site] Update stale BlobStore docs (#68)
This PR is to clean up the BlobStore Start Guide with current information and fix some minor typos.
jekyll was run locally to verify these changes.
You can merge this Pull Request by running:
git pull https://github.com/rackerlabs/jclouds-site update-stale-docs
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-site/pull/68
-- Commit Summary --
* Cleaned up BlobStore Start Guide and fixed minor typos
* Formatting/typo fixes
-- File Changes --
M guides/azure-storage.md (2)
M reference/configuration.md (7)
M start/blobstore.md (494)
-- Patch Links --
https://github.com/jclouds/jclouds-site/pull/68.patch
https://github.com/jclouds/jclouds-site/pull/68.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Jeremy Daggett <no...@github.com>.
>
> -## Supported Providers
> +Please refer to the [BlobStore Supported Providers](/guides/providers/#blobstore-providers) page for
Fixed.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11222396
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #225](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/225/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-39145122
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
>
> -## Using BlobStore API
> +A `BlobStoreContext` associates an identity on a provider to a set of network connections.
[minor] "identify for" rather than "identity on"?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r13615450
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Everett Toews <no...@github.com>.
Closed #68.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
>
> ### Access Control
>
> -By default, every item you put into a container is private, if you are interested in giving access to others,
> -you will have to explicitly configure that.
> +By default, every item you put into a container is _private_, if you are interested in giving access
> +to others, you will have to explicitly configure that. Exposing public containers is provider-
> +specific.
[minor] remove the space between "provider-" and "specific? Comes out like this:
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r13615417
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by jclouds-commentator <no...@github.com>.
Go to http://77d3899c9766b8f978ad-505283e67e4f19b040abb331968b83b4.r12.cf1.rackcdn.com/ to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-41223329
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
@jdaggett Ping? Would be great to finally get this in.
@andrewgaul @shrinadj As expert BlobStore-rs, any comments you have would be really valuable!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-50352879
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Jeremy Daggett <no...@github.com>.
> {% endhighlight %}
>
> -#### AsyncBlobStore
> +### AsyncBlobStore API
I removed it for now. Comments below.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11222504
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
> I've repaired the jclouds-site-staging job by reverting it to 1.7.1 for the time being.
Thanks, @everett-toews!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-41244474
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
>
> -We use the same model across the [ComputeGuide](/documentation/userguide/compute) which allows you to facilitate collocation of processing and data.
> +Our location API helps you to portably identify a container within context, such as Americas or
"within a context"?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11151030
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Jeremy Daggett <no...@github.com>.
That line wraps! ;) "rackspace-cloudfiles-us" is correct.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-41102522
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
Hm. The _job_ succeeds, at least...but the upload doesn't look good:
@jdaggett @everett-toews Any idea why this might not be working? Could you have a look a the contents of that blob to see what's actually up there?
Thanks!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-41103658
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Jeremy Daggett <no...@github.com>.
Closed #68.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#event-175946587
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
>
> -A blob you've downloaded via `blobstore.getBlob()` can be accessed via `blob.getPayload().getInput()` or
> -`blob.getPayload().writeTo(outputStream)`. Since these are streaming, you shouldn't have a problem with memory
> -unless you rebuffer it.
> +A blob you've downloaded via `blobstore.getBlob()` can be accessed via
> +`blob.getPayload().getInput()` or `blob.getPayload().writeTo(outputStream)`. Since these are
> +streaming, you shouldn't have a problem with memory unless you rebuffer it.
[minor] "rebuffer the payload."? "it" sounds like it refers to "memory" here.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r13616180
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #339](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/339/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-45672741
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by jclouds-commentator <no...@github.com>.
Go to http://82cb4d27028b5f2da720-a5885cc8c368884850298f986087b419.r37.cf1.rackcdn.com/ to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-39145294
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
>
> - * *S3* According to Amazon, it is better to create or delete buckets in a separate initialization or setup routine that you run less often.
> - You are also only allowed 100 buckets per account, so be parsimonious (frugal).
> - * *Azure* You have to wait 30 seconds before recreating a container with the same name.
> - * _Azure_ currently supports max 64MB files, google storage has a very large limit,
> - * Amazon S3 introduced a multipart upload possibility which allow files until 5TB size.
> - * _S3_ and _Rackspace_ CloudFiles have a 5GB limit. We've engineered jclouds to not put further limits on blob size.
> + * *Amazon S3*, *OpenStack Swift*, and *Rackspace Cloud Files* have a 5GB size limit for blobs.
> + We've engineered jclouds to not put further limits on blob size.
> + * *Google Cloud Storage* has has no limits on object size.
> + * *Amazon S3*: According to Amazon, it is better to create or delete buckets in a separate
> + initialization or setup routine that you run less often. You are also only allowed 100 buckets
> + per account, so be mindful of this limitation.
> + * *Azure*: You have to wait 30 seconds before recreating a container with the same name. Azure
> + supports a maximum size of 200GB for block blobs and 1TB for page blobs.
Rather than trying to keep this up to date, how about saying something like "see the provider guides for blobstore-specific limitations and tips"?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11151201
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Jeremy Daggett <no...@github.com>.
> @@ -4,206 +4,242 @@ title: BlobStore Guide
> permalink: /start/blobstore/
> ---
>
> -The BlobStore API is a portable means of managing key-value storage providers such as Microsoft Azure Blob Service
> -and Amazon S3. It offers both asynchronous and synchronous APIs, as well as Map-based access to your data.
> -Our APIs are dramatically simplified from the providers, yet still offer enough sophistication to perform
> -most work in a portable manner.
> -We also have integrations underway for popular tools such as Apache commons VFS.
> +The BlobStore API is a portable means of managing key-value storage providers such as Microsoft
> +Azure Blob Service, Amazon S3, or OpenStack Object Storage. It offers both synchronous and
> +asynchronous APIs, as well as map-based access to your data.
Removed the async part.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11222367
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Jeremy Daggett <no...@github.com>.
>
> -We use the same model across the [ComputeGuide](/documentation/userguide/compute) which allows you to facilitate collocation of processing and data.
> +Our location API helps you to portably identify a container within context, such as Americas or
Thx. Fixed.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11222370
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Everett Toews <no...@github.com>.
Closed #68.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#event-129991911
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
Just one small comment about removing the AsnycBlobStore from the example code, otherwise I think this is good to go. Many thanks, @jdaggett - much improved!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-39382321
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by jclouds-commentator <no...@github.com>.
Go to http://80cec3fa1087b696dadb-0afa8be6bff6b8d6117fe45f9d49a980.r48.cf5.rackcdn.com/ to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-41103393
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Everett Toews <no...@github.com>.
Reopened #68.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#event-129991939
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
Suggestion: close this and continue at #133?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-58404918
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Jeremy Daggett <no...@github.com>.
>
> ### Virtual Path
>
> -A virtual path can either be a marker file or a prefix. In either case, they are purely used to
> -give the appearance of a hierarchical structure in a flat BlobStore.
> -When you perform a list at a virtual path, the blob names returned are absolute paths.
> +A **_virtual path_** can either be a marker file or a prefix.
> +
> +In either case, they are purely used to give the appearance of a hierarchical structure in a flat
> +BlobStore. When you perform a list at a virtual path, the blob names returned are absolute paths.
Must have missed that one! Thx
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11222470
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
>
> -## Supported Providers
> +Please refer to the [BlobStore Supported Providers](/guides/providers/#blobstore-providers) page for
"Supported BlobStore Providers"?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11151081
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
>
> -This is verified against all of our http clients, conceding that it isn't going to help limited environments such as
> -google app engine.
> +This is verified against all of our http clients, conceding that it isn't going to help limited
[minor] "HTTP clients"? And drop the ", conceding that..." bit - is that clear or highly relevant today?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r13616139
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #337](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/337/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-45661429
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #270](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/270/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-41103159
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
Reopened #68.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
> How would the examples break that?
That's already the (hopefully) fixed version, by the way - it was downloading the old cloudfiles-us provider
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-41102325
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
> @@ -4,206 +4,242 @@ title: BlobStore Guide
> permalink: /start/blobstore/
> ---
>
> -The BlobStore API is a portable means of managing key-value storage providers such as Microsoft Azure Blob Service
> -and Amazon S3. It offers both asynchronous and synchronous APIs, as well as Map-based access to your data.
> -Our APIs are dramatically simplified from the providers, yet still offer enough sophistication to perform
> -most work in a portable manner.
> -We also have integrations underway for popular tools such as Apache commons VFS.
> +The BlobStore API is a portable means of managing key-value storage providers such as Microsoft
> +Azure Blob Service, Amazon S3, or OpenStack Object Storage. It offers both synchronous and
> +asynchronous APIs, as well as map-based access to your data.
Isn't the async API essentially deprecated? The map stuff certainly is. In which case, "It offers a synchronous API to access your data."?
@andrewgaul: Thoughts?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11151023
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Jeremy Daggett <no...@github.com>.
This guide has needed some love. :) I feel that we should take the async references out completely. If its not in the docs, then new users won't accidentally start using the async interfaces. The section "Multipart Upload" should possibly move to the provider specific guide. This was just a first stab at updating the information in the guide. More to come... :)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-39371917
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
>
> -### Multipart upload
> -
> -Providers may implement multipart upload for large or very files.
> -Here's an example of `multipart upload` using aws-s3 provider, which [allow uploading files large as 5TB.](http://docs.amazonwebservices.com/AmazonS3/latest/dev/index.html?qfacts.html)
> +Providers may implement multipart upload for large or very files. Here's an example of multipart
> "for large or very files" -- ???
"for large or very large files, I'm pretty sure". But I like the idea of a "very file" ;-)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r15487291
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #274](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/274/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-41222222
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
>
> -{% highlight clojure %}
> -(defproject mygroup/myproject "1.0.0"
> - :description "FIXME: write"
> - :dependencies [[org.clojure/clojure "1.2.0"]
> - [org.clojure/clojure-contrib "1.2.0"]
> - [org.jclouds/jclouds-allblobstore "1.1.0"]])
> -{% endhighlight %}
> +<!-- TODO: update this to latest clojure -->
> +The above examples show how to use the `BlobStore` API in Java. The same API can be utilized Clojure!
"utilized in/by/via/from Clojure"?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r13615641
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #267](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/267/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-41100225
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
As for the change: +1 - looks good to me. Thanks, @jdaggett!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-41244721
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
>
> ### Filesystem Provider
>
> -Our file system BlobStore allows you to use the same API when persisting to disk, memory, or a remote BlobStore like Amazon S3.
> +Our **_filesystem_** provider allows you to use the same API when persisting to disk, memory, or a
Same question about formatting?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11151069
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #268](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/268/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-41101714
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Jeremy Daggett <no...@github.com>.
> {% endhighlight %}
>
> ### Logging
>
> -You can now see status of aggregate blobstore commands by enabling at least DEBUG on the log category: "jclouds.blobstore".
> +You can now see status of aggregate blobstore commands by enabling at least **DEBUG** on the log
> +category `jclouds.blobstore`.
Agreed!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11222506
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Jeremy Daggett <no...@github.com>.
@demobox Interesting. How would the examples break that?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-41101709
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
Closed #68.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
>
> -### Integration with non-java clients
> +You have a choice of using either the **_synchronous_** or **_asynchronous_** BlobStore API. If you choose
> +to use the asynchronous API, you will benefit by gaining access to the most efficient means to
See comment above about the async API.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11151055
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Shri Javadekar <no...@github.com>.
>
> +A connection to a `BlobStore` in jclouds is called a `BlobStoreContext`. It is is thread-safe and
"It is is" -> "It is"
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r15486474
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
> - <param name="Threshold" value="TRACE" />
> - <layout class="org.apache.log4j.PatternLayout">
> - <param name="ConversionPattern" value="%d %-5p [%c] (%t) %m%n" />
> - </layout>
> - </appender>
> -
> - <appender name="ASYNCBLOBSTORE" class="org.apache.log4j.AsyncAppender">
> - <appender-ref ref="BLOBSTOREFILE" />
> - </appender>
> -
> - <category name="jclouds.blobstore">
> - <priority value="TRACE" />
> - <appender-ref ref="ASYNCBLOBSTORE" />
> - </category>
> +// Upload the Blob
> +String futureETag = blobStore.putBlob(containerName, blob, multipart());
Again, not closing the context here. And why "futureETag" instead of e.g. "eTag", out of curiosity?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r13615612
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
>
> -The BlobStore API requires knowledge of 3 concepts: service, container, and blob.
> -A BlobStore is a key-value store such as Amazon S3, where your account exists, and where you can create containers.
> -A container is a namespace for your data, and you can have many of them.
> -Inside your container, you store data as a Blob referenced by a name. In all BlobStores the combination of your account, container,
> -and blob relates directly to an HTTPs url.
> +A **_blobstore_** is a key-value storage **_service_**, such as Amazon S3, where your account exists, and
Do we need to make "service" a Top Level Concept here? Do we use that anywhere in the code, actually?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11151098
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Everett Toews <no...@github.com>.
Reopened #68.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#event-129950737
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Everett Toews <no...@github.com>.
Closed #68.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
>
> -For this reason, we have a `DeleteDirectoryStrategy` strategy. The default version of this used
> -for flat trees removes all known deviations of directory markers.
> +The challenge with this approach is that there are multiple ways to suggest presence of a
> +directory. For example, it is entirely possible that _both_ the trailing slash `/` and `_$folder$`
> +suffixes exist. For this reason, a simple remove, or `rmDir` will not work, as may be the case that
"as it may be the case"?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r13615820
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Jeremy Daggett <no...@github.com>.
>
> -The BlobStore API requires knowledge of 3 concepts: service, container, and blob.
> -A BlobStore is a key-value store such as Amazon S3, where your account exists, and where you can create containers.
> -A container is a namespace for your data, and you can have many of them.
> -Inside your container, you store data as a Blob referenced by a name. In all BlobStores the combination of your account, container,
> -and blob relates directly to an HTTPs url.
> +A **_blobstore_** is a key-value storage **_service_**, such as Amazon S3, where your account exists, and
Agreed. I will remove the opening paragraph since it doesn't make a lot of sense.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11222402
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
>
> ### Transient Provider
>
> -Our in-memory BlobStore allows you to test your storage code without credentials or a credit card!
> +Our **_in-memory_** provider allows you to test your storage code without credentials or a credit card!
Do we need both types of formatting?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11151066
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
>
> {% highlight java %}
> context.close();
> {% endhighlight %}
>
> -There are many options available for creating contexts. Please see the Javadoc for
> -[ContextBuilder](http://demobox.github.com/jclouds-maven-site-1.5.5/1.5.5/jclouds-multi/apidocs/org/jclouds/ContextBuilder.html)
> -for detailed description.
> -
> -### APIs
> +There are many options available for creating a `Context`. Please see the
> +[ContextBuilder](http://javadocs.jclouds.cloudbees.net/org/jclouds/ContextBuilder.html) JavaDocs for
[minor] "Javadocs"
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r13615493
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Everett Toews <no...@github.com>.
Rackspace Cloud Files create static website is broken in 1.7.2, see [JCLOUDS-547](https://issues.apache.org/jira/browse/JCLOUDS-547).
I've repaired the jclouds-site-staging job by reverting it to 1.7.1 for the time being.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-41225028
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #269](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/269/) FAILURE
Looks like there's a problem with this pull request
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-41102557
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by jclouds-commentator <no...@github.com>.
Go to http://6805d61e78699c6102a1-a91789db63c99205e869a37bc5acf6c1.r85.cf1.rackcdn.com/ to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-39374678
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Jeremy Daggett <no...@github.com>.
>
> ### Filesystem Provider
>
> -Our file system BlobStore allows you to use the same API when persisting to disk, memory, or a remote BlobStore like Amazon S3.
> +Our **_filesystem_** provider allows you to use the same API when persisting to disk, memory, or a
Same as above.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11222392
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Jeremy Daggett <no...@github.com>.
>
> -### limitations
> -Each blobstore has its own limitations.
> +Each **BlobStore** has its own limitations:
Missed that one too...
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11222483
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
>
> ## Content Metadata : Content Disposition
>
> -You may be using jclouds to upload some photos to the cloud, show thumbnails of them to the user
> -via a website and allow to download the original image. When the user clicks on the thumbnail,
> -a the download dialog appears. To control the name of the file in the "save as" dialog,
> -you must set [Content Disposition](http://www.jtricks.com/bits/content_disposition.html). Here's how you can do
> -it with BlobStore API:
> +You may be using jclouds to upload some photos to the cloud, show thumbnails of them to the user via
> +a website, and allow to download the original image.
> +
> +When the user clicks on the thumbnail, a download dialog appears. To control the name of the file in
> +the "Save As" dilog, you must set [Content
"dialog, you must set the..."
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r13615945
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Everett Toews <no...@github.com>.
Closed #68.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Jeremy Daggett <no...@github.com>.
>
> ### Transient Provider
>
> -Our in-memory BlobStore allows you to test your storage code without credentials or a credit card!
> +Our **_in-memory_** provider allows you to test your storage code without credentials or a credit card!
If you look at the output of the site, I think it looks much nicer having it bold and italics. ;)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11222387
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
> jclouds-site-pull-requests #269 FAILURE
Grr. Some [Jenkins gremlin](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/269/console). Here we go again...
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-41103049
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
Thanks for chewing through this, @jdaggett! A couple of small text comments, and one question (about whether or not to keep the async API stuff) that I think we can handle in a follow-up PR, if necessary.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-39181200
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Jeremy Daggett <no...@github.com>.
>
> ### Folder
>
> -A folder is a subcontainer. It can contain blobs or other folders. The names of items in a folder are `basenames`.
> -Blob names incorporate folders via "/" - just like you would with a "regular" file system.
> +A **_folder_** is a subcontainer and can contain blobs or other folders.
> +
> +The names of items in a folder are `basenames`. Blob names incorporate folders via a path separator
> +`"/"` and is similar to accessing a file in a typical filesystem.
Fixed.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11222456
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
@jdaggett: Needs a rebase now? GitHub doesn't want to merge at present...
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-41097342
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
>
> ### Folder
>
> -A folder is a subcontainer. It can contain blobs or other folders. The names of items in a folder are `basenames`.
> -Blob names incorporate folders via "/" - just like you would with a "regular" file system.
> +A **_folder_** is a subcontainer and can contain blobs or other folders.
> +
> +The names of items in a folder are `basenames`. Blob names incorporate folders via a path separator
> +`"/"` and is similar to accessing a file in a typical filesystem.
[minor] "a typical"?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11151159
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
Closed #68.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
>
> ### Blob
>
> -A blob is unstructured data that is stored in a container.
> -Some blobstores call them objects, blobs, or files. You lookup blobs in a container by a text key, which often relates
> -directly to the HTTP url used to manipulate it. Blobs can be zero length or larger, some restricting size to 5GB,
> -and others not restricting at all.
> +A **_blob_** is unstructured data that is stored in a container.
> +
> +Some blobstores refer to them as **_objects_**, **_blobs_**, or **_files_**. You lookup a blob in a
> +container by a text key, which often relates directly to the HTTP URL used to manipulate it. Blobs
> +can be zero length or larger, some restricting size to 5GB, and others not restricting at all.
"larger, with some providers limiting blobs to a maximum size, and..."?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11151148
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Everett Toews <no...@github.com>.
@jdaggett Care to address the last comment and then merge/deploy this?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-40421621
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Jeremy Daggett <no...@github.com>.
>
> - * *S3* According to Amazon, it is better to create or delete buckets in a separate initialization or setup routine that you run less often.
> - You are also only allowed 100 buckets per account, so be parsimonious (frugal).
> - * *Azure* You have to wait 30 seconds before recreating a container with the same name.
> - * _Azure_ currently supports max 64MB files, google storage has a very large limit,
> - * Amazon S3 introduced a multipart upload possibility which allow files until 5TB size.
> - * _S3_ and _Rackspace_ CloudFiles have a 5GB limit. We've engineered jclouds to not put further limits on blob size.
> + * *Amazon S3*, *OpenStack Swift*, and *Rackspace Cloud Files* have a 5GB size limit for blobs.
> + We've engineered jclouds to not put further limits on blob size.
> + * *Google Cloud Storage* has has no limits on object size.
> + * *Amazon S3*: According to Amazon, it is better to create or delete buckets in a separate
> + initialization or setup routine that you run less often. You are also only allowed 100 buckets
> + per account, so be mindful of this limitation.
> + * *Azure*: You have to wait 30 seconds before recreating a container with the same name. Azure
> + supports a maximum size of 200GB for block blobs and 1TB for page blobs.
Agreed. Changed the paragraph.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11222494
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by jclouds-commentator <no...@github.com>.
Go to http://74bef59ac1513c054d73-501d1e9dc8bc66c2986fabf75d57b8c6.r98.cf5.rackcdn.com/ to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-45672905
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
>
> -For this reason, we have a `DeleteDirectoryStrategy` strategy. The default version of this used
> -for flat trees removes all known deviations of directory markers.
> +The challenge with this approach is that there are multiple ways to suggest presence of a
> +directory. For example, it is entirely possible that _both_ the trailing slash `/` and `_$folder$`
> +suffixes exist. For this reason, a simple remove, or `rmDir` will not work, as may be the case that
> +there are multiple tokens relating to the same directory.
> +
> +For this reason, we have a `DeleteDirectoryStrategy` strategy. The default version of this used for
> +flat trees removes all known deviations of directory markers.
>
> ## Content Metadata : Content Disposition
[minor] Just "Content Disposition"?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r13615884
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
> {% endhighlight %}
>
> ### Logging
>
> -You can now see status of aggregate blobstore commands by enabling at least DEBUG on the log category: "jclouds.blobstore".
> +You can now see status of aggregate blobstore commands by enabling at least **DEBUG** on the log
> +category `jclouds.blobstore`.
Also link here to the jclouds logging configuration page (http://jclouds.apache.org/reference/logging/)?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11151259
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
>
> -## Uploading Large Files
> +### Uploading
> +As long as you use either `InputStream` or File as the payload your blob, you should
[minor] `File`?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r13616060
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Everett Toews <no...@github.com>.
Closed #68.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#event-129950707
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
> @@ -330,59 +285,89 @@ Clearly, you need to substitute your accounts and keys below.
> (create-container *blobstore* "mycontainer")
> (put-blob *blobstore* "mycontainer" (blob "test" :payload "testdata"))
> {% endhighlight %}
Does Clojure close the context automatically for us?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r13615678
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
>
> {% endhighlight %}
>
> -## Configure multipart upload strategies ==
> -There are two `MultipartUploadStrategy` implementations: `SequentialMultipartUploadStrategy` and `ParallelMultipartUploadStrategy`.
> -Default strategy is the `ParallelMultipartUploadStrategy`. With parallel strategy the number of threads running in parallel can be configured using `jclouds.mpu.parallel.degree` property, the default value is 4.
> +## Multipart Uploads
We already have a section called "Multipart Upload" above...call this "Multipart Upload Strategies" or so?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r13615724
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Jeremy Daggett <no...@github.com>.
Yes, closing.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-58409235
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Jeremy Daggett <no...@github.com>.
>
> ### Blob
>
> -A blob is unstructured data that is stored in a container.
> -Some blobstores call them objects, blobs, or files. You lookup blobs in a container by a text key, which often relates
> -directly to the HTTP url used to manipulate it. Blobs can be zero length or larger, some restricting size to 5GB,
> -and others not restricting at all.
> +A **_blob_** is unstructured data that is stored in a container.
> +
> +Some blobstores refer to them as **_objects_**, **_blobs_**, or **_files_**. You lookup a blob in a
Changed to "You access..."??
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11222430
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
>
> -For this reason, we have a `DeleteDirectoryStrategy` strategy. The default version of this used
> -for flat trees removes all known deviations of directory markers.
> +The challenge with this approach is that there are multiple ways to suggest presence of a
> +directory. For example, it is entirely possible that _both_ the trailing slash `/` and `_$folder$`
> +suffixes exist. For this reason, a simple remove, or `rmDir` will not work, as may be the case that
> +there are multiple tokens relating to the same directory.
> +
> +For this reason, we have a `DeleteDirectoryStrategy` strategy. The default version of this used for
> +flat trees removes all known deviations of directory markers.
"all known types of directory markers"?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r13615864
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
>
> ### Virtual Path
>
> -A virtual path can either be a marker file or a prefix. In either case, they are purely used to
> -give the appearance of a hierarchical structure in a flat BlobStore.
> -When you perform a list at a virtual path, the blob names returned are absolute paths.
> +A **_virtual path_** can either be a marker file or a prefix.
> +
> +In either case, they are purely used to give the appearance of a hierarchical structure in a flat
> +BlobStore. When you perform a list at a virtual path, the blob names returned are absolute paths.
"blobstore"?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11151166
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by jclouds-commentator <no...@github.com>.
Go to http://fc4c72bdc894cf36eb98-56887cf170763a9dddf9f2873e70ba9a.r18.cf5.rackcdn.com/ to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-45661627
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
>
> ### Blob
>
> -A blob is unstructured data that is stored in a container.
> -Some blobstores call them objects, blobs, or files. You lookup blobs in a container by a text key, which often relates
> -directly to the HTTP url used to manipulate it. Blobs can be zero length or larger, some restricting size to 5GB,
> -and others not restricting at all.
> +A **_blob_** is unstructured data that is stored in a container.
> +
> +Some blobstores refer to them as **_objects_**, **_blobs_**, or **_files_**. You lookup a blob in a
". You look up..."?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11151126
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #273](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/273/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-41221788
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
@jdaggett @everett-toews Are we waiting for anything specifically here?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-41724645
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
> * Unlimited scaling
> * Most are billed on a usage basis
>
> ### Container
>
> -A container is a namespace for your objects. Depending on the service, the scope can be global, account, or sub-account scoped.
> -For example, in Amazon S3, containers are called buckets, and they must be uniquely named such that no-one else in
> - the world conflicts. In other blobstores, the naming convention of the container is less strict.
> -All blobstores allow you to list your containers and also the contents within them. These contents can
> -either be blobs, folders, or virtual paths.
> +A **_container_** is a namespace for your objects.
> +
> +Depending on the service, the scope can be **_global_**, **_account_**, or **_sub-account_** scoped.
Also region scoped, now?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11151107
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
>
> ## Content Metadata : Content Disposition
>
> -You may be using jclouds to upload some photos to the cloud, show thumbnails of them to the user
> -via a website and allow to download the original image. When the user clicks on the thumbnail,
> -a the download dialog appears. To control the name of the file in the "save as" dialog,
> -you must set [Content Disposition](http://www.jtricks.com/bits/content_disposition.html). Here's how you can do
> -it with BlobStore API:
> +You may be using jclouds to upload some photos to the cloud, show thumbnails of them to the user via
> +a website, and allow to download the original image.
> +
> +When the user clicks on the thumbnail, a download dialog appears. To control the name of the file in
> +the "Save As" dilog, you must set [Content
> +Disposition](http://www.jtricks.com/bits/content_disposition.html). Here's how you can do it with
[minor] Use a slightly more "official" link, e.g. http://www.iana.org/assignments/cont-disp/cont-disp.xhtml?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r13615977
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
>
> -### limitations
> -Each blobstore has its own limitations.
> +Each **BlobStore** has its own limitations:
Why caps now? Elsewhere, we use "blobstore" to refer to the generic thing (rather than the jclouds abstraction).
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11151186
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #232](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/232/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-39374504
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Jeremy Daggett <no...@github.com>.
> {% endhighlight %}
>
> -This will give you a connection to the BlobStore, and if it is remote, it will be SSL unless unsupported by
> -the provider. Everything you access from this context will use the same credentials and potentially the same objects.
> +This will give you a connection to the BlobStore, and if it is remote, it will be SSL unless
> +unsupported by the provider. Everything you access from this context will use the same credentials
> +and potentially the same objects.
Removed. Its a little ambiguous.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11222500
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
>
> +// Access the AsyncBlobStore
> +AsyncBlobStore blobStore = context.getAsyncBlobStore();
Use a (sync) BlobStore here?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11227173
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
> {% highlight java %}
>
> -HttpRequest request = context.getSigner().
> - signGetBlob("adriansmovies",
> - "sushi.avi");
> -{% endhighlight %}
> -### clojure example
> +HttpRequest request = context.getSigner()
> + .signGetBlob("adriansmovies", "sushi.avi");
[minor] No need to wrap here?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r13615691
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Jeremy Daggett <no...@github.com>.
>
> +// Access the AsyncBlobStore
> +AsyncBlobStore blobStore = context.getAsyncBlobStore();
@demobox Good catch, thanks!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11862540
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #275](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/275/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-41223209
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Jeremy Daggett <no...@github.com>.
> * Unlimited scaling
> * Most are billed on a usage basis
>
> ### Container
>
> -A container is a namespace for your objects. Depending on the service, the scope can be global, account, or sub-account scoped.
> -For example, in Amazon S3, containers are called buckets, and they must be uniquely named such that no-one else in
> - the world conflicts. In other blobstores, the naming convention of the container is less strict.
> -All blobstores allow you to list your containers and also the contents within them. These contents can
> -either be blobs, folders, or virtual paths.
> +A **_container_** is a namespace for your objects.
> +
> +Depending on the service, the scope can be **_global_**, **_account_**, or **_sub-account_** scoped.
Good catch!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11222405
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
Closed #68.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Everett Toews <no...@github.com>.
Don't forget to squash first!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-40984853
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Shri Javadekar <no...@github.com>.
>
> -### Multipart upload
> -
> -Providers may implement multipart upload for large or very files.
> -Here's an example of `multipart upload` using aws-s3 provider, which [allow uploading files large as 5TB.](http://docs.amazonwebservices.com/AmazonS3/latest/dev/index.html?qfacts.html)
> +Providers may implement multipart upload for large or very files. Here's an example of multipart
"for large or very files" -- ???
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r15486910
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Jeremy Daggett <no...@github.com>.
>
> ### Blob
>
> -A blob is unstructured data that is stored in a container.
> -Some blobstores call them objects, blobs, or files. You lookup blobs in a container by a text key, which often relates
> -directly to the HTTP url used to manipulate it. Blobs can be zero length or larger, some restricting size to 5GB,
> -and others not restricting at all.
> +A **_blob_** is unstructured data that is stored in a container.
> +
> +Some blobstores refer to them as **_objects_**, **_blobs_**, or **_files_**. You lookup a blob in a
> +container by a text key, which often relates directly to the HTTP URL used to manipulate it. Blobs
> +can be zero length or larger, some restricting size to 5GB, and others not restricting at all.
Agreed.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11222444
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #338](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/338/) FAILURE
Looks like there's a problem with this pull request
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-45671918
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
Let me kick this again. It looks like [a recent update](https://github.com/jclouds/jclouds-examples/commit/f9bdf4ca048d1db63fead0855347be6b98828c5b) broke the site PR publisher.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-41101439
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
Reopened #68.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
> .build();
> +
> +// Upload the Blob
> blobStore.putBlob(containerName, blob);
We're not closing the context in this example. Is that OK?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r13615544
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
> ## Return Null on Not Found
>
> -All APIs, provider-specific or abstraction, must return null when an object is requested, but not found.
> -Throwing exceptions is only appropriate when there is a state problem, for example requesting an object from a container
> -that does not exist is a state problem, and should throw an exception.
> +All APIs, provider-specific or abstraction, must return null when an object is requested, but not
> +found. Throwing exceptions is only appropriate when there is a state problem, for example requesting
"...is a state problem. For example, requesting..."
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r13616016
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #266](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/266/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-41064249
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Jeremy Daggett <no...@github.com>.
>
> -### Integration with non-java clients
> +You have a choice of using either the **_synchronous_** or **_asynchronous_** BlobStore API. If you choose
> +to use the asynchronous API, you will benefit by gaining access to the most efficient means to
I am going to rip out the whole "Flexible API" section.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11222381
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Everett Toews <no...@github.com>.
Reopened #68.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
> {% endhighlight %}
>
> -#### AsyncBlobStore
> +### AsyncBlobStore API
Remove this whole section? @andrewgaul: thoughts?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11151242
Re: [jclouds-site] Update stale BlobStore docs (#68)
Posted by Andrew Phillips <no...@github.com>.
> {% endhighlight %}
>
> -This will give you a connection to the BlobStore, and if it is remote, it will be SSL unless unsupported by
> -the provider. Everything you access from this context will use the same credentials and potentially the same objects.
> +This will give you a connection to the BlobStore, and if it is remote, it will be SSL unless
> +unsupported by the provider. Everything you access from this context will use the same credentials
> +and potentially the same objects.
Remove the "and potentially the same objects" bit? Not sure that's clear?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11151220