Re: Hello (Upgrade to 4.1)

We have done all ACS4.1 testing using OEL64 (which effectively is RHEL64). /Ove On 06/07/2013 05:40 AM, Kirk Kosinski wrote: The install guide [1] says "6.3+" so I would assume 6.4 would work. Hopefully someone else on the list has tried it and can confirm. Operating system: Preferred: Cent

Re: system templates in 4.1

I have looked into mysql log: mysql> SELECT template_host_ref.id, template_host_ref.host_id, template_host_ref.template_id, template_host_ref.created, template_host_ref.last_updated, template_host_ref.download_pct, template_host_ref.size, template_host_ref.physical_size, template_host_ref.download

Re: system templates in 4.1

I had figured out reason of template lookup failure. I added some logging to server/src/com/cloud/storage/dao/VMTemplateDaoImpl.java and recompiled it, Then I got following results: 2013-06-07 11:07:32,130 DEBUG [storage.dao.VMTemplateDaoImpl] (consoleproxy-1:null) sukaslayer starting findSystemVMT

CloudStack 4.1.0 Install, but -bash: cloud-setup-databases: command not found

Hello, Have you installed CS4.1.0 from RPM repo, I have tried it, But there is no cloud-setup-database script. -bash: cloud-setup-databases: command not found What's the matter? Thanks

vSphere 5.1 support

Hello everybody, does CS 4.1 support VMware vSphere 5.1 version? Thanks in advance, Gaspare

Re: vSphere 5.1 support

Hello everybody, does CS 4.1 support VMware vSphere 5.1 version? Thanks in advance, Gaspare

Unable to adjust firewall rules on VR since upgrade

Hi, Before posting a bug report for this, I am curious to see if anyone else faced that issue. We were running on 4.0.0, and we had couple isolated networks (hence couple VRs) with firewall rules. When we upgraded to 4.1.0, we were not able to adjust/delete firewall rules for the existing V

Re: vSphere 5.1 support

I'm no expert here but I am running CS 4.1 on vsphere/vcenter 5.1u1 and it's working fine. Officially, I do not think its supported as CS still uses vsphere 4.1 API calls I believe but I could be wrong. On 2013/06/08, at 1:50, Gaspare A Silvestri wrote: > Hello everybody, > > does CS 4.1 su

Cloudmonkey Async Job Issue

Hi all, I'm testing Cloudstack 4.1 on a Xen 6.1 system with a CentOS 6.4 management server. I installed Cloudmonkey 4.1.0-0 through pip, and started testing our deployment scripts. I've found that Cloudmonkey hangs on asynchronous job commands- it continues to poll the status of the job once i

Re: CloudStack 4.1.0 Install, but -bash: cloud-setup-databases: command not found

try cloudstack-setup-databases They have been converting from cloud- to cloudstack- Hope this helps Patrick On Fri, Jun 7, 2013 at 9:40 AM, wq meng wrote: > Hello, > > Have you installed CS4.1.0 from RPM repo, > > I have tried it, > > But there is no cloud-setup-database script. > > -bash

Re: CloudStack 4.1.0 Install, but -bash: cloud-setup-databases: command not found

Yeah, I have already found it, my bad as I always modify my install script from the old versions. It is better to add a note in the install guide on CS4.1.0 which start changing many cloud to cloudstack. Thank you very much. On Sat, Jun 8, 2013 at 5:19 AM, Patrick Miller wrote: > try cloudst

Re: CloudStack 4.1.0 Install, but -bash: cloud-setup-databases: command not found

can you file a bug for a doc fix? we should be filing any doc issues as soon as one runs across them: https://issues.apache.org/jira/secure/Dashboard.jspa On Fri, Jun 7, 2013 at 2:36 PM, wq meng wrote: > Yeah, > > I have already found it, my bad as I always modify my install script from > the

Re: Format of images in sharedmountpoint

I dont think this is supported at the moment, I know ceph requires raw images and converts qcow's to raw when deploying. If you can, please file a feature enhancement here: https://issues.apache.org/jira/secure/Dashboard.jspa On Mon, Jun 3, 2013 at 5:22 AM, Alexey Samarin wrote: > Hello list! >

Re: problem in key generation and in adding the host

Hey Ram, can you post full logs at pastebin.com or paste.cloudstack.org? On Mon, Jun 3, 2013 at 5:18 AM, ram kumar wrote: > Other log in management directory is as follows: > > root@krishna-S1200RP:/var/log/cloud/management# grep -Rin Error * > awsapi.log:1:2013-06-03 17:31:47,691 ERROR [control

Bug in updateUser API in CS 4.1.0

Hi, When I try to run the updateUser API for the admin user, the password field requires a cleartext unhashed password. With previous versions I could provide the hashed MD5 password, and the admin password would get updated. -a

Re: CloudStack 4.1.0 Install, but -bash: cloud-setup-databases: command not found

try : cloudstack-setup-databases 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 Fri, Jun 7, 2013 at 12:40 PM, wq meng wrote: > Hello, > > Have you ins

Re: Bug in updateUser API in CS 4.1.0

See this discussion http://markmail.org/thread/7r6ia3ckkt6fzlic You might have to install the MD5Authenticator as the default authenticator. On 6/7/13 3:44 PM, "Anoop Rajendra" wrote: >Hi, When I try to run the updateUser API for the admin user, the >password field requires a cleartext unhashed

Re: Cloudmonkey Async Job Issue

You might actually have an outdated cloud monkey (pip versioning issues) See http://markmail.org/thread/neprm4xrl4ydtqdy On 6/7/13 2:06 PM, "Tim Schultheiss" wrote: >Hi all, > > > >I'm testing Cloudstack 4.1 on a Xen 6.1 system with a CentOS 6.4 >management >server. I installed Cloudmonkey 4.1

Re: vSphere 5.1 support

https://cwiki.apache.org/confluence/x/lyrVAQ On 6/7/13 10:22 AM, "Jake G." wrote: >I'm no expert here but I am running CS 4.1 on vsphere/vcenter 5.1u1 and >it's working fine. > >Officially, I do not think its supported as CS still uses vsphere 4.1 API >calls I believe but I could be wrong. > > >

Hello (Upgrade to 4.1)

I just wanted to follow up, seems as though the communcation has stopped. I am presetly utilizing CS 4.0.2 | KVM | CentOS 6.3 I would like to go ahead and upgrade to CS 4.1 / CentOS 6.4; however, prior to doing so, it would be suggested to pause all containers (instances) as it seems it will