# service cloud-usage stop
# service cloud-management stop
#
mysqldump
-u root -pmysql_password
cloud >cloudstack_backup.dmp
#
mysqldump
-u root -pmysql_password
cloud_usage >usage_backup.dmp
#
yum
update cloud-*
#
apt-get
update#
apt-get
upgrade cloud-*
# service cloud-management start
# service cloud-usage start
# service cloud-agent stop
# yum update cloud-*
# apt-get update
# apt-get upgrade cloud-*
# service cloud-agent start
/etc/cloud/agent/agent.properties
to change the resource parameter from "com.cloud.agent.resource.computing.LibvirtComputingResource" to "com.cloud.hypervisor.kvm.resource.LibvirtComputingResource".
Field
|
Value
|
---|---|
Name
|
systemvm-vmware-3.0.0
|
Description
|
systemvm-vmware-3.0.0
|
URL
|
http://download.cloud.com/templates/burbank/burbank-systemvm-08012012.ova
|
Zone
|
Choose the zone where this hypervisor is used
|
Hypervisor
|
VMware
|
Format
|
OVA
|
OS Type
|
Debian GNU/Linux 5.0 (32-bit)
|
Extractable
|
no
|
Password Enabled
|
no
|
Public
|
no
|
Featured
|
no
|
# service cloud-usage stop
# service cloud-management stop
#
mysqldump
-u root -pmysql_password
cloud >cloud-backup.dmp
#
mysqldump
-u root -pmysql_password
cloud_usage >cloud-usage-backup.dmp
#
yum
update cloud-*
#
apt-get
update#
apt-get
upgrade cloud-*
warning: /etc/cloud/management/components.xml created as /etc/cloud/management/components.xml.rpmnew
/etc/cloud/management/components.xml
the changes will be preserved in the upgrade. However, you need to do the following steps to place these changes in a new version of the file which is compatible with version 4.0.1-incubating.
/etc/cloud/management/components.xml
. For example:
# mv /etc/cloud/management/components.xml /etc/cloud/management/components.xml-backup
/etc/cloud/management/components.xml.rpmnew
to create a new /etc/cloud/management/components.xml
:
# cp -ap /etc/cloud/management/components.xml.rpmnew /etc/cloud/management/components.xml
components.xml
.
# vi /etc/cloud/management/components.xml
# service cloud-management start
# service cloud-usage start
# service cloud-agent stop
# yum update cloud-*
# apt-get update
# apt-get upgrade cloud-*
# service cloud-agent start
/etc/cloud/agent/agent.properties
to change the resource parameter from "com.cloud.agent.resource.computing.LibvirtComputingResource" to "com.cloud.hypervisor.kvm.resource.LibvirtComputingResource".
cloud-sysvmadm
script to stop, then start, all Secondary Storage VMs, Console Proxy VMs, and virtual routers. Run the script once on each management server. Substitute your own IP address of the MySQL instance, the MySQL user to connect as, and the password to use for that user. In addition to those parameters, provide the -c
and -r
arguments. For example:
# nohup cloud-sysvmadm -d 192.168.1.5 -u cloud -p password -c -r > sysvm.log 2>&1 &
# tail -f sysvm.log
/opt/xensource/bin/cloud-clean-vlan.sh
/opt/xensource/bin/cloud-prepare-upgrade.sh
xe patch-upload file-name=XS602E003.xsupdate
# xe vm-list
# xe vm-migrate live=true host=host-name
vm=VM-name
/opt/xensource/bin/make_migratable.sh b6cf79c8-02ee-050b-922f-49583d9f1a14
.
# xe host-list
xe
patch-apply host-uuid=host-uuid
uuid=hotfix-uuid
Copy from here...
|
...to here
|
---|---|
/usr/lib64/cloud/common/scripts/vm/hypervisor/xenserver/xenserver60/NFSSR.py
|
/opt/xensource/sm/NFSSR.py
|
/usr/lib64/cloud/common/scripts/vm/hypervisor/xenserver/setupxenserver.sh
|
/opt/xensource/bin/setupxenserver.sh
|
/usr/lib64/cloud/common/scripts/vm/hypervisor/xenserver/make_migratable.sh
|
/opt/xensource/bin/make_migratable.sh
|
# tar xf xenserver-cloud-supp.tgz
# xe-install-supplemental-pack xenserver-cloud-supp.iso
# xe-switch-network-backend bridge
/opt/xensource/bin/setupxenserver.sh
for pbd in `xe pbd-list currently-attached=false| grep ^uuid | awk '{print $NF}'`; do xe pbd-plug uuid=$pbd ;
Hypervisor
|
Description
|
---|---|
XenServer
|
Name: systemvm-xenserver-3.0.0
Description: systemvm-xenserver-3.0.0
URL: http://download.cloud.com/templates/acton/acton-systemvm-02062012.vhd.bz2
Zone: Choose the zone where this hypervisor is used
Hypervisor: XenServer
Format: VHD
OS Type: Debian GNU/Linux 5.0 (32-bit)
Extractable: no
Password Enabled: no
Public: no
Featured: no
|
KVM
|
Name: systemvm-kvm-3.0.0
Description: systemvm-kvm-3.0.0
URL: http://download.cloud.com/templates/acton/acton-systemvm-02062012.qcow2.bz2
Zone: Choose the zone where this hypervisor is used
Hypervisor: KVM
Format: QCOW2
OS Type: Debian GNU/Linux 5.0 (32-bit)
Extractable: no
Password Enabled: no
Public: no
Featured: no
|
VMware
|
Name: systemvm-vmware-3.0.0
Description: systemvm-vmware-3.0.0
URL: http://download.cloud.com/templates/burbank/burbank-systemvm-08012012.ova
Zone: Choose the zone where this hypervisor is used
Hypervisor: VMware
Format: OVA
OS Type: Debian GNU/Linux 5.0 (32-bit)
Extractable: no
Password Enabled: no
Public: no
Featured: no
|
# service cloud-usage stop
# service cloud-management stop
#
mysqldump
-u root -pmysql_password
cloud >cloud-backup.dmp
#
mysqldump
-u root -pmysql_password
cloud_usage >cloud-usage-backup.dmp
#
yum
update cloud-*
#
apt-get
update#
apt-get
upgrade cloud-*
warning: /etc/cloud/management/components.xml created as /etc/cloud/management/components.xml.rpmnew
/etc/cloud/management/components.xml
file. For example:
#
mv
/etc/cloud/management/components.xml
/etc/cloud/management/components.xml-backup
/etc/cloud/management/components.xml.rpmnew
to create a new /etc/cloud/management/components.xml
:
#
cp
-ap/etc/cloud/management/components.xml.rpmnew
/etc/cloud/management/components.xml
#
vi
/etc/cloud/management/components.xml
/etc/cloud/management/db.properties
file in your previous-version CloudStack installation, the changes will be preserved in the upgrade. However, you need to do the following steps to place these changes in a new version of the file which is compatible with version 4.0.1-incubating.
/etc/cloud/management/db.properties
. For example:
#
mv
/etc/cloud/management/db.properties
/etc/cloud/management/db.properties-backup
/etc/cloud/management/db.properties.rpmnew
to create a new /etc/cloud/management/db.properties
:
#
cp
-ap/etc/cloud/management/db.properties.rpmnew
etc/cloud/management/db.properties
#
vi
/etc/cloud/management/db.properties
#
cloud-setup-encryption
-eencryption_type
-mmanagement_server_key
-kdatabase_key
# service cloud-management start
# service cloud-usage start
# service cloud-agent stop
#
yum
update cloud-*
#
apt-get
update#
apt-get
upgrade cloud-*
# service cloud-agent start
agent.properties
file to the new agent.properties
file by using the following command
sed
-i 's/com.cloud.agent.resource.computing.LibvirtComputingResource/com.cloud.hypervisor.kvm.resource.LibvirtComputingResource/g'/etc/cloud/agent/agent.properties
#
nohup cloud-sysvmadm
-d192.168.1.5
-u cloud -ppassword
-c -r > sysvm.log 2>&1 &#
tail
-fsysvm.log
#
tail
-fsysvm.log
Stopping and starting 1 secondary storage vm(s)... Done stopping and starting secondary storage vm(s) Stopping and starting 1 console proxy vm(s)... Done stopping and starting console proxy vm(s). Stopping and starting 4 running routing vm(s)... Done restarting router(s).
#
ssh
-iprivate-key-path
link-local-ip
-p 3922 # cat /etc/cloudstack-release
Cloudstack Release 4.0.1-incubating Mon Oct 9 15:10:04 PST 2012
#
ssh
-iprivate-key-path
private-ip
-p 3922#
cat
/etc/cloudstack-release
Cloudstack Release 4.0.1-incubating Mon Oct 9 15:10:04 PST 2012
/opt/xensource/bin/cloud-clean-vlan.sh
/opt/xensource/bin/cloud-prepare-upgrade.sh
xe patch-upload file-name=XS602E003.xsupdate
# xe vm-list
#
xe
vm-migrate live=true host=host-name
vm=VM-name
/opt/xensource/bin/make_migratable.sh b6cf79c8-02ee-050b-922f-49583d9f1a14
.
# xe host-list
xe patch-apply host-uuid=host-uuid
uuid=hotfix-uuid
Copy from here...
|
...to here
|
---|---|
/usr/lib64/cloud/common/scripts/vm/hypervisor/xenserver/xenserver60/NFSSR.py
|
/opt/xensource/sm/NFSSR.py
|
/usr/lib64/cloud/common/scripts/vm/hypervisor/xenserver/setupxenserver.sh
|
/opt/xensource/bin/setupxenserver.sh
|
/usr/lib64/cloud/common/scripts/vm/hypervisor/xenserver/make_migratable.sh
|
/opt/xensource/bin/make_migratable.sh
|
# tar xf xenserver-cloud-supp.tgz
# xe-install-supplemental-pack xenserver-cloud-supp.iso
# xe-switch-network-backend bridge
/opt/xensource/bin/setupxenserver.sh
for pbd in `xe pbd-list currently-attached=false| grep ^uuid | awk '{print $NF}'`; do xe pbd-plug uuid=$pbd ;
Defect
|
Description
|
---|---|
PropagateResourceEventCommand failes in cluster configuration.
| |
When running cloud-setup-databases, it auto chooses the highest priority nic(lowest number ie: eth0).
| |
Install Guide: Section 4.5.5 (Prepare NFS Shares): Confusing statement about iSCSI
| |
Primary Storage and Secondary Storage sections missing sub-sections
| |
restartNetwork call causes VM to be unreachable when Nicira based SDN is used.
| |
XSL files missing license header.
| |
SetVPCStaticNatRules unimplemented for KVM.
| |
SSVM bootstrap failure on XenServer hosts with E3 CPU.
| |
French language file quotes are dropping javascript syntax errors.
| |
API Doc for uploadCustomCertificate doesn't explain how to use the optional parameters well.
| |
Installation Documentation error: Section 4.5.5.2 needs to mention nfs-kernel-server.
| |
Missing dependency in RPM of KVM Agent.
| |
VPC router needs to resolve its hostname.
| |
CloudStack logs the private key in plaintext.
| |
fix api docs for listSSHKeyPairs.
| |
NVP Installation.
| |
remove citrix cloudpatform from 4.0 build - CloudStack is ASF project.
| |
Usage server doesn't work in 4.0.0 due to missing db changes.
| |
Wrong vnet in iptables on KVM hypervisors after VM reboot.
| |
In the add primary storage dialog in the ui the RBD fields don't disappear when changing from RBD to another protocol.
|
Issue ID
|
Description
|
---|---|
Nexus 1000v DVS integration is not functional
This source code release includes some partial functionality to support the Cisco Nexus 1000v Distributed Virtual Switch within a VMware hypervisor environment. The functionality is not complete at this time.
| |
OVM - cannot create guest VM
This source code release has regressed from the CloudStack 2.2.x code and is unable to support Oracle VM (OVM).
| |
Deleting a project fails when executed by the regular user. This works as expected for root/domain admin. To workaround, perform either of the following:
|