cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "France (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-4233) Upload NFSSR.py and others to XenServer hipervisor automatically
Date Wed, 25 Sep 2013 13:46:07 GMT

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

France commented on CLOUDSTACK-4233:
------------------------------------

I'm actually looking at file:
/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/xenserver60/patch
on CS 4.1.1.

To mee it seems this functionality is already in place.
Maybe we just need to call this each time a host is added?
                
> Upload NFSSR.py and others to XenServer hipervisor automatically
> ----------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4233
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4233
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: pre-4.0.0, 4.0.0, 4.0.1, 4.0.2, 4.1.0, 4.1.1
>         Environment: CentOS 6.4+
>            Reporter: France
>            Priority: Minor
>
> When installing XenServer 6.0.2 hotfixes, they can overwrite NFSSR.py and other manually
changed files.
> I see no reason, why we should not add a check, when a host is (re)connected, to check
md5sum of 
> /opt/xensource/sm/NFSSR.py
> /opt/xensource/bin/setupxenserver.sh
> /opt/xensource/bin/make_migratable.sh
> /opt/xensource/bin/cloud-clean-vlan.sh
> and if it's different than the one on management server, upload fixed version it to hipervisor.
:-)
> I had to learn to update that by hand the hard way quite some time ago, so i now regularly
check after applying hotfixes. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message