incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kelven Yang <kelven.y...@citrix.com>
Subject RE: More packaging questions
Date Tue, 24 Apr 2012 17:24:14 GMT
>> Do I understand it correctly that everything that is related to 
console-proxy should not be packaged?

Yes, you are right, console proxy should not be packaged, at one time, console proxy is deployed
along with KVM agent, and this is the legacy from that. This feature has been depreciated.

Kelven

-----Original Message-----
From: Robert Schweikert [mailto:rjschwei@suse.com] 
Sent: Tuesday, April 24, 2012 10:14 AM
To: cloudstack-dev@incubator.apache.org
Subject: More packaging questions

Hi,

Sorry for continuing to flood the list with more questions about this.

Do I understand it correctly that everything that is related to 
console-proxy should not be packaged?

This would include the /usr/lib64/cloud/console-proxy directory as well 
as the symlinks in /usr/lib64/cloud/agent that point to nodes in 
/usr/lib64/cloud/console-proxy, correct?

/usr/share/java/cloud-console-proxy.jar should therefore also not be 
packaged?

In what packages should /usr/bin/cloud-daemonize live?

Thanks,
Robert

-- 
Robert Schweikert                           MAY THE SOURCE BE WITH YOU
SUSE-IBM Software Integration Center                   LINUX
Tech Lead
rjschwei@suse.com
rschweik@ca.ibm.com
781-464-8147

Mime
View raw message