GitHub user DaanHoogland reopened 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 <[email protected]>
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'
commit c4f13fe286e0b53360d4adf2e7b63cca3b6c9549
Author: Daan Hoogland <[email protected]>
Date: 2016-06-07T10:40:38Z
CLOUDSTACK-9408 remove antiquated devcloud project
as it contains references to cloud.com and is not current
commit 9b7049d6c116a82287fed7bb9201e0344e70a13f
Author: Daan Hoogland <[email protected]>
Date: 2016-06-07T18:10:25Z
CLOUDSTACK-9408 change URLs in templates.sql
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
