So I gave a first stab at changing the url for downloading (
download.cloud.com). Please empty your guns at this. I didn't follow all of
the discussions around this but deemed it important enough to just start
working on it.

On Tue, Jun 7, 2016 at 12:24 PM, DaanHoogland <g...@git.apache.org> wrote:

> GitHub user DaanHoogland opened a pull request:
>
>     https://github.com/apache/cloudstack/pull/1582
>
>     CLOUDSTACK-9408 for the move away from download.cloud.com
>
>      - commented some occurences of cloud.com as being harmless
>       * examples
>       * identifiers (internal)
>      - changed the URL for vhd-util download
>      - changed comments from 'cloud.com' to 'Apache CloudStack'
>
>     What remains now is to find all other downloads that occur from the
> code and reconstruct the tree in a save location (atm at
> cloudstack.apt-get.eu)
>
>     We will also want to use a CNAME for download.cloudstack.org which
> can for now point to cloudstack.apt-get.eu and can later be implemented
> with a redirect mechanism to a mirror list.
>
>     this should be save to pull in now but we can add the missing parts in
> this PR as well.
>
> You can merge this pull request into a Git repository by running:
>
>     $ git pull https://github.com/DaanHoogland/cloudstack CLOUDSTACK-9408
>
> Alternatively you can review and apply these changes as the patch at:
>
>     https://github.com/apache/cloudstack/pull/1582.patch
>
> To close this pull request, make a commit to your master/trunk branch
> with (at least) the following in the commit message:
>
>     This closes #1582
>
> ----
> commit c443efd7825038c1b42785e13246bbfadd2f08ab
> Author: Daan Hoogland <d...@onecht.net>
> Date:   2016-06-07T10:20:36Z
>
>     CLOUDSTACK-9408 for the move away from download.cloud.com
>      - commented some occurences of cloud.com as being harmless
>       * examples
>       * identifiers (internal)
>      - changed the URL for vhd-util download
>      - changed comments from 'cloud.com' to 'Apache CloudStack'
>
> ----
>
>
> ---
> If your project is set up for it, you can reply to this email and have your
> reply appear on GitHub as well. If your project does not have this feature
> enabled and wishes so, or if the feature is enabled but not working, please
> contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
> with INFRA.
> ---
>



-- 
Daan

Reply via email to