+1 for the feature, but usually I just go for “other paravirtualized (64 bit)” (paraphrasing, mistakes mine) nowadays. What would be more useful, IMHO, is to better document the what the selection OS type selection choice means for a VM. For KVM, it’s a hell of a lot more than SCSI vs IDE root disk...
On Mar 3, 2014, at 12:44 PM, Amogh Vasekar <amogh.vase...@citrix.com<mailto:amogh.vase...@citrix.com>> wrote: Hi, CloudStack currently does not allow an easy way to add new guest OS types, for example, a standard way to add say, CentOS 6.5 even though a hypervisor may support it. Part of the reason is since the OS to hypervisor-specific platform mappings are currently hard-coded into the code-base [1][2] To support such new OS addition, the current way is to manipulate the DB using upgrade scripts and make the necessary code changes. This proposal aims to partially mitigate this issue by allowing the CloudStack admin the ability to add new OS in the list, and update the mapping to hypervisor-specific platform names, via APIs / UI. For now, the admin will be responsible for providing the mapping to hypervisor-specific platform names based on his knowledge, which may be enhanced in future. For example, based on [1], an admin should be able to add a mapping like : CentOS 6.5 (64 bit) -> CentsOS 6.5 . The functional spec can be found at : https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal+-+Ability+t o+add+new+guest+OS+mappings Comments / suggestions welcome. Thanks, Amogh [1] https://github.com/apache/cloudstack/blob/master/plugins/hypervisors/kvm/sr c/com/cloud/hypervisor/kvm/resource/KVMGuestOsMapper.java [2] https://github.com/apache/cloudstack/blob/master/plugins/hypervisors/xen/sr c/com/cloud/hypervisor/xen/resource/CitrixHelper.java Stratosec<http://stratosec.co/> - Compliance as a Service o: 415.315.9385 @johnlkinsella<http://twitter.com/johnlkinsella>
