Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Sat, 25 Jan 2014 02:29:39 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12687285.1388796094756.10419.1390616979024@arcas>
In-Reply-To: <JIRA.12687285.1388796094756@arcas>
References: <JIRA.12687285.1388796094756@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-5779) Consolidate all the VR
 commands execution to one resource
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

ASF subversion and git services commented on CLOUDSTACK-5779:
-------------------------------------------------------------

Commit 2d3022594c94b0359ddced70907c8a95014eec96 in branch refs/heads/master from [~yasker]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2d30225 ]

CLOUDSTACK-5779: Generalize calling to execute or create file for Vmware


> Consolidate all the VR commands execution to one resource
> ---------------------------------------------------------
>
>                 Key: CLOUDSTACK-5779
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5779
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Sheng Yang
>            Assignee: Sheng Yang
>            Priority: Critical
>             Fix For: 4.4.0
>
>
> Currently when anyone add one command to VR(which happened very frequently these days), they need to modify every hypervisor resources to accommodate the new command, which is really inconvenient as well as bug prone, since e.g. the parameters formation would be duplicate across the hypervisors.
> This improvement would make all VR commands to be executed by only one resource, and in the future, any new command/improvement or bug fixes to VR resource would only need to be done once in the VR resource. 
> This would be done through:
> 1. Use routeProxy script for all VR commands, no more standalone script for each VR scripts in the host. All VR command scripts would be moved to /opt/cloud/bin for this purpose as well.
> 2. Every hypervisor would provide an executor to VR resource, to execute the command in giving hypervisor.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)