Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

Proof of concept for single Node installation of Cloudstack

2025-02-24 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >

Share

Shulou(Shulou.com)06/02 Report--

On the left above is my personal Wechat. For further communication, please add WeChat. On the right is my official account "Openstack Private Cloud". If you are interested, please follow us.

The new unit uses cloudstack as the infrastructure of the cloud platform, and it is an old rule to familiarize yourself with the basic components of cloudstack by building an experimental environment.

Find the official installation manual on the official website at the following address:

Http://docs.cloudstack.apache.org/en/4.11.2.0/quickinstallationguide/qig.html

You can see that the update of the cloudstack version should be slow. The latest version up to now (March 2019) is 4.11.2.0. The basic OS used is Centos6.8. Download Centos6.8 first, and the URL is as follows:

Http://mirrors.kernel.org/centos/6/isos/x86_64/

According to the request, the minimal version is downloaded.

First of all, do not rush to start, first read through the above installation manual, the basic idea is to first install the basic OS, and then selinux, ntp, nfs and other basic configuration, configure the installation source of Cloudstack start to install Cloudstack components, install mariadb database, download management image, and then start to configure Cloudstack. Generally speaking, installation and deployment should be simpler than Openstack, because the relevant components of Cloudstack are done directly by downloading standard template images and through virtual machines. I personally feel that this approach is very good, similar to Openstack's Kolla, containerized installation simplifies installation and improves the flexibility of the entire system.

At the beginning of the use of their own work notebook, using VMWare workstation14, virtual machine configuration 4CMagne4G memory, a network card, a piece of 200G hard disk, but after installation found that the boot stuck, forget it, or to use PVE to do, the same virtual machine configuration, configuration of 4CMagin 4G memory, a network card, a 200G hard disk.

The installation process will not be detailed. For details, see the installation manual on the official website above. Record the holes encountered and the places that need to be paid attention to.

1. The latest version in the official website is 4.11, the corresponding operating system version is centos6.8, and the corresponding centos download link in the article is centos6.10.

2. When installing the cloudstack-management command, an error was reported that the location of an installation package could not be found:

# yum-y install cloudstack-management http://download.cloudstack.org/centos/6/4.11/repodata/c696ac24f6d36ebf0ea76e44d12f519601521b6cc659d225f472a9e4fbd3c820-filelists.sqlite.bz2: [Errno 14] PYCURL ERROR 22-"The requested URL returned error: 404 Not Found" Trying other mirror.

By changing the source version of the repo software to 4.12, the baseurl in / etc/yum.repos.d/cloudstack.repo is changed to:

Baseurl= http://download.cloudstack.org/centos/6/4.12/

3. When installing cloudstack-management, the speed is very slow, so I use the scientific Internet surfing agent built by myself. Refer to "linux client Scientific Internet access (K8s installation networking problem)"

4. Long hostname needs to be set. Be careful to modify the hostname in / etc/sysconfig/network and / etc/hosts file to long hostname, otherwise an error will be reported when executing the cloudstack-setup-management command.

5. To use the kvm module, the pve virtual machine needs to be configured to support cpu virtualization as follows: (if proxmoxVE is not used, this part can be skipped)

Execute on the physical machine pve: root@pve:~# qm showcmd 110/usr/bin/kvm-id 110m-name pve-1-chardev 'socket,id=qmp,path=/var/run/qemu-server/111.qmp,server,nowait'-mon' chardev=qmp,mode=control'-pidfile / var/run/qemu-server/111.pid-daemonize-smbios' type=1,uuid=d9eb0729-f0ee-4176-836dKui 308b70d13754'-smp '3coresspushes 3'-nodefaults-boot' menu=on,strict=on,reboot-timeout=1000 Splash=/usr/share/qemu-server/bootsplash.jpg'-vga std-vnc unix:/var/run/qemu-server/111.vnc,x509,password-cpu kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce-m 12000-device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e'-device' pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f'-device 'piix3-usb-uhci,id=uhci,bus=pci.0 Addr=0x1.0x2'-device 'usb-tablet,id=tablet,bus=uhci.0,port=1'-device' virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3'-iscsi 'initiator-name=iqn.1993-08.org.Debian Velvet 01VOV b48afece2d1'-drive' file=/var/lib/vz/template/iso/proxmox-ve_5.2-1.Isophilic noneLegary idyllic driveliche 2 mediajudicial cdrom virtio-scsi-pci,id=scsihw0 aiofolk thread'- device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200'-device' virtio-scsi-pci,id=scsihw0 Bus=pci.0,addr=0x5'-drive 'file=/dev/pvevg2/vm-111-disk-7,if=none,id=drive-scsi0,format=raw,cache=none,aio=native,detect-zeroes=on'-device' scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100'-drive 'file=/dev/pvevg2/vm-111-disk-2,if=none,id=drive-scsi1,format=raw,cache=none,aio=native,detect-zeroes=on'-device' scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=1,drive=drive-scsi1 Id=scsi1'-drive 'file=/dev/pvevg2/vm-111-disk-3,if=none,id=drive-scsi2,format=raw,cache=none,aio=native,detect-zeroes=on'-device' scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=2,drive=drive-scsi2,id=scsi2'-drive 'file=/dev/pvevg2/vm-111-disk-6,if=none,id=drive-scsi3,format=raw,cache=none,aio=native,detect-zeroes=on'-device' scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=3,drive=drive-scsi3,id=scsi3'-netdev 'type=tap,id=net0,ifname=tap111i0 Script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on'-device 'virtio-net-pci,mac=76:60:17:9D:6A:FF,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'-netdev' type=tap,id=net1,ifname=tap111i1,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on'-device 'virtio-net-pci,mac=6A:93:EB:0E:A8:84,netdev=net1,bus=pci.0 Addr=0x13,id=net1,bootindex=301' found the "- cpu kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce" part. Add the "+ vmx," parameter before enforce as follows:-cpu kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,+vmx,enforce saves the modified command to a script 110.sh, and chmod + x 110.sh executes: after qm stop 110 stops the virtual machine, execute the above modified command. / 110.sh. After the virtual machine starts, ssh enters and executes grep vmx / proc/cpuinfo to see if there is any output. As follows: root@pve-1:~# grep vmx / proc/cpuinfo flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx lm constant_tsc nopl xtopology cpuid pni vmx cx16 x2apic hypervisor lahf_lm cpuid_fault pti tpr_shadow vnmi flexpriority ept vpidflags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx lm constant_tsc nopl xtopology cpuid pni vmx cx16 x2apic hypervisor lahf_lm cpuid_fault pti tpr_shadow vnmi flexpriority Ept vpidflags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx lm constant_tsc nopl xtopology cpuid pni vmx cx16 x2apic hypervisor lahf_lm cpuid_fault pti tpr_shadow vnmi flexpriority ept vpid indicates that virtual nesting is already supported.

After installing cloudstack-management and cloudstack-agent, and setting up kvm, start configuring cloudstack:

Log in with the account admin and password password. After logging in, you will be prompted to change the password, such as cloudstack, and then set the information of zone, pod, cluster and host according to the prompts. After that, the system will automatically initialize the operation, as shown below:

As you can see, the two virtual machines to be generated during the initialization process are not successful. It is estimated that the mismatch between the template version and the downloaded template version is caused. The template downloaded in the installation steps of the official website is still version 4.6, and version 4.12 is installed. Download the latest version 4.11.1.2 template again:

/ usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt-m / export/secondary-u http://download.cloudstack.org/systemvm/4.11/systemvmtemplate-4.11.2-kvm.qcow2.bz2-h kvm-F

Note: the templates downloaded above are stored in the / export/secondary directory.

Delete and rebuild secondary storage through the web interface, turn off the firewall, and restart the cloudstack-management service at the same time. After that, wait for the system to rebuild the console proxy VM and Secondary Storage VM system virtual machines. After that, it is normal, as follows:

Create a virtual machine:

Console:

4c 4G memory resources have been used up:

Shut down, reallocate 8-core CPU 8G memory, and then restart, resources are not so tight.

Summary:

The whole installation process is simpler than expected, the concept is clear, and it feels more friendly than openstack. The use and management of virtual machines are also more convenient than openstack, storage management is very flexible, and network management has not yet had time to test. In a word, it is easier to use than openstack as a whole, but I don't seem to have seen anything related to the PAAS layer, such as the PAAS component sahara, the object storage component swift, the file system manila, and so on, which are similar to openstack. The cloudstack official website itself also says that it provides the IAAS layer.

But if you use it purely as a virtual iaas layer, it still doesn't feel as good as proxmoxVE. For various virtualized nanotubes, it may be stronger than proxmoxVE. For example, for environments with VMWare virtualization, kvm virtualization and xen virtual machines, cloudstack can manage nanotubes at the same time. This piece has not been tested yet, and it is not known whether it is convenient to use.

One more choice is always good, all good things, look at different scenes, there can be different choices.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Servers

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report