You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGES.md
+8-8
Original file line number
Diff line number
Diff line change
@@ -430,11 +430,11 @@ Bug ID | Description
430
430
[CLOUDSTACK-6099](https://issues.apache.org/jira/browse/CLOUDSTACK-6099) | live migration is failing for vm deployed using dynamic compute offerings with NPE
431
431
[CLOUDSTACK-7528](https://issues.apache.org/jira/browse/CLOUDSTACK-7528) | More verbose logging when sending alert fails
432
432
[CLOUDSTACK-6624](https://issues.apache.org/jira/browse/CLOUDSTACK-6624) | set specifyIpRanges to true if specifyVlan is set to true
433
-
[CLOUDSTACK-7404](https://issues.apache.org/jira/browse/CLOUDSTACK-7404) | Failed to start an instance when originating template has been deleted
433
+
[CLOUDSTACK-7404](https://issues.apache.org/jira/browse/CLOUDSTACK-7404) | Failed to start an instance when originating template has been deleted
434
434
[CLOUDSTACK-6531](https://issues.apache.org/jira/browse/CLOUDSTACK-6531) | Stopping the router in case of command failures
[CLOUDSTACK-6472](https://issues.apache.org/jira/browse/CLOUDSTACK-6472) | (4.3 specific) listUsageRecords: Pull information from removed items as well
460
460
[CLOUDSTACK-5976](https://issues.apache.org/jira/browse/CLOUDSTACK-5976) | Typo in "ssh_keypairs" table's foreign key constraints on the Upgraded Setup
@@ -657,11 +657,11 @@ Version 4.1.0
657
657
-------------
658
658
659
659
This is the second major release of CloudStack from within the Apache Software Foundation, and the
660
-
first major release as a Top-Level Project (TLP).
660
+
first major release as a Top-Level Project (TLP).
661
661
662
662
Build Tool Changes:
663
663
664
-
* The project now uses Maven 3 exclusively to build.
664
+
* The project now uses Maven 3 exclusively to build.
665
665
666
666
New Features:
667
667
* CLOUDSTACK-101: OVS support in KVM
@@ -976,14 +976,14 @@ Issues fixed in this release:
976
976
* CLOUDSTACK-1845: KVM - storage migration often fails
977
977
* CLOUDSTACK-1846: KVM - storage pools can silently fail to be unregistered, leading to failure to register later
978
978
* CLOUDSTACK-2003: Deleting domain while deleted account is cleaning up leaves VMs expunging forever due to 'Failed to update resource count'
979
-
* CLOUDSTACK-2090: Upgrade from version 4.0.1 to version 4.0.2 triggers the 4.0.0 to 4.0.1.
979
+
* CLOUDSTACK-2090: Upgrade from version 4.0.1 to version 4.0.2 triggers the 4.0.0 to 4.0.1.
980
980
* CLOUDSTACK-2091: Error in API documentation for 4.0.x.
981
981
982
982
983
983
Version 4.0.1-incubating
984
984
------------------------
985
985
986
-
This is a bugfix release for Apache CloudStack 4.0.0-incubating, with no new features.
986
+
This is a bugfix release for Apache CloudStack 4.0.0-incubating, with no new features.
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+9-9
Original file line number
Diff line number
Diff line change
@@ -3,25 +3,25 @@ Contributing to Apache CloudStack (ACS)
3
3
4
4
Summary
5
5
-------
6
-
This document covers how to contribute to the ACS project. ACS uses GitHub PRs to manage code contributions.
6
+
This document covers how to contribute to the ACS project. ACS uses GitHub PRs to manage code contributions.
7
7
These instructions assume you have a GitHub.com account, so if you don't have one you will have to create one. Your proposed code changes will be published to your own fork of the ACS project and you will submit a Pull Request for your changes to be added.
8
8
9
9
_Lets get started!!!_
10
10
11
11
Bug fixes
12
12
---------
13
13
14
-
It's very important that we can easily track bug fix commits, so their hashes should remain the same in all branches.
15
-
Therefore, a pull request (PR) that fixes a bug, should be sent against a release branch.
16
-
This can be either the "current release" or the "previous release", depending on which ones are maintained.
14
+
It's very important that we can easily track bug fix commits, so their hashes should remain the same in all branches.
15
+
Therefore, a pull request (PR) that fixes a bug, should be sent against a release branch.
16
+
This can be either the "current release" or the "previous release", depending on which ones are maintained.
17
17
Since the goal is a stable main, bug fixes should be "merged forward" to the next branch in order: "previous release" -> "current release" -> main (in other words: old to new)
18
18
19
19
Developing new features
20
20
-----------------------
21
21
22
-
Development should be done in a feature branch, branched off of main.
23
-
Send a PR(steps below) to get it into main (2x LGTM applies).
24
-
PR will only be merged when main is open, will be held otherwise until main is open again.
22
+
Development should be done in a feature branch, branched off of main.
23
+
Send a PR(steps below) to get it into main (2x LGTM applies).
24
+
PR will only be merged when main is open, will be held otherwise until main is open again.
25
25
No back porting / cherry-picking features to existing branches!
26
26
27
27
PendingReleaseNotes file
@@ -33,7 +33,7 @@ When adding information to the PendingReleaseNotes file make sure that you write
33
33
34
34
Updating the PendingReleaseNotes file is preferably a part of the original Pull Request, but that is up to the developers' discretion.
35
35
36
-
Fork the code
36
+
Fork the code
37
37
-------------
38
38
39
39
In your browser, navigate to: [https://github.com/apache/cloudstack](https://github.com/apache/cloudstack)
@@ -136,4 +136,4 @@ $ git push origin :feature_x
136
136
137
137
Release Principles
138
138
------------------
139
-
Detailed information about ACS release principles is available at https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+principles+for+Apache+CloudStack+4.6+and+up
139
+
Detailed information about ACS release principles is available at https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+principles+for+Apache+CloudStack+4.6+and+up
Copy file name to clipboardExpand all lines: client/bindir/cloud-update-xenserver-licenses.in
+9-9
Original file line number
Diff line number
Diff line change
@@ -7,9 +7,9 @@
7
7
# to you under the Apache License, Version 2.0 (the
8
8
# "License"); you may not use this file except in compliance
9
9
# with the License. You may obtain a copy of the License at
10
-
#
10
+
#
11
11
# http://www.apache.org/licenses/LICENSE-2.0
12
-
#
12
+
#
13
13
# Unless required by applicable law or agreed to in writing,
14
14
# software distributed under the License is distributed on an
15
15
# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
@@ -46,7 +46,7 @@ cfg = "@MSCONF@/db.properties"
46
46
#---------------------- option parsing and command line checks ------------------------
47
47
48
48
49
-
usage="""%prog <license file> <-a | host names / IP addresses...>
49
+
usage="""%prog <license file> <-a | host names / IP addresses...>
50
50
51
51
This command deploys the license file specified in the command line into a specific XenServer host or all XenServer hosts known to the management server."""
Copy file name to clipboardExpand all lines: plugins/storage/volume/storpool/README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -294,7 +294,7 @@ This is independent of StorPool as snapshots exist on secondary.
294
294
### Creating ROOT volume from templates
295
295
296
296
When creating the first volume based on the given template, if snapshot of the template does not exists on StorPool it will be first downloaded (cached) to PRIMARY storage.
297
-
This is mapped to a StorPool snapshot so, creating succecutive volumes from the same template does not incur additional
297
+
This is mapped to a StorPool snapshot so, creating succecutive volumes from the same template does not incur additional
298
298
copying of data to PRIMARY storage.
299
299
300
300
This cached snapshot is garbage collected when the original template is deleted from CloudStack. This cleanup is done
0 commit comments