cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9408) remove runtime references to
Date Sun, 12 Jun 2016 21:05:20 GMT


ASF GitHub Bot commented on CLOUDSTACK-9408:

Github user chiradeep commented on the issue: is owned by Citrix.
    I meant the this line in templates.sql
    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, '',
'ed0e788280ff2912ea40f7f91ca7a249', 'CentOS 5.5(64-bit) no GUI (KVM)', 0, 'QCOW2', 112, 1,
1, 'KVM', 1);		 +    VALUES (4, UUID(), 'centos55-x86_64', 'CentOS 5.5(64-bit) no GUI (KVM)',
1, now(), 'BUILTIN', 0, 64, 1, '',
'ed0e788280ff2912ea40f7f91ca7a249', 'CentOS 5.5(64-bit) no GUI (KVM)', 0, 'QCOW2', 112, 1,
1, 'KVM', 1);
    Is there a possibility of a better template (CentOS 6 or 7 for example). 
    I am not saying delete
from the repo. Older releases of cloudstack will want it. But for 4.9, we should be supplying
modern templates without known security issues (SHELLSHOCK for example).
    Another change required (perhaps another bug) is to update documentation for earlier releases.
The documentation should include
     - how to patch templates.sql to point to 

> remove runtime references to
> ------------------------------------------------------
>                 Key: CLOUDSTACK-9408
>                 URL:
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.5.2, 4.6.2, 4.7.1, 4.8.0, 4.9.0
>            Reporter: Daan Hoogland
>            Assignee: Daan Hoogland
>            Priority: Blocker
>             Fix For: 4.9.0
> As was bought and sold, We have no assurance and can give none to our users
as to wether downloads from that site will remain possible. This is to investigate what occurances
of can remain and which need to change, and change them.
> [~chiradeep][~widodh] I am assigning this to me but am going to ask for some further
> [~wstevens]I got no pushback so I am marking this as blocker for now.

This message was sent by Atlassian JIRA

View raw message