dheeraj12347 commented on code in PR #14493:
URL: https://github.com/apache/cloudstack/pull/14493#discussion_r4558121861
##########
setup/db/templates.sql:
##########
@@ -34,16 +34,16 @@ INSERT INTO `cloud`.`vm_template` (id, uuid, unique_name,
name, public, created,
VALUES (2, UUID(), 'centos53-x86_64', 'CentOS 5.3(64-bit) no GUI
(XenServer)', 1, now(), now(), 'BUILTIN', 0, 64, 1,
'http://download.cloudstack.org/templates/builtin/f59f18fb-ae94-4f97-afd2-f84755767aca.vhd.bz2',
'b63d854a9560c013142567bbae8d98cf', 0, 'CentOS 5.3(64-bit) no GUI
(XenServer)', 'VHD', 12, 1, 1, 'XenServer', 1);
INSERT INTO `cloud`.`vm_template` (id, uuid, unique_name, name, public,
created, type, hvm, bits, account_id, url, checksum, display_text,
enable_password, format, guest_os_id, featured, cross_zones, hypervisor_type,
extractable)
- VALUES (4, UUID(), 'centos55-x86_64', 'CentOS 5.5(64-bit) no GUI (KVM)',
1, now(), 'BUILTIN', 0, 64, 1,
'http://download.cloudstack.org/releases/2.2.0/eec2209b-9875-3c8d-92be-c001bd8a0faf.qcow2.bz2',
'ed0e788280ff2912ea40f7f91ca7a249', 'CentOS 5.5(64-bit) no GUI (KVM)', 0,
'QCOW2', 112, 1, 1, 'KVM', 1);
+ VALUES (4, UUID(), 'debian13-x86_64-kvm', 'Debian 13 (64-bit) genericcloud
(KVM)', 1, now(), 'BUILTIN', 0, 64, 1,
'http://download.cloudstack.org/templates/debian-13-genericcloud-amd64/debian-13-genericcloud-amd64-20261026-2643-acs.qcow2',
'{SHA-512}bd95d28cc1e42e2f9d54c16c1015fee0204677dc6122c9a10bec8aaf0b3730b426f47e1c50e046f21add95f917344fe07089d791eb996fbd996257879022aafe',
'Debian 13 (64-bit) genericcloud (KVM)', 0, 'QCOW2', 184, 1, 1, 'KVM', 1);
Review Comment:
@weizhouapache and @harikrishna-patnala,
The new Debian 13 templates all reference `guest_os_id = 184`, but this ID
is currently mapped to `Debian GNU/Linux 7 (64-bit)` in `templates.sql`.
Could we add a Debian 13 guest OS entry and reference its ID in all three
template records (KVM, XenServer, and VMware)? Otherwise, CloudStack will
associate these templates with Debian 7 metadata.
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
