Re: Cloudstack 4.7 password reset issue.

2016-04-04 Thread Erik Weber
On Mon, Apr 4, 2016 at 9:17 PM, Richard Klein (RSI) 
wrote:

> Thanks for the reply and sorry for the delay.  You know how it is on
> Monday's.
>
> I checked the VR password file as suggested after the password reset via
> the GUI but before powering on the VM.  I did see the password reset there
> as expected.  I powered on the VM and the password was reset as expected.
> The test VM is built from a CentOS7 template with password enabled.  I
> checked the /var/log/messages and you can see from the client perspective
> the change went as expected.  Below is "snippet1" from the message log on
> the VM (there are no SSH key so it fails as expected):
>
>
This is your first VM snippet:


> Apr  4 13:45:35 rsi-test-c7 systemd: Starting LSB:
> cloud-set-guest-sshkey...
> Apr  4 13:45:35 rsi-test-c7 systemd: Starting LSB:
> cloud-set-guest-password...
> Apr  4 13:45:35 rsi-test-c7 cloud: Unable to determine the password
> server, falling back to data-server
> Apr  4 13:45:35 rsi-test-c7 cloud: Could not find ssh key server IP in
> /var/lib/dhclient/dhclient.leases
> Apr  4 13:45:36 rsi-test-c7 cloud: Unable to determine the password
> server, falling back to data-server
> Apr  4 13:45:36 rsi-test-c7 cloud: Sending request to password server at
> data-server
> Apr  4 13:45:36 rsi-test-c7 cloud: Sending request to ssh key server at
> data-server
> Apr  4 13:45:36 rsi-test-c7 cloud: Got response from server at data-server
> Apr  4 13:45:36 rsi-test-c7 cloud: Did not receive any keys from any server
> Apr  4 13:45:36 rsi-test-c7 systemd: cloud-set-guest-sshkey.service:
> control process exited, code=exited status=1
> Apr  4 13:45:36 rsi-test-c7 systemd: Failed to start LSB:
> cloud-set-guest-sshkey.
> Apr  4 13:45:36 rsi-test-c7 systemd: Unit cloud-set-guest-sshkey.service
> entered failed state.
> Apr  4 13:45:36 rsi-test-c7 systemd: cloud-set-guest-sshkey.service failed.
> Apr  4 13:45:36 rsi-test-c7 cloud: Got response from server at data-server
> Apr  4 13:45:36 rsi-test-c7 cloud: VM got a valid password from server at
> data-server
> Apr  4 13:45:36 rsi-test-c7 cloud: Changing password for user root
> Apr  4 13:45:36 rsi-test-c7 cloud: Sending acknowledgment to password
> server at data-server
> Apr  4 13:45:36 rsi-test-c7 cloud-set-guest-password: saved_password
> Apr  4 13:45:36 rsi-test-c7 systemd: Started LSB: cloud-set-guest-password.
> Apr  4 13:45:36 rsi-test-c7 systemd: Starting Initial cloud-init job
> (metadata service crawler)...
> Apr  4 13:45:37 rsi-test-c7 systemd: Started Initial cloud-init job
> (metadata service crawler).
> Apr  4 13:45:37 rsi-test-c7 systemd: Starting Apply the settings specified
> in cloud-config...
> Apr  4 13:45:37 rsi-test-c7 systemd: Started Apply the settings specified
> in cloud-config.
> Apr  4 13:45:37 rsi-test-c7 systemd: Starting Execute cloud user/final
> scripts...
> Apr  4 13:45:37 rsi-test-c7 systemd: Started Execute cloud user/final
> scripts.
>
> I checked the password file on the VR and it was empty now.  I then
> manually reset the password on the VM console only (not CS GUI) and
> performed an OS reboot from the console.  I could log in with the password
> I change with the console.  Below is the system messages "snippet2":
>
>
This is your second VM snippet, happening before snippet1


> Apr  4 13:36:27 rsi-test-c7 systemd: Starting LSB:
> cloud-set-guest-sshkey...
> Apr  4 13:36:27 rsi-test-c7 systemd: Starting LSB:
> cloud-set-guest-password...
> Apr  4 13:36:27 rsi-test-c7 cloud: Could not find ssh key server IP in
> /var/lib/dhclient/dhclient.leases
>

Do you have such file, or is there a configuration error in the
cloud-set-guest-password?
You seem to be running centos7, and that wasn't around when these scripts
where made and thus might have to be modified for them to work.


> Apr  4 13:36:27 rsi-test-c7 cloud: Unable to determine the password
> server, falling back to data-server
> Apr  4 13:36:27 rsi-test-c7 cloud: Unable to determine the password
> server, falling back to data-server
> Apr  4 13:36:27 rsi-test-c7 cloud: Sending request to password server at
> data-server
> Apr  4 13:36:27 rsi-test-c7 cloud: Sending request to ssh key server at
> data-server
> Apr  4 13:36:27 rsi-test-c7 cloud: Got response from server at data-server
> Apr  4 13:36:27 rsi-test-c7 cloud: Did not receive any keys from any server
> Apr  4 13:36:27 rsi-test-c7 systemd: cloud-set-guest-sshkey.service:
> control process exited, code=exited status=1
> Apr  4 13:36:27 rsi-test-c7 systemd: Failed to start LSB:
> cloud-set-guest-sshkey.
> Apr  4 13:36:27 rsi-test-c7 systemd: Unit cloud-set-guest-sshkey.service
> entered failed state.
> Apr  4 13:36:27 rsi-test-c7 systemd: cloud-set-guest-sshkey.service failed.
> Apr  4 13:36:27 rsi-test-c7 cloud: Got response from server at data-server
> Apr  4 13:36:27 rsi-test-c7 cloud: VM has already saved a password from
> the password server at data-server
> Apr  4 13:36:27 rsi-test-c7 cloud: Did not need to change 

RE: Lock New VM provision on specific HOST

2016-04-04 Thread Sanjeev Neelarapu
Hi Cristian,

As you mentioned, you can avoid host from allocation for new vm deployments by 
disabling it and it would not affect the existing vms.

Best Regards,
Sanjeev N
Chief Product Engineer, Accelerite
Off: +91 40 6722 9368 | EMail: sanjeev.neelar...@accelerite.com



-Original Message-
From: Cristian Ciobanu [mailto:cristian.c@istream.today]
Sent: Monday, April 04, 2016 3:14 PM
To: users@cloudstack.apache.org
Subject: Lock New VM provision on specific HOST

  I have a question regarding provisioning limit, what will be the best 
method to lock provisioning on a specific host, for example I have 4 VM's on 
one HOST, but I don't want to allocate new VM's on it even if I have free 
resources on it. can this to be done by doing "disable host" ? will this affect 
in some ways the current allocated VM's ?





  Thank you !



Regards,

Cristian






DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Accelerite, a Persistent Systems business. It is intended only for 
the use of the individual or entity to which it is addressed. If you are not 
the intended recipient, you are not authorized to read, retain, copy, print, 
distribute or use this message. If you have received this communication in 
error, please notify the sender and delete all copies of this message. 
Accelerite, a Persistent Systems business does not accept any liability for 
virus infected mails.


RE: URGENT - CloudStack agent not able to connect to management server

2016-04-04 Thread Sanjeev Neelarapu
Adding additional management server would definitely help.

Best Regards,
Sanjeev N
Chief Product Engineer, Accelerite
Off: +91 40 6722 9368 | EMail: sanjeev.neelar...@accelerite.com 


-Original Message-
From: Indra Pramana [mailto:in...@sg.or.id] 
Sent: Sunday, April 03, 2016 5:14 PM
To: users@cloudstack.apache.org
Subject: Re: URGENT - CloudStack agent not able to connect to management server

Hi Lucian,

Good day to you, and thank you for your reply. Apologise for the delay in my 
reply.

Yes, I can confirm that we can access the host and port specified. Based on the 
logs, the host can connect to the management server but there's no follow-up 
logs which usually come after it's connected. Eventually, we could only connect 
back the host after we rebooted it, which means sacrificing all the VMs which 
were still up and running during the disconnection.

At the time when the first hypervisor was disconnected, the CloudStack 
management servers were very busy handling the disconnections, trying to fence 
the hosts and initiate HA for all the affected VMs, based on the logs. Could 
this have put a strain on the management server, causing it to disconnect all 
the remaining hosts? Will adding new management server be able to resolve the 
problem?

Any advice is appreciated.

Looking forward to your reply, thank you.

Cheers.

On Thu, Mar 31, 2016 at 5:28 PM, Nux!  wrote:

> Hello,
>
> Are you sure you can connect from the hypervisors to the 
> cloudstack-management on the host and port specified in the 
> agent.properties?
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> - Original Message -
> > From: "Indra Pramana" 
> > To: users@cloudstack.apache.org
> > Sent: Thursday, 31 March, 2016 03:14:59
> > Subject: URGENT - CloudStack agent not able to connect to management
> server
>
> > Dear all,
> >
> > We are using CloudStack 4.2.0, KVM hypervisor and Ceph RBD storage. 
> > All
> our
> > agents got disconnected from the management server and unable to 
> > connect again, despite rebooting the management server and stopping 
> > and
> restarting
> > the cloudstack-agent many times.
> >
> > We even tried to physically reboot a hypervisor host (sacrificing 
> > all the running VMs inside) to see if it can reconnect after 
> > boot-up, and it's
> not
> > able to reconnect (keep on "Connecting" state). Here's the excerpts 
> > from the logs:
> >
> > 
> > 2016-03-31 10:07:49,346 DEBUG [cloud.agent.Agent] (UgentTask-5:null) 
> > Sending ping: Seq 0-11:  { Cmd , MgmtId: -1, via: 0, Ver: v1, Flags: 
> > 11,
> >
> [{"com.cloud.agent.api.PingRoutingWithNwGroupsCommand":{"newGroupState
> s":{},"newStates":{},"_gatewayAccessible":true,"_vnetAccessible":true,
> "hostType":"Routing","hostId":0,"wait":0}}]
> > }
> > 2016-03-31 10:07:49,395 DEBUG [cloud.agent.Agent] 
> > (Agent-Handler-2:null) Received response: Seq 0-11:  { Ans: , 
> > MgmtId: 161342671900, via: 75,
> Ver:
> > v1, Flags: 100010,
> >
> [{"com.cloud.agent.api.PingAnswer":{"_command":{"hostType":"Routing","
> hostId":0,"wait":0},"result":true,"wait":0}}]
> > }
> > 2016-03-31 10:08:49,271 DEBUG 
> > [kvm.resource.LibvirtComputingResource]
> > (UgentTask-5:null) Executing:
> > /usr/share/cloudstack-common/scripts/vm/network/security_group.py
> > get_rule_logs_for_vms
> > 2016-03-31 10:08:49,350 DEBUG 
> > [kvm.resource.LibvirtComputingResource]
> > (UgentTask-5:null) Execution is successful.
> > 2016-03-31 10:08:49,353 DEBUG [cloud.agent.Agent] (UgentTask-5:null) 
> > Sending ping: Seq 0-12:  { Cmd , MgmtId: -1, via: 0, Ver: v1, Flags: 
> > 11,
> >
> [{"com.cloud.agent.api.PingRoutingWithNwGroupsCommand":{"newGroupState
> s":{},"newStates":{},"_gatewayAccessible":true,"_vnetAccessible":true,
> "hostType":"Routing","hostId":0,"wait":0}}]
> > }
> > 2016-03-31 10:08:49,406 DEBUG [cloud.agent.Agent] 
> > (Agent-Handler-3:null) Received response: Seq 0-12:  { Ans: , 
> > MgmtId: 161342671900, via: 75,
> Ver:
> > v1, Flags: 100010,
> >
> [{"com.cloud.agent.api.PingAnswer":{"_command":{"hostType":"Routing","
> hostId":0,"wait":0},"result":true,"wait":0}}]
> > }
> > 2016-03-31 10:09:49,272 DEBUG 
> > [kvm.resource.LibvirtComputingResource]
> > (UgentTask-5:null) Executing:
> > /usr/share/cloudstack-common/scripts/vm/network/security_group.py
> > get_rule_logs_for_vms
> > 2016-03-31 10:09:49,345 DEBUG 
> > [kvm.resource.LibvirtComputingResource]
> > (UgentTask-5:null) Execution is successful.
> > 2016-03-31 10:09:49,347 DEBUG [cloud.agent.Agent] (UgentTask-5:null) 
> > Sending ping: Seq 0-13:  { Cmd , MgmtId: -1, via: 0, Ver: v1, Flags: 
> > 11,
> >
> [{"com.cloud.agent.api.PingRoutingWithNwGroupsCommand":{"newGroupState
> s":{},"newStates":{},"_gatewayAccessible":true,"_vnetAccessible":true,
> "hostType":"Routing","hostId":0,"wait":0}}]
> > }
> > 2016-03-31 10:09:49,398 DEBUG [cloud.agent.Agent] 
> > (Agent-Handler-4:null) Received response: Seq 0-13:  { Ans: , 
> > MgmtId: 

Re: Cloudstack 4.7 password reset issue.

2016-04-04 Thread Shweta Agarwal
Hi Richard,
This looks like a bug to me. The password should be pushed only first time of  
VM start and only after User reset password of VM via CS.

Thanks
Shweta
Principal Product Engineer, CloudPlatform
Accelerite


From: Richard Klein (RSI) 
Sent: Tuesday, April 5, 2016 12:47 AM
To: users@cloudstack.apache.org
Subject: RE: Cloudstack 4.7 password reset issue.

Thanks for the reply and sorry for the delay.  You know how it is on Monday's.

I checked the VR password file as suggested after the password reset via the 
GUI but before powering on the VM.  I did see the password reset there as 
expected.  I powered on the VM and the password was reset as expected.  The 
test VM is built from a CentOS7 template with password enabled.  I checked the 
/var/log/messages and you can see from the client perspective the change went 
as expected.  Below is "snippet1" from the message log on the VM (there are no 
SSH key so it fails as expected):

Apr  4 13:45:35 rsi-test-c7 systemd: Starting LSB: cloud-set-guest-sshkey...
Apr  4 13:45:35 rsi-test-c7 systemd: Starting LSB: cloud-set-guest-password...
Apr  4 13:45:35 rsi-test-c7 cloud: Unable to determine the password server, 
falling back to data-server
Apr  4 13:45:35 rsi-test-c7 cloud: Could not find ssh key server IP in 
/var/lib/dhclient/dhclient.leases
Apr  4 13:45:36 rsi-test-c7 cloud: Unable to determine the password server, 
falling back to data-server
Apr  4 13:45:36 rsi-test-c7 cloud: Sending request to password server at 
data-server
Apr  4 13:45:36 rsi-test-c7 cloud: Sending request to ssh key server at 
data-server
Apr  4 13:45:36 rsi-test-c7 cloud: Got response from server at data-server
Apr  4 13:45:36 rsi-test-c7 cloud: Did not receive any keys from any server
Apr  4 13:45:36 rsi-test-c7 systemd: cloud-set-guest-sshkey.service: control 
process exited, code=exited status=1
Apr  4 13:45:36 rsi-test-c7 systemd: Failed to start LSB: 
cloud-set-guest-sshkey.
Apr  4 13:45:36 rsi-test-c7 systemd: Unit cloud-set-guest-sshkey.service 
entered failed state.
Apr  4 13:45:36 rsi-test-c7 systemd: cloud-set-guest-sshkey.service failed.
Apr  4 13:45:36 rsi-test-c7 cloud: Got response from server at data-server
Apr  4 13:45:36 rsi-test-c7 cloud: VM got a valid password from server at 
data-server
Apr  4 13:45:36 rsi-test-c7 cloud: Changing password for user root
Apr  4 13:45:36 rsi-test-c7 cloud: Sending acknowledgment to password server at 
data-server
Apr  4 13:45:36 rsi-test-c7 cloud-set-guest-password: saved_password
Apr  4 13:45:36 rsi-test-c7 systemd: Started LSB: cloud-set-guest-password.
Apr  4 13:45:36 rsi-test-c7 systemd: Starting Initial cloud-init job (metadata 
service crawler)...
Apr  4 13:45:37 rsi-test-c7 systemd: Started Initial cloud-init job (metadata 
service crawler).
Apr  4 13:45:37 rsi-test-c7 systemd: Starting Apply the settings specified in 
cloud-config...
Apr  4 13:45:37 rsi-test-c7 systemd: Started Apply the settings specified in 
cloud-config.
Apr  4 13:45:37 rsi-test-c7 systemd: Starting Execute cloud user/final 
scripts...
Apr  4 13:45:37 rsi-test-c7 systemd: Started Execute cloud user/final scripts.

I checked the password file on the VR and it was empty now.  I then manually 
reset the password on the VM console only (not CS GUI) and performed an OS 
reboot from the console.  I could log in with the password I change with the 
console.  Below is the system messages "snippet2":

Apr  4 13:36:27 rsi-test-c7 systemd: Starting LSB: cloud-set-guest-sshkey...
Apr  4 13:36:27 rsi-test-c7 systemd: Starting LSB: cloud-set-guest-password...
Apr  4 13:36:27 rsi-test-c7 cloud: Could not find ssh key server IP in 
/var/lib/dhclient/dhclient.leases
Apr  4 13:36:27 rsi-test-c7 cloud: Unable to determine the password server, 
falling back to data-server
Apr  4 13:36:27 rsi-test-c7 cloud: Unable to determine the password server, 
falling back to data-server
Apr  4 13:36:27 rsi-test-c7 cloud: Sending request to password server at 
data-server
Apr  4 13:36:27 rsi-test-c7 cloud: Sending request to ssh key server at 
data-server
Apr  4 13:36:27 rsi-test-c7 cloud: Got response from server at data-server
Apr  4 13:36:27 rsi-test-c7 cloud: Did not receive any keys from any server
Apr  4 13:36:27 rsi-test-c7 systemd: cloud-set-guest-sshkey.service: control 
process exited, code=exited status=1
Apr  4 13:36:27 rsi-test-c7 systemd: Failed to start LSB: 
cloud-set-guest-sshkey.
Apr  4 13:36:27 rsi-test-c7 systemd: Unit cloud-set-guest-sshkey.service 
entered failed state.
Apr  4 13:36:27 rsi-test-c7 systemd: cloud-set-guest-sshkey.service failed.
Apr  4 13:36:27 rsi-test-c7 cloud: Got response from server at data-server
Apr  4 13:36:27 rsi-test-c7 cloud: VM has already saved a password from the 
password server at data-server
Apr  4 13:36:27 rsi-test-c7 cloud: Did not need to change password.
Apr  4 13:36:27 rsi-test-c7 systemd: Started LSB: cloud-set-guest-password.

I then powered off the VM and 

Re: REMOTE VPN CONNECTION FAILED IN UPGRADED CLOUDSTACK FROM 4.3.1 TO 4.71

2016-04-04 Thread Pierre-Luc Dion
We have a PR on fithub, or about to have one to fix this.

You have start both service on the VR has  Sanjeev said?

If both services are running, look at auth.log, could also be related to
the time on the vr? Vpn might be time sensitive so client machine and VR
might need to have time in sync.
On Apr 1, 2016 12:56 AM, "kotipalli venkatesh" 
wrote:

> Hi Sanjeev,
>
> we have already executed above commands and rebooted VR as well but no
> luck.
>
> If anything is there let me know.
>
> Regards,
> Venkatesh.k
>
> On Fri, Apr 1, 2016 at 10:17 AM, Sanjeev Neelarapu <
> sanjeev.neelar...@accelerite.com> wrote:
>
> > Hi Venkatesh,
> >
> > For starting ipsec service use "service ipsecd restart" command ,
> > similarly l2tp service.
> >
> > Best Regards,
> > Sanjeev N
> > Chief Product Engineer, Accelerite
> > Off: +91 40 6722 9368 | EMail: sanjeev.neelar...@accelerite.com
> >
> >
> > -Original Message-
> > From: kotipalli venkatesh [mailto:venkateshcloudt...@gmail.com]
> > Sent: Thursday, March 31, 2016 1:55 PM
> > To: users@cloudstack.apache.org
> > Subject: Re: REMOTE VPN CONNECTION FAILED IN UPGRADED CLOUDSTACK FROM
> > 4.3.1 TO 4.71
> >
> > Hi Pierre-LucDion,
> >
> > As per above mail conversation RemoteVPN is bug right so,Your giving some
> > hint that is login to the VR and which command fire? please share the
> > command.
> >
> > And also how to start the ipsec and l2tp services in VR
> >
> > Regards,
> > Venkatesh.k
> >
> >
> > On Thu, Mar 31, 2016 at 12:07 PM, Venkat Boggarapu  >
> > wrote:
> >
> > > Hi Glen,
> > >
> > > I am posting the auth.log file can you please check and help me
> > > regarding this issue.
> > >
> > > Mar 31 05:58:32 r-17-VM sshd[5292]: pam_unix(sshd:session): session
> > > closed for user root Mar 31 05:58:32 r-17-VM sshd[5295]: Accepted
> > > publickey for root from
> > > 169.254.0.1 port 35569 ssh2
> > > Mar 31 05:58:32 r-17-VM sshd[5295]: pam_unix(sshd:session): session
> > > opened for user root by (uid=0) Mar 31 05:58:33 r-17-VM sshd[5295]:
> > > pam_unix(sshd:session): session closed for user root Mar 31 05:58:33
> > > r-17-VM sshd[5377]: Accepted publickey for root from
> > > 169.254.0.1 port 35570 ssh2
> > > Mar 31 05:58:33 r-17-VM sshd[5377]: pam_unix(sshd:session): session
> > > opened for user root by (uid=0) Mar 31 05:58:33 r-17-VM sshd[5377]:
> > > pam_unix(sshd:session): session closed for user root Mar 31 05:58:34
> > > r-17-VM sshd[5380]: Accepted publickey for root from
> > > 169.254.0.1 port 35571 ssh2
> > > Mar 31 05:58:34 r-17-VM sshd[5380]: pam_unix(sshd:session): session
> > > opened for user root by (uid=0) Mar 31 05:58:34 r-17-VM sshd[5380]:
> > > pam_unix(sshd:session): session closed for user root Mar 31 05:58:53
> > > r-17-VM sshd[5613]: Accepted publickey for root from
> > > 169.254.0.1 port 35573 ssh2
> > > Mar 31 05:58:53 r-17-VM sshd[5613]: pam_unix(sshd:session): session
> > > opened for user root by (uid=0) Mar 31 05:58:53 r-17-VM sshd[5613]:
> > > pam_unix(sshd:session): session closed for user root Mar 31 05:58:54
> > > r-17-VM sshd[5616]: Accepted publickey for root from
> > > 169.254.0.1 port 35574 ssh2
> > > Mar 31 05:58:54 r-17-VM sshd[5616]: pam_unix(sshd:session): session
> > > opened for user root by (uid=0) Mar 31 05:58:54 r-17-VM sshd[5616]:
> > > pam_unix(sshd:session): session closed for user root
> > >
> > > Regards,
> > > Venkat Boggarapu
> > >
> > > -Original Message-
> > > From: Glenn Wagner [mailto:glenn.wag...@shapeblue.com]
> > > Sent: Wednesday, March 30, 2016 8:41 PM
> > > To: users@cloudstack.apache.org
> > > Subject: RE: REMOTE VPN CONNECTION FAILED IN UPGRADED CLOUDSTACK FROM
> > > 4.3.1 TO 4.71
> > >
> > > Hi
> > >
> > > Could you post the auth.log file of the Virtual Router you are trying
> > > to connect too
> > >
> > > Glenn
> > >
> > >
> > > Regards,
> > >
> > > Glenn Wagner
> > >
> > > glenn.wag...@shapeblue.com
> > > www.shapeblue.com
> > > 2nd Floor, Oudehuis Centre, 122 Main Rd, Somerset West, Cape Town
> > > 7130South Africa @shapeblue
> > >
> > > -Original Message-
> > > From: Venkat Boggarapu [mailto:venka...@axiomio.com]
> > > Sent: Wednesday, 30 March 2016 3:02 PM
> > > To: users@cloudstack.apache.org
> > > Subject: RE: REMOTE VPN CONNECTION FAILED IN UPGRADED CLOUDSTACK FROM
> > > 4.3.1 TO 4.71
> > >
> > > Hi Glen,
> > >
> > > We done upgraded all the virtual routers after the cloudstack upgrade.
> > >
> > > Thanks,
> > > Venkat Boggarapu
> > >
> > > -Original Message-
> > > From: Glenn Wagner [mailto:glenn.wag...@shapeblue.com]
> > > Sent: Wednesday, March 30, 2016 6:24 PM
> > > To: users@cloudstack.apache.org
> > > Subject: RE: REMOTE VPN CONNECTION FAILED IN UPGRADED CLOUDSTACK FROM
> > > 4.3.1 TO 4.71
> > >
> > > Hi,
> > >
> > > Did you upgrade the virtual routers after the upgrade too 4.7.1.
> > >
> > > Regards
> > > Glenn
> > >
> > >
> > >
> > > Regards,
> > >
> > > Glenn Wagner
> > >
> > > glenn.wag...@shapeblue.com
> 

RE: Cloudstack 4.7 password reset issue.

2016-04-04 Thread Richard Klein (RSI)
Thanks for the reply and sorry for the delay.  You know how it is on Monday's.

I checked the VR password file as suggested after the password reset via the 
GUI but before powering on the VM.  I did see the password reset there as 
expected.  I powered on the VM and the password was reset as expected.  The 
test VM is built from a CentOS7 template with password enabled.  I checked the 
/var/log/messages and you can see from the client perspective the change went 
as expected.  Below is "snippet1" from the message log on the VM (there are no 
SSH key so it fails as expected):

Apr  4 13:45:35 rsi-test-c7 systemd: Starting LSB: cloud-set-guest-sshkey...
Apr  4 13:45:35 rsi-test-c7 systemd: Starting LSB: cloud-set-guest-password...
Apr  4 13:45:35 rsi-test-c7 cloud: Unable to determine the password server, 
falling back to data-server
Apr  4 13:45:35 rsi-test-c7 cloud: Could not find ssh key server IP in 
/var/lib/dhclient/dhclient.leases
Apr  4 13:45:36 rsi-test-c7 cloud: Unable to determine the password server, 
falling back to data-server
Apr  4 13:45:36 rsi-test-c7 cloud: Sending request to password server at 
data-server
Apr  4 13:45:36 rsi-test-c7 cloud: Sending request to ssh key server at 
data-server
Apr  4 13:45:36 rsi-test-c7 cloud: Got response from server at data-server
Apr  4 13:45:36 rsi-test-c7 cloud: Did not receive any keys from any server
Apr  4 13:45:36 rsi-test-c7 systemd: cloud-set-guest-sshkey.service: control 
process exited, code=exited status=1
Apr  4 13:45:36 rsi-test-c7 systemd: Failed to start LSB: 
cloud-set-guest-sshkey.
Apr  4 13:45:36 rsi-test-c7 systemd: Unit cloud-set-guest-sshkey.service 
entered failed state.
Apr  4 13:45:36 rsi-test-c7 systemd: cloud-set-guest-sshkey.service failed.
Apr  4 13:45:36 rsi-test-c7 cloud: Got response from server at data-server
Apr  4 13:45:36 rsi-test-c7 cloud: VM got a valid password from server at 
data-server
Apr  4 13:45:36 rsi-test-c7 cloud: Changing password for user root
Apr  4 13:45:36 rsi-test-c7 cloud: Sending acknowledgment to password server at 
data-server
Apr  4 13:45:36 rsi-test-c7 cloud-set-guest-password: saved_password
Apr  4 13:45:36 rsi-test-c7 systemd: Started LSB: cloud-set-guest-password.
Apr  4 13:45:36 rsi-test-c7 systemd: Starting Initial cloud-init job (metadata 
service crawler)...
Apr  4 13:45:37 rsi-test-c7 systemd: Started Initial cloud-init job (metadata 
service crawler).
Apr  4 13:45:37 rsi-test-c7 systemd: Starting Apply the settings specified in 
cloud-config...
Apr  4 13:45:37 rsi-test-c7 systemd: Started Apply the settings specified in 
cloud-config.
Apr  4 13:45:37 rsi-test-c7 systemd: Starting Execute cloud user/final 
scripts...
Apr  4 13:45:37 rsi-test-c7 systemd: Started Execute cloud user/final scripts.

I checked the password file on the VR and it was empty now.  I then manually 
reset the password on the VM console only (not CS GUI) and performed an OS 
reboot from the console.  I could log in with the password I change with the 
console.  Below is the system messages "snippet2":

Apr  4 13:36:27 rsi-test-c7 systemd: Starting LSB: cloud-set-guest-sshkey...
Apr  4 13:36:27 rsi-test-c7 systemd: Starting LSB: cloud-set-guest-password...
Apr  4 13:36:27 rsi-test-c7 cloud: Could not find ssh key server IP in 
/var/lib/dhclient/dhclient.leases
Apr  4 13:36:27 rsi-test-c7 cloud: Unable to determine the password server, 
falling back to data-server
Apr  4 13:36:27 rsi-test-c7 cloud: Unable to determine the password server, 
falling back to data-server
Apr  4 13:36:27 rsi-test-c7 cloud: Sending request to password server at 
data-server
Apr  4 13:36:27 rsi-test-c7 cloud: Sending request to ssh key server at 
data-server
Apr  4 13:36:27 rsi-test-c7 cloud: Got response from server at data-server
Apr  4 13:36:27 rsi-test-c7 cloud: Did not receive any keys from any server
Apr  4 13:36:27 rsi-test-c7 systemd: cloud-set-guest-sshkey.service: control 
process exited, code=exited status=1
Apr  4 13:36:27 rsi-test-c7 systemd: Failed to start LSB: 
cloud-set-guest-sshkey.
Apr  4 13:36:27 rsi-test-c7 systemd: Unit cloud-set-guest-sshkey.service 
entered failed state.
Apr  4 13:36:27 rsi-test-c7 systemd: cloud-set-guest-sshkey.service failed.
Apr  4 13:36:27 rsi-test-c7 cloud: Got response from server at data-server
Apr  4 13:36:27 rsi-test-c7 cloud: VM has already saved a password from the 
password server at data-server
Apr  4 13:36:27 rsi-test-c7 cloud: Did not need to change password.
Apr  4 13:36:27 rsi-test-c7 systemd: Started LSB: cloud-set-guest-password.

I then powered off the VM and powered it back on without changing any 
passwords.  The password was set to the last change password via the GUI.  The 
logs behave as if the password reset was performed from the GUI again 
(snippet1).  I checked the password file on the VR and it was empty.  I also 
monitored the VR /var/log/cloud.log messages and discovered something 
interesting.  As expected there was a flurry of activity but the following 2 
messages 

AW: Storage decommissioning

2016-04-04 Thread S . Brüseke - proIO GmbH
Hi,

what do you mean? XenServer is taking care of the metadata backup if you 
enabled it. As far as I know XenServer will update the metadata.

Mit freundlichen Grüßen / With kind regards,

Swen


-Ursprüngliche Nachricht-
Von: Alessandro Caviglione [mailto:c.alessan...@gmail.com] 
Gesendet: Sonntag, 3. April 2016 23:20
An: users@cloudstack.apache.org
Betreff: Re: Storage decommissioning

Ok guys... we're about to finish the migration of primary storage... but I've a 
question.
Since we've moved all the Instance's volume (ROOT and DATA) through ACS (4.5), 
should we consider anything about VMs metadata?
We're running XS 6.2 SP1.

Moving the volume will move also metadata?

Regards.

On Thu, Mar 24, 2016 at 1:13 PM, Alessandro Caviglione < 
c.alessan...@gmail.com> wrote:

> Thanks for your feedback, I am now a bit more relaxed! :-
>
> On Thu, Mar 24, 2016 at 12:07 PM, S. Brüseke - proIO GmbH < 
> s.brues...@proio.com> wrote:
>
>> Don't hesitate to ask if you have more question. We did the exact 
>> same job. We migrated primary and secondary storage. Secondary was 
>> horror, primary is not a problem at all. ;-)
>>
>>
>>
>> Mit freundlichen Grüßen / With kind regards,
>>
>>
>>
>> Swen
>>
>>
>>
>> *Von:* Alessandro Caviglione [mailto:c.alessan...@gmail.com]
>> *Gesendet:* Donnerstag, 24. März 2016 12:06
>> *An:* S. Brüseke - proIO GmbH
>> *Betreff:* Re: Storage decommissioning
>>
>>
>>
>> Ok, great!
>>
>> I'll inform you about the operations... :)
>>
>>
>>
>> On Thu, Mar 24, 2016 at 11:45 AM, S. Brüseke - proIO GmbH < 
>> s.brues...@proio.com> wrote:
>>
>> You do not need to move them. If you put the primary storage they are 
>> located into maintenance than CS will recreate VRs and System VMs on 
>> another primary storage.
>> This will include a short downtime for each VR, but CS will do this 
>> step by step; VR after VR
>>
>> Mit freundlichen Grüßen / With kind regards,
>>
>> Swen
>>
>>
>> -Ursprüngliche Nachricht-
>> Von: Alessandro Caviglione [mailto:c.alessan...@gmail.com]
>> Gesendet: Donnerstag, 24. März 2016 11:15
>> An: users@cloudstack.apache.org
>> Betreff: Re: Storage decommissioning
>>
>>
>> Hi,
>> thank you for your suggests... I'm going to move VMs ROOT and DATA to 
>> the new storage using CS GUI.
>> Our environment is CS 4.5.2 with XenServer 6.2 SP1.
>> I think that the problem shoud arrive when we've to move secondary 
>> storage but one step at time.
>> Just another question How can I move VR and SSVM??
>>
>> On Thu, Mar 24, 2016 at 6:30 AM, Sanjeev Neelarapu < 
>> sanjeev.neelar...@accelerite.com> wrote:
>>
>> > Hi,
>> >
>> > Decommissioning of primary storage should not be a problem. Since 
>> > we can migrate all the disks to additional primary storage in the cluster.
>> > Coming to artifacts stored in the secondary storage, if we make the 
>> > templates as public, all the templates will be available in 
>> > additional secondary storages within the zone. For snapshots and 
>> > volumes may have to rsync and change the image_store id in all the 
>> > relevant db tables.
>> >
>> > Best Regards,
>> > Sanjeev N
>> > Chief Product Engineer, Accelerite
>> > Off: +91 40 6722 9368 | EMail: sanjeev.neelar...@accelerite.com
>> >
>> >
>> > -Original Message-
>> > From: ilya [mailto:ilya.mailing.li...@gmail.com]
>> > Sent: Thursday, March 24, 2016 1:20 AM
>> > To: users@cloudstack.apache.org
>> > Subject: Re: Storage decommissioning
>> >
>> > I'd strongly suggest you play this out in the lab environment that 
>> > mimics what you need to do.
>> >
>> > On 3/23/16 12:47 PM, ilya wrote:
>> > > Alessandro,
>> > >
>> > > You told us nothing about your environment and setup. No downtime 
>> > > is only possible with specific hypervisors - like ESX and perhaps Xen.
>> > >
>> > > Regards
>> > > ilya
>> > >
>> > >
>> > > On 3/22/16 3:29 PM, Alessandro Caviglione wrote:
>> > >> Hi guys,
>> > >> I'm writing just to ask for advice...
>> > >> We're decommissionig our storage and we need to move all the VMs 
>> > >> from old storage to this new one.
>> > >> In CS we've defined a new primary storage and I think we've to 
>> > >> migrate all ROOT and DATA disks from old PRIMARY to the new 
>> > >> PRIMARY, this should be done without interruption of the service.
>> > >> The new storage will host also SECONDARY storage, so we need to 
>> > >> move also Template, Snapshots and other things.
>> > >> How can we do it?
>> > >>
>> > >> Thank you!!
>> > >>
>> >
>> >
>> >
>> > DISCLAIMER
>> > ==
>> > This e-mail may contain privileged and confidential information 
>> > which is the property of Accelerite, a Persistent Systems business. 
>> > It is intended only for the use of the individual or entity to 
>> > which it is addressed. If you are not the intended recipient, you 
>> > are not authorized to read, retain, copy, print, distribute or use 
>> > this message. If you have received this communication in error, 
>> > please notify the sender and delete all copies of 

Re: Secondary Storage VM overloaded

2016-04-04 Thread christian.kirmse
Hi,

a few minutes ago I discovered that there is a “Active Sessions” field in the 
details pane of the SSVMs, but the value is blank.
Do I need to configure something else so that cloudstack is aware of the 
sessions of the SSVM?

Kind Regards
Christian

> On 04 Apr 2016, at 09:33, Kirmse, Christian 
>  wrote:
> 
> Hi Glenn,
> 
> ok, thanks for the information.
> So this means we are talking about network sessions, good to know.
> 
> Tanks for your help.
> 
> Kind regards
> Christian
> 
>> On 04 Apr 2016, at 09:25, Glenn Wagner  wrote:
>> 
>> Hi,
>> 
>> To find out how many sessions are connected to the SSVM you can run 
>> 
>> netstat -anp | grep ESTABLISHED
>> 
>> Thanks
>> Glenn
>> 
>> 
>> Regards,
>> 
>> Glenn Wagner
>> 
>> glenn.wag...@shapeblue.com 
>> www.shapeblue.com
>> 2nd Floor, Oudehuis Centre, 122 Main Rd, Somerset West, Cape Town  7130South 
>> Africa
>> @shapeblue
>> 
>> -Original Message-
>> From: christian.kir...@zv.fraunhofer.de 
>> [mailto:christian.kir...@zv.fraunhofer.de] 
>> Sent: Monday, 04 April 2016 9:21 AM
>> To: users@cloudstack.apache.org
>> Subject: Re: Secondary Storage VM overloaded
>> 
>> Hi Dag,
>> 
>> thanks for your reply.
>> 
>> Unfortunately we actually don’t have a clue what kind of sessions are meant.
>> Do we need to monitor ssh sessions, linux processes or some kind of java 
>> sessions?
>> 
>> Do you have any idea where we can start?
>> 
>> Kind Regards
>> Christian
>> 
>>> On 01 Apr 2016, at 12:19, Dag Sonstebo  wrote:
>>> 
>>> Hi Christian,
>>> 
>>> I think to find the actual usage figures over time you would have to 
>>> monitor the sessions locally on the SSVM, I can't see anything in the API 
>>> to query this.
>>> 
>>> One way to determine this is to lower the secstorage.sessions.max figure 
>>> and monitor how often a second SSVM is spawned. Also keep in mind you could 
>>> increase the service offering for system VMs to increase the capacity the 
>>> SSVM can handle, this could negate the requirement for multiple SSVM 
>>> instances.
>>> 
>>> Dag Sonstebo
>>> Cloud Architect
>>> ShapeBlue
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On 01/04/2016, 10:10, "christian.kir...@zv.fraunhofer.de" 
>>>  wrote:
>>> 
 Hi all,
 
 I have a question regarding the scalability of the ssvm.
 As I understood cloudstack is able to scale out the ssvm, so that a new 
 one is created when the load is to high.
 To achieve this we have to edit the two global settings 
 secstorage.capacity.standby and secstorage.session.max, but we have no 
 idea what values are rational.
 
 Is there a way to see the current values, so that we can derive the new 
 value which we want to use?
 I mean if the current ssvm needs just 10 sessions to be overloaded and we 
 set the secstorage.session.max to 20, cloudstack will never spawn a new 
 ssvm.
 
 Kind Regards
 Christian
>>> 
>>> Regards,
>>> 
>>> Dag Sonstebo
>>> 
>>> dag.sonst...@shapeblue.com
>>> www.shapeblue.com
>>> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
>> 
> 



Re: Migration was unsuccessful. (resolved)

2016-04-04 Thread Rafael Weingärtner
No problem, I just asked to make it clear to someone else that may have the
same problem in the future.

On Mon, Apr 4, 2016 at 10:17 AM, Ugo Vasi  wrote:

> I restarted libvirtd service (sorry for my english...)
>
>
> Il 04/04/2016 15:06, Rafael Weingärtner ha scritto:
>
>> you said you did not restart libvirtd. What service have you restarted
>> then?
>>
>>
>> On Mon, Apr 4, 2016 at 10:01 AM, Ugo Vasi  wrote:
>>
>> After deleted the filei-2-28-VM.xml, I had not restarted libvirtd.
>>> Now, restarting that service, the VM is migrated without problems.
>>>
>>> Thanks for the attention
>>>
>>> Il 04/04/2016 14:51, Ugo Vasi ha scritto:
>>>
>>> I confirm that hosts are KVM hypervisor. I will try other messages in the
 logs, the ones I sent were those who showed me the web interface.


 Il 04/04/2016 14:45, Rafael Weingärtner ha scritto:

 I am assuming you are using either LXC or KVM, right?
> I do not use those hypervisors, have you executed all of the required
> configurations to enable live migrations?
>
> If you have already deleted the file “/etc/libvirt/qemu/i-2-28-VM.xml”
> and
> tried the migration again, and it did not work. How is your Java
> debugging
> skills? I would suggest you to debug the migration workflow, there
> might
> be
> a hidden exception there.
>
> On Mon, Apr 4, 2016 at 9:40 AM, Ugo Vasi  wrote:
>
> Yes, the two hosts are in the same cluster and have identical hardware.
>
>>
>>
>>
>> Il 04/04/2016 14:28, Rafael Weingärtner ha scritto:
>>
>> are migrating between hosts of the same clusters or across clusters?
>>
>>> On Mon, Apr 4, 2016 at 9:25 AM, Ugo Vasi  wrote:
>>>
>>> Yes, I added a new hypervisor to a cluster. Note that this host is
>>> from an
>>>
>>> old CloudStack 3.2 installation that I reset the configuration and
 software.

 I tried deleting the file but keeps giving me the same erroreven if
 I
 can
 not find references in other system files.







 Il 04/04/2016 12:48, Rafael Weingärtner ha scritto:

 by adding a new host agent, do you mean adding a new host
 (hypervisor) to

 a
> cluster?
> Have you tried deleting the file "/etc/libvirt/qemu/i-2-28-VM.xml"
> and
> trying to migrate the vm again?
>
> On Mon, Apr 4, 2016 at 7:03 AM, Ugo Vasi 
> wrote:
>
> Hi all,
>
> I've added a new host agent to a cluster (cloudstack 4.5.2 on
> Ubuntu
>
>> 14.04).
>>
>> Today, try migrating a VM from another host to the new one, the
>> migration
>> fails with these messages:
>>
>> 2016-04-04 11:12:13,725 DEBUG [c.c.a.t.Request]
>> (AgentManager-Handler-7:null) Seq 12-5945595933059225023:
>> Processing:
>> {
>> Ans: , MgmtId: 113359592708, via: 12, Ver: v1, Flags: 10,
>>
>>
>>
>> [{"com.cloud.agent.api.MigrateAnswer":{"result":false,"details":"org.libvirt.LibvirtException:
>>
>> operation failed: domain 'i-2-28-VM' already exists with uuid
>> 23feaae3-d709-45a9-b9dd-a295f87d815c","wait":0}}] }
>> 2016-04-04 11:12:13,725 DEBUG [c.c.a.t.Request]
>> (Work-Job-Executor-45:ctx-dc665cdb job-1388/job-1389 ctx-c61ce7b1)
>> Seq
>> 12-5945595933059225023: Received:  { Ans: , MgmtId: 113359592708,
>> via:
>> 12,
>> Ver: v1, Flags: 10, { MigrateAnswer } }
>> 2016-04-04 11:12:13,725 INFO [c.c.v.VirtualMachineManagerImpl]
>> (Work-Job-Executor-45:ctx-dc665cdb job-1388/job-1389 ctx-c61ce7b1)
>> Migration was unsuccessful.  Cleaning up: VM[User|i-2-28-VM]
>>
>> In the new host I found a file called
>> "/etc/libvirt/qemu/i-2-28-VM.xml"
>> which contains the reference ID
>> "23feaae3-d709-45a9-b9dd-a295f87d815c".
>>
>> Where can I search for the problem?
>>
>> Regards,
>> Ugo
>>
>> --
>>
>>   U g o   V a s i
>>   P r o c n e  s.r.l>)
>>   via Cotonificio 45  33010 Tavagnacco IT
>>   phone: +390432486523 fax: +390432486523
>>
>> Le informazioni contenute in questo messaggio sono riservate e
>> confidenziali ed è vietata la diffusione in qualunque modo
>> eseguita.
>> Qualora Lei non fosse la persona a cui il presente messaggio è
>> destinato, La invitiamo ad eliminarlo e a non leggerlo, dandocene
>> gentilmente comunicazione.
>> Per qualsiasi informazione si 

Re: Migration was unsuccessful. (resolved)

2016-04-04 Thread Ugo Vasi

I restarted libvirtd service (sorry for my english...)

Il 04/04/2016 15:06, Rafael Weingärtner ha scritto:

you said you did not restart libvirtd. What service have you restarted then?


On Mon, Apr 4, 2016 at 10:01 AM, Ugo Vasi  wrote:


After deleted the filei-2-28-VM.xml, I had not restarted libvirtd.
Now, restarting that service, the VM is migrated without problems.

Thanks for the attention

Il 04/04/2016 14:51, Ugo Vasi ha scritto:


I confirm that hosts are KVM hypervisor. I will try other messages in the
logs, the ones I sent were those who showed me the web interface.


Il 04/04/2016 14:45, Rafael Weingärtner ha scritto:


I am assuming you are using either LXC or KVM, right?
I do not use those hypervisors, have you executed all of the required
configurations to enable live migrations?

If you have already deleted the file “/etc/libvirt/qemu/i-2-28-VM.xml”
and
tried the migration again, and it did not work. How is your Java
debugging
skills? I would suggest you to debug the migration workflow, there might
be
a hidden exception there.

On Mon, Apr 4, 2016 at 9:40 AM, Ugo Vasi  wrote:

Yes, the two hosts are in the same cluster and have identical hardware.




Il 04/04/2016 14:28, Rafael Weingärtner ha scritto:

are migrating between hosts of the same clusters or across clusters?

On Mon, Apr 4, 2016 at 9:25 AM, Ugo Vasi  wrote:

Yes, I added a new hypervisor to a cluster. Note that this host is
from an


old CloudStack 3.2 installation that I reset the configuration and
software.

I tried deleting the file but keeps giving me the same erroreven if I
can
not find references in other system files.







Il 04/04/2016 12:48, Rafael Weingärtner ha scritto:

by adding a new host agent, do you mean adding a new host
(hypervisor) to


a
cluster?
Have you tried deleting the file "/etc/libvirt/qemu/i-2-28-VM.xml"
and
trying to migrate the vm again?

On Mon, Apr 4, 2016 at 7:03 AM, Ugo Vasi  wrote:

Hi all,

I've added a new host agent to a cluster (cloudstack 4.5.2 on Ubuntu

14.04).

Today, try migrating a VM from another host to the new one, the
migration
fails with these messages:

2016-04-04 11:12:13,725 DEBUG [c.c.a.t.Request]
(AgentManager-Handler-7:null) Seq 12-5945595933059225023:
Processing:
{
Ans: , MgmtId: 113359592708, via: 12, Ver: v1, Flags: 10,


[{"com.cloud.agent.api.MigrateAnswer":{"result":false,"details":"org.libvirt.LibvirtException:

operation failed: domain 'i-2-28-VM' already exists with uuid
23feaae3-d709-45a9-b9dd-a295f87d815c","wait":0}}] }
2016-04-04 11:12:13,725 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-45:ctx-dc665cdb job-1388/job-1389 ctx-c61ce7b1)
Seq
12-5945595933059225023: Received:  { Ans: , MgmtId: 113359592708,
via:
12,
Ver: v1, Flags: 10, { MigrateAnswer } }
2016-04-04 11:12:13,725 INFO [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-45:ctx-dc665cdb job-1388/job-1389 ctx-c61ce7b1)
Migration was unsuccessful.  Cleaning up: VM[User|i-2-28-VM]

In the new host I found a file called
"/etc/libvirt/qemu/i-2-28-VM.xml"
which contains the reference ID
"23feaae3-d709-45a9-b9dd-a295f87d815c".

Where can I search for the problem?

Regards,
Ugo

--

  U g o   V a s i
  P r o c n e  s.r.l>)
  via Cotonificio 45  33010 Tavagnacco IT
  phone: +390432486523 fax: +390432486523

Le informazioni contenute in questo messaggio sono riservate e
confidenziali ed è vietata la diffusione in qualunque modo eseguita.
Qualora Lei non fosse la persona a cui il presente messaggio è
destinato, La invitiamo ad eliminarlo e a non leggerlo, dandocene
gentilmente comunicazione.
Per qualsiasi informazione si prega di contattare supp...@procne.it
.
Rif. D.L. 196/2003



--


 U g o   V a s i

 P r o c n e  s.r.l>)
 via Cotonificio 45  33010 Tavagnacco IT
 phone: +390432486523 fax: +390432486523

Le informazioni contenute in questo messaggio sono riservate e
confidenziali ed è vietata la diffusione in qualunque modo eseguita.
Qualora Lei non fosse la persona a cui il presente messaggio è
destinato, La invitiamo ad eliminarlo e a non leggerlo, dandocene
gentilmente comunicazione.
Per qualsiasi informazione si prega di contattare supp...@procne.it .
Rif. D.L. 196/2003



--

U g o   V a s i
P r o c n e  s.r.l>)
via Cotonificio 45  33010 Tavagnacco IT
phone: +390432486523 fax: +390432486523

Le informazioni contenute in questo messaggio sono riservate e
confidenziali ed è vietata la diffusione in qualunque modo eseguita.
Qualora Lei non fosse la persona a cui il presente messaggio è
destinato, La invitiamo ad eliminarlo e a non leggerlo, dandocene
gentilmente comunicazione.
Per qualsiasi informazione si prega di contattare supp...@procne.it .
Rif. D.L. 196/2003






--

   U g o   V a s i
   P r o c n e  s.r.l>)
   via Cotonificio 45  33010 Tavagnacco IT
   phone: 

Re: Migration was unsuccessful. (resolved)

2016-04-04 Thread Rafael Weingärtner
you said you did not restart libvirtd. What service have you restarted then?


On Mon, Apr 4, 2016 at 10:01 AM, Ugo Vasi  wrote:

> After deleted the filei-2-28-VM.xml, I had not restarted libvirtd.
> Now, restarting that service, the VM is migrated without problems.
>
> Thanks for the attention
>
> Il 04/04/2016 14:51, Ugo Vasi ha scritto:
>
>> I confirm that hosts are KVM hypervisor. I will try other messages in the
>> logs, the ones I sent were those who showed me the web interface.
>>
>>
>> Il 04/04/2016 14:45, Rafael Weingärtner ha scritto:
>>
>>> I am assuming you are using either LXC or KVM, right?
>>> I do not use those hypervisors, have you executed all of the required
>>> configurations to enable live migrations?
>>>
>>> If you have already deleted the file “/etc/libvirt/qemu/i-2-28-VM.xml”
>>> and
>>> tried the migration again, and it did not work. How is your Java
>>> debugging
>>> skills? I would suggest you to debug the migration workflow, there might
>>> be
>>> a hidden exception there.
>>>
>>> On Mon, Apr 4, 2016 at 9:40 AM, Ugo Vasi  wrote:
>>>
>>> Yes, the two hosts are in the same cluster and have identical hardware.




 Il 04/04/2016 14:28, Rafael Weingärtner ha scritto:

 are migrating between hosts of the same clusters or across clusters?
>
> On Mon, Apr 4, 2016 at 9:25 AM, Ugo Vasi  wrote:
>
> Yes, I added a new hypervisor to a cluster. Note that this host is
> from an
>
>> old CloudStack 3.2 installation that I reset the configuration and
>> software.
>>
>> I tried deleting the file but keeps giving me the same erroreven if I
>> can
>> not find references in other system files.
>>
>>
>>
>>
>>
>>
>>
>> Il 04/04/2016 12:48, Rafael Weingärtner ha scritto:
>>
>> by adding a new host agent, do you mean adding a new host
>> (hypervisor) to
>>
>>> a
>>> cluster?
>>> Have you tried deleting the file "/etc/libvirt/qemu/i-2-28-VM.xml"
>>> and
>>> trying to migrate the vm again?
>>>
>>> On Mon, Apr 4, 2016 at 7:03 AM, Ugo Vasi  wrote:
>>>
>>> Hi all,
>>>
>>> I've added a new host agent to a cluster (cloudstack 4.5.2 on Ubuntu
 14.04).

 Today, try migrating a VM from another host to the new one, the
 migration
 fails with these messages:

 2016-04-04 11:12:13,725 DEBUG [c.c.a.t.Request]
 (AgentManager-Handler-7:null) Seq 12-5945595933059225023:
 Processing:
 {
 Ans: , MgmtId: 113359592708, via: 12, Ver: v1, Flags: 10,


 [{"com.cloud.agent.api.MigrateAnswer":{"result":false,"details":"org.libvirt.LibvirtException:

 operation failed: domain 'i-2-28-VM' already exists with uuid
 23feaae3-d709-45a9-b9dd-a295f87d815c","wait":0}}] }
 2016-04-04 11:12:13,725 DEBUG [c.c.a.t.Request]
 (Work-Job-Executor-45:ctx-dc665cdb job-1388/job-1389 ctx-c61ce7b1)
 Seq
 12-5945595933059225023: Received:  { Ans: , MgmtId: 113359592708,
 via:
 12,
 Ver: v1, Flags: 10, { MigrateAnswer } }
 2016-04-04 11:12:13,725 INFO [c.c.v.VirtualMachineManagerImpl]
 (Work-Job-Executor-45:ctx-dc665cdb job-1388/job-1389 ctx-c61ce7b1)
 Migration was unsuccessful.  Cleaning up: VM[User|i-2-28-VM]

 In the new host I found a file called
 "/etc/libvirt/qemu/i-2-28-VM.xml"
 which contains the reference ID
 "23feaae3-d709-45a9-b9dd-a295f87d815c".

 Where can I search for the problem?

 Regards,
 Ugo

 --

  U g o   V a s i
  P r o c n e  s.r.l>)
  via Cotonificio 45  33010 Tavagnacco IT
  phone: +390432486523 fax: +390432486523

 Le informazioni contenute in questo messaggio sono riservate e
 confidenziali ed è vietata la diffusione in qualunque modo eseguita.
 Qualora Lei non fosse la persona a cui il presente messaggio è
 destinato, La invitiamo ad eliminarlo e a non leggerlo, dandocene
 gentilmente comunicazione.
 Per qualsiasi informazione si prega di contattare supp...@procne.it
 .
 Rif. D.L. 196/2003



 --

>>> U g o   V a s i
>> P r o c n e  s.r.l>)
>> via Cotonificio 45  33010 Tavagnacco IT
>> phone: +390432486523 fax: +390432486523
>>
>> Le informazioni contenute in questo messaggio sono riservate e
>> confidenziali ed è vietata la diffusione in qualunque modo eseguita.
>> Qualora Lei non fosse la persona a cui il presente messaggio è
>> destinato, La invitiamo ad eliminarlo e a non leggerlo, dandocene

Re: Migration was unsuccessful. (resolved)

2016-04-04 Thread Ugo Vasi

After deleted the filei-2-28-VM.xml, I had not restarted libvirtd.
Now, restarting that service, the VM is migrated without problems.

Thanks for the attention

Il 04/04/2016 14:51, Ugo Vasi ha scritto:
I confirm that hosts are KVM hypervisor. I will try other messages in 
the logs, the ones I sent were those who showed me the web interface.



Il 04/04/2016 14:45, Rafael Weingärtner ha scritto:

I am assuming you are using either LXC or KVM, right?
I do not use those hypervisors, have you executed all of the required
configurations to enable live migrations?

If you have already deleted the file 
“/etc/libvirt/qemu/i-2-28-VM.xml” and
tried the migration again, and it did not work. How is your Java 
debugging
skills? I would suggest you to debug the migration workflow, there 
might be

a hidden exception there.

On Mon, Apr 4, 2016 at 9:40 AM, Ugo Vasi  wrote:


Yes, the two hosts are in the same cluster and have identical hardware.




Il 04/04/2016 14:28, Rafael Weingärtner ha scritto:


are migrating between hosts of the same clusters or across clusters?

On Mon, Apr 4, 2016 at 9:25 AM, Ugo Vasi  wrote:

Yes, I added a new hypervisor to a cluster. Note that this host is 
from an

old CloudStack 3.2 installation that I reset the configuration and
software.

I tried deleting the file but keeps giving me the same erroreven 
if I can

not find references in other system files.







Il 04/04/2016 12:48, Rafael Weingärtner ha scritto:

by adding a new host agent, do you mean adding a new host 
(hypervisor) to

a
cluster?
Have you tried deleting the file 
"/etc/libvirt/qemu/i-2-28-VM.xml" and

trying to migrate the vm again?

On Mon, Apr 4, 2016 at 7:03 AM, Ugo Vasi  wrote:

Hi all,

I've added a new host agent to a cluster (cloudstack 4.5.2 on 
Ubuntu

14.04).

Today, try migrating a VM from another host to the new one, the
migration
fails with these messages:

2016-04-04 11:12:13,725 DEBUG [c.c.a.t.Request]
(AgentManager-Handler-7:null) Seq 12-5945595933059225023: 
Processing:

{
Ans: , MgmtId: 113359592708, via: 12, Ver: v1, Flags: 10,


[{"com.cloud.agent.api.MigrateAnswer":{"result":false,"details":"org.libvirt.LibvirtException: 


operation failed: domain 'i-2-28-VM' already exists with uuid
23feaae3-d709-45a9-b9dd-a295f87d815c","wait":0}}] }
2016-04-04 11:12:13,725 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-45:ctx-dc665cdb job-1388/job-1389 
ctx-c61ce7b1) Seq
12-5945595933059225023: Received:  { Ans: , MgmtId: 
113359592708, via:

12,
Ver: v1, Flags: 10, { MigrateAnswer } }
2016-04-04 11:12:13,725 INFO [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-45:ctx-dc665cdb job-1388/job-1389 ctx-c61ce7b1)
Migration was unsuccessful.  Cleaning up: VM[User|i-2-28-VM]

In the new host I found a file called 
"/etc/libvirt/qemu/i-2-28-VM.xml"

which contains the reference ID
"23feaae3-d709-45a9-b9dd-a295f87d815c".

Where can I search for the problem?

Regards,
Ugo

--

 U g o   V a s i
 P r o c n e  s.r.l>)
 via Cotonificio 45  33010 Tavagnacco IT
 phone: +390432486523 fax: +390432486523

Le informazioni contenute in questo messaggio sono riservate e
confidenziali ed è vietata la diffusione in qualunque modo 
eseguita.

Qualora Lei non fosse la persona a cui il presente messaggio è
destinato, La invitiamo ad eliminarlo e a non leggerlo, dandocene
gentilmente comunicazione.
Per qualsiasi informazione si prega di contattare 
supp...@procne.it .

Rif. D.L. 196/2003



--

U g o   V a s i
P r o c n e  s.r.l>)
via Cotonificio 45  33010 Tavagnacco IT
phone: +390432486523 fax: +390432486523

Le informazioni contenute in questo messaggio sono riservate e
confidenziali ed è vietata la diffusione in qualunque modo eseguita.
Qualora Lei non fosse la persona a cui il presente messaggio è
destinato, La invitiamo ad eliminarlo e a non leggerlo, dandocene
gentilmente comunicazione.
Per qualsiasi informazione si prega di contattare supp...@procne.it .
Rif. D.L. 196/2003




--

   U g o   V a s i
   P r o c n e  s.r.l>)
   via Cotonificio 45  33010 Tavagnacco IT
   phone: +390432486523 fax: +390432486523

Le informazioni contenute in questo messaggio sono riservate e
confidenziali ed è vietata la diffusione in qualunque modo eseguita.
Qualora Lei non fosse la persona a cui il presente messaggio è
destinato, La invitiamo ad eliminarlo e a non leggerlo, dandocene
gentilmente comunicazione.
Per qualsiasi informazione si prega di contattare supp...@procne.it .
Rif. D.L. 196/2003










--

  U g o   V a s i
  P r o c n e  s.r.l>)
  via Cotonificio 45  33010 Tavagnacco IT
  phone: +390432486523 fax: +390432486523

Le informazioni contenute in questo messaggio sono riservate e
confidenziali ed è vietata la diffusione in qualunque modo eseguita.
Qualora Lei non fosse la persona a cui il presente messaggio è
destinato, La 

Re: Migration was unsuccessful.

2016-04-04 Thread Ugo Vasi
I confirm that hosts are KVM hypervisor. I will try other messages in 
the logs, the ones I sent were those who showed me the web interface.



Il 04/04/2016 14:45, Rafael Weingärtner ha scritto:

I am assuming you are using either LXC or KVM, right?
I do not use those hypervisors, have you executed all of the required
configurations to enable live migrations?

If you have already deleted the file “/etc/libvirt/qemu/i-2-28-VM.xml” and
tried the migration again, and it did not work. How is your Java debugging
skills? I would suggest you to debug the migration workflow, there might be
a hidden exception there.

On Mon, Apr 4, 2016 at 9:40 AM, Ugo Vasi  wrote:


Yes, the two hosts are in the same cluster and have identical hardware.




Il 04/04/2016 14:28, Rafael Weingärtner ha scritto:


are migrating between hosts of the same clusters or across clusters?

On Mon, Apr 4, 2016 at 9:25 AM, Ugo Vasi  wrote:

Yes, I added a new hypervisor to a cluster. Note that this host is from an

old CloudStack 3.2 installation that I reset the configuration and
software.

I tried deleting the file but keeps giving me the same erroreven if I can
not find references in other system files.







Il 04/04/2016 12:48, Rafael Weingärtner ha scritto:

by adding a new host agent, do you mean adding a new host (hypervisor) to

a
cluster?
Have you tried deleting the file "/etc/libvirt/qemu/i-2-28-VM.xml" and
trying to migrate the vm again?

On Mon, Apr 4, 2016 at 7:03 AM, Ugo Vasi  wrote:

Hi all,


I've added a new host agent to a cluster (cloudstack 4.5.2 on Ubuntu
14.04).

Today, try migrating a VM from another host to the new one, the
migration
fails with these messages:

2016-04-04 11:12:13,725 DEBUG [c.c.a.t.Request]
(AgentManager-Handler-7:null) Seq 12-5945595933059225023: Processing:
{
Ans: , MgmtId: 113359592708, via: 12, Ver: v1, Flags: 10,


[{"com.cloud.agent.api.MigrateAnswer":{"result":false,"details":"org.libvirt.LibvirtException:
operation failed: domain 'i-2-28-VM' already exists with uuid
23feaae3-d709-45a9-b9dd-a295f87d815c","wait":0}}] }
2016-04-04 11:12:13,725 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-45:ctx-dc665cdb job-1388/job-1389 ctx-c61ce7b1) Seq
12-5945595933059225023: Received:  { Ans: , MgmtId: 113359592708, via:
12,
Ver: v1, Flags: 10, { MigrateAnswer } }
2016-04-04 11:12:13,725 INFO  [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-45:ctx-dc665cdb job-1388/job-1389 ctx-c61ce7b1)
Migration was unsuccessful.  Cleaning up: VM[User|i-2-28-VM]

In the new host I found a file called "/etc/libvirt/qemu/i-2-28-VM.xml"
which contains the reference ID
"23feaae3-d709-45a9-b9dd-a295f87d815c".

Where can I search for the problem?

Regards,
Ugo

--

 U g o   V a s i
 P r o c n e  s.r.l>)
 via Cotonificio 45  33010 Tavagnacco IT
 phone: +390432486523 fax: +390432486523

Le informazioni contenute in questo messaggio sono riservate e
confidenziali ed è vietata la diffusione in qualunque modo eseguita.
Qualora Lei non fosse la persona a cui il presente messaggio è
destinato, La invitiamo ad eliminarlo e a non leggerlo, dandocene
gentilmente comunicazione.
Per qualsiasi informazione si prega di contattare supp...@procne.it .
Rif. D.L. 196/2003



--

U g o   V a s i
P r o c n e  s.r.l>)
via Cotonificio 45  33010 Tavagnacco IT
phone: +390432486523 fax: +390432486523

Le informazioni contenute in questo messaggio sono riservate e
confidenziali ed è vietata la diffusione in qualunque modo eseguita.
Qualora Lei non fosse la persona a cui il presente messaggio è
destinato, La invitiamo ad eliminarlo e a non leggerlo, dandocene
gentilmente comunicazione.
Per qualsiasi informazione si prega di contattare supp...@procne.it .
Rif. D.L. 196/2003




--

   U g o   V a s i
   P r o c n e  s.r.l>)
   via Cotonificio 45  33010 Tavagnacco IT
   phone: +390432486523 fax: +390432486523

Le informazioni contenute in questo messaggio sono riservate e
confidenziali ed è vietata la diffusione in qualunque modo eseguita.
Qualora Lei non fosse la persona a cui il presente messaggio è
destinato, La invitiamo ad eliminarlo e a non leggerlo, dandocene
gentilmente comunicazione.
Per qualsiasi informazione si prega di contattare supp...@procne.it .
Rif. D.L. 196/2003







--

  U g o   V a s i
  P r o c n e  s.r.l>)
  via Cotonificio 45  33010 Tavagnacco IT
  phone: +390432486523 fax: +390432486523

Le informazioni contenute in questo messaggio sono riservate e
confidenziali ed è vietata la diffusione in qualunque modo eseguita.
Qualora Lei non fosse la persona a cui il presente messaggio è
destinato, La invitiamo ad eliminarlo e a non leggerlo, dandocene
gentilmente comunicazione.
Per qualsiasi informazione si prega di contattare supp...@procne.it .
Rif. D.L. 196/2003



Re: Migration was unsuccessful.

2016-04-04 Thread Rafael Weingärtner
I am assuming you are using either LXC or KVM, right?
I do not use those hypervisors, have you executed all of the required
configurations to enable live migrations?

If you have already deleted the file “/etc/libvirt/qemu/i-2-28-VM.xml” and
tried the migration again, and it did not work. How is your Java debugging
skills? I would suggest you to debug the migration workflow, there might be
a hidden exception there.

On Mon, Apr 4, 2016 at 9:40 AM, Ugo Vasi  wrote:

> Yes, the two hosts are in the same cluster and have identical hardware.
>
>
>
>
> Il 04/04/2016 14:28, Rafael Weingärtner ha scritto:
>
>> are migrating between hosts of the same clusters or across clusters?
>>
>> On Mon, Apr 4, 2016 at 9:25 AM, Ugo Vasi  wrote:
>>
>> Yes, I added a new hypervisor to a cluster. Note that this host is from an
>>> old CloudStack 3.2 installation that I reset the configuration and
>>> software.
>>>
>>> I tried deleting the file but keeps giving me the same erroreven if I can
>>> not find references in other system files.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Il 04/04/2016 12:48, Rafael Weingärtner ha scritto:
>>>
>>> by adding a new host agent, do you mean adding a new host (hypervisor) to
 a
 cluster?
 Have you tried deleting the file "/etc/libvirt/qemu/i-2-28-VM.xml" and
 trying to migrate the vm again?

 On Mon, Apr 4, 2016 at 7:03 AM, Ugo Vasi  wrote:

 Hi all,

> I've added a new host agent to a cluster (cloudstack 4.5.2 on Ubuntu
> 14.04).
>
> Today, try migrating a VM from another host to the new one, the
> migration
> fails with these messages:
>
> 2016-04-04 11:12:13,725 DEBUG [c.c.a.t.Request]
> (AgentManager-Handler-7:null) Seq 12-5945595933059225023: Processing:
> {
> Ans: , MgmtId: 113359592708, via: 12, Ver: v1, Flags: 10,
>
>
> [{"com.cloud.agent.api.MigrateAnswer":{"result":false,"details":"org.libvirt.LibvirtException:
> operation failed: domain 'i-2-28-VM' already exists with uuid
> 23feaae3-d709-45a9-b9dd-a295f87d815c","wait":0}}] }
> 2016-04-04 11:12:13,725 DEBUG [c.c.a.t.Request]
> (Work-Job-Executor-45:ctx-dc665cdb job-1388/job-1389 ctx-c61ce7b1) Seq
> 12-5945595933059225023: Received:  { Ans: , MgmtId: 113359592708, via:
> 12,
> Ver: v1, Flags: 10, { MigrateAnswer } }
> 2016-04-04 11:12:13,725 INFO  [c.c.v.VirtualMachineManagerImpl]
> (Work-Job-Executor-45:ctx-dc665cdb job-1388/job-1389 ctx-c61ce7b1)
> Migration was unsuccessful.  Cleaning up: VM[User|i-2-28-VM]
>
> In the new host I found a file called "/etc/libvirt/qemu/i-2-28-VM.xml"
> which contains the reference ID
> "23feaae3-d709-45a9-b9dd-a295f87d815c".
>
> Where can I search for the problem?
>
> Regards,
> Ugo
>
> --
>
> U g o   V a s i
> P r o c n e  s.r.l>)
> via Cotonificio 45  33010 Tavagnacco IT
> phone: +390432486523 fax: +390432486523
>
> Le informazioni contenute in questo messaggio sono riservate e
> confidenziali ed è vietata la diffusione in qualunque modo eseguita.
> Qualora Lei non fosse la persona a cui il presente messaggio è
> destinato, La invitiamo ad eliminarlo e a non leggerlo, dandocene
> gentilmente comunicazione.
> Per qualsiasi informazione si prega di contattare supp...@procne.it .
> Rif. D.L. 196/2003
>
>
>
> --
>>>
>>>U g o   V a s i
>>>P r o c n e  s.r.l>)
>>>via Cotonificio 45  33010 Tavagnacco IT
>>>phone: +390432486523 fax: +390432486523
>>>
>>> Le informazioni contenute in questo messaggio sono riservate e
>>> confidenziali ed è vietata la diffusione in qualunque modo eseguita.
>>> Qualora Lei non fosse la persona a cui il presente messaggio è
>>> destinato, La invitiamo ad eliminarlo e a non leggerlo, dandocene
>>> gentilmente comunicazione.
>>> Per qualsiasi informazione si prega di contattare supp...@procne.it .
>>> Rif. D.L. 196/2003
>>>
>>>
>>>
>>
>
> --
>
>   U g o   V a s i
>   P r o c n e  s.r.l>)
>   via Cotonificio 45  33010 Tavagnacco IT
>   phone: +390432486523 fax: +390432486523
>
> Le informazioni contenute in questo messaggio sono riservate e
> confidenziali ed è vietata la diffusione in qualunque modo eseguita.
> Qualora Lei non fosse la persona a cui il presente messaggio è
> destinato, La invitiamo ad eliminarlo e a non leggerlo, dandocene
> gentilmente comunicazione.
> Per qualsiasi informazione si prega di contattare supp...@procne.it .
> Rif. D.L. 196/2003
>
>


-- 
Rafael Weingärtner


Re: Migration was unsuccessful.

2016-04-04 Thread Ugo Vasi

Yes, the two hosts are in the same cluster and have identical hardware.



Il 04/04/2016 14:28, Rafael Weingärtner ha scritto:

are migrating between hosts of the same clusters or across clusters?

On Mon, Apr 4, 2016 at 9:25 AM, Ugo Vasi  wrote:


Yes, I added a new hypervisor to a cluster. Note that this host is from an
old CloudStack 3.2 installation that I reset the configuration and software.

I tried deleting the file but keeps giving me the same erroreven if I can
not find references in other system files.







Il 04/04/2016 12:48, Rafael Weingärtner ha scritto:


by adding a new host agent, do you mean adding a new host (hypervisor) to
a
cluster?
Have you tried deleting the file "/etc/libvirt/qemu/i-2-28-VM.xml" and
trying to migrate the vm again?

On Mon, Apr 4, 2016 at 7:03 AM, Ugo Vasi  wrote:

Hi all,

I've added a new host agent to a cluster (cloudstack 4.5.2 on Ubuntu
14.04).

Today, try migrating a VM from another host to the new one, the migration
fails with these messages:

2016-04-04 11:12:13,725 DEBUG [c.c.a.t.Request]
(AgentManager-Handler-7:null) Seq 12-5945595933059225023: Processing:  {
Ans: , MgmtId: 113359592708, via: 12, Ver: v1, Flags: 10,

[{"com.cloud.agent.api.MigrateAnswer":{"result":false,"details":"org.libvirt.LibvirtException:
operation failed: domain 'i-2-28-VM' already exists with uuid
23feaae3-d709-45a9-b9dd-a295f87d815c","wait":0}}] }
2016-04-04 11:12:13,725 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-45:ctx-dc665cdb job-1388/job-1389 ctx-c61ce7b1) Seq
12-5945595933059225023: Received:  { Ans: , MgmtId: 113359592708, via:
12,
Ver: v1, Flags: 10, { MigrateAnswer } }
2016-04-04 11:12:13,725 INFO  [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-45:ctx-dc665cdb job-1388/job-1389 ctx-c61ce7b1)
Migration was unsuccessful.  Cleaning up: VM[User|i-2-28-VM]

In the new host I found a file called "/etc/libvirt/qemu/i-2-28-VM.xml"
which contains the reference ID
"23feaae3-d709-45a9-b9dd-a295f87d815c".

Where can I search for the problem?

Regards,
Ugo

--

U g o   V a s i
P r o c n e  s.r.l>)
via Cotonificio 45  33010 Tavagnacco IT
phone: +390432486523 fax: +390432486523

Le informazioni contenute in questo messaggio sono riservate e
confidenziali ed è vietata la diffusione in qualunque modo eseguita.
Qualora Lei non fosse la persona a cui il presente messaggio è
destinato, La invitiamo ad eliminarlo e a non leggerlo, dandocene
gentilmente comunicazione.
Per qualsiasi informazione si prega di contattare supp...@procne.it .
Rif. D.L. 196/2003




--

   U g o   V a s i
   P r o c n e  s.r.l>)
   via Cotonificio 45  33010 Tavagnacco IT
   phone: +390432486523 fax: +390432486523

Le informazioni contenute in questo messaggio sono riservate e
confidenziali ed è vietata la diffusione in qualunque modo eseguita.
Qualora Lei non fosse la persona a cui il presente messaggio è
destinato, La invitiamo ad eliminarlo e a non leggerlo, dandocene
gentilmente comunicazione.
Per qualsiasi informazione si prega di contattare supp...@procne.it .
Rif. D.L. 196/2003







--

  U g o   V a s i
  P r o c n e  s.r.l>)
  via Cotonificio 45  33010 Tavagnacco IT
  phone: +390432486523 fax: +390432486523

Le informazioni contenute in questo messaggio sono riservate e
confidenziali ed è vietata la diffusione in qualunque modo eseguita.
Qualora Lei non fosse la persona a cui il presente messaggio è
destinato, La invitiamo ad eliminarlo e a non leggerlo, dandocene
gentilmente comunicazione.
Per qualsiasi informazione si prega di contattare supp...@procne.it .
Rif. D.L. 196/2003



Re: Migration was unsuccessful.

2016-04-04 Thread Rafael Weingärtner
are migrating between hosts of the same clusters or across clusters?

On Mon, Apr 4, 2016 at 9:25 AM, Ugo Vasi  wrote:

> Yes, I added a new hypervisor to a cluster. Note that this host is from an
> old CloudStack 3.2 installation that I reset the configuration and software.
>
> I tried deleting the file but keeps giving me the same erroreven if I can
> not find references in other system files.
>
>
>
>
>
>
>
> Il 04/04/2016 12:48, Rafael Weingärtner ha scritto:
>
>> by adding a new host agent, do you mean adding a new host (hypervisor) to
>> a
>> cluster?
>> Have you tried deleting the file "/etc/libvirt/qemu/i-2-28-VM.xml" and
>> trying to migrate the vm again?
>>
>> On Mon, Apr 4, 2016 at 7:03 AM, Ugo Vasi  wrote:
>>
>> Hi all,
>>> I've added a new host agent to a cluster (cloudstack 4.5.2 on Ubuntu
>>> 14.04).
>>>
>>> Today, try migrating a VM from another host to the new one, the migration
>>> fails with these messages:
>>>
>>> 2016-04-04 11:12:13,725 DEBUG [c.c.a.t.Request]
>>> (AgentManager-Handler-7:null) Seq 12-5945595933059225023: Processing:  {
>>> Ans: , MgmtId: 113359592708, via: 12, Ver: v1, Flags: 10,
>>>
>>> [{"com.cloud.agent.api.MigrateAnswer":{"result":false,"details":"org.libvirt.LibvirtException:
>>> operation failed: domain 'i-2-28-VM' already exists with uuid
>>> 23feaae3-d709-45a9-b9dd-a295f87d815c","wait":0}}] }
>>> 2016-04-04 11:12:13,725 DEBUG [c.c.a.t.Request]
>>> (Work-Job-Executor-45:ctx-dc665cdb job-1388/job-1389 ctx-c61ce7b1) Seq
>>> 12-5945595933059225023: Received:  { Ans: , MgmtId: 113359592708, via:
>>> 12,
>>> Ver: v1, Flags: 10, { MigrateAnswer } }
>>> 2016-04-04 11:12:13,725 INFO  [c.c.v.VirtualMachineManagerImpl]
>>> (Work-Job-Executor-45:ctx-dc665cdb job-1388/job-1389 ctx-c61ce7b1)
>>> Migration was unsuccessful.  Cleaning up: VM[User|i-2-28-VM]
>>>
>>> In the new host I found a file called "/etc/libvirt/qemu/i-2-28-VM.xml"
>>> which contains the reference ID
>>> "23feaae3-d709-45a9-b9dd-a295f87d815c".
>>>
>>> Where can I search for the problem?
>>>
>>> Regards,
>>> Ugo
>>>
>>> --
>>>
>>>U g o   V a s i
>>>P r o c n e  s.r.l>)
>>>via Cotonificio 45  33010 Tavagnacco IT
>>>phone: +390432486523 fax: +390432486523
>>>
>>> Le informazioni contenute in questo messaggio sono riservate e
>>> confidenziali ed è vietata la diffusione in qualunque modo eseguita.
>>> Qualora Lei non fosse la persona a cui il presente messaggio è
>>> destinato, La invitiamo ad eliminarlo e a non leggerlo, dandocene
>>> gentilmente comunicazione.
>>> Per qualsiasi informazione si prega di contattare supp...@procne.it .
>>> Rif. D.L. 196/2003
>>>
>>>
>>>
>>
>
> --
>
>   U g o   V a s i
>   P r o c n e  s.r.l>)
>   via Cotonificio 45  33010 Tavagnacco IT
>   phone: +390432486523 fax: +390432486523
>
> Le informazioni contenute in questo messaggio sono riservate e
> confidenziali ed è vietata la diffusione in qualunque modo eseguita.
> Qualora Lei non fosse la persona a cui il presente messaggio è
> destinato, La invitiamo ad eliminarlo e a non leggerlo, dandocene
> gentilmente comunicazione.
> Per qualsiasi informazione si prega di contattare supp...@procne.it .
> Rif. D.L. 196/2003
>
>


-- 
Rafael Weingärtner


Re: Migration was unsuccessful.

2016-04-04 Thread Ugo Vasi
Yes, I added a new hypervisor to a cluster. Note that this host is from 
an old CloudStack 3.2 installation that I reset the configuration and 
software.


I tried deleting the file but keeps giving me the same erroreven if I 
can not find references in other system files.







Il 04/04/2016 12:48, Rafael Weingärtner ha scritto:

by adding a new host agent, do you mean adding a new host (hypervisor) to a
cluster?
Have you tried deleting the file "/etc/libvirt/qemu/i-2-28-VM.xml" and
trying to migrate the vm again?

On Mon, Apr 4, 2016 at 7:03 AM, Ugo Vasi  wrote:


Hi all,
I've added a new host agent to a cluster (cloudstack 4.5.2 on Ubuntu
14.04).

Today, try migrating a VM from another host to the new one, the migration
fails with these messages:

2016-04-04 11:12:13,725 DEBUG [c.c.a.t.Request]
(AgentManager-Handler-7:null) Seq 12-5945595933059225023: Processing:  {
Ans: , MgmtId: 113359592708, via: 12, Ver: v1, Flags: 10,
[{"com.cloud.agent.api.MigrateAnswer":{"result":false,"details":"org.libvirt.LibvirtException:
operation failed: domain 'i-2-28-VM' already exists with uuid
23feaae3-d709-45a9-b9dd-a295f87d815c","wait":0}}] }
2016-04-04 11:12:13,725 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-45:ctx-dc665cdb job-1388/job-1389 ctx-c61ce7b1) Seq
12-5945595933059225023: Received:  { Ans: , MgmtId: 113359592708, via: 12,
Ver: v1, Flags: 10, { MigrateAnswer } }
2016-04-04 11:12:13,725 INFO  [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-45:ctx-dc665cdb job-1388/job-1389 ctx-c61ce7b1)
Migration was unsuccessful.  Cleaning up: VM[User|i-2-28-VM]

In the new host I found a file called "/etc/libvirt/qemu/i-2-28-VM.xml"
which contains the reference ID
"23feaae3-d709-45a9-b9dd-a295f87d815c".

Where can I search for the problem?

Regards,
Ugo

--

   U g o   V a s i
   P r o c n e  s.r.l>)
   via Cotonificio 45  33010 Tavagnacco IT
   phone: +390432486523 fax: +390432486523

Le informazioni contenute in questo messaggio sono riservate e
confidenziali ed è vietata la diffusione in qualunque modo eseguita.
Qualora Lei non fosse la persona a cui il presente messaggio è
destinato, La invitiamo ad eliminarlo e a non leggerlo, dandocene
gentilmente comunicazione.
Per qualsiasi informazione si prega di contattare supp...@procne.it .
Rif. D.L. 196/2003







--

  U g o   V a s i
  P r o c n e  s.r.l>)
  via Cotonificio 45  33010 Tavagnacco IT
  phone: +390432486523 fax: +390432486523

Le informazioni contenute in questo messaggio sono riservate e
confidenziali ed è vietata la diffusione in qualunque modo eseguita.
Qualora Lei non fosse la persona a cui il presente messaggio è
destinato, La invitiamo ad eliminarlo e a non leggerlo, dandocene
gentilmente comunicazione.
Per qualsiasi informazione si prega di contattare supp...@procne.it .
Rif. D.L. 196/2003



Re: SSVM cant route to MS, Iptables keep self-updating

2016-04-04 Thread Rafael Weingärtner
What hypervisor are you using?
Did change the iptables rules at the SSVM itself?

On Mon, Apr 4, 2016 at 6:50 AM, Glenn Wagner 
wrote:

> Hi,
>
> Can you ping the default gateway of the SSVM?
> Can you ping google DNS 8.8.8.8 from the SSVM?
>
> Thanks
> Glenn
>
>
> Regards,
>
> Glenn Wagner
>
> glenn.wag...@shapeblue.com
> www.shapeblue.com
> 2nd Floor, Oudehuis Centre, 122 Main Rd, Somerset West, Cape Town
> 7130South Africa
> @shapeblue
>
> -Original Message-
> From: Syafiq Rokman [mailto:msyafiq.rok...@gmail.com]
> Sent: Monday, 04 April 2016 11:16 AM
> To: users@cloudstack.apache.org
> Subject: SSVM cant route to MS, Iptables keep self-updating
>
> Hi everyone!
>
> Im running CS 4.8 on Ubuntu 14.04 LTS.
>
> So I've managed to set up everything, but I still cant install templates.
> So I SSH-ed into the SSVM and ran the healthcheck and it seems that the
> SSVM can't connect to the DNS.
>
> Logs says that it can't route to host.
>
> So I've tried to allow all outgoing/incoming connections on Iptables, but
> it keeps changing back to deny outgoing connections.
>
> Any ideas on how to proceed?
>
> Will provide logs if anyone needs it.
>
> Thanks
> Syafiq Rokman
> B.ICT Student
>



-- 
Rafael Weingärtner


Re: Migration was unsuccessful.

2016-04-04 Thread Rafael Weingärtner
by adding a new host agent, do you mean adding a new host (hypervisor) to a
cluster?
Have you tried deleting the file "/etc/libvirt/qemu/i-2-28-VM.xml" and
trying to migrate the vm again?

On Mon, Apr 4, 2016 at 7:03 AM, Ugo Vasi  wrote:

> Hi all,
> I've added a new host agent to a cluster (cloudstack 4.5.2 on Ubuntu
> 14.04).
>
> Today, try migrating a VM from another host to the new one, the migration
> fails with these messages:
>
> 2016-04-04 11:12:13,725 DEBUG [c.c.a.t.Request]
> (AgentManager-Handler-7:null) Seq 12-5945595933059225023: Processing:  {
> Ans: , MgmtId: 113359592708, via: 12, Ver: v1, Flags: 10,
> [{"com.cloud.agent.api.MigrateAnswer":{"result":false,"details":"org.libvirt.LibvirtException:
> operation failed: domain 'i-2-28-VM' already exists with uuid
> 23feaae3-d709-45a9-b9dd-a295f87d815c","wait":0}}] }
> 2016-04-04 11:12:13,725 DEBUG [c.c.a.t.Request]
> (Work-Job-Executor-45:ctx-dc665cdb job-1388/job-1389 ctx-c61ce7b1) Seq
> 12-5945595933059225023: Received:  { Ans: , MgmtId: 113359592708, via: 12,
> Ver: v1, Flags: 10, { MigrateAnswer } }
> 2016-04-04 11:12:13,725 INFO  [c.c.v.VirtualMachineManagerImpl]
> (Work-Job-Executor-45:ctx-dc665cdb job-1388/job-1389 ctx-c61ce7b1)
> Migration was unsuccessful.  Cleaning up: VM[User|i-2-28-VM]
>
> In the new host I found a file called "/etc/libvirt/qemu/i-2-28-VM.xml"
> which contains the reference ID
> "23feaae3-d709-45a9-b9dd-a295f87d815c".
>
> Where can I search for the problem?
>
> Regards,
> Ugo
>
> --
>
>   U g o   V a s i
>   P r o c n e  s.r.l>)
>   via Cotonificio 45  33010 Tavagnacco IT
>   phone: +390432486523 fax: +390432486523
>
> Le informazioni contenute in questo messaggio sono riservate e
> confidenziali ed è vietata la diffusione in qualunque modo eseguita.
> Qualora Lei non fosse la persona a cui il presente messaggio è
> destinato, La invitiamo ad eliminarlo e a non leggerlo, dandocene
> gentilmente comunicazione.
> Per qualsiasi informazione si prega di contattare supp...@procne.it .
> Rif. D.L. 196/2003
>
>


-- 
Rafael Weingärtner


RE: Cloudstack 4.7 password reset issue.

2016-04-04 Thread Suresh Sadhu
This look like an issue, please check the VR password file 
(/var/cache/cloud/passwords) and entries look like below: Guest_vm_ip=Password)
Eg:
10.1.1.145=sX3qvbstr--- here, In this case it  successfully 
generated the password  but didn't applied on Guest vm
10.1.1.135=saved_password-- if it  applied successfully on VM  then it 
will show as  guest_vm_ip=Saved_password.)

So please check you entries as well check your logs for any errors. 

Regards
Sadhu
Chief Product Engineer, Accelerite
suresh.sa...@accelerite.com


-Original Message-
From: Erik Weber [mailto:terbol...@gmail.com] 
Sent: Monday, April 4, 2016 11:54 AM
To: users@cloudstack.apache.org
Subject: Re: Cloudstack 4.7 password reset issue.

On Mon, Apr 4, 2016 at 7:28 AM, Shweta Agarwal < 
shweta.agarw...@accelerite.com> wrote:

> Hi Richard,
> Cloudstack is working as expected at every steps you mentioned .
>
> when your template is password enabled  then every time you reset 
> password via CS and stop start the VM then router will push new 
> password to the user VM .
>

This works, but if you read his example you will see that the password is reset 
after an additional reboot, which it should not.

Looks like a bug, but more info is needed to state if it is in CloudStack or 
the password reset script.

--
Erik



DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Accelerite, a Persistent Systems business. It is intended only for 
the use of the individual or entity to which it is addressed. If you are not 
the intended recipient, you are not authorized to read, retain, copy, print, 
distribute or use this message. If you have received this communication in 
error, please notify the sender and delete all copies of this message. 
Accelerite, a Persistent Systems business does not accept any liability for 
virus infected mails.


Migration was unsuccessful.

2016-04-04 Thread Ugo Vasi

Hi all,
I've added a new host agent to a cluster (cloudstack 4.5.2 on Ubuntu 14.04).

Today, try migrating a VM from another host to the new one, the 
migration fails with these messages:


2016-04-04 11:12:13,725 DEBUG [c.c.a.t.Request] 
(AgentManager-Handler-7:null) Seq 12-5945595933059225023: Processing:  { 
Ans: , MgmtId: 113359592708, via: 12, Ver: v1, Flags: 10, 
[{"com.cloud.agent.api.MigrateAnswer":{"result":false,"details":"org.libvirt.LibvirtException: 
operation failed: domain 'i-2-28-VM' already exists with uuid 
23feaae3-d709-45a9-b9dd-a295f87d815c","wait":0}}] }
2016-04-04 11:12:13,725 DEBUG [c.c.a.t.Request] 
(Work-Job-Executor-45:ctx-dc665cdb job-1388/job-1389 ctx-c61ce7b1) Seq 
12-5945595933059225023: Received:  { Ans: , MgmtId: 113359592708, via: 
12, Ver: v1, Flags: 10, { MigrateAnswer } }
2016-04-04 11:12:13,725 INFO  [c.c.v.VirtualMachineManagerImpl] 
(Work-Job-Executor-45:ctx-dc665cdb job-1388/job-1389 ctx-c61ce7b1) 
Migration was unsuccessful.  Cleaning up: VM[User|i-2-28-VM]


In the new host I found a file called "/etc/libvirt/qemu/i-2-28-VM.xml" 
which contains the reference ID 
"23feaae3-d709-45a9-b9dd-a295f87d815c".


Where can I search for the problem?

Regards,
Ugo

--

  U g o   V a s i
  P r o c n e  s.r.l>)
  via Cotonificio 45  33010 Tavagnacco IT
  phone: +390432486523 fax: +390432486523

Le informazioni contenute in questo messaggio sono riservate e
confidenziali ed è vietata la diffusione in qualunque modo eseguita.
Qualora Lei non fosse la persona a cui il presente messaggio è
destinato, La invitiamo ad eliminarlo e a non leggerlo, dandocene
gentilmente comunicazione.
Per qualsiasi informazione si prega di contattare supp...@procne.it .
Rif. D.L. 196/2003



RE: SSVM cant route to MS, Iptables keep self-updating

2016-04-04 Thread Glenn Wagner
Hi,

Can you ping the default gateway of the SSVM?
Can you ping google DNS 8.8.8.8 from the SSVM?

Thanks 
Glenn


Regards,

Glenn Wagner

glenn.wag...@shapeblue.com 
www.shapeblue.com
2nd Floor, Oudehuis Centre, 122 Main Rd, Somerset West, Cape Town  7130South 
Africa
@shapeblue

-Original Message-
From: Syafiq Rokman [mailto:msyafiq.rok...@gmail.com] 
Sent: Monday, 04 April 2016 11:16 AM
To: users@cloudstack.apache.org
Subject: SSVM cant route to MS, Iptables keep self-updating

Hi everyone!

Im running CS 4.8 on Ubuntu 14.04 LTS.

So I've managed to set up everything, but I still cant install templates.
So I SSH-ed into the SSVM and ran the healthcheck and it seems that the SSVM 
can't connect to the DNS.

Logs says that it can't route to host.

So I've tried to allow all outgoing/incoming connections on Iptables, but it 
keeps changing back to deny outgoing connections.

Any ideas on how to proceed?

Will provide logs if anyone needs it.

Thanks
Syafiq Rokman
B.ICT Student


Lock New VM provision on specific HOST

2016-04-04 Thread Cristian Ciobanu
  I have a question regarding provisioning limit, what will be the best
method to lock provisioning on a specific host, for example I have 4 VM's on
one HOST, but I don't want to allocate new VM's on it even if I have free
resources on it. can this to be done by doing "disable host" ? will this
affect in some ways the current allocated VM's ?

 

 

  Thank you !

 

Regards,

Cristian

 



SSVM cant route to MS, Iptables keep self-updating

2016-04-04 Thread Syafiq Rokman
Hi everyone!

Im running CS 4.8 on Ubuntu 14.04 LTS.

So I've managed to set up everything, but I still cant install templates.
So I SSH-ed into the SSVM and ran the healthcheck and it seems that the
SSVM can't connect to the DNS.

Logs says that it can't route to host.

So I've tried to allow all outgoing/incoming connections on Iptables, but
it keeps changing back to deny outgoing connections.

Any ideas on how to proceed?

Will provide logs if anyone needs it.

Thanks
Syafiq Rokman
B.ICT Student


Re: Host Tags

2016-04-04 Thread Shweta Agarwal
Hi Sam,
There is no way we can change already created offerings. You can only create 
new offerings with the required tags and use them.

Thanks
Shweta
Principal Product Engineer, CloudPlatform
Accelerite


From: S. Reddit 
Sent: Monday, April 4, 2016 2:08 PM
To: users@cloudstack.apache.org
Subject: Host Tags

Hi List

I need to implement Host Tags in a running environment where existing
service offerings do not have any tags registered. While I can add tags to
hosts anytime, I haven't found a way to add those to offerings... Is there
a way to add tags to the existing offerings or do I have to delete and
recreate those with the respective tags in place?

Best regards,
Sam



DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Accelerite, a Persistent Systems business. It is intended only for 
the use of the individual or entity to which it is addressed. If you are not 
the intended recipient, you are not authorized to read, retain, copy, print, 
distribute or use this message. If you have received this communication in 
error, please notify the sender and delete all copies of this message. 
Accelerite, a Persistent Systems business does not accept any liability for 
virus infected mails.


Host Tags

2016-04-04 Thread S. Reddit
Hi List

I need to implement Host Tags in a running environment where existing
service offerings do not have any tags registered. While I can add tags to
hosts anytime, I haven't found a way to add those to offerings... Is there
a way to add tags to the existing offerings or do I have to delete and
recreate those with the respective tags in place?

Best regards,
Sam


Re: Secondary Storage VM overloaded

2016-04-04 Thread christian.kirmse
Hi Glenn,

ok, thanks for the information.
So this means we are talking about network sessions, good to know.

Tanks for your help.

Kind regards
Christian

> On 04 Apr 2016, at 09:25, Glenn Wagner  wrote:
> 
> Hi,
> 
> To find out how many sessions are connected to the SSVM you can run 
> 
> netstat -anp | grep ESTABLISHED
> 
> Thanks
> Glenn
> 
> 
> Regards,
> 
> Glenn Wagner
> 
> glenn.wag...@shapeblue.com 
> www.shapeblue.com
> 2nd Floor, Oudehuis Centre, 122 Main Rd, Somerset West, Cape Town  7130South 
> Africa
> @shapeblue
> 
> -Original Message-
> From: christian.kir...@zv.fraunhofer.de 
> [mailto:christian.kir...@zv.fraunhofer.de] 
> Sent: Monday, 04 April 2016 9:21 AM
> To: users@cloudstack.apache.org
> Subject: Re: Secondary Storage VM overloaded
> 
> Hi Dag,
> 
> thanks for your reply.
> 
> Unfortunately we actually don’t have a clue what kind of sessions are meant.
> Do we need to monitor ssh sessions, linux processes or some kind of java 
> sessions?
> 
> Do you have any idea where we can start?
> 
> Kind Regards
> Christian
> 
>> On 01 Apr 2016, at 12:19, Dag Sonstebo  wrote:
>> 
>> Hi Christian,
>> 
>> I think to find the actual usage figures over time you would have to monitor 
>> the sessions locally on the SSVM, I can't see anything in the API to query 
>> this.
>> 
>> One way to determine this is to lower the secstorage.sessions.max figure and 
>> monitor how often a second SSVM is spawned. Also keep in mind you could 
>> increase the service offering for system VMs to increase the capacity the 
>> SSVM can handle, this could negate the requirement for multiple SSVM 
>> instances.
>> 
>> Dag Sonstebo
>> Cloud Architect
>> ShapeBlue
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> On 01/04/2016, 10:10, "christian.kir...@zv.fraunhofer.de" 
>>  wrote:
>> 
>>> Hi all,
>>> 
>>> I have a question regarding the scalability of the ssvm.
>>> As I understood cloudstack is able to scale out the ssvm, so that a new one 
>>> is created when the load is to high.
>>> To achieve this we have to edit the two global settings 
>>> secstorage.capacity.standby and secstorage.session.max, but we have no idea 
>>> what values are rational.
>>> 
>>> Is there a way to see the current values, so that we can derive the new 
>>> value which we want to use?
>>> I mean if the current ssvm needs just 10 sessions to be overloaded and we 
>>> set the secstorage.session.max to 20, cloudstack will never spawn a new 
>>> ssvm.
>>> 
>>> Kind Regards
>>> Christian
>> 
>> Regards,
>> 
>> Dag Sonstebo
>> 
>> dag.sonst...@shapeblue.com
>> www.shapeblue.com
>> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
> 



RE: Secondary Storage VM overloaded

2016-04-04 Thread Glenn Wagner
Hi,

To find out how many sessions are connected to the SSVM you can run 

netstat -anp | grep ESTABLISHED

Thanks
Glenn


Regards,

Glenn Wagner

glenn.wag...@shapeblue.com 
www.shapeblue.com
2nd Floor, Oudehuis Centre, 122 Main Rd, Somerset West, Cape Town  7130South 
Africa
@shapeblue

-Original Message-
From: christian.kir...@zv.fraunhofer.de 
[mailto:christian.kir...@zv.fraunhofer.de] 
Sent: Monday, 04 April 2016 9:21 AM
To: users@cloudstack.apache.org
Subject: Re: Secondary Storage VM overloaded

Hi Dag,

thanks for your reply.

Unfortunately we actually don’t have a clue what kind of sessions are meant.
Do we need to monitor ssh sessions, linux processes or some kind of java 
sessions?

Do you have any idea where we can start?

Kind Regards
Christian

> On 01 Apr 2016, at 12:19, Dag Sonstebo  wrote:
> 
> Hi Christian,
> 
> I think to find the actual usage figures over time you would have to monitor 
> the sessions locally on the SSVM, I can't see anything in the API to query 
> this.
> 
> One way to determine this is to lower the secstorage.sessions.max figure and 
> monitor how often a second SSVM is spawned. Also keep in mind you could 
> increase the service offering for system VMs to increase the capacity the 
> SSVM can handle, this could negate the requirement for multiple SSVM 
> instances.
> 
> Dag Sonstebo
> Cloud Architect
> ShapeBlue
> 
> 
> 
> 
> 
> 
> 
> On 01/04/2016, 10:10, "christian.kir...@zv.fraunhofer.de" 
>  wrote:
> 
>> Hi all,
>> 
>> I have a question regarding the scalability of the ssvm.
>> As I understood cloudstack is able to scale out the ssvm, so that a new one 
>> is created when the load is to high.
>> To achieve this we have to edit the two global settings 
>> secstorage.capacity.standby and secstorage.session.max, but we have no idea 
>> what values are rational.
>> 
>> Is there a way to see the current values, so that we can derive the new 
>> value which we want to use?
>> I mean if the current ssvm needs just 10 sessions to be overloaded and we 
>> set the secstorage.session.max to 20, cloudstack will never spawn a new ssvm.
>> 
>> Kind Regards
>> Christian
> 
> Regards,
> 
> Dag Sonstebo
> 
> dag.sonst...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue



Re: Secondary Storage VM overloaded

2016-04-04 Thread christian.kirmse
Hi Dag,

thanks for your reply.

Unfortunately we actually don’t have a clue what kind of sessions are meant.
Do we need to monitor ssh sessions, linux processes or some kind of java 
sessions?

Do you have any idea where we can start?

Kind Regards
Christian

> On 01 Apr 2016, at 12:19, Dag Sonstebo  wrote:
> 
> Hi Christian,
> 
> I think to find the actual usage figures over time you would have to monitor 
> the sessions locally on the SSVM, I can't see anything in the API to query 
> this.
> 
> One way to determine this is to lower the secstorage.sessions.max figure and 
> monitor how often a second SSVM is spawned. Also keep in mind you could 
> increase the service offering for system VMs to increase the capacity the 
> SSVM can handle, this could negate the requirement for multiple SSVM 
> instances.
> 
> Dag Sonstebo
> Cloud Architect
> ShapeBlue
> 
> 
> 
> 
> 
> 
> 
> On 01/04/2016, 10:10, "christian.kir...@zv.fraunhofer.de" 
>  wrote:
> 
>> Hi all,
>> 
>> I have a question regarding the scalability of the ssvm.
>> As I understood cloudstack is able to scale out the ssvm, so that a new one 
>> is created when the load is to high.
>> To achieve this we have to edit the two global settings 
>> secstorage.capacity.standby and secstorage.session.max, but we have no idea 
>> what values are rational.
>> 
>> Is there a way to see the current values, so that we can derive the new 
>> value which we want to use?
>> I mean if the current ssvm needs just 10 sessions to be overloaded and we 
>> set the secstorage.session.max to 20, cloudstack will never spawn a new ssvm.
>> 
>> Kind Regards
>> Christian
> 
> Regards,
> 
> Dag Sonstebo
> 
> dag.sonst...@shapeblue.com 
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue



Re: Cloudstack 4.7 password reset issue.

2016-04-04 Thread Erik Weber
On Mon, Apr 4, 2016 at 7:28 AM, Shweta Agarwal <
shweta.agarw...@accelerite.com> wrote:

> Hi Richard,
> Cloudstack is working as expected at every steps you mentioned .
>
> when your template is password enabled  then every time you reset password
> via CS and stop start the VM then router will push new password to the user
> VM .
>

This works, but if you read his example you will see that the password is
reset after an additional reboot, which it should not.

Looks like a bug, but more info is needed to state if it is in CloudStack
or the password reset script.

-- 
Erik