[URGENT] Unable to stop/start system VMs after upgrade to 4.2.0

2013-10-03 Thread Indra Pramana
Dear all,

I am now in the progress of upgrading my CloudStack from 4.1.1 to 4.2.0.
Running cloudstack-sysvmadm can restart the SSVM, but failed to restart the
CPVM and all the VRs.


[1] 3152
root@cs-mgmt-01:~/backup/20131003# tail -f sysvm.log
nohup: ignoring input
/usr/bin/cloudstack-sysvmadm: line 21: /etc/rc.d/init.d/functions: No such
file or directory

Stopping and starting 1 secondary storage vm(s)...
Done stopping and starting secondary storage vm(s)

Stopping and starting 1 console proxy vm(s)...
ERROR: Failed to stop console proxy vm with id 1980

Done stopping and starting console proxy vm(s) .

Stopping and starting 0 running routing vm(s)...


SSVM seems OK, I have run health check script and everything is in order.

VM state of CPVM is running, but state is disconnected. I can't stop or
destroy the CPVM.

All the VRs are running now but I am not too sure if they are already using
the new 4.2 template or still using the old template, since it seems the
sysvmadm script was unable to detect the virtual routers.

Anyone can help?

Thank you.


Re: [URGENT] Unable to stop/start system VMs after upgrade to 4.2.0

2013-10-03 Thread Indra Pramana
Dear all,

I managed to fix the VRs issue by destroying the routers and restarting the
networks associated to the routers.

Only left is the CPVM, I am not able to stop/destroy it. Any advise?

Looking forward to your reply, thank you.

Cheers.



On Thu, Oct 3, 2013 at 8:16 PM, Indra Pramana in...@sg.or.id wrote:

 Dear all,

 I am now in the progress of upgrading my CloudStack from 4.1.1 to 4.2.0.
 Running cloudstack-sysvmadm can restart the SSVM, but failed to restart the
 CPVM and all the VRs.

 
 [1] 3152
 root@cs-mgmt-01:~/backup/20131003# tail -f sysvm.log
 nohup: ignoring input
 /usr/bin/cloudstack-sysvmadm: line 21: /etc/rc.d/init.d/functions: No such
 file or directory

 Stopping and starting 1 secondary storage vm(s)...
 Done stopping and starting secondary storage vm(s)

 Stopping and starting 1 console proxy vm(s)...
 ERROR: Failed to stop console proxy vm with id 1980

 Done stopping and starting console proxy vm(s) .

 Stopping and starting 0 running routing vm(s)...
 

 SSVM seems OK, I have run health check script and everything is in order.

 VM state of CPVM is running, but state is disconnected. I can't stop or
 destroy the CPVM.

 All the VRs are running now but I am not too sure if they are already
 using the new 4.2 template or still using the old template, since it seems
 the sysvmadm script was unable to detect the virtual routers.

 Anyone can help?

 Thank you.



Assign instance to another account

2013-10-03 Thread Chris Sciarrino
Hi,

Is it possible to assign a VM to another user through the cloudstack web
interface?

For example if I had a request from a user to have an instance deployed for
them, I would be able to deploy it as the admin and then assign it to their
account so that they would still be able to control the VM (power on/off,
snapshots etc).

I have seen references that it is possible to do this but can't seem to
find the option.


Re: [URGENT] Unable to stop/start system VMs after upgrade to 4.2.0

2013-10-03 Thread Dean Kamali
Hi Indra

did you destroy them manually? or you were able to get the script to do
that for you?


On Thu, Oct 3, 2013 at 8:22 AM, Indra Pramana in...@sg.or.id wrote:

 Dear all,

 I managed to fix the VRs issue by destroying the routers and restarting the
 networks associated to the routers.

 Only left is the CPVM, I am not able to stop/destroy it. Any advise?

 Looking forward to your reply, thank you.

 Cheers.



 On Thu, Oct 3, 2013 at 8:16 PM, Indra Pramana in...@sg.or.id wrote:

  Dear all,
 
  I am now in the progress of upgrading my CloudStack from 4.1.1 to 4.2.0.
  Running cloudstack-sysvmadm can restart the SSVM, but failed to restart
 the
  CPVM and all the VRs.
 
  
  [1] 3152
  root@cs-mgmt-01:~/backup/20131003# tail -f sysvm.log
  nohup: ignoring input
  /usr/bin/cloudstack-sysvmadm: line 21: /etc/rc.d/init.d/functions: No
 such
  file or directory
 
  Stopping and starting 1 secondary storage vm(s)...
  Done stopping and starting secondary storage vm(s)
 
  Stopping and starting 1 console proxy vm(s)...
  ERROR: Failed to stop console proxy vm with id 1980
 
  Done stopping and starting console proxy vm(s) .
 
  Stopping and starting 0 running routing vm(s)...
  
 
  SSVM seems OK, I have run health check script and everything is in order.
 
  VM state of CPVM is running, but state is disconnected. I can't stop or
  destroy the CPVM.
 
  All the VRs are running now but I am not too sure if they are already
  using the new 4.2 template or still using the old template, since it
 seems
  the sysvmadm script was unable to detect the virtual routers.
 
  Anyone can help?
 
  Thank you.
 



Re: Cloudstack 4.1

2013-10-03 Thread motty cruz
Thank for your reply, here is what i get on the logs:

2013-10-03 06:07:22,285 DEBUG [cloud.vm.VirtualMachineManagerImpl]
(Job-Executor-8:job-92) Cleaning up resources for the vm VM[User|zee] in
Starting state
2013-10-03 06:07:22,289 DEBUG [agent.transport.Request]
(Job-Executor-8:job-92) Seq 5-1150027132: Sending  { Cmd , MgmtId:
73644477032, via: 5, Ver: v1, Flags: 100111,
[{StopCommand:{isProxy:false,vmName:i-2-18-VM,wait:0}}] }
2013-10-03 06:07:22,426 DEBUG [agent.transport.Request]
(AgentManager-Handler-13:null) Seq 5-1150027132: Processing:  { Ans: ,
MgmtId: 73644477032, via: 5, Ver: v1, Flags: 110,
[{StopAnswer:{vncPort:0,result:true,wait:0}}] }
2013-10-03 06:07:22,426 DEBUG [agent.manager.AgentAttache]
(AgentManager-Handler-13:null) Seq 5-1150027132: No more commands found
2013-10-03 06:07:22,426 DEBUG [agent.transport.Request]
(Job-Executor-8:job-92) Seq 5-1150027132: Received:  { Ans: , MgmtId:
73644477032, via: 5, Ver: v1, Flags: 110, { StopAnswer } }
2013-10-03 06:07:22,435 DEBUG [db.Transaction.Transaction]
(Job-Executor-8:job-92) Rolling back the transaction: Time = 4 Name =
 
-AsyncJobManagerImpl$1.run:401-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRun:334-FutureTask.run:166-ThreadPoolExecutor.runWorker:1146-ThreadPoolExecutor$Worker.run:615-Thread.run:679;
called by
-Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.close:657-TransactionContextBuilder.interceptComplete:56-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:131-NetworkManagerImpl.release:1687-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-VirtualMachineManagerImpl.cleanup:962-VirtualMachineManagerImpl.advanceStart:850-VirtualMachineManagerImpl.start:471-VMEntityManagerImpl.deployVirtualMachine:212-VirtualMachineEntityImpl.deploy:209
2013-10-03 06:07:22,440 DEBUG [db.Transaction.Transaction]
(Job-Executor-8:job-92) Rolling back the transaction: Time = 4 Name =
 
-AsyncJobManagerImpl$1.run:401-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRun:334-FutureTask.run:166-ThreadPoolExecutor.runWorker:1146-ThreadPoolExecutor$Worker.run:615-Thread.run:679;
called by
-Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.close:657-TransactionContextBuilder.interceptComplete:56-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:131-NetworkManagerImpl.release:1687-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-VirtualMachineManagerImpl.cleanup:962-VirtualMachineManagerImpl.advanceStart:850-VirtualMachineManagerImpl.start:471-VMEntityManagerImpl.deployVirtualMachine:212-VirtualMachineEntityImpl.deploy:209
2013-10-03 06:07:22,441 DEBUG [cloud.vm.VirtualMachineManagerImpl]
(Job-Executor-8:job-92) Successfully released network resources for the vm
VM[User|zee]
2013-10-03 06:07:22,441 DEBUG [cloud.vm.VirtualMachineManagerImpl]
(Job-Executor-8:job-92) Successfully cleanued up resources for the vm
VM[User|zee] in Starting state
2013-10-03 06:07:22,443 DEBUG [cloud.deploy.FirstFitPlanner]
(Job-Executor-8:job-92) DataCenter id = '3' provided is in avoid set,
DeploymentPlanner cannot allocate the VM, returning.
2013-10-03 06:07:22,460 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-8:job-92) VM state transitted from :Starting to Stopped with
event: OperationFailedvm's original host id: null new host id: null host id
before state transition: 5
2013-10-03 06:07:22,468 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-8:job-92) Hosts's actual total CPU: 48000 and CPU after
applying overprovisioning: 48000
2013-10-03 06:07:22,468 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-8:job-92) release cpu from host: 5, old used: 4,reserved: 0,
actual total: 48000, total with overprovisioning: 48000; new used:
0,reserved:0; movedfromreserved: false,moveToReserveredfalse
2013-10-03 06:07:22,468 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-8:job-92) release mem from host: 5, old used:
2147483648,reserved: 0, total: 67521658880; new used: 0,reserved:0;
movedfromreserved: false,moveToReserveredfalse
2013-10-03 06:07:22,477 DEBUG [cloud.vm.UserVmManagerImpl]
(Job-Executor-8:job-92) Destroying vm VM[User|zee] as it failed to create
on Host with Id:null
2013-10-03 06:07:22,493 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-8:job-92) VM state transitted from :Stopped to Error with
event: OperationFailedToErrorvm's original host id: null new host id: null
host id before state transition: null
2013-10-03 06:07:22,609 INFO  [user.vm.DeployVMCmd] (Job-Executor-8:job-92)
com.cloud.exception.InsufficientServerCapacityException: Unable to create a
deployment for VM[User|zee]Scope=interface com.cloud.dc.DataCenter; id=3



On Wed, Oct 2, 2013 at 8:34 PM, Kirk Kosinski kirkkosin...@gmail.comwrote:

 Hi, the log shows a VM being destroyed, which doesn't match the
 description of the problem.  If the description is correct, upload more
 of the load to Pastebin.  The log that needs to be provided will 

Cloudstack 4.0 after power|cooling loss

2013-10-03 Thread Old, Curtis
Guys,

My lab took a hit this morning the air handler for my lab crapped out,
temp was over a 100 in the lab.  Servers powering off or bouncing.
Cloudstack 4.0 is backup, but out of the 10 compute nodes (5 KVM, 5
Xenserver) the Xenserver nodes keep going into Alert or Connecting state.
Is there anything specific I should try?

Curtis Old 





Re: Assign instance to another account

2013-10-03 Thread murali reddy
http://cloudstack.apache.org/docs/api/apidocs-4.0.0/root_admin/assignVirtualMachine.html


On Thu, Oct 3, 2013 at 6:06 PM, Chris Sciarrino
chris.sciarr...@gmail.comwrote:

 Hi,

 Is it possible to assign a VM to another user through the cloudstack web
 interface?

 For example if I had a request from a user to have an instance deployed for
 them, I would be able to deploy it as the admin and then assign it to their
 account so that they would still be able to control the VM (power on/off,
 snapshots etc).

 I have seen references that it is possible to do this but can't seem to
 find the option.



Re: Cloudstack 4.0 after power|cooling loss

2013-10-03 Thread Old, Curtis
Also noticed Console Proxy VM stuck in staring state (runs on KVM node)

Curtis Old 
Neustar, Inc. / Neustarlabs / Senior Research Engineer
46000 Center Oak Plaza Sterling, VA 20166
Office: +1.571.434.5384 Mobile: +1.540.532.2230 / curtis@neustar.biz
/ www.neustar.biz http://www.neustar.biz/



The information contained in this e-mail message is intended only for the
use of the recipient(s) named above and may contain confidential and/or
privileged information. If you are not the intended recipient you have
received this e-mail message in error and any review, dissemination,
distribution, or copying of this message is strictly prohibited. If you
have received this communication in error, please notify us immediately
and delete the original message.





On 10/3/13 9:26 AM, Old, Curtis curtis@neustar.biz wrote:

Guys,

   My lab took a hit this morning the air handler for my lab crapped out,
temp was over a 100 in the lab.  Servers powering off or bouncing.
Cloudstack 4.0 is backup, but out of the 10 compute nodes (5 KVM, 5
Xenserver) the Xenserver nodes keep going into Alert or Connecting state.
Is there anything specific I should try?

Curtis Old 






Re: Assign instance to another account

2013-10-03 Thread Chris Sciarrino
Okay thanks for confirming. I will submit a feature request for it, this
seems like something that should be available through the UI.


On Thu, Oct 3, 2013 at 9:39 AM, Dean Kamali dean.kam...@gmail.com wrote:

 you will need to do that using the api it is not possible to via UI as far
 as I know.


 On Thu, Oct 3, 2013 at 8:36 AM, Chris Sciarrino
 chris.sciarr...@gmail.comwrote:

  Hi,
 
  Is it possible to assign a VM to another user through the cloudstack web
  interface?
 
  For example if I had a request from a user to have an instance deployed
 for
  them, I would be able to deploy it as the admin and then assign it to
 their
  account so that they would still be able to control the VM (power on/off,
  snapshots etc).
 
  I have seen references that it is possible to do this but can't seem to
  find the option.
 



[URGENT] Mounting issues from KVM hosts to secondary storage

2013-10-03 Thread Indra Pramana
Dear all,

We face a major problem after upgrading to 4.2.0. Mounting from KVM hosts
to secondary storage seems to fail, every time a new VM instance is
created, it will use up the / (root) partition of the KVM hosts instead.

Here is the df result:


root@hv-kvm-02:/home/indra# df
Filesystem  1K-blocksUsed
Available Use% Mounted on
/dev/sda1 4195924
4195924 0 100% /
udev132053356   4
132053352   1% /dev
tmpfs52825052 440
52824612   1% /run
none 5120
0  5120   0% /run/lock
none132062620   0
132062620   0% /run/shm
cgroup  132062620   0
132062620   0% /sys/fs/cgroup
/dev/sda610650544 2500424
7609092  25% /home
10.237.11.31:/mnt/vol1/sec-storage2/template/tmpl/2/288   4195924
4195924 0 100% /mnt/5230667e-9c58-3ff6-983c-5fc2a72df669


The strange thing is that df shows that it seems to be mounted, but it's
actually not mounted. If you noticed, the total capacity of the mount point
is exactly the same as the capacity of the / (root) partition. By right it
should show 7 TB instead of just 4 GB.

This caused VM creation to be error due to out of disk space. This also
affect the KVM operations since the / (root) partition becomes full, and we
can only release the space after we reboot the KVM host.

Anyone experience this problem before? We are at loss on how to resolve the
problem.

Looking forward to your reply, thank you.

Cheers.


Re: [URGENT] Mounting issues from KVM hosts to secondary storage

2013-10-03 Thread Dean Kamali
have you looked at storage over-provisioning settings ??


On Thu, Oct 3, 2013 at 11:53 AM, Indra Pramana in...@sg.or.id wrote:

 Dear all,

 We face a major problem after upgrading to 4.2.0. Mounting from KVM hosts
 to secondary storage seems to fail, every time a new VM instance is
 created, it will use up the / (root) partition of the KVM hosts instead.

 Here is the df result:

 
 root@hv-kvm-02:/home/indra# df
 Filesystem  1K-blocksUsed
 Available Use% Mounted on
 /dev/sda1 4195924
 4195924 0 100% /
 udev132053356   4
 132053352   1% /dev
 tmpfs52825052 440
 52824612   1% /run
 none 5120
 0  5120   0% /run/lock
 none132062620   0
 132062620   0% /run/shm
 cgroup  132062620   0
 132062620   0% /sys/fs/cgroup
 /dev/sda610650544 2500424
 7609092  25% /home
 10.237.11.31:/mnt/vol1/sec-storage2/template/tmpl/2/288   4195924
 4195924 0 100% /mnt/5230667e-9c58-3ff6-983c-5fc2a72df669
 

 The strange thing is that df shows that it seems to be mounted, but it's
 actually not mounted. If you noticed, the total capacity of the mount point
 is exactly the same as the capacity of the / (root) partition. By right it
 should show 7 TB instead of just 4 GB.

 This caused VM creation to be error due to out of disk space. This also
 affect the KVM operations since the / (root) partition becomes full, and we
 can only release the space after we reboot the KVM host.

 Anyone experience this problem before? We are at loss on how to resolve the
 problem.

 Looking forward to your reply, thank you.

 Cheers.



Re: [URGENT] Mounting issues from KVM hosts to secondary storage

2013-10-03 Thread Marcus Sorensen
Are you using the release artifacts, or your own 4.2 build?

When you rebooted the host, did the problem go away or come back the
same? You may want to look at 'virsh pool-list' to see if libvirt is
mounting/registering the secondary storage.

Is this happening on multiple hosts, the same way? You may want to
look at /etc/mtab, if the system reports it's mounted, though it's
not, it might be in there. Look at /proc/mounts as well.

On Thu, Oct 3, 2013 at 9:53 AM, Indra Pramana in...@sg.or.id wrote:
 Dear all,

 We face a major problem after upgrading to 4.2.0. Mounting from KVM hosts
 to secondary storage seems to fail, every time a new VM instance is
 created, it will use up the / (root) partition of the KVM hosts instead.

 Here is the df result:

 
 root@hv-kvm-02:/home/indra# df
 Filesystem  1K-blocksUsed
 Available Use% Mounted on
 /dev/sda1 4195924
 4195924 0 100% /
 udev132053356   4
 132053352   1% /dev
 tmpfs52825052 440
 52824612   1% /run
 none 5120
 0  5120   0% /run/lock
 none132062620   0
 132062620   0% /run/shm
 cgroup  132062620   0
 132062620   0% /sys/fs/cgroup
 /dev/sda610650544 2500424
 7609092  25% /home
 10.237.11.31:/mnt/vol1/sec-storage2/template/tmpl/2/288   4195924
 4195924 0 100% /mnt/5230667e-9c58-3ff6-983c-5fc2a72df669
 

 The strange thing is that df shows that it seems to be mounted, but it's
 actually not mounted. If you noticed, the total capacity of the mount point
 is exactly the same as the capacity of the / (root) partition. By right it
 should show 7 TB instead of just 4 GB.

 This caused VM creation to be error due to out of disk space. This also
 affect the KVM operations since the / (root) partition becomes full, and we
 can only release the space after we reboot the KVM host.

 Anyone experience this problem before? We are at loss on how to resolve the
 problem.

 Looking forward to your reply, thank you.

 Cheers.


Re: CS 4.2 storage vm

2013-10-03 Thread Laszlo Hornyak
Hi Peter,

The above class is in the vmware plugin, could you check if it is available
in the agent?




On Thu, Oct 3, 2013 at 12:29 AM, Erdősi Péter f...@niif.hu wrote:

 Dear,

 I installed CS 4.2 from rpm packages to Centos 6.4.
 Everything works fine, with install, and with configuration, but after the
 CS deploy the storage VM I can't add ISO-s.

 After some research in the logs I found this on a secstorage system VM:

 s-1-VM: /var/log/cloud.log
 2013-10-02 13:31:19,269 INFO  [cloud.agent.AgentShell] (main:null) Agent
 started
 2013-10-02 13:31:19,273 INFO  [cloud.agent.AgentShell] (main:null)
 Implementation Version is 4.2.0
 2013-10-02 13:31:19,274 INFO  [cloud.agent.AgentShell] (main:null)
 agent.properties found at /usr/local/cloud/systemvm/**
 conf/agent.properties
 2013-10-02 13:31:19,281 DEBUG [cloud.agent.AgentShell] (main:null) Found
 property: instance
 2013-10-02 13:31:19,281 DEBUG [cloud.agent.AgentShell] (main:null) Found
 property: resource
 2013-10-02 13:31:19,281 INFO  [cloud.agent.AgentShell] (main:null)
 Defaulting to using properties file for storage
 2013-10-02 13:31:19,283 INFO  [cloud.agent.AgentShell] (main:null)
 Defaulting to the constant time backoff algorithm
 2013-10-02 13:31:19,290 INFO  [cloud.utils.LogUtils] (main:null) log4j
 configuration found at /usr/local/cloud/systemvm/**conf/log4j-cloud.xml
 2013-10-02 13:31:19,318 DEBUG [cloud.agent.AgentShell] (main:null)
 Checking to see if agent.SecStorage.pid exists.
 2013-10-02 13:31:19,326 DEBUG [cloud.utils.ProcessUtil] (main:null)
 environment.properties could not be opened
 2013-10-02 13:31:19,337 DEBUG [cloud.utils.ProcessUtil] (main:null)
 Executing: bash -c echo $PPID
 2013-10-02 13:31:19,344 DEBUG [cloud.utils.ProcessUtil] (main:null)
 Execution is successful.
 2013-10-02 13:31:19,345 ERROR [cloud.agent.AgentShell] (main:null) *Unable
 to start agent: Resource class not found: com.cloud.storage.resource.**
 PremiumSecondaryStorageResourc**e due to: java.lang.**ClassNotFoundException:
 com.cloud.storage.resource.**PremiumSecondaryStorageResourc**e *


 Can somebody help me with this?

 Thanks,
  Peter ERDOSI




-- 

EOF


Re: [URGENT] Mounting issues from KVM hosts to secondary storage

2013-10-03 Thread Indra Pramana
Hi Marcus,

Good day to you, and thank you for your e-mail. See my reply inline.

On Fri, Oct 4, 2013 at 12:29 AM, Marcus Sorensen shadow...@gmail.comwrote:

 Are you using the release artifacts, or your own 4.2 build?


[Indra:] We are using the release artifacts from below repo since we are
using Ubuntu:

deb http://cloudstack.apt-get.eu/ubuntu precise 4.2


 When you rebooted the host, did the problem go away or come back the
 same?


[Indra:] When I rebooted the host, the problem go away for a while, but it
will come back again after some time. It will come randomly at the time
when we need to create a new instance on that host, or start an existing
stopped instance.


 You may want to look at 'virsh pool-list' to see if libvirt is
 mounting/registering the secondary storage.


[Indra:] This is the result of the virsh pool-list command:

root@hv-kvm-02:/var/log/libvirt# virsh pool-list
Name State  Autostart
-
301071ac-4c1d-4eac-855b-124126da0a38 active no
5230667e-9c58-3ff6-983c-5fc2a72df669 active no
d433809b-01ea-3947-ba0f-48077244e4d6 active no

Strange thing is that none of my secondary storage IDs are there. Could it
be that the ID might have changed during Cloudstack upgrade? Here is the
list of my secondary storage (there are two of them) even though they are
on the same NFS server:
c02da448-b9f4-401b-b8d5-83e8ead5cfdenfs://10.237.11.31/mnt/vol1/sec-storage
NFS 5937edb6-2e95-4ae2-907b-80fe4599ed87nfs://
10.237.11.31/mnt/vol1/sec-storage2NFS

 Is this happening on multiple hosts, the same way?


[Indra:] Yes, it is happening on all the two hosts that I have, the same
way.


 You may want to
 look at /etc/mtab, if the system reports it's mounted, though it's
 not, it might be in there. Look at /proc/mounts as well.


[Indra:] Please find result of df, /etc/mtab and /proc/mounts below. The
ghost mount point is on df and /etc/mtab, but not on /proc/mounts.

root@hv-kvm-02:/etc# df
Filesystem  1K-blocksUsed
Available Use% Mounted on
/dev/sda1 4195924
4192372 0 100% /
udev132053356   4
132053352   1% /dev
tmpfs52825052 704
52824348   1% /run
none 5120
0  5120   0% /run/lock
none132062620   0
132062620   0% /run/shm
cgroup  132062620   0
132062620   0% /sys/fs/cgroup
/dev/sda610650544 2500460
7609056  25% /home
10.237.11.31:/mnt/vol1/sec-storage2/template/tmpl/2/288   4195924
4192372 0 100% /mnt/5230667e-9c58-3ff6-983c-5fc2a72df669

root@hv-kvm-02:/etc# cat /etc/mtab
/dev/sda1 / ext4 rw,errors=remount-ro 0 0
proc /proc proc rw,noexec,nosuid,nodev 0 0
sysfs /sys sysfs rw,noexec,nosuid,nodev 0 0
none /sys/fs/fuse/connections fusectl rw 0 0
none /sys/kernel/debug debugfs rw 0 0
none /sys/kernel/security securityfs rw 0 0
udev /dev devtmpfs rw,mode=0755 0 0
devpts /dev/pts devpts rw,noexec,nosuid,gid=5,mode=0620 0 0
tmpfs /run tmpfs rw,noexec,nosuid,size=10%,mode=0755 0 0
none /run/lock tmpfs rw,noexec,nosuid,nodev,size=5242880 0 0
none /run/shm tmpfs rw,nosuid,nodev 0 0
cgroup /sys/fs/cgroup tmpfs rw,relatime,mode=755 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,relatime,cpuset 0 0
cgroup /sys/fs/cgroup/cpu cgroup rw,relatime,cpu 0 0
cgroup /sys/fs/cgroup/cpuacct cgroup rw,relatime,cpuacct 0 0
cgroup /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,relatime,devices 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,relatime,freezer 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,relatime,blkio 0 0
cgroup /sys/fs/cgroup/perf_event cgroup rw,relatime,perf_event 0 0
/dev/sda6 /home ext4 rw 0 0
rpc_pipefs /run/rpc_pipefs rpc_pipefs rw 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,noexec,nosuid,nodev 0 0
10.237.11.31:/mnt/vol1/sec-storage2/template/tmpl/2/288
/mnt/5230667e-9c58-3ff6-983c-5fc2a72df669 nfs rw,addr=10.237.11.31 0 0

rootfs / rootfs rw 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,relatime,size=132053356k,nr_inodes=33013339,mode=755
0 0
devpts /dev/pts devpts
rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,relatime,size=52825052k,mode=755 0 0
/dev/disk/by-uuid/d21f4676-075d-44be-a378-92ef6aaf2496 / ext4
rw,relatime,errors=remount-ro,data=ordered 0 0
none /sys/fs/fuse/connections fusectl rw,relatime 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0
cgroup /sys/fs/cgroup tmpfs rw,relatime,mode=755 0 0
none /sys/kernel/security securityfs rw,relatime 0 0
none /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
none /run/shm 

Re: [URGENT] Mounting issues from KVM hosts to secondary storage

2013-10-03 Thread Indra Pramana
Hi Marcus and all,

I also find some strange and interesting error messages from the libvirt
logs:

http://pastebin.com/5ByfNpAf

Looking forward to your reply, thank you.

Cheers.



On Fri, Oct 4, 2013 at 1:38 AM, Indra Pramana in...@sg.or.id wrote:

 Hi Marcus,

 Good day to you, and thank you for your e-mail. See my reply inline.

 On Fri, Oct 4, 2013 at 12:29 AM, Marcus Sorensen shadow...@gmail.comwrote:

 Are you using the release artifacts, or your own 4.2 build?


 [Indra:] We are using the release artifacts from below repo since we are
 using Ubuntu:

 deb http://cloudstack.apt-get.eu/ubuntu precise 4.2


 When you rebooted the host, did the problem go away or come back the
 same?


 [Indra:] When I rebooted the host, the problem go away for a while, but it
 will come back again after some time. It will come randomly at the time
 when we need to create a new instance on that host, or start an existing
 stopped instance.


 You may want to look at 'virsh pool-list' to see if libvirt is
 mounting/registering the secondary storage.


 [Indra:] This is the result of the virsh pool-list command:

 root@hv-kvm-02:/var/log/libvirt# virsh pool-list
 Name State  Autostart
 -
 301071ac-4c1d-4eac-855b-124126da0a38 active no
 5230667e-9c58-3ff6-983c-5fc2a72df669 active no
 d433809b-01ea-3947-ba0f-48077244e4d6 active no

 Strange thing is that none of my secondary storage IDs are there. Could it
 be that the ID might have changed during Cloudstack upgrade? Here is the
 list of my secondary storage (there are two of them) even though they are
 on the same NFS server:
   c02da448-b9f4-401b-b8d5-83e8ead5cfde nfs://
 10.237.11.31/mnt/vol1/sec-storage NFS
 5937edb6-2e95-4ae2-907b-80fe4599ed87 nfs://
 10.237.11.31/mnt/vol1/sec-storage2 NFS

 Is this happening on multiple hosts, the same way?


 [Indra:] Yes, it is happening on all the two hosts that I have, the same
 way.


 You may want to
 look at /etc/mtab, if the system reports it's mounted, though it's
 not, it might be in there. Look at /proc/mounts as well.


 [Indra:] Please find result of df, /etc/mtab and /proc/mounts below. The
 ghost mount point is on df and /etc/mtab, but not on /proc/mounts.

 root@hv-kvm-02:/etc# df

 Filesystem  1K-blocksUsed
 Available Use% Mounted on
 /dev/sda1 4195924
 4192372 0 100% /

 udev132053356   4
 132053352   1% /dev
 tmpfs52825052 704
 52824348   1% /run

 none 5120
 0  5120   0% /run/lock
 none132062620   0
 132062620   0% /run/shm
 cgroup  132062620   0
 132062620   0% /sys/fs/cgroup
 /dev/sda610650544
 2500460   7609056  25% /home
 10.237.11.31:/mnt/vol1/sec-storage2/template/tmpl/2/288   4195924
 4192372 0 100% /mnt/5230667e-9c58-3ff6-983c-5fc2a72df669

 root@hv-kvm-02:/etc# cat /etc/mtab
 /dev/sda1 / ext4 rw,errors=remount-ro 0 0
 proc /proc proc rw,noexec,nosuid,nodev 0 0
 sysfs /sys sysfs rw,noexec,nosuid,nodev 0 0
 none /sys/fs/fuse/connections fusectl rw 0 0
 none /sys/kernel/debug debugfs rw 0 0
 none /sys/kernel/security securityfs rw 0 0
 udev /dev devtmpfs rw,mode=0755 0 0
 devpts /dev/pts devpts rw,noexec,nosuid,gid=5,mode=0620 0 0
 tmpfs /run tmpfs rw,noexec,nosuid,size=10%,mode=0755 0 0
 none /run/lock tmpfs rw,noexec,nosuid,nodev,size=5242880 0 0
 none /run/shm tmpfs rw,nosuid,nodev 0 0
 cgroup /sys/fs/cgroup tmpfs rw,relatime,mode=755 0 0
 cgroup /sys/fs/cgroup/cpuset cgroup rw,relatime,cpuset 0 0
 cgroup /sys/fs/cgroup/cpu cgroup rw,relatime,cpu 0 0
 cgroup /sys/fs/cgroup/cpuacct cgroup rw,relatime,cpuacct 0 0
 cgroup /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0
 cgroup /sys/fs/cgroup/devices cgroup rw,relatime,devices 0 0
 cgroup /sys/fs/cgroup/freezer cgroup rw,relatime,freezer 0 0
 cgroup /sys/fs/cgroup/blkio cgroup rw,relatime,blkio 0 0
 cgroup /sys/fs/cgroup/perf_event cgroup rw,relatime,perf_event 0 0
 /dev/sda6 /home ext4 rw 0 0
 rpc_pipefs /run/rpc_pipefs rpc_pipefs rw 0 0
 binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,noexec,nosuid,nodev 0 0
 10.237.11.31:/mnt/vol1/sec-storage2/template/tmpl/2/288
 /mnt/5230667e-9c58-3ff6-983c-5fc2a72df669 nfs rw,addr=10.237.11.31 0 0

 rootfs / rootfs rw 0 0
 sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
 udev /dev devtmpfs rw,relatime,size=132053356k,nr_inodes=33013339,mode=755
 0 0
 devpts /dev/pts devpts
 rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
 tmpfs /run tmpfs rw,nosuid,relatime,size=52825052k,mode=755 0 0
 /dev/disk/by-uuid/d21f4676-075d-44be-a378-92ef6aaf2496 

Re: [URGENT] Mounting issues from KVM hosts to secondary storage

2013-10-03 Thread Marcus Sorensen
It sort of looks like the out of space triggered the issue. Libvirt shows

2013-10-03 15:38:57.414+: 2710: error : virCommandWait:2348 :
internal error Child process (/bin/umount
/mnt/5230667e-9c58-3ff6-983c-5fc2a72df669) unexpected exit status 32:
error writing /etc/mtab.tmp: No space left on device

So that entry of the filesystem being mounted is orphaned in
/etc/mtab, since it can't be removed. That seems to be the source of
why 'df' shows the thing mounted when it isn't, at least.


On Thu, Oct 3, 2013 at 11:45 AM, Indra Pramana in...@sg.or.id wrote:
 Hi Marcus and all,

 I also find some strange and interesting error messages from the libvirt
 logs:

 http://pastebin.com/5ByfNpAf

 Looking forward to your reply, thank you.

 Cheers.



 On Fri, Oct 4, 2013 at 1:38 AM, Indra Pramana in...@sg.or.id wrote:

 Hi Marcus,

 Good day to you, and thank you for your e-mail. See my reply inline.

 On Fri, Oct 4, 2013 at 12:29 AM, Marcus Sorensen shadow...@gmail.comwrote:

 Are you using the release artifacts, or your own 4.2 build?


 [Indra:] We are using the release artifacts from below repo since we are
 using Ubuntu:

 deb http://cloudstack.apt-get.eu/ubuntu precise 4.2


 When you rebooted the host, did the problem go away or come back the
 same?


 [Indra:] When I rebooted the host, the problem go away for a while, but it
 will come back again after some time. It will come randomly at the time
 when we need to create a new instance on that host, or start an existing
 stopped instance.


 You may want to look at 'virsh pool-list' to see if libvirt is
 mounting/registering the secondary storage.


 [Indra:] This is the result of the virsh pool-list command:

 root@hv-kvm-02:/var/log/libvirt# virsh pool-list
 Name State  Autostart
 -
 301071ac-4c1d-4eac-855b-124126da0a38 active no
 5230667e-9c58-3ff6-983c-5fc2a72df669 active no
 d433809b-01ea-3947-ba0f-48077244e4d6 active no

 Strange thing is that none of my secondary storage IDs are there. Could it
 be that the ID might have changed during Cloudstack upgrade? Here is the
 list of my secondary storage (there are two of them) even though they are
 on the same NFS server:
   c02da448-b9f4-401b-b8d5-83e8ead5cfde nfs://
 10.237.11.31/mnt/vol1/sec-storage NFS
 5937edb6-2e95-4ae2-907b-80fe4599ed87 nfs://
 10.237.11.31/mnt/vol1/sec-storage2 NFS

 Is this happening on multiple hosts, the same way?


 [Indra:] Yes, it is happening on all the two hosts that I have, the same
 way.


 You may want to
 look at /etc/mtab, if the system reports it's mounted, though it's
 not, it might be in there. Look at /proc/mounts as well.


 [Indra:] Please find result of df, /etc/mtab and /proc/mounts below. The
 ghost mount point is on df and /etc/mtab, but not on /proc/mounts.

 root@hv-kvm-02:/etc# df

 Filesystem  1K-blocksUsed
 Available Use% Mounted on
 /dev/sda1 4195924
 4192372 0 100% /

 udev132053356   4
 132053352   1% /dev
 tmpfs52825052 704
 52824348   1% /run

 none 5120
 0  5120   0% /run/lock
 none132062620   0
 132062620   0% /run/shm
 cgroup  132062620   0
 132062620   0% /sys/fs/cgroup
 /dev/sda610650544
 2500460   7609056  25% /home
 10.237.11.31:/mnt/vol1/sec-storage2/template/tmpl/2/288   4195924
 4192372 0 100% /mnt/5230667e-9c58-3ff6-983c-5fc2a72df669

 root@hv-kvm-02:/etc# cat /etc/mtab
 /dev/sda1 / ext4 rw,errors=remount-ro 0 0
 proc /proc proc rw,noexec,nosuid,nodev 0 0
 sysfs /sys sysfs rw,noexec,nosuid,nodev 0 0
 none /sys/fs/fuse/connections fusectl rw 0 0
 none /sys/kernel/debug debugfs rw 0 0
 none /sys/kernel/security securityfs rw 0 0
 udev /dev devtmpfs rw,mode=0755 0 0
 devpts /dev/pts devpts rw,noexec,nosuid,gid=5,mode=0620 0 0
 tmpfs /run tmpfs rw,noexec,nosuid,size=10%,mode=0755 0 0
 none /run/lock tmpfs rw,noexec,nosuid,nodev,size=5242880 0 0
 none /run/shm tmpfs rw,nosuid,nodev 0 0
 cgroup /sys/fs/cgroup tmpfs rw,relatime,mode=755 0 0
 cgroup /sys/fs/cgroup/cpuset cgroup rw,relatime,cpuset 0 0
 cgroup /sys/fs/cgroup/cpu cgroup rw,relatime,cpu 0 0
 cgroup /sys/fs/cgroup/cpuacct cgroup rw,relatime,cpuacct 0 0
 cgroup /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0
 cgroup /sys/fs/cgroup/devices cgroup rw,relatime,devices 0 0
 cgroup /sys/fs/cgroup/freezer cgroup rw,relatime,freezer 0 0
 cgroup /sys/fs/cgroup/blkio cgroup rw,relatime,blkio 0 0
 cgroup /sys/fs/cgroup/perf_event cgroup rw,relatime,perf_event 0 0
 /dev/sda6 /home ext4 rw 0 0
 rpc_pipefs /run/rpc_pipefs rpc_pipefs rw 0 0
 binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc 

Re: [URGENT] Mounting issues from KVM hosts to secondary storage

2013-10-03 Thread Indra Pramana
Hi Marcus,

It happens randomly, mounting fails, and then / gets filled. I suspect this
occurs when the mounting fails, any files which is supposed to be
transferred to the mount point (e.g. templates used to create VMs) will
fill-up the / partition of the KVM host instead. This doesn't happen in
4.1.1, this only happens after we upgraded to 4.2.0.

And how about virsh pool-list result which is not reflecting the actual IDs
of the secondary storage we see from Cloudstack GUI, is it supposed to be
the case? If not, how to rectify it?

Looking forward to your reply, thank you.

Cheers.




On Fri, Oct 4, 2013 at 1:51 AM, Marcus Sorensen shadow...@gmail.com wrote:

 It sort of looks like the out of space triggered the issue. Libvirt shows

 2013-10-03 15:38:57.414+: 2710: error : virCommandWait:2348 :
 internal error Child process (/bin/umount
 /mnt/5230667e-9c58-3ff6-983c-5fc2a72df669) unexpected exit status 32:
 error writing /etc/mtab.tmp: No space left on device

 So that entry of the filesystem being mounted is orphaned in
 /etc/mtab, since it can't be removed. That seems to be the source of
 why 'df' shows the thing mounted when it isn't, at least.


 On Thu, Oct 3, 2013 at 11:45 AM, Indra Pramana in...@sg.or.id wrote:
  Hi Marcus and all,
 
  I also find some strange and interesting error messages from the libvirt
  logs:
 
  http://pastebin.com/5ByfNpAf
 
  Looking forward to your reply, thank you.
 
  Cheers.
 
 
 
  On Fri, Oct 4, 2013 at 1:38 AM, Indra Pramana in...@sg.or.id wrote:
 
  Hi Marcus,
 
  Good day to you, and thank you for your e-mail. See my reply inline.
 
  On Fri, Oct 4, 2013 at 12:29 AM, Marcus Sorensen shadow...@gmail.com
 wrote:
 
  Are you using the release artifacts, or your own 4.2 build?
 
 
  [Indra:] We are using the release artifacts from below repo since we are
  using Ubuntu:
 
  deb http://cloudstack.apt-get.eu/ubuntu precise 4.2
 
 
  When you rebooted the host, did the problem go away or come back the
  same?
 
 
  [Indra:] When I rebooted the host, the problem go away for a while, but
 it
  will come back again after some time. It will come randomly at the time
  when we need to create a new instance on that host, or start an existing
  stopped instance.
 
 
  You may want to look at 'virsh pool-list' to see if libvirt is
  mounting/registering the secondary storage.
 
 
  [Indra:] This is the result of the virsh pool-list command:
 
  root@hv-kvm-02:/var/log/libvirt# virsh pool-list
  Name State  Autostart
  -
  301071ac-4c1d-4eac-855b-124126da0a38 active no
  5230667e-9c58-3ff6-983c-5fc2a72df669 active no
  d433809b-01ea-3947-ba0f-48077244e4d6 active no
 
  Strange thing is that none of my secondary storage IDs are there. Could
 it
  be that the ID might have changed during Cloudstack upgrade? Here is the
  list of my secondary storage (there are two of them) even though they
 are
  on the same NFS server:
c02da448-b9f4-401b-b8d5-83e8ead5cfde nfs://
  10.237.11.31/mnt/vol1/sec-storage NFS
  5937edb6-2e95-4ae2-907b-80fe4599ed87 nfs://
  10.237.11.31/mnt/vol1/sec-storage2 NFS
 
  Is this happening on multiple hosts, the same way?
 
 
  [Indra:] Yes, it is happening on all the two hosts that I have, the same
  way.
 
 
  You may want to
  look at /etc/mtab, if the system reports it's mounted, though it's
  not, it might be in there. Look at /proc/mounts as well.
 
 
  [Indra:] Please find result of df, /etc/mtab and /proc/mounts below. The
  ghost mount point is on df and /etc/mtab, but not on /proc/mounts.
 
  root@hv-kvm-02:/etc# df
 
  Filesystem  1K-blocks
  Used
  Available Use% Mounted on
  /dev/sda1 4195924
  4192372 0 100% /
 
  udev132053356
 4
  132053352   1% /dev
  tmpfs52825052
 704
  52824348   1% /run
 
  none 5120
  0  5120   0% /run/lock
  none132062620
 0
  132062620   0% /run/shm
  cgroup  132062620
 0
  132062620   0% /sys/fs/cgroup
  /dev/sda610650544
  2500460   7609056  25% /home
  10.237.11.31:/mnt/vol1/sec-storage2/template/tmpl/2/288   4195924
  4192372 0 100% /mnt/5230667e-9c58-3ff6-983c-5fc2a72df669
 
  root@hv-kvm-02:/etc# cat /etc/mtab
  /dev/sda1 / ext4 rw,errors=remount-ro 0 0
  proc /proc proc rw,noexec,nosuid,nodev 0 0
  sysfs /sys sysfs rw,noexec,nosuid,nodev 0 0
  none /sys/fs/fuse/connections fusectl rw 0 0
  none /sys/kernel/debug debugfs rw 0 0
  none /sys/kernel/security securityfs rw 0 0
  udev /dev devtmpfs rw,mode=0755 0 0
  devpts /dev/pts devpts rw,noexec,nosuid,gid=5,mode=0620 0 0
  tmpfs /run tmpfs 

Create Template on NFS secondary Storage

2013-10-03 Thread Pierre-Luc Dion
Hi all,

We are currently using Cloudstack 4.1.0 managing XenServer 6.0.2 servers.


Since recently, I don't know what cause this to appear on our system but
 went we create a template from a Instance the template (.vhd) is upload on
on the secondary storage (NFS) but in a subdirectory  ex:

from the Storage VM:
/mnt/SecStorage/7f6f1f2d-2d6f-3ec6-a25e-fb25f2704167/template/tmpl/3/246
root@s-184-VM:~# ls -l
total 8
drwxr-xr-x 2 4294967294 4294967294 4096 Oct  3 19:35
02ee28f2-0c02-f936-3ca3-099cfe3f3a20
-rw-rw-rw- 1 4294967294 4294967294  314 Oct  3 19:36 template.properties

root@s-184-VM:~# ls 02ee28f2-0c02-f936-3ca3-099cfe3f3a20/
fe2fa941-3030-412d-8c35-b0e80a2e7e09.vhd


So, when we create a new Instance from the template, the Instance creation
fail with the following error in the management-server.log:

2013-10-03 15:48:01,190 WARN  [xen.resource.CitrixResourceBase]
(DirectAgent-255:null) Catch Exception
com.cloud.utils.exception.CloudRuntimeException on
host:9a02ac57-bc92-43af-b50a-f5ba2d0fd806 for template: nfs://
172.24.1.120/data/secondary/template/tmpl/3/246/fe2fa941-3030-412d-8c35-b0e80a2e7e09.vhddue
to com.cloud.utils.exception.CloudRuntimeException: can not create vdi
in sr 451078ee-d335-bdb0-c41c-cd86524be3ea

if I move the VHD file in the 246 folder, it works !

Does anyone have this problem too  or have an idea of where it would come
from ?

Thanks !


Pierre-Luc Dion
Responsable technique - infrastructure | Technical lead - infrastructure
- - -*
CloudOps
*www.cloudops.com
@CloudOps_


Re: Create Template on NFS secondary Storage

2013-10-03 Thread Travis Graham
Can you check the permissions on the subdirectories?

Travis

On Oct 3, 2013, at 3:51 PM, Pierre-Luc Dion pd...@cloudops.com wrote:

 Hi all,
 
 We are currently using Cloudstack 4.1.0 managing XenServer 6.0.2 servers.
 
 
 Since recently, I don't know what cause this to appear on our system but
 went we create a template from a Instance the template (.vhd) is upload on
 on the secondary storage (NFS) but in a subdirectory  ex:
 
 from the Storage VM:
 /mnt/SecStorage/7f6f1f2d-2d6f-3ec6-a25e-fb25f2704167/template/tmpl/3/246
 root@s-184-VM:~# ls -l
 total 8
 drwxr-xr-x 2 4294967294 4294967294 4096 Oct  3 19:35
 02ee28f2-0c02-f936-3ca3-099cfe3f3a20
 -rw-rw-rw- 1 4294967294 4294967294  314 Oct  3 19:36 template.properties
 
 root@s-184-VM:~# ls 02ee28f2-0c02-f936-3ca3-099cfe3f3a20/
 fe2fa941-3030-412d-8c35-b0e80a2e7e09.vhd
 
 
 So, when we create a new Instance from the template, the Instance creation
 fail with the following error in the management-server.log:
 
 2013-10-03 15:48:01,190 WARN  [xen.resource.CitrixResourceBase]
 (DirectAgent-255:null) Catch Exception
 com.cloud.utils.exception.CloudRuntimeException on
 host:9a02ac57-bc92-43af-b50a-f5ba2d0fd806 for template: nfs://
 172.24.1.120/data/secondary/template/tmpl/3/246/fe2fa941-3030-412d-8c35-b0e80a2e7e09.vhddue
 to com.cloud.utils.exception.CloudRuntimeException: can not create vdi
 in sr 451078ee-d335-bdb0-c41c-cd86524be3ea
 
 if I move the VHD file in the 246 folder, it works !
 
 Does anyone have this problem too  or have an idea of where it would come
 from ?
 
 Thanks !
 
 
 Pierre-Luc Dion
 Responsable technique - infrastructure | Technical lead - infrastructure
 - - -*
 CloudOps
 *www.cloudops.com
 @CloudOps_



Re: Create Template on NFS secondary Storage

2013-10-03 Thread Travis Graham
Can you check the permissions on the actual folders, 244 and 246 and see if 
they differ or have different owners?

Travis

On Oct 3, 2013, at 4:06 PM, Pierre-Luc Dion pd...@cloudops.com wrote:

 root@s-184-VM:# ls -lh 244/*
 -rw-rw-rw- 1 4294967294 4294967294  309 Oct  3 18:01 244/template.properties
 
 244/a8ecc932-eaab-88f4-0687-37fbf15aeae5:
 total 1.4G
 -rw-r--r-- 1 4294967294 4294967294 1.5G Oct  3 18:01
 73e0632e-c856-44f4-8712-ae1daf0d79d2.vhd
 
 
 
 Pierre-Luc Dion
 Responsable technique - infrastructure | Technical lead - infrastructure
 514-447-3456, 1101
 - - -*
 CloudOps
 *420 rue Guy
 Montréal QC  H3J 1S6
 www.cloudops.com
 @CloudOps_
 
 
 On Thu, Oct 3, 2013 at 3:59 PM, Travis Graham tgra...@tgraham.us wrote:
 
 Can you check the permissions on the subdirectories?
 
 Travis
 
 On Oct 3, 2013, at 3:51 PM, Pierre-Luc Dion pd...@cloudops.com wrote:
 
 Hi all,
 
 We are currently using Cloudstack 4.1.0 managing XenServer 6.0.2 servers.
 
 
 Since recently, I don't know what cause this to appear on our system but
 went we create a template from a Instance the template (.vhd) is upload
 on
 on the secondary storage (NFS) but in a subdirectory  ex:
 
 from the Storage VM:
 /mnt/SecStorage/7f6f1f2d-2d6f-3ec6-a25e-fb25f2704167/template/tmpl/3/246
 root@s-184-VM:~# ls -l
 total 8
 drwxr-xr-x 2 4294967294 4294967294 4096 Oct  3 19:35
 02ee28f2-0c02-f936-3ca3-099cfe3f3a20
 -rw-rw-rw- 1 4294967294 4294967294  314 Oct  3 19:36 template.properties
 
 root@s-184-VM:~# ls 02ee28f2-0c02-f936-3ca3-099cfe3f3a20/
 fe2fa941-3030-412d-8c35-b0e80a2e7e09.vhd
 
 
 So, when we create a new Instance from the template, the Instance
 creation
 fail with the following error in the management-server.log:
 
 2013-10-03 15:48:01,190 WARN  [xen.resource.CitrixResourceBase]
 (DirectAgent-255:null) Catch Exception
 com.cloud.utils.exception.CloudRuntimeException on
 host:9a02ac57-bc92-43af-b50a-f5ba2d0fd806 for template: nfs://
 
 172.24.1.120/data/secondary/template/tmpl/3/246/fe2fa941-3030-412d-8c35-b0e80a2e7e09.vhddue
 to com.cloud.utils.exception.CloudRuntimeException: can not create vdi
 in sr 451078ee-d335-bdb0-c41c-cd86524be3ea
 
 if I move the VHD file in the 246 folder, it works !
 
 Does anyone have this problem too  or have an idea of where it would come
 from ?
 
 Thanks !
 
 
 Pierre-Luc Dion
 Responsable technique - infrastructure | Technical lead - infrastructure
 - - -*
 CloudOps
 *www.cloudops.com
 @CloudOps_
 
 



Re: Create Template on NFS secondary Storage

2013-10-03 Thread Kirk Kosinski
Did you patch the hosts recently?  That is the likely cause.  The
patched NFSSR.py that CloudStack copies to XS hosts can be overwritten
by some patches.  Without the patched NFSSR.py, when secondary storage
is mounted it reverts to the default XenServer behavior of including an
extra directory named after the SR UUID.

One solution is to copy the correct NFSSR.py manually from the
management server to /opt/xensource/sm/NFSSR.py on every XS host.  There
will be several versions of the script in
/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/ on the
management server, and you can check the MD5 checksums beforehand to
confirm it is the problem.

Another solution is to force CloudStack to setup the host again, which
includes copying NFSSR.py.  To do this, unmanage the cluster in
Cloudstack, clear the tags parameter for every host in the cluster (xe
host-list, xe host-param-clear uuid=uuid param-name=tags), re-manage
the cluster, and wait a few minutes.

Best regards,
Kirk

On 10/03/2013 12:51 PM, Pierre-Luc Dion wrote:
 Hi all,
 
 We are currently using Cloudstack 4.1.0 managing XenServer 6.0.2 servers.
 
 
 Since recently, I don't know what cause this to appear on our system but
  went we create a template from a Instance the template (.vhd) is upload on
 on the secondary storage (NFS) but in a subdirectory  ex:
 
 from the Storage VM:
 /mnt/SecStorage/7f6f1f2d-2d6f-3ec6-a25e-fb25f2704167/template/tmpl/3/246
 root@s-184-VM:~# ls -l
 total 8
 drwxr-xr-x 2 4294967294 4294967294 4096 Oct  3 19:35
 02ee28f2-0c02-f936-3ca3-099cfe3f3a20
 -rw-rw-rw- 1 4294967294 4294967294  314 Oct  3 19:36 template.properties
 
 root@s-184-VM:~# ls 02ee28f2-0c02-f936-3ca3-099cfe3f3a20/
 fe2fa941-3030-412d-8c35-b0e80a2e7e09.vhd
 
 
 So, when we create a new Instance from the template, the Instance creation
 fail with the following error in the management-server.log:
 
 2013-10-03 15:48:01,190 WARN  [xen.resource.CitrixResourceBase]
 (DirectAgent-255:null) Catch Exception
 com.cloud.utils.exception.CloudRuntimeException on
 host:9a02ac57-bc92-43af-b50a-f5ba2d0fd806 for template: nfs://
 172.24.1.120/data/secondary/template/tmpl/3/246/fe2fa941-3030-412d-8c35-b0e80a2e7e09.vhddue
 to com.cloud.utils.exception.CloudRuntimeException: can not create vdi
 in sr 451078ee-d335-bdb0-c41c-cd86524be3ea
 
 if I move the VHD file in the 246 folder, it works !
 
 Does anyone have this problem too  or have an idea of where it would come
 from ?
 
 Thanks !
 
 
 Pierre-Luc Dion
 Responsable technique - infrastructure | Technical lead - infrastructure
 - - -*
 CloudOps
 *www.cloudops.com
 @CloudOps_
 


Re: [URGENT] Mounting issues from KVM hosts to secondary storage

2013-10-03 Thread Indra Pramana
Hi Marcus,

Good day to you, and thank you for your e-mail.

We will try to do what you have suggested and will see if we can fix the
problem. I am looking into increasing the filesystem of the KVM hosts to
see if it can resolve the problem for now.

Thank you very much for your help!

Cheers.



On Fri, Oct 4, 2013 at 2:32 AM, Marcus Sorensen shadow...@gmail.com wrote:

 You'll have to go back further in the log then, and/or go to the agent
 log, because the issue of the ghost mount is due to the filesystem
 being full, and if that's your secondary storage I'm not sure why it
 would be written to from the kvm host unless you were doing backups or
 snapshots.

 On Thu, Oct 3, 2013 at 12:03 PM, Indra Pramana in...@sg.or.id wrote:
  Hi Marcus,
 
  It happens randomly, mounting fails, and then / gets filled. I suspect
 this
  occurs when the mounting fails, any files which is supposed to be
  transferred to the mount point (e.g. templates used to create VMs) will
  fill-up the / partition of the KVM host instead. This doesn't happen in
  4.1.1, this only happens after we upgraded to 4.2.0.
 
  And how about virsh pool-list result which is not reflecting the actual
 IDs
  of the secondary storage we see from Cloudstack GUI, is it supposed to be
  the case? If not, how to rectify it?
 
  Looking forward to your reply, thank you.
 
  Cheers.
 
 
 
 
  On Fri, Oct 4, 2013 at 1:51 AM, Marcus Sorensen shadow...@gmail.com
 wrote:
 
  It sort of looks like the out of space triggered the issue. Libvirt
 shows
 
  2013-10-03 15:38:57.414+: 2710: error : virCommandWait:2348 :
  internal error Child process (/bin/umount
  /mnt/5230667e-9c58-3ff6-983c-5fc2a72df669) unexpected exit status 32:
  error writing /etc/mtab.tmp: No space left on device
 
  So that entry of the filesystem being mounted is orphaned in
  /etc/mtab, since it can't be removed. That seems to be the source of
  why 'df' shows the thing mounted when it isn't, at least.
 
 
  On Thu, Oct 3, 2013 at 11:45 AM, Indra Pramana in...@sg.or.id wrote:
   Hi Marcus and all,
  
   I also find some strange and interesting error messages from the
 libvirt
   logs:
  
   http://pastebin.com/5ByfNpAf
  
   Looking forward to your reply, thank you.
  
   Cheers.
  
  
  
   On Fri, Oct 4, 2013 at 1:38 AM, Indra Pramana in...@sg.or.id wrote:
  
   Hi Marcus,
  
   Good day to you, and thank you for your e-mail. See my reply inline.
  
   On Fri, Oct 4, 2013 at 12:29 AM, Marcus Sorensen 
 shadow...@gmail.com
  wrote:
  
   Are you using the release artifacts, or your own 4.2 build?
  
  
   [Indra:] We are using the release artifacts from below repo since we
 are
   using Ubuntu:
  
   deb http://cloudstack.apt-get.eu/ubuntu precise 4.2
  
  
   When you rebooted the host, did the problem go away or come back the
   same?
  
  
   [Indra:] When I rebooted the host, the problem go away for a while,
 but
  it
   will come back again after some time. It will come randomly at the
 time
   when we need to create a new instance on that host, or start an
 existing
   stopped instance.
  
  
   You may want to look at 'virsh pool-list' to see if libvirt is
   mounting/registering the secondary storage.
  
  
   [Indra:] This is the result of the virsh pool-list command:
  
   root@hv-kvm-02:/var/log/libvirt# virsh pool-list
   Name State  Autostart
   -
   301071ac-4c1d-4eac-855b-124126da0a38 active no
   5230667e-9c58-3ff6-983c-5fc2a72df669 active no
   d433809b-01ea-3947-ba0f-48077244e4d6 active no
  
   Strange thing is that none of my secondary storage IDs are there.
 Could
  it
   be that the ID might have changed during Cloudstack upgrade? Here is
 the
   list of my secondary storage (there are two of them) even though they
  are
   on the same NFS server:
 c02da448-b9f4-401b-b8d5-83e8ead5cfde nfs://
   10.237.11.31/mnt/vol1/sec-storage NFS
   5937edb6-2e95-4ae2-907b-80fe4599ed87 nfs://
   10.237.11.31/mnt/vol1/sec-storage2 NFS
  
   Is this happening on multiple hosts, the same way?
  
  
   [Indra:] Yes, it is happening on all the two hosts that I have, the
 same
   way.
  
  
   You may want to
   look at /etc/mtab, if the system reports it's mounted, though it's
   not, it might be in there. Look at /proc/mounts as well.
  
  
   [Indra:] Please find result of df, /etc/mtab and /proc/mounts below.
 The
   ghost mount point is on df and /etc/mtab, but not on /proc/mounts.
  
   root@hv-kvm-02:/etc# df
  
   Filesystem  1K-blocks
   Used
   Available Use% Mounted on
   /dev/sda1 4195924
   4192372 0 100% /
  
   udev132053356
  4
   132053352   1% /dev
   tmpfs52825052
  704
   52824348   1% /run
  
   none 5120
   0  5120   0% 

Resize data-disk doesn't work after upgrade

2013-10-03 Thread Indra Pramana
Dear all,

After upgrading to 4.2.0, I tried to resize a data disk of a VM instance
from 20 GB to 60 GB, through the Cloudstack GUI. The UI reports that the
resize was successful, and that the data disk is now showing 60 GB instead
of 20 GB. However, when I check the actual disk on the VM, it seems that
it's still 20 GB.

Any reason what might have been the cause of the problem? I even tried to
re-partition it to see if the size changed, but it wasn't and still at 20
GB. Which logs I need to look into?

Any help on this is greatly appreciated.

Looking forward to your reply, thank you.

Cheers.


Re: Resize data-disk doesn't work after upgrade

2013-10-03 Thread Marcus Sorensen
I just tested local storage qcow2 and CLVM resize on 4.2, they both worked.

Resize works like this:

1. Do sanity checks
2. Send resize command to the agent
3. Resize the disk/lun/file
4. Inform the VM instance that the disk has changed by making a
libvirt volBlockResize call (this is not fatal, some guest types can't
resize online and need to be restarted)
5. Update the database

You can check #3 looking at the disks themselves on storage to see if
they've grown. You can check #4 by restarting the VM to see if it
picks up the change.

It may be that libvirt was unable to inform the VM of the change (for
example if you haven't upgraded to a supported version of Ubuntu or
CentOS and it has an old libvirt that doesn't support volBlockResize).
 The way to know for sure is stop/start the VM if you can.

Look at those two things and let us know

On Thu, Oct 3, 2013 at 2:33 PM, Indra Pramana in...@sg.or.id wrote:
 Dear all,

 After upgrading to 4.2.0, I tried to resize a data disk of a VM instance
 from 20 GB to 60 GB, through the Cloudstack GUI. The UI reports that the
 resize was successful, and that the data disk is now showing 60 GB instead
 of 20 GB. However, when I check the actual disk on the VM, it seems that
 it's still 20 GB.

 Any reason what might have been the cause of the problem? I even tried to
 re-partition it to see if the size changed, but it wasn't and still at 20
 GB. Which logs I need to look into?

 Any help on this is greatly appreciated.

 Looking forward to your reply, thank you.

 Cheers.


Management addresses on XenServers

2013-10-03 Thread David Comerford
Hi,

Why do system VM's on XenServer in a Basic networking zone require a
link-local address AND a private IP from the management range?

Best regards,
David Comerford

Tel: +353 87 1238295
Email: davest...@gmail.com
Website: http://dave.ie
GPG key: http://gpg.dave.ie


Re: Management addresses on XenServers

2013-10-03 Thread Geoff Higginbottom
David,

Link local is so that the management server can talk to them, and the private 
(management) address is so they can talk to the management server.

The Virtual Router has no private address so the standard way that CloudStack 
management servers talk to all system VMs is via link local.

SSVM and CPVM have a private address and they use this when thy initiate comms 
to the management server, using the address specified in the 'host' global 
setting' which should be a load balanced ip if you have more than one 
management server.

The exception to this is if using VMware which does not have a link local 
network, in which case the equivalent VIF on the vm is allocated a private ip 
range, but of course basic networking does not work with VMWare so we can 
ignore that for now.

Regards

Geoff Higginbottom
CTO / Cloud Architect


D: +44 20 3603 0542tel:+442036030542 | S: +44 20 3603 0540tel:+442036030540 
| M: +447968161581tel:+447968161581

geoff.higginbot...@shapeblue.commailto:geoff.higginbot...@shapeblue.com | 
www.shapeblue.com

ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS



On 3 Oct 2013, at 22:02, David Comerford 
davest...@gmail.commailto:davest...@gmail.com wrote:

Hi,

Why do system VM's on XenServer in a Basic networking zone require a
link-local address AND a private IP from the management range?

Best regards,
David Comerford

Tel: +353 87 1238295
Email: davest...@gmail.commailto:davest...@gmail.com
Website: http://dave.ie
GPG key: http://gpg.dave.ie
This email and any attachments to it may be confidential and are intended 
solely for the use of the individual to whom it is addressed. Any views or 
opinions expressed are solely those of the author and do not necessarily 
represent those of Shape Blue Ltd or related companies. If you are not the 
intended recipient of this email, you must neither take any action based upon 
its contents, nor copy or show it to anyone. Please contact the sender if you 
believe you have received this email in error. Shape Blue Ltd is a company 
incorporated in England  Wales. ShapeBlue Services India LLP is a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.


Re: Resize data-disk doesn't work after upgrade

2013-10-03 Thread Indra Pramana
Hi Marcus,

Good day to you, and thank you for your e-mail.

I have tried restarting the VM and even stop and start the VM, but after
logging in to the VM, I still see the hard drive's size as 20 GB instead of
60 GB.

I tried to check /var/log/libvirt/libvirtd.log file on the KVM host where
the VM is hosted, and can't find any messages related to volBlockResize.

Any other troubleshooting steps you can recommend, i.e. any other area I
can look into?

Looking forward to your reply, thank you.

Cheers.



On Fri, Oct 4, 2013 at 4:46 AM, Marcus Sorensen shadow...@gmail.com wrote:

 I just tested local storage qcow2 and CLVM resize on 4.2, they both worked.

 Resize works like this:

 1. Do sanity checks
 2. Send resize command to the agent
 3. Resize the disk/lun/file
 4. Inform the VM instance that the disk has changed by making a
 libvirt volBlockResize call (this is not fatal, some guest types can't
 resize online and need to be restarted)
 5. Update the database

 You can check #3 looking at the disks themselves on storage to see if
 they've grown. You can check #4 by restarting the VM to see if it
 picks up the change.

 It may be that libvirt was unable to inform the VM of the change (for
 example if you haven't upgraded to a supported version of Ubuntu or
 CentOS and it has an old libvirt that doesn't support volBlockResize).
  The way to know for sure is stop/start the VM if you can.

 Look at those two things and let us know

 On Thu, Oct 3, 2013 at 2:33 PM, Indra Pramana in...@sg.or.id wrote:
  Dear all,
 
  After upgrading to 4.2.0, I tried to resize a data disk of a VM instance
  from 20 GB to 60 GB, through the Cloudstack GUI. The UI reports that the
  resize was successful, and that the data disk is now showing 60 GB
 instead
  of 20 GB. However, when I check the actual disk on the VM, it seems that
  it's still 20 GB.
 
  Any reason what might have been the cause of the problem? I even tried to
  re-partition it to see if the size changed, but it wasn't and still at 20
  GB. Which logs I need to look into?
 
  Any help on this is greatly appreciated.
 
  Looking forward to your reply, thank you.
 
  Cheers.



Re: CS 4.2 storage vm

2013-10-03 Thread Laszlo Hornyak
Oops, of course vmware is non redistributable, so maybe it is not there.
However, this class should only be used if your CS is configured with
premium=true. If you turn it off, it will default to the
NfsSecondaryStorageResource included in the distribution.

Strage,


On Thu, Oct 3, 2013 at 7:09 PM, Laszlo Hornyak laszlo.horn...@gmail.comwrote:

 Hi Peter,

 The above class is in the vmware plugin, could you check if it is
 available in the agent?




 On Thu, Oct 3, 2013 at 12:29 AM, Erdősi Péter f...@niif.hu wrote:

 Dear,

 I installed CS 4.2 from rpm packages to Centos 6.4.
 Everything works fine, with install, and with configuration, but after
 the CS deploy the storage VM I can't add ISO-s.

 After some research in the logs I found this on a secstorage system VM:

 s-1-VM: /var/log/cloud.log
 2013-10-02 13:31:19,269 INFO  [cloud.agent.AgentShell] (main:null) Agent
 started
 2013-10-02 13:31:19,273 INFO  [cloud.agent.AgentShell] (main:null)
 Implementation Version is 4.2.0
 2013-10-02 13:31:19,274 INFO  [cloud.agent.AgentShell] (main:null)
 agent.properties found at /usr/local/cloud/systemvm/**
 conf/agent.properties
 2013-10-02 13:31:19,281 DEBUG [cloud.agent.AgentShell] (main:null) Found
 property: instance
 2013-10-02 13:31:19,281 DEBUG [cloud.agent.AgentShell] (main:null) Found
 property: resource
 2013-10-02 13:31:19,281 INFO  [cloud.agent.AgentShell] (main:null)
 Defaulting to using properties file for storage
 2013-10-02 13:31:19,283 INFO  [cloud.agent.AgentShell] (main:null)
 Defaulting to the constant time backoff algorithm
 2013-10-02 13:31:19,290 INFO  [cloud.utils.LogUtils] (main:null) log4j
 configuration found at /usr/local/cloud/systemvm/**conf/log4j-cloud.xml
 2013-10-02 13:31:19,318 DEBUG [cloud.agent.AgentShell] (main:null)
 Checking to see if agent.SecStorage.pid exists.
 2013-10-02 13:31:19,326 DEBUG [cloud.utils.ProcessUtil] (main:null)
 environment.properties could not be opened
 2013-10-02 13:31:19,337 DEBUG [cloud.utils.ProcessUtil] (main:null)
 Executing: bash -c echo $PPID
 2013-10-02 13:31:19,344 DEBUG [cloud.utils.ProcessUtil] (main:null)
 Execution is successful.
 2013-10-02 13:31:19,345 ERROR [cloud.agent.AgentShell] (main:null)
 *Unable to start agent: Resource class not found:
 com.cloud.storage.resource.**PremiumSecondaryStorageResourc**e due to:
 java.lang.**ClassNotFoundException: com.cloud.storage.resource.**
 PremiumSecondaryStorageResourc**e *


 Can somebody help me with this?

 Thanks,
  Peter ERDOSI




 --

 EOF




-- 

EOF


How to hide some server offerings?

2013-10-03 Thread Rafael Weingartner
Hey all,

I was wondering, I have some server offering that should just be used by
the administrator, so, is it possible to hide them from normal users?

I noticed that when I am creating a service offering there is a check-box
called public? So, I created some service offering that would be used just
for by the administrator, but they are appearing for all users (I did not
check that checkbox).

I also tried to check and uncheck the check-box(by the way it seems there
is a javascript problem on that page) and then selecting a domain like
root, but still the offerings are appearing to everybody.

Is it the expected behavior?
Do you happen to know if I can change any flag on the database and hide
them from normal users?

-- 
Rafael Weingartner


Re: Resize data-disk doesn't work after upgrade

2013-10-03 Thread Marcus Sorensen
What primary storage are you using? Any errors in agent log?
On Oct 3, 2013 3:16 PM, Indra Pramana in...@sg.or.id wrote:

 Hi Marcus,

 Good day to you, and thank you for your e-mail.

 I have tried restarting the VM and even stop and start the VM, but after
 logging in to the VM, I still see the hard drive's size as 20 GB instead of
 60 GB.

 I tried to check /var/log/libvirt/libvirtd.log file on the KVM host where
 the VM is hosted, and can't find any messages related to volBlockResize.

 Any other troubleshooting steps you can recommend, i.e. any other area I
 can look into?

 Looking forward to your reply, thank you.

 Cheers.



 On Fri, Oct 4, 2013 at 4:46 AM, Marcus Sorensen shadow...@gmail.com
 wrote:

  I just tested local storage qcow2 and CLVM resize on 4.2, they both
 worked.
 
  Resize works like this:
 
  1. Do sanity checks
  2. Send resize command to the agent
  3. Resize the disk/lun/file
  4. Inform the VM instance that the disk has changed by making a
  libvirt volBlockResize call (this is not fatal, some guest types can't
  resize online and need to be restarted)
  5. Update the database
 
  You can check #3 looking at the disks themselves on storage to see if
  they've grown. You can check #4 by restarting the VM to see if it
  picks up the change.
 
  It may be that libvirt was unable to inform the VM of the change (for
  example if you haven't upgraded to a supported version of Ubuntu or
  CentOS and it has an old libvirt that doesn't support volBlockResize).
   The way to know for sure is stop/start the VM if you can.
 
  Look at those two things and let us know
 
  On Thu, Oct 3, 2013 at 2:33 PM, Indra Pramana in...@sg.or.id wrote:
   Dear all,
  
   After upgrading to 4.2.0, I tried to resize a data disk of a VM
 instance
   from 20 GB to 60 GB, through the Cloudstack GUI. The UI reports that
 the
   resize was successful, and that the data disk is now showing 60 GB
  instead
   of 20 GB. However, when I check the actual disk on the VM, it seems
 that
   it's still 20 GB.
  
   Any reason what might have been the cause of the problem? I even tried
 to
   re-partition it to see if the size changed, but it wasn't and still at
 20
   GB. Which logs I need to look into?
  
   Any help on this is greatly appreciated.
  
   Looking forward to your reply, thank you.
  
   Cheers.
 



Re: How to hide some server offerings?

2013-10-03 Thread Alena Prokharchyk
Rafael, there is no way to filter offerings by the caller type, not even
in the DB.

Public attribute means that the offering is available to everyone in the
cloud; there is another alternative - offering can be domain specific. In
this case it can be used by all users from this domain/its subdomains.

As a workaround, you can set the name for the offerings you want to be
visible to admin, with some prefix. And filter out those offerings when
return the result to the regular user - but for that some custom
modifications need to be done in the CS UI.

-Alena.

On 10/3/13 3:31 PM, Rafael Weingartner rafaelweingart...@gmail.com
wrote:

Hey all,

I was wondering, I have some server offering that should just be used by
the administrator, so, is it possible to hide them from normal users?

I noticed that when I am creating a service offering there is a check-box
called public? So, I created some service offering that would be used just
for by the administrator, but they are appearing for all users (I did not
check that checkbox).

I also tried to check and uncheck the check-box(by the way it seems there
is a javascript problem on that page) and then selecting a domain like
root, but still the offerings are appearing to everybody.

Is it the expected behavior?
Do you happen to know if I can change any flag on the database and hide
them from normal users?

-- 
Rafael Weingartner





Network offering for GRE

2013-10-03 Thread Luca Salvatore
I'm trying to test getting cloudstack 4.1 to build some GRE tunnels between 
zones.
I have two zones and a Xen server in each.  I have sdn.ovs.controller set to 
true and separate physical interfaces configured for management traffic and GRE 
traffic.
When I deploy a VM in each zone I can see interfaces on the VMs called 
OVSTunnel… So I think it is all working well.

I want to overlay a layer 2 network across a layer 3 network, but just not sure 
how cloudstack does this.  It doesn't seem to be working at the moment.
Do I need to create some type of special network service offering to make this 
happen?  The only 'virtual networking' options I see is Nicira and BigSwitch.
For it to be layer 2, would I need to have each zone using the same subnet? Or 
should I assign a second NIC to each VM for the purpose of the GRE?

Thanks
--




Re: CS 4.2 storage vm

2013-10-03 Thread Erdősi Péter

Hi Laszlo,

Thanks for the information, however do You know, where can I change it? 
(I installed it from rpm packages.)
This is a compile-stage setting, or can be made on my installed system 
(if yes, can You tell where)?


Thanks:
 Peter

2013.10.03. 23:41 keltezéssel, Laszlo Hornyak írta:

Oops, of course vmware is non redistributable, so maybe it is not there.
However, this class should only be used if your CS is configured with
premium=true. If you turn it off, it will default to the
NfsSecondaryStorageResource included in the distribution.

Strage,


On Thu, Oct 3, 2013 at 7:09 PM, Laszlo Hornyak laszlo.horn...@gmail.comwrote:


Hi Peter,

The above class is in the vmware plugin, could you check if it is
available in the agent?




On Thu, Oct 3, 2013 at 12:29 AM, Erdősi Péter f...@niif.hu wrote:


Dear,

I installed CS 4.2 from rpm packages to Centos 6.4.
Everything works fine, with install, and with configuration, but after
the CS deploy the storage VM I can't add ISO-s.

After some research in the logs I found this on a secstorage system VM:

s-1-VM: /var/log/cloud.log
2013-10-02 13:31:19,269 INFO  [cloud.agent.AgentShell] (main:null) Agent
started
2013-10-02 13:31:19,273 INFO  [cloud.agent.AgentShell] (main:null)
Implementation Version is 4.2.0
2013-10-02 13:31:19,274 INFO  [cloud.agent.AgentShell] (main:null)
agent.properties found at /usr/local/cloud/systemvm/**
conf/agent.properties
2013-10-02 13:31:19,281 DEBUG [cloud.agent.AgentShell] (main:null) Found
property: instance
2013-10-02 13:31:19,281 DEBUG [cloud.agent.AgentShell] (main:null) Found
property: resource
2013-10-02 13:31:19,281 INFO  [cloud.agent.AgentShell] (main:null)
Defaulting to using properties file for storage
2013-10-02 13:31:19,283 INFO  [cloud.agent.AgentShell] (main:null)
Defaulting to the constant time backoff algorithm
2013-10-02 13:31:19,290 INFO  [cloud.utils.LogUtils] (main:null) log4j
configuration found at /usr/local/cloud/systemvm/**conf/log4j-cloud.xml
2013-10-02 13:31:19,318 DEBUG [cloud.agent.AgentShell] (main:null)
Checking to see if agent.SecStorage.pid exists.
2013-10-02 13:31:19,326 DEBUG [cloud.utils.ProcessUtil] (main:null)
environment.properties could not be opened
2013-10-02 13:31:19,337 DEBUG [cloud.utils.ProcessUtil] (main:null)
Executing: bash -c echo $PPID
2013-10-02 13:31:19,344 DEBUG [cloud.utils.ProcessUtil] (main:null)
Execution is successful.
2013-10-02 13:31:19,345 ERROR [cloud.agent.AgentShell] (main:null)
*Unable to start agent: Resource class not found:
com.cloud.storage.resource.**PremiumSecondaryStorageResourc**e due to:
java.lang.**ClassNotFoundException: com.cloud.storage.resource.**
PremiumSecondaryStorageResourc**e *


Can somebody help me with this?

Thanks,
  Peter ERDOSI




--

EOF








Re: Network offering for GRE

2013-10-03 Thread Luca Salvatore
So are you saying in version 4.1 it is currently not working?  WHat
version are the patches available in?

Any thoughts on how it will work between zones?  E.g. Layer 2 over layer 3?
Should we assign the same Subnets to each zone?
-- 
Luca





On 4/10/13 11:19 AM, Nguyen Anh Tu ng.t...@gmail.com wrote:

2013/10/4 Luca Salvatore l...@ninefold.com


 I want to overlay a layer 2 network across a layer 3 network, but just
not
 sure how cloudstack does this.  It doesn't seem to be working at the
moment.
 Do I need to create some type of special network service offering to
make
 this happen?  The only 'virtual networking' options I see is Nicira and
 BigSwitch.


Hi Luca,

At GSoC period, I worked on enhancing GRE controller. I submitted patches
to review board for these issue:
+ make GRE support for XCP
+ add L3 services (load balancing, port forwarding and staticNAT) to GRE
+ make GRE support for KVM

All patches are on the way to review and test.

Thanks,


-- 

N.g.U.y.e.N.A.n.H.t.U



Slow network speed to VM instances after upgrade to CloudStack 4.2.0

2013-10-03 Thread Indra Pramana
Dear all,

After CloudStack upgrade to 4.2.0, the network speed to our VM instances is
very slow and seems to be limited to 2 Mbps for both ingress and egress
traffic for each instance. It seems that there's some network rate limiting
which didn't take effect on CloudStack version 4.1.1 or below, but now is
taking effect on CloudStack 4.2.0.

I read this article on how CloudStack manages the network traffic for the
VMs:

http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.1.1/html/Admin_Guide/network-rate.html

For guest VMs, the network rate-limiting is set on the compute offering
associate with each VM. Please CMIIW.

All our guest VMs are created under different accounts and have their own
compute offering, which is auto-created under that specific account when
the VM instance is created.

The issue is, from admin account, I can't seem to modify the compute
offering for the guest VMs. If I go to GUI  Service Offerings  Compute
Offering, I can only see the compute offering for admin account only. How
can I see and modify the compute offering under different accounts?

Furthermore, it seems that I cannot modify the network rate field of an
existing compute offering. How do I modify it so that I can set higher
network rate limit or unlimited bandwidth for an existing guest VM?

Looking forward to your reply, thank you.

Cheers.


Re: Assign instance to another account

2013-10-03 Thread Punit Dambiwal
Hi,

It can be possible in CS 4.2

http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Release_Notes/version-4.2.html#host-and-vm-enhancements

Thanks,
Punit Dambiwal


On Thu, Oct 3, 2013 at 11:41 PM, Chris Sciarrino
chris.sciarr...@gmail.comwrote:

 Okay thanks for confirming. I will submit a feature request for it, this
 seems like something that should be available through the UI.


 On Thu, Oct 3, 2013 at 9:39 AM, Dean Kamali dean.kam...@gmail.com wrote:

  you will need to do that using the api it is not possible to via UI as
 far
  as I know.
 
 
  On Thu, Oct 3, 2013 at 8:36 AM, Chris Sciarrino
  chris.sciarr...@gmail.comwrote:
 
   Hi,
  
   Is it possible to assign a VM to another user through the cloudstack
 web
   interface?
  
   For example if I had a request from a user to have an instance deployed
  for
   them, I would be able to deploy it as the admin and then assign it to
  their
   account so that they would still be able to control the VM (power
 on/off,
   snapshots etc).
  
   I have seen references that it is possible to do this but can't seem to
   find the option.
  
 



Re: Network offering for GRE

2013-10-03 Thread Nguyen Anh Tu
2013/10/4 Luca Salvatore l...@ninefold.com

 So are you saying in version 4.1 it is currently not working?  WHat
 version are the patches available in?

 Yes, I'm working on sdnextensions branch, which are not merged to any
release branch.


 Any thoughts on how it will work between zones?  E.g. Layer 2 over layer 3?
 Should we assign the same Subnets to each zone?


Not sure if I understand your question correctly. Between zones it still
works I think, because GRE uses publicIP when create tunnels. Of course
zones must have the same hypervisor, and hosts must reach each other.


-- 

N.g.U.y.e.N.A.n.H.t.U


Re: Network offering for GRE

2013-10-03 Thread Luca Salvatore
What I mean is that, the GRE tunnel is build between the XenServers OVS.
The XenSevers would need public IPs between them for connectivity over the
L3 network.  This is normal for GRE end points.

However the VMs inside the XenServer don't know anything about the GRE.
For it to be proper layer 2 over layer 3 the VMs in each zone would need
to be on the same subnet.  That way they can ARP for a VM in a different
zone and traffic would use the GRE tunnel.
---



On 4/10/13 2:09 PM, Nguyen Anh Tu ng.t...@gmail.com wrote:

2013/10/4 Luca Salvatore l...@ninefold.com

 So are you saying in version 4.1 it is currently not working?  WHat
 version are the patches available in?

 Yes, I'm working on sdnextensions branch, which are not merged to any
release branch.


 Any thoughts on how it will work between zones?  E.g. Layer 2 over
layer 3?
 Should we assign the same Subnets to each zone?


Not sure if I understand your question correctly. Between zones it still
works I think, because GRE uses publicIP when create tunnels. Of course
zones must have the same hypervisor, and hosts must reach each other.


-- 

N.g.U.y.e.N.A.n.H.t.U