cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9489) When upgrading, Config.java new configuration are not updated.
Date Thu, 29 Sep 2016 17:22:20 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15533399#comment-15533399
] 

ASF GitHub Bot commented on CLOUDSTACK-9489:
--------------------------------------------

Github user PaulAngus commented on the issue:

    https://github.com/apache/cloudstack/pull/1684
  
    That isnt correct @bhaisaab.  commands.properties can be different on every mgmt server.
 Cloudstack would not know which version to use.
    
    
    
    ________________________________
    From: Rohit Yadav <notifications@github.com>
    Sent: 29 Sep 2016 18:16
    To: apache/cloudstack
    Cc: Paul Angus; Mention
    Subject: Re: [apache/cloudstack] CLOUDSTACK-9489: the new config vars that are added do
not goto DB if… (#1684)
    
    
    @jburwell<https://github.com/jburwell> when a fresh mgmt server is deployed for
upgrading an existing CloudStack environment, several files from /etc/cloudstack/management
are copied to the new server, especially the db.properties file. The commands.properties is
no different, in the past all such deployment (where in-place upgrades were avoided) copied
all these config files in /etc/cloudstack/management from old server to new server.
    
    Official docs only talk about in-place upgrades, our packaging system (post-install/upgrade
scripts) assume in-place upgrade as well; if someone's doing fresh mgmt server for upgrade,
they know what they are doing and its out-of-scope of what the project can support. At the
same time, we may add documentation for such kind of upgrades as well. The solution for this
problem is documentation and release/upgrade notes.
    
    —
    You are receiving this because you were mentioned.
    Reply to this email directly, view it on GitHub<https://github.com/apache/cloudstack/pull/1684#issuecomment-250531992>,
or mute the thread<https://github.com/notifications/unsubscribe-auth/AEll7O8ks5aJSv3zEVnq9pNqLuZonMjBks5qu_JsgaJpZM4KEn6g>.
    
    
    Paul Angus
    VP Technology
    s: +44 203 603 0540  |   m: +44 7711 418784  |   d: +44 203 468 5163
    e: paul.angus@shapeblue.com  |  w: www.shapeblue.com  |  t: @cloudyangus @shapeblue
    a: 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
    
    
    Shape Blue Ltd is a company incorporated in England &amp; Wales. ShapeBlue Services
India LLP is a company incorporated in India and is operated under license from Shape Blue
Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated
under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic
of South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is a registered
trademark.This email and any attachments to it may be confidential and are intended solely
for the use of the individual to whom it is addressed. Any views or opinions expressed are
solely those of the author and do not necessarily represent those of Shape Blue Ltd or related
companies. If you are not the intended recipient of this email, you must neither take any
action based upon its contents, nor copy or show it to anyone. Please contact the sender if
you believe you have received this email in error.
    
    Find out more about ShapeBlue and our range of CloudStack related services:
    IaaS Cloud Design &amp; Build    |    CSForge - rapid IaaS deployment framework
    CloudStack Consulting    |    CloudStack Software Engineering
    CloudStack Infrastructure Support    |    CloudStack Bootcamp Training Courses



> When upgrading, Config.java new configuration are not updated.
> --------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9489
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9489
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.6.2, 4.7.1, 4.8.0, 4.9.0
>            Reporter: Pierre-Luc Dion
>            Assignee: Pierre-Luc Dion
>            Priority: Blocker
>
> When Upgrading CloudStack, new configurations (Global Settings) defined in  {{server/src/com/cloud/configuration/Config.java}}
are not populated.
> This file changed in 4.5 and 4.6 and those configurations are not applied when upgrading
to post 4.6.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message