andrijapanicsb opened a new pull request #3712: Centos8 new builtin templates
URL: https://github.com/apache/cloudstack/pull/3712
 
 
   ## Description
   
   New default/bultin templates for major hypervisors:
   (new PR, instead of #3710 ) 
   - CentOS 8.0 (VMware/KVM/XenServer) 
   - Minimal install with "standard" / "core" groupinstall (a.k.a. additional 
network tools - ifconfig, route, etc.)
   - nano, iftop, iotop, htop, bash-completion, traceroute
   - ssh running, systemctl stop/disable firewalld, SELinux disabled
   - disabled "predictive" interface names (net.ifnames=0 added to kernel boot 
line)
   - stripped UUID/MAC from eth0 network config file
   - VMware: opensource variant "open-vm-tools" installed - recommended by 
VMware (instead of using the one from ESXi hosts); both vmw_pvscsi and vmxnet3 
drivers present and details added to vm_template_table to spin VMs with those 
devices
   - XenServer: XenServer Tools 6.5sp1 installed (xs-tools confirmed as 
running, considering this is CentOS8 which the xs-tools installation script was 
not aware of)
   - KVM: no special configuration, VirtIO present by default
   
   ## Types of changes
   - [ x] Enhancement (improves an existing feature and functionality)
   
   
   ## Screenshots (if appropriate):
   
   ## How Has This Been Tested?
   Templates were deployed on ACS install with old versions of hypervisors: 
VMware 5.5, XenServer 6.5sp1 fully patched up to patch 1066 and CentOS 7.3 (3 
clusters, mixed env) and verified to work on those versions of hypervisors.
   
   Yet to be tested against VMware 6.0/6.5/6.7, XenServer 7.0, 7.1, 7.x and 
Ubuntu 16/18, CentOS 7.6 maybe - but if it works on older ones than any newer 
hypervisor should be no problem.
   
   ## Comment:
   - The only concern is that XenServer 6.5 must have all the patches installed 
(confirmed that patch XS65ESP1066 is needed) - otherwise, CentOS 8 (actually, 
anything newer than CentOS 7.2) will not boot successfully.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to