This is an automated email from the ASF dual-hosted git repository.
dahn pushed a commit to branch staging-site
in repository https://gitbox.apache.org/repos/asf/cloudstack-www.git
The following commit(s) were added to refs/heads/staging-site by this push:
new 7616b130c fix broken links in old blogs (#281)
7616b130c is described below
commit 7616b130c82c1d452d7f09c28cc0af3b8f118764
Author: dahn <daan.hoogl...@shapeblue.com>
AuthorDate: Fri Jan 17 11:26:54 2025 +0100
fix broken links in old blogs (#281)
---
blog/2013-02-26-apache_cloudstack_weekly_news_25.md | 2 +-
blog/2013-03-05-apache_cloudstack_weekly_news_41.md | 4 ++--
blog/2013-03-12-apache_cloudstack_weekly_news_111.md | 2 +-
blog/2013-07-02-apache_cloudstack_weekly_news_12.md | 2 +-
blog/2016-02-05-two_late_announced_security_advisories.md | 4 ++--
blog/2024-12-02-cloudstack-4.20.0.0-release/index.md | 2 +-
6 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/blog/2013-02-26-apache_cloudstack_weekly_news_25.md
b/blog/2013-02-26-apache_cloudstack_weekly_news_25.md
index 12b12ed00..1d9933875 100644
--- a/blog/2013-02-26-apache_cloudstack_weekly_news_25.md
+++ b/blog/2013-02-26-apache_cloudstack_weekly_news_25.md
@@ -43,7 +43,7 @@ possible.</p></blockquote>
<h5><a
name="ApacheCloudstackWeeklyNews-25February2013-QAScrumMeetingMinutes"></a>QA
Scrum Meeting Minutes</h5>
-<p><a href="/confluence/display/CLOUDSTACK/Minutes+18th+Feb+2013"
title="Minutes 18th Feb 2013">The QA Scrum meeting minutes for 18 February
2013</a> sent to the mailing list.</p>
+<p><a
href="https://cwiki.apache.org/confluence/display/CLOUDSTACK/Minutes+18th+Feb+2013";
title="Minutes 18th Feb 2013">The QA Scrum meeting minutes for 18 February
2013</a> sent to the mailing list.</p>
<h5><a
name="ApacheCloudstackWeeklyNews-25February2013-WeeklyIRCMeetingMinutes"></a>Weekly
IRC Meeting Minutes</h5>
diff --git a/blog/2013-03-05-apache_cloudstack_weekly_news_41.md
b/blog/2013-03-05-apache_cloudstack_weekly_news_41.md
index 472452d5d..3ec755b1b 100644
--- a/blog/2013-03-05-apache_cloudstack_weekly_news_41.md
+++ b/blog/2013-03-05-apache_cloudstack_weekly_news_41.md
@@ -32,7 +32,7 @@ code developed elsewhere.</p></blockquote>
<p>Rohit Yadav <a href="http://markmail.org/message/josnaa7tgvnmruva";
class="external-link" rel="nofollow">shared "that the do-it-yourself systemvm
appliance feature works for me, for Xen,"</a>:</p>
<blockquote>
-<p>There is one catch though, VirtualBox exports VHD appliance which is said
to be compliant with HyperV. I thought we may need to do something for Xen
separately, so I followed and <a
href="http://rohityadav.in/logs/building-systemvms/"; class="external-link"
rel="nofollow">found a way</a>. The "way" is to export a raw disk image and
convert it to a VHD <a
href="/confluence/pages/createpage.action?spaceKey=CLOUDSTACK&title=1&linkCreation=true&fromPageId=30755264"
class="creat [...]
+<p>There is one catch though, VirtualBox exports VHD appliance which is said
to be compliant with HyperV. I thought we may need to do something for Xen
separately, so I followed and <a
href="http://rohityadav.in/logs/building-systemvms/"; class="external-link"
rel="nofollow">found a way</a>. The "way" is to export a raw disk image and
convert it to a VHD <a
href="https://cwiki.apache.org/confluence/pages/createpage.action?spaceKey=CLOUDSTACK&title=1&linkCreation=true&fromPageI
[...]
<p>Read the rest of the thread if you have an interest in creating custom
system VMs for CloudStack.</p>
@@ -68,7 +68,7 @@ code developed elsewhere.</p></blockquote>
<h5><a name="ApacheCloudStackWeeklyNews-4March2013-APIThrottling"></a>API
Throttling</h5>
-<p>Parth Jagirdar has <a href="http://markmail.org/thread/nj75xlemzxcy5qr2";
class="external-link" rel="nofollow">started a discuss thread</a> about API
throttling. "API throttling number can be set to anything at this point.
Suggestions here is to have this number set to a value that is 'greater than'
number of API that can be fired by any potential action on UI." (Note, Parth
then sent out a follow-up email to correct the initial subject line from
[DISCUSS} to <a href="/confluence/pages [...]
+<p>Parth Jagirdar has <a href="http://markmail.org/thread/nj75xlemzxcy5qr2";
class="external-link" rel="nofollow">started a discuss thread</a> about API
throttling. "API throttling number can be set to anything at this point.
Suggestions here is to have this number set to a value that is 'greater than'
number of API that can be fired by any potential action on UI." (Note, Parth
then sent out a follow-up email to correct the initial subject line from
[DISCUSS} to <a href="https://cwiki.apa [...]
<h5><a
name="ApacheCloudStackWeeklyNews-4March2013-BranchStabilityStatus"></a>Branch
Stability Status</h5>
diff --git a/blog/2013-03-12-apache_cloudstack_weekly_news_111.md
b/blog/2013-03-12-apache_cloudstack_weekly_news_111.md
index 9322cf255..3a30ffec1 100644
--- a/blog/2013-03-12-apache_cloudstack_weekly_news_111.md
+++ b/blog/2013-03-12-apache_cloudstack_weekly_news_111.md
@@ -43,7 +43,7 @@ inefficient for certain primary storage types, for example if
you end up creatin
<h5><a
name="ApacheCloudStackWeeklyNews-11March2013-BuildVerificationTest%28BVT%29forCloudStackCheckins"></a>Build
Verification Test (BVT) for CloudStack Checkins</h5>
-<p>Alex Huang <a href="http://markmail.org/message/kvtkfjaswopqkd7m";
class="external-link" rel="nofollow">proposed</a> building a BVT system to
"ensure that checkins do not break the <a
href="/confluence/pages/createpage.action?spaceKey=CLOUDSTACK&title=master&linkCreation=true&fromPageId=30756122"
class="createlink">master</a> branch." </p>
+<p>Alex Huang <a href="http://markmail.org/message/kvtkfjaswopqkd7m";
class="external-link" rel="nofollow">proposed</a> building a BVT system to
"ensure that checkins do not break the <a
href="https://cwiki.apache.org/confluence/pages/createpage.action?spaceKey=CLOUDSTACK&title=master&linkCreation=true&fromPageId=30756122";
class="createlink">master</a> branch." </p>
<p>After a fair amount of discussion, Chip Childers <a
href="http://markmail.org/message/2tavrqatlyyrwmp6"; class="external-link"
rel="nofollow">responded, saying that the first step to getting Gerrit</a> is
"for us to agree to using it and to be able to clearly articulate <b>why</b>.
Without being able to explain our issue, we'll be questioned about jumping to a
tool-based solution by the infra team."</p>
diff --git a/blog/2013-07-02-apache_cloudstack_weekly_news_12.md
b/blog/2013-07-02-apache_cloudstack_weekly_news_12.md
index 064fe4309..e40df2282 100644
--- a/blog/2013-07-02-apache_cloudstack_weekly_news_12.md
+++ b/blog/2013-07-02-apache_cloudstack_weekly_news_12.md
@@ -111,7 +111,7 @@ slug: apache_cloudstack_weekly_news_12
<p>After complaints that the BVT environment was broken, Alex Huang did some
investigating to identify the root cause and raise a suggest on how BVT testing
should be <a href="http://markmail.org/message/si6rt2mkc7dt4krw";
class="external-link" rel="nofollow">dealt with in the future</a>. </p>
<blockquote>
-<p>After Dave's complain in the vmsync <a
href="/confluence/pages/createpage.action?spaceKey=CLOUDSTACK&title=MERGE&linkCreation=true&fromPageId=31825135"
class="createlink">MERGE</a> thread about BVT in horrible shape on master, I
went around to figure out what exactly happened. The best I can figure is that
after a certain merge (I will leave out which merge as that's not important),
BVT no longer runs automatically. It was promised to be fixed and there are
people who ar [...]
+<p>After Dave's complain in the vmsync <a
href="https://cwiki.apache.org/confluence/pages/createpage.action?spaceKey=CLOUDSTACK&title=MERGE&linkCreation=true&fromPageId=31825135";
class="createlink">MERGE</a> thread about BVT in horrible shape on master, I
went around to figure out what exactly happened. The best I can figure is that
after a certain merge (I will leave out which merge as that's not important),
BVT no longer runs automatically. It was promised to be fixed and [...]
<p>New Rule....<br/>
If BVT or automated regression tests break on master or any release branch, we
revert all commits that broke it. It doesn't matter if they promise to fix it
within the next hour. If it's broken, the release manager will revert the
commits and developers must resubmit. It sounds mean but it's the only way
this problem can be fixed. </p>
diff --git a/blog/2016-02-05-two_late_announced_security_advisories.md
b/blog/2016-02-05-two_late_announced_security_advisories.md
index 865f769fb..f8634bc50 100644
--- a/blog/2016-02-05-two_late_announced_security_advisories.md
+++ b/blog/2016-02-05-two_late_announced_security_advisories.md
@@ -10,10 +10,10 @@ slug: two_late_announced_security_advisories
<!-- truncate -->
<p>While these vulnerabilities are of moderate and low severity
(respectively), the reason for this post is because the advisories were
announced approximately 5 months after the first release of the patches in
4.5.2. This is personally embarrassing, unacceptable, and in a more severe case
could be downright dangerous.</p>
-<H2>What happened?</H2>
+<h2>What happened?</h2>
<p>The CloudStack security team worked through the related vulnerabilities
through the summer of 2015. We had advisory drafts, patches, and mitigations
all ready well before the release. Far enough ahead, actually, that we forgot
about the release and weren't paying attention to the release (at least I
wasn't - I know others were), and didn't send out the advisories at the
appropriate time. Part of this is due to me having become an unofficial
lead/spokesperson for the security team; In [...]
<p>Luckily, the CloudStack Security Team works with and under the direction of
the ASF security team. During one of their periodic reviews, they noticed
CloudStack had loose ends on these two advisories, and asked for an update.
Earlier today I realized the advisories had not been released, so here we are.
</p>
-<H2>How will we improve?</H2>
+<h2>How will we improve?</h2>
<p>Obviously, we don't want to be in this situation again. Here's some steps
we're taking to minimize the chance of a repeat performance:</p>
<ul>
<li> I've modified the <a
href="https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+Procedure";>Release
Procedure</a> to specifically request the release manager give the security
team a heads up that a release is about to be announced. This can be a simple
non-blocking email that shouldn't slow down the release process, but still
ensure that we're aware of the upcoming release.</li>
diff --git a/blog/2024-12-02-cloudstack-4.20.0.0-release/index.md
b/blog/2024-12-02-cloudstack-4.20.0.0-release/index.md
index 875ad008f..42c074c3f 100644
--- a/blog/2024-12-02-cloudstack-4.20.0.0-release/index.md
+++ b/blog/2024-12-02-cloudstack-4.20.0.0-release/index.md
@@ -112,7 +112,7 @@ Furthermore, already existing features were revamped, such
as the Quota plugin,
"
</em>
-\- [João Jandre Paraquetti](www.linkedin.com/in/joão-jandre-136a32159),
CloudStack Committer, 4.20 Release Manager
+\- [João Jandre
Paraquetti](https://www.linkedin.com/in/joão-jandre-136a32159), CloudStack
Committer, 4.20 Release Manager
</div>
</div>
<br/>
