Skip to content

Commit 78423a2

Browse files
committed
fix broken links in old blogs
1 parent 3b5757c commit 78423a2

6 files changed

+8
-8
lines changed

blog/2013-02-26-apache_cloudstack_weekly_news_25.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ possible.</p></blockquote>
4343

4444
<h5><a name="ApacheCloudstackWeeklyNews-25February2013-QAScrumMeetingMinutes"></a>QA Scrum Meeting Minutes</h5>
4545

46-
<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>
46+
<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>
4747

4848
<h5><a name="ApacheCloudstackWeeklyNews-25February2013-WeeklyIRCMeetingMinutes"></a>Weekly IRC Meeting Minutes</h5>
4949

blog/2013-03-05-apache_cloudstack_weekly_news_41.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ code developed elsewhere.</p></blockquote>
3232
<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>
3333

3434
<blockquote>
35-
<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&amp;title=1&amp;linkCreation=true&amp;fromPageId=30755264" class="createlink">1</a> but the problem is the VHD created from that "way" fails when vhd-util tries to scan for any dependent VHDs (parents etc.), I don't know what's the reason.</p></blockquote>
35+
<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&amp;title=1&amp;linkCreation=true&amp;fromPageId=30755264" class="createlink">1</a> but the problem is the VHD created from that "way" fails when vhd-util tries to scan for any dependent VHDs (parents etc.), I don't know what's the reason.</p></blockquote>
3636

3737
<p>Read the rest of the thread if you have an interest in creating custom system VMs for CloudStack.</p>
3838

@@ -68,7 +68,7 @@ code developed elsewhere.</p></blockquote>
6868

6969
<h5><a name="ApacheCloudStackWeeklyNews-4March2013-APIThrottling"></a>API Throttling</h5>
7070

71-
<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/createpage.action?spaceKey=CLOUDSTACK&amp;title=DISCUSS&amp;linkCreation=true&amp;fromPageId=30755264" class="createlink">DISCUSS</a>, but all relevant discussion has happened in the original thread. It's probably not necessary to send a follow-up in those situations and may fragment the conversation.)</p>
71+
<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.apache.org/confluence/pages/createpage.action?spaceKey=CLOUDSTACK&amp;title=DISCUSS&amp;linkCreation=true&amp;fromPageId=30755264" class="createlink">DISCUSS</a>, but all relevant discussion has happened in the original thread. It's probably not necessary to send a follow-up in those situations and may fragment the conversation.)</p>
7272

7373
<h5><a name="ApacheCloudStackWeeklyNews-4March2013-BranchStabilityStatus"></a>Branch Stability Status</h5>
7474

blog/2013-03-12-apache_cloudstack_weekly_news_111.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ inefficient for certain primary storage types, for example if you end up creatin
4343

4444
<h5><a name="ApacheCloudStackWeeklyNews-11March2013-BuildVerificationTest%28BVT%29forCloudStackCheckins"></a>Build Verification Test (BVT) for CloudStack Checkins</h5>
4545

46-
<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&amp;title=master&amp;linkCreation=true&amp;fromPageId=30756122" class="createlink">master</a> branch." </p>
46+
<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&amp;title=master&amp;linkCreation=true&amp;fromPageId=30756122" class="createlink">master</a> branch." </p>
4747

4848
<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>
4949

blog/2013-07-02-apache_cloudstack_weekly_news_12.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -111,7 +111,7 @@ slug: apache_cloudstack_weekly_news_12
111111
<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>
112112

113113
<blockquote>
114-
<p>After Dave's complain in the vmsync <a href="/confluence/pages/createpage.action?spaceKey=CLOUDSTACK&amp;title=MERGE&amp;linkCreation=true&amp;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 are actively fixing it but it's been in this way for about two weeks. People running BVTs are working around the problem but it's not automated anymore and so it's no longer running on master. I understand people are nice and tried to be accommodating to other people by working around the problem but sometimes we just have to be an arse. So let me be that arse...</p>
114+
<p>After Dave's complain in the vmsync <a href="https://cwiki.apache.org/confluence/pages/createpage.action?spaceKey=CLOUDSTACK&amp;title=MERGE&amp;linkCreation=true&amp;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 are actively fixing it but it's been in this way for about two weeks. People running BVTs are working around the problem but it's not automated anymore and so it's no longer running on master. I understand people are nice and tried to be accommodating to other people by working around the problem but sometimes we just have to be an arse. So let me be that arse...</p>
115115

116116
<p>New Rule....<br/>
117117
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>

blog/2016-02-05-two_late_announced_security_advisories.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,10 +10,10 @@ slug: two_late_announced_security_advisories
1010
<!-- truncate -->
1111

1212
<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>
13-
<H2>What happened?</H2>
13+
<h2>What happened?</h2>
1414
<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 the past there has been at least one occasion when others released advisories when I was not available, but usually I'm coordinating issues and publishing announcements.</p>
1515
<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>
16-
<H2>How will we improve?</H2>
16+
<h2>How will we improve?</h2>
1717
<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>
1818
<ul>
1919
<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>

blog/2024-12-02-cloudstack-4.20.0.0-release/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -112,7 +112,7 @@ Furthermore, already existing features were revamped, such as the Quota plugin,
112112
"
113113
</em>
114114

115-
\- [João Jandre Paraquetti](www.linkedin.com/in/joão-jandre-136a32159), CloudStack Committer, 4.20 Release Manager
115+
\- [João Jandre Paraquetti](https://www.linkedin.com/in/joão-jandre-136a32159), CloudStack Committer, 4.20 Release Manager
116116
</div>
117117
</div>
118118
<br/>

0 commit comments

Comments
 (0)