I am gona give a shot to CS 4.3
    Thanks

On 05/23/2014 09:54 AM, Pierre-Luc Dion wrote:
I think this release-note is not clear, cloudstack-agent run on KVM
hypervisor, following the installation steps does not install agent on the
mangement server (
http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/latest/installation.html
).

The 4.3 release note refer the agent upgrade to KVM host only.

I had some fun upgrading to 4.2.1 I found the upgrade instruction
confusing. Hopefully Upgrade instructions will get cleaner...


Rodrigo, any reason not upgrade to 4.3 instead?



Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
855-OK-CLOUD (855-652-5683) x1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_


On Thu, May 22, 2014 at 7:58 PM, Rafael Weingartner <
rafaelweingart...@gmail.com> wrote:

pois eh foi o que perguntei.
mas segundo o que ele falou o agente so precisa no host do kvm...


On Thu, May 22, 2014 at 8:47 PM, Rodrigo D. Lopez <
rodrigoduartelo...@gmail.com> wrote:

Entao o agent nao eh necessario... so em caso de ms usando kvm. Na pagina
diz o contrario mas ta bom.

Entao meu problema eh outro. Nao tem nada a ver com o agent.
Em 22/05/2014 20:45, "Rafael Weingartner" <rafaelweingart...@gmail.com>
escreveu:

Step 8.d says exactly the opposite:
"You will need to manually install the cloudstack-agent package:

$ sudo apt-get install cloudstack-agent

"
Taken from:


http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.1/html/Release_Notes/upgrade-instructions.html#upgrade-from-4.1-to-4.2.1
So, at the end, should or not the cloudstack-agent be installed in the
management server?


On Thu, May 22, 2014 at 7:19 PM, Pierre-Luc Dion <pd...@cloudops.com>
wrote:

You don't need the cloudstack-agent on the management server.
Cloudstack-agent is an agent that run on a KVM host.



Le jeudi 22 mai 2014, Rodrigo D. Lopez <rodrigoduartelo...@gmail.com
a
écrit :

     Hi, I have the following configuration:
     hosts running Xen-hypervisor 4.1 and XCP 1.6 over debian
wheezy.
     I tried to update my CS 4.1 to 4.2.1, but I got this error,
when
I
started the cloudstack-agent service

service cloudstack-agent start
  * Starting CloudStack Agent cloudstack-agent cat:
/var/run/cloudstack-agent.pid: No such file or directory
  * jsvc failed to start

     /var/log/cloudstack/agent/agent.log

2014-05-22 15:58:46,477 INFO  [cloud.agent.AgentShell] (main:null)
Agent
started
2014-05-22 15:58:46,478 INFO  [cloud.agent.AgentShell] (main:null)
Implementation Version is 4.2.1
2014-05-22 15:58:46,481 INFO  [cloud.agent.AgentShell] (main:null)
agent.properties found at /etc/cloudstack/agent/agent.properties
2014-05-22 15:58:46,482 INFO  [cloud.agent.AgentShell] (main:null)
Defaulting to using properties file for storage
2014-05-22 15:58:46,483 INFO  [cloud.agent.AgentShell] (main:null)
Defaulting to the constant time backoff algorithm
2014-05-22 15:58:46,485 INFO  [cloud.utils.LogUtils] (main:null)
log4j
configuration found at /etc/cloudstack/agent/log4j-cloud.xml
2014-05-22 15:58:46,579 INFO  [cloud.agent.Agent] (main:null) id is
2014-05-22 15:58:46,583 WARN  [cloud.resource.ServerResourceBase]
(main:null) Nics are not specified in properties file/db, will try
to
autodiscover
2014-05-22 15:58:46,588 INFO  [cloud.resource.ServerResourceBase]
(main:null) Designating private to be nic eth0
2014-05-22 15:58:46,596 INFO
[resource.virtualnetwork.VirtualRoutingResource]
(main:null) VirtualRoutingResource _scriptDir to use:
scripts/network/domr/kvm
2014-05-22 15:58:46,946 ERROR [cloud.agent.AgentShell] (main:null)
Unable
to start agent: Failed to get private nic name

     I do not understand why the cloudstack-agent is looking for KVM
scrips
if I am using Xen-hypervisor.
     Does anyone have any ideias of what is happening?


--

Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
855-OK-CLOUD (855-652-5683) x1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_



--
Rafael Weingärtner



--
Rafael Weingärtner


Reply via email to