Re: Host KVM Installation documentation
Thanks for identifying this pressing issues. Many of my friends to whom I
have recommended to use Cloudstack (at UG level) say that it the docs are
mostly using CentOS 6's commands for RHEL/CentOS and that many a times they
have ran into issues with the documentation. What I do for host KVM
installation is stop and disable the firewalld, and then install
iptables-services package in CentOS 7. I think Cloudstack regulates the
firewall using iptables, so firewalld support would have to change the way
ACS manages network. I have personally prepared a host KVM installation
document (almost like quick install guide) which includes the changes or
deviations you need to do from the official documentation. If ACS community
needs help in documentation work, I can help as I have few months until the
start of my masters.
Your all other mails too, are relevant. I had a tough time figuring out and
explaining each concept to my colleagues during my internship at a company
as most of the ACS documentation is dated and is no longer relevant. I was
thinking to implement a ACS plugin, but as there were no sufficient docs
available I gave up on it. I don't want anyone to feel the same despair I
experienced if they wanted to extend ACS and add to the ACS community. I
have by far loved ACS more than OpenStack and would certainly love to
contribute to it.
On Sun, 15 Apr 2018 at 10:09 Ron Wheeler <rwheeler@xxxxxxxxxxxxxxxxxxxxx>
> I am surprised to see that RedHat is not supported/recommended.
> What about Atomic? CoreOS?
> *Homogeneous CPUs*
> "All hosts within a cluster must be homogenous. The CPUs must be of the
> same type, count, and feature flags"
> This appears to be an attempt to add some flesh to the definition of
> What does type mean - AMD vs Intel? Can you really not use an Athlon
> in the same cluster as a Phenom?
> Count of what? CPUs?
> Surely not all feature flags matter?
> What is the real restriction?
> When you deploy CloudStack, the hypervisor host must not have any VMs
> already running. These will be destroy by CloudStack
> Might be better expressed as
> When you deploy CloudStack, any VMs already running on the hypervisor
> host will be destroyed by CloudStack.
> *Configure CPU model for KVM guest (Optional)*
> By default, the CPU model of KVM instance is likely QEMU Virtual CPU
> version x.x.x with least CPU features exposed.
> likely??? What does this mean?
> *CentOS 7 uses Firewalld**
> The section on opening ports in the firewall uses iptables which is no
> longer used in CentOS 7*
> Ron Wheeler
> Artifact Software Inc
> email: rwheeler@xxxxxxxxxxxxxxxxxxxxx
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102 <(866)%20970-2435>