I am not sure .. I've asked on infrastructre@ (and infra-dev@), but only
gotten crickets. I'll ask again tomorrow on #asfinfra on freenode.

David

On Mon, 2012-02-13 at 15:55 +0200, [email protected] wrote:
> Now that we're 'on git' do we have a new procedure for pushing to the
> deltacloud website? I pushed these changes on Friday but they are yet to
> be reflected. Do we need to do something similar to the old 'git svn up'
> on people.apache.org?
> 
> marios
> 
> On 10/02/12 15:04, [email protected] wrote:
> > Updated Branches:
> >   refs/heads/master db37db48e -> 18716c6bc
> > 
> > 
> > Update site docs - adds link to OpenNebula 'how-to' and couple minor bug 
> > fixes
> > 
> > 
> > Project: http://git-wip-us.apache.org/repos/asf/deltacloud/repo
> > Commit: http://git-wip-us.apache.org/repos/asf/deltacloud/commit/18716c6b
> > Tree: http://git-wip-us.apache.org/repos/asf/deltacloud/tree/18716c6b
> > Diff: http://git-wip-us.apache.org/repos/asf/deltacloud/diff/18716c6b
> > 
> > Branch: refs/heads/master
> > Commit: 18716c6bc4f68d908855e6af8d78a5b919351993
> > Parents: db37db4
> > Author: marios <[email protected]>
> > Authored: Fri Feb 10 14:55:24 2012 +0200
> > Committer: marios <[email protected]>
> > Committed: Fri Feb 10 14:55:24 2012 +0200
> > 
> > ----------------------------------------------------------------------
> >  site/content/_drivers.mdown  |    9 +++++++--
> >  site/lib/provider_support.rb |    5 +++--
> >  site/output/api.html         |    6 +++---
> >  site/output/drivers.html     |   22 +++++++++++++---------
> >  site/output/index.html       |   13 ++++++-------
> >  5 files changed, 32 insertions(+), 23 deletions(-)
> > ----------------------------------------------------------------------
> > 
> > 
> > http://git-wip-us.apache.org/repos/asf/deltacloud/blob/18716c6b/site/content/_drivers.mdown
> > ----------------------------------------------------------------------
> > diff --git a/site/content/_drivers.mdown b/site/content/_drivers.mdown
> > index 4f81e00..cf78b33 100644
> > --- a/site/content/_drivers.mdown
> > +++ b/site/content/_drivers.mdown
> > @@ -119,8 +119,8 @@ host you want to use. Example:
> >  
> >      API_PROVIDER="vsphere.hostname.com"
> >  
> > -The username and password in 401 challenge should be (your???) the same as 
> > in vSphere Control
> > -Center in the vSphere box(clen nechat, ak sa boxom mysli nejaky checkbox, 
> > a nepatri to k nazvu).
> > +The username and password in 401 challenge should be the same as those 
> > used in the vSphere Control
> > +Center.
> >  
> >  ------------------------------------------------
> >  
> > @@ -156,6 +156,11 @@ should be your OpenNebula user and password.
> >  The address, on which the OCCI server is listening, needs to be defined in
> >  an environment variable called OCCI_URL.
> >  
> > +The OpenNebula driver has been updated to support v3.x of the OpenNebula 
> > API.
> > +The driver is contributed by Daniel Molina who has also put together a 
> > 'how to'
> > +for using OpenNebula through Deltacloud which is available
> > +[here](http://wiki.opennebula.org/deltacloud).
> > +
> >  ------------------------------------------------
> >  
> >  ### IBM Smartcloud Driver
> > 
> > http://git-wip-us.apache.org/repos/asf/deltacloud/blob/18716c6b/site/lib/provider_support.rb
> > ----------------------------------------------------------------------
> > diff --git a/site/lib/provider_support.rb b/site/lib/provider_support.rb
> > index e6154b8..5a5cd0a 100644
> > --- a/site/lib/provider_support.rb
> > +++ b/site/lib/provider_support.rb
> > @@ -45,8 +45,9 @@ module ProviderSupportHelper
> >         :blob => { :create => true, :update => true, :rw => true,
> >           :rw_attr => true } },
> >       { :name => "Google Storage", :driver => true,
> > -      :blob => { :create => true, :update => true, :rw => true,
> > -                :rw_attr => true } },
> > +       :container => { :create => true, :update => true },
> > +       :blob => { :create => true, :update => true, :rw => true,
> > +         :rw_attr => true } }
> >      ]
> >    end
> >  
> > 
> > http://git-wip-us.apache.org/repos/asf/deltacloud/blob/18716c6b/site/output/api.html
> > ----------------------------------------------------------------------
> > diff --git a/site/output/api.html b/site/output/api.html
> > index a5fa138..96b56dc 100644
> > --- a/site/output/api.html
> > +++ b/site/output/api.html
> > @@ -458,7 +458,7 @@
> >          meanings assigned to the standard HTTP verbs GET, POST, PUT, and 
> > DELETE.</p>
> >          
> >          <p>Beyond the generally accepted REST design principles, Apache 
> > Deltacloud
> > -        follows the guidelines discussed in the Fedora Project <a 
> > href="http://fedoraproject.org/wiki/Cloud_APIs_REST_Style_Guide"; 
> > title="Fedora Cloud APIs REST Style Guide">Cloud APIs Rest Style 
> > Guide</a>.</p>
> > +        follows the guidelines discussed in the Fedora Project <a 
> > title="Fedora Cloud APIs REST Style Guide" 
> > href="http://fedoraproject.org/wiki/Cloud_APIs_REST_Style_Guide";>Cloud APIs 
> > Rest Style Guide</a>.</p>
> >          
> >          <p>The URL space of the API is structured into collections of 
> > resources
> >          (entities, objects). The top level entities used in the Deltacloud 
> > API are:
> > @@ -1886,7 +1886,7 @@
> >          <p>Creates a new <strong><em>bucket</em></strong> and requires 
> > that you specify the <strong><em>name</em></strong> as a
> >          parameter. Optionally for Amazon S3 buckets, you can specify a 
> > bucket location
> >          with the <strong><em>location</em></strong> parameter, as per
> > -         <a 
> > href="http://docs.amazonwebservices.com/general/latest/gr/index.html?rande.html";
> >  title="AWS Regions and Endpoints">Regions and Endpoints for Amazon Simple 
> > Storage Service</a>;
> > +         <a title="AWS Regions and Endpoints" 
> > href="http://docs.amazonwebservices.com/general/latest/gr/index.html?rande.html";>Regions
> >  and Endpoints for Amazon Simple Storage Service</a>;
> >          valid values for S3 bucket <em>location</em> parameter are: 
> > "us-west-1", "EU",
> >          "ap-southeast-1", "ap-northeast-1" (while not specifying a 
> > location defaults to
> >          the "US Standard" region). Note that clients may specify 
> > parameters as
> > @@ -2031,7 +2031,7 @@
> >          <h4 id="h4_3_10"><code>HEAD 
> > /api/buckets/:bucket_id/:blob_id</code></h4>
> >          
> >          <p>The <code>HTTP HEAD</code> operation on a specified 
> > <strong><em>blob</em></strong> URI will return all user defined
> > -        metadata fields. As per <a 
> > href="http://www.ietf.org/rfc/rfc2616.txt"; title="RFC 2616 HTTP/1.1">RFC 
> > 2616</a>
> > +        metadata fields. As per <a title="RFC 2616 HTTP/1.1" 
> > href="http://www.ietf.org/rfc/rfc2616.txt";>RFC 2616</a>
> >          this <code>HEAD</code> operation does not return a message body. 
> > Rather, the <strong><em>blob</em></strong> user
> >          metadata values are returned in the response 
> > <strong><em>X-Deltacloud-Blobmeta-</em></strong>
> >          headers (e.g., X-Deltacloud-Blobmeta-version:1.2).</p>
> > 
> > http://git-wip-us.apache.org/repos/asf/deltacloud/blob/18716c6b/site/output/drivers.html
> > ----------------------------------------------------------------------
> > diff --git a/site/output/drivers.html b/site/output/drivers.html
> > index d123697..a890918 100644
> > --- a/site/output/drivers.html
> > +++ b/site/output/drivers.html
> > @@ -439,14 +439,13 @@
> >            <tr>
> >              <td class='provider'>
> >                Google Storage
> > -              <span>coming soon</span>
> >              </td>
> > -            <td class="not-supported">TBD</td>
> > -            <td class="not-supported">TBD</td>
> > -            <td class="not-supported">TBD</td>
> > -            <td class="not-supported">TBD</td>
> > -            <td class="not-supported">TBD</td>
> > -            <td class="not-supported">TBD</td>
> > +            <td class="supported">yes</td>
> > +            <td class="supported">yes</td>
> > +            <td class="supported">yes</td>
> > +            <td class="supported">yes</td>
> > +            <td class="supported">yes</td>
> > +            <td class="supported">yes</td>
> >            </tr>
> >          </table>
> >          <p>
> > @@ -786,8 +785,8 @@
> >          
> >          <pre><code>API_PROVIDER="vsphere.hostname.com"&#x000A;</code></pre>
> >          
> > -        <p>The username and password in 401 challenge should be (your???) 
> > the same as in vSphere Control
> > -        Center in the vSphere box(clen nechat, ak sa boxom mysli nejaky 
> > checkbox, a nepatri to k nazvu).</p>
> > +        <p>The username and password in 401 challenge should be the same 
> > as those used in the vSphere Control
> > +        Center.</p>
> >          
> >          <hr />
> >          
> > @@ -823,6 +822,11 @@
> >          <p>The address, on which the OCCI server is listening, needs to be 
> > defined in
> >          an environment variable called OCCI_URL.</p>
> >          
> > +        <p>The OpenNebula driver has been updated to support v3.x of the 
> > OpenNebula API.
> > +        The driver is contributed by Daniel Molina who has also put 
> > together a 'how to'
> > +        for using OpenNebula through Deltacloud which is available
> > +        <a href="http://wiki.opennebula.org/deltacloud";>here</a>.</p>
> > +        
> >          <hr />
> >          
> >          <h3 id="h3_9">IBM Smartcloud Driver</h3>
> > 
> > http://git-wip-us.apache.org/repos/asf/deltacloud/blob/18716c6b/site/output/index.html
> > ----------------------------------------------------------------------
> > diff --git a/site/output/index.html b/site/output/index.html
> > index 33991d0..dfb93c7 100644
> > --- a/site/output/index.html
> > +++ b/site/output/index.html
> > @@ -401,14 +401,13 @@
> >                <tr>
> >                  <td class='provider'>
> >                    Google Storage
> > -                  <span>coming soon</span>
> >                  </td>
> > -                <td class="not-supported">TBD</td>
> > -                <td class="not-supported">TBD</td>
> > -                <td class="not-supported">TBD</td>
> > -                <td class="not-supported">TBD</td>
> > -                <td class="not-supported">TBD</td>
> > -                <td class="not-supported">TBD</td>
> > +                <td class="supported">yes</td>
> > +                <td class="supported">yes</td>
> > +                <td class="supported">yes</td>
> > +                <td class="supported">yes</td>
> > +                <td class="supported">yes</td>
> > +                <td class="supported">yes</td>
> >                </tr>
> >              </table>
> >            </div>
> > 
> 



Reply via email to