Regarding cloudstack automation

[umesh kute <um...@gmail.com>]

Hi All,
Good morning !!!
I am working as QA engineer and I am new to the cloudstack community.
We have started using cloudstack and deployed it in our infrastructure.

Can somebody please help me in identifying the good automation
framework/tool/anything? The main intention is we want to automate the
infrastructure validation related cases (for e.g. create/update/delete
cases for instances, project, network, etc...)

It would be good if you can help in identifying it.

Please note: I have gone through cloudmonkey. But i haven't found much help
on it. May be i need to search a bit more.. I am also going through the
marvin and planning to setup it. If apart from these two, if anyone has
different view please suggest.

Also, if somebody has any pointers on cloudmonkey and marvin or any more
info on this (like, if it would suffice the infrastructure validation
related cases i mentioned above) any pros/cons would really be helpful for
me...

Appreciate any help on this and looking forward for the response on this!!!

Thanks and Regards
-- Umesh Kute

Re: Regarding cloudstack automation

[umesh kute <um...@gmail.com>]

Thanks a lot Manas for your quick response!!!

Thanks and Regards
-- Umesh Kute


On Sun, Dec 8, 2013 at 3:25 PM, manas biswal <ma...@gmail.com>wrote:

> Dear Umesh
>
> As you have mentioned about "automation", is  it worth talking about
> scaling.
> which the cloud is really meant for. Basically there are 2 types of scaling
> scale up
> and scale out ( or horizontal and vertical scaling) . scale up means you
> are making automatic up and
> down the vm resources according to the requirement. i.e for example when
> your machine need extra memory
> it will attach automatically. In scale up scheme the single machine is
> scaled. In horizontal scaling
> -- another instance of same type will be up to balance he load ( as incase
> of http). Though Cloudstack provides
> API for scaling, you can write your own autoscaling script. As told by
> Apache, they may add this in future release.for
> time being it is supported by Netscaler ( Hardware) provided by Citrix. But
> there are some third party tools
> which can do this. you can se "scalr" https://github.com/Scalr/  and
> http://www.scalr.com/
> Cloudmonkey is the commandline interface for CloudStack, it is not a
> automation tool.  But you can use the API acces method used in Cloudmonkey
> for writting your own plugin for CloudStack
>
> Hope you understand
>
>
>
> On Sun, Dec 8, 2013 at 11:58 AM, umesh kute <um...@gmail.com> wrote:
>
> > Hi All,
> > Good morning !!!
> > I am working as QA engineer and I am new to the cloudstack community.
> > We have started using cloudstack and deployed it in our infrastructure.
> >
> > Can somebody please help me in identifying the good automation
> > framework/tool/anything? The main intention is we want to automate the
> > infrastructure validation related cases (for e.g. create/update/delete
> > cases for instances, project, network, etc...)
> >
> > It would be good if you can help in identifying it.
> >
> > Please note: I have gone through cloudmonkey. But i haven't found much
> help
> > on it. May be i need to search a bit more.. I am also going through the
> > marvin and planning to setup it. If apart from these two, if anyone has
> > different view please suggest.
> >
> > Also, if somebody has any pointers on cloudmonkey and marvin or any more
> > info on this (like, if it would suffice the infrastructure validation
> > related cases i mentioned above) any pros/cons would really be helpful
> for
> > me...
> >
> > Appreciate any help on this and looking forward for the response on
> this!!!
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
>
>
>
> --
> *Thanks and Regards*
> Manas Ranjan Biswal
> Research Scientist,
> OpenTechnology Center,
> NIC,Chennai
> 08015698191,9776349149
> manas.biswal@nic.in
>

Re: Regarding cloudstack automation

[manas biswal <ma...@gmail.com>]

Dear Umesh

As you have mentioned about "automation", is  it worth talking about
scaling.
which the cloud is really meant for. Basically there are 2 types of scaling
scale up
and scale out ( or horizontal and vertical scaling) . scale up means you
are making automatic up and
down the vm resources according to the requirement. i.e for example when
your machine need extra memory
it will attach automatically. In scale up scheme the single machine is
scaled. In horizontal scaling
-- another instance of same type will be up to balance he load ( as incase
of http). Though Cloudstack provides
API for scaling, you can write your own autoscaling script. As told by
Apache, they may add this in future release.for
time being it is supported by Netscaler ( Hardware) provided by Citrix. But
there are some third party tools
which can do this. you can se "scalr" https://github.com/Scalr/  and
http://www.scalr.com/
Cloudmonkey is the commandline interface for CloudStack, it is not a
automation tool.  But you can use the API acces method used in Cloudmonkey
for writting your own plugin for CloudStack

Hope you understand



On Sun, Dec 8, 2013 at 11:58 AM, umesh kute <um...@gmail.com> wrote:

> Hi All,
> Good morning !!!
> I am working as QA engineer and I am new to the cloudstack community.
> We have started using cloudstack and deployed it in our infrastructure.
>
> Can somebody please help me in identifying the good automation
> framework/tool/anything? The main intention is we want to automate the
> infrastructure validation related cases (for e.g. create/update/delete
> cases for instances, project, network, etc...)
>
> It would be good if you can help in identifying it.
>
> Please note: I have gone through cloudmonkey. But i haven't found much help
> on it. May be i need to search a bit more.. I am also going through the
> marvin and planning to setup it. If apart from these two, if anyone has
> different view please suggest.
>
> Also, if somebody has any pointers on cloudmonkey and marvin or any more
> info on this (like, if it would suffice the infrastructure validation
> related cases i mentioned above) any pros/cons would really be helpful for
> me...
>
> Appreciate any help on this and looking forward for the response on this!!!
>
> Thanks and Regards
> -- Umesh Kute
>



-- 
*Thanks and Regards*
Manas Ranjan Biswal
Research Scientist,
OpenTechnology Center,
NIC,Chennai
08015698191,9776349149
manas.biswal@nic.in

RE: Regarding cloudstack automation

[Chandan Purushothama <Ch...@citrix.com>]

Hello Umesh,

>From the logs that you posted, it appears to me that your command for deployment of VM got fired to the setup correctly. It looks like the VM deployment failed on the setup. Can you kindly check your cloudstack management server logs for the error information in order to understand the root cause for the issue,

Thank you,
Chandan


-------- Original message --------
From: Santhosh Edukulla
Date:12/30/2013 4:20 AM (GMT-08:00)
To: users@cloudstack.apache.org,Chandan Purushothama
Cc: Sudha Ponnaganti
Subject: RE: Regarding cloudstack automation

Umesh,

One question : Did you registered the template for ostype:     "ostype": 'CentOS 5.3 (64-bit)'?

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com]
Sent: Monday, December 30, 2013 6:32 AM
To: Chandan Purushothama
Cc: users@cloudstack.apache.org; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Hi Chandan,
Thanks for your response.
I have the latest Marvin repository (December 20th). I am able to proceed further. There was an issue of firewall for that machine and it got resolved.

But now i am getting another error when i tried to run the script "test_deploy_vm.py"

I have attached the log. Can somebody please have a look on it and help me in resolving the issue?

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
test_deploy_vm (integration.smoke.test_deploy_vm.TestDeployVM): CRITICAL: EXCEPTION: test_deploy_vm: Traceback (most recent call last):
  File "/usr/local/lib/python2.7/unittest/case.py", line 327, in run
    testMethod()
  File "/DataDisk/temp/cloudstack/test/integration/smoke/test_deploy_vm.py", line 116, in test_deploy_vm
    templateid=self.template.id<http://self.template.id>
  File "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py", line 415, in create
    virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
  File "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py", line 593, in deployVirtualMachine
    response = self.connection.marvinRequest(command, response_type=response, method=method)
  File "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py", line 280, in marvinRequest
    response = self.poll(asyncJobId, response_type)
  File "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py", line 86, in poll
    "asyncquery", asyncResonse.jobresult)
cloudstackAPIException: Execute cmd: asyncquery failed, due to: {errorcode : 533, errortext : u'Unable to create a deployment for VM[User|testvmshr]'}
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

PFA entire logs.

Please let me know in case if anything is required.

Thanks and Regards
-- Umesh Kute


On Sun, Dec 29, 2013 at 10:32 PM, Chandan Purushothama <Ch...@citrix.com>> wrote:

Hello Umesh,

I had a similar experience with an older Marvin build. I updated mine to the latest and tried again and it worked. I recommend you to kindly try again with the latest Marvin build and see if you are able to work with the automation framework,

Thank you,
Chandan


-------- Original message --------
From: umesh kute
Date:12/26/2013 12:29 AM (GMT-08:00)
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>,Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Hi All,
I have created a Marvin setup on CentOS6.3 by following the document:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python

All the pre-requisites are installed successfully.

I tried to run the sample script test_deploy_vm.py
(cloudstack/test/integration/smoke/), I am getting following error:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[root@localhost smoke]# nosetests --with-marvin
--marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg --load
test_deploy_vm.py

 Exception Occurred Under __deployDC :
HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
with url: /client/api?account=admin&command=listUsers&response=json (Caused
by <class 'socket.error'>: [Errno 110] Connection timed out)
Traceback (most recent call last):
  File "/usr/local/bin/nosetests", line 9, in <module>
    load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
line 118, in __init__
    **extra_args)
  File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
    self.runTests()
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
line 197, in runTests
    result = self.testRunner.run(self.test)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
line 61, in run
    test(result)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 176, in __call__
    return self.run(*arg, **kw)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 223, in run
    test(orig)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 176, in __call__
    return self.run(*arg, **kw)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 223, in run
    test(orig)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 176, in __call__
    return self.run(*arg, **kw)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 223, in run
    test(orig)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 176, in __call__
    return self.run(*arg, **kw)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 223, in run
    test(orig)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 176, in __call__
    return self.run(*arg, **kw)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 223, in run
    test(orig)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 176, in __call__
    return self.run(*arg, **kw)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 223, in run
    test(orig)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
line 45, in __call__
    return self.run(*arg, **kwarg)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
line 138, in run
    result.addError(self, err)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
line 124, in addError
    plugin_handled = plugins.handleError(self.test, err)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
line 99, in __call__
    return self.call(*arg, **kw)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
line 167, in simple
    result = meth(*arg, **kw)
  File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
line 155, in handleError
    self.tcRunLogger.fatal("%s: %s: %s" %
AttributeError: 'NoneType' object has no attribute 'fatal'

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

The logs are generated at /tmp and the log has following error.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
{'account': 'admin'}
2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
http://10.88.91.100:8096/client/api :
HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
with url: /client/api?account=admin&command=listUsers&response=json (Caused
by <class 'socket.error'>: [Errno 110] Connection timed out)

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Please note: I have opened the integration port 8096 on management server.
Also, changed the global settings integration.api.port
on cloudstack GUI to 8096 and restarted the management server.

Still I am getting the above issue. I am not sure if i missed any
configuration.

Can somebody please help me with resolution of this issue?
Appreciate your help here!!!

Thanks and Regards
-- Umesh Kute


On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <um...@gmail.com>> wrote:

> Thanks a lot Sudha for your quick response.
> I will setup the Marvin on local machine and get back in case if I face
> any challenges in setup.
>
> Thanks and Regards
> -- Umesh Kute
>
>
>
> On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
> sudha.ponnaganti@citrix.com<ma...@citrix.com>> wrote:
>
>> Hi Umesh,
>>
>> Looks like you have started on right track - Marvin is the framework to
>> use for functional or integration automation.
>> There are sizable number of test cases exist and you can review them.
>>  There are some wiki pages already written explaining Marvin [1]. Also best
>> practices are published by community as well [2]. You can contribute to it
>> as much as you can.
>>
>> Besides this, there is Junit framework (unit Test), Selenium framework
>> (UI automation) which are not as popular as Marvin. Marvin is perfect for
>> majority of the validation. You can use simulator as well with Marvin.
>>
>> Please do pursue these and post questions to the community if you run in
>> to any issues in setting up env and running tests. There are jobs setup by
>> various community members to test Master or current releases in various
>> labs and can help answer questions.
>>
>> [1]
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
>>
>>
>> Thanks
>> /Sudha
>>
>>
>> -----Original Message-----
>> From: umesh kute [mailto:umeshvkute@gmail.com]
>> Sent: Saturday, December 07, 2013 10:29 PM
>> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
>> Subject: Regarding cloudstack automation
>>
>> Hi All,
>> Good morning !!!
>> I am working as QA engineer and I am new to the cloudstack community.
>> We have started using cloudstack and deployed it in our infrastructure.
>>
>> Can somebody please help me in identifying the good automation
>> framework/tool/anything? The main intention is we want to automate the
>> infrastructure validation related cases (for e.g. create/update/delete
>> cases for instances, project, network, etc...)
>>
>> It would be good if you can help in identifying it.
>>
>> Please note: I have gone through cloudmonkey. But i haven't found much
>> help on it. May be i need to search a bit more.. I am also going through
>> the marvin and planning to setup it. If apart from these two, if anyone has
>> different view please suggest.
>>
>> Also, if somebody has any pointers on cloudmonkey and marvin or any more
>> info on this (like, if it would suffice the infrastructure validation
>> related cases i mentioned above) any pros/cons would really be helpful for
>> me...
>>
>> Appreciate any help on this and looking forward for the response on
>> this!!!
>>
>> Thanks and Regards
>> -- Umesh Kute
>>
>
>

RE: Regarding cloudstack automation

[Santhosh Edukulla <sa...@citrix.com>]

1. I would suggest you to get host to a clean state for your regression\automation run. Is it that you are using automation to run and check your cloudstack setup for new build?  Then, please expect the host to be a clean host before you start regression. There are some hard codings currently, along with few test cases like affinity suite which has certain assumptions, may have issues if you run on an already used host. We are removing few hardcodings from framework.

2. The approach we follow in regression is to have a host refreshed to a fresh state, then deployDC and run regression. The regression is working properly with better pass rates.  Its not the rule, but the procedure followed. Raise the tickets thereafter if you still see any issues. There could be test scripts issues as well, but unless otherwise with relevant data to debug, it will be little hard to know. Ideally, the test scripts with config to drive and run despite the host state should be ideal to work.

3. You can do one thing, we removed few dependencies in separate marvin branch under cloudstack repo, if you can help and test using that, then that should be good.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com]
Sent: Thursday, January 30, 2014 5:36 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org; Chandan Purushothama; Sudha Ponnaganti; dev@cloudstack.apache.org
Subject: Re: Regarding cloudstack automation

Hi Santhosh,
We cannot get the host to a clean state as it is being used by many people for testing.
We are using this since couple of months and its not refreshed to clean state.

As you suggested, I will raise the separate issues for the failures. It can be setup or test script specific.

Thanks and Regards
-- Umesh Kute


On Wed, Jan 29, 2014 at 8:03 PM, Santhosh Edukulla <sa...@citrix.com>> wrote:
Umesh,

1. Observing few issues, is the host, refreshed to clean state or a fresh one with out any  zones,vms  etc? Can you get your host(hypervisor) to a clean state before proceeding with your automation or regression run?

2. Deploy the DC using marvin and then run your automation thereafter.

Thanks!
Santhosh
________________________________________
From: Santhosh Edukulla
Sent: Wednesday, January 29, 2014 1:27 AM
To: umesh kute
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>; Chandan Purushothama; Sudha Ponnaganti; dev@cloudstack.apache.org<ma...@cloudstack.apache.org>
Subject: RE: Regarding cloudstack automation

Umesh,

1. Haven't had much time to look in to them in detail.

2. Can you please create few jira tickets for failures especially for the exceptions thrown under failed_plus_exceptions file for each test module? Look only for exceptions not assertion errors. I created one as below for few exceptions
in your log file.

EX: https://issues.apache.org/jira/browse/CLOUDSTACK-5973

3. This will help to look in to issues more clearly and fix them if there are any issues.

4. Note, the errors could be specific to setup\test scripts, not related to marvin.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>]
Sent: Tuesday, January 28, 2014 1:01 PM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>; Chandan Purushothama; Sudha Ponnaganti; dev@cloudstack.apache.org<ma...@cloudstack.apache.org>
Subject: Re: Regarding cloudstack automation

Hi Santhosh,
Did you get the chance to look into the log for the issue?

Thanks and Regards
-- Umesh Kute


On Mon, Jan 27, 2014 at 6:31 PM, umesh kute <um...@gmail.com>>> wrote:
Hi Santhosh,
I am attaching the failure logs in the zip file for 10 scripts executed so far. PFA (ComponetTestSuite_AllLogs.zip)

Regarding point#3, for BVT, there are 18-Pass, 17-Failed out of 35 cases.
That would be good, if you can let me know if there is any issue in marvin setup or configuration which i am using.

Please let me know if any additional information is required.

Thanks and Regards
-- Umesh Kute


On Fri, Jan 24, 2014 at 6:57 PM, Santhosh Edukulla <sa...@citrix.com>>> wrote:
Umesh,

1. There should not be any issues inherent inside of it as such not to run scripts atleast existing ones altogether. Now, compared to earlier mentioned failures viz., ssh,password, template etc ,these are mainly away from framework and are setup issues.

2. Component signifies regression cases, if you already know. Now for the run and failures count, mentioned below, can you let us know what are the failures or You can attach logs to elucidate the failures? Regression do run almost every day for various releases and has many passes and failures if any for product logged as bugs. The pass % for regression is more than 90% as far iam aware. The failures below, could be mainly due to infrastructure\setup specific or the way we may perceive it to run because of it few limitations.

3. We can help you to setup and start running marvin. Are all cases for bvt running first and with no issues? Mention the host and infrastructure setup details and flow you are using.

4. Also, we have a topic branch created for marvin. If you see an issue anywhere, you can log a bug, submit a patch for review to fix the same there.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>]
Sent: Friday, January 24, 2014 8:04 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>; Chandan Purushothama; Sudha Ponnaganti; dev@cloudstack.apache.org<ma...@cloudstack.apache.org>>
Subject: Re: Regarding cloudstack automation

Hi Santhosh,
To proceed further I deployed the template by disabling password and providing the default password as "password". Now its able to connect using ssh.

But when I started with the test case execution for the scripts which are there in "component folder", Out of 80 scripts, executed 11 and all 11 are failing (mentioned below).

test_affinity_groups.py
test_add_remove_network.py
test_accounts.py
test_allocation_states.py
test_baremetal.py
test_assign_vm.py
test_vm_passwdenabled.py
test_vpc_vm_life_cycle.py
test_vpc_routers.py
test_vpn_users.py
test_vpc_vms_deployment.py

Are there any issues with Marvin framework for running component script and is it executed before? I am facing many failures in a script.

If required I can share the logs.

Please note: We have a cloudstack 4.2 deployed in lab. We planned to use the Marvin to validate the cloudstack infrastructure. I have installed the marvin (0.1.0) and cloudstack using (4.2).

Thanks and Regards
-- Umesh Kute


On Sat, Jan 18, 2014 at 2:31 AM, Santhosh Edukulla <sa...@citrix.com>>>> wrote:
Umesh,

1. Its good that the template issue is resolved.

2. Regarding point 4 mentioned below, your understanding is right. The idea is during automation run for various test suites,  we use a template seeded into CS which has the password set with the one used in Services Class. So, in a way for all test suites having this password mentioned is assumed to be having an instance deployed with template matching our condition and so ssh works.

3. There are test cases pertaining explicitly to verify reset cases under CS, that covers scenarios to test, but for every ssh we dont use the password given by the API output.

4. So, for creating instances you can use a template with password as "password" for your testing, thats the easy solution i believe and all test suits has this password inside them, it will work. In a way, this not so a good design, but
We are planning to remove Services class test data from tests and separate it out as a test data, So for user running tests can alter the config to suit the template he has and all test suites using ssh works and will be configurable, compared to now we have to modify all test suites to get it working with custom password for user.

Thanks!
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>]
Sent: Friday, January 17, 2014 7:32 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Hi Santhosh,
Thanks again...
I tried the steps that you mentioned below. Fortunately i could able to proceed a bit further on this issue.

Now, instance got created successfully of type CentOS 6.4 (64-bit).

It is stuck in the ssh step.
Here is what happens...

1. All the steps/APIs till instance creation works fine (including listDomains, listZones, listOsTypes, listTemplates, createAccount, createServiceOffering, deployVirtualMachine, queryAsyncJobResult, associateIPAddress, createFirewallRules, createPortForwardingRule, createEgressFirewallRule)

2. When it tries to SSH to virtual machine it fails after timeout of 600s (20-retries, 30-intervals). Script is terminated.

3. I put some debug statements in function get_ssh_client() under: "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py"

The credentials i think it tries is :
self.ssh_ip: 207.x.x.x
self.ssh_port: 22
self.username: root
self.password: password
keyPairFileLocation: None

It means, it tries to connect to instance using password as password (it is provided in dictionary in test_vm_passwdenabled.py. Note: Earlier i gave references for test_loadbalance.py and its the same case).

4. In log, i found that the password that is returned in response to deployVirtualMachine API call is: xA2yeaxvb. (PFA file runinfo). When i tried to do ssh to the instance with same password it works and with dictionary "password" it doesn't. I think so.. please confirm...

Either, for ssh connection it should use the returned password or reset password before connection.

PFA all the logs.
Please correct if my understanding is correct or I am missing something here....

Please let me know if there is any resolution of this issue or if somebody encounters it before.

Thanks and Regards
-- Umesh Kute

On Tue, Jan 14, 2014 at 6:48 PM, Santhosh Edukulla <sa...@citrix.com>>>>> wrote:
Umesh,

Lets put steps so that we are in same page:

1. When we deploy  a VM, we use get_template function which basically retrieves the template information matching the description you provided under services class for ostype under test module EX: test_loadbalance.py.  I am surprised that you are receiving a "featured" and "builtin" template as windows template as output for this function. We are explicitly verifiying the template type as "BUILTIN" to retrieve the template information. So, a windows template cannot be a BUILTIN Template. Either it could be a bug in this function, or something with API. But, to double confirm, Can you please check whats the template information you are retrieving from this function matching with listTemplates API output( run either from your browser or script )  passing the same arguments as passed inside get_template?

Inside if we see, basically it gets the id matching with that ostype description using "listOsTypes"  and then use "listTemplates" command. So, this template is used to deploy the vm.  As far as i know, a builtin template cannot be a windows template?  Here, we use a featured and builtin template along with description filter passed. So, please check whether the template you are retrieving is windows or otherwise. Check for the field ostypename for the output you receive? Provide the output here for get_template copy pasted with dir(template) for return value?

2. To double confirm that it is template issue and not any other issue related to ssh like ( firewall\iptables\network connectivity issue) for ssh, please manually check for that particular ip in the test case whether ssh works or not and is not a windows machine?

3. Run one test case, first by adding a tag EX: "umesh" to the tags list as mentioned below for a particular test case under test module EX: test_loadbalance.py, then  run with nose command passing in tags argument mentioned below.

 @attr(tags = ["advanced", "advancedns", "smoke", "umesh"])
    def test_01_create_lb_rule_src_nat(self):

nosetests-2.7 -v --with-marvin --marvin-config=/root/softwares/cscode/setup/dev/advanced.cfg --load -a -w /root/softwares/cscode/test/integration/smoke/ -a tags=umesh

Let me know.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>]
Sent: Tuesday, January 14, 2014 7:02 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

I re-installed the marvin today to get the latest code.
I am again facing the same problem in get_template. It is returning the windows template and creating the windows VM. Hence when it tries to do SSH for VM, it fails.

I have also build the cloudstack to get the latest code for Marvin.

PFA the script logs and test_loadbalance script for reference.

Also, do let me know if I am missing some configuration or anything...

Just an FYI.. I have executed 35 scripts in smoke test directory. Out of 35 scripts executed, 17-PASS, 18-FAIL.
Around 50% failure are due to SSH related issue.

Thanks and Regards
-- Umesh Kute


On Fri, Jan 10, 2014 at 5:53 PM, Santhosh Edukulla <sa...@citrix.com>>>>>> wrote:
1. As such because of  bug in get_template, you are getting windows machine in your setup and then ssh is tried in test module, so you are getting the error.

2. Now, to overcome, just checkout the latest marvin, it should have a fix.

Note: It still has some other issues, but you can continue with your testing further. Let us know.

Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>]
Sent: Friday, January 10, 2014 5:19 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

So far i have found the failure on following scripts:
1. test_loadbalance
2. test_network
3. test_nic

In runinfo.txt log it is stuck at the step:
SSH into VM (IPaddress: 10.1.1.55) & NAT Rule (Public IP: 207.x.x.x)

PFA the Marvin logs for the test_loadbalance.py script.

I have modified the following entry in the script i.e. provided the correct template name which is present.
"ostype": "CentOS 6.4 (64-bit)",
#"ostype": "CentOS 5.3 (64-bit)",

Please let me know for your comments.

Thanks and Regards
-- Umesh Kute



On Fri, Jan 10, 2014 at 2:57 PM, Santhosh Edukulla <sa...@citrix.com>>>>>>> wrote:
You can log the bug for this. We have fixed few other issues along with this in a private branch. Will soon merge with ACS. If you need a temporary fix, let me know.

Question : Related to ssh issue, ssh to vm failing at which part? Can you add some information related to ssh failure which test module, which case etc? This may be related\unrelated to the above issue. We can check to see the issue is either same\different.

Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>]
Sent: Friday, January 10, 2014 4:21 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks a lot Santhosh For your response.

Sorry for delay.. But is there any workaround for this issue? Because as i mentioned, even if os type is provided as "ostype": 'CentOS 6.4 (64-bit)' it is picking up the first one in list i.e. Windows Server 2008 R2 Enterprise.
So some of the scripts which required to SSH into VM are failing.

Can I get the JIRA ID for this issue to track?

Thanks and Regards
-- Umesh Kute


On Fri, Jan 3, 2014 at 5:19 PM, Santhosh Edukulla <sa...@citrix.com>>>>>>>> wrote:
Umesh,

This could be probably due to the bug under get_template function under marvin/integration/lib/common.py. Though, the ostype description is used and corresponding id is retrieved.

But the later part, listTemplate API call returning the list and we are picking up either the template which is ready or matching with id we retrieved. This case is what could be causing the issue you mentioned.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>>]
Sent: Friday, January 03, 2014 5:04 AM
To: Santhosh Edukulla; users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks for your help Santhosh!!!

You are right...
The public IP address range was exhausted. After cleaning up the resources, I was able to run the sample script "test_deploy_vm.py" successfully.

One question - i have provided the "ostype": 'CentOS 6.4 (64-bit)'. What is the use of this parameter?

When observed in management server logs and on cloudstack UI (while running script), VM was created of type: "Windows Server 2008 R2 Enterprise with SQL 2012 Web Edition". This is the first one in the list.

Does it choose the one which we provided in script or picks it from the template list that is returned as a result of response to listTemplate API call?

Thanks and Regards
-- Umesh Kute


On Thu, Jan 2, 2014 at 7:22 PM, Santhosh Edukulla <sa...@citrix.com>>>>>>>>> wrote:
Umesh,

1. It seems you have exhausted few of CloudStack Resources. These resources usage should show up on your cloudstack dashboard. Anything appears in Red are exhausted resources.

2. Few of the cases could be EX: Guest VM IPs\Management ip addresses  are exhausted,

3. Check for these resources in Red on your dashboard EX: http://localhost:8080/client/->Dashboard and clean up them or add new resources.


Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>]
Sent: Thursday, January 02, 2014 7:06 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thank you once again Santhosh & Chandan.

I have gone through the management server logs. The deployment of VM got fired to the setup correctly and there are couple of errors in the management-server log.
I am summarizing those below:

test data in "test_deploy_vm.py"
 def __init__(self):
        self.testdata = {
            #data to create an account
            "account": {
                "email": "test@test.com<ma...@test.com>>>>>>>>>",
                "firstname": "Test",
                "lastname": "User",
                "username": "test",
                "password": "password",
            },
            #data reqd for virtual machine creation
            "virtual_machine" : {
                "name" : "testvmshr",
                "displayname" : "Test VM shr",
            },
            #small service offering
            "service_offering": {
                "small": {
                    "name": "SOSmall",
                    "displaytext": "Small Instance",
                    "cpunumber": 1,
                    "cpuspeed": 2000,
                    "memory": 1024,
                },
            },
            "ostype": 'CentOS 6.4 (64-bit)',
        }


1. Account is successfully created
2. Service offering is successfully created
3. Management server logs - management-server.log has following error:


2014-01-02 01:43:40,693 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Lock is released for network Ntwk[326|Guest|15] as a part of network shutdown
2014-01-02 01:43:40,695 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Lock is released for network id 326 as a part of network implement
2014-01-02 01:43:40,695 INFO  [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Insufficient capacity
com.cloud.exception.InsufficientAddressCapacityException: Insufficient address capacityScope=interface com.cloud.dc.DataCenter; id=1
at com.cloud.network.NetworkManagerImpl.fetchNewPublicIp(NetworkManagerImpl.java:479)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.assignDedicateIpAddress(NetworkManagerImpl.java:613)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.assignSourceNatIpAddressToGuestNetwork(NetworkManagerImpl.java:582)
at com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:2013)
at com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1939)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2120)
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:887)
at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2014-01-02 01:43:40,703 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Cleaning up resources for the vm VM[User|testvmshr] in Starting state

4. When i checked the database for the network id 326 in table "networks", it has following entry:

| 326 | test-TestDeployVM-test_deploy_vm-QQ91N0-network | b7cb9e31-835f-47e3-9585-97e3b4084e4d | test-TestDeployVM-test_deploy_vm-QQ91N0-network | Guest        | Vlan                  | NULL          | 10.1.1.1       | 10.1.1.0/24<http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24>     | Dhcp   |                  15 |                 200 |              1 | ExternalGuestNetworkGuru | Destroy     |     326 |         1 |        305 | 8.8.8.8 | 8.8.4.4 | NULL      |          0 | Account  | cs131cloud.internal | ecf5b617-04da-469b-b378-f53e05d8cc53 | Isolated   |                0 | 2014-01-02 06:43:39 | 2014-01-02 06:43:46 |                 0 |   NULL | NULL        | NULL     | NULL         |               1 |           NULL |


Basically it tries to create a network offering (id=15) : "HA Isolated Network With Source Nat"


5. I think the script creates a network shown in above table: "test-TestDeployVM-test_deploy_vm-QQ91N0-network".

I am not sure why it still gives the Insufficient address capacityScope exception.

6. One more thing i observed. I have provided the "ostype": 'CentOS 6.4 (64-bit)'. But in DeployVMCmd it uses the template id: "03ffb96f-2cfa-11e3-a4f0-f245a5b3ba0f" which is for template "Windows Server 2008 R2 Enterprise with SQL 2012 Web Edition".


I am attaching the management-server logs and script logs for references.

If somebody can help me what's wrong here, would really be helpful.


Thanks and Regards
-- Umesh Kute


On Thu, Jan 2, 2014 at 2:59 PM, Santhosh Edukulla <sa...@citrix.com>>>>>>>>>> wrote:
1. Is it still failing post this registration?

2. If yes, may be you can verify\provide the management server logs.
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>>]
Sent: Thursday, January 02, 2014 4:16 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks Santhosh.
Yes, I have registered the following template which i am using.

"ostype": 'CentOS 6.4 (64-bit)',

Thanks and Regards
-- Umesh Kute


On Mon, Dec 30, 2013 at 5:50 PM, Santhosh Edukulla <
santhosh.edukulla@citrix.com<ma...@citrix.com>>>>>>>>>> wrote:

> Umesh,
>
> One question : Did you registered the template for ostype:     "ostype":
> 'CentOS 5.3 (64-bit)'?
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>>]
> Sent: Monday, December 30, 2013 6:32 AM
> To: Chandan Purushothama
> Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>>; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi Chandan,
> Thanks for your response.
> I have the latest Marvin repository (December 20th). I am able to proceed
> further. There was an issue of firewall for that machine and it got
> resolved.
>
> But now i am getting another error when i tried to run the script
> "test_deploy_vm.py"
>
> I have attached the log. Can somebody please have a look on it and help me
> in resolving the issue?
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> test_deploy_vm (integration.smoke.test_deploy_vm.TestDeployVM): CRITICAL:
> EXCEPTION: test_deploy_vm: Traceback (most recent call last):
>   File "/usr/local/lib/python2.7/unittest/case.py", line 327, in run
>     testMethod()
>   File
> "/DataDisk/temp/cloudstack/test/integration/smoke/test_deploy_vm.py", line
> 116, in test_deploy_vm
>     templateid=self.template.id<http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id>
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py",
> line 415, in create
>     virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> line 593, in deployVirtualMachine
>     response = self.connection.marvinRequest(command,
> response_type=response, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 280, in marvinRequest
>     response = self.poll(asyncJobId, response_type)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 86, in poll
>     "asyncquery", asyncResonse.jobresult)
> cloudstackAPIException: Execute cmd: asyncquery failed, due to: {errorcode
> : 533, errortext : u'Unable to create a deployment for VM[User|testvmshr]'}
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> PFA entire logs.
>
> Please let me know in case if anything is required.
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Sun, Dec 29, 2013 at 10:32 PM, Chandan Purushothama <
> Chandan.Purushothama@citrix.com<ma...@citrix.com>>>>>>>>>>>
> wrote:
>
> Hello Umesh,
>
> I had a similar experience with an older Marvin build. I updated mine to
> the latest and tried again and it worked. I recommend you to kindly try
> again with the latest Marvin build and see if you are able to work with the
> automation framework,
>
> Thank you,
> Chandan
>
>
> -------- Original message --------
> From: umesh kute
> Date:12/26/2013 12:29 AM (GMT-08:00)
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>>>,Sudha
> Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi All,
> I have created a Marvin setup on CentOS6.3 by following the document:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
>
> All the pre-requisites are installed successfully.
>
> I tried to run the sample script test_deploy_vm.py
> (cloudstack/test/integration/smoke/), I am getting following error:
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> [root@localhost smoke]# nosetests --with-marvin
> --marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg --load
> test_deploy_vm.py
>
>  Exception Occurred Under __deployDC :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
> Traceback (most recent call last):
>   File "/usr/local/bin/nosetests", line 9, in <module>
>     load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 118, in __init__
>     **extra_args)
>   File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
>     self.runTests()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 197, in runTests
>     result = self.testRunner.run(self.test)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 61, in run
>     test(result)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 45, in __call__
>     return self.run(*arg, **kwarg)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 138, in run
>     result.addError(self, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
> line 124, in addError
>     plugin_handled = plugins.handleError(self.test, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 99, in __call__
>     return self.call(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 167, in simple
>     result = meth(*arg, **kw)
>   File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
> line 155, in handleError
>     self.tcRunLogger.fatal("%s: %s: %s" %
> AttributeError: 'NoneType' object has no attribute 'fatal'
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> The logs are generated at /tmp and the log has following error.
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
> {'account': 'admin'}
> 2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
> http://10.88.91.100:8096/client/api :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Please note: I have opened the integration port 8096 on management server.
> Also, changed the global settings integration.api.port
> on cloudstack GUI to 8096 and restarted the management server.
>
> Still I am getting the above issue. I am not sure if i missed any
> configuration.
>
> Can somebody please help me with resolution of this issue?
> Appreciate your help here!!!
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <um...@gmail.com>>>>>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>>>> wrote:
>
> > Thanks a lot Sudha for your quick response.
> > I will setup the Marvin on local machine and get back in case if I face
> > any challenges in setup.
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> >
> > On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
> > sudha.ponnaganti@citrix.com<ma...@citrix.com>>>>>>>>>>> wrote:
> >
> >> Hi Umesh,
> >>
> >> Looks like you have started on right track - Marvin is the framework to
> >> use for functional or integration automation.
> >> There are sizable number of test cases exist and you can review them.
> >>  There are some wiki pages already written explaining Marvin [1]. Also
> best
> >> practices are published by community as well [2]. You can contribute to
> it
> >> as much as you can.
> >>
> >> Besides this, there is Junit framework (unit Test), Selenium framework
> >> (UI automation) which are not as popular as Marvin. Marvin is perfect
> for
> >> majority of the validation. You can use simulator as well with Marvin.
> >>
> >> Please do pursue these and post questions to the community if you run in
> >> to any issues in setting up env and running tests. There are jobs setup
> by
> >> various community members to test Master or current releases in various
> >> labs and can help answer questions.
> >>
> >> [1]
> >>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> >>
> >>
> >> Thanks
> >> /Sudha
> >>
> >>
> >> -----Original Message-----
> >> From: umesh kute [mailto:umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>>]
> >> Sent: Saturday, December 07, 2013 10:29 PM
> >> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>>>
> >> Subject: Regarding cloudstack automation
> >>
> >> Hi All,
> >> Good morning !!!
> >> I am working as QA engineer and I am new to the cloudstack community.
> >> We have started using cloudstack and deployed it in our infrastructure.
> >>
> >> Can somebody please help me in identifying the good automation
> >> framework/tool/anything? The main intention is we want to automate the
> >> infrastructure validation related cases (for e.g. create/update/delete
> >> cases for instances, project, network, etc...)
> >>
> >> It would be good if you can help in identifying it.
> >>
> >> Please note: I have gone through cloudmonkey. But i haven't found much
> >> help on it. May be i need to search a bit more.. I am also going through
> >> the marvin and planning to setup it. If apart from these two, if anyone
> has
> >> different view please suggest.
> >>
> >> Also, if somebody has any pointers on cloudmonkey and marvin or any more
> >> info on this (like, if it would suffice the infrastructure validation
> >> related cases i mentioned above) any pros/cons would really be helpful
> for
> >> me...
> >>
> >> Appreciate any help on this and looking forward for the response on
> >> this!!!
> >>
> >> Thanks and Regards
> >> -- Umesh Kute
> >>
> >
> >
>
>

RE: Regarding cloudstack automation

[Santhosh Edukulla <sa...@citrix.com>]

1. I would suggest you to get host to a clean state for your regression\automation run. Is it that you are using automation to run and check your cloudstack setup for new build?  Then, please expect the host to be a clean host before you start regression. There are some hard codings currently, along with few test cases like affinity suite which has certain assumptions, may have issues if you run on an already used host. We are removing few hardcodings from framework.

2. The approach we follow in regression is to have a host refreshed to a fresh state, then deployDC and run regression. The regression is working properly with better pass rates.  Its not the rule, but the procedure followed. Raise the tickets thereafter if you still see any issues. There could be test scripts issues as well, but unless otherwise with relevant data to debug, it will be little hard to know. Ideally, the test scripts with config to drive and run despite the host state should be ideal to work.

3. You can do one thing, we removed few dependencies in separate marvin branch under cloudstack repo, if you can help and test using that, then that should be good.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com]
Sent: Thursday, January 30, 2014 5:36 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org; Chandan Purushothama; Sudha Ponnaganti; dev@cloudstack.apache.org
Subject: Re: Regarding cloudstack automation

Hi Santhosh,
We cannot get the host to a clean state as it is being used by many people for testing.
We are using this since couple of months and its not refreshed to clean state.

As you suggested, I will raise the separate issues for the failures. It can be setup or test script specific.

Thanks and Regards
-- Umesh Kute


On Wed, Jan 29, 2014 at 8:03 PM, Santhosh Edukulla <sa...@citrix.com>> wrote:
Umesh,

1. Observing few issues, is the host, refreshed to clean state or a fresh one with out any  zones,vms  etc? Can you get your host(hypervisor) to a clean state before proceeding with your automation or regression run?

2. Deploy the DC using marvin and then run your automation thereafter.

Thanks!
Santhosh
________________________________________
From: Santhosh Edukulla
Sent: Wednesday, January 29, 2014 1:27 AM
To: umesh kute
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>; Chandan Purushothama; Sudha Ponnaganti; dev@cloudstack.apache.org<ma...@cloudstack.apache.org>
Subject: RE: Regarding cloudstack automation

Umesh,

1. Haven't had much time to look in to them in detail.

2. Can you please create few jira tickets for failures especially for the exceptions thrown under failed_plus_exceptions file for each test module? Look only for exceptions not assertion errors. I created one as below for few exceptions
in your log file.

EX: https://issues.apache.org/jira/browse/CLOUDSTACK-5973

3. This will help to look in to issues more clearly and fix them if there are any issues.

4. Note, the errors could be specific to setup\test scripts, not related to marvin.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>]
Sent: Tuesday, January 28, 2014 1:01 PM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>; Chandan Purushothama; Sudha Ponnaganti; dev@cloudstack.apache.org<ma...@cloudstack.apache.org>
Subject: Re: Regarding cloudstack automation

Hi Santhosh,
Did you get the chance to look into the log for the issue?

Thanks and Regards
-- Umesh Kute


On Mon, Jan 27, 2014 at 6:31 PM, umesh kute <um...@gmail.com>>> wrote:
Hi Santhosh,
I am attaching the failure logs in the zip file for 10 scripts executed so far. PFA (ComponetTestSuite_AllLogs.zip)

Regarding point#3, for BVT, there are 18-Pass, 17-Failed out of 35 cases.
That would be good, if you can let me know if there is any issue in marvin setup or configuration which i am using.

Please let me know if any additional information is required.

Thanks and Regards
-- Umesh Kute


On Fri, Jan 24, 2014 at 6:57 PM, Santhosh Edukulla <sa...@citrix.com>>> wrote:
Umesh,

1. There should not be any issues inherent inside of it as such not to run scripts atleast existing ones altogether. Now, compared to earlier mentioned failures viz., ssh,password, template etc ,these are mainly away from framework and are setup issues.

2. Component signifies regression cases, if you already know. Now for the run and failures count, mentioned below, can you let us know what are the failures or You can attach logs to elucidate the failures? Regression do run almost every day for various releases and has many passes and failures if any for product logged as bugs. The pass % for regression is more than 90% as far iam aware. The failures below, could be mainly due to infrastructure\setup specific or the way we may perceive it to run because of it few limitations.

3. We can help you to setup and start running marvin. Are all cases for bvt running first and with no issues? Mention the host and infrastructure setup details and flow you are using.

4. Also, we have a topic branch created for marvin. If you see an issue anywhere, you can log a bug, submit a patch for review to fix the same there.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>]
Sent: Friday, January 24, 2014 8:04 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>; Chandan Purushothama; Sudha Ponnaganti; dev@cloudstack.apache.org<ma...@cloudstack.apache.org>>
Subject: Re: Regarding cloudstack automation

Hi Santhosh,
To proceed further I deployed the template by disabling password and providing the default password as "password". Now its able to connect using ssh.

But when I started with the test case execution for the scripts which are there in "component folder", Out of 80 scripts, executed 11 and all 11 are failing (mentioned below).

test_affinity_groups.py
test_add_remove_network.py
test_accounts.py
test_allocation_states.py
test_baremetal.py
test_assign_vm.py
test_vm_passwdenabled.py
test_vpc_vm_life_cycle.py
test_vpc_routers.py
test_vpn_users.py
test_vpc_vms_deployment.py

Are there any issues with Marvin framework for running component script and is it executed before? I am facing many failures in a script.

If required I can share the logs.

Please note: We have a cloudstack 4.2 deployed in lab. We planned to use the Marvin to validate the cloudstack infrastructure. I have installed the marvin (0.1.0) and cloudstack using (4.2).

Thanks and Regards
-- Umesh Kute


On Sat, Jan 18, 2014 at 2:31 AM, Santhosh Edukulla <sa...@citrix.com>>>> wrote:
Umesh,

1. Its good that the template issue is resolved.

2. Regarding point 4 mentioned below, your understanding is right. The idea is during automation run for various test suites,  we use a template seeded into CS which has the password set with the one used in Services Class. So, in a way for all test suites having this password mentioned is assumed to be having an instance deployed with template matching our condition and so ssh works.

3. There are test cases pertaining explicitly to verify reset cases under CS, that covers scenarios to test, but for every ssh we dont use the password given by the API output.

4. So, for creating instances you can use a template with password as "password" for your testing, thats the easy solution i believe and all test suits has this password inside them, it will work. In a way, this not so a good design, but
We are planning to remove Services class test data from tests and separate it out as a test data, So for user running tests can alter the config to suit the template he has and all test suites using ssh works and will be configurable, compared to now we have to modify all test suites to get it working with custom password for user.

Thanks!
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>]
Sent: Friday, January 17, 2014 7:32 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Hi Santhosh,
Thanks again...
I tried the steps that you mentioned below. Fortunately i could able to proceed a bit further on this issue.

Now, instance got created successfully of type CentOS 6.4 (64-bit).

It is stuck in the ssh step.
Here is what happens...

1. All the steps/APIs till instance creation works fine (including listDomains, listZones, listOsTypes, listTemplates, createAccount, createServiceOffering, deployVirtualMachine, queryAsyncJobResult, associateIPAddress, createFirewallRules, createPortForwardingRule, createEgressFirewallRule)

2. When it tries to SSH to virtual machine it fails after timeout of 600s (20-retries, 30-intervals). Script is terminated.

3. I put some debug statements in function get_ssh_client() under: "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py"

The credentials i think it tries is :
self.ssh_ip: 207.x.x.x
self.ssh_port: 22
self.username: root
self.password: password
keyPairFileLocation: None

It means, it tries to connect to instance using password as password (it is provided in dictionary in test_vm_passwdenabled.py. Note: Earlier i gave references for test_loadbalance.py and its the same case).

4. In log, i found that the password that is returned in response to deployVirtualMachine API call is: xA2yeaxvb. (PFA file runinfo). When i tried to do ssh to the instance with same password it works and with dictionary "password" it doesn't. I think so.. please confirm...

Either, for ssh connection it should use the returned password or reset password before connection.

PFA all the logs.
Please correct if my understanding is correct or I am missing something here....

Please let me know if there is any resolution of this issue or if somebody encounters it before.

Thanks and Regards
-- Umesh Kute

On Tue, Jan 14, 2014 at 6:48 PM, Santhosh Edukulla <sa...@citrix.com>>>>> wrote:
Umesh,

Lets put steps so that we are in same page:

1. When we deploy  a VM, we use get_template function which basically retrieves the template information matching the description you provided under services class for ostype under test module EX: test_loadbalance.py.  I am surprised that you are receiving a "featured" and "builtin" template as windows template as output for this function. We are explicitly verifiying the template type as "BUILTIN" to retrieve the template information. So, a windows template cannot be a BUILTIN Template. Either it could be a bug in this function, or something with API. But, to double confirm, Can you please check whats the template information you are retrieving from this function matching with listTemplates API output( run either from your browser or script )  passing the same arguments as passed inside get_template?

Inside if we see, basically it gets the id matching with that ostype description using "listOsTypes"  and then use "listTemplates" command. So, this template is used to deploy the vm.  As far as i know, a builtin template cannot be a windows template?  Here, we use a featured and builtin template along with description filter passed. So, please check whether the template you are retrieving is windows or otherwise. Check for the field ostypename for the output you receive? Provide the output here for get_template copy pasted with dir(template) for return value?

2. To double confirm that it is template issue and not any other issue related to ssh like ( firewall\iptables\network connectivity issue) for ssh, please manually check for that particular ip in the test case whether ssh works or not and is not a windows machine?

3. Run one test case, first by adding a tag EX: "umesh" to the tags list as mentioned below for a particular test case under test module EX: test_loadbalance.py, then  run with nose command passing in tags argument mentioned below.

 @attr(tags = ["advanced", "advancedns", "smoke", "umesh"])
    def test_01_create_lb_rule_src_nat(self):

nosetests-2.7 -v --with-marvin --marvin-config=/root/softwares/cscode/setup/dev/advanced.cfg --load -a -w /root/softwares/cscode/test/integration/smoke/ -a tags=umesh

Let me know.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>]
Sent: Tuesday, January 14, 2014 7:02 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

I re-installed the marvin today to get the latest code.
I am again facing the same problem in get_template. It is returning the windows template and creating the windows VM. Hence when it tries to do SSH for VM, it fails.

I have also build the cloudstack to get the latest code for Marvin.

PFA the script logs and test_loadbalance script for reference.

Also, do let me know if I am missing some configuration or anything...

Just an FYI.. I have executed 35 scripts in smoke test directory. Out of 35 scripts executed, 17-PASS, 18-FAIL.
Around 50% failure are due to SSH related issue.

Thanks and Regards
-- Umesh Kute


On Fri, Jan 10, 2014 at 5:53 PM, Santhosh Edukulla <sa...@citrix.com>>>>>> wrote:
1. As such because of  bug in get_template, you are getting windows machine in your setup and then ssh is tried in test module, so you are getting the error.

2. Now, to overcome, just checkout the latest marvin, it should have a fix.

Note: It still has some other issues, but you can continue with your testing further. Let us know.

Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>]
Sent: Friday, January 10, 2014 5:19 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

So far i have found the failure on following scripts:
1. test_loadbalance
2. test_network
3. test_nic

In runinfo.txt log it is stuck at the step:
SSH into VM (IPaddress: 10.1.1.55) & NAT Rule (Public IP: 207.x.x.x)

PFA the Marvin logs for the test_loadbalance.py script.

I have modified the following entry in the script i.e. provided the correct template name which is present.
"ostype": "CentOS 6.4 (64-bit)",
#"ostype": "CentOS 5.3 (64-bit)",

Please let me know for your comments.

Thanks and Regards
-- Umesh Kute



On Fri, Jan 10, 2014 at 2:57 PM, Santhosh Edukulla <sa...@citrix.com>>>>>>> wrote:
You can log the bug for this. We have fixed few other issues along with this in a private branch. Will soon merge with ACS. If you need a temporary fix, let me know.

Question : Related to ssh issue, ssh to vm failing at which part? Can you add some information related to ssh failure which test module, which case etc? This may be related\unrelated to the above issue. We can check to see the issue is either same\different.

Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>]
Sent: Friday, January 10, 2014 4:21 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks a lot Santhosh For your response.

Sorry for delay.. But is there any workaround for this issue? Because as i mentioned, even if os type is provided as "ostype": 'CentOS 6.4 (64-bit)' it is picking up the first one in list i.e. Windows Server 2008 R2 Enterprise.
So some of the scripts which required to SSH into VM are failing.

Can I get the JIRA ID for this issue to track?

Thanks and Regards
-- Umesh Kute


On Fri, Jan 3, 2014 at 5:19 PM, Santhosh Edukulla <sa...@citrix.com>>>>>>>> wrote:
Umesh,

This could be probably due to the bug under get_template function under marvin/integration/lib/common.py. Though, the ostype description is used and corresponding id is retrieved.

But the later part, listTemplate API call returning the list and we are picking up either the template which is ready or matching with id we retrieved. This case is what could be causing the issue you mentioned.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>>]
Sent: Friday, January 03, 2014 5:04 AM
To: Santhosh Edukulla; users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks for your help Santhosh!!!

You are right...
The public IP address range was exhausted. After cleaning up the resources, I was able to run the sample script "test_deploy_vm.py" successfully.

One question - i have provided the "ostype": 'CentOS 6.4 (64-bit)'. What is the use of this parameter?

When observed in management server logs and on cloudstack UI (while running script), VM was created of type: "Windows Server 2008 R2 Enterprise with SQL 2012 Web Edition". This is the first one in the list.

Does it choose the one which we provided in script or picks it from the template list that is returned as a result of response to listTemplate API call?

Thanks and Regards
-- Umesh Kute


On Thu, Jan 2, 2014 at 7:22 PM, Santhosh Edukulla <sa...@citrix.com>>>>>>>>> wrote:
Umesh,

1. It seems you have exhausted few of CloudStack Resources. These resources usage should show up on your cloudstack dashboard. Anything appears in Red are exhausted resources.

2. Few of the cases could be EX: Guest VM IPs\Management ip addresses  are exhausted,

3. Check for these resources in Red on your dashboard EX: http://localhost:8080/client/->Dashboard and clean up them or add new resources.


Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>]
Sent: Thursday, January 02, 2014 7:06 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thank you once again Santhosh & Chandan.

I have gone through the management server logs. The deployment of VM got fired to the setup correctly and there are couple of errors in the management-server log.
I am summarizing those below:

test data in "test_deploy_vm.py"
 def __init__(self):
        self.testdata = {
            #data to create an account
            "account": {
                "email": "test@test.com<ma...@test.com>>>>>>>>>",
                "firstname": "Test",
                "lastname": "User",
                "username": "test",
                "password": "password",
            },
            #data reqd for virtual machine creation
            "virtual_machine" : {
                "name" : "testvmshr",
                "displayname" : "Test VM shr",
            },
            #small service offering
            "service_offering": {
                "small": {
                    "name": "SOSmall",
                    "displaytext": "Small Instance",
                    "cpunumber": 1,
                    "cpuspeed": 2000,
                    "memory": 1024,
                },
            },
            "ostype": 'CentOS 6.4 (64-bit)',
        }


1. Account is successfully created
2. Service offering is successfully created
3. Management server logs - management-server.log has following error:


2014-01-02 01:43:40,693 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Lock is released for network Ntwk[326|Guest|15] as a part of network shutdown
2014-01-02 01:43:40,695 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Lock is released for network id 326 as a part of network implement
2014-01-02 01:43:40,695 INFO  [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Insufficient capacity
com.cloud.exception.InsufficientAddressCapacityException: Insufficient address capacityScope=interface com.cloud.dc.DataCenter; id=1
at com.cloud.network.NetworkManagerImpl.fetchNewPublicIp(NetworkManagerImpl.java:479)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.assignDedicateIpAddress(NetworkManagerImpl.java:613)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.assignSourceNatIpAddressToGuestNetwork(NetworkManagerImpl.java:582)
at com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:2013)
at com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1939)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2120)
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:887)
at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2014-01-02 01:43:40,703 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Cleaning up resources for the vm VM[User|testvmshr] in Starting state

4. When i checked the database for the network id 326 in table "networks", it has following entry:

| 326 | test-TestDeployVM-test_deploy_vm-QQ91N0-network | b7cb9e31-835f-47e3-9585-97e3b4084e4d | test-TestDeployVM-test_deploy_vm-QQ91N0-network | Guest        | Vlan                  | NULL          | 10.1.1.1       | 10.1.1.0/24<http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24>     | Dhcp   |                  15 |                 200 |              1 | ExternalGuestNetworkGuru | Destroy     |     326 |         1 |        305 | 8.8.8.8 | 8.8.4.4 | NULL      |          0 | Account  | cs131cloud.internal | ecf5b617-04da-469b-b378-f53e05d8cc53 | Isolated   |                0 | 2014-01-02 06:43:39 | 2014-01-02 06:43:46 |                 0 |   NULL | NULL        | NULL     | NULL         |               1 |           NULL |


Basically it tries to create a network offering (id=15) : "HA Isolated Network With Source Nat"


5. I think the script creates a network shown in above table: "test-TestDeployVM-test_deploy_vm-QQ91N0-network".

I am not sure why it still gives the Insufficient address capacityScope exception.

6. One more thing i observed. I have provided the "ostype": 'CentOS 6.4 (64-bit)'. But in DeployVMCmd it uses the template id: "03ffb96f-2cfa-11e3-a4f0-f245a5b3ba0f" which is for template "Windows Server 2008 R2 Enterprise with SQL 2012 Web Edition".


I am attaching the management-server logs and script logs for references.

If somebody can help me what's wrong here, would really be helpful.


Thanks and Regards
-- Umesh Kute


On Thu, Jan 2, 2014 at 2:59 PM, Santhosh Edukulla <sa...@citrix.com>>>>>>>>>> wrote:
1. Is it still failing post this registration?

2. If yes, may be you can verify\provide the management server logs.
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>>]
Sent: Thursday, January 02, 2014 4:16 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks Santhosh.
Yes, I have registered the following template which i am using.

"ostype": 'CentOS 6.4 (64-bit)',

Thanks and Regards
-- Umesh Kute


On Mon, Dec 30, 2013 at 5:50 PM, Santhosh Edukulla <
santhosh.edukulla@citrix.com<ma...@citrix.com>>>>>>>>>> wrote:

> Umesh,
>
> One question : Did you registered the template for ostype:     "ostype":
> 'CentOS 5.3 (64-bit)'?
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>>]
> Sent: Monday, December 30, 2013 6:32 AM
> To: Chandan Purushothama
> Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>>; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi Chandan,
> Thanks for your response.
> I have the latest Marvin repository (December 20th). I am able to proceed
> further. There was an issue of firewall for that machine and it got
> resolved.
>
> But now i am getting another error when i tried to run the script
> "test_deploy_vm.py"
>
> I have attached the log. Can somebody please have a look on it and help me
> in resolving the issue?
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> test_deploy_vm (integration.smoke.test_deploy_vm.TestDeployVM): CRITICAL:
> EXCEPTION: test_deploy_vm: Traceback (most recent call last):
>   File "/usr/local/lib/python2.7/unittest/case.py", line 327, in run
>     testMethod()
>   File
> "/DataDisk/temp/cloudstack/test/integration/smoke/test_deploy_vm.py", line
> 116, in test_deploy_vm
>     templateid=self.template.id<http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id>
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py",
> line 415, in create
>     virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> line 593, in deployVirtualMachine
>     response = self.connection.marvinRequest(command,
> response_type=response, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 280, in marvinRequest
>     response = self.poll(asyncJobId, response_type)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 86, in poll
>     "asyncquery", asyncResonse.jobresult)
> cloudstackAPIException: Execute cmd: asyncquery failed, due to: {errorcode
> : 533, errortext : u'Unable to create a deployment for VM[User|testvmshr]'}
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> PFA entire logs.
>
> Please let me know in case if anything is required.
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Sun, Dec 29, 2013 at 10:32 PM, Chandan Purushothama <
> Chandan.Purushothama@citrix.com<ma...@citrix.com>>>>>>>>>>>
> wrote:
>
> Hello Umesh,
>
> I had a similar experience with an older Marvin build. I updated mine to
> the latest and tried again and it worked. I recommend you to kindly try
> again with the latest Marvin build and see if you are able to work with the
> automation framework,
>
> Thank you,
> Chandan
>
>
> -------- Original message --------
> From: umesh kute
> Date:12/26/2013 12:29 AM (GMT-08:00)
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>>>,Sudha
> Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi All,
> I have created a Marvin setup on CentOS6.3 by following the document:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
>
> All the pre-requisites are installed successfully.
>
> I tried to run the sample script test_deploy_vm.py
> (cloudstack/test/integration/smoke/), I am getting following error:
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> [root@localhost smoke]# nosetests --with-marvin
> --marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg --load
> test_deploy_vm.py
>
>  Exception Occurred Under __deployDC :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
> Traceback (most recent call last):
>   File "/usr/local/bin/nosetests", line 9, in <module>
>     load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 118, in __init__
>     **extra_args)
>   File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
>     self.runTests()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 197, in runTests
>     result = self.testRunner.run(self.test)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 61, in run
>     test(result)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 45, in __call__
>     return self.run(*arg, **kwarg)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 138, in run
>     result.addError(self, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
> line 124, in addError
>     plugin_handled = plugins.handleError(self.test, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 99, in __call__
>     return self.call(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 167, in simple
>     result = meth(*arg, **kw)
>   File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
> line 155, in handleError
>     self.tcRunLogger.fatal("%s: %s: %s" %
> AttributeError: 'NoneType' object has no attribute 'fatal'
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> The logs are generated at /tmp and the log has following error.
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
> {'account': 'admin'}
> 2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
> http://10.88.91.100:8096/client/api :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Please note: I have opened the integration port 8096 on management server.
> Also, changed the global settings integration.api.port
> on cloudstack GUI to 8096 and restarted the management server.
>
> Still I am getting the above issue. I am not sure if i missed any
> configuration.
>
> Can somebody please help me with resolution of this issue?
> Appreciate your help here!!!
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <um...@gmail.com>>>>>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>>>> wrote:
>
> > Thanks a lot Sudha for your quick response.
> > I will setup the Marvin on local machine and get back in case if I face
> > any challenges in setup.
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> >
> > On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
> > sudha.ponnaganti@citrix.com<ma...@citrix.com>>>>>>>>>>> wrote:
> >
> >> Hi Umesh,
> >>
> >> Looks like you have started on right track - Marvin is the framework to
> >> use for functional or integration automation.
> >> There are sizable number of test cases exist and you can review them.
> >>  There are some wiki pages already written explaining Marvin [1]. Also
> best
> >> practices are published by community as well [2]. You can contribute to
> it
> >> as much as you can.
> >>
> >> Besides this, there is Junit framework (unit Test), Selenium framework
> >> (UI automation) which are not as popular as Marvin. Marvin is perfect
> for
> >> majority of the validation. You can use simulator as well with Marvin.
> >>
> >> Please do pursue these and post questions to the community if you run in
> >> to any issues in setting up env and running tests. There are jobs setup
> by
> >> various community members to test Master or current releases in various
> >> labs and can help answer questions.
> >>
> >> [1]
> >>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> >>
> >>
> >> Thanks
> >> /Sudha
> >>
> >>
> >> -----Original Message-----
> >> From: umesh kute [mailto:umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>>]
> >> Sent: Saturday, December 07, 2013 10:29 PM
> >> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>>>
> >> Subject: Regarding cloudstack automation
> >>
> >> Hi All,
> >> Good morning !!!
> >> I am working as QA engineer and I am new to the cloudstack community.
> >> We have started using cloudstack and deployed it in our infrastructure.
> >>
> >> Can somebody please help me in identifying the good automation
> >> framework/tool/anything? The main intention is we want to automate the
> >> infrastructure validation related cases (for e.g. create/update/delete
> >> cases for instances, project, network, etc...)
> >>
> >> It would be good if you can help in identifying it.
> >>
> >> Please note: I have gone through cloudmonkey. But i haven't found much
> >> help on it. May be i need to search a bit more.. I am also going through
> >> the marvin and planning to setup it. If apart from these two, if anyone
> has
> >> different view please suggest.
> >>
> >> Also, if somebody has any pointers on cloudmonkey and marvin or any more
> >> info on this (like, if it would suffice the infrastructure validation
> >> related cases i mentioned above) any pros/cons would really be helpful
> for
> >> me...
> >>
> >> Appreciate any help on this and looking forward for the response on
> >> this!!!
> >>
> >> Thanks and Regards
> >> -- Umesh Kute
> >>
> >
> >
>
>

Re: Regarding cloudstack automation

[umesh kute <um...@gmail.com>]

Hi Santhosh,
We cannot get the host to a clean state as it is being used by many people
for testing.
We are using this since couple of months and its not refreshed to clean
state.

As you suggested, I will raise the separate issues for the failures. It can
be setup or test script specific.

Thanks and Regards
-- Umesh Kute


On Wed, Jan 29, 2014 at 8:03 PM, Santhosh Edukulla <
santhosh.edukulla@citrix.com> wrote:

> Umesh,
>
> 1. Observing few issues, is the host, refreshed to clean state or a fresh
> one with out any  zones,vms  etc? Can you get your host(hypervisor) to a
> clean state before proceeding with your automation or regression run?
>
> 2. Deploy the DC using marvin and then run your automation thereafter.
>
> Thanks!
> Santhosh
> ________________________________________
> From: Santhosh Edukulla
> Sent: Wednesday, January 29, 2014 1:27 AM
> To: umesh kute
> Cc: users@cloudstack.apache.org; Chandan Purushothama; Sudha Ponnaganti;
> dev@cloudstack.apache.org
> Subject: RE: Regarding cloudstack automation
>
> Umesh,
>
> 1. Haven't had much time to look in to them in detail.
>
> 2. Can you please create few jira tickets for failures especially for the
> exceptions thrown under failed_plus_exceptions file for each test module?
> Look only for exceptions not assertion errors. I created one as below for
> few exceptions
> in your log file.
>
> EX: https://issues.apache.org/jira/browse/CLOUDSTACK-5973
>
> 3. This will help to look in to issues more clearly and fix them if there
> are any issues.
>
> 4. Note, the errors could be specific to setup\test scripts, not related
> to marvin.
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com]
> Sent: Tuesday, January 28, 2014 1:01 PM
> To: Santhosh Edukulla
> Cc: users@cloudstack.apache.org; Chandan Purushothama; Sudha Ponnaganti;
> dev@cloudstack.apache.org
> Subject: Re: Regarding cloudstack automation
>
> Hi Santhosh,
> Did you get the chance to look into the log for the issue?
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Mon, Jan 27, 2014 at 6:31 PM, umesh kute <umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>> wrote:
> Hi Santhosh,
> I am attaching the failure logs in the zip file for 10 scripts executed so
> far. PFA (ComponetTestSuite_AllLogs.zip)
>
> Regarding point#3, for BVT, there are 18-Pass, 17-Failed out of 35 cases.
> That would be good, if you can let me know if there is any issue in marvin
> setup or configuration which i am using.
>
> Please let me know if any additional information is required.
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Fri, Jan 24, 2014 at 6:57 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com>> wrote:
> Umesh,
>
> 1. There should not be any issues inherent inside of it as such not to run
> scripts atleast existing ones altogether. Now, compared to earlier
> mentioned failures viz., ssh,password, template etc ,these are mainly away
> from framework and are setup issues.
>
> 2. Component signifies regression cases, if you already know. Now for the
> run and failures count, mentioned below, can you let us know what are the
> failures or You can attach logs to elucidate the failures? Regression do
> run almost every day for various releases and has many passes and failures
> if any for product logged as bugs. The pass % for regression is more than
> 90% as far iam aware. The failures below, could be mainly due to
> infrastructure\setup specific or the way we may perceive it to run because
> of it few limitations.
>
> 3. We can help you to setup and start running marvin. Are all cases for
> bvt running first and with no issues? Mention the host and infrastructure
> setup details and flow you are using.
>
> 4. Also, we have a topic branch created for marvin. If you see an issue
> anywhere, you can log a bug, submit a patch for review to fix the same
> there.
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>]
> Sent: Friday, January 24, 2014 8:04 AM
> To: Santhosh Edukulla
> Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>;
> Chandan Purushothama; Sudha Ponnaganti; dev@cloudstack.apache.org<mailto:
> dev@cloudstack.apache.org>
> Subject: Re: Regarding cloudstack automation
>
> Hi Santhosh,
> To proceed further I deployed the template by disabling password and
> providing the default password as "password". Now its able to connect using
> ssh.
>
> But when I started with the test case execution for the scripts which are
> there in "component folder", Out of 80 scripts, executed 11 and all 11 are
> failing (mentioned below).
>
> test_affinity_groups.py
> test_add_remove_network.py
> test_accounts.py
> test_allocation_states.py
> test_baremetal.py
> test_assign_vm.py
> test_vm_passwdenabled.py
> test_vpc_vm_life_cycle.py
> test_vpc_routers.py
> test_vpn_users.py
> test_vpc_vms_deployment.py
>
> Are there any issues with Marvin framework for running component script
> and is it executed before? I am facing many failures in a script.
>
> If required I can share the logs.
>
> Please note: We have a cloudstack 4.2 deployed in lab. We planned to use
> the Marvin to validate the cloudstack infrastructure. I have installed the
> marvin (0.1.0) and cloudstack using (4.2).
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Sat, Jan 18, 2014 at 2:31 AM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>>> wrote:
> Umesh,
>
> 1. Its good that the template issue is resolved.
>
> 2. Regarding point 4 mentioned below, your understanding is right. The
> idea is during automation run for various test suites,  we use a template
> seeded into CS which has the password set with the one used in Services
> Class. So, in a way for all test suites having this password mentioned is
> assumed to be having an instance deployed with template matching our
> condition and so ssh works.
>
> 3. There are test cases pertaining explicitly to verify reset cases under
> CS, that covers scenarios to test, but for every ssh we dont use the
> password given by the API output.
>
> 4. So, for creating instances you can use a template with password as
> "password" for your testing, thats the easy solution i believe and all test
> suits has this password inside them, it will work. In a way, this not so a
> good design, but
> We are planning to remove Services class test data from tests and separate
> it out as a test data, So for user running tests can alter the config to
> suit the template he has and all test suites using ssh works and will be
> configurable, compared to now we have to modify all test suites to get it
> working with custom password for user.
>
> Thanks!
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>>]
> Sent: Friday, January 17, 2014 7:32 AM
> To: Santhosh Edukulla
> Cc: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><ma...@cloudstack.apache.org>>;
> Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi Santhosh,
> Thanks again...
> I tried the steps that you mentioned below. Fortunately i could able to
> proceed a bit further on this issue.
>
> Now, instance got created successfully of type CentOS 6.4 (64-bit).
>
> It is stuck in the ssh step.
> Here is what happens...
>
> 1. All the steps/APIs till instance creation works fine (including
> listDomains, listZones, listOsTypes, listTemplates, createAccount,
> createServiceOffering, deployVirtualMachine, queryAsyncJobResult,
> associateIPAddress, createFirewallRules, createPortForwardingRule,
> createEgressFirewallRule)
>
> 2. When it tries to SSH to virtual machine it fails after timeout of 600s
> (20-retries, 30-intervals). Script is terminated.
>
> 3. I put some debug statements in function get_ssh_client() under:
> "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py"
>
> The credentials i think it tries is :
> self.ssh_ip: 207.x.x.x
> self.ssh_port: 22
> self.username: root
> self.password: password
> keyPairFileLocation: None
>
> It means, it tries to connect to instance using password as password (it
> is provided in dictionary in test_vm_passwdenabled.py. Note: Earlier i gave
> references for test_loadbalance.py and its the same case).
>
> 4. In log, i found that the password that is returned in response to
> deployVirtualMachine API call is: xA2yeaxvb. (PFA file runinfo). When i
> tried to do ssh to the instance with same password it works and with
> dictionary "password" it doesn't. I think so.. please confirm...
>
> Either, for ssh connection it should use the returned password or reset
> password before connection.
>
> PFA all the logs.
> Please correct if my understanding is correct or I am missing something
> here....
>
> Please let me know if there is any resolution of this issue or if somebody
> encounters it before.
>
> Thanks and Regards
> -- Umesh Kute
>
> On Tue, Jan 14, 2014 at 6:48 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>>>>
> wrote:
> Umesh,
>
> Lets put steps so that we are in same page:
>
> 1. When we deploy  a VM, we use get_template function which basically
> retrieves the template information matching the description you provided
> under services class for ostype under test module EX: test_loadbalance.py.
>  I am surprised that you are receiving a "featured" and "builtin" template
> as windows template as output for this function. We are explicitly
> verifiying the template type as "BUILTIN" to retrieve the template
> information. So, a windows template cannot be a BUILTIN Template. Either it
> could be a bug in this function, or something with API. But, to double
> confirm, Can you please check whats the template information you are
> retrieving from this function matching with listTemplates API output( run
> either from your browser or script )  passing the same arguments as passed
> inside get_template?
>
> Inside if we see, basically it gets the id matching with that ostype
> description using "listOsTypes"  and then use "listTemplates" command. So,
> this template is used to deploy the vm.  As far as i know, a builtin
> template cannot be a windows template?  Here, we use a featured and builtin
> template along with description filter passed. So, please check whether the
> template you are retrieving is windows or otherwise. Check for the field
> ostypename for the output you receive? Provide the output here for
> get_template copy pasted with dir(template) for return value?
>
> 2. To double confirm that it is template issue and not any other issue
> related to ssh like ( firewall\iptables\network connectivity issue) for
> ssh, please manually check for that particular ip in the test case whether
> ssh works or not and is not a windows machine?
>
> 3. Run one test case, first by adding a tag EX: "umesh" to the tags list
> as mentioned below for a particular test case under test module EX:
> test_loadbalance.py, then  run with nose command passing in tags argument
> mentioned below.
>
>  @attr(tags = ["advanced", "advancedns", "smoke", "umesh"])
>     def test_01_create_lb_rule_src_nat(self):
>
> nosetests-2.7 -v --with-marvin
> --marvin-config=/root/softwares/cscode/setup/dev/advanced.cfg --load -a -w
> /root/softwares/cscode/test/integration/smoke/ -a tags=umesh
>
> Let me know.
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>]
> Sent: Tuesday, January 14, 2014 7:02 AM
> To: Santhosh Edukulla
> Cc: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><ma...@cloudstack.apache.org>>>;
> Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> I re-installed the marvin today to get the latest code.
> I am again facing the same problem in get_template. It is returning the
> windows template and creating the windows VM. Hence when it tries to do SSH
> for VM, it fails.
>
> I have also build the cloudstack to get the latest code for Marvin.
>
> PFA the script logs and test_loadbalance script for reference.
>
> Also, do let me know if I am missing some configuration or anything...
>
> Just an FYI.. I have executed 35 scripts in smoke test directory. Out of
> 35 scripts executed, 17-PASS, 18-FAIL.
> Around 50% failure are due to SSH related issue.
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Fri, Jan 10, 2014 at 5:53 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>>> wrote:
> 1. As such because of  bug in get_template, you are getting windows
> machine in your setup and then ssh is tried in test module, so you are
> getting the error.
>
> 2. Now, to overcome, just checkout the latest marvin, it should have a fix.
>
> Note: It still has some other issues, but you can continue with your
> testing further. Let us know.
>
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>]
> Sent: Friday, January 10, 2014 5:19 AM
> To: Santhosh Edukulla
> Cc: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><ma...@cloudstack.apache.org>>>>;
> Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> So far i have found the failure on following scripts:
> 1. test_loadbalance
> 2. test_network
> 3. test_nic
>
> In runinfo.txt log it is stuck at the step:
> SSH into VM (IPaddress: 10.1.1.55) & NAT Rule (Public IP: 207.x.x.x)
>
> PFA the Marvin logs for the test_loadbalance.py script.
>
> I have modified the following entry in the script i.e. provided the
> correct template name which is present.
> "ostype": "CentOS 6.4 (64-bit)",
> #"ostype": "CentOS 5.3 (64-bit)",
>
> Please let me know for your comments.
>
> Thanks and Regards
> -- Umesh Kute
>
>
>
> On Fri, Jan 10, 2014 at 2:57 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>>>>>>
> wrote:
> You can log the bug for this. We have fixed few other issues along with
> this in a private branch. Will soon merge with ACS. If you need a temporary
> fix, let me know.
>
> Question : Related to ssh issue, ssh to vm failing at which part? Can you
> add some information related to ssh failure which test module, which case
> etc? This may be related\unrelated to the above issue. We can check to see
> the issue is either same\different.
>
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>]
> Sent: Friday, January 10, 2014 4:21 AM
> To: Santhosh Edukulla
> Cc: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><ma...@cloudstack.apache.org>>>>>;
> Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thanks a lot Santhosh For your response.
>
> Sorry for delay.. But is there any workaround for this issue? Because as i
> mentioned, even if os type is provided as "ostype": 'CentOS 6.4 (64-bit)'
> it is picking up the first one in list i.e. Windows Server 2008 R2
> Enterprise.
> So some of the scripts which required to SSH into VM are failing.
>
> Can I get the JIRA ID for this issue to track?
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Fri, Jan 3, 2014 at 5:19 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>>>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>>>>> wrote:
> Umesh,
>
> This could be probably due to the bug under get_template function under
> marvin/integration/lib/common.py. Though, the ostype description is used
> and corresponding id is retrieved.
>
> But the later part, listTemplate API call returning the list and we are
> picking up either the template which is ready or matching with id we
> retrieved. This case is what could be causing the issue you mentioned.
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>]
> Sent: Friday, January 03, 2014 5:04 AM
> To: Santhosh Edukulla; users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>>>
> Cc: Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thanks for your help Santhosh!!!
>
> You are right...
> The public IP address range was exhausted. After cleaning up the
> resources, I was able to run the sample script "test_deploy_vm.py"
> successfully.
>
> One question - i have provided the "ostype": 'CentOS 6.4 (64-bit)'. What
> is the use of this parameter?
>
> When observed in management server logs and on cloudstack UI (while
> running script), VM was created of type: "Windows Server 2008 R2 Enterprise
> with SQL 2012 Web Edition". This is the first one in the list.
>
> Does it choose the one which we provided in script or picks it from the
> template list that is returned as a result of response to listTemplate API
> call?
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Thu, Jan 2, 2014 at 7:22 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>>>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>>>>>>>>
> wrote:
> Umesh,
>
> 1. It seems you have exhausted few of CloudStack Resources. These
> resources usage should show up on your cloudstack dashboard. Anything
> appears in Red are exhausted resources.
>
> 2. Few of the cases could be EX: Guest VM IPs\Management ip addresses  are
> exhausted,
>
> 3. Check for these resources in Red on your dashboard EX:
> http://localhost:8080/client/->Dashboard and clean up them or add new
> resources.
>
>
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>>]
> Sent: Thursday, January 02, 2014 7:06 AM
> To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>
> Cc: Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thank you once again Santhosh & Chandan.
>
> I have gone through the management server logs. The deployment of VM got
> fired to the setup correctly and there are couple of errors in the
> management-server log.
> I am summarizing those below:
>
> test data in "test_deploy_vm.py"
>  def __init__(self):
>         self.testdata = {
>             #data to create an account
>             "account": {
>                 "email": "test@test.com<ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>>>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>>>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>>>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>>>>>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>>>>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>>>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>>>>>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>>>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>>>>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>>>>>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>>>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>>>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>>>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>>>>>>>>",
>                 "firstname": "Test",
>                 "lastname": "User",
>                 "username": "test",
>                 "password": "password",
>             },
>             #data reqd for virtual machine creation
>             "virtual_machine" : {
>                 "name" : "testvmshr",
>                 "displayname" : "Test VM shr",
>             },
>             #small service offering
>             "service_offering": {
>                 "small": {
>                     "name": "SOSmall",
>                     "displaytext": "Small Instance",
>                     "cpunumber": 1,
>                     "cpuspeed": 2000,
>                     "memory": 1024,
>                 },
>             },
>             "ostype": 'CentOS 6.4 (64-bit)',
>         }
>
>
> 1. Account is successfully created
> 2. Service offering is successfully created
> 3. Management server logs - management-server.log has following error:
>
>
> 2014-01-02 01:43:40,693 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Lock is released for network Ntwk[326|Guest|15] as a part of network
> shutdown
> 2014-01-02 01:43:40,695 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Lock is released for network id 326 as a part of network implement
> 2014-01-02 01:43:40,695 INFO  [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Insufficient capacity
> com.cloud.exception.InsufficientAddressCapacityException: Insufficient
> address capacityScope=interface com.cloud.dc.DataCenter; id=1
> at
> com.cloud.network.NetworkManagerImpl.fetchNewPublicIp(NetworkManagerImpl.java:479)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.network.NetworkManagerImpl.assignDedicateIpAddress(NetworkManagerImpl.java:613)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.network.NetworkManagerImpl.assignSourceNatIpAddressToGuestNetwork(NetworkManagerImpl.java:582)
> at
> com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:2013)
> at
> com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1939)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2120)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:887)
> at
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:679)
> 2014-01-02 01:43:40,703 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Cleaning up resources for the vm VM[User|testvmshr] in Starting state
>
> 4. When i checked the database for the network id 326 in table "networks",
> it has following entry:
>
> | 326 | test-TestDeployVM-test_deploy_vm-QQ91N0-network |
> b7cb9e31-835f-47e3-9585-97e3b4084e4d |
> test-TestDeployVM-test_deploy_vm-QQ91N0-network | Guest        | Vlan
>            | NULL          | 10.1.1.1       | 10.1.1.0/24<
> http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><
> http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><
> http://10.1.1.0/24><http://10.1.1.0/24>     | Dhcp   |
>  15 |                 200 |              1 | ExternalGuestNetworkGuru |
> Destroy     |     326 |         1 |        305 | 8.8.8.8 | 8.8.4.4 | NULL
>    |          0 | Account  | cs131cloud.internal |
> ecf5b617-04da-469b-b378-f53e05d8cc53 | Isolated   |                0 |
> 2014-01-02 06:43:39 | 2014-01-02 06:43:46 |                 0 |   NULL |
> NULL        | NULL     | NULL         |               1 |           NULL |
>
>
> Basically it tries to create a network offering (id=15) : "HA Isolated
> Network With Source Nat"
>
>
> 5. I think the script creates a network shown in above table:
> "test-TestDeployVM-test_deploy_vm-QQ91N0-network".
>
> I am not sure why it still gives the Insufficient address capacityScope
> exception.
>
> 6. One more thing i observed. I have provided the "ostype": 'CentOS 6.4
> (64-bit)'. But in DeployVMCmd it uses the template id:
> "03ffb96f-2cfa-11e3-a4f0-f245a5b3ba0f" which is for template "Windows
> Server 2008 R2 Enterprise with SQL 2012 Web Edition".
>
>
> I am attaching the management-server logs and script logs for references.
>
> If somebody can help me what's wrong here, would really be helpful.
>
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Thu, Jan 2, 2014 at 2:59 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>>>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>>>>>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>>>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>>>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>>>>>>> wrote:
> 1. Is it still failing post this registration?
>
> 2. If yes, may be you can verify\provide the management server logs.
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>]
> Sent: Thursday, January 02, 2014 4:16 AM
> To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>>>>
> Cc: Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thanks Santhosh.
> Yes, I have registered the following template which i am using.
>
> "ostype": 'CentOS 6.4 (64-bit)',
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Mon, Dec 30, 2013 at 5:50 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>>>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>>>>>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>>>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>>>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>>>>>>> wrote:
>
> > Umesh,
> >
> > One question : Did you registered the template for ostype:     "ostype":
> > 'CentOS 5.3 (64-bit)'?
> >
> > Regards,
> > Santhosh
> > ________________________________________
> > From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>]
> > Sent: Monday, December 30, 2013 6:32 AM
> > To: Chandan Purushothama
> > Cc: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>>>>; Sudha Ponnaganti
> > Subject: Re: Regarding cloudstack automation
> >
> > Hi Chandan,
> > Thanks for your response.
> > I have the latest Marvin repository (December 20th). I am able to proceed
> > further. There was an issue of firewall for that machine and it got
> > resolved.
> >
> > But now i am getting another error when i tried to run the script
> > "test_deploy_vm.py"
> >
> > I have attached the log. Can somebody please have a look on it and help
> me
> > in resolving the issue?
> >
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > test_deploy_vm (integration.smoke.test_deploy_vm.TestDeployVM): CRITICAL:
> > EXCEPTION: test_deploy_vm: Traceback (most recent call last):
> >   File "/usr/local/lib/python2.7/unittest/case.py", line 327, in run
> >     testMethod()
> >   File
> > "/DataDisk/temp/cloudstack/test/integration/smoke/test_deploy_vm.py",
> line
> > 116, in test_deploy_vm
> >     templateid=self.template.id<http://self.template.id><
> http://self.template.id><http://self.template.id><http://self.template.id
> ><http://self.template.id><http://self.template.id><
> http://self.template.id><http://self.template.id><http://self.template.id>
> >   File
> > "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py",
> > line 415, in create
> >     virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> > line 593, in deployVirtualMachine
> >     response = self.connection.marvinRequest(command,
> > response_type=response, method=method)
> >   File
> > "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> > line 280, in marvinRequest
> >     response = self.poll(asyncJobId, response_type)
> >   File
> > "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> > line 86, in poll
> >     "asyncquery", asyncResonse.jobresult)
> > cloudstackAPIException: Execute cmd: asyncquery failed, due to:
> {errorcode
> > : 533, errortext : u'Unable to create a deployment for
> VM[User|testvmshr]'}
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > PFA entire logs.
> >
> > Please let me know in case if anything is required.
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> > On Sun, Dec 29, 2013 at 10:32 PM, Chandan Purushothama <
> > Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>>>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>>>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>>>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>>>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>>>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>>>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>>>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>>>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>>>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>>>>>>>>
> > wrote:
> >
> > Hello Umesh,
> >
> > I had a similar experience with an older Marvin build. I updated mine to
> > the latest and tried again and it worked. I recommend you to kindly try
> > again with the latest Marvin build and see if you are able to work with
> the
> > automation framework,
> >
> > Thank you,
> > Chandan
> >
> >
> > -------- Original message --------
> > From: umesh kute
> > Date:12/26/2013 12:29 AM (GMT-08:00)
> > To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>>>>>>,Sudha
> > Ponnaganti
> > Subject: Re: Regarding cloudstack automation
> >
> > Hi All,
> > I have created a Marvin setup on CentOS6.3 by following the document:
> >
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> >
> > All the pre-requisites are installed successfully.
> >
> > I tried to run the sample script test_deploy_vm.py
> > (cloudstack/test/integration/smoke/), I am getting following error:
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > [root@localhost smoke]# nosetests --with-marvin
> > --marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg
> --load
> > test_deploy_vm.py
> >
> >  Exception Occurred Under __deployDC :
> > HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> > with url: /client/api?account=admin&command=listUsers&response=json
> (Caused
> > by <class 'socket.error'>: [Errno 110] Connection timed out)
> > Traceback (most recent call last):
> >   File "/usr/local/bin/nosetests", line 9, in <module>
> >     load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> > line 118, in __init__
> >     **extra_args)
> >   File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
> >     self.runTests()
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> > line 197, in runTests
> >     result = self.testRunner.run(self.test)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> > line 61, in run
> >     test(result)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> > line 45, in __call__
> >     return self.run(*arg, **kwarg)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> > line 138, in run
> >     result.addError(self, err)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
> > line 124, in addError
> >     plugin_handled = plugins.handleError(self.test, err)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> > line 99, in __call__
> >     return self.call(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> > line 167, in simple
> >     result = meth(*arg, **kw)
> >   File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
> > line 155, in handleError
> >     self.tcRunLogger.fatal("%s: %s: %s" %
> > AttributeError: 'NoneType' object has no attribute 'fatal'
> >
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > The logs are generated at /tmp and the log has following error.
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > 2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
> > {'account': 'admin'}
> > 2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
> > http://10.88.91.100:8096/client/api :
> > HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> > with url: /client/api?account=admin&command=listUsers&response=json
> (Caused
> > by <class 'socket.error'>: [Errno 110] Connection timed out)
> >
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > Please note: I have opened the integration port 8096 on management
> server.
> > Also, changed the global settings integration.api.port
> > on cloudstack GUI to 8096 and restarted the management server.
> >
> > Still I am getting the above issue. I am not sure if i missed any
> > configuration.
> >
> > Can somebody please help me with resolution of this issue?
> > Appreciate your help here!!!
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> > On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>>>>><mailto:
> > umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>>> wrote:
> >
> > > Thanks a lot Sudha for your quick response.
> > > I will setup the Marvin on local machine and get back in case if I face
> > > any challenges in setup.
> > >
> > > Thanks and Regards
> > > -- Umesh Kute
> > >
> > >
> > >
> > > On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
> > > sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>>><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>>>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>>>>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>>>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>>>>>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>>>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>>>>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>>>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>>>>>>>>>
> wrote:
> > >
> > >> Hi Umesh,
> > >>
> > >> Looks like you have started on right track - Marvin is the framework
> to
> > >> use for functional or integration automation.
> > >> There are sizable number of test cases exist and you can review them.
> > >>  There are some wiki pages already written explaining Marvin [1]. Also
> > best
> > >> practices are published by community as well [2]. You can contribute
> to
> > it
> > >> as much as you can.
> > >>
> > >> Besides this, there is Junit framework (unit Test), Selenium framework
> > >> (UI automation) which are not as popular as Marvin. Marvin is perfect
> > for
> > >> majority of the validation. You can use simulator as well with Marvin.
> > >>
> > >> Please do pursue these and post questions to the community if you run
> in
> > >> to any issues in setting up env and running tests. There are jobs
> setup
> > by
> > >> various community members to test Master or current releases in
> various
> > >> labs and can help answer questions.
> > >>
> > >> [1]
> > >>
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> > >>
> > >>
> > >> Thanks
> > >> /Sudha
> > >>
> > >>
> > >> -----Original Message-----
> > >> From: umesh kute [mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>>>>>]
> > >> Sent: Saturday, December 07, 2013 10:29 PM
> > >> To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>>
> > >> Subject: Regarding cloudstack automation
> > >>
> > >> Hi All,
> > >> Good morning !!!
> > >> I am working as QA engineer and I am new to the cloudstack community.
> > >> We have started using cloudstack and deployed it in our
> infrastructure.
> > >>
> > >> Can somebody please help me in identifying the good automation
> > >> framework/tool/anything? The main intention is we want to automate the
> > >> infrastructure validation related cases (for e.g. create/update/delete
> > >> cases for instances, project, network, etc...)
> > >>
> > >> It would be good if you can help in identifying it.
> > >>
> > >> Please note: I have gone through cloudmonkey. But i haven't found much
> > >> help on it. May be i need to search a bit more.. I am also going
> through
> > >> the marvin and planning to setup it. If apart from these two, if
> anyone
> > has
> > >> different view please suggest.
> > >>
> > >> Also, if somebody has any pointers on cloudmonkey and marvin or any
> more
> > >> info on this (like, if it would suffice the infrastructure validation
> > >> related cases i mentioned above) any pros/cons would really be helpful
> > for
> > >> me...
> > >>
> > >> Appreciate any help on this and looking forward for the response on
> > >> this!!!
> > >>
> > >> Thanks and Regards
> > >> -- Umesh Kute
> > >>
> > >
> > >
> >
> >
>
>
>
>
>

Re: Regarding cloudstack automation

[umesh kute <um...@gmail.com>]

Hi Santhosh,
We cannot get the host to a clean state as it is being used by many people
for testing.
We are using this since couple of months and its not refreshed to clean
state.

As you suggested, I will raise the separate issues for the failures. It can
be setup or test script specific.

Thanks and Regards
-- Umesh Kute


On Wed, Jan 29, 2014 at 8:03 PM, Santhosh Edukulla <
santhosh.edukulla@citrix.com> wrote:

> Umesh,
>
> 1. Observing few issues, is the host, refreshed to clean state or a fresh
> one with out any  zones,vms  etc? Can you get your host(hypervisor) to a
> clean state before proceeding with your automation or regression run?
>
> 2. Deploy the DC using marvin and then run your automation thereafter.
>
> Thanks!
> Santhosh
> ________________________________________
> From: Santhosh Edukulla
> Sent: Wednesday, January 29, 2014 1:27 AM
> To: umesh kute
> Cc: users@cloudstack.apache.org; Chandan Purushothama; Sudha Ponnaganti;
> dev@cloudstack.apache.org
> Subject: RE: Regarding cloudstack automation
>
> Umesh,
>
> 1. Haven't had much time to look in to them in detail.
>
> 2. Can you please create few jira tickets for failures especially for the
> exceptions thrown under failed_plus_exceptions file for each test module?
> Look only for exceptions not assertion errors. I created one as below for
> few exceptions
> in your log file.
>
> EX: https://issues.apache.org/jira/browse/CLOUDSTACK-5973
>
> 3. This will help to look in to issues more clearly and fix them if there
> are any issues.
>
> 4. Note, the errors could be specific to setup\test scripts, not related
> to marvin.
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com]
> Sent: Tuesday, January 28, 2014 1:01 PM
> To: Santhosh Edukulla
> Cc: users@cloudstack.apache.org; Chandan Purushothama; Sudha Ponnaganti;
> dev@cloudstack.apache.org
> Subject: Re: Regarding cloudstack automation
>
> Hi Santhosh,
> Did you get the chance to look into the log for the issue?
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Mon, Jan 27, 2014 at 6:31 PM, umesh kute <umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>> wrote:
> Hi Santhosh,
> I am attaching the failure logs in the zip file for 10 scripts executed so
> far. PFA (ComponetTestSuite_AllLogs.zip)
>
> Regarding point#3, for BVT, there are 18-Pass, 17-Failed out of 35 cases.
> That would be good, if you can let me know if there is any issue in marvin
> setup or configuration which i am using.
>
> Please let me know if any additional information is required.
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Fri, Jan 24, 2014 at 6:57 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com>> wrote:
> Umesh,
>
> 1. There should not be any issues inherent inside of it as such not to run
> scripts atleast existing ones altogether. Now, compared to earlier
> mentioned failures viz., ssh,password, template etc ,these are mainly away
> from framework and are setup issues.
>
> 2. Component signifies regression cases, if you already know. Now for the
> run and failures count, mentioned below, can you let us know what are the
> failures or You can attach logs to elucidate the failures? Regression do
> run almost every day for various releases and has many passes and failures
> if any for product logged as bugs. The pass % for regression is more than
> 90% as far iam aware. The failures below, could be mainly due to
> infrastructure\setup specific or the way we may perceive it to run because
> of it few limitations.
>
> 3. We can help you to setup and start running marvin. Are all cases for
> bvt running first and with no issues? Mention the host and infrastructure
> setup details and flow you are using.
>
> 4. Also, we have a topic branch created for marvin. If you see an issue
> anywhere, you can log a bug, submit a patch for review to fix the same
> there.
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>]
> Sent: Friday, January 24, 2014 8:04 AM
> To: Santhosh Edukulla
> Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>;
> Chandan Purushothama; Sudha Ponnaganti; dev@cloudstack.apache.org<mailto:
> dev@cloudstack.apache.org>
> Subject: Re: Regarding cloudstack automation
>
> Hi Santhosh,
> To proceed further I deployed the template by disabling password and
> providing the default password as "password". Now its able to connect using
> ssh.
>
> But when I started with the test case execution for the scripts which are
> there in "component folder", Out of 80 scripts, executed 11 and all 11 are
> failing (mentioned below).
>
> test_affinity_groups.py
> test_add_remove_network.py
> test_accounts.py
> test_allocation_states.py
> test_baremetal.py
> test_assign_vm.py
> test_vm_passwdenabled.py
> test_vpc_vm_life_cycle.py
> test_vpc_routers.py
> test_vpn_users.py
> test_vpc_vms_deployment.py
>
> Are there any issues with Marvin framework for running component script
> and is it executed before? I am facing many failures in a script.
>
> If required I can share the logs.
>
> Please note: We have a cloudstack 4.2 deployed in lab. We planned to use
> the Marvin to validate the cloudstack infrastructure. I have installed the
> marvin (0.1.0) and cloudstack using (4.2).
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Sat, Jan 18, 2014 at 2:31 AM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>>> wrote:
> Umesh,
>
> 1. Its good that the template issue is resolved.
>
> 2. Regarding point 4 mentioned below, your understanding is right. The
> idea is during automation run for various test suites,  we use a template
> seeded into CS which has the password set with the one used in Services
> Class. So, in a way for all test suites having this password mentioned is
> assumed to be having an instance deployed with template matching our
> condition and so ssh works.
>
> 3. There are test cases pertaining explicitly to verify reset cases under
> CS, that covers scenarios to test, but for every ssh we dont use the
> password given by the API output.
>
> 4. So, for creating instances you can use a template with password as
> "password" for your testing, thats the easy solution i believe and all test
> suits has this password inside them, it will work. In a way, this not so a
> good design, but
> We are planning to remove Services class test data from tests and separate
> it out as a test data, So for user running tests can alter the config to
> suit the template he has and all test suites using ssh works and will be
> configurable, compared to now we have to modify all test suites to get it
> working with custom password for user.
>
> Thanks!
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>>]
> Sent: Friday, January 17, 2014 7:32 AM
> To: Santhosh Edukulla
> Cc: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><ma...@cloudstack.apache.org>>;
> Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi Santhosh,
> Thanks again...
> I tried the steps that you mentioned below. Fortunately i could able to
> proceed a bit further on this issue.
>
> Now, instance got created successfully of type CentOS 6.4 (64-bit).
>
> It is stuck in the ssh step.
> Here is what happens...
>
> 1. All the steps/APIs till instance creation works fine (including
> listDomains, listZones, listOsTypes, listTemplates, createAccount,
> createServiceOffering, deployVirtualMachine, queryAsyncJobResult,
> associateIPAddress, createFirewallRules, createPortForwardingRule,
> createEgressFirewallRule)
>
> 2. When it tries to SSH to virtual machine it fails after timeout of 600s
> (20-retries, 30-intervals). Script is terminated.
>
> 3. I put some debug statements in function get_ssh_client() under:
> "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py"
>
> The credentials i think it tries is :
> self.ssh_ip: 207.x.x.x
> self.ssh_port: 22
> self.username: root
> self.password: password
> keyPairFileLocation: None
>
> It means, it tries to connect to instance using password as password (it
> is provided in dictionary in test_vm_passwdenabled.py. Note: Earlier i gave
> references for test_loadbalance.py and its the same case).
>
> 4. In log, i found that the password that is returned in response to
> deployVirtualMachine API call is: xA2yeaxvb. (PFA file runinfo). When i
> tried to do ssh to the instance with same password it works and with
> dictionary "password" it doesn't. I think so.. please confirm...
>
> Either, for ssh connection it should use the returned password or reset
> password before connection.
>
> PFA all the logs.
> Please correct if my understanding is correct or I am missing something
> here....
>
> Please let me know if there is any resolution of this issue or if somebody
> encounters it before.
>
> Thanks and Regards
> -- Umesh Kute
>
> On Tue, Jan 14, 2014 at 6:48 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>>>>
> wrote:
> Umesh,
>
> Lets put steps so that we are in same page:
>
> 1. When we deploy  a VM, we use get_template function which basically
> retrieves the template information matching the description you provided
> under services class for ostype under test module EX: test_loadbalance.py.
>  I am surprised that you are receiving a "featured" and "builtin" template
> as windows template as output for this function. We are explicitly
> verifiying the template type as "BUILTIN" to retrieve the template
> information. So, a windows template cannot be a BUILTIN Template. Either it
> could be a bug in this function, or something with API. But, to double
> confirm, Can you please check whats the template information you are
> retrieving from this function matching with listTemplates API output( run
> either from your browser or script )  passing the same arguments as passed
> inside get_template?
>
> Inside if we see, basically it gets the id matching with that ostype
> description using "listOsTypes"  and then use "listTemplates" command. So,
> this template is used to deploy the vm.  As far as i know, a builtin
> template cannot be a windows template?  Here, we use a featured and builtin
> template along with description filter passed. So, please check whether the
> template you are retrieving is windows or otherwise. Check for the field
> ostypename for the output you receive? Provide the output here for
> get_template copy pasted with dir(template) for return value?
>
> 2. To double confirm that it is template issue and not any other issue
> related to ssh like ( firewall\iptables\network connectivity issue) for
> ssh, please manually check for that particular ip in the test case whether
> ssh works or not and is not a windows machine?
>
> 3. Run one test case, first by adding a tag EX: "umesh" to the tags list
> as mentioned below for a particular test case under test module EX:
> test_loadbalance.py, then  run with nose command passing in tags argument
> mentioned below.
>
>  @attr(tags = ["advanced", "advancedns", "smoke", "umesh"])
>     def test_01_create_lb_rule_src_nat(self):
>
> nosetests-2.7 -v --with-marvin
> --marvin-config=/root/softwares/cscode/setup/dev/advanced.cfg --load -a -w
> /root/softwares/cscode/test/integration/smoke/ -a tags=umesh
>
> Let me know.
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>]
> Sent: Tuesday, January 14, 2014 7:02 AM
> To: Santhosh Edukulla
> Cc: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><ma...@cloudstack.apache.org>>>;
> Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> I re-installed the marvin today to get the latest code.
> I am again facing the same problem in get_template. It is returning the
> windows template and creating the windows VM. Hence when it tries to do SSH
> for VM, it fails.
>
> I have also build the cloudstack to get the latest code for Marvin.
>
> PFA the script logs and test_loadbalance script for reference.
>
> Also, do let me know if I am missing some configuration or anything...
>
> Just an FYI.. I have executed 35 scripts in smoke test directory. Out of
> 35 scripts executed, 17-PASS, 18-FAIL.
> Around 50% failure are due to SSH related issue.
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Fri, Jan 10, 2014 at 5:53 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>>> wrote:
> 1. As such because of  bug in get_template, you are getting windows
> machine in your setup and then ssh is tried in test module, so you are
> getting the error.
>
> 2. Now, to overcome, just checkout the latest marvin, it should have a fix.
>
> Note: It still has some other issues, but you can continue with your
> testing further. Let us know.
>
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>]
> Sent: Friday, January 10, 2014 5:19 AM
> To: Santhosh Edukulla
> Cc: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><ma...@cloudstack.apache.org>>>>;
> Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> So far i have found the failure on following scripts:
> 1. test_loadbalance
> 2. test_network
> 3. test_nic
>
> In runinfo.txt log it is stuck at the step:
> SSH into VM (IPaddress: 10.1.1.55) & NAT Rule (Public IP: 207.x.x.x)
>
> PFA the Marvin logs for the test_loadbalance.py script.
>
> I have modified the following entry in the script i.e. provided the
> correct template name which is present.
> "ostype": "CentOS 6.4 (64-bit)",
> #"ostype": "CentOS 5.3 (64-bit)",
>
> Please let me know for your comments.
>
> Thanks and Regards
> -- Umesh Kute
>
>
>
> On Fri, Jan 10, 2014 at 2:57 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>>>>>>
> wrote:
> You can log the bug for this. We have fixed few other issues along with
> this in a private branch. Will soon merge with ACS. If you need a temporary
> fix, let me know.
>
> Question : Related to ssh issue, ssh to vm failing at which part? Can you
> add some information related to ssh failure which test module, which case
> etc? This may be related\unrelated to the above issue. We can check to see
> the issue is either same\different.
>
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>]
> Sent: Friday, January 10, 2014 4:21 AM
> To: Santhosh Edukulla
> Cc: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><ma...@cloudstack.apache.org>>>>>;
> Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thanks a lot Santhosh For your response.
>
> Sorry for delay.. But is there any workaround for this issue? Because as i
> mentioned, even if os type is provided as "ostype": 'CentOS 6.4 (64-bit)'
> it is picking up the first one in list i.e. Windows Server 2008 R2
> Enterprise.
> So some of the scripts which required to SSH into VM are failing.
>
> Can I get the JIRA ID for this issue to track?
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Fri, Jan 3, 2014 at 5:19 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>>>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>>>>> wrote:
> Umesh,
>
> This could be probably due to the bug under get_template function under
> marvin/integration/lib/common.py. Though, the ostype description is used
> and corresponding id is retrieved.
>
> But the later part, listTemplate API call returning the list and we are
> picking up either the template which is ready or matching with id we
> retrieved. This case is what could be causing the issue you mentioned.
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>]
> Sent: Friday, January 03, 2014 5:04 AM
> To: Santhosh Edukulla; users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>>>
> Cc: Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thanks for your help Santhosh!!!
>
> You are right...
> The public IP address range was exhausted. After cleaning up the
> resources, I was able to run the sample script "test_deploy_vm.py"
> successfully.
>
> One question - i have provided the "ostype": 'CentOS 6.4 (64-bit)'. What
> is the use of this parameter?
>
> When observed in management server logs and on cloudstack UI (while
> running script), VM was created of type: "Windows Server 2008 R2 Enterprise
> with SQL 2012 Web Edition". This is the first one in the list.
>
> Does it choose the one which we provided in script or picks it from the
> template list that is returned as a result of response to listTemplate API
> call?
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Thu, Jan 2, 2014 at 7:22 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>>>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>>>>>>>>
> wrote:
> Umesh,
>
> 1. It seems you have exhausted few of CloudStack Resources. These
> resources usage should show up on your cloudstack dashboard. Anything
> appears in Red are exhausted resources.
>
> 2. Few of the cases could be EX: Guest VM IPs\Management ip addresses  are
> exhausted,
>
> 3. Check for these resources in Red on your dashboard EX:
> http://localhost:8080/client/->Dashboard and clean up them or add new
> resources.
>
>
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>>]
> Sent: Thursday, January 02, 2014 7:06 AM
> To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>
> Cc: Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thank you once again Santhosh & Chandan.
>
> I have gone through the management server logs. The deployment of VM got
> fired to the setup correctly and there are couple of errors in the
> management-server log.
> I am summarizing those below:
>
> test data in "test_deploy_vm.py"
>  def __init__(self):
>         self.testdata = {
>             #data to create an account
>             "account": {
>                 "email": "test@test.com<ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>>>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>>>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>>>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>>>>>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>>>>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>>>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>>>>>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>>>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>>>>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>>>>>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>>>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>>>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>>>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>>>>>>>>",
>                 "firstname": "Test",
>                 "lastname": "User",
>                 "username": "test",
>                 "password": "password",
>             },
>             #data reqd for virtual machine creation
>             "virtual_machine" : {
>                 "name" : "testvmshr",
>                 "displayname" : "Test VM shr",
>             },
>             #small service offering
>             "service_offering": {
>                 "small": {
>                     "name": "SOSmall",
>                     "displaytext": "Small Instance",
>                     "cpunumber": 1,
>                     "cpuspeed": 2000,
>                     "memory": 1024,
>                 },
>             },
>             "ostype": 'CentOS 6.4 (64-bit)',
>         }
>
>
> 1. Account is successfully created
> 2. Service offering is successfully created
> 3. Management server logs - management-server.log has following error:
>
>
> 2014-01-02 01:43:40,693 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Lock is released for network Ntwk[326|Guest|15] as a part of network
> shutdown
> 2014-01-02 01:43:40,695 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Lock is released for network id 326 as a part of network implement
> 2014-01-02 01:43:40,695 INFO  [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Insufficient capacity
> com.cloud.exception.InsufficientAddressCapacityException: Insufficient
> address capacityScope=interface com.cloud.dc.DataCenter; id=1
> at
> com.cloud.network.NetworkManagerImpl.fetchNewPublicIp(NetworkManagerImpl.java:479)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.network.NetworkManagerImpl.assignDedicateIpAddress(NetworkManagerImpl.java:613)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.network.NetworkManagerImpl.assignSourceNatIpAddressToGuestNetwork(NetworkManagerImpl.java:582)
> at
> com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:2013)
> at
> com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1939)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2120)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:887)
> at
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:679)
> 2014-01-02 01:43:40,703 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Cleaning up resources for the vm VM[User|testvmshr] in Starting state
>
> 4. When i checked the database for the network id 326 in table "networks",
> it has following entry:
>
> | 326 | test-TestDeployVM-test_deploy_vm-QQ91N0-network |
> b7cb9e31-835f-47e3-9585-97e3b4084e4d |
> test-TestDeployVM-test_deploy_vm-QQ91N0-network | Guest        | Vlan
>            | NULL          | 10.1.1.1       | 10.1.1.0/24<
> http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><
> http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><
> http://10.1.1.0/24><http://10.1.1.0/24>     | Dhcp   |
>  15 |                 200 |              1 | ExternalGuestNetworkGuru |
> Destroy     |     326 |         1 |        305 | 8.8.8.8 | 8.8.4.4 | NULL
>    |          0 | Account  | cs131cloud.internal |
> ecf5b617-04da-469b-b378-f53e05d8cc53 | Isolated   |                0 |
> 2014-01-02 06:43:39 | 2014-01-02 06:43:46 |                 0 |   NULL |
> NULL        | NULL     | NULL         |               1 |           NULL |
>
>
> Basically it tries to create a network offering (id=15) : "HA Isolated
> Network With Source Nat"
>
>
> 5. I think the script creates a network shown in above table:
> "test-TestDeployVM-test_deploy_vm-QQ91N0-network".
>
> I am not sure why it still gives the Insufficient address capacityScope
> exception.
>
> 6. One more thing i observed. I have provided the "ostype": 'CentOS 6.4
> (64-bit)'. But in DeployVMCmd it uses the template id:
> "03ffb96f-2cfa-11e3-a4f0-f245a5b3ba0f" which is for template "Windows
> Server 2008 R2 Enterprise with SQL 2012 Web Edition".
>
>
> I am attaching the management-server logs and script logs for references.
>
> If somebody can help me what's wrong here, would really be helpful.
>
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Thu, Jan 2, 2014 at 2:59 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>>>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>>>>>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>>>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>>>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>>>>>>> wrote:
> 1. Is it still failing post this registration?
>
> 2. If yes, may be you can verify\provide the management server logs.
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>]
> Sent: Thursday, January 02, 2014 4:16 AM
> To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>>>>
> Cc: Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thanks Santhosh.
> Yes, I have registered the following template which i am using.
>
> "ostype": 'CentOS 6.4 (64-bit)',
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Mon, Dec 30, 2013 at 5:50 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>>>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>>>>>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>>>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>>>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>>>>>>> wrote:
>
> > Umesh,
> >
> > One question : Did you registered the template for ostype:     "ostype":
> > 'CentOS 5.3 (64-bit)'?
> >
> > Regards,
> > Santhosh
> > ________________________________________
> > From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>]
> > Sent: Monday, December 30, 2013 6:32 AM
> > To: Chandan Purushothama
> > Cc: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>>>>; Sudha Ponnaganti
> > Subject: Re: Regarding cloudstack automation
> >
> > Hi Chandan,
> > Thanks for your response.
> > I have the latest Marvin repository (December 20th). I am able to proceed
> > further. There was an issue of firewall for that machine and it got
> > resolved.
> >
> > But now i am getting another error when i tried to run the script
> > "test_deploy_vm.py"
> >
> > I have attached the log. Can somebody please have a look on it and help
> me
> > in resolving the issue?
> >
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > test_deploy_vm (integration.smoke.test_deploy_vm.TestDeployVM): CRITICAL:
> > EXCEPTION: test_deploy_vm: Traceback (most recent call last):
> >   File "/usr/local/lib/python2.7/unittest/case.py", line 327, in run
> >     testMethod()
> >   File
> > "/DataDisk/temp/cloudstack/test/integration/smoke/test_deploy_vm.py",
> line
> > 116, in test_deploy_vm
> >     templateid=self.template.id<http://self.template.id><
> http://self.template.id><http://self.template.id><http://self.template.id
> ><http://self.template.id><http://self.template.id><
> http://self.template.id><http://self.template.id><http://self.template.id>
> >   File
> > "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py",
> > line 415, in create
> >     virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> > line 593, in deployVirtualMachine
> >     response = self.connection.marvinRequest(command,
> > response_type=response, method=method)
> >   File
> > "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> > line 280, in marvinRequest
> >     response = self.poll(asyncJobId, response_type)
> >   File
> > "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> > line 86, in poll
> >     "asyncquery", asyncResonse.jobresult)
> > cloudstackAPIException: Execute cmd: asyncquery failed, due to:
> {errorcode
> > : 533, errortext : u'Unable to create a deployment for
> VM[User|testvmshr]'}
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > PFA entire logs.
> >
> > Please let me know in case if anything is required.
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> > On Sun, Dec 29, 2013 at 10:32 PM, Chandan Purushothama <
> > Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>>>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>>>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>>>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>>>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>>>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>>>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>>>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>>>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>>>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>>>>>>>>
> > wrote:
> >
> > Hello Umesh,
> >
> > I had a similar experience with an older Marvin build. I updated mine to
> > the latest and tried again and it worked. I recommend you to kindly try
> > again with the latest Marvin build and see if you are able to work with
> the
> > automation framework,
> >
> > Thank you,
> > Chandan
> >
> >
> > -------- Original message --------
> > From: umesh kute
> > Date:12/26/2013 12:29 AM (GMT-08:00)
> > To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>>>>>>,Sudha
> > Ponnaganti
> > Subject: Re: Regarding cloudstack automation
> >
> > Hi All,
> > I have created a Marvin setup on CentOS6.3 by following the document:
> >
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> >
> > All the pre-requisites are installed successfully.
> >
> > I tried to run the sample script test_deploy_vm.py
> > (cloudstack/test/integration/smoke/), I am getting following error:
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > [root@localhost smoke]# nosetests --with-marvin
> > --marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg
> --load
> > test_deploy_vm.py
> >
> >  Exception Occurred Under __deployDC :
> > HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> > with url: /client/api?account=admin&command=listUsers&response=json
> (Caused
> > by <class 'socket.error'>: [Errno 110] Connection timed out)
> > Traceback (most recent call last):
> >   File "/usr/local/bin/nosetests", line 9, in <module>
> >     load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> > line 118, in __init__
> >     **extra_args)
> >   File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
> >     self.runTests()
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> > line 197, in runTests
> >     result = self.testRunner.run(self.test)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> > line 61, in run
> >     test(result)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> > line 45, in __call__
> >     return self.run(*arg, **kwarg)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> > line 138, in run
> >     result.addError(self, err)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
> > line 124, in addError
> >     plugin_handled = plugins.handleError(self.test, err)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> > line 99, in __call__
> >     return self.call(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> > line 167, in simple
> >     result = meth(*arg, **kw)
> >   File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
> > line 155, in handleError
> >     self.tcRunLogger.fatal("%s: %s: %s" %
> > AttributeError: 'NoneType' object has no attribute 'fatal'
> >
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > The logs are generated at /tmp and the log has following error.
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > 2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
> > {'account': 'admin'}
> > 2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
> > http://10.88.91.100:8096/client/api :
> > HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> > with url: /client/api?account=admin&command=listUsers&response=json
> (Caused
> > by <class 'socket.error'>: [Errno 110] Connection timed out)
> >
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > Please note: I have opened the integration port 8096 on management
> server.
> > Also, changed the global settings integration.api.port
> > on cloudstack GUI to 8096 and restarted the management server.
> >
> > Still I am getting the above issue. I am not sure if i missed any
> > configuration.
> >
> > Can somebody please help me with resolution of this issue?
> > Appreciate your help here!!!
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> > On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>>>>><mailto:
> > umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>>> wrote:
> >
> > > Thanks a lot Sudha for your quick response.
> > > I will setup the Marvin on local machine and get back in case if I face
> > > any challenges in setup.
> > >
> > > Thanks and Regards
> > > -- Umesh Kute
> > >
> > >
> > >
> > > On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
> > > sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>>><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>>>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>>>>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>>>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>>>>>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>>>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>>>>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>>>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>>>>>>>>>
> wrote:
> > >
> > >> Hi Umesh,
> > >>
> > >> Looks like you have started on right track - Marvin is the framework
> to
> > >> use for functional or integration automation.
> > >> There are sizable number of test cases exist and you can review them.
> > >>  There are some wiki pages already written explaining Marvin [1]. Also
> > best
> > >> practices are published by community as well [2]. You can contribute
> to
> > it
> > >> as much as you can.
> > >>
> > >> Besides this, there is Junit framework (unit Test), Selenium framework
> > >> (UI automation) which are not as popular as Marvin. Marvin is perfect
> > for
> > >> majority of the validation. You can use simulator as well with Marvin.
> > >>
> > >> Please do pursue these and post questions to the community if you run
> in
> > >> to any issues in setting up env and running tests. There are jobs
> setup
> > by
> > >> various community members to test Master or current releases in
> various
> > >> labs and can help answer questions.
> > >>
> > >> [1]
> > >>
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> > >>
> > >>
> > >> Thanks
> > >> /Sudha
> > >>
> > >>
> > >> -----Original Message-----
> > >> From: umesh kute [mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>>>>>]
> > >> Sent: Saturday, December 07, 2013 10:29 PM
> > >> To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>>
> > >> Subject: Regarding cloudstack automation
> > >>
> > >> Hi All,
> > >> Good morning !!!
> > >> I am working as QA engineer and I am new to the cloudstack community.
> > >> We have started using cloudstack and deployed it in our
> infrastructure.
> > >>
> > >> Can somebody please help me in identifying the good automation
> > >> framework/tool/anything? The main intention is we want to automate the
> > >> infrastructure validation related cases (for e.g. create/update/delete
> > >> cases for instances, project, network, etc...)
> > >>
> > >> It would be good if you can help in identifying it.
> > >>
> > >> Please note: I have gone through cloudmonkey. But i haven't found much
> > >> help on it. May be i need to search a bit more.. I am also going
> through
> > >> the marvin and planning to setup it. If apart from these two, if
> anyone
> > has
> > >> different view please suggest.
> > >>
> > >> Also, if somebody has any pointers on cloudmonkey and marvin or any
> more
> > >> info on this (like, if it would suffice the infrastructure validation
> > >> related cases i mentioned above) any pros/cons would really be helpful
> > for
> > >> me...
> > >>
> > >> Appreciate any help on this and looking forward for the response on
> > >> this!!!
> > >>
> > >> Thanks and Regards
> > >> -- Umesh Kute
> > >>
> > >
> > >
> >
> >
>
>
>
>
>

RE: Regarding cloudstack automation

[Santhosh Edukulla <sa...@citrix.com>]

Umesh,

1. Observing few issues, is the host, refreshed to clean state or a fresh one with out any  zones,vms  etc? Can you get your host(hypervisor) to a clean state before proceeding with your automation or regression run?  

2. Deploy the DC using marvin and then run your automation thereafter.

Thanks!
Santhosh
________________________________________
From: Santhosh Edukulla
Sent: Wednesday, January 29, 2014 1:27 AM
To: umesh kute
Cc: users@cloudstack.apache.org; Chandan Purushothama; Sudha Ponnaganti; dev@cloudstack.apache.org
Subject: RE: Regarding cloudstack automation

Umesh,

1. Haven't had much time to look in to them in detail.

2. Can you please create few jira tickets for failures especially for the exceptions thrown under failed_plus_exceptions file for each test module? Look only for exceptions not assertion errors. I created one as below for few exceptions
in your log file.

EX: https://issues.apache.org/jira/browse/CLOUDSTACK-5973

3. This will help to look in to issues more clearly and fix them if there are any issues.

4. Note, the errors could be specific to setup\test scripts, not related to marvin.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com]
Sent: Tuesday, January 28, 2014 1:01 PM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org; Chandan Purushothama; Sudha Ponnaganti; dev@cloudstack.apache.org
Subject: Re: Regarding cloudstack automation

Hi Santhosh,
Did you get the chance to look into the log for the issue?

Thanks and Regards
-- Umesh Kute


On Mon, Jan 27, 2014 at 6:31 PM, umesh kute <um...@gmail.com>> wrote:
Hi Santhosh,
I am attaching the failure logs in the zip file for 10 scripts executed so far. PFA (ComponetTestSuite_AllLogs.zip)

Regarding point#3, for BVT, there are 18-Pass, 17-Failed out of 35 cases.
That would be good, if you can let me know if there is any issue in marvin setup or configuration which i am using.

Please let me know if any additional information is required.

Thanks and Regards
-- Umesh Kute


On Fri, Jan 24, 2014 at 6:57 PM, Santhosh Edukulla <sa...@citrix.com>> wrote:
Umesh,

1. There should not be any issues inherent inside of it as such not to run scripts atleast existing ones altogether. Now, compared to earlier mentioned failures viz., ssh,password, template etc ,these are mainly away from framework and are setup issues.

2. Component signifies regression cases, if you already know. Now for the run and failures count, mentioned below, can you let us know what are the failures or You can attach logs to elucidate the failures? Regression do run almost every day for various releases and has many passes and failures if any for product logged as bugs. The pass % for regression is more than 90% as far iam aware. The failures below, could be mainly due to infrastructure\setup specific or the way we may perceive it to run because of it few limitations.

3. We can help you to setup and start running marvin. Are all cases for bvt running first and with no issues? Mention the host and infrastructure setup details and flow you are using.

4. Also, we have a topic branch created for marvin. If you see an issue anywhere, you can log a bug, submit a patch for review to fix the same there.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>]
Sent: Friday, January 24, 2014 8:04 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>; Chandan Purushothama; Sudha Ponnaganti; dev@cloudstack.apache.org<ma...@cloudstack.apache.org>
Subject: Re: Regarding cloudstack automation

Hi Santhosh,
To proceed further I deployed the template by disabling password and providing the default password as "password". Now its able to connect using ssh.

But when I started with the test case execution for the scripts which are there in "component folder", Out of 80 scripts, executed 11 and all 11 are failing (mentioned below).

test_affinity_groups.py
test_add_remove_network.py
test_accounts.py
test_allocation_states.py
test_baremetal.py
test_assign_vm.py
test_vm_passwdenabled.py
test_vpc_vm_life_cycle.py
test_vpc_routers.py
test_vpn_users.py
test_vpc_vms_deployment.py

Are there any issues with Marvin framework for running component script and is it executed before? I am facing many failures in a script.

If required I can share the logs.

Please note: We have a cloudstack 4.2 deployed in lab. We planned to use the Marvin to validate the cloudstack infrastructure. I have installed the marvin (0.1.0) and cloudstack using (4.2).

Thanks and Regards
-- Umesh Kute


On Sat, Jan 18, 2014 at 2:31 AM, Santhosh Edukulla <sa...@citrix.com>>> wrote:
Umesh,

1. Its good that the template issue is resolved.

2. Regarding point 4 mentioned below, your understanding is right. The idea is during automation run for various test suites,  we use a template seeded into CS which has the password set with the one used in Services Class. So, in a way for all test suites having this password mentioned is assumed to be having an instance deployed with template matching our condition and so ssh works.

3. There are test cases pertaining explicitly to verify reset cases under CS, that covers scenarios to test, but for every ssh we dont use the password given by the API output.

4. So, for creating instances you can use a template with password as "password" for your testing, thats the easy solution i believe and all test suits has this password inside them, it will work. In a way, this not so a good design, but
We are planning to remove Services class test data from tests and separate it out as a test data, So for user running tests can alter the config to suit the template he has and all test suites using ssh works and will be configurable, compared to now we have to modify all test suites to get it working with custom password for user.

Thanks!
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>]
Sent: Friday, January 17, 2014 7:32 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Hi Santhosh,
Thanks again...
I tried the steps that you mentioned below. Fortunately i could able to proceed a bit further on this issue.

Now, instance got created successfully of type CentOS 6.4 (64-bit).

It is stuck in the ssh step.
Here is what happens...

1. All the steps/APIs till instance creation works fine (including listDomains, listZones, listOsTypes, listTemplates, createAccount, createServiceOffering, deployVirtualMachine, queryAsyncJobResult, associateIPAddress, createFirewallRules, createPortForwardingRule, createEgressFirewallRule)

2. When it tries to SSH to virtual machine it fails after timeout of 600s (20-retries, 30-intervals). Script is terminated.

3. I put some debug statements in function get_ssh_client() under: "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py"

The credentials i think it tries is :
self.ssh_ip: 207.x.x.x
self.ssh_port: 22
self.username: root
self.password: password
keyPairFileLocation: None

It means, it tries to connect to instance using password as password (it is provided in dictionary in test_vm_passwdenabled.py. Note: Earlier i gave references for test_loadbalance.py and its the same case).

4. In log, i found that the password that is returned in response to deployVirtualMachine API call is: xA2yeaxvb. (PFA file runinfo). When i tried to do ssh to the instance with same password it works and with dictionary "password" it doesn't. I think so.. please confirm...

Either, for ssh connection it should use the returned password or reset password before connection.

PFA all the logs.
Please correct if my understanding is correct or I am missing something here....

Please let me know if there is any resolution of this issue or if somebody encounters it before.

Thanks and Regards
-- Umesh Kute

On Tue, Jan 14, 2014 at 6:48 PM, Santhosh Edukulla <sa...@citrix.com>>>> wrote:
Umesh,

Lets put steps so that we are in same page:

1. When we deploy  a VM, we use get_template function which basically retrieves the template information matching the description you provided under services class for ostype under test module EX: test_loadbalance.py.  I am surprised that you are receiving a "featured" and "builtin" template as windows template as output for this function. We are explicitly verifiying the template type as "BUILTIN" to retrieve the template information. So, a windows template cannot be a BUILTIN Template. Either it could be a bug in this function, or something with API. But, to double confirm, Can you please check whats the template information you are retrieving from this function matching with listTemplates API output( run either from your browser or script )  passing the same arguments as passed inside get_template?

Inside if we see, basically it gets the id matching with that ostype description using "listOsTypes"  and then use "listTemplates" command. So, this template is used to deploy the vm.  As far as i know, a builtin template cannot be a windows template?  Here, we use a featured and builtin template along with description filter passed. So, please check whether the template you are retrieving is windows or otherwise. Check for the field ostypename for the output you receive? Provide the output here for get_template copy pasted with dir(template) for return value?

2. To double confirm that it is template issue and not any other issue related to ssh like ( firewall\iptables\network connectivity issue) for ssh, please manually check for that particular ip in the test case whether ssh works or not and is not a windows machine?

3. Run one test case, first by adding a tag EX: "umesh" to the tags list as mentioned below for a particular test case under test module EX: test_loadbalance.py, then  run with nose command passing in tags argument mentioned below.

 @attr(tags = ["advanced", "advancedns", "smoke", "umesh"])
    def test_01_create_lb_rule_src_nat(self):

nosetests-2.7 -v --with-marvin --marvin-config=/root/softwares/cscode/setup/dev/advanced.cfg --load -a -w /root/softwares/cscode/test/integration/smoke/ -a tags=umesh

Let me know.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>]
Sent: Tuesday, January 14, 2014 7:02 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

I re-installed the marvin today to get the latest code.
I am again facing the same problem in get_template. It is returning the windows template and creating the windows VM. Hence when it tries to do SSH for VM, it fails.

I have also build the cloudstack to get the latest code for Marvin.

PFA the script logs and test_loadbalance script for reference.

Also, do let me know if I am missing some configuration or anything...

Just an FYI.. I have executed 35 scripts in smoke test directory. Out of 35 scripts executed, 17-PASS, 18-FAIL.
Around 50% failure are due to SSH related issue.

Thanks and Regards
-- Umesh Kute


On Fri, Jan 10, 2014 at 5:53 PM, Santhosh Edukulla <sa...@citrix.com>>>>> wrote:
1. As such because of  bug in get_template, you are getting windows machine in your setup and then ssh is tried in test module, so you are getting the error.

2. Now, to overcome, just checkout the latest marvin, it should have a fix.

Note: It still has some other issues, but you can continue with your testing further. Let us know.

Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>]
Sent: Friday, January 10, 2014 5:19 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

So far i have found the failure on following scripts:
1. test_loadbalance
2. test_network
3. test_nic

In runinfo.txt log it is stuck at the step:
SSH into VM (IPaddress: 10.1.1.55) & NAT Rule (Public IP: 207.x.x.x)

PFA the Marvin logs for the test_loadbalance.py script.

I have modified the following entry in the script i.e. provided the correct template name which is present.
"ostype": "CentOS 6.4 (64-bit)",
#"ostype": "CentOS 5.3 (64-bit)",

Please let me know for your comments.

Thanks and Regards
-- Umesh Kute



On Fri, Jan 10, 2014 at 2:57 PM, Santhosh Edukulla <sa...@citrix.com>>>>>> wrote:
You can log the bug for this. We have fixed few other issues along with this in a private branch. Will soon merge with ACS. If you need a temporary fix, let me know.

Question : Related to ssh issue, ssh to vm failing at which part? Can you add some information related to ssh failure which test module, which case etc? This may be related\unrelated to the above issue. We can check to see the issue is either same\different.

Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>]
Sent: Friday, January 10, 2014 4:21 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks a lot Santhosh For your response.

Sorry for delay.. But is there any workaround for this issue? Because as i mentioned, even if os type is provided as "ostype": 'CentOS 6.4 (64-bit)' it is picking up the first one in list i.e. Windows Server 2008 R2 Enterprise.
So some of the scripts which required to SSH into VM are failing.

Can I get the JIRA ID for this issue to track?

Thanks and Regards
-- Umesh Kute


On Fri, Jan 3, 2014 at 5:19 PM, Santhosh Edukulla <sa...@citrix.com>>>>>>> wrote:
Umesh,

This could be probably due to the bug under get_template function under marvin/integration/lib/common.py. Though, the ostype description is used and corresponding id is retrieved.

But the later part, listTemplate API call returning the list and we are picking up either the template which is ready or matching with id we retrieved. This case is what could be causing the issue you mentioned.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>]
Sent: Friday, January 03, 2014 5:04 AM
To: Santhosh Edukulla; users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks for your help Santhosh!!!

You are right...
The public IP address range was exhausted. After cleaning up the resources, I was able to run the sample script "test_deploy_vm.py" successfully.

One question - i have provided the "ostype": 'CentOS 6.4 (64-bit)'. What is the use of this parameter?

When observed in management server logs and on cloudstack UI (while running script), VM was created of type: "Windows Server 2008 R2 Enterprise with SQL 2012 Web Edition". This is the first one in the list.

Does it choose the one which we provided in script or picks it from the template list that is returned as a result of response to listTemplate API call?

Thanks and Regards
-- Umesh Kute


On Thu, Jan 2, 2014 at 7:22 PM, Santhosh Edukulla <sa...@citrix.com>>>>>>>> wrote:
Umesh,

1. It seems you have exhausted few of CloudStack Resources. These resources usage should show up on your cloudstack dashboard. Anything appears in Red are exhausted resources.

2. Few of the cases could be EX: Guest VM IPs\Management ip addresses  are exhausted,

3. Check for these resources in Red on your dashboard EX: http://localhost:8080/client/->Dashboard and clean up them or add new resources.


Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>>]
Sent: Thursday, January 02, 2014 7:06 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thank you once again Santhosh & Chandan.

I have gone through the management server logs. The deployment of VM got fired to the setup correctly and there are couple of errors in the management-server log.
I am summarizing those below:

test data in "test_deploy_vm.py"
 def __init__(self):
        self.testdata = {
            #data to create an account
            "account": {
                "email": "test@test.com<ma...@test.com>>>>>>>>",
                "firstname": "Test",
                "lastname": "User",
                "username": "test",
                "password": "password",
            },
            #data reqd for virtual machine creation
            "virtual_machine" : {
                "name" : "testvmshr",
                "displayname" : "Test VM shr",
            },
            #small service offering
            "service_offering": {
                "small": {
                    "name": "SOSmall",
                    "displaytext": "Small Instance",
                    "cpunumber": 1,
                    "cpuspeed": 2000,
                    "memory": 1024,
                },
            },
            "ostype": 'CentOS 6.4 (64-bit)',
        }


1. Account is successfully created
2. Service offering is successfully created
3. Management server logs - management-server.log has following error:


2014-01-02 01:43:40,693 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Lock is released for network Ntwk[326|Guest|15] as a part of network shutdown
2014-01-02 01:43:40,695 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Lock is released for network id 326 as a part of network implement
2014-01-02 01:43:40,695 INFO  [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Insufficient capacity
com.cloud.exception.InsufficientAddressCapacityException: Insufficient address capacityScope=interface com.cloud.dc.DataCenter; id=1
at com.cloud.network.NetworkManagerImpl.fetchNewPublicIp(NetworkManagerImpl.java:479)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.assignDedicateIpAddress(NetworkManagerImpl.java:613)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.assignSourceNatIpAddressToGuestNetwork(NetworkManagerImpl.java:582)
at com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:2013)
at com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1939)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2120)
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:887)
at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2014-01-02 01:43:40,703 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Cleaning up resources for the vm VM[User|testvmshr] in Starting state

4. When i checked the database for the network id 326 in table "networks", it has following entry:

| 326 | test-TestDeployVM-test_deploy_vm-QQ91N0-network | b7cb9e31-835f-47e3-9585-97e3b4084e4d | test-TestDeployVM-test_deploy_vm-QQ91N0-network | Guest        | Vlan                  | NULL          | 10.1.1.1       | 10.1.1.0/24<http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24>     | Dhcp   |                  15 |                 200 |              1 | ExternalGuestNetworkGuru | Destroy     |     326 |         1 |        305 | 8.8.8.8 | 8.8.4.4 | NULL      |          0 | Account  | cs131cloud.internal | ecf5b617-04da-469b-b378-f53e05d8cc53 | Isolated   |                0 | 2014-01-02 06:43:39 | 2014-01-02 06:43:46 |                 0 |   NULL | NULL        | NULL     | NULL         |               1 |           NULL |


Basically it tries to create a network offering (id=15) : "HA Isolated Network With Source Nat"


5. I think the script creates a network shown in above table: "test-TestDeployVM-test_deploy_vm-QQ91N0-network".

I am not sure why it still gives the Insufficient address capacityScope exception.

6. One more thing i observed. I have provided the "ostype": 'CentOS 6.4 (64-bit)'. But in DeployVMCmd it uses the template id: "03ffb96f-2cfa-11e3-a4f0-f245a5b3ba0f" which is for template "Windows Server 2008 R2 Enterprise with SQL 2012 Web Edition".


I am attaching the management-server logs and script logs for references.

If somebody can help me what's wrong here, would really be helpful.


Thanks and Regards
-- Umesh Kute


On Thu, Jan 2, 2014 at 2:59 PM, Santhosh Edukulla <sa...@citrix.com>>>>>>>>> wrote:
1. Is it still failing post this registration?

2. If yes, may be you can verify\provide the management server logs.
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>]
Sent: Thursday, January 02, 2014 4:16 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks Santhosh.
Yes, I have registered the following template which i am using.

"ostype": 'CentOS 6.4 (64-bit)',

Thanks and Regards
-- Umesh Kute


On Mon, Dec 30, 2013 at 5:50 PM, Santhosh Edukulla <
santhosh.edukulla@citrix.com<ma...@citrix.com>>>>>>>>> wrote:

> Umesh,
>
> One question : Did you registered the template for ostype:     "ostype":
> 'CentOS 5.3 (64-bit)'?
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>]
> Sent: Monday, December 30, 2013 6:32 AM
> To: Chandan Purushothama
> Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi Chandan,
> Thanks for your response.
> I have the latest Marvin repository (December 20th). I am able to proceed
> further. There was an issue of firewall for that machine and it got
> resolved.
>
> But now i am getting another error when i tried to run the script
> "test_deploy_vm.py"
>
> I have attached the log. Can somebody please have a look on it and help me
> in resolving the issue?
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> test_deploy_vm (integration.smoke.test_deploy_vm.TestDeployVM): CRITICAL:
> EXCEPTION: test_deploy_vm: Traceback (most recent call last):
>   File "/usr/local/lib/python2.7/unittest/case.py", line 327, in run
>     testMethod()
>   File
> "/DataDisk/temp/cloudstack/test/integration/smoke/test_deploy_vm.py", line
> 116, in test_deploy_vm
>     templateid=self.template.id<http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id>
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py",
> line 415, in create
>     virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> line 593, in deployVirtualMachine
>     response = self.connection.marvinRequest(command,
> response_type=response, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 280, in marvinRequest
>     response = self.poll(asyncJobId, response_type)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 86, in poll
>     "asyncquery", asyncResonse.jobresult)
> cloudstackAPIException: Execute cmd: asyncquery failed, due to: {errorcode
> : 533, errortext : u'Unable to create a deployment for VM[User|testvmshr]'}
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> PFA entire logs.
>
> Please let me know in case if anything is required.
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Sun, Dec 29, 2013 at 10:32 PM, Chandan Purushothama <
> Chandan.Purushothama@citrix.com<ma...@citrix.com>>>>>>>>>>
> wrote:
>
> Hello Umesh,
>
> I had a similar experience with an older Marvin build. I updated mine to
> the latest and tried again and it worked. I recommend you to kindly try
> again with the latest Marvin build and see if you are able to work with the
> automation framework,
>
> Thank you,
> Chandan
>
>
> -------- Original message --------
> From: umesh kute
> Date:12/26/2013 12:29 AM (GMT-08:00)
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>>,Sudha
> Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi All,
> I have created a Marvin setup on CentOS6.3 by following the document:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
>
> All the pre-requisites are installed successfully.
>
> I tried to run the sample script test_deploy_vm.py
> (cloudstack/test/integration/smoke/), I am getting following error:
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> [root@localhost smoke]# nosetests --with-marvin
> --marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg --load
> test_deploy_vm.py
>
>  Exception Occurred Under __deployDC :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
> Traceback (most recent call last):
>   File "/usr/local/bin/nosetests", line 9, in <module>
>     load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 118, in __init__
>     **extra_args)
>   File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
>     self.runTests()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 197, in runTests
>     result = self.testRunner.run(self.test)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 61, in run
>     test(result)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 45, in __call__
>     return self.run(*arg, **kwarg)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 138, in run
>     result.addError(self, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
> line 124, in addError
>     plugin_handled = plugins.handleError(self.test, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 99, in __call__
>     return self.call(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 167, in simple
>     result = meth(*arg, **kw)
>   File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
> line 155, in handleError
>     self.tcRunLogger.fatal("%s: %s: %s" %
> AttributeError: 'NoneType' object has no attribute 'fatal'
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> The logs are generated at /tmp and the log has following error.
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
> {'account': 'admin'}
> 2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
> http://10.88.91.100:8096/client/api :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Please note: I have opened the integration port 8096 on management server.
> Also, changed the global settings integration.api.port
> on cloudstack GUI to 8096 and restarted the management server.
>
> Still I am getting the above issue. I am not sure if i missed any
> configuration.
>
> Can somebody please help me with resolution of this issue?
> Appreciate your help here!!!
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <um...@gmail.com>>>>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>>> wrote:
>
> > Thanks a lot Sudha for your quick response.
> > I will setup the Marvin on local machine and get back in case if I face
> > any challenges in setup.
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> >
> > On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
> > sudha.ponnaganti@citrix.com<ma...@citrix.com>>>>>>>>>> wrote:
> >
> >> Hi Umesh,
> >>
> >> Looks like you have started on right track - Marvin is the framework to
> >> use for functional or integration automation.
> >> There are sizable number of test cases exist and you can review them.
> >>  There are some wiki pages already written explaining Marvin [1]. Also
> best
> >> practices are published by community as well [2]. You can contribute to
> it
> >> as much as you can.
> >>
> >> Besides this, there is Junit framework (unit Test), Selenium framework
> >> (UI automation) which are not as popular as Marvin. Marvin is perfect
> for
> >> majority of the validation. You can use simulator as well with Marvin.
> >>
> >> Please do pursue these and post questions to the community if you run in
> >> to any issues in setting up env and running tests. There are jobs setup
> by
> >> various community members to test Master or current releases in various
> >> labs and can help answer questions.
> >>
> >> [1]
> >>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> >>
> >>
> >> Thanks
> >> /Sudha
> >>
> >>
> >> -----Original Message-----
> >> From: umesh kute [mailto:umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>]
> >> Sent: Saturday, December 07, 2013 10:29 PM
> >> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>>
> >> Subject: Regarding cloudstack automation
> >>
> >> Hi All,
> >> Good morning !!!
> >> I am working as QA engineer and I am new to the cloudstack community.
> >> We have started using cloudstack and deployed it in our infrastructure.
> >>
> >> Can somebody please help me in identifying the good automation
> >> framework/tool/anything? The main intention is we want to automate the
> >> infrastructure validation related cases (for e.g. create/update/delete
> >> cases for instances, project, network, etc...)
> >>
> >> It would be good if you can help in identifying it.
> >>
> >> Please note: I have gone through cloudmonkey. But i haven't found much
> >> help on it. May be i need to search a bit more.. I am also going through
> >> the marvin and planning to setup it. If apart from these two, if anyone
> has
> >> different view please suggest.
> >>
> >> Also, if somebody has any pointers on cloudmonkey and marvin or any more
> >> info on this (like, if it would suffice the infrastructure validation
> >> related cases i mentioned above) any pros/cons would really be helpful
> for
> >> me...
> >>
> >> Appreciate any help on this and looking forward for the response on
> >> this!!!
> >>
> >> Thanks and Regards
> >> -- Umesh Kute
> >>
> >
> >
>
>

RE: Regarding cloudstack automation

[Santhosh Edukulla <sa...@citrix.com>]

Umesh,

1. Observing few issues, is the host, refreshed to clean state or a fresh one with out any  zones,vms  etc? Can you get your host(hypervisor) to a clean state before proceeding with your automation or regression run?  

2. Deploy the DC using marvin and then run your automation thereafter.

Thanks!
Santhosh
________________________________________
From: Santhosh Edukulla
Sent: Wednesday, January 29, 2014 1:27 AM
To: umesh kute
Cc: users@cloudstack.apache.org; Chandan Purushothama; Sudha Ponnaganti; dev@cloudstack.apache.org
Subject: RE: Regarding cloudstack automation

Umesh,

1. Haven't had much time to look in to them in detail.

2. Can you please create few jira tickets for failures especially for the exceptions thrown under failed_plus_exceptions file for each test module? Look only for exceptions not assertion errors. I created one as below for few exceptions
in your log file.

EX: https://issues.apache.org/jira/browse/CLOUDSTACK-5973

3. This will help to look in to issues more clearly and fix them if there are any issues.

4. Note, the errors could be specific to setup\test scripts, not related to marvin.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com]
Sent: Tuesday, January 28, 2014 1:01 PM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org; Chandan Purushothama; Sudha Ponnaganti; dev@cloudstack.apache.org
Subject: Re: Regarding cloudstack automation

Hi Santhosh,
Did you get the chance to look into the log for the issue?

Thanks and Regards
-- Umesh Kute


On Mon, Jan 27, 2014 at 6:31 PM, umesh kute <um...@gmail.com>> wrote:
Hi Santhosh,
I am attaching the failure logs in the zip file for 10 scripts executed so far. PFA (ComponetTestSuite_AllLogs.zip)

Regarding point#3, for BVT, there are 18-Pass, 17-Failed out of 35 cases.
That would be good, if you can let me know if there is any issue in marvin setup or configuration which i am using.

Please let me know if any additional information is required.

Thanks and Regards
-- Umesh Kute


On Fri, Jan 24, 2014 at 6:57 PM, Santhosh Edukulla <sa...@citrix.com>> wrote:
Umesh,

1. There should not be any issues inherent inside of it as such not to run scripts atleast existing ones altogether. Now, compared to earlier mentioned failures viz., ssh,password, template etc ,these are mainly away from framework and are setup issues.

2. Component signifies regression cases, if you already know. Now for the run and failures count, mentioned below, can you let us know what are the failures or You can attach logs to elucidate the failures? Regression do run almost every day for various releases and has many passes and failures if any for product logged as bugs. The pass % for regression is more than 90% as far iam aware. The failures below, could be mainly due to infrastructure\setup specific or the way we may perceive it to run because of it few limitations.

3. We can help you to setup and start running marvin. Are all cases for bvt running first and with no issues? Mention the host and infrastructure setup details and flow you are using.

4. Also, we have a topic branch created for marvin. If you see an issue anywhere, you can log a bug, submit a patch for review to fix the same there.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>]
Sent: Friday, January 24, 2014 8:04 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>; Chandan Purushothama; Sudha Ponnaganti; dev@cloudstack.apache.org<ma...@cloudstack.apache.org>
Subject: Re: Regarding cloudstack automation

Hi Santhosh,
To proceed further I deployed the template by disabling password and providing the default password as "password". Now its able to connect using ssh.

But when I started with the test case execution for the scripts which are there in "component folder", Out of 80 scripts, executed 11 and all 11 are failing (mentioned below).

test_affinity_groups.py
test_add_remove_network.py
test_accounts.py
test_allocation_states.py
test_baremetal.py
test_assign_vm.py
test_vm_passwdenabled.py
test_vpc_vm_life_cycle.py
test_vpc_routers.py
test_vpn_users.py
test_vpc_vms_deployment.py

Are there any issues with Marvin framework for running component script and is it executed before? I am facing many failures in a script.

If required I can share the logs.

Please note: We have a cloudstack 4.2 deployed in lab. We planned to use the Marvin to validate the cloudstack infrastructure. I have installed the marvin (0.1.0) and cloudstack using (4.2).

Thanks and Regards
-- Umesh Kute


On Sat, Jan 18, 2014 at 2:31 AM, Santhosh Edukulla <sa...@citrix.com>>> wrote:
Umesh,

1. Its good that the template issue is resolved.

2. Regarding point 4 mentioned below, your understanding is right. The idea is during automation run for various test suites,  we use a template seeded into CS which has the password set with the one used in Services Class. So, in a way for all test suites having this password mentioned is assumed to be having an instance deployed with template matching our condition and so ssh works.

3. There are test cases pertaining explicitly to verify reset cases under CS, that covers scenarios to test, but for every ssh we dont use the password given by the API output.

4. So, for creating instances you can use a template with password as "password" for your testing, thats the easy solution i believe and all test suits has this password inside them, it will work. In a way, this not so a good design, but
We are planning to remove Services class test data from tests and separate it out as a test data, So for user running tests can alter the config to suit the template he has and all test suites using ssh works and will be configurable, compared to now we have to modify all test suites to get it working with custom password for user.

Thanks!
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>]
Sent: Friday, January 17, 2014 7:32 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Hi Santhosh,
Thanks again...
I tried the steps that you mentioned below. Fortunately i could able to proceed a bit further on this issue.

Now, instance got created successfully of type CentOS 6.4 (64-bit).

It is stuck in the ssh step.
Here is what happens...

1. All the steps/APIs till instance creation works fine (including listDomains, listZones, listOsTypes, listTemplates, createAccount, createServiceOffering, deployVirtualMachine, queryAsyncJobResult, associateIPAddress, createFirewallRules, createPortForwardingRule, createEgressFirewallRule)

2. When it tries to SSH to virtual machine it fails after timeout of 600s (20-retries, 30-intervals). Script is terminated.

3. I put some debug statements in function get_ssh_client() under: "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py"

The credentials i think it tries is :
self.ssh_ip: 207.x.x.x
self.ssh_port: 22
self.username: root
self.password: password
keyPairFileLocation: None

It means, it tries to connect to instance using password as password (it is provided in dictionary in test_vm_passwdenabled.py. Note: Earlier i gave references for test_loadbalance.py and its the same case).

4. In log, i found that the password that is returned in response to deployVirtualMachine API call is: xA2yeaxvb. (PFA file runinfo). When i tried to do ssh to the instance with same password it works and with dictionary "password" it doesn't. I think so.. please confirm...

Either, for ssh connection it should use the returned password or reset password before connection.

PFA all the logs.
Please correct if my understanding is correct or I am missing something here....

Please let me know if there is any resolution of this issue or if somebody encounters it before.

Thanks and Regards
-- Umesh Kute

On Tue, Jan 14, 2014 at 6:48 PM, Santhosh Edukulla <sa...@citrix.com>>>> wrote:
Umesh,

Lets put steps so that we are in same page:

1. When we deploy  a VM, we use get_template function which basically retrieves the template information matching the description you provided under services class for ostype under test module EX: test_loadbalance.py.  I am surprised that you are receiving a "featured" and "builtin" template as windows template as output for this function. We are explicitly verifiying the template type as "BUILTIN" to retrieve the template information. So, a windows template cannot be a BUILTIN Template. Either it could be a bug in this function, or something with API. But, to double confirm, Can you please check whats the template information you are retrieving from this function matching with listTemplates API output( run either from your browser or script )  passing the same arguments as passed inside get_template?

Inside if we see, basically it gets the id matching with that ostype description using "listOsTypes"  and then use "listTemplates" command. So, this template is used to deploy the vm.  As far as i know, a builtin template cannot be a windows template?  Here, we use a featured and builtin template along with description filter passed. So, please check whether the template you are retrieving is windows or otherwise. Check for the field ostypename for the output you receive? Provide the output here for get_template copy pasted with dir(template) for return value?

2. To double confirm that it is template issue and not any other issue related to ssh like ( firewall\iptables\network connectivity issue) for ssh, please manually check for that particular ip in the test case whether ssh works or not and is not a windows machine?

3. Run one test case, first by adding a tag EX: "umesh" to the tags list as mentioned below for a particular test case under test module EX: test_loadbalance.py, then  run with nose command passing in tags argument mentioned below.

 @attr(tags = ["advanced", "advancedns", "smoke", "umesh"])
    def test_01_create_lb_rule_src_nat(self):

nosetests-2.7 -v --with-marvin --marvin-config=/root/softwares/cscode/setup/dev/advanced.cfg --load -a -w /root/softwares/cscode/test/integration/smoke/ -a tags=umesh

Let me know.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>]
Sent: Tuesday, January 14, 2014 7:02 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

I re-installed the marvin today to get the latest code.
I am again facing the same problem in get_template. It is returning the windows template and creating the windows VM. Hence when it tries to do SSH for VM, it fails.

I have also build the cloudstack to get the latest code for Marvin.

PFA the script logs and test_loadbalance script for reference.

Also, do let me know if I am missing some configuration or anything...

Just an FYI.. I have executed 35 scripts in smoke test directory. Out of 35 scripts executed, 17-PASS, 18-FAIL.
Around 50% failure are due to SSH related issue.

Thanks and Regards
-- Umesh Kute


On Fri, Jan 10, 2014 at 5:53 PM, Santhosh Edukulla <sa...@citrix.com>>>>> wrote:
1. As such because of  bug in get_template, you are getting windows machine in your setup and then ssh is tried in test module, so you are getting the error.

2. Now, to overcome, just checkout the latest marvin, it should have a fix.

Note: It still has some other issues, but you can continue with your testing further. Let us know.

Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>]
Sent: Friday, January 10, 2014 5:19 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

So far i have found the failure on following scripts:
1. test_loadbalance
2. test_network
3. test_nic

In runinfo.txt log it is stuck at the step:
SSH into VM (IPaddress: 10.1.1.55) & NAT Rule (Public IP: 207.x.x.x)

PFA the Marvin logs for the test_loadbalance.py script.

I have modified the following entry in the script i.e. provided the correct template name which is present.
"ostype": "CentOS 6.4 (64-bit)",
#"ostype": "CentOS 5.3 (64-bit)",

Please let me know for your comments.

Thanks and Regards
-- Umesh Kute



On Fri, Jan 10, 2014 at 2:57 PM, Santhosh Edukulla <sa...@citrix.com>>>>>> wrote:
You can log the bug for this. We have fixed few other issues along with this in a private branch. Will soon merge with ACS. If you need a temporary fix, let me know.

Question : Related to ssh issue, ssh to vm failing at which part? Can you add some information related to ssh failure which test module, which case etc? This may be related\unrelated to the above issue. We can check to see the issue is either same\different.

Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>]
Sent: Friday, January 10, 2014 4:21 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks a lot Santhosh For your response.

Sorry for delay.. But is there any workaround for this issue? Because as i mentioned, even if os type is provided as "ostype": 'CentOS 6.4 (64-bit)' it is picking up the first one in list i.e. Windows Server 2008 R2 Enterprise.
So some of the scripts which required to SSH into VM are failing.

Can I get the JIRA ID for this issue to track?

Thanks and Regards
-- Umesh Kute


On Fri, Jan 3, 2014 at 5:19 PM, Santhosh Edukulla <sa...@citrix.com>>>>>>> wrote:
Umesh,

This could be probably due to the bug under get_template function under marvin/integration/lib/common.py. Though, the ostype description is used and corresponding id is retrieved.

But the later part, listTemplate API call returning the list and we are picking up either the template which is ready or matching with id we retrieved. This case is what could be causing the issue you mentioned.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>]
Sent: Friday, January 03, 2014 5:04 AM
To: Santhosh Edukulla; users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks for your help Santhosh!!!

You are right...
The public IP address range was exhausted. After cleaning up the resources, I was able to run the sample script "test_deploy_vm.py" successfully.

One question - i have provided the "ostype": 'CentOS 6.4 (64-bit)'. What is the use of this parameter?

When observed in management server logs and on cloudstack UI (while running script), VM was created of type: "Windows Server 2008 R2 Enterprise with SQL 2012 Web Edition". This is the first one in the list.

Does it choose the one which we provided in script or picks it from the template list that is returned as a result of response to listTemplate API call?

Thanks and Regards
-- Umesh Kute


On Thu, Jan 2, 2014 at 7:22 PM, Santhosh Edukulla <sa...@citrix.com>>>>>>>> wrote:
Umesh,

1. It seems you have exhausted few of CloudStack Resources. These resources usage should show up on your cloudstack dashboard. Anything appears in Red are exhausted resources.

2. Few of the cases could be EX: Guest VM IPs\Management ip addresses  are exhausted,

3. Check for these resources in Red on your dashboard EX: http://localhost:8080/client/->Dashboard and clean up them or add new resources.


Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>>]
Sent: Thursday, January 02, 2014 7:06 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thank you once again Santhosh & Chandan.

I have gone through the management server logs. The deployment of VM got fired to the setup correctly and there are couple of errors in the management-server log.
I am summarizing those below:

test data in "test_deploy_vm.py"
 def __init__(self):
        self.testdata = {
            #data to create an account
            "account": {
                "email": "test@test.com<ma...@test.com>>>>>>>>",
                "firstname": "Test",
                "lastname": "User",
                "username": "test",
                "password": "password",
            },
            #data reqd for virtual machine creation
            "virtual_machine" : {
                "name" : "testvmshr",
                "displayname" : "Test VM shr",
            },
            #small service offering
            "service_offering": {
                "small": {
                    "name": "SOSmall",
                    "displaytext": "Small Instance",
                    "cpunumber": 1,
                    "cpuspeed": 2000,
                    "memory": 1024,
                },
            },
            "ostype": 'CentOS 6.4 (64-bit)',
        }


1. Account is successfully created
2. Service offering is successfully created
3. Management server logs - management-server.log has following error:


2014-01-02 01:43:40,693 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Lock is released for network Ntwk[326|Guest|15] as a part of network shutdown
2014-01-02 01:43:40,695 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Lock is released for network id 326 as a part of network implement
2014-01-02 01:43:40,695 INFO  [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Insufficient capacity
com.cloud.exception.InsufficientAddressCapacityException: Insufficient address capacityScope=interface com.cloud.dc.DataCenter; id=1
at com.cloud.network.NetworkManagerImpl.fetchNewPublicIp(NetworkManagerImpl.java:479)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.assignDedicateIpAddress(NetworkManagerImpl.java:613)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.assignSourceNatIpAddressToGuestNetwork(NetworkManagerImpl.java:582)
at com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:2013)
at com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1939)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2120)
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:887)
at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2014-01-02 01:43:40,703 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Cleaning up resources for the vm VM[User|testvmshr] in Starting state

4. When i checked the database for the network id 326 in table "networks", it has following entry:

| 326 | test-TestDeployVM-test_deploy_vm-QQ91N0-network | b7cb9e31-835f-47e3-9585-97e3b4084e4d | test-TestDeployVM-test_deploy_vm-QQ91N0-network | Guest        | Vlan                  | NULL          | 10.1.1.1       | 10.1.1.0/24<http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24>     | Dhcp   |                  15 |                 200 |              1 | ExternalGuestNetworkGuru | Destroy     |     326 |         1 |        305 | 8.8.8.8 | 8.8.4.4 | NULL      |          0 | Account  | cs131cloud.internal | ecf5b617-04da-469b-b378-f53e05d8cc53 | Isolated   |                0 | 2014-01-02 06:43:39 | 2014-01-02 06:43:46 |                 0 |   NULL | NULL        | NULL     | NULL         |               1 |           NULL |


Basically it tries to create a network offering (id=15) : "HA Isolated Network With Source Nat"


5. I think the script creates a network shown in above table: "test-TestDeployVM-test_deploy_vm-QQ91N0-network".

I am not sure why it still gives the Insufficient address capacityScope exception.

6. One more thing i observed. I have provided the "ostype": 'CentOS 6.4 (64-bit)'. But in DeployVMCmd it uses the template id: "03ffb96f-2cfa-11e3-a4f0-f245a5b3ba0f" which is for template "Windows Server 2008 R2 Enterprise with SQL 2012 Web Edition".


I am attaching the management-server logs and script logs for references.

If somebody can help me what's wrong here, would really be helpful.


Thanks and Regards
-- Umesh Kute


On Thu, Jan 2, 2014 at 2:59 PM, Santhosh Edukulla <sa...@citrix.com>>>>>>>>> wrote:
1. Is it still failing post this registration?

2. If yes, may be you can verify\provide the management server logs.
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>]
Sent: Thursday, January 02, 2014 4:16 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks Santhosh.
Yes, I have registered the following template which i am using.

"ostype": 'CentOS 6.4 (64-bit)',

Thanks and Regards
-- Umesh Kute


On Mon, Dec 30, 2013 at 5:50 PM, Santhosh Edukulla <
santhosh.edukulla@citrix.com<ma...@citrix.com>>>>>>>>> wrote:

> Umesh,
>
> One question : Did you registered the template for ostype:     "ostype":
> 'CentOS 5.3 (64-bit)'?
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>]
> Sent: Monday, December 30, 2013 6:32 AM
> To: Chandan Purushothama
> Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi Chandan,
> Thanks for your response.
> I have the latest Marvin repository (December 20th). I am able to proceed
> further. There was an issue of firewall for that machine and it got
> resolved.
>
> But now i am getting another error when i tried to run the script
> "test_deploy_vm.py"
>
> I have attached the log. Can somebody please have a look on it and help me
> in resolving the issue?
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> test_deploy_vm (integration.smoke.test_deploy_vm.TestDeployVM): CRITICAL:
> EXCEPTION: test_deploy_vm: Traceback (most recent call last):
>   File "/usr/local/lib/python2.7/unittest/case.py", line 327, in run
>     testMethod()
>   File
> "/DataDisk/temp/cloudstack/test/integration/smoke/test_deploy_vm.py", line
> 116, in test_deploy_vm
>     templateid=self.template.id<http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id>
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py",
> line 415, in create
>     virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> line 593, in deployVirtualMachine
>     response = self.connection.marvinRequest(command,
> response_type=response, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 280, in marvinRequest
>     response = self.poll(asyncJobId, response_type)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 86, in poll
>     "asyncquery", asyncResonse.jobresult)
> cloudstackAPIException: Execute cmd: asyncquery failed, due to: {errorcode
> : 533, errortext : u'Unable to create a deployment for VM[User|testvmshr]'}
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> PFA entire logs.
>
> Please let me know in case if anything is required.
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Sun, Dec 29, 2013 at 10:32 PM, Chandan Purushothama <
> Chandan.Purushothama@citrix.com<ma...@citrix.com>>>>>>>>>>
> wrote:
>
> Hello Umesh,
>
> I had a similar experience with an older Marvin build. I updated mine to
> the latest and tried again and it worked. I recommend you to kindly try
> again with the latest Marvin build and see if you are able to work with the
> automation framework,
>
> Thank you,
> Chandan
>
>
> -------- Original message --------
> From: umesh kute
> Date:12/26/2013 12:29 AM (GMT-08:00)
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>>,Sudha
> Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi All,
> I have created a Marvin setup on CentOS6.3 by following the document:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
>
> All the pre-requisites are installed successfully.
>
> I tried to run the sample script test_deploy_vm.py
> (cloudstack/test/integration/smoke/), I am getting following error:
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> [root@localhost smoke]# nosetests --with-marvin
> --marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg --load
> test_deploy_vm.py
>
>  Exception Occurred Under __deployDC :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
> Traceback (most recent call last):
>   File "/usr/local/bin/nosetests", line 9, in <module>
>     load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 118, in __init__
>     **extra_args)
>   File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
>     self.runTests()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 197, in runTests
>     result = self.testRunner.run(self.test)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 61, in run
>     test(result)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 45, in __call__
>     return self.run(*arg, **kwarg)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 138, in run
>     result.addError(self, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
> line 124, in addError
>     plugin_handled = plugins.handleError(self.test, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 99, in __call__
>     return self.call(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 167, in simple
>     result = meth(*arg, **kw)
>   File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
> line 155, in handleError
>     self.tcRunLogger.fatal("%s: %s: %s" %
> AttributeError: 'NoneType' object has no attribute 'fatal'
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> The logs are generated at /tmp and the log has following error.
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
> {'account': 'admin'}
> 2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
> http://10.88.91.100:8096/client/api :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Please note: I have opened the integration port 8096 on management server.
> Also, changed the global settings integration.api.port
> on cloudstack GUI to 8096 and restarted the management server.
>
> Still I am getting the above issue. I am not sure if i missed any
> configuration.
>
> Can somebody please help me with resolution of this issue?
> Appreciate your help here!!!
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <um...@gmail.com>>>>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>>> wrote:
>
> > Thanks a lot Sudha for your quick response.
> > I will setup the Marvin on local machine and get back in case if I face
> > any challenges in setup.
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> >
> > On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
> > sudha.ponnaganti@citrix.com<ma...@citrix.com>>>>>>>>>> wrote:
> >
> >> Hi Umesh,
> >>
> >> Looks like you have started on right track - Marvin is the framework to
> >> use for functional or integration automation.
> >> There are sizable number of test cases exist and you can review them.
> >>  There are some wiki pages already written explaining Marvin [1]. Also
> best
> >> practices are published by community as well [2]. You can contribute to
> it
> >> as much as you can.
> >>
> >> Besides this, there is Junit framework (unit Test), Selenium framework
> >> (UI automation) which are not as popular as Marvin. Marvin is perfect
> for
> >> majority of the validation. You can use simulator as well with Marvin.
> >>
> >> Please do pursue these and post questions to the community if you run in
> >> to any issues in setting up env and running tests. There are jobs setup
> by
> >> various community members to test Master or current releases in various
> >> labs and can help answer questions.
> >>
> >> [1]
> >>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> >>
> >>
> >> Thanks
> >> /Sudha
> >>
> >>
> >> -----Original Message-----
> >> From: umesh kute [mailto:umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>]
> >> Sent: Saturday, December 07, 2013 10:29 PM
> >> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>>
> >> Subject: Regarding cloudstack automation
> >>
> >> Hi All,
> >> Good morning !!!
> >> I am working as QA engineer and I am new to the cloudstack community.
> >> We have started using cloudstack and deployed it in our infrastructure.
> >>
> >> Can somebody please help me in identifying the good automation
> >> framework/tool/anything? The main intention is we want to automate the
> >> infrastructure validation related cases (for e.g. create/update/delete
> >> cases for instances, project, network, etc...)
> >>
> >> It would be good if you can help in identifying it.
> >>
> >> Please note: I have gone through cloudmonkey. But i haven't found much
> >> help on it. May be i need to search a bit more.. I am also going through
> >> the marvin and planning to setup it. If apart from these two, if anyone
> has
> >> different view please suggest.
> >>
> >> Also, if somebody has any pointers on cloudmonkey and marvin or any more
> >> info on this (like, if it would suffice the infrastructure validation
> >> related cases i mentioned above) any pros/cons would really be helpful
> for
> >> me...
> >>
> >> Appreciate any help on this and looking forward for the response on
> >> this!!!
> >>
> >> Thanks and Regards
> >> -- Umesh Kute
> >>
> >
> >
>
>

RE: Regarding cloudstack automation

[Santhosh Edukulla <sa...@citrix.com>]

Umesh,

1. Haven't had much time to look in to them in detail. 

2. Can you please create few jira tickets for failures especially for the exceptions thrown under failed_plus_exceptions file for each test module? Look only for exceptions not assertion errors. I created one as below for few exceptions
in your log file.

EX: https://issues.apache.org/jira/browse/CLOUDSTACK-5973

3. This will help to look in to issues more clearly and fix them if there are any issues.

4. Note, the errors could be specific to setup\test scripts, not related to marvin.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com]
Sent: Tuesday, January 28, 2014 1:01 PM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org; Chandan Purushothama; Sudha Ponnaganti; dev@cloudstack.apache.org
Subject: Re: Regarding cloudstack automation

Hi Santhosh,
Did you get the chance to look into the log for the issue?

Thanks and Regards
-- Umesh Kute


On Mon, Jan 27, 2014 at 6:31 PM, umesh kute <um...@gmail.com>> wrote:
Hi Santhosh,
I am attaching the failure logs in the zip file for 10 scripts executed so far. PFA (ComponetTestSuite_AllLogs.zip)

Regarding point#3, for BVT, there are 18-Pass, 17-Failed out of 35 cases.
That would be good, if you can let me know if there is any issue in marvin setup or configuration which i am using.

Please let me know if any additional information is required.

Thanks and Regards
-- Umesh Kute


On Fri, Jan 24, 2014 at 6:57 PM, Santhosh Edukulla <sa...@citrix.com>> wrote:
Umesh,

1. There should not be any issues inherent inside of it as such not to run scripts atleast existing ones altogether. Now, compared to earlier mentioned failures viz., ssh,password, template etc ,these are mainly away from framework and are setup issues.

2. Component signifies regression cases, if you already know. Now for the run and failures count, mentioned below, can you let us know what are the failures or You can attach logs to elucidate the failures? Regression do run almost every day for various releases and has many passes and failures if any for product logged as bugs. The pass % for regression is more than 90% as far iam aware. The failures below, could be mainly due to infrastructure\setup specific or the way we may perceive it to run because of it few limitations.

3. We can help you to setup and start running marvin. Are all cases for bvt running first and with no issues? Mention the host and infrastructure setup details and flow you are using.

4. Also, we have a topic branch created for marvin. If you see an issue anywhere, you can log a bug, submit a patch for review to fix the same there.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>]
Sent: Friday, January 24, 2014 8:04 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>; Chandan Purushothama; Sudha Ponnaganti; dev@cloudstack.apache.org<ma...@cloudstack.apache.org>
Subject: Re: Regarding cloudstack automation

Hi Santhosh,
To proceed further I deployed the template by disabling password and providing the default password as "password". Now its able to connect using ssh.

But when I started with the test case execution for the scripts which are there in "component folder", Out of 80 scripts, executed 11 and all 11 are failing (mentioned below).

test_affinity_groups.py
test_add_remove_network.py
test_accounts.py
test_allocation_states.py
test_baremetal.py
test_assign_vm.py
test_vm_passwdenabled.py
test_vpc_vm_life_cycle.py
test_vpc_routers.py
test_vpn_users.py
test_vpc_vms_deployment.py

Are there any issues with Marvin framework for running component script and is it executed before? I am facing many failures in a script.

If required I can share the logs.

Please note: We have a cloudstack 4.2 deployed in lab. We planned to use the Marvin to validate the cloudstack infrastructure. I have installed the marvin (0.1.0) and cloudstack using (4.2).

Thanks and Regards
-- Umesh Kute


On Sat, Jan 18, 2014 at 2:31 AM, Santhosh Edukulla <sa...@citrix.com>>> wrote:
Umesh,

1. Its good that the template issue is resolved.

2. Regarding point 4 mentioned below, your understanding is right. The idea is during automation run for various test suites,  we use a template seeded into CS which has the password set with the one used in Services Class. So, in a way for all test suites having this password mentioned is assumed to be having an instance deployed with template matching our condition and so ssh works.

3. There are test cases pertaining explicitly to verify reset cases under CS, that covers scenarios to test, but for every ssh we dont use the password given by the API output.

4. So, for creating instances you can use a template with password as "password" for your testing, thats the easy solution i believe and all test suits has this password inside them, it will work. In a way, this not so a good design, but
We are planning to remove Services class test data from tests and separate it out as a test data, So for user running tests can alter the config to suit the template he has and all test suites using ssh works and will be configurable, compared to now we have to modify all test suites to get it working with custom password for user.

Thanks!
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>]
Sent: Friday, January 17, 2014 7:32 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Hi Santhosh,
Thanks again...
I tried the steps that you mentioned below. Fortunately i could able to proceed a bit further on this issue.

Now, instance got created successfully of type CentOS 6.4 (64-bit).

It is stuck in the ssh step.
Here is what happens...

1. All the steps/APIs till instance creation works fine (including listDomains, listZones, listOsTypes, listTemplates, createAccount, createServiceOffering, deployVirtualMachine, queryAsyncJobResult, associateIPAddress, createFirewallRules, createPortForwardingRule, createEgressFirewallRule)

2. When it tries to SSH to virtual machine it fails after timeout of 600s (20-retries, 30-intervals). Script is terminated.

3. I put some debug statements in function get_ssh_client() under: "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py"

The credentials i think it tries is :
self.ssh_ip: 207.x.x.x
self.ssh_port: 22
self.username: root
self.password: password
keyPairFileLocation: None

It means, it tries to connect to instance using password as password (it is provided in dictionary in test_vm_passwdenabled.py. Note: Earlier i gave references for test_loadbalance.py and its the same case).

4. In log, i found that the password that is returned in response to deployVirtualMachine API call is: xA2yeaxvb. (PFA file runinfo). When i tried to do ssh to the instance with same password it works and with dictionary "password" it doesn't. I think so.. please confirm...

Either, for ssh connection it should use the returned password or reset password before connection.

PFA all the logs.
Please correct if my understanding is correct or I am missing something here....

Please let me know if there is any resolution of this issue or if somebody encounters it before.

Thanks and Regards
-- Umesh Kute

On Tue, Jan 14, 2014 at 6:48 PM, Santhosh Edukulla <sa...@citrix.com>>>> wrote:
Umesh,

Lets put steps so that we are in same page:

1. When we deploy  a VM, we use get_template function which basically retrieves the template information matching the description you provided under services class for ostype under test module EX: test_loadbalance.py.  I am surprised that you are receiving a "featured" and "builtin" template as windows template as output for this function. We are explicitly verifiying the template type as "BUILTIN" to retrieve the template information. So, a windows template cannot be a BUILTIN Template. Either it could be a bug in this function, or something with API. But, to double confirm, Can you please check whats the template information you are retrieving from this function matching with listTemplates API output( run either from your browser or script )  passing the same arguments as passed inside get_template?

Inside if we see, basically it gets the id matching with that ostype description using "listOsTypes"  and then use "listTemplates" command. So, this template is used to deploy the vm.  As far as i know, a builtin template cannot be a windows template?  Here, we use a featured and builtin template along with description filter passed. So, please check whether the template you are retrieving is windows or otherwise. Check for the field ostypename for the output you receive? Provide the output here for get_template copy pasted with dir(template) for return value?

2. To double confirm that it is template issue and not any other issue related to ssh like ( firewall\iptables\network connectivity issue) for ssh, please manually check for that particular ip in the test case whether ssh works or not and is not a windows machine?

3. Run one test case, first by adding a tag EX: "umesh" to the tags list as mentioned below for a particular test case under test module EX: test_loadbalance.py, then  run with nose command passing in tags argument mentioned below.

 @attr(tags = ["advanced", "advancedns", "smoke", "umesh"])
    def test_01_create_lb_rule_src_nat(self):

nosetests-2.7 -v --with-marvin --marvin-config=/root/softwares/cscode/setup/dev/advanced.cfg --load -a -w /root/softwares/cscode/test/integration/smoke/ -a tags=umesh

Let me know.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>]
Sent: Tuesday, January 14, 2014 7:02 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

I re-installed the marvin today to get the latest code.
I am again facing the same problem in get_template. It is returning the windows template and creating the windows VM. Hence when it tries to do SSH for VM, it fails.

I have also build the cloudstack to get the latest code for Marvin.

PFA the script logs and test_loadbalance script for reference.

Also, do let me know if I am missing some configuration or anything...

Just an FYI.. I have executed 35 scripts in smoke test directory. Out of 35 scripts executed, 17-PASS, 18-FAIL.
Around 50% failure are due to SSH related issue.

Thanks and Regards
-- Umesh Kute


On Fri, Jan 10, 2014 at 5:53 PM, Santhosh Edukulla <sa...@citrix.com>>>>> wrote:
1. As such because of  bug in get_template, you are getting windows machine in your setup and then ssh is tried in test module, so you are getting the error.

2. Now, to overcome, just checkout the latest marvin, it should have a fix.

Note: It still has some other issues, but you can continue with your testing further. Let us know.

Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>]
Sent: Friday, January 10, 2014 5:19 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

So far i have found the failure on following scripts:
1. test_loadbalance
2. test_network
3. test_nic

In runinfo.txt log it is stuck at the step:
SSH into VM (IPaddress: 10.1.1.55) & NAT Rule (Public IP: 207.x.x.x)

PFA the Marvin logs for the test_loadbalance.py script.

I have modified the following entry in the script i.e. provided the correct template name which is present.
"ostype": "CentOS 6.4 (64-bit)",
#"ostype": "CentOS 5.3 (64-bit)",

Please let me know for your comments.

Thanks and Regards
-- Umesh Kute



On Fri, Jan 10, 2014 at 2:57 PM, Santhosh Edukulla <sa...@citrix.com>>>>>> wrote:
You can log the bug for this. We have fixed few other issues along with this in a private branch. Will soon merge with ACS. If you need a temporary fix, let me know.

Question : Related to ssh issue, ssh to vm failing at which part? Can you add some information related to ssh failure which test module, which case etc? This may be related\unrelated to the above issue. We can check to see the issue is either same\different.

Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>]
Sent: Friday, January 10, 2014 4:21 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks a lot Santhosh For your response.

Sorry for delay.. But is there any workaround for this issue? Because as i mentioned, even if os type is provided as "ostype": 'CentOS 6.4 (64-bit)' it is picking up the first one in list i.e. Windows Server 2008 R2 Enterprise.
So some of the scripts which required to SSH into VM are failing.

Can I get the JIRA ID for this issue to track?

Thanks and Regards
-- Umesh Kute


On Fri, Jan 3, 2014 at 5:19 PM, Santhosh Edukulla <sa...@citrix.com>>>>>>> wrote:
Umesh,

This could be probably due to the bug under get_template function under marvin/integration/lib/common.py. Though, the ostype description is used and corresponding id is retrieved.

But the later part, listTemplate API call returning the list and we are picking up either the template which is ready or matching with id we retrieved. This case is what could be causing the issue you mentioned.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>]
Sent: Friday, January 03, 2014 5:04 AM
To: Santhosh Edukulla; users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks for your help Santhosh!!!

You are right...
The public IP address range was exhausted. After cleaning up the resources, I was able to run the sample script "test_deploy_vm.py" successfully.

One question - i have provided the "ostype": 'CentOS 6.4 (64-bit)'. What is the use of this parameter?

When observed in management server logs and on cloudstack UI (while running script), VM was created of type: "Windows Server 2008 R2 Enterprise with SQL 2012 Web Edition". This is the first one in the list.

Does it choose the one which we provided in script or picks it from the template list that is returned as a result of response to listTemplate API call?

Thanks and Regards
-- Umesh Kute


On Thu, Jan 2, 2014 at 7:22 PM, Santhosh Edukulla <sa...@citrix.com>>>>>>>> wrote:
Umesh,

1. It seems you have exhausted few of CloudStack Resources. These resources usage should show up on your cloudstack dashboard. Anything appears in Red are exhausted resources.

2. Few of the cases could be EX: Guest VM IPs\Management ip addresses  are exhausted,

3. Check for these resources in Red on your dashboard EX: http://localhost:8080/client/->Dashboard and clean up them or add new resources.


Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>>]
Sent: Thursday, January 02, 2014 7:06 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thank you once again Santhosh & Chandan.

I have gone through the management server logs. The deployment of VM got fired to the setup correctly and there are couple of errors in the management-server log.
I am summarizing those below:

test data in "test_deploy_vm.py"
 def __init__(self):
        self.testdata = {
            #data to create an account
            "account": {
                "email": "test@test.com<ma...@test.com>>>>>>>>",
                "firstname": "Test",
                "lastname": "User",
                "username": "test",
                "password": "password",
            },
            #data reqd for virtual machine creation
            "virtual_machine" : {
                "name" : "testvmshr",
                "displayname" : "Test VM shr",
            },
            #small service offering
            "service_offering": {
                "small": {
                    "name": "SOSmall",
                    "displaytext": "Small Instance",
                    "cpunumber": 1,
                    "cpuspeed": 2000,
                    "memory": 1024,
                },
            },
            "ostype": 'CentOS 6.4 (64-bit)',
        }


1. Account is successfully created
2. Service offering is successfully created
3. Management server logs - management-server.log has following error:


2014-01-02 01:43:40,693 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Lock is released for network Ntwk[326|Guest|15] as a part of network shutdown
2014-01-02 01:43:40,695 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Lock is released for network id 326 as a part of network implement
2014-01-02 01:43:40,695 INFO  [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Insufficient capacity
com.cloud.exception.InsufficientAddressCapacityException: Insufficient address capacityScope=interface com.cloud.dc.DataCenter; id=1
at com.cloud.network.NetworkManagerImpl.fetchNewPublicIp(NetworkManagerImpl.java:479)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.assignDedicateIpAddress(NetworkManagerImpl.java:613)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.assignSourceNatIpAddressToGuestNetwork(NetworkManagerImpl.java:582)
at com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:2013)
at com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1939)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2120)
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:887)
at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2014-01-02 01:43:40,703 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Cleaning up resources for the vm VM[User|testvmshr] in Starting state

4. When i checked the database for the network id 326 in table "networks", it has following entry:

| 326 | test-TestDeployVM-test_deploy_vm-QQ91N0-network | b7cb9e31-835f-47e3-9585-97e3b4084e4d | test-TestDeployVM-test_deploy_vm-QQ91N0-network | Guest        | Vlan                  | NULL          | 10.1.1.1       | 10.1.1.0/24<http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24>     | Dhcp   |                  15 |                 200 |              1 | ExternalGuestNetworkGuru | Destroy     |     326 |         1 |        305 | 8.8.8.8 | 8.8.4.4 | NULL      |          0 | Account  | cs131cloud.internal | ecf5b617-04da-469b-b378-f53e05d8cc53 | Isolated   |                0 | 2014-01-02 06:43:39 | 2014-01-02 06:43:46 |                 0 |   NULL | NULL        | NULL     | NULL         |               1 |           NULL |


Basically it tries to create a network offering (id=15) : "HA Isolated Network With Source Nat"


5. I think the script creates a network shown in above table: "test-TestDeployVM-test_deploy_vm-QQ91N0-network".

I am not sure why it still gives the Insufficient address capacityScope exception.

6. One more thing i observed. I have provided the "ostype": 'CentOS 6.4 (64-bit)'. But in DeployVMCmd it uses the template id: "03ffb96f-2cfa-11e3-a4f0-f245a5b3ba0f" which is for template "Windows Server 2008 R2 Enterprise with SQL 2012 Web Edition".


I am attaching the management-server logs and script logs for references.

If somebody can help me what's wrong here, would really be helpful.


Thanks and Regards
-- Umesh Kute


On Thu, Jan 2, 2014 at 2:59 PM, Santhosh Edukulla <sa...@citrix.com>>>>>>>>> wrote:
1. Is it still failing post this registration?

2. If yes, may be you can verify\provide the management server logs.
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>]
Sent: Thursday, January 02, 2014 4:16 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks Santhosh.
Yes, I have registered the following template which i am using.

"ostype": 'CentOS 6.4 (64-bit)',

Thanks and Regards
-- Umesh Kute


On Mon, Dec 30, 2013 at 5:50 PM, Santhosh Edukulla <
santhosh.edukulla@citrix.com<ma...@citrix.com>>>>>>>>> wrote:

> Umesh,
>
> One question : Did you registered the template for ostype:     "ostype":
> 'CentOS 5.3 (64-bit)'?
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>]
> Sent: Monday, December 30, 2013 6:32 AM
> To: Chandan Purushothama
> Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi Chandan,
> Thanks for your response.
> I have the latest Marvin repository (December 20th). I am able to proceed
> further. There was an issue of firewall for that machine and it got
> resolved.
>
> But now i am getting another error when i tried to run the script
> "test_deploy_vm.py"
>
> I have attached the log. Can somebody please have a look on it and help me
> in resolving the issue?
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> test_deploy_vm (integration.smoke.test_deploy_vm.TestDeployVM): CRITICAL:
> EXCEPTION: test_deploy_vm: Traceback (most recent call last):
>   File "/usr/local/lib/python2.7/unittest/case.py", line 327, in run
>     testMethod()
>   File
> "/DataDisk/temp/cloudstack/test/integration/smoke/test_deploy_vm.py", line
> 116, in test_deploy_vm
>     templateid=self.template.id<http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id>
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py",
> line 415, in create
>     virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> line 593, in deployVirtualMachine
>     response = self.connection.marvinRequest(command,
> response_type=response, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 280, in marvinRequest
>     response = self.poll(asyncJobId, response_type)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 86, in poll
>     "asyncquery", asyncResonse.jobresult)
> cloudstackAPIException: Execute cmd: asyncquery failed, due to: {errorcode
> : 533, errortext : u'Unable to create a deployment for VM[User|testvmshr]'}
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> PFA entire logs.
>
> Please let me know in case if anything is required.
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Sun, Dec 29, 2013 at 10:32 PM, Chandan Purushothama <
> Chandan.Purushothama@citrix.com<ma...@citrix.com>>>>>>>>>>
> wrote:
>
> Hello Umesh,
>
> I had a similar experience with an older Marvin build. I updated mine to
> the latest and tried again and it worked. I recommend you to kindly try
> again with the latest Marvin build and see if you are able to work with the
> automation framework,
>
> Thank you,
> Chandan
>
>
> -------- Original message --------
> From: umesh kute
> Date:12/26/2013 12:29 AM (GMT-08:00)
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>>,Sudha
> Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi All,
> I have created a Marvin setup on CentOS6.3 by following the document:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
>
> All the pre-requisites are installed successfully.
>
> I tried to run the sample script test_deploy_vm.py
> (cloudstack/test/integration/smoke/), I am getting following error:
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> [root@localhost smoke]# nosetests --with-marvin
> --marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg --load
> test_deploy_vm.py
>
>  Exception Occurred Under __deployDC :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
> Traceback (most recent call last):
>   File "/usr/local/bin/nosetests", line 9, in <module>
>     load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 118, in __init__
>     **extra_args)
>   File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
>     self.runTests()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 197, in runTests
>     result = self.testRunner.run(self.test)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 61, in run
>     test(result)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 45, in __call__
>     return self.run(*arg, **kwarg)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 138, in run
>     result.addError(self, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
> line 124, in addError
>     plugin_handled = plugins.handleError(self.test, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 99, in __call__
>     return self.call(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 167, in simple
>     result = meth(*arg, **kw)
>   File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
> line 155, in handleError
>     self.tcRunLogger.fatal("%s: %s: %s" %
> AttributeError: 'NoneType' object has no attribute 'fatal'
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> The logs are generated at /tmp and the log has following error.
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
> {'account': 'admin'}
> 2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
> http://10.88.91.100:8096/client/api :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Please note: I have opened the integration port 8096 on management server.
> Also, changed the global settings integration.api.port
> on cloudstack GUI to 8096 and restarted the management server.
>
> Still I am getting the above issue. I am not sure if i missed any
> configuration.
>
> Can somebody please help me with resolution of this issue?
> Appreciate your help here!!!
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <um...@gmail.com>>>>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>>> wrote:
>
> > Thanks a lot Sudha for your quick response.
> > I will setup the Marvin on local machine and get back in case if I face
> > any challenges in setup.
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> >
> > On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
> > sudha.ponnaganti@citrix.com<ma...@citrix.com>>>>>>>>>> wrote:
> >
> >> Hi Umesh,
> >>
> >> Looks like you have started on right track - Marvin is the framework to
> >> use for functional or integration automation.
> >> There are sizable number of test cases exist and you can review them.
> >>  There are some wiki pages already written explaining Marvin [1]. Also
> best
> >> practices are published by community as well [2]. You can contribute to
> it
> >> as much as you can.
> >>
> >> Besides this, there is Junit framework (unit Test), Selenium framework
> >> (UI automation) which are not as popular as Marvin. Marvin is perfect
> for
> >> majority of the validation. You can use simulator as well with Marvin.
> >>
> >> Please do pursue these and post questions to the community if you run in
> >> to any issues in setting up env and running tests. There are jobs setup
> by
> >> various community members to test Master or current releases in various
> >> labs and can help answer questions.
> >>
> >> [1]
> >>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> >>
> >>
> >> Thanks
> >> /Sudha
> >>
> >>
> >> -----Original Message-----
> >> From: umesh kute [mailto:umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>]
> >> Sent: Saturday, December 07, 2013 10:29 PM
> >> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>>
> >> Subject: Regarding cloudstack automation
> >>
> >> Hi All,
> >> Good morning !!!
> >> I am working as QA engineer and I am new to the cloudstack community.
> >> We have started using cloudstack and deployed it in our infrastructure.
> >>
> >> Can somebody please help me in identifying the good automation
> >> framework/tool/anything? The main intention is we want to automate the
> >> infrastructure validation related cases (for e.g. create/update/delete
> >> cases for instances, project, network, etc...)
> >>
> >> It would be good if you can help in identifying it.
> >>
> >> Please note: I have gone through cloudmonkey. But i haven't found much
> >> help on it. May be i need to search a bit more.. I am also going through
> >> the marvin and planning to setup it. If apart from these two, if anyone
> has
> >> different view please suggest.
> >>
> >> Also, if somebody has any pointers on cloudmonkey and marvin or any more
> >> info on this (like, if it would suffice the infrastructure validation
> >> related cases i mentioned above) any pros/cons would really be helpful
> for
> >> me...
> >>
> >> Appreciate any help on this and looking forward for the response on
> >> this!!!
> >>
> >> Thanks and Regards
> >> -- Umesh Kute
> >>
> >
> >
>
>

RE: Regarding cloudstack automation

[Santhosh Edukulla <sa...@citrix.com>]

Umesh,

1. Haven't had much time to look in to them in detail. 

2. Can you please create few jira tickets for failures especially for the exceptions thrown under failed_plus_exceptions file for each test module? Look only for exceptions not assertion errors. I created one as below for few exceptions
in your log file.

EX: https://issues.apache.org/jira/browse/CLOUDSTACK-5973

3. This will help to look in to issues more clearly and fix them if there are any issues.

4. Note, the errors could be specific to setup\test scripts, not related to marvin.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com]
Sent: Tuesday, January 28, 2014 1:01 PM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org; Chandan Purushothama; Sudha Ponnaganti; dev@cloudstack.apache.org
Subject: Re: Regarding cloudstack automation

Hi Santhosh,
Did you get the chance to look into the log for the issue?

Thanks and Regards
-- Umesh Kute


On Mon, Jan 27, 2014 at 6:31 PM, umesh kute <um...@gmail.com>> wrote:
Hi Santhosh,
I am attaching the failure logs in the zip file for 10 scripts executed so far. PFA (ComponetTestSuite_AllLogs.zip)

Regarding point#3, for BVT, there are 18-Pass, 17-Failed out of 35 cases.
That would be good, if you can let me know if there is any issue in marvin setup or configuration which i am using.

Please let me know if any additional information is required.

Thanks and Regards
-- Umesh Kute


On Fri, Jan 24, 2014 at 6:57 PM, Santhosh Edukulla <sa...@citrix.com>> wrote:
Umesh,

1. There should not be any issues inherent inside of it as such not to run scripts atleast existing ones altogether. Now, compared to earlier mentioned failures viz., ssh,password, template etc ,these are mainly away from framework and are setup issues.

2. Component signifies regression cases, if you already know. Now for the run and failures count, mentioned below, can you let us know what are the failures or You can attach logs to elucidate the failures? Regression do run almost every day for various releases and has many passes and failures if any for product logged as bugs. The pass % for regression is more than 90% as far iam aware. The failures below, could be mainly due to infrastructure\setup specific or the way we may perceive it to run because of it few limitations.

3. We can help you to setup and start running marvin. Are all cases for bvt running first and with no issues? Mention the host and infrastructure setup details and flow you are using.

4. Also, we have a topic branch created for marvin. If you see an issue anywhere, you can log a bug, submit a patch for review to fix the same there.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>]
Sent: Friday, January 24, 2014 8:04 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>; Chandan Purushothama; Sudha Ponnaganti; dev@cloudstack.apache.org<ma...@cloudstack.apache.org>
Subject: Re: Regarding cloudstack automation

Hi Santhosh,
To proceed further I deployed the template by disabling password and providing the default password as "password". Now its able to connect using ssh.

But when I started with the test case execution for the scripts which are there in "component folder", Out of 80 scripts, executed 11 and all 11 are failing (mentioned below).

test_affinity_groups.py
test_add_remove_network.py
test_accounts.py
test_allocation_states.py
test_baremetal.py
test_assign_vm.py
test_vm_passwdenabled.py
test_vpc_vm_life_cycle.py
test_vpc_routers.py
test_vpn_users.py
test_vpc_vms_deployment.py

Are there any issues with Marvin framework for running component script and is it executed before? I am facing many failures in a script.

If required I can share the logs.

Please note: We have a cloudstack 4.2 deployed in lab. We planned to use the Marvin to validate the cloudstack infrastructure. I have installed the marvin (0.1.0) and cloudstack using (4.2).

Thanks and Regards
-- Umesh Kute


On Sat, Jan 18, 2014 at 2:31 AM, Santhosh Edukulla <sa...@citrix.com>>> wrote:
Umesh,

1. Its good that the template issue is resolved.

2. Regarding point 4 mentioned below, your understanding is right. The idea is during automation run for various test suites,  we use a template seeded into CS which has the password set with the one used in Services Class. So, in a way for all test suites having this password mentioned is assumed to be having an instance deployed with template matching our condition and so ssh works.

3. There are test cases pertaining explicitly to verify reset cases under CS, that covers scenarios to test, but for every ssh we dont use the password given by the API output.

4. So, for creating instances you can use a template with password as "password" for your testing, thats the easy solution i believe and all test suits has this password inside them, it will work. In a way, this not so a good design, but
We are planning to remove Services class test data from tests and separate it out as a test data, So for user running tests can alter the config to suit the template he has and all test suites using ssh works and will be configurable, compared to now we have to modify all test suites to get it working with custom password for user.

Thanks!
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>]
Sent: Friday, January 17, 2014 7:32 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Hi Santhosh,
Thanks again...
I tried the steps that you mentioned below. Fortunately i could able to proceed a bit further on this issue.

Now, instance got created successfully of type CentOS 6.4 (64-bit).

It is stuck in the ssh step.
Here is what happens...

1. All the steps/APIs till instance creation works fine (including listDomains, listZones, listOsTypes, listTemplates, createAccount, createServiceOffering, deployVirtualMachine, queryAsyncJobResult, associateIPAddress, createFirewallRules, createPortForwardingRule, createEgressFirewallRule)

2. When it tries to SSH to virtual machine it fails after timeout of 600s (20-retries, 30-intervals). Script is terminated.

3. I put some debug statements in function get_ssh_client() under: "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py"

The credentials i think it tries is :
self.ssh_ip: 207.x.x.x
self.ssh_port: 22
self.username: root
self.password: password
keyPairFileLocation: None

It means, it tries to connect to instance using password as password (it is provided in dictionary in test_vm_passwdenabled.py. Note: Earlier i gave references for test_loadbalance.py and its the same case).

4. In log, i found that the password that is returned in response to deployVirtualMachine API call is: xA2yeaxvb. (PFA file runinfo). When i tried to do ssh to the instance with same password it works and with dictionary "password" it doesn't. I think so.. please confirm...

Either, for ssh connection it should use the returned password or reset password before connection.

PFA all the logs.
Please correct if my understanding is correct or I am missing something here....

Please let me know if there is any resolution of this issue or if somebody encounters it before.

Thanks and Regards
-- Umesh Kute

On Tue, Jan 14, 2014 at 6:48 PM, Santhosh Edukulla <sa...@citrix.com>>>> wrote:
Umesh,

Lets put steps so that we are in same page:

1. When we deploy  a VM, we use get_template function which basically retrieves the template information matching the description you provided under services class for ostype under test module EX: test_loadbalance.py.  I am surprised that you are receiving a "featured" and "builtin" template as windows template as output for this function. We are explicitly verifiying the template type as "BUILTIN" to retrieve the template information. So, a windows template cannot be a BUILTIN Template. Either it could be a bug in this function, or something with API. But, to double confirm, Can you please check whats the template information you are retrieving from this function matching with listTemplates API output( run either from your browser or script )  passing the same arguments as passed inside get_template?

Inside if we see, basically it gets the id matching with that ostype description using "listOsTypes"  and then use "listTemplates" command. So, this template is used to deploy the vm.  As far as i know, a builtin template cannot be a windows template?  Here, we use a featured and builtin template along with description filter passed. So, please check whether the template you are retrieving is windows or otherwise. Check for the field ostypename for the output you receive? Provide the output here for get_template copy pasted with dir(template) for return value?

2. To double confirm that it is template issue and not any other issue related to ssh like ( firewall\iptables\network connectivity issue) for ssh, please manually check for that particular ip in the test case whether ssh works or not and is not a windows machine?

3. Run one test case, first by adding a tag EX: "umesh" to the tags list as mentioned below for a particular test case under test module EX: test_loadbalance.py, then  run with nose command passing in tags argument mentioned below.

 @attr(tags = ["advanced", "advancedns", "smoke", "umesh"])
    def test_01_create_lb_rule_src_nat(self):

nosetests-2.7 -v --with-marvin --marvin-config=/root/softwares/cscode/setup/dev/advanced.cfg --load -a -w /root/softwares/cscode/test/integration/smoke/ -a tags=umesh

Let me know.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>]
Sent: Tuesday, January 14, 2014 7:02 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

I re-installed the marvin today to get the latest code.
I am again facing the same problem in get_template. It is returning the windows template and creating the windows VM. Hence when it tries to do SSH for VM, it fails.

I have also build the cloudstack to get the latest code for Marvin.

PFA the script logs and test_loadbalance script for reference.

Also, do let me know if I am missing some configuration or anything...

Just an FYI.. I have executed 35 scripts in smoke test directory. Out of 35 scripts executed, 17-PASS, 18-FAIL.
Around 50% failure are due to SSH related issue.

Thanks and Regards
-- Umesh Kute


On Fri, Jan 10, 2014 at 5:53 PM, Santhosh Edukulla <sa...@citrix.com>>>>> wrote:
1. As such because of  bug in get_template, you are getting windows machine in your setup and then ssh is tried in test module, so you are getting the error.

2. Now, to overcome, just checkout the latest marvin, it should have a fix.

Note: It still has some other issues, but you can continue with your testing further. Let us know.

Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>]
Sent: Friday, January 10, 2014 5:19 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

So far i have found the failure on following scripts:
1. test_loadbalance
2. test_network
3. test_nic

In runinfo.txt log it is stuck at the step:
SSH into VM (IPaddress: 10.1.1.55) & NAT Rule (Public IP: 207.x.x.x)

PFA the Marvin logs for the test_loadbalance.py script.

I have modified the following entry in the script i.e. provided the correct template name which is present.
"ostype": "CentOS 6.4 (64-bit)",
#"ostype": "CentOS 5.3 (64-bit)",

Please let me know for your comments.

Thanks and Regards
-- Umesh Kute



On Fri, Jan 10, 2014 at 2:57 PM, Santhosh Edukulla <sa...@citrix.com>>>>>> wrote:
You can log the bug for this. We have fixed few other issues along with this in a private branch. Will soon merge with ACS. If you need a temporary fix, let me know.

Question : Related to ssh issue, ssh to vm failing at which part? Can you add some information related to ssh failure which test module, which case etc? This may be related\unrelated to the above issue. We can check to see the issue is either same\different.

Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>]
Sent: Friday, January 10, 2014 4:21 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks a lot Santhosh For your response.

Sorry for delay.. But is there any workaround for this issue? Because as i mentioned, even if os type is provided as "ostype": 'CentOS 6.4 (64-bit)' it is picking up the first one in list i.e. Windows Server 2008 R2 Enterprise.
So some of the scripts which required to SSH into VM are failing.

Can I get the JIRA ID for this issue to track?

Thanks and Regards
-- Umesh Kute


On Fri, Jan 3, 2014 at 5:19 PM, Santhosh Edukulla <sa...@citrix.com>>>>>>> wrote:
Umesh,

This could be probably due to the bug under get_template function under marvin/integration/lib/common.py. Though, the ostype description is used and corresponding id is retrieved.

But the later part, listTemplate API call returning the list and we are picking up either the template which is ready or matching with id we retrieved. This case is what could be causing the issue you mentioned.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>]
Sent: Friday, January 03, 2014 5:04 AM
To: Santhosh Edukulla; users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks for your help Santhosh!!!

You are right...
The public IP address range was exhausted. After cleaning up the resources, I was able to run the sample script "test_deploy_vm.py" successfully.

One question - i have provided the "ostype": 'CentOS 6.4 (64-bit)'. What is the use of this parameter?

When observed in management server logs and on cloudstack UI (while running script), VM was created of type: "Windows Server 2008 R2 Enterprise with SQL 2012 Web Edition". This is the first one in the list.

Does it choose the one which we provided in script or picks it from the template list that is returned as a result of response to listTemplate API call?

Thanks and Regards
-- Umesh Kute


On Thu, Jan 2, 2014 at 7:22 PM, Santhosh Edukulla <sa...@citrix.com>>>>>>>> wrote:
Umesh,

1. It seems you have exhausted few of CloudStack Resources. These resources usage should show up on your cloudstack dashboard. Anything appears in Red are exhausted resources.

2. Few of the cases could be EX: Guest VM IPs\Management ip addresses  are exhausted,

3. Check for these resources in Red on your dashboard EX: http://localhost:8080/client/->Dashboard and clean up them or add new resources.


Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>>]
Sent: Thursday, January 02, 2014 7:06 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thank you once again Santhosh & Chandan.

I have gone through the management server logs. The deployment of VM got fired to the setup correctly and there are couple of errors in the management-server log.
I am summarizing those below:

test data in "test_deploy_vm.py"
 def __init__(self):
        self.testdata = {
            #data to create an account
            "account": {
                "email": "test@test.com<ma...@test.com>>>>>>>>",
                "firstname": "Test",
                "lastname": "User",
                "username": "test",
                "password": "password",
            },
            #data reqd for virtual machine creation
            "virtual_machine" : {
                "name" : "testvmshr",
                "displayname" : "Test VM shr",
            },
            #small service offering
            "service_offering": {
                "small": {
                    "name": "SOSmall",
                    "displaytext": "Small Instance",
                    "cpunumber": 1,
                    "cpuspeed": 2000,
                    "memory": 1024,
                },
            },
            "ostype": 'CentOS 6.4 (64-bit)',
        }


1. Account is successfully created
2. Service offering is successfully created
3. Management server logs - management-server.log has following error:


2014-01-02 01:43:40,693 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Lock is released for network Ntwk[326|Guest|15] as a part of network shutdown
2014-01-02 01:43:40,695 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Lock is released for network id 326 as a part of network implement
2014-01-02 01:43:40,695 INFO  [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Insufficient capacity
com.cloud.exception.InsufficientAddressCapacityException: Insufficient address capacityScope=interface com.cloud.dc.DataCenter; id=1
at com.cloud.network.NetworkManagerImpl.fetchNewPublicIp(NetworkManagerImpl.java:479)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.assignDedicateIpAddress(NetworkManagerImpl.java:613)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.assignSourceNatIpAddressToGuestNetwork(NetworkManagerImpl.java:582)
at com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:2013)
at com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1939)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2120)
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:887)
at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2014-01-02 01:43:40,703 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Cleaning up resources for the vm VM[User|testvmshr] in Starting state

4. When i checked the database for the network id 326 in table "networks", it has following entry:

| 326 | test-TestDeployVM-test_deploy_vm-QQ91N0-network | b7cb9e31-835f-47e3-9585-97e3b4084e4d | test-TestDeployVM-test_deploy_vm-QQ91N0-network | Guest        | Vlan                  | NULL          | 10.1.1.1       | 10.1.1.0/24<http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24>     | Dhcp   |                  15 |                 200 |              1 | ExternalGuestNetworkGuru | Destroy     |     326 |         1 |        305 | 8.8.8.8 | 8.8.4.4 | NULL      |          0 | Account  | cs131cloud.internal | ecf5b617-04da-469b-b378-f53e05d8cc53 | Isolated   |                0 | 2014-01-02 06:43:39 | 2014-01-02 06:43:46 |                 0 |   NULL | NULL        | NULL     | NULL         |               1 |           NULL |


Basically it tries to create a network offering (id=15) : "HA Isolated Network With Source Nat"


5. I think the script creates a network shown in above table: "test-TestDeployVM-test_deploy_vm-QQ91N0-network".

I am not sure why it still gives the Insufficient address capacityScope exception.

6. One more thing i observed. I have provided the "ostype": 'CentOS 6.4 (64-bit)'. But in DeployVMCmd it uses the template id: "03ffb96f-2cfa-11e3-a4f0-f245a5b3ba0f" which is for template "Windows Server 2008 R2 Enterprise with SQL 2012 Web Edition".


I am attaching the management-server logs and script logs for references.

If somebody can help me what's wrong here, would really be helpful.


Thanks and Regards
-- Umesh Kute


On Thu, Jan 2, 2014 at 2:59 PM, Santhosh Edukulla <sa...@citrix.com>>>>>>>>> wrote:
1. Is it still failing post this registration?

2. If yes, may be you can verify\provide the management server logs.
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>]
Sent: Thursday, January 02, 2014 4:16 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks Santhosh.
Yes, I have registered the following template which i am using.

"ostype": 'CentOS 6.4 (64-bit)',

Thanks and Regards
-- Umesh Kute


On Mon, Dec 30, 2013 at 5:50 PM, Santhosh Edukulla <
santhosh.edukulla@citrix.com<ma...@citrix.com>>>>>>>>> wrote:

> Umesh,
>
> One question : Did you registered the template for ostype:     "ostype":
> 'CentOS 5.3 (64-bit)'?
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>]
> Sent: Monday, December 30, 2013 6:32 AM
> To: Chandan Purushothama
> Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi Chandan,
> Thanks for your response.
> I have the latest Marvin repository (December 20th). I am able to proceed
> further. There was an issue of firewall for that machine and it got
> resolved.
>
> But now i am getting another error when i tried to run the script
> "test_deploy_vm.py"
>
> I have attached the log. Can somebody please have a look on it and help me
> in resolving the issue?
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> test_deploy_vm (integration.smoke.test_deploy_vm.TestDeployVM): CRITICAL:
> EXCEPTION: test_deploy_vm: Traceback (most recent call last):
>   File "/usr/local/lib/python2.7/unittest/case.py", line 327, in run
>     testMethod()
>   File
> "/DataDisk/temp/cloudstack/test/integration/smoke/test_deploy_vm.py", line
> 116, in test_deploy_vm
>     templateid=self.template.id<http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id>
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py",
> line 415, in create
>     virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> line 593, in deployVirtualMachine
>     response = self.connection.marvinRequest(command,
> response_type=response, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 280, in marvinRequest
>     response = self.poll(asyncJobId, response_type)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 86, in poll
>     "asyncquery", asyncResonse.jobresult)
> cloudstackAPIException: Execute cmd: asyncquery failed, due to: {errorcode
> : 533, errortext : u'Unable to create a deployment for VM[User|testvmshr]'}
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> PFA entire logs.
>
> Please let me know in case if anything is required.
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Sun, Dec 29, 2013 at 10:32 PM, Chandan Purushothama <
> Chandan.Purushothama@citrix.com<ma...@citrix.com>>>>>>>>>>
> wrote:
>
> Hello Umesh,
>
> I had a similar experience with an older Marvin build. I updated mine to
> the latest and tried again and it worked. I recommend you to kindly try
> again with the latest Marvin build and see if you are able to work with the
> automation framework,
>
> Thank you,
> Chandan
>
>
> -------- Original message --------
> From: umesh kute
> Date:12/26/2013 12:29 AM (GMT-08:00)
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>>,Sudha
> Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi All,
> I have created a Marvin setup on CentOS6.3 by following the document:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
>
> All the pre-requisites are installed successfully.
>
> I tried to run the sample script test_deploy_vm.py
> (cloudstack/test/integration/smoke/), I am getting following error:
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> [root@localhost smoke]# nosetests --with-marvin
> --marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg --load
> test_deploy_vm.py
>
>  Exception Occurred Under __deployDC :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
> Traceback (most recent call last):
>   File "/usr/local/bin/nosetests", line 9, in <module>
>     load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 118, in __init__
>     **extra_args)
>   File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
>     self.runTests()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 197, in runTests
>     result = self.testRunner.run(self.test)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 61, in run
>     test(result)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 45, in __call__
>     return self.run(*arg, **kwarg)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 138, in run
>     result.addError(self, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
> line 124, in addError
>     plugin_handled = plugins.handleError(self.test, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 99, in __call__
>     return self.call(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 167, in simple
>     result = meth(*arg, **kw)
>   File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
> line 155, in handleError
>     self.tcRunLogger.fatal("%s: %s: %s" %
> AttributeError: 'NoneType' object has no attribute 'fatal'
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> The logs are generated at /tmp and the log has following error.
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
> {'account': 'admin'}
> 2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
> http://10.88.91.100:8096/client/api :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Please note: I have opened the integration port 8096 on management server.
> Also, changed the global settings integration.api.port
> on cloudstack GUI to 8096 and restarted the management server.
>
> Still I am getting the above issue. I am not sure if i missed any
> configuration.
>
> Can somebody please help me with resolution of this issue?
> Appreciate your help here!!!
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <um...@gmail.com>>>>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>>> wrote:
>
> > Thanks a lot Sudha for your quick response.
> > I will setup the Marvin on local machine and get back in case if I face
> > any challenges in setup.
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> >
> > On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
> > sudha.ponnaganti@citrix.com<ma...@citrix.com>>>>>>>>>> wrote:
> >
> >> Hi Umesh,
> >>
> >> Looks like you have started on right track - Marvin is the framework to
> >> use for functional or integration automation.
> >> There are sizable number of test cases exist and you can review them.
> >>  There are some wiki pages already written explaining Marvin [1]. Also
> best
> >> practices are published by community as well [2]. You can contribute to
> it
> >> as much as you can.
> >>
> >> Besides this, there is Junit framework (unit Test), Selenium framework
> >> (UI automation) which are not as popular as Marvin. Marvin is perfect
> for
> >> majority of the validation. You can use simulator as well with Marvin.
> >>
> >> Please do pursue these and post questions to the community if you run in
> >> to any issues in setting up env and running tests. There are jobs setup
> by
> >> various community members to test Master or current releases in various
> >> labs and can help answer questions.
> >>
> >> [1]
> >>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> >>
> >>
> >> Thanks
> >> /Sudha
> >>
> >>
> >> -----Original Message-----
> >> From: umesh kute [mailto:umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>]
> >> Sent: Saturday, December 07, 2013 10:29 PM
> >> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>>
> >> Subject: Regarding cloudstack automation
> >>
> >> Hi All,
> >> Good morning !!!
> >> I am working as QA engineer and I am new to the cloudstack community.
> >> We have started using cloudstack and deployed it in our infrastructure.
> >>
> >> Can somebody please help me in identifying the good automation
> >> framework/tool/anything? The main intention is we want to automate the
> >> infrastructure validation related cases (for e.g. create/update/delete
> >> cases for instances, project, network, etc...)
> >>
> >> It would be good if you can help in identifying it.
> >>
> >> Please note: I have gone through cloudmonkey. But i haven't found much
> >> help on it. May be i need to search a bit more.. I am also going through
> >> the marvin and planning to setup it. If apart from these two, if anyone
> has
> >> different view please suggest.
> >>
> >> Also, if somebody has any pointers on cloudmonkey and marvin or any more
> >> info on this (like, if it would suffice the infrastructure validation
> >> related cases i mentioned above) any pros/cons would really be helpful
> for
> >> me...
> >>
> >> Appreciate any help on this and looking forward for the response on
> >> this!!!
> >>
> >> Thanks and Regards
> >> -- Umesh Kute
> >>
> >
> >
>
>

Re: Regarding cloudstack automation

[umesh kute <um...@gmail.com>]

Hi Santhosh,
Did you get the chance to look into the log for the issue?

Thanks and Regards
-- Umesh Kute


On Mon, Jan 27, 2014 at 6:31 PM, umesh kute <um...@gmail.com> wrote:

> Hi Santhosh,
> I am attaching the failure logs in the zip file for 10 scripts executed so
> far. PFA (ComponetTestSuite_AllLogs.zip)
>
> Regarding point#3, for BVT, there are 18-Pass, 17-Failed out of 35 cases.
> That would be good, if you can let me know if there is any issue in marvin
> setup or configuration which i am using.
>
> Please let me know if any additional information is required.
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Fri, Jan 24, 2014 at 6:57 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com> wrote:
>
>> Umesh,
>>
>> 1. There should not be any issues inherent inside of it as such not to
>> run scripts atleast existing ones altogether. Now, compared to earlier
>> mentioned failures viz., ssh,password, template etc ,these are mainly away
>> from framework and are setup issues.
>>
>> 2. Component signifies regression cases, if you already know. Now for the
>> run and failures count, mentioned below, can you let us know what are the
>> failures or You can attach logs to elucidate the failures? Regression do
>> run almost every day for various releases and has many passes and failures
>> if any for product logged as bugs. The pass % for regression is more than
>> 90% as far iam aware. The failures below, could be mainly due to
>> infrastructure\setup specific or the way we may perceive it to run because
>> of it few limitations.
>>
>> 3. We can help you to setup and start running marvin. Are all cases for
>> bvt running first and with no issues? Mention the host and infrastructure
>> setup details and flow you are using.
>>
>> 4. Also, we have a topic branch created for marvin. If you see an issue
>> anywhere, you can log a bug, submit a patch for review to fix the same
>> there.
>>
>> Regards,
>> Santhosh
>> ________________________________________
>> From: umesh kute [umeshvkute@gmail.com]
>> Sent: Friday, January 24, 2014 8:04 AM
>> To: Santhosh Edukulla
>> Cc: users@cloudstack.apache.org; Chandan Purushothama; Sudha Ponnaganti;
>> dev@cloudstack.apache.org
>> Subject: Re: Regarding cloudstack automation
>>
>> Hi Santhosh,
>> To proceed further I deployed the template by disabling password and
>> providing the default password as "password". Now its able to connect using
>> ssh.
>>
>> But when I started with the test case execution for the scripts which are
>> there in "component folder", Out of 80 scripts, executed 11 and all 11 are
>> failing (mentioned below).
>>
>> test_affinity_groups.py
>> test_add_remove_network.py
>> test_accounts.py
>> test_allocation_states.py
>> test_baremetal.py
>> test_assign_vm.py
>> test_vm_passwdenabled.py
>> test_vpc_vm_life_cycle.py
>> test_vpc_routers.py
>> test_vpn_users.py
>> test_vpc_vms_deployment.py
>>
>> Are there any issues with Marvin framework for running component script
>> and is it executed before? I am facing many failures in a script.
>>
>> If required I can share the logs.
>>
>> Please note: We have a cloudstack 4.2 deployed in lab. We planned to use
>> the Marvin to validate the cloudstack infrastructure. I have installed the
>> marvin (0.1.0) and cloudstack using (4.2).
>>
>> Thanks and Regards
>> -- Umesh Kute
>>
>>
>> On Sat, Jan 18, 2014 at 2:31 AM, Santhosh Edukulla <
>> santhosh.edukulla@citrix.com<ma...@citrix.com>> wrote:
>> Umesh,
>>
>> 1. Its good that the template issue is resolved.
>>
>> 2. Regarding point 4 mentioned below, your understanding is right. The
>> idea is during automation run for various test suites,  we use a template
>> seeded into CS which has the password set with the one used in Services
>> Class. So, in a way for all test suites having this password mentioned is
>> assumed to be having an instance deployed with template matching our
>> condition and so ssh works.
>>
>> 3. There are test cases pertaining explicitly to verify reset cases under
>> CS, that covers scenarios to test, but for every ssh we dont use the
>> password given by the API output.
>>
>> 4. So, for creating instances you can use a template with password as
>> "password" for your testing, thats the easy solution i believe and all test
>> suits has this password inside them, it will work. In a way, this not so a
>> good design, but
>> We are planning to remove Services class test data from tests and
>> separate it out as a test data, So for user running tests can alter the
>> config to suit the template he has and all test suites using ssh works and
>> will be configurable, compared to now we have to modify all test suites to
>> get it working with custom password for user.
>>
>> Thanks!
>> Santhosh
>> ________________________________________
>> From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>]
>> Sent: Friday, January 17, 2014 7:32 AM
>> To: Santhosh Edukulla
>> Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>;
>> Chandan Purushothama; Sudha Ponnaganti
>> Subject: Re: Regarding cloudstack automation
>>
>> Hi Santhosh,
>> Thanks again...
>> I tried the steps that you mentioned below. Fortunately i could able to
>> proceed a bit further on this issue.
>>
>> Now, instance got created successfully of type CentOS 6.4 (64-bit).
>>
>> It is stuck in the ssh step.
>> Here is what happens...
>>
>> 1. All the steps/APIs till instance creation works fine (including
>> listDomains, listZones, listOsTypes, listTemplates, createAccount,
>> createServiceOffering, deployVirtualMachine, queryAsyncJobResult,
>> associateIPAddress, createFirewallRules, createPortForwardingRule,
>> createEgressFirewallRule)
>>
>> 2. When it tries to SSH to virtual machine it fails after timeout of 600s
>> (20-retries, 30-intervals). Script is terminated.
>>
>> 3. I put some debug statements in function get_ssh_client() under:
>> "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py"
>>
>> The credentials i think it tries is :
>> self.ssh_ip: 207.x.x.x
>> self.ssh_port: 22
>> self.username: root
>> self.password: password
>> keyPairFileLocation: None
>>
>> It means, it tries to connect to instance using password as password (it
>> is provided in dictionary in test_vm_passwdenabled.py. Note: Earlier i gave
>> references for test_loadbalance.py and its the same case).
>>
>> 4. In log, i found that the password that is returned in response to
>> deployVirtualMachine API call is: xA2yeaxvb. (PFA file runinfo). When i
>> tried to do ssh to the instance with same password it works and with
>> dictionary "password" it doesn't. I think so.. please confirm...
>>
>> Either, for ssh connection it should use the returned password or reset
>> password before connection.
>>
>> PFA all the logs.
>> Please correct if my understanding is correct or I am missing something
>> here....
>>
>> Please let me know if there is any resolution of this issue or if
>> somebody encounters it before.
>>
>> Thanks and Regards
>> -- Umesh Kute
>>
>> On Tue, Jan 14, 2014 at 6:48 PM, Santhosh Edukulla <
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com>>>
>> wrote:
>> Umesh,
>>
>> Lets put steps so that we are in same page:
>>
>> 1. When we deploy  a VM, we use get_template function which basically
>> retrieves the template information matching the description you provided
>> under services class for ostype under test module EX: test_loadbalance.py.
>>  I am surprised that you are receiving a "featured" and "builtin" template
>> as windows template as output for this function. We are explicitly
>> verifiying the template type as "BUILTIN" to retrieve the template
>> information. So, a windows template cannot be a BUILTIN Template. Either it
>> could be a bug in this function, or something with API. But, to double
>> confirm, Can you please check whats the template information you are
>> retrieving from this function matching with listTemplates API output( run
>> either from your browser or script )  passing the same arguments as passed
>> inside get_template?
>>
>> Inside if we see, basically it gets the id matching with that ostype
>> description using "listOsTypes"  and then use "listTemplates" command. So,
>> this template is used to deploy the vm.  As far as i know, a builtin
>> template cannot be a windows template?  Here, we use a featured and builtin
>> template along with description filter passed. So, please check whether the
>> template you are retrieving is windows or otherwise. Check for the field
>> ostypename for the output you receive? Provide the output here for
>> get_template copy pasted with dir(template) for return value?
>>
>> 2. To double confirm that it is template issue and not any other issue
>> related to ssh like ( firewall\iptables\network connectivity issue) for
>> ssh, please manually check for that particular ip in the test case whether
>> ssh works or not and is not a windows machine?
>>
>> 3. Run one test case, first by adding a tag EX: "umesh" to the tags list
>> as mentioned below for a particular test case under test module EX:
>> test_loadbalance.py, then  run with nose command passing in tags argument
>> mentioned below.
>>
>>  @attr(tags = ["advanced", "advancedns", "smoke", "umesh"])
>>     def test_01_create_lb_rule_src_nat(self):
>>
>> nosetests-2.7 -v --with-marvin
>> --marvin-config=/root/softwares/cscode/setup/dev/advanced.cfg --load -a -w
>> /root/softwares/cscode/test/integration/smoke/ -a tags=umesh
>>
>> Let me know.
>>
>> Regards,
>> Santhosh
>> ________________________________________
>> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
>> ><ma...@gmail.com>>]
>> Sent: Tuesday, January 14, 2014 7:02 AM
>> To: Santhosh Edukulla
>> Cc: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><ma...@cloudstack.apache.org>>;
>> Chandan Purushothama; Sudha Ponnaganti
>> Subject: Re: Regarding cloudstack automation
>>
>> I re-installed the marvin today to get the latest code.
>> I am again facing the same problem in get_template. It is returning the
>> windows template and creating the windows VM. Hence when it tries to do SSH
>> for VM, it fails.
>>
>> I have also build the cloudstack to get the latest code for Marvin.
>>
>> PFA the script logs and test_loadbalance script for reference.
>>
>> Also, do let me know if I am missing some configuration or anything...
>>
>> Just an FYI.. I have executed 35 scripts in smoke test directory. Out of
>> 35 scripts executed, 17-PASS, 18-FAIL.
>> Around 50% failure are due to SSH related issue.
>>
>> Thanks and Regards
>> -- Umesh Kute
>>
>>
>> On Fri, Jan 10, 2014 at 5:53 PM, Santhosh Edukulla <
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>>> wrote:
>> 1. As such because of  bug in get_template, you are getting windows
>> machine in your setup and then ssh is tried in test module, so you are
>> getting the error.
>>
>> 2. Now, to overcome, just checkout the latest marvin, it should have a
>> fix.
>>
>> Note: It still has some other issues, but you can continue with your
>> testing further. Let us know.
>>
>> Santhosh
>> ________________________________________
>> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
>> ><ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>]
>> Sent: Friday, January 10, 2014 5:19 AM
>> To: Santhosh Edukulla
>> Cc: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><ma...@cloudstack.apache.org>>>;
>> Chandan Purushothama; Sudha Ponnaganti
>> Subject: Re: Regarding cloudstack automation
>>
>> So far i have found the failure on following scripts:
>> 1. test_loadbalance
>> 2. test_network
>> 3. test_nic
>>
>> In runinfo.txt log it is stuck at the step:
>> SSH into VM (IPaddress: 10.1.1.55) & NAT Rule (Public IP: 207.x.x.x)
>>
>> PFA the Marvin logs for the test_loadbalance.py script.
>>
>> I have modified the following entry in the script i.e. provided the
>> correct template name which is present.
>> "ostype": "CentOS 6.4 (64-bit)",
>> #"ostype": "CentOS 5.3 (64-bit)",
>>
>> Please let me know for your comments.
>>
>> Thanks and Regards
>> -- Umesh Kute
>>
>>
>>
>> On Fri, Jan 10, 2014 at 2:57 PM, Santhosh Edukulla <
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com>>>>>
>> wrote:
>> You can log the bug for this. We have fixed few other issues along with
>> this in a private branch. Will soon merge with ACS. If you need a temporary
>> fix, let me know.
>>
>> Question : Related to ssh issue, ssh to vm failing at which part? Can you
>> add some information related to ssh failure which test module, which case
>> etc? This may be related\unrelated to the above issue. We can check to see
>> the issue is either same\different.
>>
>> Santhosh
>> ________________________________________
>> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
>> ><ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>]
>> Sent: Friday, January 10, 2014 4:21 AM
>> To: Santhosh Edukulla
>> Cc: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><ma...@cloudstack.apache.org>>>>;
>> Chandan Purushothama; Sudha Ponnaganti
>> Subject: Re: Regarding cloudstack automation
>>
>> Thanks a lot Santhosh For your response.
>>
>> Sorry for delay.. But is there any workaround for this issue? Because as
>> i mentioned, even if os type is provided as "ostype": 'CentOS 6.4 (64-bit)'
>> it is picking up the first one in list i.e. Windows Server 2008 R2
>> Enterprise.
>> So some of the scripts which required to SSH into VM are failing.
>>
>> Can I get the JIRA ID for this issue to track?
>>
>> Thanks and Regards
>> -- Umesh Kute
>>
>>
>> On Fri, Jan 3, 2014 at 5:19 PM, Santhosh Edukulla <
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >>>><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>>>>> wrote:
>> Umesh,
>>
>> This could be probably due to the bug under get_template function under
>> marvin/integration/lib/common.py. Though, the ostype description is used
>> and corresponding id is retrieved.
>>
>> But the later part, listTemplate API call returning the list and we are
>> picking up either the template which is ready or matching with id we
>> retrieved. This case is what could be causing the issue you mentioned.
>>
>> Regards,
>> Santhosh
>> ________________________________________
>> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
>> ><ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>>]
>> Sent: Friday, January 03, 2014 5:04 AM
>> To: Santhosh Edukulla; users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>>>
>> Cc: Chandan Purushothama; Sudha Ponnaganti
>> Subject: Re: Regarding cloudstack automation
>>
>> Thanks for your help Santhosh!!!
>>
>> You are right...
>> The public IP address range was exhausted. After cleaning up the
>> resources, I was able to run the sample script "test_deploy_vm.py"
>> successfully.
>>
>> One question - i have provided the "ostype": 'CentOS 6.4 (64-bit)'. What
>> is the use of this parameter?
>>
>> When observed in management server logs and on cloudstack UI (while
>> running script), VM was created of type: "Windows Server 2008 R2 Enterprise
>> with SQL 2012 Web Edition". This is the first one in the list.
>>
>> Does it choose the one which we provided in script or picks it from the
>> template list that is returned as a result of response to listTemplate API
>> call?
>>
>> Thanks and Regards
>> -- Umesh Kute
>>
>>
>> On Thu, Jan 2, 2014 at 7:22 PM, Santhosh Edukulla <
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >>>><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>>>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >>><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>>>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com>>>>>>>
>> wrote:
>> Umesh,
>>
>> 1. It seems you have exhausted few of CloudStack Resources. These
>> resources usage should show up on your cloudstack dashboard. Anything
>> appears in Red are exhausted resources.
>>
>> 2. Few of the cases could be EX: Guest VM IPs\Management ip addresses
>>  are exhausted,
>>
>> 3. Check for these resources in Red on your dashboard EX:
>> http://localhost:8080/client/->Dashboard and clean up them or add new
>> resources.
>>
>>
>> Santhosh
>> ________________________________________
>> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
>> ><ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>>>]
>> Sent: Thursday, January 02, 2014 7:06 AM
>> To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>
>> Cc: Chandan Purushothama; Sudha Ponnaganti
>> Subject: Re: Regarding cloudstack automation
>>
>> Thank you once again Santhosh & Chandan.
>>
>> I have gone through the management server logs. The deployment of VM got
>> fired to the setup correctly and there are couple of errors in the
>> management-server log.
>> I am summarizing those below:
>>
>> test data in "test_deploy_vm.py"
>>  def __init__(self):
>>         self.testdata = {
>>             #data to create an account
>>             "account": {
>>                 "email": "test@test.com<ma...@test.com><mailto:
>> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
>> test@test.com><ma...@test.com>>><mailto:
>> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
>> test@test.com>><ma...@test.com><mailto:
>> test@test.com<ma...@test.com>>>><mailto:test@test.com<mailto:
>> test@test.com><ma...@test.com>><mailto:
>> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
>> test@test.com>>><ma...@test.com><mailto:
>> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
>> test@test.com><ma...@test.com>>>>><mailto:
>> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
>> test@test.com>><ma...@test.com><mailto:
>> test@test.com<ma...@test.com>>><mailto:test@test.com<mailto:
>> test@test.com><ma...@test.com>><mailto:
>> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
>> test@test.com>>>><ma...@test.com><mailto:
>> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
>> test@test.com><ma...@test.com>>><mailto:
>> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
>> test@test.com>><ma...@test.com><mailto:
>> test@test.com<ma...@test.com>>>>>><mailto:test@test.com<mailto:
>> test@test.com><ma...@test.com>><mailto:
>> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
>> test@test.com>>><ma...@test.com><mailto:
>> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
>> test@test.com><ma...@test.com>>>><mailto:
>> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
>> test@test.com>><ma...@test.com><mailto:
>> test@test.com<ma...@test.com>>><mailto:test@test.com<mailto:
>> test@test.com><ma...@test.com>><mailto:
>> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
>> test@test.com>>>>><ma...@test.com><mailto:
>> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
>> test@test.com><ma...@test.com>>><mailto:
>> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
>> test@test.com>><ma...@test.com><mailto:
>> test@test.com<ma...@test.com>>>><mailto:test@test.com<mailto:
>> test@test.com><ma...@test.com>><mailto:
>> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
>> test@test.com>>><ma...@test.com><mailto:
>> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
>> test@test.com><ma...@test.com>>>>>>>",
>>                 "firstname": "Test",
>>                 "lastname": "User",
>>                 "username": "test",
>>                 "password": "password",
>>             },
>>             #data reqd for virtual machine creation
>>             "virtual_machine" : {
>>                 "name" : "testvmshr",
>>                 "displayname" : "Test VM shr",
>>             },
>>             #small service offering
>>             "service_offering": {
>>                 "small": {
>>                     "name": "SOSmall",
>>                     "displaytext": "Small Instance",
>>                     "cpunumber": 1,
>>                     "cpuspeed": 2000,
>>                     "memory": 1024,
>>                 },
>>             },
>>             "ostype": 'CentOS 6.4 (64-bit)',
>>         }
>>
>>
>> 1. Account is successfully created
>> 2. Service offering is successfully created
>> 3. Management server logs - management-server.log has following error:
>>
>>
>> 2014-01-02 01:43:40,693 DEBUG [cloud.network.NetworkManagerImpl]
>> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
>> Lock is released for network Ntwk[326|Guest|15] as a part of network
>> shutdown
>> 2014-01-02 01:43:40,695 DEBUG [cloud.network.NetworkManagerImpl]
>> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
>> Lock is released for network id 326 as a part of network implement
>> 2014-01-02 01:43:40,695 INFO  [cloud.vm.VirtualMachineManagerImpl]
>> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
>> Insufficient capacity
>> com.cloud.exception.InsufficientAddressCapacityException: Insufficient
>> address capacityScope=interface com.cloud.dc.DataCenter; id=1
>> at
>> com.cloud.network.NetworkManagerImpl.fetchNewPublicIp(NetworkManagerImpl.java:479)
>> at
>> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
>> at
>> com.cloud.network.NetworkManagerImpl.assignDedicateIpAddress(NetworkManagerImpl.java:613)
>> at
>> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
>> at
>> com.cloud.network.NetworkManagerImpl.assignSourceNatIpAddressToGuestNetwork(NetworkManagerImpl.java:582)
>> at
>> com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:2013)
>> at
>> com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1939)
>> at
>> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
>> at
>> com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2120)
>> at
>> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:887)
>> at
>> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
>> at
>> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
>> at
>> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
>> at
>> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
>> at
>> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
>> at
>> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
>> at
>> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
>> at
>> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
>> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
>> at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
>> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
>> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> at java.lang.Thread.run(Thread.java:679)
>> 2014-01-02 01:43:40,703 DEBUG [cloud.vm.VirtualMachineManagerImpl]
>> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
>> Cleaning up resources for the vm VM[User|testvmshr] in Starting state
>>
>> 4. When i checked the database for the network id 326 in table
>> "networks", it has following entry:
>>
>> | 326 | test-TestDeployVM-test_deploy_vm-QQ91N0-network |
>> b7cb9e31-835f-47e3-9585-97e3b4084e4d |
>> test-TestDeployVM-test_deploy_vm-QQ91N0-network | Guest        | Vlan
>>            | NULL          | 10.1.1.1       | 10.1.1.0/24<
>> http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><
>> http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><
>> http://10.1.1.0/24>     | Dhcp   |                  15 |
>> 200 |              1 | ExternalGuestNetworkGuru | Destroy     |     326 |
>>       1 |        305 | 8.8.8.8 | 8.8.4.4 | NULL      |          0 | Account
>>  | cs131cloud.internal | ecf5b617-04da-469b-b378-f53e05d8cc53 | Isolated
>> |                0 | 2014-01-02 06:43:39 | 2014-01-02 06:43:46 |
>>       0 |   NULL | NULL        | NULL     | NULL         |               1
>> |           NULL |
>>
>>
>> Basically it tries to create a network offering (id=15) : "HA Isolated
>> Network With Source Nat"
>>
>>
>> 5. I think the script creates a network shown in above table:
>> "test-TestDeployVM-test_deploy_vm-QQ91N0-network".
>>
>> I am not sure why it still gives the Insufficient address capacityScope
>> exception.
>>
>> 6. One more thing i observed. I have provided the "ostype": 'CentOS 6.4
>> (64-bit)'. But in DeployVMCmd it uses the template id:
>> "03ffb96f-2cfa-11e3-a4f0-f245a5b3ba0f" which is for template "Windows
>> Server 2008 R2 Enterprise with SQL 2012 Web Edition".
>>
>>
>> I am attaching the management-server logs and script logs for references.
>>
>> If somebody can help me what's wrong here, would really be helpful.
>>
>>
>> Thanks and Regards
>> -- Umesh Kute
>>
>>
>> On Thu, Jan 2, 2014 at 2:59 PM, Santhosh Edukulla <
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >>>><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>>>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >>><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>>>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >>>>>><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >>><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>>>>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >>>><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>>>>>>> wrote:
>> 1. Is it still failing post this registration?
>>
>> 2. If yes, may be you can verify\provide the management server logs.
>> ________________________________________
>> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
>> ><ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>>>>]
>> Sent: Thursday, January 02, 2014 4:16 AM
>> To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>>>>>
>> Cc: Chandan Purushothama; Sudha Ponnaganti
>> Subject: Re: Regarding cloudstack automation
>>
>> Thanks Santhosh.
>> Yes, I have registered the following template which i am using.
>>
>> "ostype": 'CentOS 6.4 (64-bit)',
>>
>> Thanks and Regards
>> -- Umesh Kute
>>
>>
>> On Mon, Dec 30, 2013 at 5:50 PM, Santhosh Edukulla <
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >>>><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>>>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >>><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>>>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >>>>>><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >>><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>>>>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >>>><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>>>>>>> wrote:
>>
>> > Umesh,
>> >
>> > One question : Did you registered the template for ostype:     "ostype":
>> > 'CentOS 5.3 (64-bit)'?
>> >
>> > Regards,
>> > Santhosh
>> > ________________________________________
>> > From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
>> ><ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>>>>]
>> > Sent: Monday, December 30, 2013 6:32 AM
>> > To: Chandan Purushothama
>> > Cc: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>>>>>; Sudha Ponnaganti
>> > Subject: Re: Regarding cloudstack automation
>> >
>> > Hi Chandan,
>> > Thanks for your response.
>> > I have the latest Marvin repository (December 20th). I am able to
>> proceed
>> > further. There was an issue of firewall for that machine and it got
>> > resolved.
>> >
>> > But now i am getting another error when i tried to run the script
>> > "test_deploy_vm.py"
>> >
>> > I have attached the log. Can somebody please have a look on it and help
>> me
>> > in resolving the issue?
>> >
>> >
>> >
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> > test_deploy_vm (integration.smoke.test_deploy_vm.TestDeployVM):
>> CRITICAL:
>> > EXCEPTION: test_deploy_vm: Traceback (most recent call last):
>> >   File "/usr/local/lib/python2.7/unittest/case.py", line 327, in run
>> >     testMethod()
>> >   File
>> > "/DataDisk/temp/cloudstack/test/integration/smoke/test_deploy_vm.py",
>> line
>> > 116, in test_deploy_vm
>> >     templateid=self.template.id<http://self.template.id><
>> http://self.template.id><http://self.template.id><http://self.template.id
>> ><http://self.template.id><http://self.template.id><
>> http://self.template.id><http://self.template.id>
>> >   File
>> > "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py",
>> > line 415, in create
>> >     virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
>> >   File
>> >
>> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
>> > line 593, in deployVirtualMachine
>> >     response = self.connection.marvinRequest(command,
>> > response_type=response, method=method)
>> >   File
>> > "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
>> > line 280, in marvinRequest
>> >     response = self.poll(asyncJobId, response_type)
>> >   File
>> > "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
>> > line 86, in poll
>> >     "asyncquery", asyncResonse.jobresult)
>> > cloudstackAPIException: Execute cmd: asyncquery failed, due to:
>> {errorcode
>> > : 533, errortext : u'Unable to create a deployment for
>> VM[User|testvmshr]'}
>> >
>> >
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> >
>> > PFA entire logs.
>> >
>> > Please let me know in case if anything is required.
>> >
>> > Thanks and Regards
>> > -- Umesh Kute
>> >
>> >
>> > On Sun, Dec 29, 2013 at 10:32 PM, Chandan Purushothama <
>> > Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>>>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>>>>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>>>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>>>>>>>
>> > wrote:
>> >
>> > Hello Umesh,
>> >
>> > I had a similar experience with an older Marvin build. I updated mine to
>> > the latest and tried again and it worked. I recommend you to kindly try
>> > again with the latest Marvin build and see if you are able to work with
>> the
>> > automation framework,
>> >
>> > Thank you,
>> > Chandan
>> >
>> >
>> > -------- Original message --------
>> > From: umesh kute
>> > Date:12/26/2013 12:29 AM (GMT-08:00)
>> > To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>>>>>>,Sudha
>> > Ponnaganti
>> > Subject: Re: Regarding cloudstack automation
>> >
>> > Hi All,
>> > I have created a Marvin setup on CentOS6.3 by following the document:
>> >
>> >
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
>> >
>> > All the pre-requisites are installed successfully.
>> >
>> > I tried to run the sample script test_deploy_vm.py
>> > (cloudstack/test/integration/smoke/), I am getting following error:
>> >
>> >
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> > [root@localhost smoke]# nosetests --with-marvin
>> > --marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg
>> --load
>> > test_deploy_vm.py
>> >
>> >  Exception Occurred Under __deployDC :
>> > HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
>> > with url: /client/api?account=admin&command=listUsers&response=json
>> (Caused
>> > by <class 'socket.error'>: [Errno 110] Connection timed out)
>> > Traceback (most recent call last):
>> >   File "/usr/local/bin/nosetests", line 9, in <module>
>> >     load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
>> >   File
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
>> > line 118, in __init__
>> >     **extra_args)
>> >   File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
>> >     self.runTests()
>> >   File
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
>> > line 197, in runTests
>> >     result = self.testRunner.run(self.test)
>> >   File
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
>> > line 61, in run
>> >     test(result)
>> >   File
>> >
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
>> > line 176, in __call__
>> >     return self.run(*arg, **kw)
>> >   File
>> >
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
>> > line 223, in run
>> >     test(orig)
>> >   File
>> >
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
>> > line 176, in __call__
>> >     return self.run(*arg, **kw)
>> >   File
>> >
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
>> > line 223, in run
>> >     test(orig)
>> >   File
>> >
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
>> > line 176, in __call__
>> >     return self.run(*arg, **kw)
>> >   File
>> >
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
>> > line 223, in run
>> >     test(orig)
>> >   File
>> >
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
>> > line 176, in __call__
>> >     return self.run(*arg, **kw)
>> >   File
>> >
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
>> > line 223, in run
>> >     test(orig)
>> >   File
>> >
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
>> > line 176, in __call__
>> >     return self.run(*arg, **kw)
>> >   File
>> >
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
>> > line 223, in run
>> >     test(orig)
>> >   File
>> >
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
>> > line 176, in __call__
>> >     return self.run(*arg, **kw)
>> >   File
>> >
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
>> > line 223, in run
>> >     test(orig)
>> >   File
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
>> > line 45, in __call__
>> >     return self.run(*arg, **kwarg)
>> >   File
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
>> > line 138, in run
>> >     result.addError(self, err)
>> >   File
>> >
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
>> > line 124, in addError
>> >     plugin_handled = plugins.handleError(self.test, err)
>> >   File
>> >
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
>> > line 99, in __call__
>> >     return self.call(*arg, **kw)
>> >   File
>> >
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
>> > line 167, in simple
>> >     result = meth(*arg, **kw)
>> >   File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
>> > line 155, in handleError
>> >     self.tcRunLogger.fatal("%s: %s: %s" %
>> > AttributeError: 'NoneType' object has no attribute 'fatal'
>> >
>> >
>> >
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> >
>> > The logs are generated at /tmp and the log has following error.
>> >
>> >
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> > 2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
>> > {'account': 'admin'}
>> > 2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
>> > http://10.88.91.100:8096/client/api :
>> > HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
>> > with url: /client/api?account=admin&command=listUsers&response=json
>> (Caused
>> > by <class 'socket.error'>: [Errno 110] Connection timed out)
>> >
>> >
>> >
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> >
>> > Please note: I have opened the integration port 8096 on management
>> server.
>> > Also, changed the global settings integration.api.port
>> > on cloudstack GUI to 8096 and restarted the management server.
>> >
>> > Still I am getting the above issue. I am not sure if i missed any
>> > configuration.
>> >
>> > Can somebody please help me with resolution of this issue?
>> > Appreciate your help here!!!
>> >
>> > Thanks and Regards
>> > -- Umesh Kute
>> >
>> >
>> > On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <umeshvkute@gmail.com
>> <ma...@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>>>>><mailto:
>> > umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>> wrote:
>> >
>> > > Thanks a lot Sudha for your quick response.
>> > > I will setup the Marvin on local machine and get back in case if I
>> face
>> > > any challenges in setup.
>> > >
>> > > Thanks and Regards
>> > > -- Umesh Kute
>> > >
>> > >
>> > >
>> > > On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
>> > > sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
>> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
>> >><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
>> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
>> >>><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
>> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
>> >><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
>> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
>> >>>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>>>>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>>>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
>> >>>>>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>>>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>>>>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
>> >>>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>>>>>>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>>>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
>> >>>>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>>>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>>>>>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
>> >>>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>>>>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>>>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>>>>>>>>>
>> wrote:
>> > >
>> > >> Hi Umesh,
>> > >>
>> > >> Looks like you have started on right track - Marvin is the framework
>> to
>> > >> use for functional or integration automation.
>> > >> There are sizable number of test cases exist and you can review them.
>> > >>  There are some wiki pages already written explaining Marvin [1].
>> Also
>> > best
>> > >> practices are published by community as well [2]. You can contribute
>> to
>> > it
>> > >> as much as you can.
>> > >>
>> > >> Besides this, there is Junit framework (unit Test), Selenium
>> framework
>> > >> (UI automation) which are not as popular as Marvin. Marvin is perfect
>> > for
>> > >> majority of the validation. You can use simulator as well with
>> Marvin.
>> > >>
>> > >> Please do pursue these and post questions to the community if you
>> run in
>> > >> to any issues in setting up env and running tests. There are jobs
>> setup
>> > by
>> > >> various community members to test Master or current releases in
>> various
>> > >> labs and can help answer questions.
>> > >>
>> > >> [1]
>> > >>
>> >
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
>> > >>
>> > >>
>> > >> Thanks
>> > >> /Sudha
>> > >>
>> > >>
>> > >> -----Original Message-----
>> > >> From: umesh kute [mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>>>>>]
>> > >> Sent: Saturday, December 07, 2013 10:29 PM
>> > >> To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>
>> > >> Subject: Regarding cloudstack automation
>> > >>
>> > >> Hi All,
>> > >> Good morning !!!
>> > >> I am working as QA engineer and I am new to the cloudstack community.
>> > >> We have started using cloudstack and deployed it in our
>> infrastructure.
>> > >>
>> > >> Can somebody please help me in identifying the good automation
>> > >> framework/tool/anything? The main intention is we want to automate
>> the
>> > >> infrastructure validation related cases (for e.g.
>> create/update/delete
>> > >> cases for instances, project, network, etc...)
>> > >>
>> > >> It would be good if you can help in identifying it.
>> > >>
>> > >> Please note: I have gone through cloudmonkey. But i haven't found
>> much
>> > >> help on it. May be i need to search a bit more.. I am also going
>> through
>> > >> the marvin and planning to setup it. If apart from these two, if
>> anyone
>> > has
>> > >> different view please suggest.
>> > >>
>> > >> Also, if somebody has any pointers on cloudmonkey and marvin or any
>> more
>> > >> info on this (like, if it would suffice the infrastructure validation
>> > >> related cases i mentioned above) any pros/cons would really be
>> helpful
>> > for
>> > >> me...
>> > >>
>> > >> Appreciate any help on this and looking forward for the response on
>> > >> this!!!
>> > >>
>> > >> Thanks and Regards
>> > >> -- Umesh Kute
>> > >>
>> > >
>> > >
>> >
>> >
>>
>>
>>
>>
>

Re: Regarding cloudstack automation

[umesh kute <um...@gmail.com>]

Hi Santhosh,
Did you get the chance to look into the log for the issue?

Thanks and Regards
-- Umesh Kute


On Mon, Jan 27, 2014 at 6:31 PM, umesh kute <um...@gmail.com> wrote:

> Hi Santhosh,
> I am attaching the failure logs in the zip file for 10 scripts executed so
> far. PFA (ComponetTestSuite_AllLogs.zip)
>
> Regarding point#3, for BVT, there are 18-Pass, 17-Failed out of 35 cases.
> That would be good, if you can let me know if there is any issue in marvin
> setup or configuration which i am using.
>
> Please let me know if any additional information is required.
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Fri, Jan 24, 2014 at 6:57 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com> wrote:
>
>> Umesh,
>>
>> 1. There should not be any issues inherent inside of it as such not to
>> run scripts atleast existing ones altogether. Now, compared to earlier
>> mentioned failures viz., ssh,password, template etc ,these are mainly away
>> from framework and are setup issues.
>>
>> 2. Component signifies regression cases, if you already know. Now for the
>> run and failures count, mentioned below, can you let us know what are the
>> failures or You can attach logs to elucidate the failures? Regression do
>> run almost every day for various releases and has many passes and failures
>> if any for product logged as bugs. The pass % for regression is more than
>> 90% as far iam aware. The failures below, could be mainly due to
>> infrastructure\setup specific or the way we may perceive it to run because
>> of it few limitations.
>>
>> 3. We can help you to setup and start running marvin. Are all cases for
>> bvt running first and with no issues? Mention the host and infrastructure
>> setup details and flow you are using.
>>
>> 4. Also, we have a topic branch created for marvin. If you see an issue
>> anywhere, you can log a bug, submit a patch for review to fix the same
>> there.
>>
>> Regards,
>> Santhosh
>> ________________________________________
>> From: umesh kute [umeshvkute@gmail.com]
>> Sent: Friday, January 24, 2014 8:04 AM
>> To: Santhosh Edukulla
>> Cc: users@cloudstack.apache.org; Chandan Purushothama; Sudha Ponnaganti;
>> dev@cloudstack.apache.org
>> Subject: Re: Regarding cloudstack automation
>>
>> Hi Santhosh,
>> To proceed further I deployed the template by disabling password and
>> providing the default password as "password". Now its able to connect using
>> ssh.
>>
>> But when I started with the test case execution for the scripts which are
>> there in "component folder", Out of 80 scripts, executed 11 and all 11 are
>> failing (mentioned below).
>>
>> test_affinity_groups.py
>> test_add_remove_network.py
>> test_accounts.py
>> test_allocation_states.py
>> test_baremetal.py
>> test_assign_vm.py
>> test_vm_passwdenabled.py
>> test_vpc_vm_life_cycle.py
>> test_vpc_routers.py
>> test_vpn_users.py
>> test_vpc_vms_deployment.py
>>
>> Are there any issues with Marvin framework for running component script
>> and is it executed before? I am facing many failures in a script.
>>
>> If required I can share the logs.
>>
>> Please note: We have a cloudstack 4.2 deployed in lab. We planned to use
>> the Marvin to validate the cloudstack infrastructure. I have installed the
>> marvin (0.1.0) and cloudstack using (4.2).
>>
>> Thanks and Regards
>> -- Umesh Kute
>>
>>
>> On Sat, Jan 18, 2014 at 2:31 AM, Santhosh Edukulla <
>> santhosh.edukulla@citrix.com<ma...@citrix.com>> wrote:
>> Umesh,
>>
>> 1. Its good that the template issue is resolved.
>>
>> 2. Regarding point 4 mentioned below, your understanding is right. The
>> idea is during automation run for various test suites,  we use a template
>> seeded into CS which has the password set with the one used in Services
>> Class. So, in a way for all test suites having this password mentioned is
>> assumed to be having an instance deployed with template matching our
>> condition and so ssh works.
>>
>> 3. There are test cases pertaining explicitly to verify reset cases under
>> CS, that covers scenarios to test, but for every ssh we dont use the
>> password given by the API output.
>>
>> 4. So, for creating instances you can use a template with password as
>> "password" for your testing, thats the easy solution i believe and all test
>> suits has this password inside them, it will work. In a way, this not so a
>> good design, but
>> We are planning to remove Services class test data from tests and
>> separate it out as a test data, So for user running tests can alter the
>> config to suit the template he has and all test suites using ssh works and
>> will be configurable, compared to now we have to modify all test suites to
>> get it working with custom password for user.
>>
>> Thanks!
>> Santhosh
>> ________________________________________
>> From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>]
>> Sent: Friday, January 17, 2014 7:32 AM
>> To: Santhosh Edukulla
>> Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>;
>> Chandan Purushothama; Sudha Ponnaganti
>> Subject: Re: Regarding cloudstack automation
>>
>> Hi Santhosh,
>> Thanks again...
>> I tried the steps that you mentioned below. Fortunately i could able to
>> proceed a bit further on this issue.
>>
>> Now, instance got created successfully of type CentOS 6.4 (64-bit).
>>
>> It is stuck in the ssh step.
>> Here is what happens...
>>
>> 1. All the steps/APIs till instance creation works fine (including
>> listDomains, listZones, listOsTypes, listTemplates, createAccount,
>> createServiceOffering, deployVirtualMachine, queryAsyncJobResult,
>> associateIPAddress, createFirewallRules, createPortForwardingRule,
>> createEgressFirewallRule)
>>
>> 2. When it tries to SSH to virtual machine it fails after timeout of 600s
>> (20-retries, 30-intervals). Script is terminated.
>>
>> 3. I put some debug statements in function get_ssh_client() under:
>> "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py"
>>
>> The credentials i think it tries is :
>> self.ssh_ip: 207.x.x.x
>> self.ssh_port: 22
>> self.username: root
>> self.password: password
>> keyPairFileLocation: None
>>
>> It means, it tries to connect to instance using password as password (it
>> is provided in dictionary in test_vm_passwdenabled.py. Note: Earlier i gave
>> references for test_loadbalance.py and its the same case).
>>
>> 4. In log, i found that the password that is returned in response to
>> deployVirtualMachine API call is: xA2yeaxvb. (PFA file runinfo). When i
>> tried to do ssh to the instance with same password it works and with
>> dictionary "password" it doesn't. I think so.. please confirm...
>>
>> Either, for ssh connection it should use the returned password or reset
>> password before connection.
>>
>> PFA all the logs.
>> Please correct if my understanding is correct or I am missing something
>> here....
>>
>> Please let me know if there is any resolution of this issue or if
>> somebody encounters it before.
>>
>> Thanks and Regards
>> -- Umesh Kute
>>
>> On Tue, Jan 14, 2014 at 6:48 PM, Santhosh Edukulla <
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com>>>
>> wrote:
>> Umesh,
>>
>> Lets put steps so that we are in same page:
>>
>> 1. When we deploy  a VM, we use get_template function which basically
>> retrieves the template information matching the description you provided
>> under services class for ostype under test module EX: test_loadbalance.py.
>>  I am surprised that you are receiving a "featured" and "builtin" template
>> as windows template as output for this function. We are explicitly
>> verifiying the template type as "BUILTIN" to retrieve the template
>> information. So, a windows template cannot be a BUILTIN Template. Either it
>> could be a bug in this function, or something with API. But, to double
>> confirm, Can you please check whats the template information you are
>> retrieving from this function matching with listTemplates API output( run
>> either from your browser or script )  passing the same arguments as passed
>> inside get_template?
>>
>> Inside if we see, basically it gets the id matching with that ostype
>> description using "listOsTypes"  and then use "listTemplates" command. So,
>> this template is used to deploy the vm.  As far as i know, a builtin
>> template cannot be a windows template?  Here, we use a featured and builtin
>> template along with description filter passed. So, please check whether the
>> template you are retrieving is windows or otherwise. Check for the field
>> ostypename for the output you receive? Provide the output here for
>> get_template copy pasted with dir(template) for return value?
>>
>> 2. To double confirm that it is template issue and not any other issue
>> related to ssh like ( firewall\iptables\network connectivity issue) for
>> ssh, please manually check for that particular ip in the test case whether
>> ssh works or not and is not a windows machine?
>>
>> 3. Run one test case, first by adding a tag EX: "umesh" to the tags list
>> as mentioned below for a particular test case under test module EX:
>> test_loadbalance.py, then  run with nose command passing in tags argument
>> mentioned below.
>>
>>  @attr(tags = ["advanced", "advancedns", "smoke", "umesh"])
>>     def test_01_create_lb_rule_src_nat(self):
>>
>> nosetests-2.7 -v --with-marvin
>> --marvin-config=/root/softwares/cscode/setup/dev/advanced.cfg --load -a -w
>> /root/softwares/cscode/test/integration/smoke/ -a tags=umesh
>>
>> Let me know.
>>
>> Regards,
>> Santhosh
>> ________________________________________
>> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
>> ><ma...@gmail.com>>]
>> Sent: Tuesday, January 14, 2014 7:02 AM
>> To: Santhosh Edukulla
>> Cc: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><ma...@cloudstack.apache.org>>;
>> Chandan Purushothama; Sudha Ponnaganti
>> Subject: Re: Regarding cloudstack automation
>>
>> I re-installed the marvin today to get the latest code.
>> I am again facing the same problem in get_template. It is returning the
>> windows template and creating the windows VM. Hence when it tries to do SSH
>> for VM, it fails.
>>
>> I have also build the cloudstack to get the latest code for Marvin.
>>
>> PFA the script logs and test_loadbalance script for reference.
>>
>> Also, do let me know if I am missing some configuration or anything...
>>
>> Just an FYI.. I have executed 35 scripts in smoke test directory. Out of
>> 35 scripts executed, 17-PASS, 18-FAIL.
>> Around 50% failure are due to SSH related issue.
>>
>> Thanks and Regards
>> -- Umesh Kute
>>
>>
>> On Fri, Jan 10, 2014 at 5:53 PM, Santhosh Edukulla <
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>>> wrote:
>> 1. As such because of  bug in get_template, you are getting windows
>> machine in your setup and then ssh is tried in test module, so you are
>> getting the error.
>>
>> 2. Now, to overcome, just checkout the latest marvin, it should have a
>> fix.
>>
>> Note: It still has some other issues, but you can continue with your
>> testing further. Let us know.
>>
>> Santhosh
>> ________________________________________
>> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
>> ><ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>]
>> Sent: Friday, January 10, 2014 5:19 AM
>> To: Santhosh Edukulla
>> Cc: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><ma...@cloudstack.apache.org>>>;
>> Chandan Purushothama; Sudha Ponnaganti
>> Subject: Re: Regarding cloudstack automation
>>
>> So far i have found the failure on following scripts:
>> 1. test_loadbalance
>> 2. test_network
>> 3. test_nic
>>
>> In runinfo.txt log it is stuck at the step:
>> SSH into VM (IPaddress: 10.1.1.55) & NAT Rule (Public IP: 207.x.x.x)
>>
>> PFA the Marvin logs for the test_loadbalance.py script.
>>
>> I have modified the following entry in the script i.e. provided the
>> correct template name which is present.
>> "ostype": "CentOS 6.4 (64-bit)",
>> #"ostype": "CentOS 5.3 (64-bit)",
>>
>> Please let me know for your comments.
>>
>> Thanks and Regards
>> -- Umesh Kute
>>
>>
>>
>> On Fri, Jan 10, 2014 at 2:57 PM, Santhosh Edukulla <
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com>>>>>
>> wrote:
>> You can log the bug for this. We have fixed few other issues along with
>> this in a private branch. Will soon merge with ACS. If you need a temporary
>> fix, let me know.
>>
>> Question : Related to ssh issue, ssh to vm failing at which part? Can you
>> add some information related to ssh failure which test module, which case
>> etc? This may be related\unrelated to the above issue. We can check to see
>> the issue is either same\different.
>>
>> Santhosh
>> ________________________________________
>> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
>> ><ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>]
>> Sent: Friday, January 10, 2014 4:21 AM
>> To: Santhosh Edukulla
>> Cc: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><ma...@cloudstack.apache.org>>>>;
>> Chandan Purushothama; Sudha Ponnaganti
>> Subject: Re: Regarding cloudstack automation
>>
>> Thanks a lot Santhosh For your response.
>>
>> Sorry for delay.. But is there any workaround for this issue? Because as
>> i mentioned, even if os type is provided as "ostype": 'CentOS 6.4 (64-bit)'
>> it is picking up the first one in list i.e. Windows Server 2008 R2
>> Enterprise.
>> So some of the scripts which required to SSH into VM are failing.
>>
>> Can I get the JIRA ID for this issue to track?
>>
>> Thanks and Regards
>> -- Umesh Kute
>>
>>
>> On Fri, Jan 3, 2014 at 5:19 PM, Santhosh Edukulla <
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >>>><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>>>>> wrote:
>> Umesh,
>>
>> This could be probably due to the bug under get_template function under
>> marvin/integration/lib/common.py. Though, the ostype description is used
>> and corresponding id is retrieved.
>>
>> But the later part, listTemplate API call returning the list and we are
>> picking up either the template which is ready or matching with id we
>> retrieved. This case is what could be causing the issue you mentioned.
>>
>> Regards,
>> Santhosh
>> ________________________________________
>> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
>> ><ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>>]
>> Sent: Friday, January 03, 2014 5:04 AM
>> To: Santhosh Edukulla; users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>>>
>> Cc: Chandan Purushothama; Sudha Ponnaganti
>> Subject: Re: Regarding cloudstack automation
>>
>> Thanks for your help Santhosh!!!
>>
>> You are right...
>> The public IP address range was exhausted. After cleaning up the
>> resources, I was able to run the sample script "test_deploy_vm.py"
>> successfully.
>>
>> One question - i have provided the "ostype": 'CentOS 6.4 (64-bit)'. What
>> is the use of this parameter?
>>
>> When observed in management server logs and on cloudstack UI (while
>> running script), VM was created of type: "Windows Server 2008 R2 Enterprise
>> with SQL 2012 Web Edition". This is the first one in the list.
>>
>> Does it choose the one which we provided in script or picks it from the
>> template list that is returned as a result of response to listTemplate API
>> call?
>>
>> Thanks and Regards
>> -- Umesh Kute
>>
>>
>> On Thu, Jan 2, 2014 at 7:22 PM, Santhosh Edukulla <
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >>>><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>>>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >>><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>>>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com>>>>>>>
>> wrote:
>> Umesh,
>>
>> 1. It seems you have exhausted few of CloudStack Resources. These
>> resources usage should show up on your cloudstack dashboard. Anything
>> appears in Red are exhausted resources.
>>
>> 2. Few of the cases could be EX: Guest VM IPs\Management ip addresses
>>  are exhausted,
>>
>> 3. Check for these resources in Red on your dashboard EX:
>> http://localhost:8080/client/->Dashboard and clean up them or add new
>> resources.
>>
>>
>> Santhosh
>> ________________________________________
>> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
>> ><ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>>>]
>> Sent: Thursday, January 02, 2014 7:06 AM
>> To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>
>> Cc: Chandan Purushothama; Sudha Ponnaganti
>> Subject: Re: Regarding cloudstack automation
>>
>> Thank you once again Santhosh & Chandan.
>>
>> I have gone through the management server logs. The deployment of VM got
>> fired to the setup correctly and there are couple of errors in the
>> management-server log.
>> I am summarizing those below:
>>
>> test data in "test_deploy_vm.py"
>>  def __init__(self):
>>         self.testdata = {
>>             #data to create an account
>>             "account": {
>>                 "email": "test@test.com<ma...@test.com><mailto:
>> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
>> test@test.com><ma...@test.com>>><mailto:
>> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
>> test@test.com>><ma...@test.com><mailto:
>> test@test.com<ma...@test.com>>>><mailto:test@test.com<mailto:
>> test@test.com><ma...@test.com>><mailto:
>> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
>> test@test.com>>><ma...@test.com><mailto:
>> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
>> test@test.com><ma...@test.com>>>>><mailto:
>> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
>> test@test.com>><ma...@test.com><mailto:
>> test@test.com<ma...@test.com>>><mailto:test@test.com<mailto:
>> test@test.com><ma...@test.com>><mailto:
>> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
>> test@test.com>>>><ma...@test.com><mailto:
>> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
>> test@test.com><ma...@test.com>>><mailto:
>> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
>> test@test.com>><ma...@test.com><mailto:
>> test@test.com<ma...@test.com>>>>>><mailto:test@test.com<mailto:
>> test@test.com><ma...@test.com>><mailto:
>> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
>> test@test.com>>><ma...@test.com><mailto:
>> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
>> test@test.com><ma...@test.com>>>><mailto:
>> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
>> test@test.com>><ma...@test.com><mailto:
>> test@test.com<ma...@test.com>>><mailto:test@test.com<mailto:
>> test@test.com><ma...@test.com>><mailto:
>> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
>> test@test.com>>>>><ma...@test.com><mailto:
>> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
>> test@test.com><ma...@test.com>>><mailto:
>> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
>> test@test.com>><ma...@test.com><mailto:
>> test@test.com<ma...@test.com>>>><mailto:test@test.com<mailto:
>> test@test.com><ma...@test.com>><mailto:
>> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
>> test@test.com>>><ma...@test.com><mailto:
>> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
>> test@test.com><ma...@test.com>>>>>>>",
>>                 "firstname": "Test",
>>                 "lastname": "User",
>>                 "username": "test",
>>                 "password": "password",
>>             },
>>             #data reqd for virtual machine creation
>>             "virtual_machine" : {
>>                 "name" : "testvmshr",
>>                 "displayname" : "Test VM shr",
>>             },
>>             #small service offering
>>             "service_offering": {
>>                 "small": {
>>                     "name": "SOSmall",
>>                     "displaytext": "Small Instance",
>>                     "cpunumber": 1,
>>                     "cpuspeed": 2000,
>>                     "memory": 1024,
>>                 },
>>             },
>>             "ostype": 'CentOS 6.4 (64-bit)',
>>         }
>>
>>
>> 1. Account is successfully created
>> 2. Service offering is successfully created
>> 3. Management server logs - management-server.log has following error:
>>
>>
>> 2014-01-02 01:43:40,693 DEBUG [cloud.network.NetworkManagerImpl]
>> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
>> Lock is released for network Ntwk[326|Guest|15] as a part of network
>> shutdown
>> 2014-01-02 01:43:40,695 DEBUG [cloud.network.NetworkManagerImpl]
>> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
>> Lock is released for network id 326 as a part of network implement
>> 2014-01-02 01:43:40,695 INFO  [cloud.vm.VirtualMachineManagerImpl]
>> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
>> Insufficient capacity
>> com.cloud.exception.InsufficientAddressCapacityException: Insufficient
>> address capacityScope=interface com.cloud.dc.DataCenter; id=1
>> at
>> com.cloud.network.NetworkManagerImpl.fetchNewPublicIp(NetworkManagerImpl.java:479)
>> at
>> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
>> at
>> com.cloud.network.NetworkManagerImpl.assignDedicateIpAddress(NetworkManagerImpl.java:613)
>> at
>> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
>> at
>> com.cloud.network.NetworkManagerImpl.assignSourceNatIpAddressToGuestNetwork(NetworkManagerImpl.java:582)
>> at
>> com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:2013)
>> at
>> com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1939)
>> at
>> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
>> at
>> com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2120)
>> at
>> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:887)
>> at
>> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
>> at
>> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
>> at
>> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
>> at
>> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
>> at
>> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
>> at
>> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
>> at
>> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
>> at
>> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
>> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
>> at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
>> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
>> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> at java.lang.Thread.run(Thread.java:679)
>> 2014-01-02 01:43:40,703 DEBUG [cloud.vm.VirtualMachineManagerImpl]
>> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
>> Cleaning up resources for the vm VM[User|testvmshr] in Starting state
>>
>> 4. When i checked the database for the network id 326 in table
>> "networks", it has following entry:
>>
>> | 326 | test-TestDeployVM-test_deploy_vm-QQ91N0-network |
>> b7cb9e31-835f-47e3-9585-97e3b4084e4d |
>> test-TestDeployVM-test_deploy_vm-QQ91N0-network | Guest        | Vlan
>>            | NULL          | 10.1.1.1       | 10.1.1.0/24<
>> http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><
>> http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><
>> http://10.1.1.0/24>     | Dhcp   |                  15 |
>> 200 |              1 | ExternalGuestNetworkGuru | Destroy     |     326 |
>>       1 |        305 | 8.8.8.8 | 8.8.4.4 | NULL      |          0 | Account
>>  | cs131cloud.internal | ecf5b617-04da-469b-b378-f53e05d8cc53 | Isolated
>> |                0 | 2014-01-02 06:43:39 | 2014-01-02 06:43:46 |
>>       0 |   NULL | NULL        | NULL     | NULL         |               1
>> |           NULL |
>>
>>
>> Basically it tries to create a network offering (id=15) : "HA Isolated
>> Network With Source Nat"
>>
>>
>> 5. I think the script creates a network shown in above table:
>> "test-TestDeployVM-test_deploy_vm-QQ91N0-network".
>>
>> I am not sure why it still gives the Insufficient address capacityScope
>> exception.
>>
>> 6. One more thing i observed. I have provided the "ostype": 'CentOS 6.4
>> (64-bit)'. But in DeployVMCmd it uses the template id:
>> "03ffb96f-2cfa-11e3-a4f0-f245a5b3ba0f" which is for template "Windows
>> Server 2008 R2 Enterprise with SQL 2012 Web Edition".
>>
>>
>> I am attaching the management-server logs and script logs for references.
>>
>> If somebody can help me what's wrong here, would really be helpful.
>>
>>
>> Thanks and Regards
>> -- Umesh Kute
>>
>>
>> On Thu, Jan 2, 2014 at 2:59 PM, Santhosh Edukulla <
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >>>><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>>>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >>><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>>>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >>>>>><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >>><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>>>>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >>>><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>>>>>>> wrote:
>> 1. Is it still failing post this registration?
>>
>> 2. If yes, may be you can verify\provide the management server logs.
>> ________________________________________
>> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
>> ><ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>>>>]
>> Sent: Thursday, January 02, 2014 4:16 AM
>> To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>>>>>
>> Cc: Chandan Purushothama; Sudha Ponnaganti
>> Subject: Re: Regarding cloudstack automation
>>
>> Thanks Santhosh.
>> Yes, I have registered the following template which i am using.
>>
>> "ostype": 'CentOS 6.4 (64-bit)',
>>
>> Thanks and Regards
>> -- Umesh Kute
>>
>>
>> On Mon, Dec 30, 2013 at 5:50 PM, Santhosh Edukulla <
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >>>><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>>>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >>><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>>>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >>>>>><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >>><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>>>>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >>>><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
>> <ma...@citrix.com>>><mailto:
>> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
>> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
>> >><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
>> santhosh.edukulla@citrix.com>>>>>>>> wrote:
>>
>> > Umesh,
>> >
>> > One question : Did you registered the template for ostype:     "ostype":
>> > 'CentOS 5.3 (64-bit)'?
>> >
>> > Regards,
>> > Santhosh
>> > ________________________________________
>> > From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
>> ><ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>>>>]
>> > Sent: Monday, December 30, 2013 6:32 AM
>> > To: Chandan Purushothama
>> > Cc: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>>>>>; Sudha Ponnaganti
>> > Subject: Re: Regarding cloudstack automation
>> >
>> > Hi Chandan,
>> > Thanks for your response.
>> > I have the latest Marvin repository (December 20th). I am able to
>> proceed
>> > further. There was an issue of firewall for that machine and it got
>> > resolved.
>> >
>> > But now i am getting another error when i tried to run the script
>> > "test_deploy_vm.py"
>> >
>> > I have attached the log. Can somebody please have a look on it and help
>> me
>> > in resolving the issue?
>> >
>> >
>> >
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> > test_deploy_vm (integration.smoke.test_deploy_vm.TestDeployVM):
>> CRITICAL:
>> > EXCEPTION: test_deploy_vm: Traceback (most recent call last):
>> >   File "/usr/local/lib/python2.7/unittest/case.py", line 327, in run
>> >     testMethod()
>> >   File
>> > "/DataDisk/temp/cloudstack/test/integration/smoke/test_deploy_vm.py",
>> line
>> > 116, in test_deploy_vm
>> >     templateid=self.template.id<http://self.template.id><
>> http://self.template.id><http://self.template.id><http://self.template.id
>> ><http://self.template.id><http://self.template.id><
>> http://self.template.id><http://self.template.id>
>> >   File
>> > "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py",
>> > line 415, in create
>> >     virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
>> >   File
>> >
>> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
>> > line 593, in deployVirtualMachine
>> >     response = self.connection.marvinRequest(command,
>> > response_type=response, method=method)
>> >   File
>> > "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
>> > line 280, in marvinRequest
>> >     response = self.poll(asyncJobId, response_type)
>> >   File
>> > "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
>> > line 86, in poll
>> >     "asyncquery", asyncResonse.jobresult)
>> > cloudstackAPIException: Execute cmd: asyncquery failed, due to:
>> {errorcode
>> > : 533, errortext : u'Unable to create a deployment for
>> VM[User|testvmshr]'}
>> >
>> >
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> >
>> > PFA entire logs.
>> >
>> > Please let me know in case if anything is required.
>> >
>> > Thanks and Regards
>> > -- Umesh Kute
>> >
>> >
>> > On Sun, Dec 29, 2013 at 10:32 PM, Chandan Purushothama <
>> > Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>>>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>>>>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>>>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
>> <ma...@citrix.com>><mailto:
>> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
>> ><mailto:Chandan.Purushothama@citrix.com<mailto:
>> Chandan.Purushothama@citrix.com>>>>>>>>>
>> > wrote:
>> >
>> > Hello Umesh,
>> >
>> > I had a similar experience with an older Marvin build. I updated mine to
>> > the latest and tried again and it worked. I recommend you to kindly try
>> > again with the latest Marvin build and see if you are able to work with
>> the
>> > automation framework,
>> >
>> > Thank you,
>> > Chandan
>> >
>> >
>> > -------- Original message --------
>> > From: umesh kute
>> > Date:12/26/2013 12:29 AM (GMT-08:00)
>> > To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>>>>>>,Sudha
>> > Ponnaganti
>> > Subject: Re: Regarding cloudstack automation
>> >
>> > Hi All,
>> > I have created a Marvin setup on CentOS6.3 by following the document:
>> >
>> >
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
>> >
>> > All the pre-requisites are installed successfully.
>> >
>> > I tried to run the sample script test_deploy_vm.py
>> > (cloudstack/test/integration/smoke/), I am getting following error:
>> >
>> >
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> > [root@localhost smoke]# nosetests --with-marvin
>> > --marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg
>> --load
>> > test_deploy_vm.py
>> >
>> >  Exception Occurred Under __deployDC :
>> > HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
>> > with url: /client/api?account=admin&command=listUsers&response=json
>> (Caused
>> > by <class 'socket.error'>: [Errno 110] Connection timed out)
>> > Traceback (most recent call last):
>> >   File "/usr/local/bin/nosetests", line 9, in <module>
>> >     load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
>> >   File
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
>> > line 118, in __init__
>> >     **extra_args)
>> >   File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
>> >     self.runTests()
>> >   File
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
>> > line 197, in runTests
>> >     result = self.testRunner.run(self.test)
>> >   File
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
>> > line 61, in run
>> >     test(result)
>> >   File
>> >
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
>> > line 176, in __call__
>> >     return self.run(*arg, **kw)
>> >   File
>> >
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
>> > line 223, in run
>> >     test(orig)
>> >   File
>> >
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
>> > line 176, in __call__
>> >     return self.run(*arg, **kw)
>> >   File
>> >
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
>> > line 223, in run
>> >     test(orig)
>> >   File
>> >
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
>> > line 176, in __call__
>> >     return self.run(*arg, **kw)
>> >   File
>> >
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
>> > line 223, in run
>> >     test(orig)
>> >   File
>> >
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
>> > line 176, in __call__
>> >     return self.run(*arg, **kw)
>> >   File
>> >
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
>> > line 223, in run
>> >     test(orig)
>> >   File
>> >
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
>> > line 176, in __call__
>> >     return self.run(*arg, **kw)
>> >   File
>> >
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
>> > line 223, in run
>> >     test(orig)
>> >   File
>> >
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
>> > line 176, in __call__
>> >     return self.run(*arg, **kw)
>> >   File
>> >
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
>> > line 223, in run
>> >     test(orig)
>> >   File
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
>> > line 45, in __call__
>> >     return self.run(*arg, **kwarg)
>> >   File
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
>> > line 138, in run
>> >     result.addError(self, err)
>> >   File
>> >
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
>> > line 124, in addError
>> >     plugin_handled = plugins.handleError(self.test, err)
>> >   File
>> >
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
>> > line 99, in __call__
>> >     return self.call(*arg, **kw)
>> >   File
>> >
>> >
>> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
>> > line 167, in simple
>> >     result = meth(*arg, **kw)
>> >   File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
>> > line 155, in handleError
>> >     self.tcRunLogger.fatal("%s: %s: %s" %
>> > AttributeError: 'NoneType' object has no attribute 'fatal'
>> >
>> >
>> >
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> >
>> > The logs are generated at /tmp and the log has following error.
>> >
>> >
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> > 2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
>> > {'account': 'admin'}
>> > 2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
>> > http://10.88.91.100:8096/client/api :
>> > HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
>> > with url: /client/api?account=admin&command=listUsers&response=json
>> (Caused
>> > by <class 'socket.error'>: [Errno 110] Connection timed out)
>> >
>> >
>> >
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> >
>> > Please note: I have opened the integration port 8096 on management
>> server.
>> > Also, changed the global settings integration.api.port
>> > on cloudstack GUI to 8096 and restarted the management server.
>> >
>> > Still I am getting the above issue. I am not sure if i missed any
>> > configuration.
>> >
>> > Can somebody please help me with resolution of this issue?
>> > Appreciate your help here!!!
>> >
>> > Thanks and Regards
>> > -- Umesh Kute
>> >
>> >
>> > On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <umeshvkute@gmail.com
>> <ma...@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>>>>><mailto:
>> > umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com><mailto:
>> umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>> wrote:
>> >
>> > > Thanks a lot Sudha for your quick response.
>> > > I will setup the Marvin on local machine and get back in case if I
>> face
>> > > any challenges in setup.
>> > >
>> > > Thanks and Regards
>> > > -- Umesh Kute
>> > >
>> > >
>> > >
>> > > On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
>> > > sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
>> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
>> >><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
>> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
>> >>><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
>> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
>> >><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
>> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
>> >>>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>>>>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>>>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
>> >>>>>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>>>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>>>>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
>> >>>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>>>>>>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>>>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
>> >>>>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>>>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>>>>>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
>> >>>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
>> sudha.ponnaganti@citrix.com>>>>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
>> <ma...@citrix.com>>>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
>> sudha.ponnaganti@citrix.com<ma...@citrix.com>>>>>>>>>
>> wrote:
>> > >
>> > >> Hi Umesh,
>> > >>
>> > >> Looks like you have started on right track - Marvin is the framework
>> to
>> > >> use for functional or integration automation.
>> > >> There are sizable number of test cases exist and you can review them.
>> > >>  There are some wiki pages already written explaining Marvin [1].
>> Also
>> > best
>> > >> practices are published by community as well [2]. You can contribute
>> to
>> > it
>> > >> as much as you can.
>> > >>
>> > >> Besides this, there is Junit framework (unit Test), Selenium
>> framework
>> > >> (UI automation) which are not as popular as Marvin. Marvin is perfect
>> > for
>> > >> majority of the validation. You can use simulator as well with
>> Marvin.
>> > >>
>> > >> Please do pursue these and post questions to the community if you
>> run in
>> > >> to any issues in setting up env and running tests. There are jobs
>> setup
>> > by
>> > >> various community members to test Master or current releases in
>> various
>> > >> labs and can help answer questions.
>> > >>
>> > >> [1]
>> > >>
>> >
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
>> > >>
>> > >>
>> > >> Thanks
>> > >> /Sudha
>> > >>
>> > >>
>> > >> -----Original Message-----
>> > >> From: umesh kute [mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
>> umeshvkute@gmail.com>>>>>>>]
>> > >> Sent: Saturday, December 07, 2013 10:29 PM
>> > >> To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
>> >>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
>> users@cloudstack.apache.org>>>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
>> <ma...@cloudstack.apache.org>>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
>> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>
>> > >> Subject: Regarding cloudstack automation
>> > >>
>> > >> Hi All,
>> > >> Good morning !!!
>> > >> I am working as QA engineer and I am new to the cloudstack community.
>> > >> We have started using cloudstack and deployed it in our
>> infrastructure.
>> > >>
>> > >> Can somebody please help me in identifying the good automation
>> > >> framework/tool/anything? The main intention is we want to automate
>> the
>> > >> infrastructure validation related cases (for e.g.
>> create/update/delete
>> > >> cases for instances, project, network, etc...)
>> > >>
>> > >> It would be good if you can help in identifying it.
>> > >>
>> > >> Please note: I have gone through cloudmonkey. But i haven't found
>> much
>> > >> help on it. May be i need to search a bit more.. I am also going
>> through
>> > >> the marvin and planning to setup it. If apart from these two, if
>> anyone
>> > has
>> > >> different view please suggest.
>> > >>
>> > >> Also, if somebody has any pointers on cloudmonkey and marvin or any
>> more
>> > >> info on this (like, if it would suffice the infrastructure validation
>> > >> related cases i mentioned above) any pros/cons would really be
>> helpful
>> > for
>> > >> me...
>> > >>
>> > >> Appreciate any help on this and looking forward for the response on
>> > >> this!!!
>> > >>
>> > >> Thanks and Regards
>> > >> -- Umesh Kute
>> > >>
>> > >
>> > >
>> >
>> >
>>
>>
>>
>>
>

RE: Regarding cloudstack automation

[Santhosh Edukulla <sa...@citrix.com>]

Umesh,

1. There should not be any issues inherent inside of it as such not to run scripts atleast existing ones altogether. Now, compared to earlier mentioned failures viz., ssh,password, template etc ,these are mainly away from framework and are setup issues.

2. Component signifies regression cases, if you already know. Now for the run and failures count, mentioned below, can you let us know what are the failures or You can attach logs to elucidate the failures? Regression do run almost every day for various releases and has many passes and failures if any for product logged as bugs. The pass % for regression is more than 90% as far iam aware. The failures below, could be mainly due to infrastructure\setup specific or the way we may perceive it to run because of it few limitations.  

3. We can help you to setup and start running marvin. Are all cases for bvt running first and with no issues? Mention the host and infrastructure setup details and flow you are using.

4. Also, we have a topic branch created for marvin. If you see an issue anywhere, you can log a bug, submit a patch for review to fix the same there.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com]
Sent: Friday, January 24, 2014 8:04 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org; Chandan Purushothama; Sudha Ponnaganti; dev@cloudstack.apache.org
Subject: Re: Regarding cloudstack automation

Hi Santhosh,
To proceed further I deployed the template by disabling password and providing the default password as "password". Now its able to connect using ssh.

But when I started with the test case execution for the scripts which are there in "component folder", Out of 80 scripts, executed 11 and all 11 are failing (mentioned below).

test_affinity_groups.py
test_add_remove_network.py
test_accounts.py
test_allocation_states.py
test_baremetal.py
test_assign_vm.py
test_vm_passwdenabled.py
test_vpc_vm_life_cycle.py
test_vpc_routers.py
test_vpn_users.py
test_vpc_vms_deployment.py

Are there any issues with Marvin framework for running component script and is it executed before? I am facing many failures in a script.

If required I can share the logs.

Please note: We have a cloudstack 4.2 deployed in lab. We planned to use the Marvin to validate the cloudstack infrastructure. I have installed the marvin (0.1.0) and cloudstack using (4.2).

Thanks and Regards
-- Umesh Kute


On Sat, Jan 18, 2014 at 2:31 AM, Santhosh Edukulla <sa...@citrix.com>> wrote:
Umesh,

1. Its good that the template issue is resolved.

2. Regarding point 4 mentioned below, your understanding is right. The idea is during automation run for various test suites,  we use a template seeded into CS which has the password set with the one used in Services Class. So, in a way for all test suites having this password mentioned is assumed to be having an instance deployed with template matching our condition and so ssh works.

3. There are test cases pertaining explicitly to verify reset cases under CS, that covers scenarios to test, but for every ssh we dont use the password given by the API output.

4. So, for creating instances you can use a template with password as "password" for your testing, thats the easy solution i believe and all test suits has this password inside them, it will work. In a way, this not so a good design, but
We are planning to remove Services class test data from tests and separate it out as a test data, So for user running tests can alter the config to suit the template he has and all test suites using ssh works and will be configurable, compared to now we have to modify all test suites to get it working with custom password for user.

Thanks!
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>]
Sent: Friday, January 17, 2014 7:32 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Hi Santhosh,
Thanks again...
I tried the steps that you mentioned below. Fortunately i could able to proceed a bit further on this issue.

Now, instance got created successfully of type CentOS 6.4 (64-bit).

It is stuck in the ssh step.
Here is what happens...

1. All the steps/APIs till instance creation works fine (including listDomains, listZones, listOsTypes, listTemplates, createAccount, createServiceOffering, deployVirtualMachine, queryAsyncJobResult, associateIPAddress, createFirewallRules, createPortForwardingRule, createEgressFirewallRule)

2. When it tries to SSH to virtual machine it fails after timeout of 600s (20-retries, 30-intervals). Script is terminated.

3. I put some debug statements in function get_ssh_client() under: "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py"

The credentials i think it tries is :
self.ssh_ip: 207.x.x.x
self.ssh_port: 22
self.username: root
self.password: password
keyPairFileLocation: None

It means, it tries to connect to instance using password as password (it is provided in dictionary in test_vm_passwdenabled.py. Note: Earlier i gave references for test_loadbalance.py and its the same case).

4. In log, i found that the password that is returned in response to deployVirtualMachine API call is: xA2yeaxvb. (PFA file runinfo). When i tried to do ssh to the instance with same password it works and with dictionary "password" it doesn't. I think so.. please confirm...

Either, for ssh connection it should use the returned password or reset password before connection.

PFA all the logs.
Please correct if my understanding is correct or I am missing something here....

Please let me know if there is any resolution of this issue or if somebody encounters it before.

Thanks and Regards
-- Umesh Kute

On Tue, Jan 14, 2014 at 6:48 PM, Santhosh Edukulla <sa...@citrix.com>>> wrote:
Umesh,

Lets put steps so that we are in same page:

1. When we deploy  a VM, we use get_template function which basically retrieves the template information matching the description you provided under services class for ostype under test module EX: test_loadbalance.py.  I am surprised that you are receiving a "featured" and "builtin" template as windows template as output for this function. We are explicitly verifiying the template type as "BUILTIN" to retrieve the template information. So, a windows template cannot be a BUILTIN Template. Either it could be a bug in this function, or something with API. But, to double confirm, Can you please check whats the template information you are retrieving from this function matching with listTemplates API output( run either from your browser or script )  passing the same arguments as passed inside get_template?

Inside if we see, basically it gets the id matching with that ostype description using "listOsTypes"  and then use "listTemplates" command. So, this template is used to deploy the vm.  As far as i know, a builtin template cannot be a windows template?  Here, we use a featured and builtin template along with description filter passed. So, please check whether the template you are retrieving is windows or otherwise. Check for the field ostypename for the output you receive? Provide the output here for get_template copy pasted with dir(template) for return value?

2. To double confirm that it is template issue and not any other issue related to ssh like ( firewall\iptables\network connectivity issue) for ssh, please manually check for that particular ip in the test case whether ssh works or not and is not a windows machine?

3. Run one test case, first by adding a tag EX: "umesh" to the tags list as mentioned below for a particular test case under test module EX: test_loadbalance.py, then  run with nose command passing in tags argument mentioned below.

 @attr(tags = ["advanced", "advancedns", "smoke", "umesh"])
    def test_01_create_lb_rule_src_nat(self):

nosetests-2.7 -v --with-marvin --marvin-config=/root/softwares/cscode/setup/dev/advanced.cfg --load -a -w /root/softwares/cscode/test/integration/smoke/ -a tags=umesh

Let me know.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>]
Sent: Tuesday, January 14, 2014 7:02 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

I re-installed the marvin today to get the latest code.
I am again facing the same problem in get_template. It is returning the windows template and creating the windows VM. Hence when it tries to do SSH for VM, it fails.

I have also build the cloudstack to get the latest code for Marvin.

PFA the script logs and test_loadbalance script for reference.

Also, do let me know if I am missing some configuration or anything...

Just an FYI.. I have executed 35 scripts in smoke test directory. Out of 35 scripts executed, 17-PASS, 18-FAIL.
Around 50% failure are due to SSH related issue.

Thanks and Regards
-- Umesh Kute


On Fri, Jan 10, 2014 at 5:53 PM, Santhosh Edukulla <sa...@citrix.com>>>> wrote:
1. As such because of  bug in get_template, you are getting windows machine in your setup and then ssh is tried in test module, so you are getting the error.

2. Now, to overcome, just checkout the latest marvin, it should have a fix.

Note: It still has some other issues, but you can continue with your testing further. Let us know.

Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>]
Sent: Friday, January 10, 2014 5:19 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

So far i have found the failure on following scripts:
1. test_loadbalance
2. test_network
3. test_nic

In runinfo.txt log it is stuck at the step:
SSH into VM (IPaddress: 10.1.1.55) & NAT Rule (Public IP: 207.x.x.x)

PFA the Marvin logs for the test_loadbalance.py script.

I have modified the following entry in the script i.e. provided the correct template name which is present.
"ostype": "CentOS 6.4 (64-bit)",
#"ostype": "CentOS 5.3 (64-bit)",

Please let me know for your comments.

Thanks and Regards
-- Umesh Kute



On Fri, Jan 10, 2014 at 2:57 PM, Santhosh Edukulla <sa...@citrix.com>>>>> wrote:
You can log the bug for this. We have fixed few other issues along with this in a private branch. Will soon merge with ACS. If you need a temporary fix, let me know.

Question : Related to ssh issue, ssh to vm failing at which part? Can you add some information related to ssh failure which test module, which case etc? This may be related\unrelated to the above issue. We can check to see the issue is either same\different.

Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>]
Sent: Friday, January 10, 2014 4:21 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks a lot Santhosh For your response.

Sorry for delay.. But is there any workaround for this issue? Because as i mentioned, even if os type is provided as "ostype": 'CentOS 6.4 (64-bit)' it is picking up the first one in list i.e. Windows Server 2008 R2 Enterprise.
So some of the scripts which required to SSH into VM are failing.

Can I get the JIRA ID for this issue to track?

Thanks and Regards
-- Umesh Kute


On Fri, Jan 3, 2014 at 5:19 PM, Santhosh Edukulla <sa...@citrix.com>>>>>> wrote:
Umesh,

This could be probably due to the bug under get_template function under marvin/integration/lib/common.py. Though, the ostype description is used and corresponding id is retrieved.

But the later part, listTemplate API call returning the list and we are picking up either the template which is ready or matching with id we retrieved. This case is what could be causing the issue you mentioned.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>]
Sent: Friday, January 03, 2014 5:04 AM
To: Santhosh Edukulla; users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks for your help Santhosh!!!

You are right...
The public IP address range was exhausted. After cleaning up the resources, I was able to run the sample script "test_deploy_vm.py" successfully.

One question - i have provided the "ostype": 'CentOS 6.4 (64-bit)'. What is the use of this parameter?

When observed in management server logs and on cloudstack UI (while running script), VM was created of type: "Windows Server 2008 R2 Enterprise with SQL 2012 Web Edition". This is the first one in the list.

Does it choose the one which we provided in script or picks it from the template list that is returned as a result of response to listTemplate API call?

Thanks and Regards
-- Umesh Kute


On Thu, Jan 2, 2014 at 7:22 PM, Santhosh Edukulla <sa...@citrix.com>>>>>>> wrote:
Umesh,

1. It seems you have exhausted few of CloudStack Resources. These resources usage should show up on your cloudstack dashboard. Anything appears in Red are exhausted resources.

2. Few of the cases could be EX: Guest VM IPs\Management ip addresses  are exhausted,

3. Check for these resources in Red on your dashboard EX: http://localhost:8080/client/->Dashboard and clean up them or add new resources.


Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>]
Sent: Thursday, January 02, 2014 7:06 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thank you once again Santhosh & Chandan.

I have gone through the management server logs. The deployment of VM got fired to the setup correctly and there are couple of errors in the management-server log.
I am summarizing those below:

test data in "test_deploy_vm.py"
 def __init__(self):
        self.testdata = {
            #data to create an account
            "account": {
                "email": "test@test.com<ma...@test.com>>>>>>>",
                "firstname": "Test",
                "lastname": "User",
                "username": "test",
                "password": "password",
            },
            #data reqd for virtual machine creation
            "virtual_machine" : {
                "name" : "testvmshr",
                "displayname" : "Test VM shr",
            },
            #small service offering
            "service_offering": {
                "small": {
                    "name": "SOSmall",
                    "displaytext": "Small Instance",
                    "cpunumber": 1,
                    "cpuspeed": 2000,
                    "memory": 1024,
                },
            },
            "ostype": 'CentOS 6.4 (64-bit)',
        }


1. Account is successfully created
2. Service offering is successfully created
3. Management server logs - management-server.log has following error:


2014-01-02 01:43:40,693 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Lock is released for network Ntwk[326|Guest|15] as a part of network shutdown
2014-01-02 01:43:40,695 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Lock is released for network id 326 as a part of network implement
2014-01-02 01:43:40,695 INFO  [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Insufficient capacity
com.cloud.exception.InsufficientAddressCapacityException: Insufficient address capacityScope=interface com.cloud.dc.DataCenter; id=1
at com.cloud.network.NetworkManagerImpl.fetchNewPublicIp(NetworkManagerImpl.java:479)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.assignDedicateIpAddress(NetworkManagerImpl.java:613)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.assignSourceNatIpAddressToGuestNetwork(NetworkManagerImpl.java:582)
at com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:2013)
at com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1939)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2120)
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:887)
at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2014-01-02 01:43:40,703 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Cleaning up resources for the vm VM[User|testvmshr] in Starting state

4. When i checked the database for the network id 326 in table "networks", it has following entry:

| 326 | test-TestDeployVM-test_deploy_vm-QQ91N0-network | b7cb9e31-835f-47e3-9585-97e3b4084e4d | test-TestDeployVM-test_deploy_vm-QQ91N0-network | Guest        | Vlan                  | NULL          | 10.1.1.1       | 10.1.1.0/24<http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24>     | Dhcp   |                  15 |                 200 |              1 | ExternalGuestNetworkGuru | Destroy     |     326 |         1 |        305 | 8.8.8.8 | 8.8.4.4 | NULL      |          0 | Account  | cs131cloud.internal | ecf5b617-04da-469b-b378-f53e05d8cc53 | Isolated   |                0 | 2014-01-02 06:43:39 | 2014-01-02 06:43:46 |                 0 |   NULL | NULL        | NULL     | NULL         |               1 |           NULL |


Basically it tries to create a network offering (id=15) : "HA Isolated Network With Source Nat"


5. I think the script creates a network shown in above table: "test-TestDeployVM-test_deploy_vm-QQ91N0-network".

I am not sure why it still gives the Insufficient address capacityScope exception.

6. One more thing i observed. I have provided the "ostype": 'CentOS 6.4 (64-bit)'. But in DeployVMCmd it uses the template id: "03ffb96f-2cfa-11e3-a4f0-f245a5b3ba0f" which is for template "Windows Server 2008 R2 Enterprise with SQL 2012 Web Edition".


I am attaching the management-server logs and script logs for references.

If somebody can help me what's wrong here, would really be helpful.


Thanks and Regards
-- Umesh Kute


On Thu, Jan 2, 2014 at 2:59 PM, Santhosh Edukulla <sa...@citrix.com>>>>>>>> wrote:
1. Is it still failing post this registration?

2. If yes, may be you can verify\provide the management server logs.
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>>]
Sent: Thursday, January 02, 2014 4:16 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks Santhosh.
Yes, I have registered the following template which i am using.

"ostype": 'CentOS 6.4 (64-bit)',

Thanks and Regards
-- Umesh Kute


On Mon, Dec 30, 2013 at 5:50 PM, Santhosh Edukulla <
santhosh.edukulla@citrix.com<ma...@citrix.com>>>>>>>> wrote:

> Umesh,
>
> One question : Did you registered the template for ostype:     "ostype":
> 'CentOS 5.3 (64-bit)'?
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>>]
> Sent: Monday, December 30, 2013 6:32 AM
> To: Chandan Purushothama
> Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi Chandan,
> Thanks for your response.
> I have the latest Marvin repository (December 20th). I am able to proceed
> further. There was an issue of firewall for that machine and it got
> resolved.
>
> But now i am getting another error when i tried to run the script
> "test_deploy_vm.py"
>
> I have attached the log. Can somebody please have a look on it and help me
> in resolving the issue?
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> test_deploy_vm (integration.smoke.test_deploy_vm.TestDeployVM): CRITICAL:
> EXCEPTION: test_deploy_vm: Traceback (most recent call last):
>   File "/usr/local/lib/python2.7/unittest/case.py", line 327, in run
>     testMethod()
>   File
> "/DataDisk/temp/cloudstack/test/integration/smoke/test_deploy_vm.py", line
> 116, in test_deploy_vm
>     templateid=self.template.id<http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id>
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py",
> line 415, in create
>     virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> line 593, in deployVirtualMachine
>     response = self.connection.marvinRequest(command,
> response_type=response, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 280, in marvinRequest
>     response = self.poll(asyncJobId, response_type)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 86, in poll
>     "asyncquery", asyncResonse.jobresult)
> cloudstackAPIException: Execute cmd: asyncquery failed, due to: {errorcode
> : 533, errortext : u'Unable to create a deployment for VM[User|testvmshr]'}
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> PFA entire logs.
>
> Please let me know in case if anything is required.
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Sun, Dec 29, 2013 at 10:32 PM, Chandan Purushothama <
> Chandan.Purushothama@citrix.com<ma...@citrix.com>>>>>>>>>
> wrote:
>
> Hello Umesh,
>
> I had a similar experience with an older Marvin build. I updated mine to
> the latest and tried again and it worked. I recommend you to kindly try
> again with the latest Marvin build and see if you are able to work with the
> automation framework,
>
> Thank you,
> Chandan
>
>
> -------- Original message --------
> From: umesh kute
> Date:12/26/2013 12:29 AM (GMT-08:00)
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>,Sudha
> Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi All,
> I have created a Marvin setup on CentOS6.3 by following the document:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
>
> All the pre-requisites are installed successfully.
>
> I tried to run the sample script test_deploy_vm.py
> (cloudstack/test/integration/smoke/), I am getting following error:
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> [root@localhost smoke]# nosetests --with-marvin
> --marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg --load
> test_deploy_vm.py
>
>  Exception Occurred Under __deployDC :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
> Traceback (most recent call last):
>   File "/usr/local/bin/nosetests", line 9, in <module>
>     load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 118, in __init__
>     **extra_args)
>   File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
>     self.runTests()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 197, in runTests
>     result = self.testRunner.run(self.test)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 61, in run
>     test(result)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 45, in __call__
>     return self.run(*arg, **kwarg)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 138, in run
>     result.addError(self, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
> line 124, in addError
>     plugin_handled = plugins.handleError(self.test, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 99, in __call__
>     return self.call(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 167, in simple
>     result = meth(*arg, **kw)
>   File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
> line 155, in handleError
>     self.tcRunLogger.fatal("%s: %s: %s" %
> AttributeError: 'NoneType' object has no attribute 'fatal'
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> The logs are generated at /tmp and the log has following error.
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
> {'account': 'admin'}
> 2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
> http://10.88.91.100:8096/client/api :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Please note: I have opened the integration port 8096 on management server.
> Also, changed the global settings integration.api.port
> on cloudstack GUI to 8096 and restarted the management server.
>
> Still I am getting the above issue. I am not sure if i missed any
> configuration.
>
> Can somebody please help me with resolution of this issue?
> Appreciate your help here!!!
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <um...@gmail.com>>>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>> wrote:
>
> > Thanks a lot Sudha for your quick response.
> > I will setup the Marvin on local machine and get back in case if I face
> > any challenges in setup.
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> >
> > On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
> > sudha.ponnaganti@citrix.com<ma...@citrix.com>>>>>>>>> wrote:
> >
> >> Hi Umesh,
> >>
> >> Looks like you have started on right track - Marvin is the framework to
> >> use for functional or integration automation.
> >> There are sizable number of test cases exist and you can review them.
> >>  There are some wiki pages already written explaining Marvin [1]. Also
> best
> >> practices are published by community as well [2]. You can contribute to
> it
> >> as much as you can.
> >>
> >> Besides this, there is Junit framework (unit Test), Selenium framework
> >> (UI automation) which are not as popular as Marvin. Marvin is perfect
> for
> >> majority of the validation. You can use simulator as well with Marvin.
> >>
> >> Please do pursue these and post questions to the community if you run in
> >> to any issues in setting up env and running tests. There are jobs setup
> by
> >> various community members to test Master or current releases in various
> >> labs and can help answer questions.
> >>
> >> [1]
> >>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> >>
> >>
> >> Thanks
> >> /Sudha
> >>
> >>
> >> -----Original Message-----
> >> From: umesh kute [mailto:umeshvkute@gmail.com<ma...@gmail.com>>>>>>>]
> >> Sent: Saturday, December 07, 2013 10:29 PM
> >> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>
> >> Subject: Regarding cloudstack automation
> >>
> >> Hi All,
> >> Good morning !!!
> >> I am working as QA engineer and I am new to the cloudstack community.
> >> We have started using cloudstack and deployed it in our infrastructure.
> >>
> >> Can somebody please help me in identifying the good automation
> >> framework/tool/anything? The main intention is we want to automate the
> >> infrastructure validation related cases (for e.g. create/update/delete
> >> cases for instances, project, network, etc...)
> >>
> >> It would be good if you can help in identifying it.
> >>
> >> Please note: I have gone through cloudmonkey. But i haven't found much
> >> help on it. May be i need to search a bit more.. I am also going through
> >> the marvin and planning to setup it. If apart from these two, if anyone
> has
> >> different view please suggest.
> >>
> >> Also, if somebody has any pointers on cloudmonkey and marvin or any more
> >> info on this (like, if it would suffice the infrastructure validation
> >> related cases i mentioned above) any pros/cons would really be helpful
> for
> >> me...
> >>
> >> Appreciate any help on this and looking forward for the response on
> >> this!!!
> >>
> >> Thanks and Regards
> >> -- Umesh Kute
> >>
> >
> >
>
>

RE: Regarding cloudstack automation

[Santhosh Edukulla <sa...@citrix.com>]

Umesh,

1. There should not be any issues inherent inside of it as such not to run scripts atleast existing ones altogether. Now, compared to earlier mentioned failures viz., ssh,password, template etc ,these are mainly away from framework and are setup issues.

2. Component signifies regression cases, if you already know. Now for the run and failures count, mentioned below, can you let us know what are the failures or You can attach logs to elucidate the failures? Regression do run almost every day for various releases and has many passes and failures if any for product logged as bugs. The pass % for regression is more than 90% as far iam aware. The failures below, could be mainly due to infrastructure\setup specific or the way we may perceive it to run because of it few limitations.  

3. We can help you to setup and start running marvin. Are all cases for bvt running first and with no issues? Mention the host and infrastructure setup details and flow you are using.

4. Also, we have a topic branch created for marvin. If you see an issue anywhere, you can log a bug, submit a patch for review to fix the same there.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com]
Sent: Friday, January 24, 2014 8:04 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org; Chandan Purushothama; Sudha Ponnaganti; dev@cloudstack.apache.org
Subject: Re: Regarding cloudstack automation

Hi Santhosh,
To proceed further I deployed the template by disabling password and providing the default password as "password". Now its able to connect using ssh.

But when I started with the test case execution for the scripts which are there in "component folder", Out of 80 scripts, executed 11 and all 11 are failing (mentioned below).

test_affinity_groups.py
test_add_remove_network.py
test_accounts.py
test_allocation_states.py
test_baremetal.py
test_assign_vm.py
test_vm_passwdenabled.py
test_vpc_vm_life_cycle.py
test_vpc_routers.py
test_vpn_users.py
test_vpc_vms_deployment.py

Are there any issues with Marvin framework for running component script and is it executed before? I am facing many failures in a script.

If required I can share the logs.

Please note: We have a cloudstack 4.2 deployed in lab. We planned to use the Marvin to validate the cloudstack infrastructure. I have installed the marvin (0.1.0) and cloudstack using (4.2).

Thanks and Regards
-- Umesh Kute


On Sat, Jan 18, 2014 at 2:31 AM, Santhosh Edukulla <sa...@citrix.com>> wrote:
Umesh,

1. Its good that the template issue is resolved.

2. Regarding point 4 mentioned below, your understanding is right. The idea is during automation run for various test suites,  we use a template seeded into CS which has the password set with the one used in Services Class. So, in a way for all test suites having this password mentioned is assumed to be having an instance deployed with template matching our condition and so ssh works.

3. There are test cases pertaining explicitly to verify reset cases under CS, that covers scenarios to test, but for every ssh we dont use the password given by the API output.

4. So, for creating instances you can use a template with password as "password" for your testing, thats the easy solution i believe and all test suits has this password inside them, it will work. In a way, this not so a good design, but
We are planning to remove Services class test data from tests and separate it out as a test data, So for user running tests can alter the config to suit the template he has and all test suites using ssh works and will be configurable, compared to now we have to modify all test suites to get it working with custom password for user.

Thanks!
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>]
Sent: Friday, January 17, 2014 7:32 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Hi Santhosh,
Thanks again...
I tried the steps that you mentioned below. Fortunately i could able to proceed a bit further on this issue.

Now, instance got created successfully of type CentOS 6.4 (64-bit).

It is stuck in the ssh step.
Here is what happens...

1. All the steps/APIs till instance creation works fine (including listDomains, listZones, listOsTypes, listTemplates, createAccount, createServiceOffering, deployVirtualMachine, queryAsyncJobResult, associateIPAddress, createFirewallRules, createPortForwardingRule, createEgressFirewallRule)

2. When it tries to SSH to virtual machine it fails after timeout of 600s (20-retries, 30-intervals). Script is terminated.

3. I put some debug statements in function get_ssh_client() under: "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py"

The credentials i think it tries is :
self.ssh_ip: 207.x.x.x
self.ssh_port: 22
self.username: root
self.password: password
keyPairFileLocation: None

It means, it tries to connect to instance using password as password (it is provided in dictionary in test_vm_passwdenabled.py. Note: Earlier i gave references for test_loadbalance.py and its the same case).

4. In log, i found that the password that is returned in response to deployVirtualMachine API call is: xA2yeaxvb. (PFA file runinfo). When i tried to do ssh to the instance with same password it works and with dictionary "password" it doesn't. I think so.. please confirm...

Either, for ssh connection it should use the returned password or reset password before connection.

PFA all the logs.
Please correct if my understanding is correct or I am missing something here....

Please let me know if there is any resolution of this issue or if somebody encounters it before.

Thanks and Regards
-- Umesh Kute

On Tue, Jan 14, 2014 at 6:48 PM, Santhosh Edukulla <sa...@citrix.com>>> wrote:
Umesh,

Lets put steps so that we are in same page:

1. When we deploy  a VM, we use get_template function which basically retrieves the template information matching the description you provided under services class for ostype under test module EX: test_loadbalance.py.  I am surprised that you are receiving a "featured" and "builtin" template as windows template as output for this function. We are explicitly verifiying the template type as "BUILTIN" to retrieve the template information. So, a windows template cannot be a BUILTIN Template. Either it could be a bug in this function, or something with API. But, to double confirm, Can you please check whats the template information you are retrieving from this function matching with listTemplates API output( run either from your browser or script )  passing the same arguments as passed inside get_template?

Inside if we see, basically it gets the id matching with that ostype description using "listOsTypes"  and then use "listTemplates" command. So, this template is used to deploy the vm.  As far as i know, a builtin template cannot be a windows template?  Here, we use a featured and builtin template along with description filter passed. So, please check whether the template you are retrieving is windows or otherwise. Check for the field ostypename for the output you receive? Provide the output here for get_template copy pasted with dir(template) for return value?

2. To double confirm that it is template issue and not any other issue related to ssh like ( firewall\iptables\network connectivity issue) for ssh, please manually check for that particular ip in the test case whether ssh works or not and is not a windows machine?

3. Run one test case, first by adding a tag EX: "umesh" to the tags list as mentioned below for a particular test case under test module EX: test_loadbalance.py, then  run with nose command passing in tags argument mentioned below.

 @attr(tags = ["advanced", "advancedns", "smoke", "umesh"])
    def test_01_create_lb_rule_src_nat(self):

nosetests-2.7 -v --with-marvin --marvin-config=/root/softwares/cscode/setup/dev/advanced.cfg --load -a -w /root/softwares/cscode/test/integration/smoke/ -a tags=umesh

Let me know.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>]
Sent: Tuesday, January 14, 2014 7:02 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

I re-installed the marvin today to get the latest code.
I am again facing the same problem in get_template. It is returning the windows template and creating the windows VM. Hence when it tries to do SSH for VM, it fails.

I have also build the cloudstack to get the latest code for Marvin.

PFA the script logs and test_loadbalance script for reference.

Also, do let me know if I am missing some configuration or anything...

Just an FYI.. I have executed 35 scripts in smoke test directory. Out of 35 scripts executed, 17-PASS, 18-FAIL.
Around 50% failure are due to SSH related issue.

Thanks and Regards
-- Umesh Kute


On Fri, Jan 10, 2014 at 5:53 PM, Santhosh Edukulla <sa...@citrix.com>>>> wrote:
1. As such because of  bug in get_template, you are getting windows machine in your setup and then ssh is tried in test module, so you are getting the error.

2. Now, to overcome, just checkout the latest marvin, it should have a fix.

Note: It still has some other issues, but you can continue with your testing further. Let us know.

Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>]
Sent: Friday, January 10, 2014 5:19 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

So far i have found the failure on following scripts:
1. test_loadbalance
2. test_network
3. test_nic

In runinfo.txt log it is stuck at the step:
SSH into VM (IPaddress: 10.1.1.55) & NAT Rule (Public IP: 207.x.x.x)

PFA the Marvin logs for the test_loadbalance.py script.

I have modified the following entry in the script i.e. provided the correct template name which is present.
"ostype": "CentOS 6.4 (64-bit)",
#"ostype": "CentOS 5.3 (64-bit)",

Please let me know for your comments.

Thanks and Regards
-- Umesh Kute



On Fri, Jan 10, 2014 at 2:57 PM, Santhosh Edukulla <sa...@citrix.com>>>>> wrote:
You can log the bug for this. We have fixed few other issues along with this in a private branch. Will soon merge with ACS. If you need a temporary fix, let me know.

Question : Related to ssh issue, ssh to vm failing at which part? Can you add some information related to ssh failure which test module, which case etc? This may be related\unrelated to the above issue. We can check to see the issue is either same\different.

Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>]
Sent: Friday, January 10, 2014 4:21 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks a lot Santhosh For your response.

Sorry for delay.. But is there any workaround for this issue? Because as i mentioned, even if os type is provided as "ostype": 'CentOS 6.4 (64-bit)' it is picking up the first one in list i.e. Windows Server 2008 R2 Enterprise.
So some of the scripts which required to SSH into VM are failing.

Can I get the JIRA ID for this issue to track?

Thanks and Regards
-- Umesh Kute


On Fri, Jan 3, 2014 at 5:19 PM, Santhosh Edukulla <sa...@citrix.com>>>>>> wrote:
Umesh,

This could be probably due to the bug under get_template function under marvin/integration/lib/common.py. Though, the ostype description is used and corresponding id is retrieved.

But the later part, listTemplate API call returning the list and we are picking up either the template which is ready or matching with id we retrieved. This case is what could be causing the issue you mentioned.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>]
Sent: Friday, January 03, 2014 5:04 AM
To: Santhosh Edukulla; users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks for your help Santhosh!!!

You are right...
The public IP address range was exhausted. After cleaning up the resources, I was able to run the sample script "test_deploy_vm.py" successfully.

One question - i have provided the "ostype": 'CentOS 6.4 (64-bit)'. What is the use of this parameter?

When observed in management server logs and on cloudstack UI (while running script), VM was created of type: "Windows Server 2008 R2 Enterprise with SQL 2012 Web Edition". This is the first one in the list.

Does it choose the one which we provided in script or picks it from the template list that is returned as a result of response to listTemplate API call?

Thanks and Regards
-- Umesh Kute


On Thu, Jan 2, 2014 at 7:22 PM, Santhosh Edukulla <sa...@citrix.com>>>>>>> wrote:
Umesh,

1. It seems you have exhausted few of CloudStack Resources. These resources usage should show up on your cloudstack dashboard. Anything appears in Red are exhausted resources.

2. Few of the cases could be EX: Guest VM IPs\Management ip addresses  are exhausted,

3. Check for these resources in Red on your dashboard EX: http://localhost:8080/client/->Dashboard and clean up them or add new resources.


Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>]
Sent: Thursday, January 02, 2014 7:06 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thank you once again Santhosh & Chandan.

I have gone through the management server logs. The deployment of VM got fired to the setup correctly and there are couple of errors in the management-server log.
I am summarizing those below:

test data in "test_deploy_vm.py"
 def __init__(self):
        self.testdata = {
            #data to create an account
            "account": {
                "email": "test@test.com<ma...@test.com>>>>>>>",
                "firstname": "Test",
                "lastname": "User",
                "username": "test",
                "password": "password",
            },
            #data reqd for virtual machine creation
            "virtual_machine" : {
                "name" : "testvmshr",
                "displayname" : "Test VM shr",
            },
            #small service offering
            "service_offering": {
                "small": {
                    "name": "SOSmall",
                    "displaytext": "Small Instance",
                    "cpunumber": 1,
                    "cpuspeed": 2000,
                    "memory": 1024,
                },
            },
            "ostype": 'CentOS 6.4 (64-bit)',
        }


1. Account is successfully created
2. Service offering is successfully created
3. Management server logs - management-server.log has following error:


2014-01-02 01:43:40,693 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Lock is released for network Ntwk[326|Guest|15] as a part of network shutdown
2014-01-02 01:43:40,695 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Lock is released for network id 326 as a part of network implement
2014-01-02 01:43:40,695 INFO  [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Insufficient capacity
com.cloud.exception.InsufficientAddressCapacityException: Insufficient address capacityScope=interface com.cloud.dc.DataCenter; id=1
at com.cloud.network.NetworkManagerImpl.fetchNewPublicIp(NetworkManagerImpl.java:479)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.assignDedicateIpAddress(NetworkManagerImpl.java:613)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.assignSourceNatIpAddressToGuestNetwork(NetworkManagerImpl.java:582)
at com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:2013)
at com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1939)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2120)
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:887)
at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2014-01-02 01:43:40,703 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Cleaning up resources for the vm VM[User|testvmshr] in Starting state

4. When i checked the database for the network id 326 in table "networks", it has following entry:

| 326 | test-TestDeployVM-test_deploy_vm-QQ91N0-network | b7cb9e31-835f-47e3-9585-97e3b4084e4d | test-TestDeployVM-test_deploy_vm-QQ91N0-network | Guest        | Vlan                  | NULL          | 10.1.1.1       | 10.1.1.0/24<http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24>     | Dhcp   |                  15 |                 200 |              1 | ExternalGuestNetworkGuru | Destroy     |     326 |         1 |        305 | 8.8.8.8 | 8.8.4.4 | NULL      |          0 | Account  | cs131cloud.internal | ecf5b617-04da-469b-b378-f53e05d8cc53 | Isolated   |                0 | 2014-01-02 06:43:39 | 2014-01-02 06:43:46 |                 0 |   NULL | NULL        | NULL     | NULL         |               1 |           NULL |


Basically it tries to create a network offering (id=15) : "HA Isolated Network With Source Nat"


5. I think the script creates a network shown in above table: "test-TestDeployVM-test_deploy_vm-QQ91N0-network".

I am not sure why it still gives the Insufficient address capacityScope exception.

6. One more thing i observed. I have provided the "ostype": 'CentOS 6.4 (64-bit)'. But in DeployVMCmd it uses the template id: "03ffb96f-2cfa-11e3-a4f0-f245a5b3ba0f" which is for template "Windows Server 2008 R2 Enterprise with SQL 2012 Web Edition".


I am attaching the management-server logs and script logs for references.

If somebody can help me what's wrong here, would really be helpful.


Thanks and Regards
-- Umesh Kute


On Thu, Jan 2, 2014 at 2:59 PM, Santhosh Edukulla <sa...@citrix.com>>>>>>>> wrote:
1. Is it still failing post this registration?

2. If yes, may be you can verify\provide the management server logs.
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>>]
Sent: Thursday, January 02, 2014 4:16 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks Santhosh.
Yes, I have registered the following template which i am using.

"ostype": 'CentOS 6.4 (64-bit)',

Thanks and Regards
-- Umesh Kute


On Mon, Dec 30, 2013 at 5:50 PM, Santhosh Edukulla <
santhosh.edukulla@citrix.com<ma...@citrix.com>>>>>>>> wrote:

> Umesh,
>
> One question : Did you registered the template for ostype:     "ostype":
> 'CentOS 5.3 (64-bit)'?
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>>]
> Sent: Monday, December 30, 2013 6:32 AM
> To: Chandan Purushothama
> Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi Chandan,
> Thanks for your response.
> I have the latest Marvin repository (December 20th). I am able to proceed
> further. There was an issue of firewall for that machine and it got
> resolved.
>
> But now i am getting another error when i tried to run the script
> "test_deploy_vm.py"
>
> I have attached the log. Can somebody please have a look on it and help me
> in resolving the issue?
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> test_deploy_vm (integration.smoke.test_deploy_vm.TestDeployVM): CRITICAL:
> EXCEPTION: test_deploy_vm: Traceback (most recent call last):
>   File "/usr/local/lib/python2.7/unittest/case.py", line 327, in run
>     testMethod()
>   File
> "/DataDisk/temp/cloudstack/test/integration/smoke/test_deploy_vm.py", line
> 116, in test_deploy_vm
>     templateid=self.template.id<http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id>
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py",
> line 415, in create
>     virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> line 593, in deployVirtualMachine
>     response = self.connection.marvinRequest(command,
> response_type=response, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 280, in marvinRequest
>     response = self.poll(asyncJobId, response_type)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 86, in poll
>     "asyncquery", asyncResonse.jobresult)
> cloudstackAPIException: Execute cmd: asyncquery failed, due to: {errorcode
> : 533, errortext : u'Unable to create a deployment for VM[User|testvmshr]'}
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> PFA entire logs.
>
> Please let me know in case if anything is required.
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Sun, Dec 29, 2013 at 10:32 PM, Chandan Purushothama <
> Chandan.Purushothama@citrix.com<ma...@citrix.com>>>>>>>>>
> wrote:
>
> Hello Umesh,
>
> I had a similar experience with an older Marvin build. I updated mine to
> the latest and tried again and it worked. I recommend you to kindly try
> again with the latest Marvin build and see if you are able to work with the
> automation framework,
>
> Thank you,
> Chandan
>
>
> -------- Original message --------
> From: umesh kute
> Date:12/26/2013 12:29 AM (GMT-08:00)
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>,Sudha
> Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi All,
> I have created a Marvin setup on CentOS6.3 by following the document:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
>
> All the pre-requisites are installed successfully.
>
> I tried to run the sample script test_deploy_vm.py
> (cloudstack/test/integration/smoke/), I am getting following error:
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> [root@localhost smoke]# nosetests --with-marvin
> --marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg --load
> test_deploy_vm.py
>
>  Exception Occurred Under __deployDC :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
> Traceback (most recent call last):
>   File "/usr/local/bin/nosetests", line 9, in <module>
>     load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 118, in __init__
>     **extra_args)
>   File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
>     self.runTests()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 197, in runTests
>     result = self.testRunner.run(self.test)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 61, in run
>     test(result)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 45, in __call__
>     return self.run(*arg, **kwarg)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 138, in run
>     result.addError(self, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
> line 124, in addError
>     plugin_handled = plugins.handleError(self.test, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 99, in __call__
>     return self.call(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 167, in simple
>     result = meth(*arg, **kw)
>   File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
> line 155, in handleError
>     self.tcRunLogger.fatal("%s: %s: %s" %
> AttributeError: 'NoneType' object has no attribute 'fatal'
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> The logs are generated at /tmp and the log has following error.
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
> {'account': 'admin'}
> 2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
> http://10.88.91.100:8096/client/api :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Please note: I have opened the integration port 8096 on management server.
> Also, changed the global settings integration.api.port
> on cloudstack GUI to 8096 and restarted the management server.
>
> Still I am getting the above issue. I am not sure if i missed any
> configuration.
>
> Can somebody please help me with resolution of this issue?
> Appreciate your help here!!!
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <um...@gmail.com>>>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>>>> wrote:
>
> > Thanks a lot Sudha for your quick response.
> > I will setup the Marvin on local machine and get back in case if I face
> > any challenges in setup.
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> >
> > On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
> > sudha.ponnaganti@citrix.com<ma...@citrix.com>>>>>>>>> wrote:
> >
> >> Hi Umesh,
> >>
> >> Looks like you have started on right track - Marvin is the framework to
> >> use for functional or integration automation.
> >> There are sizable number of test cases exist and you can review them.
> >>  There are some wiki pages already written explaining Marvin [1]. Also
> best
> >> practices are published by community as well [2]. You can contribute to
> it
> >> as much as you can.
> >>
> >> Besides this, there is Junit framework (unit Test), Selenium framework
> >> (UI automation) which are not as popular as Marvin. Marvin is perfect
> for
> >> majority of the validation. You can use simulator as well with Marvin.
> >>
> >> Please do pursue these and post questions to the community if you run in
> >> to any issues in setting up env and running tests. There are jobs setup
> by
> >> various community members to test Master or current releases in various
> >> labs and can help answer questions.
> >>
> >> [1]
> >>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> >>
> >>
> >> Thanks
> >> /Sudha
> >>
> >>
> >> -----Original Message-----
> >> From: umesh kute [mailto:umeshvkute@gmail.com<ma...@gmail.com>>>>>>>]
> >> Sent: Saturday, December 07, 2013 10:29 PM
> >> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>>
> >> Subject: Regarding cloudstack automation
> >>
> >> Hi All,
> >> Good morning !!!
> >> I am working as QA engineer and I am new to the cloudstack community.
> >> We have started using cloudstack and deployed it in our infrastructure.
> >>
> >> Can somebody please help me in identifying the good automation
> >> framework/tool/anything? The main intention is we want to automate the
> >> infrastructure validation related cases (for e.g. create/update/delete
> >> cases for instances, project, network, etc...)
> >>
> >> It would be good if you can help in identifying it.
> >>
> >> Please note: I have gone through cloudmonkey. But i haven't found much
> >> help on it. May be i need to search a bit more.. I am also going through
> >> the marvin and planning to setup it. If apart from these two, if anyone
> has
> >> different view please suggest.
> >>
> >> Also, if somebody has any pointers on cloudmonkey and marvin or any more
> >> info on this (like, if it would suffice the infrastructure validation
> >> related cases i mentioned above) any pros/cons would really be helpful
> for
> >> me...
> >>
> >> Appreciate any help on this and looking forward for the response on
> >> this!!!
> >>
> >> Thanks and Regards
> >> -- Umesh Kute
> >>
> >
> >
>
>

Re: Regarding cloudstack automation

[umesh kute <um...@gmail.com>]

Hi Santhosh,
To proceed further I deployed the template by disabling password and
providing the default password as "password". Now its able to connect using
ssh.

But when I started with the test case execution for the scripts which are
there in "*component folder*", Out of 80 scripts, executed 11 and all 11
are failing (mentioned below).

test_affinity_groups.py
test_add_remove_network.py
test_accounts.py
test_allocation_states.py
test_baremetal.py
test_assign_vm.py
test_vm_passwdenabled.py
test_vpc_vm_life_cycle.py
test_vpc_routers.py
test_vpn_users.py
test_vpc_vms_deployment.py

Are there any issues with Marvin framework for running *component *script
and is it executed before? I am facing many failures in a script.

If required I can share the logs.

*Please note:* We have a cloudstack 4.2 deployed in lab. We planned to use
the Marvin to validate the cloudstack infrastructure. I have installed the
marvin (0.1.0) and cloudstack using (4.2).

Thanks and Regards
-- Umesh Kute


On Sat, Jan 18, 2014 at 2:31 AM, Santhosh Edukulla <
santhosh.edukulla@citrix.com> wrote:

> Umesh,
>
> 1. Its good that the template issue is resolved.
>
> 2. Regarding point 4 mentioned below, your understanding is right. The
> idea is during automation run for various test suites,  we use a template
> seeded into CS which has the password set with the one used in Services
> Class. So, in a way for all test suites having this password mentioned is
> assumed to be having an instance deployed with template matching our
> condition and so ssh works.
>
> 3. There are test cases pertaining explicitly to verify reset cases under
> CS, that covers scenarios to test, but for every ssh we dont use the
> password given by the API output.
>
> 4. So, for creating instances you can use a template with password as
> "password" for your testing, thats the easy solution i believe and all test
> suits has this password inside them, it will work. In a way, this not so a
> good design, but
> We are planning to remove Services class test data from tests and separate
> it out as a test data, So for user running tests can alter the config to
> suit the template he has and all test suites using ssh works and will be
> configurable, compared to now we have to modify all test suites to get it
> working with custom password for user.
>
> Thanks!
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com]
> Sent: Friday, January 17, 2014 7:32 AM
> To: Santhosh Edukulla
> Cc: users@cloudstack.apache.org; Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi Santhosh,
> Thanks again...
> I tried the steps that you mentioned below. Fortunately i could able to
> proceed a bit further on this issue.
>
> Now, instance got created successfully of type CentOS 6.4 (64-bit).
>
> It is stuck in the ssh step.
> Here is what happens...
>
> 1. All the steps/APIs till instance creation works fine (including
> listDomains, listZones, listOsTypes, listTemplates, createAccount,
> createServiceOffering, deployVirtualMachine, queryAsyncJobResult,
> associateIPAddress, createFirewallRules, createPortForwardingRule,
> createEgressFirewallRule)
>
> 2. When it tries to SSH to virtual machine it fails after timeout of 600s
> (20-retries, 30-intervals). Script is terminated.
>
> 3. I put some debug statements in function get_ssh_client() under:
> "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py"
>
> The credentials i think it tries is :
> self.ssh_ip: 207.x.x.x
> self.ssh_port: 22
> self.username: root
> self.password: password
> keyPairFileLocation: None
>
> It means, it tries to connect to instance using password as password (it
> is provided in dictionary in test_vm_passwdenabled.py. Note: Earlier i gave
> references for test_loadbalance.py and its the same case).
>
> 4. In log, i found that the password that is returned in response to
> deployVirtualMachine API call is: xA2yeaxvb. (PFA file runinfo). When i
> tried to do ssh to the instance with same password it works and with
> dictionary "password" it doesn't. I think so.. please confirm...
>
> Either, for ssh connection it should use the returned password or reset
> password before connection.
>
> PFA all the logs.
> Please correct if my understanding is correct or I am missing something
> here....
>
> Please let me know if there is any resolution of this issue or if somebody
> encounters it before.
>
> Thanks and Regards
> -- Umesh Kute
>
> On Tue, Jan 14, 2014 at 6:48 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com>> wrote:
> Umesh,
>
> Lets put steps so that we are in same page:
>
> 1. When we deploy  a VM, we use get_template function which basically
> retrieves the template information matching the description you provided
> under services class for ostype under test module EX: test_loadbalance.py.
>  I am surprised that you are receiving a "featured" and "builtin" template
> as windows template as output for this function. We are explicitly
> verifiying the template type as "BUILTIN" to retrieve the template
> information. So, a windows template cannot be a BUILTIN Template. Either it
> could be a bug in this function, or something with API. But, to double
> confirm, Can you please check whats the template information you are
> retrieving from this function matching with listTemplates API output( run
> either from your browser or script )  passing the same arguments as passed
> inside get_template?
>
> Inside if we see, basically it gets the id matching with that ostype
> description using "listOsTypes"  and then use "listTemplates" command. So,
> this template is used to deploy the vm.  As far as i know, a builtin
> template cannot be a windows template?  Here, we use a featured and builtin
> template along with description filter passed. So, please check whether the
> template you are retrieving is windows or otherwise. Check for the field
> ostypename for the output you receive? Provide the output here for
> get_template copy pasted with dir(template) for return value?
>
> 2. To double confirm that it is template issue and not any other issue
> related to ssh like ( firewall\iptables\network connectivity issue) for
> ssh, please manually check for that particular ip in the test case whether
> ssh works or not and is not a windows machine?
>
> 3. Run one test case, first by adding a tag EX: "umesh" to the tags list
> as mentioned below for a particular test case under test module EX:
> test_loadbalance.py, then  run with nose command passing in tags argument
> mentioned below.
>
>  @attr(tags = ["advanced", "advancedns", "smoke", "umesh"])
>     def test_01_create_lb_rule_src_nat(self):
>
> nosetests-2.7 -v --with-marvin
> --marvin-config=/root/softwares/cscode/setup/dev/advanced.cfg --load -a -w
> /root/softwares/cscode/test/integration/smoke/ -a tags=umesh
>
> Let me know.
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>]
> Sent: Tuesday, January 14, 2014 7:02 AM
> To: Santhosh Edukulla
> Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>;
> Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> I re-installed the marvin today to get the latest code.
> I am again facing the same problem in get_template. It is returning the
> windows template and creating the windows VM. Hence when it tries to do SSH
> for VM, it fails.
>
> I have also build the cloudstack to get the latest code for Marvin.
>
> PFA the script logs and test_loadbalance script for reference.
>
> Also, do let me know if I am missing some configuration or anything...
>
> Just an FYI.. I have executed 35 scripts in smoke test directory. Out of
> 35 scripts executed, 17-PASS, 18-FAIL.
> Around 50% failure are due to SSH related issue.
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Fri, Jan 10, 2014 at 5:53 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>>> wrote:
> 1. As such because of  bug in get_template, you are getting windows
> machine in your setup and then ssh is tried in test module, so you are
> getting the error.
>
> 2. Now, to overcome, just checkout the latest marvin, it should have a fix.
>
> Note: It still has some other issues, but you can continue with your
> testing further. Let us know.
>
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>>]
> Sent: Friday, January 10, 2014 5:19 AM
> To: Santhosh Edukulla
> Cc: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><ma...@cloudstack.apache.org>>;
> Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> So far i have found the failure on following scripts:
> 1. test_loadbalance
> 2. test_network
> 3. test_nic
>
> In runinfo.txt log it is stuck at the step:
> SSH into VM (IPaddress: 10.1.1.55) & NAT Rule (Public IP: 207.x.x.x)
>
> PFA the Marvin logs for the test_loadbalance.py script.
>
> I have modified the following entry in the script i.e. provided the
> correct template name which is present.
> "ostype": "CentOS 6.4 (64-bit)",
> #"ostype": "CentOS 5.3 (64-bit)",
>
> Please let me know for your comments.
>
> Thanks and Regards
> -- Umesh Kute
>
>
>
> On Fri, Jan 10, 2014 at 2:57 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>>>>
> wrote:
> You can log the bug for this. We have fixed few other issues along with
> this in a private branch. Will soon merge with ACS. If you need a temporary
> fix, let me know.
>
> Question : Related to ssh issue, ssh to vm failing at which part? Can you
> add some information related to ssh failure which test module, which case
> etc? This may be related\unrelated to the above issue. We can check to see
> the issue is either same\different.
>
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>]
> Sent: Friday, January 10, 2014 4:21 AM
> To: Santhosh Edukulla
> Cc: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><ma...@cloudstack.apache.org>>>;
> Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thanks a lot Santhosh For your response.
>
> Sorry for delay.. But is there any workaround for this issue? Because as i
> mentioned, even if os type is provided as "ostype": 'CentOS 6.4 (64-bit)'
> it is picking up the first one in list i.e. Windows Server 2008 R2
> Enterprise.
> So some of the scripts which required to SSH into VM are failing.
>
> Can I get the JIRA ID for this issue to track?
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Fri, Jan 3, 2014 at 5:19 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>>> wrote:
> Umesh,
>
> This could be probably due to the bug under get_template function under
> marvin/integration/lib/common.py. Though, the ostype description is used
> and corresponding id is retrieved.
>
> But the later part, listTemplate API call returning the list and we are
> picking up either the template which is ready or matching with id we
> retrieved. This case is what could be causing the issue you mentioned.
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>]
> Sent: Friday, January 03, 2014 5:04 AM
> To: Santhosh Edukulla; users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>
> Cc: Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thanks for your help Santhosh!!!
>
> You are right...
> The public IP address range was exhausted. After cleaning up the
> resources, I was able to run the sample script "test_deploy_vm.py"
> successfully.
>
> One question - i have provided the "ostype": 'CentOS 6.4 (64-bit)'. What
> is the use of this parameter?
>
> When observed in management server logs and on cloudstack UI (while
> running script), VM was created of type: "Windows Server 2008 R2 Enterprise
> with SQL 2012 Web Edition". This is the first one in the list.
>
> Does it choose the one which we provided in script or picks it from the
> template list that is returned as a result of response to listTemplate API
> call?
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Thu, Jan 2, 2014 at 7:22 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>>>>>>
> wrote:
> Umesh,
>
> 1. It seems you have exhausted few of CloudStack Resources. These
> resources usage should show up on your cloudstack dashboard. Anything
> appears in Red are exhausted resources.
>
> 2. Few of the cases could be EX: Guest VM IPs\Management ip addresses  are
> exhausted,
>
> 3. Check for these resources in Red on your dashboard EX:
> http://localhost:8080/client/->Dashboard and clean up them or add new
> resources.
>
>
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>]
> Sent: Thursday, January 02, 2014 7:06 AM
> To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>>
> Cc: Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thank you once again Santhosh & Chandan.
>
> I have gone through the management server logs. The deployment of VM got
> fired to the setup correctly and there are couple of errors in the
> management-server log.
> I am summarizing those below:
>
> test data in "test_deploy_vm.py"
>  def __init__(self):
>         self.testdata = {
>             #data to create an account
>             "account": {
>                 "email": "test@test.com<ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>>>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>>>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>>>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>>>>>>",
>                 "firstname": "Test",
>                 "lastname": "User",
>                 "username": "test",
>                 "password": "password",
>             },
>             #data reqd for virtual machine creation
>             "virtual_machine" : {
>                 "name" : "testvmshr",
>                 "displayname" : "Test VM shr",
>             },
>             #small service offering
>             "service_offering": {
>                 "small": {
>                     "name": "SOSmall",
>                     "displaytext": "Small Instance",
>                     "cpunumber": 1,
>                     "cpuspeed": 2000,
>                     "memory": 1024,
>                 },
>             },
>             "ostype": 'CentOS 6.4 (64-bit)',
>         }
>
>
> 1. Account is successfully created
> 2. Service offering is successfully created
> 3. Management server logs - management-server.log has following error:
>
>
> 2014-01-02 01:43:40,693 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Lock is released for network Ntwk[326|Guest|15] as a part of network
> shutdown
> 2014-01-02 01:43:40,695 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Lock is released for network id 326 as a part of network implement
> 2014-01-02 01:43:40,695 INFO  [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Insufficient capacity
> com.cloud.exception.InsufficientAddressCapacityException: Insufficient
> address capacityScope=interface com.cloud.dc.DataCenter; id=1
> at
> com.cloud.network.NetworkManagerImpl.fetchNewPublicIp(NetworkManagerImpl.java:479)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.network.NetworkManagerImpl.assignDedicateIpAddress(NetworkManagerImpl.java:613)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.network.NetworkManagerImpl.assignSourceNatIpAddressToGuestNetwork(NetworkManagerImpl.java:582)
> at
> com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:2013)
> at
> com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1939)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2120)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:887)
> at
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:679)
> 2014-01-02 01:43:40,703 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Cleaning up resources for the vm VM[User|testvmshr] in Starting state
>
> 4. When i checked the database for the network id 326 in table "networks",
> it has following entry:
>
> | 326 | test-TestDeployVM-test_deploy_vm-QQ91N0-network |
> b7cb9e31-835f-47e3-9585-97e3b4084e4d |
> test-TestDeployVM-test_deploy_vm-QQ91N0-network | Guest        | Vlan
>            | NULL          | 10.1.1.1       | 10.1.1.0/24<
> http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><
> http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24>     | Dhcp
> |                  15 |                 200 |              1 |
> ExternalGuestNetworkGuru | Destroy     |     326 |         1 |        305 |
> 8.8.8.8 | 8.8.4.4 | NULL      |          0 | Account  | cs131cloud.internal
> | ecf5b617-04da-469b-b378-f53e05d8cc53 | Isolated   |                0 |
> 2014-01-02 06:43:39 | 2014-01-02 06:43:46 |                 0 |   NULL |
> NULL        | NULL     | NULL         |               1 |           NULL |
>
>
> Basically it tries to create a network offering (id=15) : "HA Isolated
> Network With Source Nat"
>
>
> 5. I think the script creates a network shown in above table:
> "test-TestDeployVM-test_deploy_vm-QQ91N0-network".
>
> I am not sure why it still gives the Insufficient address capacityScope
> exception.
>
> 6. One more thing i observed. I have provided the "ostype": 'CentOS 6.4
> (64-bit)'. But in DeployVMCmd it uses the template id:
> "03ffb96f-2cfa-11e3-a4f0-f245a5b3ba0f" which is for template "Windows
> Server 2008 R2 Enterprise with SQL 2012 Web Edition".
>
>
> I am attaching the management-server logs and script logs for references.
>
> If somebody can help me what's wrong here, would really be helpful.
>
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Thu, Jan 2, 2014 at 2:59 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>>>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>>>>> wrote:
> 1. Is it still failing post this registration?
>
> 2. If yes, may be you can verify\provide the management server logs.
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>]
> Sent: Thursday, January 02, 2014 4:16 AM
> To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>>
> Cc: Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thanks Santhosh.
> Yes, I have registered the following template which i am using.
>
> "ostype": 'CentOS 6.4 (64-bit)',
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Mon, Dec 30, 2013 at 5:50 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>>>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>>>>> wrote:
>
> > Umesh,
> >
> > One question : Did you registered the template for ostype:     "ostype":
> > 'CentOS 5.3 (64-bit)'?
> >
> > Regards,
> > Santhosh
> > ________________________________________
> > From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>]
> > Sent: Monday, December 30, 2013 6:32 AM
> > To: Chandan Purushothama
> > Cc: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>>; Sudha Ponnaganti
> > Subject: Re: Regarding cloudstack automation
> >
> > Hi Chandan,
> > Thanks for your response.
> > I have the latest Marvin repository (December 20th). I am able to proceed
> > further. There was an issue of firewall for that machine and it got
> > resolved.
> >
> > But now i am getting another error when i tried to run the script
> > "test_deploy_vm.py"
> >
> > I have attached the log. Can somebody please have a look on it and help
> me
> > in resolving the issue?
> >
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > test_deploy_vm (integration.smoke.test_deploy_vm.TestDeployVM): CRITICAL:
> > EXCEPTION: test_deploy_vm: Traceback (most recent call last):
> >   File "/usr/local/lib/python2.7/unittest/case.py", line 327, in run
> >     testMethod()
> >   File
> > "/DataDisk/temp/cloudstack/test/integration/smoke/test_deploy_vm.py",
> line
> > 116, in test_deploy_vm
> >     templateid=self.template.id<http://self.template.id><
> http://self.template.id><http://self.template.id><http://self.template.id
> ><http://self.template.id><http://self.template.id><
> http://self.template.id>
> >   File
> > "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py",
> > line 415, in create
> >     virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> > line 593, in deployVirtualMachine
> >     response = self.connection.marvinRequest(command,
> > response_type=response, method=method)
> >   File
> > "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> > line 280, in marvinRequest
> >     response = self.poll(asyncJobId, response_type)
> >   File
> > "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> > line 86, in poll
> >     "asyncquery", asyncResonse.jobresult)
> > cloudstackAPIException: Execute cmd: asyncquery failed, due to:
> {errorcode
> > : 533, errortext : u'Unable to create a deployment for
> VM[User|testvmshr]'}
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > PFA entire logs.
> >
> > Please let me know in case if anything is required.
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> > On Sun, Dec 29, 2013 at 10:32 PM, Chandan Purushothama <
> > Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>>>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>>>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>>>>>>
> > wrote:
> >
> > Hello Umesh,
> >
> > I had a similar experience with an older Marvin build. I updated mine to
> > the latest and tried again and it worked. I recommend you to kindly try
> > again with the latest Marvin build and see if you are able to work with
> the
> > automation framework,
> >
> > Thank you,
> > Chandan
> >
> >
> > -------- Original message --------
> > From: umesh kute
> > Date:12/26/2013 12:29 AM (GMT-08:00)
> > To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>>>>,Sudha
> > Ponnaganti
> > Subject: Re: Regarding cloudstack automation
> >
> > Hi All,
> > I have created a Marvin setup on CentOS6.3 by following the document:
> >
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> >
> > All the pre-requisites are installed successfully.
> >
> > I tried to run the sample script test_deploy_vm.py
> > (cloudstack/test/integration/smoke/), I am getting following error:
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > [root@localhost smoke]# nosetests --with-marvin
> > --marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg
> --load
> > test_deploy_vm.py
> >
> >  Exception Occurred Under __deployDC :
> > HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> > with url: /client/api?account=admin&command=listUsers&response=json
> (Caused
> > by <class 'socket.error'>: [Errno 110] Connection timed out)
> > Traceback (most recent call last):
> >   File "/usr/local/bin/nosetests", line 9, in <module>
> >     load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> > line 118, in __init__
> >     **extra_args)
> >   File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
> >     self.runTests()
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> > line 197, in runTests
> >     result = self.testRunner.run(self.test)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> > line 61, in run
> >     test(result)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> > line 45, in __call__
> >     return self.run(*arg, **kwarg)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> > line 138, in run
> >     result.addError(self, err)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
> > line 124, in addError
> >     plugin_handled = plugins.handleError(self.test, err)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> > line 99, in __call__
> >     return self.call(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> > line 167, in simple
> >     result = meth(*arg, **kw)
> >   File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
> > line 155, in handleError
> >     self.tcRunLogger.fatal("%s: %s: %s" %
> > AttributeError: 'NoneType' object has no attribute 'fatal'
> >
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > The logs are generated at /tmp and the log has following error.
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > 2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
> > {'account': 'admin'}
> > 2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
> > http://10.88.91.100:8096/client/api :
> > HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> > with url: /client/api?account=admin&command=listUsers&response=json
> (Caused
> > by <class 'socket.error'>: [Errno 110] Connection timed out)
> >
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > Please note: I have opened the integration port 8096 on management
> server.
> > Also, changed the global settings integration.api.port
> > on cloudstack GUI to 8096 and restarted the management server.
> >
> > Still I am getting the above issue. I am not sure if i missed any
> > configuration.
> >
> > Can somebody please help me with resolution of this issue?
> > Appreciate your help here!!!
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> > On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>>><mailto:
> > umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>>> wrote:
> >
> > > Thanks a lot Sudha for your quick response.
> > > I will setup the Marvin on local machine and get back in case if I face
> > > any challenges in setup.
> > >
> > > Thanks and Regards
> > > -- Umesh Kute
> > >
> > >
> > >
> > > On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
> > > sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>>><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>>>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>>>>>>>
> wrote:
> > >
> > >> Hi Umesh,
> > >>
> > >> Looks like you have started on right track - Marvin is the framework
> to
> > >> use for functional or integration automation.
> > >> There are sizable number of test cases exist and you can review them.
> > >>  There are some wiki pages already written explaining Marvin [1]. Also
> > best
> > >> practices are published by community as well [2]. You can contribute
> to
> > it
> > >> as much as you can.
> > >>
> > >> Besides this, there is Junit framework (unit Test), Selenium framework
> > >> (UI automation) which are not as popular as Marvin. Marvin is perfect
> > for
> > >> majority of the validation. You can use simulator as well with Marvin.
> > >>
> > >> Please do pursue these and post questions to the community if you run
> in
> > >> to any issues in setting up env and running tests. There are jobs
> setup
> > by
> > >> various community members to test Master or current releases in
> various
> > >> labs and can help answer questions.
> > >>
> > >> [1]
> > >>
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> > >>
> > >>
> > >> Thanks
> > >> /Sudha
> > >>
> > >>
> > >> -----Original Message-----
> > >> From: umesh kute [mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>>>]
> > >> Sent: Saturday, December 07, 2013 10:29 PM
> > >> To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>
> > >> Subject: Regarding cloudstack automation
> > >>
> > >> Hi All,
> > >> Good morning !!!
> > >> I am working as QA engineer and I am new to the cloudstack community.
> > >> We have started using cloudstack and deployed it in our
> infrastructure.
> > >>
> > >> Can somebody please help me in identifying the good automation
> > >> framework/tool/anything? The main intention is we want to automate the
> > >> infrastructure validation related cases (for e.g. create/update/delete
> > >> cases for instances, project, network, etc...)
> > >>
> > >> It would be good if you can help in identifying it.
> > >>
> > >> Please note: I have gone through cloudmonkey. But i haven't found much
> > >> help on it. May be i need to search a bit more.. I am also going
> through
> > >> the marvin and planning to setup it. If apart from these two, if
> anyone
> > has
> > >> different view please suggest.
> > >>
> > >> Also, if somebody has any pointers on cloudmonkey and marvin or any
> more
> > >> info on this (like, if it would suffice the infrastructure validation
> > >> related cases i mentioned above) any pros/cons would really be helpful
> > for
> > >> me...
> > >>
> > >> Appreciate any help on this and looking forward for the response on
> > >> this!!!
> > >>
> > >> Thanks and Regards
> > >> -- Umesh Kute
> > >>
> > >
> > >
> >
> >
>
>
>
>

Re: Regarding cloudstack automation

[umesh kute <um...@gmail.com>]

Hi Santhosh,
To proceed further I deployed the template by disabling password and
providing the default password as "password". Now its able to connect using
ssh.

But when I started with the test case execution for the scripts which are
there in "*component folder*", Out of 80 scripts, executed 11 and all 11
are failing (mentioned below).

test_affinity_groups.py
test_add_remove_network.py
test_accounts.py
test_allocation_states.py
test_baremetal.py
test_assign_vm.py
test_vm_passwdenabled.py
test_vpc_vm_life_cycle.py
test_vpc_routers.py
test_vpn_users.py
test_vpc_vms_deployment.py

Are there any issues with Marvin framework for running *component *script
and is it executed before? I am facing many failures in a script.

If required I can share the logs.

*Please note:* We have a cloudstack 4.2 deployed in lab. We planned to use
the Marvin to validate the cloudstack infrastructure. I have installed the
marvin (0.1.0) and cloudstack using (4.2).

Thanks and Regards
-- Umesh Kute


On Sat, Jan 18, 2014 at 2:31 AM, Santhosh Edukulla <
santhosh.edukulla@citrix.com> wrote:

> Umesh,
>
> 1. Its good that the template issue is resolved.
>
> 2. Regarding point 4 mentioned below, your understanding is right. The
> idea is during automation run for various test suites,  we use a template
> seeded into CS which has the password set with the one used in Services
> Class. So, in a way for all test suites having this password mentioned is
> assumed to be having an instance deployed with template matching our
> condition and so ssh works.
>
> 3. There are test cases pertaining explicitly to verify reset cases under
> CS, that covers scenarios to test, but for every ssh we dont use the
> password given by the API output.
>
> 4. So, for creating instances you can use a template with password as
> "password" for your testing, thats the easy solution i believe and all test
> suits has this password inside them, it will work. In a way, this not so a
> good design, but
> We are planning to remove Services class test data from tests and separate
> it out as a test data, So for user running tests can alter the config to
> suit the template he has and all test suites using ssh works and will be
> configurable, compared to now we have to modify all test suites to get it
> working with custom password for user.
>
> Thanks!
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com]
> Sent: Friday, January 17, 2014 7:32 AM
> To: Santhosh Edukulla
> Cc: users@cloudstack.apache.org; Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi Santhosh,
> Thanks again...
> I tried the steps that you mentioned below. Fortunately i could able to
> proceed a bit further on this issue.
>
> Now, instance got created successfully of type CentOS 6.4 (64-bit).
>
> It is stuck in the ssh step.
> Here is what happens...
>
> 1. All the steps/APIs till instance creation works fine (including
> listDomains, listZones, listOsTypes, listTemplates, createAccount,
> createServiceOffering, deployVirtualMachine, queryAsyncJobResult,
> associateIPAddress, createFirewallRules, createPortForwardingRule,
> createEgressFirewallRule)
>
> 2. When it tries to SSH to virtual machine it fails after timeout of 600s
> (20-retries, 30-intervals). Script is terminated.
>
> 3. I put some debug statements in function get_ssh_client() under:
> "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py"
>
> The credentials i think it tries is :
> self.ssh_ip: 207.x.x.x
> self.ssh_port: 22
> self.username: root
> self.password: password
> keyPairFileLocation: None
>
> It means, it tries to connect to instance using password as password (it
> is provided in dictionary in test_vm_passwdenabled.py. Note: Earlier i gave
> references for test_loadbalance.py and its the same case).
>
> 4. In log, i found that the password that is returned in response to
> deployVirtualMachine API call is: xA2yeaxvb. (PFA file runinfo). When i
> tried to do ssh to the instance with same password it works and with
> dictionary "password" it doesn't. I think so.. please confirm...
>
> Either, for ssh connection it should use the returned password or reset
> password before connection.
>
> PFA all the logs.
> Please correct if my understanding is correct or I am missing something
> here....
>
> Please let me know if there is any resolution of this issue or if somebody
> encounters it before.
>
> Thanks and Regards
> -- Umesh Kute
>
> On Tue, Jan 14, 2014 at 6:48 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com>> wrote:
> Umesh,
>
> Lets put steps so that we are in same page:
>
> 1. When we deploy  a VM, we use get_template function which basically
> retrieves the template information matching the description you provided
> under services class for ostype under test module EX: test_loadbalance.py.
>  I am surprised that you are receiving a "featured" and "builtin" template
> as windows template as output for this function. We are explicitly
> verifiying the template type as "BUILTIN" to retrieve the template
> information. So, a windows template cannot be a BUILTIN Template. Either it
> could be a bug in this function, or something with API. But, to double
> confirm, Can you please check whats the template information you are
> retrieving from this function matching with listTemplates API output( run
> either from your browser or script )  passing the same arguments as passed
> inside get_template?
>
> Inside if we see, basically it gets the id matching with that ostype
> description using "listOsTypes"  and then use "listTemplates" command. So,
> this template is used to deploy the vm.  As far as i know, a builtin
> template cannot be a windows template?  Here, we use a featured and builtin
> template along with description filter passed. So, please check whether the
> template you are retrieving is windows or otherwise. Check for the field
> ostypename for the output you receive? Provide the output here for
> get_template copy pasted with dir(template) for return value?
>
> 2. To double confirm that it is template issue and not any other issue
> related to ssh like ( firewall\iptables\network connectivity issue) for
> ssh, please manually check for that particular ip in the test case whether
> ssh works or not and is not a windows machine?
>
> 3. Run one test case, first by adding a tag EX: "umesh" to the tags list
> as mentioned below for a particular test case under test module EX:
> test_loadbalance.py, then  run with nose command passing in tags argument
> mentioned below.
>
>  @attr(tags = ["advanced", "advancedns", "smoke", "umesh"])
>     def test_01_create_lb_rule_src_nat(self):
>
> nosetests-2.7 -v --with-marvin
> --marvin-config=/root/softwares/cscode/setup/dev/advanced.cfg --load -a -w
> /root/softwares/cscode/test/integration/smoke/ -a tags=umesh
>
> Let me know.
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>]
> Sent: Tuesday, January 14, 2014 7:02 AM
> To: Santhosh Edukulla
> Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>;
> Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> I re-installed the marvin today to get the latest code.
> I am again facing the same problem in get_template. It is returning the
> windows template and creating the windows VM. Hence when it tries to do SSH
> for VM, it fails.
>
> I have also build the cloudstack to get the latest code for Marvin.
>
> PFA the script logs and test_loadbalance script for reference.
>
> Also, do let me know if I am missing some configuration or anything...
>
> Just an FYI.. I have executed 35 scripts in smoke test directory. Out of
> 35 scripts executed, 17-PASS, 18-FAIL.
> Around 50% failure are due to SSH related issue.
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Fri, Jan 10, 2014 at 5:53 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>>> wrote:
> 1. As such because of  bug in get_template, you are getting windows
> machine in your setup and then ssh is tried in test module, so you are
> getting the error.
>
> 2. Now, to overcome, just checkout the latest marvin, it should have a fix.
>
> Note: It still has some other issues, but you can continue with your
> testing further. Let us know.
>
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>>]
> Sent: Friday, January 10, 2014 5:19 AM
> To: Santhosh Edukulla
> Cc: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><ma...@cloudstack.apache.org>>;
> Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> So far i have found the failure on following scripts:
> 1. test_loadbalance
> 2. test_network
> 3. test_nic
>
> In runinfo.txt log it is stuck at the step:
> SSH into VM (IPaddress: 10.1.1.55) & NAT Rule (Public IP: 207.x.x.x)
>
> PFA the Marvin logs for the test_loadbalance.py script.
>
> I have modified the following entry in the script i.e. provided the
> correct template name which is present.
> "ostype": "CentOS 6.4 (64-bit)",
> #"ostype": "CentOS 5.3 (64-bit)",
>
> Please let me know for your comments.
>
> Thanks and Regards
> -- Umesh Kute
>
>
>
> On Fri, Jan 10, 2014 at 2:57 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>>>>
> wrote:
> You can log the bug for this. We have fixed few other issues along with
> this in a private branch. Will soon merge with ACS. If you need a temporary
> fix, let me know.
>
> Question : Related to ssh issue, ssh to vm failing at which part? Can you
> add some information related to ssh failure which test module, which case
> etc? This may be related\unrelated to the above issue. We can check to see
> the issue is either same\different.
>
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>]
> Sent: Friday, January 10, 2014 4:21 AM
> To: Santhosh Edukulla
> Cc: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><ma...@cloudstack.apache.org>>>;
> Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thanks a lot Santhosh For your response.
>
> Sorry for delay.. But is there any workaround for this issue? Because as i
> mentioned, even if os type is provided as "ostype": 'CentOS 6.4 (64-bit)'
> it is picking up the first one in list i.e. Windows Server 2008 R2
> Enterprise.
> So some of the scripts which required to SSH into VM are failing.
>
> Can I get the JIRA ID for this issue to track?
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Fri, Jan 3, 2014 at 5:19 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>>> wrote:
> Umesh,
>
> This could be probably due to the bug under get_template function under
> marvin/integration/lib/common.py. Though, the ostype description is used
> and corresponding id is retrieved.
>
> But the later part, listTemplate API call returning the list and we are
> picking up either the template which is ready or matching with id we
> retrieved. This case is what could be causing the issue you mentioned.
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>]
> Sent: Friday, January 03, 2014 5:04 AM
> To: Santhosh Edukulla; users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>
> Cc: Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thanks for your help Santhosh!!!
>
> You are right...
> The public IP address range was exhausted. After cleaning up the
> resources, I was able to run the sample script "test_deploy_vm.py"
> successfully.
>
> One question - i have provided the "ostype": 'CentOS 6.4 (64-bit)'. What
> is the use of this parameter?
>
> When observed in management server logs and on cloudstack UI (while
> running script), VM was created of type: "Windows Server 2008 R2 Enterprise
> with SQL 2012 Web Edition". This is the first one in the list.
>
> Does it choose the one which we provided in script or picks it from the
> template list that is returned as a result of response to listTemplate API
> call?
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Thu, Jan 2, 2014 at 7:22 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>>>>>>
> wrote:
> Umesh,
>
> 1. It seems you have exhausted few of CloudStack Resources. These
> resources usage should show up on your cloudstack dashboard. Anything
> appears in Red are exhausted resources.
>
> 2. Few of the cases could be EX: Guest VM IPs\Management ip addresses  are
> exhausted,
>
> 3. Check for these resources in Red on your dashboard EX:
> http://localhost:8080/client/->Dashboard and clean up them or add new
> resources.
>
>
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>]
> Sent: Thursday, January 02, 2014 7:06 AM
> To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>>
> Cc: Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thank you once again Santhosh & Chandan.
>
> I have gone through the management server logs. The deployment of VM got
> fired to the setup correctly and there are couple of errors in the
> management-server log.
> I am summarizing those below:
>
> test data in "test_deploy_vm.py"
>  def __init__(self):
>         self.testdata = {
>             #data to create an account
>             "account": {
>                 "email": "test@test.com<ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>>>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>>>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>>>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>>>>>>",
>                 "firstname": "Test",
>                 "lastname": "User",
>                 "username": "test",
>                 "password": "password",
>             },
>             #data reqd for virtual machine creation
>             "virtual_machine" : {
>                 "name" : "testvmshr",
>                 "displayname" : "Test VM shr",
>             },
>             #small service offering
>             "service_offering": {
>                 "small": {
>                     "name": "SOSmall",
>                     "displaytext": "Small Instance",
>                     "cpunumber": 1,
>                     "cpuspeed": 2000,
>                     "memory": 1024,
>                 },
>             },
>             "ostype": 'CentOS 6.4 (64-bit)',
>         }
>
>
> 1. Account is successfully created
> 2. Service offering is successfully created
> 3. Management server logs - management-server.log has following error:
>
>
> 2014-01-02 01:43:40,693 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Lock is released for network Ntwk[326|Guest|15] as a part of network
> shutdown
> 2014-01-02 01:43:40,695 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Lock is released for network id 326 as a part of network implement
> 2014-01-02 01:43:40,695 INFO  [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Insufficient capacity
> com.cloud.exception.InsufficientAddressCapacityException: Insufficient
> address capacityScope=interface com.cloud.dc.DataCenter; id=1
> at
> com.cloud.network.NetworkManagerImpl.fetchNewPublicIp(NetworkManagerImpl.java:479)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.network.NetworkManagerImpl.assignDedicateIpAddress(NetworkManagerImpl.java:613)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.network.NetworkManagerImpl.assignSourceNatIpAddressToGuestNetwork(NetworkManagerImpl.java:582)
> at
> com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:2013)
> at
> com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1939)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2120)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:887)
> at
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:679)
> 2014-01-02 01:43:40,703 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Cleaning up resources for the vm VM[User|testvmshr] in Starting state
>
> 4. When i checked the database for the network id 326 in table "networks",
> it has following entry:
>
> | 326 | test-TestDeployVM-test_deploy_vm-QQ91N0-network |
> b7cb9e31-835f-47e3-9585-97e3b4084e4d |
> test-TestDeployVM-test_deploy_vm-QQ91N0-network | Guest        | Vlan
>            | NULL          | 10.1.1.1       | 10.1.1.0/24<
> http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><
> http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24>     | Dhcp
> |                  15 |                 200 |              1 |
> ExternalGuestNetworkGuru | Destroy     |     326 |         1 |        305 |
> 8.8.8.8 | 8.8.4.4 | NULL      |          0 | Account  | cs131cloud.internal
> | ecf5b617-04da-469b-b378-f53e05d8cc53 | Isolated   |                0 |
> 2014-01-02 06:43:39 | 2014-01-02 06:43:46 |                 0 |   NULL |
> NULL        | NULL     | NULL         |               1 |           NULL |
>
>
> Basically it tries to create a network offering (id=15) : "HA Isolated
> Network With Source Nat"
>
>
> 5. I think the script creates a network shown in above table:
> "test-TestDeployVM-test_deploy_vm-QQ91N0-network".
>
> I am not sure why it still gives the Insufficient address capacityScope
> exception.
>
> 6. One more thing i observed. I have provided the "ostype": 'CentOS 6.4
> (64-bit)'. But in DeployVMCmd it uses the template id:
> "03ffb96f-2cfa-11e3-a4f0-f245a5b3ba0f" which is for template "Windows
> Server 2008 R2 Enterprise with SQL 2012 Web Edition".
>
>
> I am attaching the management-server logs and script logs for references.
>
> If somebody can help me what's wrong here, would really be helpful.
>
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Thu, Jan 2, 2014 at 2:59 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>>>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>>>>> wrote:
> 1. Is it still failing post this registration?
>
> 2. If yes, may be you can verify\provide the management server logs.
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>]
> Sent: Thursday, January 02, 2014 4:16 AM
> To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>>
> Cc: Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thanks Santhosh.
> Yes, I have registered the following template which i am using.
>
> "ostype": 'CentOS 6.4 (64-bit)',
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Mon, Dec 30, 2013 at 5:50 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>>>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>>>>> wrote:
>
> > Umesh,
> >
> > One question : Did you registered the template for ostype:     "ostype":
> > 'CentOS 5.3 (64-bit)'?
> >
> > Regards,
> > Santhosh
> > ________________________________________
> > From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>]
> > Sent: Monday, December 30, 2013 6:32 AM
> > To: Chandan Purushothama
> > Cc: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>>; Sudha Ponnaganti
> > Subject: Re: Regarding cloudstack automation
> >
> > Hi Chandan,
> > Thanks for your response.
> > I have the latest Marvin repository (December 20th). I am able to proceed
> > further. There was an issue of firewall for that machine and it got
> > resolved.
> >
> > But now i am getting another error when i tried to run the script
> > "test_deploy_vm.py"
> >
> > I have attached the log. Can somebody please have a look on it and help
> me
> > in resolving the issue?
> >
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > test_deploy_vm (integration.smoke.test_deploy_vm.TestDeployVM): CRITICAL:
> > EXCEPTION: test_deploy_vm: Traceback (most recent call last):
> >   File "/usr/local/lib/python2.7/unittest/case.py", line 327, in run
> >     testMethod()
> >   File
> > "/DataDisk/temp/cloudstack/test/integration/smoke/test_deploy_vm.py",
> line
> > 116, in test_deploy_vm
> >     templateid=self.template.id<http://self.template.id><
> http://self.template.id><http://self.template.id><http://self.template.id
> ><http://self.template.id><http://self.template.id><
> http://self.template.id>
> >   File
> > "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py",
> > line 415, in create
> >     virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> > line 593, in deployVirtualMachine
> >     response = self.connection.marvinRequest(command,
> > response_type=response, method=method)
> >   File
> > "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> > line 280, in marvinRequest
> >     response = self.poll(asyncJobId, response_type)
> >   File
> > "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> > line 86, in poll
> >     "asyncquery", asyncResonse.jobresult)
> > cloudstackAPIException: Execute cmd: asyncquery failed, due to:
> {errorcode
> > : 533, errortext : u'Unable to create a deployment for
> VM[User|testvmshr]'}
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > PFA entire logs.
> >
> > Please let me know in case if anything is required.
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> > On Sun, Dec 29, 2013 at 10:32 PM, Chandan Purushothama <
> > Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>>>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>>>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>>>>>>
> > wrote:
> >
> > Hello Umesh,
> >
> > I had a similar experience with an older Marvin build. I updated mine to
> > the latest and tried again and it worked. I recommend you to kindly try
> > again with the latest Marvin build and see if you are able to work with
> the
> > automation framework,
> >
> > Thank you,
> > Chandan
> >
> >
> > -------- Original message --------
> > From: umesh kute
> > Date:12/26/2013 12:29 AM (GMT-08:00)
> > To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>>>>,Sudha
> > Ponnaganti
> > Subject: Re: Regarding cloudstack automation
> >
> > Hi All,
> > I have created a Marvin setup on CentOS6.3 by following the document:
> >
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> >
> > All the pre-requisites are installed successfully.
> >
> > I tried to run the sample script test_deploy_vm.py
> > (cloudstack/test/integration/smoke/), I am getting following error:
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > [root@localhost smoke]# nosetests --with-marvin
> > --marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg
> --load
> > test_deploy_vm.py
> >
> >  Exception Occurred Under __deployDC :
> > HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> > with url: /client/api?account=admin&command=listUsers&response=json
> (Caused
> > by <class 'socket.error'>: [Errno 110] Connection timed out)
> > Traceback (most recent call last):
> >   File "/usr/local/bin/nosetests", line 9, in <module>
> >     load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> > line 118, in __init__
> >     **extra_args)
> >   File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
> >     self.runTests()
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> > line 197, in runTests
> >     result = self.testRunner.run(self.test)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> > line 61, in run
> >     test(result)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> > line 45, in __call__
> >     return self.run(*arg, **kwarg)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> > line 138, in run
> >     result.addError(self, err)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
> > line 124, in addError
> >     plugin_handled = plugins.handleError(self.test, err)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> > line 99, in __call__
> >     return self.call(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> > line 167, in simple
> >     result = meth(*arg, **kw)
> >   File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
> > line 155, in handleError
> >     self.tcRunLogger.fatal("%s: %s: %s" %
> > AttributeError: 'NoneType' object has no attribute 'fatal'
> >
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > The logs are generated at /tmp and the log has following error.
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > 2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
> > {'account': 'admin'}
> > 2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
> > http://10.88.91.100:8096/client/api :
> > HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> > with url: /client/api?account=admin&command=listUsers&response=json
> (Caused
> > by <class 'socket.error'>: [Errno 110] Connection timed out)
> >
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > Please note: I have opened the integration port 8096 on management
> server.
> > Also, changed the global settings integration.api.port
> > on cloudstack GUI to 8096 and restarted the management server.
> >
> > Still I am getting the above issue. I am not sure if i missed any
> > configuration.
> >
> > Can somebody please help me with resolution of this issue?
> > Appreciate your help here!!!
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> > On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>>><mailto:
> > umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>>> wrote:
> >
> > > Thanks a lot Sudha for your quick response.
> > > I will setup the Marvin on local machine and get back in case if I face
> > > any challenges in setup.
> > >
> > > Thanks and Regards
> > > -- Umesh Kute
> > >
> > >
> > >
> > > On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
> > > sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>>><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>>>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com><mailto:sudha.ponnaganti@citrix.com
> <ma...@citrix.com>>>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com><mailto:
> sudha.ponnaganti@citrix.com<ma...@citrix.com>>>>>>>>
> wrote:
> > >
> > >> Hi Umesh,
> > >>
> > >> Looks like you have started on right track - Marvin is the framework
> to
> > >> use for functional or integration automation.
> > >> There are sizable number of test cases exist and you can review them.
> > >>  There are some wiki pages already written explaining Marvin [1]. Also
> > best
> > >> practices are published by community as well [2]. You can contribute
> to
> > it
> > >> as much as you can.
> > >>
> > >> Besides this, there is Junit framework (unit Test), Selenium framework
> > >> (UI automation) which are not as popular as Marvin. Marvin is perfect
> > for
> > >> majority of the validation. You can use simulator as well with Marvin.
> > >>
> > >> Please do pursue these and post questions to the community if you run
> in
> > >> to any issues in setting up env and running tests. There are jobs
> setup
> > by
> > >> various community members to test Master or current releases in
> various
> > >> labs and can help answer questions.
> > >>
> > >> [1]
> > >>
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> > >>
> > >>
> > >> Thanks
> > >> /Sudha
> > >>
> > >>
> > >> -----Original Message-----
> > >> From: umesh kute [mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>>>]
> > >> Sent: Saturday, December 07, 2013 10:29 PM
> > >> To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org><mailto:users@cloudstack.apache.org
> <ma...@cloudstack.apache.org>>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>
> > >> Subject: Regarding cloudstack automation
> > >>
> > >> Hi All,
> > >> Good morning !!!
> > >> I am working as QA engineer and I am new to the cloudstack community.
> > >> We have started using cloudstack and deployed it in our
> infrastructure.
> > >>
> > >> Can somebody please help me in identifying the good automation
> > >> framework/tool/anything? The main intention is we want to automate the
> > >> infrastructure validation related cases (for e.g. create/update/delete
> > >> cases for instances, project, network, etc...)
> > >>
> > >> It would be good if you can help in identifying it.
> > >>
> > >> Please note: I have gone through cloudmonkey. But i haven't found much
> > >> help on it. May be i need to search a bit more.. I am also going
> through
> > >> the marvin and planning to setup it. If apart from these two, if
> anyone
> > has
> > >> different view please suggest.
> > >>
> > >> Also, if somebody has any pointers on cloudmonkey and marvin or any
> more
> > >> info on this (like, if it would suffice the infrastructure validation
> > >> related cases i mentioned above) any pros/cons would really be helpful
> > for
> > >> me...
> > >>
> > >> Appreciate any help on this and looking forward for the response on
> > >> this!!!
> > >>
> > >> Thanks and Regards
> > >> -- Umesh Kute
> > >>
> > >
> > >
> >
> >
>
>
>
>

RE: Regarding cloudstack automation

[Santhosh Edukulla <sa...@citrix.com>]

Umesh,

1. Its good that the template issue is resolved.

2. Regarding point 4 mentioned below, your understanding is right. The idea is during automation run for various test suites,  we use a template seeded into CS which has the password set with the one used in Services Class. So, in a way for all test suites having this password mentioned is assumed to be having an instance deployed with template matching our condition and so ssh works.

3. There are test cases pertaining explicitly to verify reset cases under CS, that covers scenarios to test, but for every ssh we dont use the password given by the API output.

4. So, for creating instances you can use a template with password as "password" for your testing, thats the easy solution i believe and all test suits has this password inside them, it will work. In a way, this not so a good design, but  
We are planning to remove Services class test data from tests and separate it out as a test data, So for user running tests can alter the config to suit the template he has and all test suites using ssh works and will be configurable, compared to now we have to modify all test suites to get it working with custom password for user.

Thanks!
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com]
Sent: Friday, January 17, 2014 7:32 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Hi Santhosh,
Thanks again...
I tried the steps that you mentioned below. Fortunately i could able to proceed a bit further on this issue.

Now, instance got created successfully of type CentOS 6.4 (64-bit).

It is stuck in the ssh step.
Here is what happens...

1. All the steps/APIs till instance creation works fine (including listDomains, listZones, listOsTypes, listTemplates, createAccount, createServiceOffering, deployVirtualMachine, queryAsyncJobResult, associateIPAddress, createFirewallRules, createPortForwardingRule, createEgressFirewallRule)

2. When it tries to SSH to virtual machine it fails after timeout of 600s (20-retries, 30-intervals). Script is terminated.

3. I put some debug statements in function get_ssh_client() under: "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py"

The credentials i think it tries is :
self.ssh_ip: 207.x.x.x
self.ssh_port: 22
self.username: root
self.password: password
keyPairFileLocation: None

It means, it tries to connect to instance using password as password (it is provided in dictionary in test_vm_passwdenabled.py. Note: Earlier i gave references for test_loadbalance.py and its the same case).

4. In log, i found that the password that is returned in response to deployVirtualMachine API call is: xA2yeaxvb. (PFA file runinfo). When i tried to do ssh to the instance with same password it works and with dictionary "password" it doesn't. I think so.. please confirm...

Either, for ssh connection it should use the returned password or reset password before connection.

PFA all the logs.
Please correct if my understanding is correct or I am missing something here....

Please let me know if there is any resolution of this issue or if somebody encounters it before.

Thanks and Regards
-- Umesh Kute

On Tue, Jan 14, 2014 at 6:48 PM, Santhosh Edukulla <sa...@citrix.com>> wrote:
Umesh,

Lets put steps so that we are in same page:

1. When we deploy  a VM, we use get_template function which basically retrieves the template information matching the description you provided under services class for ostype under test module EX: test_loadbalance.py.  I am surprised that you are receiving a "featured" and "builtin" template as windows template as output for this function. We are explicitly verifiying the template type as "BUILTIN" to retrieve the template information. So, a windows template cannot be a BUILTIN Template. Either it could be a bug in this function, or something with API. But, to double confirm, Can you please check whats the template information you are retrieving from this function matching with listTemplates API output( run either from your browser or script )  passing the same arguments as passed inside get_template?

Inside if we see, basically it gets the id matching with that ostype description using "listOsTypes"  and then use "listTemplates" command. So, this template is used to deploy the vm.  As far as i know, a builtin template cannot be a windows template?  Here, we use a featured and builtin template along with description filter passed. So, please check whether the template you are retrieving is windows or otherwise. Check for the field ostypename for the output you receive? Provide the output here for get_template copy pasted with dir(template) for return value?

2. To double confirm that it is template issue and not any other issue related to ssh like ( firewall\iptables\network connectivity issue) for ssh, please manually check for that particular ip in the test case whether ssh works or not and is not a windows machine?

3. Run one test case, first by adding a tag EX: "umesh" to the tags list as mentioned below for a particular test case under test module EX: test_loadbalance.py, then  run with nose command passing in tags argument mentioned below.

 @attr(tags = ["advanced", "advancedns", "smoke", "umesh"])
    def test_01_create_lb_rule_src_nat(self):

nosetests-2.7 -v --with-marvin --marvin-config=/root/softwares/cscode/setup/dev/advanced.cfg --load -a -w /root/softwares/cscode/test/integration/smoke/ -a tags=umesh

Let me know.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>]
Sent: Tuesday, January 14, 2014 7:02 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

I re-installed the marvin today to get the latest code.
I am again facing the same problem in get_template. It is returning the windows template and creating the windows VM. Hence when it tries to do SSH for VM, it fails.

I have also build the cloudstack to get the latest code for Marvin.

PFA the script logs and test_loadbalance script for reference.

Also, do let me know if I am missing some configuration or anything...

Just an FYI.. I have executed 35 scripts in smoke test directory. Out of 35 scripts executed, 17-PASS, 18-FAIL.
Around 50% failure are due to SSH related issue.

Thanks and Regards
-- Umesh Kute


On Fri, Jan 10, 2014 at 5:53 PM, Santhosh Edukulla <sa...@citrix.com>>> wrote:
1. As such because of  bug in get_template, you are getting windows machine in your setup and then ssh is tried in test module, so you are getting the error.

2. Now, to overcome, just checkout the latest marvin, it should have a fix.

Note: It still has some other issues, but you can continue with your testing further. Let us know.

Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>]
Sent: Friday, January 10, 2014 5:19 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

So far i have found the failure on following scripts:
1. test_loadbalance
2. test_network
3. test_nic

In runinfo.txt log it is stuck at the step:
SSH into VM (IPaddress: 10.1.1.55) & NAT Rule (Public IP: 207.x.x.x)

PFA the Marvin logs for the test_loadbalance.py script.

I have modified the following entry in the script i.e. provided the correct template name which is present.
"ostype": "CentOS 6.4 (64-bit)",
#"ostype": "CentOS 5.3 (64-bit)",

Please let me know for your comments.

Thanks and Regards
-- Umesh Kute



On Fri, Jan 10, 2014 at 2:57 PM, Santhosh Edukulla <sa...@citrix.com>>>> wrote:
You can log the bug for this. We have fixed few other issues along with this in a private branch. Will soon merge with ACS. If you need a temporary fix, let me know.

Question : Related to ssh issue, ssh to vm failing at which part? Can you add some information related to ssh failure which test module, which case etc? This may be related\unrelated to the above issue. We can check to see the issue is either same\different.

Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>]
Sent: Friday, January 10, 2014 4:21 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks a lot Santhosh For your response.

Sorry for delay.. But is there any workaround for this issue? Because as i mentioned, even if os type is provided as "ostype": 'CentOS 6.4 (64-bit)' it is picking up the first one in list i.e. Windows Server 2008 R2 Enterprise.
So some of the scripts which required to SSH into VM are failing.

Can I get the JIRA ID for this issue to track?

Thanks and Regards
-- Umesh Kute


On Fri, Jan 3, 2014 at 5:19 PM, Santhosh Edukulla <sa...@citrix.com>>>>> wrote:
Umesh,

This could be probably due to the bug under get_template function under marvin/integration/lib/common.py. Though, the ostype description is used and corresponding id is retrieved.

But the later part, listTemplate API call returning the list and we are picking up either the template which is ready or matching with id we retrieved. This case is what could be causing the issue you mentioned.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>]
Sent: Friday, January 03, 2014 5:04 AM
To: Santhosh Edukulla; users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks for your help Santhosh!!!

You are right...
The public IP address range was exhausted. After cleaning up the resources, I was able to run the sample script "test_deploy_vm.py" successfully.

One question - i have provided the "ostype": 'CentOS 6.4 (64-bit)'. What is the use of this parameter?

When observed in management server logs and on cloudstack UI (while running script), VM was created of type: "Windows Server 2008 R2 Enterprise with SQL 2012 Web Edition". This is the first one in the list.

Does it choose the one which we provided in script or picks it from the template list that is returned as a result of response to listTemplate API call?

Thanks and Regards
-- Umesh Kute


On Thu, Jan 2, 2014 at 7:22 PM, Santhosh Edukulla <sa...@citrix.com>>>>>> wrote:
Umesh,

1. It seems you have exhausted few of CloudStack Resources. These resources usage should show up on your cloudstack dashboard. Anything appears in Red are exhausted resources.

2. Few of the cases could be EX: Guest VM IPs\Management ip addresses  are exhausted,

3. Check for these resources in Red on your dashboard EX: http://localhost:8080/client/->Dashboard and clean up them or add new resources.


Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>]
Sent: Thursday, January 02, 2014 7:06 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thank you once again Santhosh & Chandan.

I have gone through the management server logs. The deployment of VM got fired to the setup correctly and there are couple of errors in the management-server log.
I am summarizing those below:

test data in "test_deploy_vm.py"
 def __init__(self):
        self.testdata = {
            #data to create an account
            "account": {
                "email": "test@test.com<ma...@test.com>>>>>>",
                "firstname": "Test",
                "lastname": "User",
                "username": "test",
                "password": "password",
            },
            #data reqd for virtual machine creation
            "virtual_machine" : {
                "name" : "testvmshr",
                "displayname" : "Test VM shr",
            },
            #small service offering
            "service_offering": {
                "small": {
                    "name": "SOSmall",
                    "displaytext": "Small Instance",
                    "cpunumber": 1,
                    "cpuspeed": 2000,
                    "memory": 1024,
                },
            },
            "ostype": 'CentOS 6.4 (64-bit)',
        }


1. Account is successfully created
2. Service offering is successfully created
3. Management server logs - management-server.log has following error:


2014-01-02 01:43:40,693 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Lock is released for network Ntwk[326|Guest|15] as a part of network shutdown
2014-01-02 01:43:40,695 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Lock is released for network id 326 as a part of network implement
2014-01-02 01:43:40,695 INFO  [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Insufficient capacity
com.cloud.exception.InsufficientAddressCapacityException: Insufficient address capacityScope=interface com.cloud.dc.DataCenter; id=1
at com.cloud.network.NetworkManagerImpl.fetchNewPublicIp(NetworkManagerImpl.java:479)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.assignDedicateIpAddress(NetworkManagerImpl.java:613)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.assignSourceNatIpAddressToGuestNetwork(NetworkManagerImpl.java:582)
at com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:2013)
at com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1939)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2120)
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:887)
at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2014-01-02 01:43:40,703 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Cleaning up resources for the vm VM[User|testvmshr] in Starting state

4. When i checked the database for the network id 326 in table "networks", it has following entry:

| 326 | test-TestDeployVM-test_deploy_vm-QQ91N0-network | b7cb9e31-835f-47e3-9585-97e3b4084e4d | test-TestDeployVM-test_deploy_vm-QQ91N0-network | Guest        | Vlan                  | NULL          | 10.1.1.1       | 10.1.1.0/24<http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24>     | Dhcp   |                  15 |                 200 |              1 | ExternalGuestNetworkGuru | Destroy     |     326 |         1 |        305 | 8.8.8.8 | 8.8.4.4 | NULL      |          0 | Account  | cs131cloud.internal | ecf5b617-04da-469b-b378-f53e05d8cc53 | Isolated   |                0 | 2014-01-02 06:43:39 | 2014-01-02 06:43:46 |                 0 |   NULL | NULL        | NULL     | NULL         |               1 |           NULL |


Basically it tries to create a network offering (id=15) : "HA Isolated Network With Source Nat"


5. I think the script creates a network shown in above table: "test-TestDeployVM-test_deploy_vm-QQ91N0-network".

I am not sure why it still gives the Insufficient address capacityScope exception.

6. One more thing i observed. I have provided the "ostype": 'CentOS 6.4 (64-bit)'. But in DeployVMCmd it uses the template id: "03ffb96f-2cfa-11e3-a4f0-f245a5b3ba0f" which is for template "Windows Server 2008 R2 Enterprise with SQL 2012 Web Edition".


I am attaching the management-server logs and script logs for references.

If somebody can help me what's wrong here, would really be helpful.


Thanks and Regards
-- Umesh Kute


On Thu, Jan 2, 2014 at 2:59 PM, Santhosh Edukulla <sa...@citrix.com>>>>>>> wrote:
1. Is it still failing post this registration?

2. If yes, may be you can verify\provide the management server logs.
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>]
Sent: Thursday, January 02, 2014 4:16 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks Santhosh.
Yes, I have registered the following template which i am using.

"ostype": 'CentOS 6.4 (64-bit)',

Thanks and Regards
-- Umesh Kute


On Mon, Dec 30, 2013 at 5:50 PM, Santhosh Edukulla <
santhosh.edukulla@citrix.com<ma...@citrix.com>>>>>>> wrote:

> Umesh,
>
> One question : Did you registered the template for ostype:     "ostype":
> 'CentOS 5.3 (64-bit)'?
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>>]
> Sent: Monday, December 30, 2013 6:32 AM
> To: Chandan Purushothama
> Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi Chandan,
> Thanks for your response.
> I have the latest Marvin repository (December 20th). I am able to proceed
> further. There was an issue of firewall for that machine and it got
> resolved.
>
> But now i am getting another error when i tried to run the script
> "test_deploy_vm.py"
>
> I have attached the log. Can somebody please have a look on it and help me
> in resolving the issue?
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> test_deploy_vm (integration.smoke.test_deploy_vm.TestDeployVM): CRITICAL:
> EXCEPTION: test_deploy_vm: Traceback (most recent call last):
>   File "/usr/local/lib/python2.7/unittest/case.py", line 327, in run
>     testMethod()
>   File
> "/DataDisk/temp/cloudstack/test/integration/smoke/test_deploy_vm.py", line
> 116, in test_deploy_vm
>     templateid=self.template.id<http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id>
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py",
> line 415, in create
>     virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> line 593, in deployVirtualMachine
>     response = self.connection.marvinRequest(command,
> response_type=response, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 280, in marvinRequest
>     response = self.poll(asyncJobId, response_type)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 86, in poll
>     "asyncquery", asyncResonse.jobresult)
> cloudstackAPIException: Execute cmd: asyncquery failed, due to: {errorcode
> : 533, errortext : u'Unable to create a deployment for VM[User|testvmshr]'}
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> PFA entire logs.
>
> Please let me know in case if anything is required.
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Sun, Dec 29, 2013 at 10:32 PM, Chandan Purushothama <
> Chandan.Purushothama@citrix.com<ma...@citrix.com>>>>>>>>
> wrote:
>
> Hello Umesh,
>
> I had a similar experience with an older Marvin build. I updated mine to
> the latest and tried again and it worked. I recommend you to kindly try
> again with the latest Marvin build and see if you are able to work with the
> automation framework,
>
> Thank you,
> Chandan
>
>
> -------- Original message --------
> From: umesh kute
> Date:12/26/2013 12:29 AM (GMT-08:00)
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>,Sudha
> Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi All,
> I have created a Marvin setup on CentOS6.3 by following the document:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
>
> All the pre-requisites are installed successfully.
>
> I tried to run the sample script test_deploy_vm.py
> (cloudstack/test/integration/smoke/), I am getting following error:
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> [root@localhost smoke]# nosetests --with-marvin
> --marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg --load
> test_deploy_vm.py
>
>  Exception Occurred Under __deployDC :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
> Traceback (most recent call last):
>   File "/usr/local/bin/nosetests", line 9, in <module>
>     load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 118, in __init__
>     **extra_args)
>   File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
>     self.runTests()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 197, in runTests
>     result = self.testRunner.run(self.test)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 61, in run
>     test(result)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 45, in __call__
>     return self.run(*arg, **kwarg)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 138, in run
>     result.addError(self, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
> line 124, in addError
>     plugin_handled = plugins.handleError(self.test, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 99, in __call__
>     return self.call(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 167, in simple
>     result = meth(*arg, **kw)
>   File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
> line 155, in handleError
>     self.tcRunLogger.fatal("%s: %s: %s" %
> AttributeError: 'NoneType' object has no attribute 'fatal'
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> The logs are generated at /tmp and the log has following error.
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
> {'account': 'admin'}
> 2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
> http://10.88.91.100:8096/client/api :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Please note: I have opened the integration port 8096 on management server.
> Also, changed the global settings integration.api.port
> on cloudstack GUI to 8096 and restarted the management server.
>
> Still I am getting the above issue. I am not sure if i missed any
> configuration.
>
> Can somebody please help me with resolution of this issue?
> Appreciate your help here!!!
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <um...@gmail.com>>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>>> wrote:
>
> > Thanks a lot Sudha for your quick response.
> > I will setup the Marvin on local machine and get back in case if I face
> > any challenges in setup.
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> >
> > On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
> > sudha.ponnaganti@citrix.com<ma...@citrix.com>>>>>>>> wrote:
> >
> >> Hi Umesh,
> >>
> >> Looks like you have started on right track - Marvin is the framework to
> >> use for functional or integration automation.
> >> There are sizable number of test cases exist and you can review them.
> >>  There are some wiki pages already written explaining Marvin [1]. Also
> best
> >> practices are published by community as well [2]. You can contribute to
> it
> >> as much as you can.
> >>
> >> Besides this, there is Junit framework (unit Test), Selenium framework
> >> (UI automation) which are not as popular as Marvin. Marvin is perfect
> for
> >> majority of the validation. You can use simulator as well with Marvin.
> >>
> >> Please do pursue these and post questions to the community if you run in
> >> to any issues in setting up env and running tests. There are jobs setup
> by
> >> various community members to test Master or current releases in various
> >> labs and can help answer questions.
> >>
> >> [1]
> >>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> >>
> >>
> >> Thanks
> >> /Sudha
> >>
> >>
> >> -----Original Message-----
> >> From: umesh kute [mailto:umeshvkute@gmail.com<ma...@gmail.com>>>>>>]
> >> Sent: Saturday, December 07, 2013 10:29 PM
> >> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>>
> >> Subject: Regarding cloudstack automation
> >>
> >> Hi All,
> >> Good morning !!!
> >> I am working as QA engineer and I am new to the cloudstack community.
> >> We have started using cloudstack and deployed it in our infrastructure.
> >>
> >> Can somebody please help me in identifying the good automation
> >> framework/tool/anything? The main intention is we want to automate the
> >> infrastructure validation related cases (for e.g. create/update/delete
> >> cases for instances, project, network, etc...)
> >>
> >> It would be good if you can help in identifying it.
> >>
> >> Please note: I have gone through cloudmonkey. But i haven't found much
> >> help on it. May be i need to search a bit more.. I am also going through
> >> the marvin and planning to setup it. If apart from these two, if anyone
> has
> >> different view please suggest.
> >>
> >> Also, if somebody has any pointers on cloudmonkey and marvin or any more
> >> info on this (like, if it would suffice the infrastructure validation
> >> related cases i mentioned above) any pros/cons would really be helpful
> for
> >> me...
> >>
> >> Appreciate any help on this and looking forward for the response on
> >> this!!!
> >>
> >> Thanks and Regards
> >> -- Umesh Kute
> >>
> >
> >
>
>

Re: Regarding cloudstack automation

[umesh kute <um...@gmail.com>]

Hi Santhosh,
Thanks again...
I tried the steps that you mentioned below. Fortunately i could able to
proceed a bit further on this issue.

Now, instance got created successfully of type CentOS 6.4 (64-bit).

It is stuck in the ssh step.
Here is what happens...

1. All the steps/APIs till instance creation works fine (including
listDomains, listZones, listOsTypes, listTemplates, createAccount,
createServiceOffering, deployVirtualMachine, queryAsyncJobResult,
associateIPAddress,
createFirewallRules, createPortForwardingRule, createEgressFirewallRule)

2. When it tries to SSH to virtual machine it fails after timeout of 600s
(20-retries, 30-intervals). Script is terminated.

3. I put some debug statements in function get_ssh_client() under:
"/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py"

The credentials i think it tries is :
self.ssh_ip: 207.x.x.x
self.ssh_port: 22
self.username: root
self.password: password
keyPairFileLocation: None

It means, it tries to connect to instance using password as password (it is
provided in dictionary in test_vm_passwdenabled.py. Note: Earlier i gave
references for test_loadbalance.py and its the same case).

4. In log, i found that the password that is returned in response to
deployVirtualMachine API call is: xA2yeaxvb. (PFA file runinfo). When i
tried to do ssh to the instance with same password it works and with
dictionary "password" it doesn't. I think so.. please confirm...

Either, for ssh connection it should use the returned password or reset
password before connection.

PFA all the logs.
Please correct if my understanding is correct or I am missing something
here....

Please let me know if there is any resolution of this issue or if somebody
encounters it before.

Thanks and Regards
-- Umesh Kute

On Tue, Jan 14, 2014 at 6:48 PM, Santhosh Edukulla <
santhosh.edukulla@citrix.com> wrote:

> Umesh,
>
> Lets put steps so that we are in same page:
>
> 1. When we deploy  a VM, we use get_template function which basically
> retrieves the template information matching the description you provided
> under services class for ostype under test module EX: test_loadbalance.py.
>  I am surprised that you are receiving a "featured" and "builtin" template
> as windows template as output for this function. We are explicitly
> verifiying the template type as "BUILTIN" to retrieve the template
> information. So, a windows template cannot be a BUILTIN Template. Either it
> could be a bug in this function, or something with API. But, to double
> confirm, Can you please check whats the template information you are
> retrieving from this function matching with listTemplates API output( run
> either from your browser or script )  passing the same arguments as passed
> inside get_template?
>
> Inside if we see, basically it gets the id matching with that ostype
> description using "listOsTypes"  and then use "listTemplates" command. So,
> this template is used to deploy the vm.  As far as i know, a builtin
> template cannot be a windows template?  Here, we use a featured and builtin
> template along with description filter passed. So, please check whether the
> template you are retrieving is windows or otherwise. Check for the field
> ostypename for the output you receive? Provide the output here for
> get_template copy pasted with dir(template) for return value?
>
> 2. To double confirm that it is template issue and not any other issue
> related to ssh like ( firewall\iptables\network connectivity issue) for
> ssh, please manually check for that particular ip in the test case whether
> ssh works or not and is not a windows machine?
>
> 3. Run one test case, first by adding a tag EX: "umesh" to the tags list
> as mentioned below for a particular test case under test module EX:
> test_loadbalance.py, then  run with nose command passing in tags argument
> mentioned below.
>
>  @attr(tags = ["advanced", "advancedns", "smoke", "umesh"])
>     def test_01_create_lb_rule_src_nat(self):
>
> nosetests-2.7 -v --with-marvin
> --marvin-config=/root/softwares/cscode/setup/dev/advanced.cfg --load -a -w
> /root/softwares/cscode/test/integration/smoke/ -a tags=umesh
>
> Let me know.
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com]
> Sent: Tuesday, January 14, 2014 7:02 AM
> To: Santhosh Edukulla
> Cc: users@cloudstack.apache.org; Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> I re-installed the marvin today to get the latest code.
> I am again facing the same problem in get_template. It is returning the
> windows template and creating the windows VM. Hence when it tries to do SSH
> for VM, it fails.
>
> I have also build the cloudstack to get the latest code for Marvin.
>
> PFA the script logs and test_loadbalance script for reference.
>
> Also, do let me know if I am missing some configuration or anything...
>
> Just an FYI.. I have executed 35 scripts in smoke test directory. Out of
> 35 scripts executed, 17-PASS, 18-FAIL.
> Around 50% failure are due to SSH related issue.
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Fri, Jan 10, 2014 at 5:53 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com>> wrote:
> 1. As such because of  bug in get_template, you are getting windows
> machine in your setup and then ssh is tried in test module, so you are
> getting the error.
>
> 2. Now, to overcome, just checkout the latest marvin, it should have a fix.
>
> Note: It still has some other issues, but you can continue with your
> testing further. Let us know.
>
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>]
> Sent: Friday, January 10, 2014 5:19 AM
> To: Santhosh Edukulla
> Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>;
> Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> So far i have found the failure on following scripts:
> 1. test_loadbalance
> 2. test_network
> 3. test_nic
>
> In runinfo.txt log it is stuck at the step:
> SSH into VM (IPaddress: 10.1.1.55) & NAT Rule (Public IP: 207.x.x.x)
>
> PFA the Marvin logs for the test_loadbalance.py script.
>
> I have modified the following entry in the script i.e. provided the
> correct template name which is present.
> "ostype": "CentOS 6.4 (64-bit)",
> #"ostype": "CentOS 5.3 (64-bit)",
>
> Please let me know for your comments.
>
> Thanks and Regards
> -- Umesh Kute
>
>
>
> On Fri, Jan 10, 2014 at 2:57 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>>> wrote:
> You can log the bug for this. We have fixed few other issues along with
> this in a private branch. Will soon merge with ACS. If you need a temporary
> fix, let me know.
>
> Question : Related to ssh issue, ssh to vm failing at which part? Can you
> add some information related to ssh failure which test module, which case
> etc? This may be related\unrelated to the above issue. We can check to see
> the issue is either same\different.
>
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>>]
> Sent: Friday, January 10, 2014 4:21 AM
> To: Santhosh Edukulla
> Cc: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><ma...@cloudstack.apache.org>>;
> Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thanks a lot Santhosh For your response.
>
> Sorry for delay.. But is there any workaround for this issue? Because as i
> mentioned, even if os type is provided as "ostype": 'CentOS 6.4 (64-bit)'
> it is picking up the first one in list i.e. Windows Server 2008 R2
> Enterprise.
> So some of the scripts which required to SSH into VM are failing.
>
> Can I get the JIRA ID for this issue to track?
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Fri, Jan 3, 2014 at 5:19 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>>>>
> wrote:
> Umesh,
>
> This could be probably due to the bug under get_template function under
> marvin/integration/lib/common.py. Though, the ostype description is used
> and corresponding id is retrieved.
>
> But the later part, listTemplate API call returning the list and we are
> picking up either the template which is ready or matching with id we
> retrieved. This case is what could be causing the issue you mentioned.
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>]
> Sent: Friday, January 03, 2014 5:04 AM
> To: Santhosh Edukulla; users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>
> Cc: Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thanks for your help Santhosh!!!
>
> You are right...
> The public IP address range was exhausted. After cleaning up the
> resources, I was able to run the sample script "test_deploy_vm.py"
> successfully.
>
> One question - i have provided the "ostype": 'CentOS 6.4 (64-bit)'. What
> is the use of this parameter?
>
> When observed in management server logs and on cloudstack UI (while
> running script), VM was created of type: "Windows Server 2008 R2 Enterprise
> with SQL 2012 Web Edition". This is the first one in the list.
>
> Does it choose the one which we provided in script or picks it from the
> template list that is returned as a result of response to listTemplate API
> call?
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Thu, Jan 2, 2014 at 7:22 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>>> wrote:
> Umesh,
>
> 1. It seems you have exhausted few of CloudStack Resources. These
> resources usage should show up on your cloudstack dashboard. Anything
> appears in Red are exhausted resources.
>
> 2. Few of the cases could be EX: Guest VM IPs\Management ip addresses  are
> exhausted,
>
> 3. Check for these resources in Red on your dashboard EX:
> http://localhost:8080/client/->Dashboard and clean up them or add new
> resources.
>
>
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>]
> Sent: Thursday, January 02, 2014 7:06 AM
> To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>
> Cc: Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thank you once again Santhosh & Chandan.
>
> I have gone through the management server logs. The deployment of VM got
> fired to the setup correctly and there are couple of errors in the
> management-server log.
> I am summarizing those below:
>
> test data in "test_deploy_vm.py"
>  def __init__(self):
>         self.testdata = {
>             #data to create an account
>             "account": {
>                 "email": "test@test.com<ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>>>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>>>>",
>                 "firstname": "Test",
>                 "lastname": "User",
>                 "username": "test",
>                 "password": "password",
>             },
>             #data reqd for virtual machine creation
>             "virtual_machine" : {
>                 "name" : "testvmshr",
>                 "displayname" : "Test VM shr",
>             },
>             #small service offering
>             "service_offering": {
>                 "small": {
>                     "name": "SOSmall",
>                     "displaytext": "Small Instance",
>                     "cpunumber": 1,
>                     "cpuspeed": 2000,
>                     "memory": 1024,
>                 },
>             },
>             "ostype": 'CentOS 6.4 (64-bit)',
>         }
>
>
> 1. Account is successfully created
> 2. Service offering is successfully created
> 3. Management server logs - management-server.log has following error:
>
>
> 2014-01-02 01:43:40,693 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Lock is released for network Ntwk[326|Guest|15] as a part of network
> shutdown
> 2014-01-02 01:43:40,695 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Lock is released for network id 326 as a part of network implement
> 2014-01-02 01:43:40,695 INFO  [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Insufficient capacity
> com.cloud.exception.InsufficientAddressCapacityException: Insufficient
> address capacityScope=interface com.cloud.dc.DataCenter; id=1
> at
> com.cloud.network.NetworkManagerImpl.fetchNewPublicIp(NetworkManagerImpl.java:479)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.network.NetworkManagerImpl.assignDedicateIpAddress(NetworkManagerImpl.java:613)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.network.NetworkManagerImpl.assignSourceNatIpAddressToGuestNetwork(NetworkManagerImpl.java:582)
> at
> com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:2013)
> at
> com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1939)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2120)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:887)
> at
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:679)
> 2014-01-02 01:43:40,703 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Cleaning up resources for the vm VM[User|testvmshr] in Starting state
>
> 4. When i checked the database for the network id 326 in table "networks",
> it has following entry:
>
> | 326 | test-TestDeployVM-test_deploy_vm-QQ91N0-network |
> b7cb9e31-835f-47e3-9585-97e3b4084e4d |
> test-TestDeployVM-test_deploy_vm-QQ91N0-network | Guest        | Vlan
>            | NULL          | 10.1.1.1       | 10.1.1.0/24<
> http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><
> http://10.1.1.0/24><http://10.1.1.0/24>     | Dhcp   |
>  15 |                 200 |              1 | ExternalGuestNetworkGuru |
> Destroy     |     326 |         1 |        305 | 8.8.8.8 | 8.8.4.4 | NULL
>    |          0 | Account  | cs131cloud.internal |
> ecf5b617-04da-469b-b378-f53e05d8cc53 | Isolated   |                0 |
> 2014-01-02 06:43:39 | 2014-01-02 06:43:46 |                 0 |   NULL |
> NULL        | NULL     | NULL         |               1 |           NULL |
>
>
> Basically it tries to create a network offering (id=15) : "HA Isolated
> Network With Source Nat"
>
>
> 5. I think the script creates a network shown in above table:
> "test-TestDeployVM-test_deploy_vm-QQ91N0-network".
>
> I am not sure why it still gives the Insufficient address capacityScope
> exception.
>
> 6. One more thing i observed. I have provided the "ostype": 'CentOS 6.4
> (64-bit)'. But in DeployVMCmd it uses the template id:
> "03ffb96f-2cfa-11e3-a4f0-f245a5b3ba0f" which is for template "Windows
> Server 2008 R2 Enterprise with SQL 2012 Web Edition".
>
>
> I am attaching the management-server logs and script logs for references.
>
> If somebody can help me what's wrong here, would really be helpful.
>
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Thu, Jan 2, 2014 at 2:59 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>>>>>>
> wrote:
> 1. Is it still failing post this registration?
>
> 2. If yes, may be you can verify\provide the management server logs.
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>]
> Sent: Thursday, January 02, 2014 4:16 AM
> To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>>
> Cc: Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thanks Santhosh.
> Yes, I have registered the following template which i am using.
>
> "ostype": 'CentOS 6.4 (64-bit)',
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Mon, Dec 30, 2013 at 5:50 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com><mailto:santhosh.edukulla@citrix.com
> <ma...@citrix.com>>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>>>>>>
> wrote:
>
> > Umesh,
> >
> > One question : Did you registered the template for ostype:     "ostype":
> > 'CentOS 5.3 (64-bit)'?
> >
> > Regards,
> > Santhosh
> > ________________________________________
> > From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>]
> > Sent: Monday, December 30, 2013 6:32 AM
> > To: Chandan Purushothama
> > Cc: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><ma...@cloudstack.apache.org>>>>>;
> Sudha Ponnaganti
> > Subject: Re: Regarding cloudstack automation
> >
> > Hi Chandan,
> > Thanks for your response.
> > I have the latest Marvin repository (December 20th). I am able to proceed
> > further. There was an issue of firewall for that machine and it got
> > resolved.
> >
> > But now i am getting another error when i tried to run the script
> > "test_deploy_vm.py"
> >
> > I have attached the log. Can somebody please have a look on it and help
> me
> > in resolving the issue?
> >
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > test_deploy_vm (integration.smoke.test_deploy_vm.TestDeployVM): CRITICAL:
> > EXCEPTION: test_deploy_vm: Traceback (most recent call last):
> >   File "/usr/local/lib/python2.7/unittest/case.py", line 327, in run
> >     testMethod()
> >   File
> > "/DataDisk/temp/cloudstack/test/integration/smoke/test_deploy_vm.py",
> line
> > 116, in test_deploy_vm
> >     templateid=self.template.id<http://self.template.id><
> http://self.template.id><http://self.template.id><http://self.template.id
> ><http://self.template.id><http://self.template.id>
> >   File
> > "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py",
> > line 415, in create
> >     virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> > line 593, in deployVirtualMachine
> >     response = self.connection.marvinRequest(command,
> > response_type=response, method=method)
> >   File
> > "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> > line 280, in marvinRequest
> >     response = self.poll(asyncJobId, response_type)
> >   File
> > "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> > line 86, in poll
> >     "asyncquery", asyncResonse.jobresult)
> > cloudstackAPIException: Execute cmd: asyncquery failed, due to:
> {errorcode
> > : 533, errortext : u'Unable to create a deployment for
> VM[User|testvmshr]'}
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > PFA entire logs.
> >
> > Please let me know in case if anything is required.
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> > On Sun, Dec 29, 2013 at 10:32 PM, Chandan Purushothama <
> > Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>>>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>>>>>
> > wrote:
> >
> > Hello Umesh,
> >
> > I had a similar experience with an older Marvin build. I updated mine to
> > the latest and tried again and it worked. I recommend you to kindly try
> > again with the latest Marvin build and see if you are able to work with
> the
> > automation framework,
> >
> > Thank you,
> > Chandan
> >
> >
> > -------- Original message --------
> > From: umesh kute
> > Date:12/26/2013 12:29 AM (GMT-08:00)
> > To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>>,Sudha
> > Ponnaganti
> > Subject: Re: Regarding cloudstack automation
> >
> > Hi All,
> > I have created a Marvin setup on CentOS6.3 by following the document:
> >
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> >
> > All the pre-requisites are installed successfully.
> >
> > I tried to run the sample script test_deploy_vm.py
> > (cloudstack/test/integration/smoke/), I am getting following error:
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > [root@localhost smoke]# nosetests --with-marvin
> > --marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg
> --load
> > test_deploy_vm.py
> >
> >  Exception Occurred Under __deployDC :
> > HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> > with url: /client/api?account=admin&command=listUsers&response=json
> (Caused
> > by <class 'socket.error'>: [Errno 110] Connection timed out)
> > Traceback (most recent call last):
> >   File "/usr/local/bin/nosetests", line 9, in <module>
> >     load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> > line 118, in __init__
> >     **extra_args)
> >   File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
> >     self.runTests()
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> > line 197, in runTests
> >     result = self.testRunner.run(self.test)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> > line 61, in run
> >     test(result)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> > line 45, in __call__
> >     return self.run(*arg, **kwarg)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> > line 138, in run
> >     result.addError(self, err)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
> > line 124, in addError
> >     plugin_handled = plugins.handleError(self.test, err)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> > line 99, in __call__
> >     return self.call(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> > line 167, in simple
> >     result = meth(*arg, **kw)
> >   File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
> > line 155, in handleError
> >     self.tcRunLogger.fatal("%s: %s: %s" %
> > AttributeError: 'NoneType' object has no attribute 'fatal'
> >
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > The logs are generated at /tmp and the log has following error.
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > 2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
> > {'account': 'admin'}
> > 2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
> > http://10.88.91.100:8096/client/api :
> > HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> > with url: /client/api?account=admin&command=listUsers&response=json
> (Caused
> > by <class 'socket.error'>: [Errno 110] Connection timed out)
> >
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > Please note: I have opened the integration port 8096 on management
> server.
> > Also, changed the global settings integration.api.port
> > on cloudstack GUI to 8096 and restarted the management server.
> >
> > Still I am getting the above issue. I am not sure if i missed any
> > configuration.
> >
> > Can somebody please help me with resolution of this issue?
> > Appreciate your help here!!!
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> > On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>><mailto:
> > umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>> wrote:
> >
> > > Thanks a lot Sudha for your quick response.
> > > I will setup the Marvin on local machine and get back in case if I face
> > > any challenges in setup.
> > >
> > > Thanks and Regards
> > > -- Umesh Kute
> > >
> > >
> > >
> > > On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
> > > sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>>><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com><mailto:sudha.ponnaganti@citrix.com<mailto:
> sudha.ponnaganti@citrix.com>>>>>>> wrote:
> > >
> > >> Hi Umesh,
> > >>
> > >> Looks like you have started on right track - Marvin is the framework
> to
> > >> use for functional or integration automation.
> > >> There are sizable number of test cases exist and you can review them.
> > >>  There are some wiki pages already written explaining Marvin [1]. Also
> > best
> > >> practices are published by community as well [2]. You can contribute
> to
> > it
> > >> as much as you can.
> > >>
> > >> Besides this, there is Junit framework (unit Test), Selenium framework
> > >> (UI automation) which are not as popular as Marvin. Marvin is perfect
> > for
> > >> majority of the validation. You can use simulator as well with Marvin.
> > >>
> > >> Please do pursue these and post questions to the community if you run
> in
> > >> to any issues in setting up env and running tests. There are jobs
> setup
> > by
> > >> various community members to test Master or current releases in
> various
> > >> labs and can help answer questions.
> > >>
> > >> [1]
> > >>
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> > >>
> > >>
> > >> Thanks
> > >> /Sudha
> > >>
> > >>
> > >> -----Original Message-----
> > >> From: umesh kute [mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>>]
> > >> Sent: Saturday, December 07, 2013 10:29 PM
> > >> To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>>>>>
> > >> Subject: Regarding cloudstack automation
> > >>
> > >> Hi All,
> > >> Good morning !!!
> > >> I am working as QA engineer and I am new to the cloudstack community.
> > >> We have started using cloudstack and deployed it in our
> infrastructure.
> > >>
> > >> Can somebody please help me in identifying the good automation
> > >> framework/tool/anything? The main intention is we want to automate the
> > >> infrastructure validation related cases (for e.g. create/update/delete
> > >> cases for instances, project, network, etc...)
> > >>
> > >> It would be good if you can help in identifying it.
> > >>
> > >> Please note: I have gone through cloudmonkey. But i haven't found much
> > >> help on it. May be i need to search a bit more.. I am also going
> through
> > >> the marvin and planning to setup it. If apart from these two, if
> anyone
> > has
> > >> different view please suggest.
> > >>
> > >> Also, if somebody has any pointers on cloudmonkey and marvin or any
> more
> > >> info on this (like, if it would suffice the infrastructure validation
> > >> related cases i mentioned above) any pros/cons would really be helpful
> > for
> > >> me...
> > >>
> > >> Appreciate any help on this and looking forward for the response on
> > >> this!!!
> > >>
> > >> Thanks and Regards
> > >> -- Umesh Kute
> > >>
> > >
> > >
> >
> >
>
>
>

RE: Regarding cloudstack automation

[Santhosh Edukulla <sa...@citrix.com>]

Umesh,

Lets put steps so that we are in same page:

1. When we deploy  a VM, we use get_template function which basically retrieves the template information matching the description you provided under services class for ostype under test module EX: test_loadbalance.py.  I am surprised that you are receiving a "featured" and "builtin" template as windows template as output for this function. We are explicitly verifiying the template type as "BUILTIN" to retrieve the template information. So, a windows template cannot be a BUILTIN Template. Either it could be a bug in this function, or something with API. But, to double confirm, Can you please check whats the template information you are retrieving from this function matching with listTemplates API output( run either from your browser or script )  passing the same arguments as passed inside get_template? 

Inside if we see, basically it gets the id matching with that ostype description using "listOsTypes"  and then use "listTemplates" command. So, this template is used to deploy the vm.  As far as i know, a builtin template cannot be a windows template?  Here, we use a featured and builtin template along with description filter passed. So, please check whether the template you are retrieving is windows or otherwise. Check for the field ostypename for the output you receive? Provide the output here for get_template copy pasted with dir(template) for return value? 

2. To double confirm that it is template issue and not any other issue related to ssh like ( firewall\iptables\network connectivity issue) for ssh, please manually check for that particular ip in the test case whether ssh works or not and is not a windows machine? 

3. Run one test case, first by adding a tag EX: "umesh" to the tags list as mentioned below for a particular test case under test module EX: test_loadbalance.py, then  run with nose command passing in tags argument mentioned below.

 @attr(tags = ["advanced", "advancedns", "smoke", "umesh"])
    def test_01_create_lb_rule_src_nat(self):

nosetests-2.7 -v --with-marvin --marvin-config=/root/softwares/cscode/setup/dev/advanced.cfg --load -a -w /root/softwares/cscode/test/integration/smoke/ -a tags=umesh

Let me know.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com]
Sent: Tuesday, January 14, 2014 7:02 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

I re-installed the marvin today to get the latest code.
I am again facing the same problem in get_template. It is returning the windows template and creating the windows VM. Hence when it tries to do SSH for VM, it fails.

I have also build the cloudstack to get the latest code for Marvin.

PFA the script logs and test_loadbalance script for reference.

Also, do let me know if I am missing some configuration or anything...

Just an FYI.. I have executed 35 scripts in smoke test directory. Out of 35 scripts executed, 17-PASS, 18-FAIL.
Around 50% failure are due to SSH related issue.

Thanks and Regards
-- Umesh Kute


On Fri, Jan 10, 2014 at 5:53 PM, Santhosh Edukulla <sa...@citrix.com>> wrote:
1. As such because of  bug in get_template, you are getting windows machine in your setup and then ssh is tried in test module, so you are getting the error.

2. Now, to overcome, just checkout the latest marvin, it should have a fix.

Note: It still has some other issues, but you can continue with your testing further. Let us know.

Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>]
Sent: Friday, January 10, 2014 5:19 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

So far i have found the failure on following scripts:
1. test_loadbalance
2. test_network
3. test_nic

In runinfo.txt log it is stuck at the step:
SSH into VM (IPaddress: 10.1.1.55) & NAT Rule (Public IP: 207.x.x.x)

PFA the Marvin logs for the test_loadbalance.py script.

I have modified the following entry in the script i.e. provided the correct template name which is present.
"ostype": "CentOS 6.4 (64-bit)",
#"ostype": "CentOS 5.3 (64-bit)",

Please let me know for your comments.

Thanks and Regards
-- Umesh Kute



On Fri, Jan 10, 2014 at 2:57 PM, Santhosh Edukulla <sa...@citrix.com>>> wrote:
You can log the bug for this. We have fixed few other issues along with this in a private branch. Will soon merge with ACS. If you need a temporary fix, let me know.

Question : Related to ssh issue, ssh to vm failing at which part? Can you add some information related to ssh failure which test module, which case etc? This may be related\unrelated to the above issue. We can check to see the issue is either same\different.

Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>]
Sent: Friday, January 10, 2014 4:21 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks a lot Santhosh For your response.

Sorry for delay.. But is there any workaround for this issue? Because as i mentioned, even if os type is provided as "ostype": 'CentOS 6.4 (64-bit)' it is picking up the first one in list i.e. Windows Server 2008 R2 Enterprise.
So some of the scripts which required to SSH into VM are failing.

Can I get the JIRA ID for this issue to track?

Thanks and Regards
-- Umesh Kute


On Fri, Jan 3, 2014 at 5:19 PM, Santhosh Edukulla <sa...@citrix.com>>>> wrote:
Umesh,

This could be probably due to the bug under get_template function under marvin/integration/lib/common.py. Though, the ostype description is used and corresponding id is retrieved.

But the later part, listTemplate API call returning the list and we are picking up either the template which is ready or matching with id we retrieved. This case is what could be causing the issue you mentioned.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>]
Sent: Friday, January 03, 2014 5:04 AM
To: Santhosh Edukulla; users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks for your help Santhosh!!!

You are right...
The public IP address range was exhausted. After cleaning up the resources, I was able to run the sample script "test_deploy_vm.py" successfully.

One question - i have provided the "ostype": 'CentOS 6.4 (64-bit)'. What is the use of this parameter?

When observed in management server logs and on cloudstack UI (while running script), VM was created of type: "Windows Server 2008 R2 Enterprise with SQL 2012 Web Edition". This is the first one in the list.

Does it choose the one which we provided in script or picks it from the template list that is returned as a result of response to listTemplate API call?

Thanks and Regards
-- Umesh Kute


On Thu, Jan 2, 2014 at 7:22 PM, Santhosh Edukulla <sa...@citrix.com>>>>> wrote:
Umesh,

1. It seems you have exhausted few of CloudStack Resources. These resources usage should show up on your cloudstack dashboard. Anything appears in Red are exhausted resources.

2. Few of the cases could be EX: Guest VM IPs\Management ip addresses  are exhausted,

3. Check for these resources in Red on your dashboard EX: http://localhost:8080/client/->Dashboard and clean up them or add new resources.


Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>]
Sent: Thursday, January 02, 2014 7:06 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thank you once again Santhosh & Chandan.

I have gone through the management server logs. The deployment of VM got fired to the setup correctly and there are couple of errors in the management-server log.
I am summarizing those below:

test data in "test_deploy_vm.py"
 def __init__(self):
        self.testdata = {
            #data to create an account
            "account": {
                "email": "test@test.com<ma...@test.com>>>>>",
                "firstname": "Test",
                "lastname": "User",
                "username": "test",
                "password": "password",
            },
            #data reqd for virtual machine creation
            "virtual_machine" : {
                "name" : "testvmshr",
                "displayname" : "Test VM shr",
            },
            #small service offering
            "service_offering": {
                "small": {
                    "name": "SOSmall",
                    "displaytext": "Small Instance",
                    "cpunumber": 1,
                    "cpuspeed": 2000,
                    "memory": 1024,
                },
            },
            "ostype": 'CentOS 6.4 (64-bit)',
        }


1. Account is successfully created
2. Service offering is successfully created
3. Management server logs - management-server.log has following error:


2014-01-02 01:43:40,693 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Lock is released for network Ntwk[326|Guest|15] as a part of network shutdown
2014-01-02 01:43:40,695 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Lock is released for network id 326 as a part of network implement
2014-01-02 01:43:40,695 INFO  [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Insufficient capacity
com.cloud.exception.InsufficientAddressCapacityException: Insufficient address capacityScope=interface com.cloud.dc.DataCenter; id=1
at com.cloud.network.NetworkManagerImpl.fetchNewPublicIp(NetworkManagerImpl.java:479)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.assignDedicateIpAddress(NetworkManagerImpl.java:613)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.assignSourceNatIpAddressToGuestNetwork(NetworkManagerImpl.java:582)
at com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:2013)
at com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1939)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2120)
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:887)
at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2014-01-02 01:43:40,703 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Cleaning up resources for the vm VM[User|testvmshr] in Starting state

4. When i checked the database for the network id 326 in table "networks", it has following entry:

| 326 | test-TestDeployVM-test_deploy_vm-QQ91N0-network | b7cb9e31-835f-47e3-9585-97e3b4084e4d | test-TestDeployVM-test_deploy_vm-QQ91N0-network | Guest        | Vlan                  | NULL          | 10.1.1.1       | 10.1.1.0/24<http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24>     | Dhcp   |                  15 |                 200 |              1 | ExternalGuestNetworkGuru | Destroy     |     326 |         1 |        305 | 8.8.8.8 | 8.8.4.4 | NULL      |          0 | Account  | cs131cloud.internal | ecf5b617-04da-469b-b378-f53e05d8cc53 | Isolated   |                0 | 2014-01-02 06:43:39 | 2014-01-02 06:43:46 |                 0 |   NULL | NULL        | NULL     | NULL         |               1 |           NULL |


Basically it tries to create a network offering (id=15) : "HA Isolated Network With Source Nat"


5. I think the script creates a network shown in above table: "test-TestDeployVM-test_deploy_vm-QQ91N0-network".

I am not sure why it still gives the Insufficient address capacityScope exception.

6. One more thing i observed. I have provided the "ostype": 'CentOS 6.4 (64-bit)'. But in DeployVMCmd it uses the template id: "03ffb96f-2cfa-11e3-a4f0-f245a5b3ba0f" which is for template "Windows Server 2008 R2 Enterprise with SQL 2012 Web Edition".


I am attaching the management-server logs and script logs for references.

If somebody can help me what's wrong here, would really be helpful.


Thanks and Regards
-- Umesh Kute


On Thu, Jan 2, 2014 at 2:59 PM, Santhosh Edukulla <sa...@citrix.com>>>>>> wrote:
1. Is it still failing post this registration?

2. If yes, may be you can verify\provide the management server logs.
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>]
Sent: Thursday, January 02, 2014 4:16 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks Santhosh.
Yes, I have registered the following template which i am using.

"ostype": 'CentOS 6.4 (64-bit)',

Thanks and Regards
-- Umesh Kute


On Mon, Dec 30, 2013 at 5:50 PM, Santhosh Edukulla <
santhosh.edukulla@citrix.com<ma...@citrix.com>>>>>> wrote:

> Umesh,
>
> One question : Did you registered the template for ostype:     "ostype":
> 'CentOS 5.3 (64-bit)'?
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>>]
> Sent: Monday, December 30, 2013 6:32 AM
> To: Chandan Purushothama
> Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi Chandan,
> Thanks for your response.
> I have the latest Marvin repository (December 20th). I am able to proceed
> further. There was an issue of firewall for that machine and it got
> resolved.
>
> But now i am getting another error when i tried to run the script
> "test_deploy_vm.py"
>
> I have attached the log. Can somebody please have a look on it and help me
> in resolving the issue?
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> test_deploy_vm (integration.smoke.test_deploy_vm.TestDeployVM): CRITICAL:
> EXCEPTION: test_deploy_vm: Traceback (most recent call last):
>   File "/usr/local/lib/python2.7/unittest/case.py", line 327, in run
>     testMethod()
>   File
> "/DataDisk/temp/cloudstack/test/integration/smoke/test_deploy_vm.py", line
> 116, in test_deploy_vm
>     templateid=self.template.id<http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id>
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py",
> line 415, in create
>     virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> line 593, in deployVirtualMachine
>     response = self.connection.marvinRequest(command,
> response_type=response, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 280, in marvinRequest
>     response = self.poll(asyncJobId, response_type)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 86, in poll
>     "asyncquery", asyncResonse.jobresult)
> cloudstackAPIException: Execute cmd: asyncquery failed, due to: {errorcode
> : 533, errortext : u'Unable to create a deployment for VM[User|testvmshr]'}
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> PFA entire logs.
>
> Please let me know in case if anything is required.
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Sun, Dec 29, 2013 at 10:32 PM, Chandan Purushothama <
> Chandan.Purushothama@citrix.com<ma...@citrix.com>>>>>>>
> wrote:
>
> Hello Umesh,
>
> I had a similar experience with an older Marvin build. I updated mine to
> the latest and tried again and it worked. I recommend you to kindly try
> again with the latest Marvin build and see if you are able to work with the
> automation framework,
>
> Thank you,
> Chandan
>
>
> -------- Original message --------
> From: umesh kute
> Date:12/26/2013 12:29 AM (GMT-08:00)
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>,Sudha
> Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi All,
> I have created a Marvin setup on CentOS6.3 by following the document:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
>
> All the pre-requisites are installed successfully.
>
> I tried to run the sample script test_deploy_vm.py
> (cloudstack/test/integration/smoke/), I am getting following error:
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> [root@localhost smoke]# nosetests --with-marvin
> --marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg --load
> test_deploy_vm.py
>
>  Exception Occurred Under __deployDC :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
> Traceback (most recent call last):
>   File "/usr/local/bin/nosetests", line 9, in <module>
>     load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 118, in __init__
>     **extra_args)
>   File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
>     self.runTests()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 197, in runTests
>     result = self.testRunner.run(self.test)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 61, in run
>     test(result)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 45, in __call__
>     return self.run(*arg, **kwarg)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 138, in run
>     result.addError(self, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
> line 124, in addError
>     plugin_handled = plugins.handleError(self.test, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 99, in __call__
>     return self.call(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 167, in simple
>     result = meth(*arg, **kw)
>   File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
> line 155, in handleError
>     self.tcRunLogger.fatal("%s: %s: %s" %
> AttributeError: 'NoneType' object has no attribute 'fatal'
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> The logs are generated at /tmp and the log has following error.
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
> {'account': 'admin'}
> 2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
> http://10.88.91.100:8096/client/api :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Please note: I have opened the integration port 8096 on management server.
> Also, changed the global settings integration.api.port
> on cloudstack GUI to 8096 and restarted the management server.
>
> Still I am getting the above issue. I am not sure if i missed any
> configuration.
>
> Can somebody please help me with resolution of this issue?
> Appreciate your help here!!!
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <um...@gmail.com>>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>>> wrote:
>
> > Thanks a lot Sudha for your quick response.
> > I will setup the Marvin on local machine and get back in case if I face
> > any challenges in setup.
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> >
> > On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
> > sudha.ponnaganti@citrix.com<ma...@citrix.com>>>>>>> wrote:
> >
> >> Hi Umesh,
> >>
> >> Looks like you have started on right track - Marvin is the framework to
> >> use for functional or integration automation.
> >> There are sizable number of test cases exist and you can review them.
> >>  There are some wiki pages already written explaining Marvin [1]. Also
> best
> >> practices are published by community as well [2]. You can contribute to
> it
> >> as much as you can.
> >>
> >> Besides this, there is Junit framework (unit Test), Selenium framework
> >> (UI automation) which are not as popular as Marvin. Marvin is perfect
> for
> >> majority of the validation. You can use simulator as well with Marvin.
> >>
> >> Please do pursue these and post questions to the community if you run in
> >> to any issues in setting up env and running tests. There are jobs setup
> by
> >> various community members to test Master or current releases in various
> >> labs and can help answer questions.
> >>
> >> [1]
> >>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> >>
> >>
> >> Thanks
> >> /Sudha
> >>
> >>
> >> -----Original Message-----
> >> From: umesh kute [mailto:umeshvkute@gmail.com<ma...@gmail.com>>>>>]
> >> Sent: Saturday, December 07, 2013 10:29 PM
> >> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>>
> >> Subject: Regarding cloudstack automation
> >>
> >> Hi All,
> >> Good morning !!!
> >> I am working as QA engineer and I am new to the cloudstack community.
> >> We have started using cloudstack and deployed it in our infrastructure.
> >>
> >> Can somebody please help me in identifying the good automation
> >> framework/tool/anything? The main intention is we want to automate the
> >> infrastructure validation related cases (for e.g. create/update/delete
> >> cases for instances, project, network, etc...)
> >>
> >> It would be good if you can help in identifying it.
> >>
> >> Please note: I have gone through cloudmonkey. But i haven't found much
> >> help on it. May be i need to search a bit more.. I am also going through
> >> the marvin and planning to setup it. If apart from these two, if anyone
> has
> >> different view please suggest.
> >>
> >> Also, if somebody has any pointers on cloudmonkey and marvin or any more
> >> info on this (like, if it would suffice the infrastructure validation
> >> related cases i mentioned above) any pros/cons would really be helpful
> for
> >> me...
> >>
> >> Appreciate any help on this and looking forward for the response on
> >> this!!!
> >>
> >> Thanks and Regards
> >> -- Umesh Kute
> >>
> >
> >
>
>

Re: Regarding cloudstack automation

[umesh kute <um...@gmail.com>]

I re-installed the marvin today to get the latest code.
I am again facing the same problem in get_template. It is returning the
windows template and creating the windows VM. Hence when it tries to do SSH
for VM, it fails.

I have also build the cloudstack to get the latest code for Marvin.

PFA the script logs and test_loadbalance script for reference.

Also, do let me know if I am missing some configuration or anything...

Just an FYI.. I have executed 35 scripts in smoke test directory. Out of 35
scripts executed, 17-PASS, 18-FAIL.
Around 50% failure are due to SSH related issue.

Thanks and Regards
-- Umesh Kute


On Fri, Jan 10, 2014 at 5:53 PM, Santhosh Edukulla <
santhosh.edukulla@citrix.com> wrote:

> 1. As such because of  bug in get_template, you are getting windows
> machine in your setup and then ssh is tried in test module, so you are
> getting the error.
>
> 2. Now, to overcome, just checkout the latest marvin, it should have a fix.
>
> Note: It still has some other issues, but you can continue with your
> testing further. Let us know.
>
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com]
> Sent: Friday, January 10, 2014 5:19 AM
> To: Santhosh Edukulla
> Cc: users@cloudstack.apache.org; Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> So far i have found the failure on following scripts:
> 1. test_loadbalance
> 2. test_network
> 3. test_nic
>
> In runinfo.txt log it is stuck at the step:
> SSH into VM (IPaddress: 10.1.1.55) & NAT Rule (Public IP: 207.x.x.x)
>
> PFA the Marvin logs for the test_loadbalance.py script.
>
> I have modified the following entry in the script i.e. provided the
> correct template name which is present.
> "ostype": "CentOS 6.4 (64-bit)",
> #"ostype": "CentOS 5.3 (64-bit)",
>
> Please let me know for your comments.
>
> Thanks and Regards
> -- Umesh Kute
>
>
>
> On Fri, Jan 10, 2014 at 2:57 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com>> wrote:
> You can log the bug for this. We have fixed few other issues along with
> this in a private branch. Will soon merge with ACS. If you need a temporary
> fix, let me know.
>
> Question : Related to ssh issue, ssh to vm failing at which part? Can you
> add some information related to ssh failure which test module, which case
> etc? This may be related\unrelated to the above issue. We can check to see
> the issue is either same\different.
>
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>]
> Sent: Friday, January 10, 2014 4:21 AM
> To: Santhosh Edukulla
> Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>;
> Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thanks a lot Santhosh For your response.
>
> Sorry for delay.. But is there any workaround for this issue? Because as i
> mentioned, even if os type is provided as "ostype": 'CentOS 6.4 (64-bit)'
> it is picking up the first one in list i.e. Windows Server 2008 R2
> Enterprise.
> So some of the scripts which required to SSH into VM are failing.
>
> Can I get the JIRA ID for this issue to track?
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Fri, Jan 3, 2014 at 5:19 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>>> wrote:
> Umesh,
>
> This could be probably due to the bug under get_template function under
> marvin/integration/lib/common.py. Though, the ostype description is used
> and corresponding id is retrieved.
>
> But the later part, listTemplate API call returning the list and we are
> picking up either the template which is ready or matching with id we
> retrieved. This case is what could be causing the issue you mentioned.
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>>]
> Sent: Friday, January 03, 2014 5:04 AM
> To: Santhosh Edukulla; users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org><mailto:users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>
> Cc: Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thanks for your help Santhosh!!!
>
> You are right...
> The public IP address range was exhausted. After cleaning up the
> resources, I was able to run the sample script "test_deploy_vm.py"
> successfully.
>
> One question - i have provided the "ostype": 'CentOS 6.4 (64-bit)'. What
> is the use of this parameter?
>
> When observed in management server logs and on cloudstack UI (while
> running script), VM was created of type: "Windows Server 2008 R2 Enterprise
> with SQL 2012 Web Edition". This is the first one in the list.
>
> Does it choose the one which we provided in script or picks it from the
> template list that is returned as a result of response to listTemplate API
> call?
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Thu, Jan 2, 2014 at 7:22 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>>>>
> wrote:
> Umesh,
>
> 1. It seems you have exhausted few of CloudStack Resources. These
> resources usage should show up on your cloudstack dashboard. Anything
> appears in Red are exhausted resources.
>
> 2. Few of the cases could be EX: Guest VM IPs\Management ip addresses  are
> exhausted,
>
> 3. Check for these resources in Red on your dashboard EX:
> http://localhost:8080/client/->Dashboard and clean up them or add new
> resources.
>
>
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>]
> Sent: Thursday, January 02, 2014 7:06 AM
> To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><ma...@cloudstack.apache.org>>>
> Cc: Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thank you once again Santhosh & Chandan.
>
> I have gone through the management server logs. The deployment of VM got
> fired to the setup correctly and there are couple of errors in the
> management-server log.
> I am summarizing those below:
>
> test data in "test_deploy_vm.py"
>  def __init__(self):
>         self.testdata = {
>             #data to create an account
>             "account": {
>                 "email": "test@test.com<ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>><mailto:
> test@test.com<ma...@test.com><mailto:test@test.com<mailto:
> test@test.com>><ma...@test.com><mailto:
> test@test.com<ma...@test.com>>>>",
>                 "firstname": "Test",
>                 "lastname": "User",
>                 "username": "test",
>                 "password": "password",
>             },
>             #data reqd for virtual machine creation
>             "virtual_machine" : {
>                 "name" : "testvmshr",
>                 "displayname" : "Test VM shr",
>             },
>             #small service offering
>             "service_offering": {
>                 "small": {
>                     "name": "SOSmall",
>                     "displaytext": "Small Instance",
>                     "cpunumber": 1,
>                     "cpuspeed": 2000,
>                     "memory": 1024,
>                 },
>             },
>             "ostype": 'CentOS 6.4 (64-bit)',
>         }
>
>
> 1. Account is successfully created
> 2. Service offering is successfully created
> 3. Management server logs - management-server.log has following error:
>
>
> 2014-01-02 01:43:40,693 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Lock is released for network Ntwk[326|Guest|15] as a part of network
> shutdown
> 2014-01-02 01:43:40,695 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Lock is released for network id 326 as a part of network implement
> 2014-01-02 01:43:40,695 INFO  [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Insufficient capacity
> com.cloud.exception.InsufficientAddressCapacityException: Insufficient
> address capacityScope=interface com.cloud.dc.DataCenter; id=1
> at
> com.cloud.network.NetworkManagerImpl.fetchNewPublicIp(NetworkManagerImpl.java:479)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.network.NetworkManagerImpl.assignDedicateIpAddress(NetworkManagerImpl.java:613)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.network.NetworkManagerImpl.assignSourceNatIpAddressToGuestNetwork(NetworkManagerImpl.java:582)
> at
> com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:2013)
> at
> com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1939)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2120)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:887)
> at
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:679)
> 2014-01-02 01:43:40,703 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Cleaning up resources for the vm VM[User|testvmshr] in Starting state
>
> 4. When i checked the database for the network id 326 in table "networks",
> it has following entry:
>
> | 326 | test-TestDeployVM-test_deploy_vm-QQ91N0-network |
> b7cb9e31-835f-47e3-9585-97e3b4084e4d |
> test-TestDeployVM-test_deploy_vm-QQ91N0-network | Guest        | Vlan
>            | NULL          | 10.1.1.1       | 10.1.1.0/24<
> http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><
> http://10.1.1.0/24>     | Dhcp   |                  15 |
> 200 |              1 | ExternalGuestNetworkGuru | Destroy     |     326 |
>       1 |        305 | 8.8.8.8 | 8.8.4.4 | NULL      |          0 | Account
>  | cs131cloud.internal | ecf5b617-04da-469b-b378-f53e05d8cc53 | Isolated
> |                0 | 2014-01-02 06:43:39 | 2014-01-02 06:43:46 |
>       0 |   NULL | NULL        | NULL     | NULL         |               1
> |           NULL |
>
>
> Basically it tries to create a network offering (id=15) : "HA Isolated
> Network With Source Nat"
>
>
> 5. I think the script creates a network shown in above table:
> "test-TestDeployVM-test_deploy_vm-QQ91N0-network".
>
> I am not sure why it still gives the Insufficient address capacityScope
> exception.
>
> 6. One more thing i observed. I have provided the "ostype": 'CentOS 6.4
> (64-bit)'. But in DeployVMCmd it uses the template id:
> "03ffb96f-2cfa-11e3-a4f0-f245a5b3ba0f" which is for template "Windows
> Server 2008 R2 Enterprise with SQL 2012 Web Edition".
>
>
> I am attaching the management-server logs and script logs for references.
>
> If somebody can help me what's wrong here, would really be helpful.
>
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Thu, Jan 2, 2014 at 2:59 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>>> wrote:
> 1. Is it still failing post this registration?
>
> 2. If yes, may be you can verify\provide the management server logs.
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>]
> Sent: Thursday, January 02, 2014 4:16 AM
> To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>
> Cc: Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thanks Santhosh.
> Yes, I have registered the following template which i am using.
>
> "ostype": 'CentOS 6.4 (64-bit)',
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Mon, Dec 30, 2013 at 5:50 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<mailto:santhosh.edukulla@citrix.com
> >>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com><mailto:santhosh.edukulla@citrix.com<mailto:
> santhosh.edukulla@citrix.com>>>>> wrote:
>
> > Umesh,
> >
> > One question : Did you registered the template for ostype:     "ostype":
> > 'CentOS 5.3 (64-bit)'?
> >
> > Regards,
> > Santhosh
> > ________________________________________
> > From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>]
> > Sent: Monday, December 30, 2013 6:32 AM
> > To: Chandan Purushothama
> > Cc: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><ma...@cloudstack.apache.org>>>>;
> Sudha Ponnaganti
> > Subject: Re: Regarding cloudstack automation
> >
> > Hi Chandan,
> > Thanks for your response.
> > I have the latest Marvin repository (December 20th). I am able to proceed
> > further. There was an issue of firewall for that machine and it got
> > resolved.
> >
> > But now i am getting another error when i tried to run the script
> > "test_deploy_vm.py"
> >
> > I have attached the log. Can somebody please have a look on it and help
> me
> > in resolving the issue?
> >
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > test_deploy_vm (integration.smoke.test_deploy_vm.TestDeployVM): CRITICAL:
> > EXCEPTION: test_deploy_vm: Traceback (most recent call last):
> >   File "/usr/local/lib/python2.7/unittest/case.py", line 327, in run
> >     testMethod()
> >   File
> > "/DataDisk/temp/cloudstack/test/integration/smoke/test_deploy_vm.py",
> line
> > 116, in test_deploy_vm
> >     templateid=self.template.id<http://self.template.id><
> http://self.template.id><http://self.template.id><http://self.template.id
> ><http://self.template.id>
> >   File
> > "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py",
> > line 415, in create
> >     virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> > line 593, in deployVirtualMachine
> >     response = self.connection.marvinRequest(command,
> > response_type=response, method=method)
> >   File
> > "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> > line 280, in marvinRequest
> >     response = self.poll(asyncJobId, response_type)
> >   File
> > "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> > line 86, in poll
> >     "asyncquery", asyncResonse.jobresult)
> > cloudstackAPIException: Execute cmd: asyncquery failed, due to:
> {errorcode
> > : 533, errortext : u'Unable to create a deployment for
> VM[User|testvmshr]'}
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > PFA entire logs.
> >
> > Please let me know in case if anything is required.
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> > On Sun, Dec 29, 2013 at 10:32 PM, Chandan Purushothama <
> > Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>>>>>
> > wrote:
> >
> > Hello Umesh,
> >
> > I had a similar experience with an older Marvin build. I updated mine to
> > the latest and tried again and it worked. I recommend you to kindly try
> > again with the latest Marvin build and see if you are able to work with
> the
> > automation framework,
> >
> > Thank you,
> > Chandan
> >
> >
> > -------- Original message --------
> > From: umesh kute
> > Date:12/26/2013 12:29 AM (GMT-08:00)
> > To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>>,Sudha
> > Ponnaganti
> > Subject: Re: Regarding cloudstack automation
> >
> > Hi All,
> > I have created a Marvin setup on CentOS6.3 by following the document:
> >
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> >
> > All the pre-requisites are installed successfully.
> >
> > I tried to run the sample script test_deploy_vm.py
> > (cloudstack/test/integration/smoke/), I am getting following error:
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > [root@localhost smoke]# nosetests --with-marvin
> > --marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg
> --load
> > test_deploy_vm.py
> >
> >  Exception Occurred Under __deployDC :
> > HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> > with url: /client/api?account=admin&command=listUsers&response=json
> (Caused
> > by <class 'socket.error'>: [Errno 110] Connection timed out)
> > Traceback (most recent call last):
> >   File "/usr/local/bin/nosetests", line 9, in <module>
> >     load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> > line 118, in __init__
> >     **extra_args)
> >   File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
> >     self.runTests()
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> > line 197, in runTests
> >     result = self.testRunner.run(self.test)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> > line 61, in run
> >     test(result)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> > line 45, in __call__
> >     return self.run(*arg, **kwarg)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> > line 138, in run
> >     result.addError(self, err)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
> > line 124, in addError
> >     plugin_handled = plugins.handleError(self.test, err)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> > line 99, in __call__
> >     return self.call(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> > line 167, in simple
> >     result = meth(*arg, **kw)
> >   File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
> > line 155, in handleError
> >     self.tcRunLogger.fatal("%s: %s: %s" %
> > AttributeError: 'NoneType' object has no attribute 'fatal'
> >
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > The logs are generated at /tmp and the log has following error.
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > 2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
> > {'account': 'admin'}
> > 2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
> > http://10.88.91.100:8096/client/api :
> > HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> > with url: /client/api?account=admin&command=listUsers&response=json
> (Caused
> > by <class 'socket.error'>: [Errno 110] Connection timed out)
> >
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > Please note: I have opened the integration port 8096 on management
> server.
> > Also, changed the global settings integration.api.port
> > on cloudstack GUI to 8096 and restarted the management server.
> >
> > Still I am getting the above issue. I am not sure if i missed any
> > configuration.
> >
> > Can somebody please help me with resolution of this issue?
> > Appreciate your help here!!!
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> > On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>><mailto:
> > umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>> wrote:
> >
> > > Thanks a lot Sudha for your quick response.
> > > I will setup the Marvin on local machine and get back in case if I face
> > > any challenges in setup.
> > >
> > > Thanks and Regards
> > > -- Umesh Kute
> > >
> > >
> > >
> > > On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
> > > sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>>><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><ma...@citrix.com>>>>>>
> wrote:
> > >
> > >> Hi Umesh,
> > >>
> > >> Looks like you have started on right track - Marvin is the framework
> to
> > >> use for functional or integration automation.
> > >> There are sizable number of test cases exist and you can review them.
> > >>  There are some wiki pages already written explaining Marvin [1]. Also
> > best
> > >> practices are published by community as well [2]. You can contribute
> to
> > it
> > >> as much as you can.
> > >>
> > >> Besides this, there is Junit framework (unit Test), Selenium framework
> > >> (UI automation) which are not as popular as Marvin. Marvin is perfect
> > for
> > >> majority of the validation. You can use simulator as well with Marvin.
> > >>
> > >> Please do pursue these and post questions to the community if you run
> in
> > >> to any issues in setting up env and running tests. There are jobs
> setup
> > by
> > >> various community members to test Master or current releases in
> various
> > >> labs and can help answer questions.
> > >>
> > >> [1]
> > >>
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> > >>
> > >>
> > >> Thanks
> > >> /Sudha
> > >>
> > >>
> > >> -----Original Message-----
> > >> From: umesh kute [mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>>]
> > >> Sent: Saturday, December 07, 2013 10:29 PM
> > >> To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>>
> > >> Subject: Regarding cloudstack automation
> > >>
> > >> Hi All,
> > >> Good morning !!!
> > >> I am working as QA engineer and I am new to the cloudstack community.
> > >> We have started using cloudstack and deployed it in our
> infrastructure.
> > >>
> > >> Can somebody please help me in identifying the good automation
> > >> framework/tool/anything? The main intention is we want to automate the
> > >> infrastructure validation related cases (for e.g. create/update/delete
> > >> cases for instances, project, network, etc...)
> > >>
> > >> It would be good if you can help in identifying it.
> > >>
> > >> Please note: I have gone through cloudmonkey. But i haven't found much
> > >> help on it. May be i need to search a bit more.. I am also going
> through
> > >> the marvin and planning to setup it. If apart from these two, if
> anyone
> > has
> > >> different view please suggest.
> > >>
> > >> Also, if somebody has any pointers on cloudmonkey and marvin or any
> more
> > >> info on this (like, if it would suffice the infrastructure validation
> > >> related cases i mentioned above) any pros/cons would really be helpful
> > for
> > >> me...
> > >>
> > >> Appreciate any help on this and looking forward for the response on
> > >> this!!!
> > >>
> > >> Thanks and Regards
> > >> -- Umesh Kute
> > >>
> > >
> > >
> >
> >
>
>
>
>

RE: Regarding cloudstack automation

[Santhosh Edukulla <sa...@citrix.com>]

1. As such because of  bug in get_template, you are getting windows machine in your setup and then ssh is tried in test module, so you are getting the error.

2. Now, to overcome, just checkout the latest marvin, it should have a fix. 

Note: It still has some other issues, but you can continue with your testing further. Let us know.

Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com]
Sent: Friday, January 10, 2014 5:19 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

So far i have found the failure on following scripts:
1. test_loadbalance
2. test_network
3. test_nic

In runinfo.txt log it is stuck at the step:
SSH into VM (IPaddress: 10.1.1.55) & NAT Rule (Public IP: 207.x.x.x)

PFA the Marvin logs for the test_loadbalance.py script.

I have modified the following entry in the script i.e. provided the correct template name which is present.
"ostype": "CentOS 6.4 (64-bit)",
#"ostype": "CentOS 5.3 (64-bit)",

Please let me know for your comments.

Thanks and Regards
-- Umesh Kute



On Fri, Jan 10, 2014 at 2:57 PM, Santhosh Edukulla <sa...@citrix.com>> wrote:
You can log the bug for this. We have fixed few other issues along with this in a private branch. Will soon merge with ACS. If you need a temporary fix, let me know.

Question : Related to ssh issue, ssh to vm failing at which part? Can you add some information related to ssh failure which test module, which case etc? This may be related\unrelated to the above issue. We can check to see the issue is either same\different.

Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>]
Sent: Friday, January 10, 2014 4:21 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks a lot Santhosh For your response.

Sorry for delay.. But is there any workaround for this issue? Because as i mentioned, even if os type is provided as "ostype": 'CentOS 6.4 (64-bit)' it is picking up the first one in list i.e. Windows Server 2008 R2 Enterprise.
So some of the scripts which required to SSH into VM are failing.

Can I get the JIRA ID for this issue to track?

Thanks and Regards
-- Umesh Kute


On Fri, Jan 3, 2014 at 5:19 PM, Santhosh Edukulla <sa...@citrix.com>>> wrote:
Umesh,

This could be probably due to the bug under get_template function under marvin/integration/lib/common.py. Though, the ostype description is used and corresponding id is retrieved.

But the later part, listTemplate API call returning the list and we are picking up either the template which is ready or matching with id we retrieved. This case is what could be causing the issue you mentioned.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>]
Sent: Friday, January 03, 2014 5:04 AM
To: Santhosh Edukulla; users@cloudstack.apache.org<ma...@cloudstack.apache.org>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks for your help Santhosh!!!

You are right...
The public IP address range was exhausted. After cleaning up the resources, I was able to run the sample script "test_deploy_vm.py" successfully.

One question - i have provided the "ostype": 'CentOS 6.4 (64-bit)'. What is the use of this parameter?

When observed in management server logs and on cloudstack UI (while running script), VM was created of type: "Windows Server 2008 R2 Enterprise with SQL 2012 Web Edition". This is the first one in the list.

Does it choose the one which we provided in script or picks it from the template list that is returned as a result of response to listTemplate API call?

Thanks and Regards
-- Umesh Kute


On Thu, Jan 2, 2014 at 7:22 PM, Santhosh Edukulla <sa...@citrix.com>>>> wrote:
Umesh,

1. It seems you have exhausted few of CloudStack Resources. These resources usage should show up on your cloudstack dashboard. Anything appears in Red are exhausted resources.

2. Few of the cases could be EX: Guest VM IPs\Management ip addresses  are exhausted,

3. Check for these resources in Red on your dashboard EX: http://localhost:8080/client/->Dashboard and clean up them or add new resources.


Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>]
Sent: Thursday, January 02, 2014 7:06 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thank you once again Santhosh & Chandan.

I have gone through the management server logs. The deployment of VM got fired to the setup correctly and there are couple of errors in the management-server log.
I am summarizing those below:

test data in "test_deploy_vm.py"
 def __init__(self):
        self.testdata = {
            #data to create an account
            "account": {
                "email": "test@test.com<ma...@test.com>>>>",
                "firstname": "Test",
                "lastname": "User",
                "username": "test",
                "password": "password",
            },
            #data reqd for virtual machine creation
            "virtual_machine" : {
                "name" : "testvmshr",
                "displayname" : "Test VM shr",
            },
            #small service offering
            "service_offering": {
                "small": {
                    "name": "SOSmall",
                    "displaytext": "Small Instance",
                    "cpunumber": 1,
                    "cpuspeed": 2000,
                    "memory": 1024,
                },
            },
            "ostype": 'CentOS 6.4 (64-bit)',
        }


1. Account is successfully created
2. Service offering is successfully created
3. Management server logs - management-server.log has following error:


2014-01-02 01:43:40,693 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Lock is released for network Ntwk[326|Guest|15] as a part of network shutdown
2014-01-02 01:43:40,695 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Lock is released for network id 326 as a part of network implement
2014-01-02 01:43:40,695 INFO  [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Insufficient capacity
com.cloud.exception.InsufficientAddressCapacityException: Insufficient address capacityScope=interface com.cloud.dc.DataCenter; id=1
at com.cloud.network.NetworkManagerImpl.fetchNewPublicIp(NetworkManagerImpl.java:479)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.assignDedicateIpAddress(NetworkManagerImpl.java:613)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.assignSourceNatIpAddressToGuestNetwork(NetworkManagerImpl.java:582)
at com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:2013)
at com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1939)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2120)
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:887)
at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2014-01-02 01:43:40,703 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Cleaning up resources for the vm VM[User|testvmshr] in Starting state

4. When i checked the database for the network id 326 in table "networks", it has following entry:

| 326 | test-TestDeployVM-test_deploy_vm-QQ91N0-network | b7cb9e31-835f-47e3-9585-97e3b4084e4d | test-TestDeployVM-test_deploy_vm-QQ91N0-network | Guest        | Vlan                  | NULL          | 10.1.1.1       | 10.1.1.0/24<http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24>     | Dhcp   |                  15 |                 200 |              1 | ExternalGuestNetworkGuru | Destroy     |     326 |         1 |        305 | 8.8.8.8 | 8.8.4.4 | NULL      |          0 | Account  | cs131cloud.internal | ecf5b617-04da-469b-b378-f53e05d8cc53 | Isolated   |                0 | 2014-01-02 06:43:39 | 2014-01-02 06:43:46 |                 0 |   NULL | NULL        | NULL     | NULL         |               1 |           NULL |


Basically it tries to create a network offering (id=15) : "HA Isolated Network With Source Nat"


5. I think the script creates a network shown in above table: "test-TestDeployVM-test_deploy_vm-QQ91N0-network".

I am not sure why it still gives the Insufficient address capacityScope exception.

6. One more thing i observed. I have provided the "ostype": 'CentOS 6.4 (64-bit)'. But in DeployVMCmd it uses the template id: "03ffb96f-2cfa-11e3-a4f0-f245a5b3ba0f" which is for template "Windows Server 2008 R2 Enterprise with SQL 2012 Web Edition".


I am attaching the management-server logs and script logs for references.

If somebody can help me what's wrong here, would really be helpful.


Thanks and Regards
-- Umesh Kute


On Thu, Jan 2, 2014 at 2:59 PM, Santhosh Edukulla <sa...@citrix.com>>>>> wrote:
1. Is it still failing post this registration?

2. If yes, may be you can verify\provide the management server logs.
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>]
Sent: Thursday, January 02, 2014 4:16 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks Santhosh.
Yes, I have registered the following template which i am using.

"ostype": 'CentOS 6.4 (64-bit)',

Thanks and Regards
-- Umesh Kute


On Mon, Dec 30, 2013 at 5:50 PM, Santhosh Edukulla <
santhosh.edukulla@citrix.com<ma...@citrix.com>>>>> wrote:

> Umesh,
>
> One question : Did you registered the template for ostype:     "ostype":
> 'CentOS 5.3 (64-bit)'?
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>>]
> Sent: Monday, December 30, 2013 6:32 AM
> To: Chandan Purushothama
> Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi Chandan,
> Thanks for your response.
> I have the latest Marvin repository (December 20th). I am able to proceed
> further. There was an issue of firewall for that machine and it got
> resolved.
>
> But now i am getting another error when i tried to run the script
> "test_deploy_vm.py"
>
> I have attached the log. Can somebody please have a look on it and help me
> in resolving the issue?
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> test_deploy_vm (integration.smoke.test_deploy_vm.TestDeployVM): CRITICAL:
> EXCEPTION: test_deploy_vm: Traceback (most recent call last):
>   File "/usr/local/lib/python2.7/unittest/case.py", line 327, in run
>     testMethod()
>   File
> "/DataDisk/temp/cloudstack/test/integration/smoke/test_deploy_vm.py", line
> 116, in test_deploy_vm
>     templateid=self.template.id<http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id>
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py",
> line 415, in create
>     virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> line 593, in deployVirtualMachine
>     response = self.connection.marvinRequest(command,
> response_type=response, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 280, in marvinRequest
>     response = self.poll(asyncJobId, response_type)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 86, in poll
>     "asyncquery", asyncResonse.jobresult)
> cloudstackAPIException: Execute cmd: asyncquery failed, due to: {errorcode
> : 533, errortext : u'Unable to create a deployment for VM[User|testvmshr]'}
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> PFA entire logs.
>
> Please let me know in case if anything is required.
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Sun, Dec 29, 2013 at 10:32 PM, Chandan Purushothama <
> Chandan.Purushothama@citrix.com<ma...@citrix.com>>>>>>
> wrote:
>
> Hello Umesh,
>
> I had a similar experience with an older Marvin build. I updated mine to
> the latest and tried again and it worked. I recommend you to kindly try
> again with the latest Marvin build and see if you are able to work with the
> automation framework,
>
> Thank you,
> Chandan
>
>
> -------- Original message --------
> From: umesh kute
> Date:12/26/2013 12:29 AM (GMT-08:00)
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>,Sudha
> Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi All,
> I have created a Marvin setup on CentOS6.3 by following the document:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
>
> All the pre-requisites are installed successfully.
>
> I tried to run the sample script test_deploy_vm.py
> (cloudstack/test/integration/smoke/), I am getting following error:
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> [root@localhost smoke]# nosetests --with-marvin
> --marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg --load
> test_deploy_vm.py
>
>  Exception Occurred Under __deployDC :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
> Traceback (most recent call last):
>   File "/usr/local/bin/nosetests", line 9, in <module>
>     load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 118, in __init__
>     **extra_args)
>   File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
>     self.runTests()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 197, in runTests
>     result = self.testRunner.run(self.test)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 61, in run
>     test(result)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 45, in __call__
>     return self.run(*arg, **kwarg)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 138, in run
>     result.addError(self, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
> line 124, in addError
>     plugin_handled = plugins.handleError(self.test, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 99, in __call__
>     return self.call(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 167, in simple
>     result = meth(*arg, **kw)
>   File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
> line 155, in handleError
>     self.tcRunLogger.fatal("%s: %s: %s" %
> AttributeError: 'NoneType' object has no attribute 'fatal'
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> The logs are generated at /tmp and the log has following error.
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
> {'account': 'admin'}
> 2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
> http://10.88.91.100:8096/client/api :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Please note: I have opened the integration port 8096 on management server.
> Also, changed the global settings integration.api.port
> on cloudstack GUI to 8096 and restarted the management server.
>
> Still I am getting the above issue. I am not sure if i missed any
> configuration.
>
> Can somebody please help me with resolution of this issue?
> Appreciate your help here!!!
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <um...@gmail.com>>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>>> wrote:
>
> > Thanks a lot Sudha for your quick response.
> > I will setup the Marvin on local machine and get back in case if I face
> > any challenges in setup.
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> >
> > On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
> > sudha.ponnaganti@citrix.com<ma...@citrix.com>>>>>> wrote:
> >
> >> Hi Umesh,
> >>
> >> Looks like you have started on right track - Marvin is the framework to
> >> use for functional or integration automation.
> >> There are sizable number of test cases exist and you can review them.
> >>  There are some wiki pages already written explaining Marvin [1]. Also
> best
> >> practices are published by community as well [2]. You can contribute to
> it
> >> as much as you can.
> >>
> >> Besides this, there is Junit framework (unit Test), Selenium framework
> >> (UI automation) which are not as popular as Marvin. Marvin is perfect
> for
> >> majority of the validation. You can use simulator as well with Marvin.
> >>
> >> Please do pursue these and post questions to the community if you run in
> >> to any issues in setting up env and running tests. There are jobs setup
> by
> >> various community members to test Master or current releases in various
> >> labs and can help answer questions.
> >>
> >> [1]
> >>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> >>
> >>
> >> Thanks
> >> /Sudha
> >>
> >>
> >> -----Original Message-----
> >> From: umesh kute [mailto:umeshvkute@gmail.com<ma...@gmail.com>>>>]
> >> Sent: Saturday, December 07, 2013 10:29 PM
> >> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>>
> >> Subject: Regarding cloudstack automation
> >>
> >> Hi All,
> >> Good morning !!!
> >> I am working as QA engineer and I am new to the cloudstack community.
> >> We have started using cloudstack and deployed it in our infrastructure.
> >>
> >> Can somebody please help me in identifying the good automation
> >> framework/tool/anything? The main intention is we want to automate the
> >> infrastructure validation related cases (for e.g. create/update/delete
> >> cases for instances, project, network, etc...)
> >>
> >> It would be good if you can help in identifying it.
> >>
> >> Please note: I have gone through cloudmonkey. But i haven't found much
> >> help on it. May be i need to search a bit more.. I am also going through
> >> the marvin and planning to setup it. If apart from these two, if anyone
> has
> >> different view please suggest.
> >>
> >> Also, if somebody has any pointers on cloudmonkey and marvin or any more
> >> info on this (like, if it would suffice the infrastructure validation
> >> related cases i mentioned above) any pros/cons would really be helpful
> for
> >> me...
> >>
> >> Appreciate any help on this and looking forward for the response on
> >> this!!!
> >>
> >> Thanks and Regards
> >> -- Umesh Kute
> >>
> >
> >
>
>

Re: Regarding cloudstack automation

[umesh kute <um...@gmail.com>]

So far i have found the failure on following scripts:
1. test_loadbalance
2. test_network
3. test_nic

In runinfo.txt log it is stuck at the step:
*SSH into VM (IPaddress: 10.1.1.55) & NAT Rule (Public IP: 207.x.x.x)*

PFA the Marvin logs for the test_loadbalance.py script.

I have modified the following entry in the script i.e. provided the correct
template name which is present.
"ostype": "CentOS 6.4 (64-bit)",
#"ostype": "CentOS 5.3 (64-bit)",

Please let me know for your comments.

Thanks and Regards
-- Umesh Kute



On Fri, Jan 10, 2014 at 2:57 PM, Santhosh Edukulla <
santhosh.edukulla@citrix.com> wrote:

> You can log the bug for this. We have fixed few other issues along with
> this in a private branch. Will soon merge with ACS. If you need a temporary
> fix, let me know.
>
> Question : Related to ssh issue, ssh to vm failing at which part? Can you
> add some information related to ssh failure which test module, which case
> etc? This may be related\unrelated to the above issue. We can check to see
> the issue is either same\different.
>
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com]
> Sent: Friday, January 10, 2014 4:21 AM
> To: Santhosh Edukulla
> Cc: users@cloudstack.apache.org; Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thanks a lot Santhosh For your response.
>
> Sorry for delay.. But is there any workaround for this issue? Because as i
> mentioned, even if os type is provided as "ostype": 'CentOS 6.4 (64-bit)'
> it is picking up the first one in list i.e. Windows Server 2008 R2
> Enterprise.
> So some of the scripts which required to SSH into VM are failing.
>
> Can I get the JIRA ID for this issue to track?
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Fri, Jan 3, 2014 at 5:19 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com>> wrote:
> Umesh,
>
> This could be probably due to the bug under get_template function under
> marvin/integration/lib/common.py. Though, the ostype description is used
> and corresponding id is retrieved.
>
> But the later part, listTemplate API call returning the list and we are
> picking up either the template which is ready or matching with id we
> retrieved. This case is what could be causing the issue you mentioned.
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>]
> Sent: Friday, January 03, 2014 5:04 AM
> To: Santhosh Edukulla; users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>
> Cc: Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thanks for your help Santhosh!!!
>
> You are right...
> The public IP address range was exhausted. After cleaning up the
> resources, I was able to run the sample script "test_deploy_vm.py"
> successfully.
>
> One question - i have provided the "ostype": 'CentOS 6.4 (64-bit)'. What
> is the use of this parameter?
>
> When observed in management server logs and on cloudstack UI (while
> running script), VM was created of type: "Windows Server 2008 R2 Enterprise
> with SQL 2012 Web Edition". This is the first one in the list.
>
> Does it choose the one which we provided in script or picks it from the
> template list that is returned as a result of response to listTemplate API
> call?
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Thu, Jan 2, 2014 at 7:22 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>>> wrote:
> Umesh,
>
> 1. It seems you have exhausted few of CloudStack Resources. These
> resources usage should show up on your cloudstack dashboard. Anything
> appears in Red are exhausted resources.
>
> 2. Few of the cases could be EX: Guest VM IPs\Management ip addresses  are
> exhausted,
>
> 3. Check for these resources in Red on your dashboard EX:
> http://localhost:8080/client/->Dashboard and clean up them or add new
> resources.
>
>
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>>]
> Sent: Thursday, January 02, 2014 7:06 AM
> To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><ma...@cloudstack.apache.org>>
> Cc: Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thank you once again Santhosh & Chandan.
>
> I have gone through the management server logs. The deployment of VM got
> fired to the setup correctly and there are couple of errors in the
> management-server log.
> I am summarizing those below:
>
> test data in "test_deploy_vm.py"
>  def __init__(self):
>         self.testdata = {
>             #data to create an account
>             "account": {
>                 "email": "test@test.com<ma...@test.com><mailto:
> test@test.com<ma...@test.com>><mailto:test@test.com<mailto:
> test@test.com><ma...@test.com>>>",
>                 "firstname": "Test",
>                 "lastname": "User",
>                 "username": "test",
>                 "password": "password",
>             },
>             #data reqd for virtual machine creation
>             "virtual_machine" : {
>                 "name" : "testvmshr",
>                 "displayname" : "Test VM shr",
>             },
>             #small service offering
>             "service_offering": {
>                 "small": {
>                     "name": "SOSmall",
>                     "displaytext": "Small Instance",
>                     "cpunumber": 1,
>                     "cpuspeed": 2000,
>                     "memory": 1024,
>                 },
>             },
>             "ostype": 'CentOS 6.4 (64-bit)',
>         }
>
>
> 1. Account is successfully created
> 2. Service offering is successfully created
> 3. Management server logs - management-server.log has following error:
>
>
> 2014-01-02 01:43:40,693 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Lock is released for network Ntwk[326|Guest|15] as a part of network
> shutdown
> 2014-01-02 01:43:40,695 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Lock is released for network id 326 as a part of network implement
> 2014-01-02 01:43:40,695 INFO  [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Insufficient capacity
> com.cloud.exception.InsufficientAddressCapacityException: Insufficient
> address capacityScope=interface com.cloud.dc.DataCenter; id=1
> at
> com.cloud.network.NetworkManagerImpl.fetchNewPublicIp(NetworkManagerImpl.java:479)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.network.NetworkManagerImpl.assignDedicateIpAddress(NetworkManagerImpl.java:613)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.network.NetworkManagerImpl.assignSourceNatIpAddressToGuestNetwork(NetworkManagerImpl.java:582)
> at
> com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:2013)
> at
> com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1939)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2120)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:887)
> at
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:679)
> 2014-01-02 01:43:40,703 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Cleaning up resources for the vm VM[User|testvmshr] in Starting state
>
> 4. When i checked the database for the network id 326 in table "networks",
> it has following entry:
>
> | 326 | test-TestDeployVM-test_deploy_vm-QQ91N0-network |
> b7cb9e31-835f-47e3-9585-97e3b4084e4d |
> test-TestDeployVM-test_deploy_vm-QQ91N0-network | Guest        | Vlan
>            | NULL          | 10.1.1.1       | 10.1.1.0/24<
> http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24>     | Dhcp
> |                  15 |                 200 |              1 |
> ExternalGuestNetworkGuru | Destroy     |     326 |         1 |        305 |
> 8.8.8.8 | 8.8.4.4 | NULL      |          0 | Account  | cs131cloud.internal
> | ecf5b617-04da-469b-b378-f53e05d8cc53 | Isolated   |                0 |
> 2014-01-02 06:43:39 | 2014-01-02 06:43:46 |                 0 |   NULL |
> NULL        | NULL     | NULL         |               1 |           NULL |
>
>
> Basically it tries to create a network offering (id=15) : "HA Isolated
> Network With Source Nat"
>
>
> 5. I think the script creates a network shown in above table:
> "test-TestDeployVM-test_deploy_vm-QQ91N0-network".
>
> I am not sure why it still gives the Insufficient address capacityScope
> exception.
>
> 6. One more thing i observed. I have provided the "ostype": 'CentOS 6.4
> (64-bit)'. But in DeployVMCmd it uses the template id:
> "03ffb96f-2cfa-11e3-a4f0-f245a5b3ba0f" which is for template "Windows
> Server 2008 R2 Enterprise with SQL 2012 Web Edition".
>
>
> I am attaching the management-server logs and script logs for references.
>
> If somebody can help me what's wrong here, would really be helpful.
>
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Thu, Jan 2, 2014 at 2:59 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>>>>
> wrote:
> 1. Is it still failing post this registration?
>
> 2. If yes, may be you can verify\provide the management server logs.
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>]
> Sent: Thursday, January 02, 2014 4:16 AM
> To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><ma...@cloudstack.apache.org>>>
> Cc: Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thanks Santhosh.
> Yes, I have registered the following template which i am using.
>
> "ostype": 'CentOS 6.4 (64-bit)',
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Mon, Dec 30, 2013 at 5:50 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>>>>
> wrote:
>
> > Umesh,
> >
> > One question : Did you registered the template for ostype:     "ostype":
> > 'CentOS 5.3 (64-bit)'?
> >
> > Regards,
> > Santhosh
> > ________________________________________
> > From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>]
> > Sent: Monday, December 30, 2013 6:32 AM
> > To: Chandan Purushothama
> > Cc: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><ma...@cloudstack.apache.org>>>;
> Sudha Ponnaganti
> > Subject: Re: Regarding cloudstack automation
> >
> > Hi Chandan,
> > Thanks for your response.
> > I have the latest Marvin repository (December 20th). I am able to proceed
> > further. There was an issue of firewall for that machine and it got
> > resolved.
> >
> > But now i am getting another error when i tried to run the script
> > "test_deploy_vm.py"
> >
> > I have attached the log. Can somebody please have a look on it and help
> me
> > in resolving the issue?
> >
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > test_deploy_vm (integration.smoke.test_deploy_vm.TestDeployVM): CRITICAL:
> > EXCEPTION: test_deploy_vm: Traceback (most recent call last):
> >   File "/usr/local/lib/python2.7/unittest/case.py", line 327, in run
> >     testMethod()
> >   File
> > "/DataDisk/temp/cloudstack/test/integration/smoke/test_deploy_vm.py",
> line
> > 116, in test_deploy_vm
> >     templateid=self.template.id<http://self.template.id><
> http://self.template.id><http://self.template.id><http://self.template.id>
> >   File
> > "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py",
> > line 415, in create
> >     virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> > line 593, in deployVirtualMachine
> >     response = self.connection.marvinRequest(command,
> > response_type=response, method=method)
> >   File
> > "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> > line 280, in marvinRequest
> >     response = self.poll(asyncJobId, response_type)
> >   File
> > "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> > line 86, in poll
> >     "asyncquery", asyncResonse.jobresult)
> > cloudstackAPIException: Execute cmd: asyncquery failed, due to:
> {errorcode
> > : 533, errortext : u'Unable to create a deployment for
> VM[User|testvmshr]'}
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > PFA entire logs.
> >
> > Please let me know in case if anything is required.
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> > On Sun, Dec 29, 2013 at 10:32 PM, Chandan Purushothama <
> > Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> >>><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com>><mailto:
> Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>>>
> > wrote:
> >
> > Hello Umesh,
> >
> > I had a similar experience with an older Marvin build. I updated mine to
> > the latest and tried again and it worked. I recommend you to kindly try
> > again with the latest Marvin build and see if you are able to work with
> the
> > automation framework,
> >
> > Thank you,
> > Chandan
> >
> >
> > -------- Original message --------
> > From: umesh kute
> > Date:12/26/2013 12:29 AM (GMT-08:00)
> > To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>,Sudha
> > Ponnaganti
> > Subject: Re: Regarding cloudstack automation
> >
> > Hi All,
> > I have created a Marvin setup on CentOS6.3 by following the document:
> >
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> >
> > All the pre-requisites are installed successfully.
> >
> > I tried to run the sample script test_deploy_vm.py
> > (cloudstack/test/integration/smoke/), I am getting following error:
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > [root@localhost smoke]# nosetests --with-marvin
> > --marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg
> --load
> > test_deploy_vm.py
> >
> >  Exception Occurred Under __deployDC :
> > HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> > with url: /client/api?account=admin&command=listUsers&response=json
> (Caused
> > by <class 'socket.error'>: [Errno 110] Connection timed out)
> > Traceback (most recent call last):
> >   File "/usr/local/bin/nosetests", line 9, in <module>
> >     load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> > line 118, in __init__
> >     **extra_args)
> >   File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
> >     self.runTests()
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> > line 197, in runTests
> >     result = self.testRunner.run(self.test)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> > line 61, in run
> >     test(result)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> > line 45, in __call__
> >     return self.run(*arg, **kwarg)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> > line 138, in run
> >     result.addError(self, err)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
> > line 124, in addError
> >     plugin_handled = plugins.handleError(self.test, err)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> > line 99, in __call__
> >     return self.call(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> > line 167, in simple
> >     result = meth(*arg, **kw)
> >   File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
> > line 155, in handleError
> >     self.tcRunLogger.fatal("%s: %s: %s" %
> > AttributeError: 'NoneType' object has no attribute 'fatal'
> >
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > The logs are generated at /tmp and the log has following error.
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > 2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
> > {'account': 'admin'}
> > 2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
> > http://10.88.91.100:8096/client/api :
> > HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> > with url: /client/api?account=admin&command=listUsers&response=json
> (Caused
> > by <class 'socket.error'>: [Errno 110] Connection timed out)
> >
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > Please note: I have opened the integration port 8096 on management
> server.
> > Also, changed the global settings integration.api.port
> > on cloudstack GUI to 8096 and restarted the management server.
> >
> > Still I am getting the above issue. I am not sure if i missed any
> > configuration.
> >
> > Can somebody please help me with resolution of this issue?
> > Appreciate your help here!!!
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> > On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>><mailto:
> > umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>> wrote:
> >
> > > Thanks a lot Sudha for your quick response.
> > > I will setup the Marvin on local machine and get back in case if I face
> > > any challenges in setup.
> > >
> > > Thanks and Regards
> > > -- Umesh Kute
> > >
> > >
> > >
> > > On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
> > > sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >>><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><ma...@citrix.com>>>>>
> wrote:
> > >
> > >> Hi Umesh,
> > >>
> > >> Looks like you have started on right track - Marvin is the framework
> to
> > >> use for functional or integration automation.
> > >> There are sizable number of test cases exist and you can review them.
> > >>  There are some wiki pages already written explaining Marvin [1]. Also
> > best
> > >> practices are published by community as well [2]. You can contribute
> to
> > it
> > >> as much as you can.
> > >>
> > >> Besides this, there is Junit framework (unit Test), Selenium framework
> > >> (UI automation) which are not as popular as Marvin. Marvin is perfect
> > for
> > >> majority of the validation. You can use simulator as well with Marvin.
> > >>
> > >> Please do pursue these and post questions to the community if you run
> in
> > >> to any issues in setting up env and running tests. There are jobs
> setup
> > by
> > >> various community members to test Master or current releases in
> various
> > >> labs and can help answer questions.
> > >>
> > >> [1]
> > >>
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> > >>
> > >>
> > >> Thanks
> > >> /Sudha
> > >>
> > >>
> > >> -----Original Message-----
> > >> From: umesh kute [mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>>]
> > >> Sent: Saturday, December 07, 2013 10:29 PM
> > >> To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>>
> > >> Subject: Regarding cloudstack automation
> > >>
> > >> Hi All,
> > >> Good morning !!!
> > >> I am working as QA engineer and I am new to the cloudstack community.
> > >> We have started using cloudstack and deployed it in our
> infrastructure.
> > >>
> > >> Can somebody please help me in identifying the good automation
> > >> framework/tool/anything? The main intention is we want to automate the
> > >> infrastructure validation related cases (for e.g. create/update/delete
> > >> cases for instances, project, network, etc...)
> > >>
> > >> It would be good if you can help in identifying it.
> > >>
> > >> Please note: I have gone through cloudmonkey. But i haven't found much
> > >> help on it. May be i need to search a bit more.. I am also going
> through
> > >> the marvin and planning to setup it. If apart from these two, if
> anyone
> > has
> > >> different view please suggest.
> > >>
> > >> Also, if somebody has any pointers on cloudmonkey and marvin or any
> more
> > >> info on this (like, if it would suffice the infrastructure validation
> > >> related cases i mentioned above) any pros/cons would really be helpful
> > for
> > >> me...
> > >>
> > >> Appreciate any help on this and looking forward for the response on
> > >> this!!!
> > >>
> > >> Thanks and Regards
> > >> -- Umesh Kute
> > >>
> > >
> > >
> >
> >
>
>
>

RE: Regarding cloudstack automation

[Santhosh Edukulla <sa...@citrix.com>]

You can log the bug for this. We have fixed few other issues along with this in a private branch. Will soon merge with ACS. If you need a temporary fix, let me know. 

Question : Related to ssh issue, ssh to vm failing at which part? Can you add some information related to ssh failure which test module, which case etc? This may be related\unrelated to the above issue. We can check to see the issue is either same\different.

Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com]
Sent: Friday, January 10, 2014 4:21 AM
To: Santhosh Edukulla
Cc: users@cloudstack.apache.org; Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks a lot Santhosh For your response.

Sorry for delay.. But is there any workaround for this issue? Because as i mentioned, even if os type is provided as "ostype": 'CentOS 6.4 (64-bit)' it is picking up the first one in list i.e. Windows Server 2008 R2 Enterprise.
So some of the scripts which required to SSH into VM are failing.

Can I get the JIRA ID for this issue to track?

Thanks and Regards
-- Umesh Kute


On Fri, Jan 3, 2014 at 5:19 PM, Santhosh Edukulla <sa...@citrix.com>> wrote:
Umesh,

This could be probably due to the bug under get_template function under marvin/integration/lib/common.py. Though, the ostype description is used and corresponding id is retrieved.

But the later part, listTemplate API call returning the list and we are picking up either the template which is ready or matching with id we retrieved. This case is what could be causing the issue you mentioned.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>]
Sent: Friday, January 03, 2014 5:04 AM
To: Santhosh Edukulla; users@cloudstack.apache.org<ma...@cloudstack.apache.org>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks for your help Santhosh!!!

You are right...
The public IP address range was exhausted. After cleaning up the resources, I was able to run the sample script "test_deploy_vm.py" successfully.

One question - i have provided the "ostype": 'CentOS 6.4 (64-bit)'. What is the use of this parameter?

When observed in management server logs and on cloudstack UI (while running script), VM was created of type: "Windows Server 2008 R2 Enterprise with SQL 2012 Web Edition". This is the first one in the list.

Does it choose the one which we provided in script or picks it from the template list that is returned as a result of response to listTemplate API call?

Thanks and Regards
-- Umesh Kute


On Thu, Jan 2, 2014 at 7:22 PM, Santhosh Edukulla <sa...@citrix.com>>> wrote:
Umesh,

1. It seems you have exhausted few of CloudStack Resources. These resources usage should show up on your cloudstack dashboard. Anything appears in Red are exhausted resources.

2. Few of the cases could be EX: Guest VM IPs\Management ip addresses  are exhausted,

3. Check for these resources in Red on your dashboard EX: http://localhost:8080/client/->Dashboard and clean up them or add new resources.


Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>]
Sent: Thursday, January 02, 2014 7:06 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thank you once again Santhosh & Chandan.

I have gone through the management server logs. The deployment of VM got fired to the setup correctly and there are couple of errors in the management-server log.
I am summarizing those below:

test data in "test_deploy_vm.py"
 def __init__(self):
        self.testdata = {
            #data to create an account
            "account": {
                "email": "test@test.com<ma...@test.com>>>",
                "firstname": "Test",
                "lastname": "User",
                "username": "test",
                "password": "password",
            },
            #data reqd for virtual machine creation
            "virtual_machine" : {
                "name" : "testvmshr",
                "displayname" : "Test VM shr",
            },
            #small service offering
            "service_offering": {
                "small": {
                    "name": "SOSmall",
                    "displaytext": "Small Instance",
                    "cpunumber": 1,
                    "cpuspeed": 2000,
                    "memory": 1024,
                },
            },
            "ostype": 'CentOS 6.4 (64-bit)',
        }


1. Account is successfully created
2. Service offering is successfully created
3. Management server logs - management-server.log has following error:


2014-01-02 01:43:40,693 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Lock is released for network Ntwk[326|Guest|15] as a part of network shutdown
2014-01-02 01:43:40,695 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Lock is released for network id 326 as a part of network implement
2014-01-02 01:43:40,695 INFO  [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Insufficient capacity
com.cloud.exception.InsufficientAddressCapacityException: Insufficient address capacityScope=interface com.cloud.dc.DataCenter; id=1
at com.cloud.network.NetworkManagerImpl.fetchNewPublicIp(NetworkManagerImpl.java:479)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.assignDedicateIpAddress(NetworkManagerImpl.java:613)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.assignSourceNatIpAddressToGuestNetwork(NetworkManagerImpl.java:582)
at com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:2013)
at com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1939)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2120)
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:887)
at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2014-01-02 01:43:40,703 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Cleaning up resources for the vm VM[User|testvmshr] in Starting state

4. When i checked the database for the network id 326 in table "networks", it has following entry:

| 326 | test-TestDeployVM-test_deploy_vm-QQ91N0-network | b7cb9e31-835f-47e3-9585-97e3b4084e4d | test-TestDeployVM-test_deploy_vm-QQ91N0-network | Guest        | Vlan                  | NULL          | 10.1.1.1       | 10.1.1.0/24<http://10.1.1.0/24><http://10.1.1.0/24><http://10.1.1.0/24>     | Dhcp   |                  15 |                 200 |              1 | ExternalGuestNetworkGuru | Destroy     |     326 |         1 |        305 | 8.8.8.8 | 8.8.4.4 | NULL      |          0 | Account  | cs131cloud.internal | ecf5b617-04da-469b-b378-f53e05d8cc53 | Isolated   |                0 | 2014-01-02 06:43:39 | 2014-01-02 06:43:46 |                 0 |   NULL | NULL        | NULL     | NULL         |               1 |           NULL |


Basically it tries to create a network offering (id=15) : "HA Isolated Network With Source Nat"


5. I think the script creates a network shown in above table: "test-TestDeployVM-test_deploy_vm-QQ91N0-network".

I am not sure why it still gives the Insufficient address capacityScope exception.

6. One more thing i observed. I have provided the "ostype": 'CentOS 6.4 (64-bit)'. But in DeployVMCmd it uses the template id: "03ffb96f-2cfa-11e3-a4f0-f245a5b3ba0f" which is for template "Windows Server 2008 R2 Enterprise with SQL 2012 Web Edition".


I am attaching the management-server logs and script logs for references.

If somebody can help me what's wrong here, would really be helpful.


Thanks and Regards
-- Umesh Kute


On Thu, Jan 2, 2014 at 2:59 PM, Santhosh Edukulla <sa...@citrix.com>>>> wrote:
1. Is it still failing post this registration?

2. If yes, may be you can verify\provide the management server logs.
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>]
Sent: Thursday, January 02, 2014 4:16 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks Santhosh.
Yes, I have registered the following template which i am using.

"ostype": 'CentOS 6.4 (64-bit)',

Thanks and Regards
-- Umesh Kute


On Mon, Dec 30, 2013 at 5:50 PM, Santhosh Edukulla <
santhosh.edukulla@citrix.com<ma...@citrix.com>>>> wrote:

> Umesh,
>
> One question : Did you registered the template for ostype:     "ostype":
> 'CentOS 5.3 (64-bit)'?
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>>]
> Sent: Monday, December 30, 2013 6:32 AM
> To: Chandan Purushothama
> Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi Chandan,
> Thanks for your response.
> I have the latest Marvin repository (December 20th). I am able to proceed
> further. There was an issue of firewall for that machine and it got
> resolved.
>
> But now i am getting another error when i tried to run the script
> "test_deploy_vm.py"
>
> I have attached the log. Can somebody please have a look on it and help me
> in resolving the issue?
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> test_deploy_vm (integration.smoke.test_deploy_vm.TestDeployVM): CRITICAL:
> EXCEPTION: test_deploy_vm: Traceback (most recent call last):
>   File "/usr/local/lib/python2.7/unittest/case.py", line 327, in run
>     testMethod()
>   File
> "/DataDisk/temp/cloudstack/test/integration/smoke/test_deploy_vm.py", line
> 116, in test_deploy_vm
>     templateid=self.template.id<http://self.template.id><http://self.template.id><http://self.template.id><http://self.template.id>
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py",
> line 415, in create
>     virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> line 593, in deployVirtualMachine
>     response = self.connection.marvinRequest(command,
> response_type=response, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 280, in marvinRequest
>     response = self.poll(asyncJobId, response_type)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 86, in poll
>     "asyncquery", asyncResonse.jobresult)
> cloudstackAPIException: Execute cmd: asyncquery failed, due to: {errorcode
> : 533, errortext : u'Unable to create a deployment for VM[User|testvmshr]'}
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> PFA entire logs.
>
> Please let me know in case if anything is required.
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Sun, Dec 29, 2013 at 10:32 PM, Chandan Purushothama <
> Chandan.Purushothama@citrix.com<ma...@citrix.com>>>>>
> wrote:
>
> Hello Umesh,
>
> I had a similar experience with an older Marvin build. I updated mine to
> the latest and tried again and it worked. I recommend you to kindly try
> again with the latest Marvin build and see if you are able to work with the
> automation framework,
>
> Thank you,
> Chandan
>
>
> -------- Original message --------
> From: umesh kute
> Date:12/26/2013 12:29 AM (GMT-08:00)
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>,Sudha
> Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi All,
> I have created a Marvin setup on CentOS6.3 by following the document:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
>
> All the pre-requisites are installed successfully.
>
> I tried to run the sample script test_deploy_vm.py
> (cloudstack/test/integration/smoke/), I am getting following error:
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> [root@localhost smoke]# nosetests --with-marvin
> --marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg --load
> test_deploy_vm.py
>
>  Exception Occurred Under __deployDC :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
> Traceback (most recent call last):
>   File "/usr/local/bin/nosetests", line 9, in <module>
>     load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 118, in __init__
>     **extra_args)
>   File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
>     self.runTests()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 197, in runTests
>     result = self.testRunner.run(self.test)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 61, in run
>     test(result)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 45, in __call__
>     return self.run(*arg, **kwarg)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 138, in run
>     result.addError(self, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
> line 124, in addError
>     plugin_handled = plugins.handleError(self.test, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 99, in __call__
>     return self.call(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 167, in simple
>     result = meth(*arg, **kw)
>   File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
> line 155, in handleError
>     self.tcRunLogger.fatal("%s: %s: %s" %
> AttributeError: 'NoneType' object has no attribute 'fatal'
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> The logs are generated at /tmp and the log has following error.
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
> {'account': 'admin'}
> 2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
> http://10.88.91.100:8096/client/api :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Please note: I have opened the integration port 8096 on management server.
> Also, changed the global settings integration.api.port
> on cloudstack GUI to 8096 and restarted the management server.
>
> Still I am getting the above issue. I am not sure if i missed any
> configuration.
>
> Can somebody please help me with resolution of this issue?
> Appreciate your help here!!!
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <um...@gmail.com>>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>>> wrote:
>
> > Thanks a lot Sudha for your quick response.
> > I will setup the Marvin on local machine and get back in case if I face
> > any challenges in setup.
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> >
> > On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
> > sudha.ponnaganti@citrix.com<ma...@citrix.com>>>>> wrote:
> >
> >> Hi Umesh,
> >>
> >> Looks like you have started on right track - Marvin is the framework to
> >> use for functional or integration automation.
> >> There are sizable number of test cases exist and you can review them.
> >>  There are some wiki pages already written explaining Marvin [1]. Also
> best
> >> practices are published by community as well [2]. You can contribute to
> it
> >> as much as you can.
> >>
> >> Besides this, there is Junit framework (unit Test), Selenium framework
> >> (UI automation) which are not as popular as Marvin. Marvin is perfect
> for
> >> majority of the validation. You can use simulator as well with Marvin.
> >>
> >> Please do pursue these and post questions to the community if you run in
> >> to any issues in setting up env and running tests. There are jobs setup
> by
> >> various community members to test Master or current releases in various
> >> labs and can help answer questions.
> >>
> >> [1]
> >>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> >>
> >>
> >> Thanks
> >> /Sudha
> >>
> >>
> >> -----Original Message-----
> >> From: umesh kute [mailto:umeshvkute@gmail.com<ma...@gmail.com>>>]
> >> Sent: Saturday, December 07, 2013 10:29 PM
> >> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>>
> >> Subject: Regarding cloudstack automation
> >>
> >> Hi All,
> >> Good morning !!!
> >> I am working as QA engineer and I am new to the cloudstack community.
> >> We have started using cloudstack and deployed it in our infrastructure.
> >>
> >> Can somebody please help me in identifying the good automation
> >> framework/tool/anything? The main intention is we want to automate the
> >> infrastructure validation related cases (for e.g. create/update/delete
> >> cases for instances, project, network, etc...)
> >>
> >> It would be good if you can help in identifying it.
> >>
> >> Please note: I have gone through cloudmonkey. But i haven't found much
> >> help on it. May be i need to search a bit more.. I am also going through
> >> the marvin and planning to setup it. If apart from these two, if anyone
> has
> >> different view please suggest.
> >>
> >> Also, if somebody has any pointers on cloudmonkey and marvin or any more
> >> info on this (like, if it would suffice the infrastructure validation
> >> related cases i mentioned above) any pros/cons would really be helpful
> for
> >> me...
> >>
> >> Appreciate any help on this and looking forward for the response on
> >> this!!!
> >>
> >> Thanks and Regards
> >> -- Umesh Kute
> >>
> >
> >
>
>

Re: Regarding cloudstack automation

[umesh kute <um...@gmail.com>]

Thanks a lot Santhosh For your response.

*Sorry for delay.. *But is there any workaround for this issue? Because as
i mentioned, even if os type is provided as "ostype": 'CentOS 6.4 (64-bit)'
it is picking up the first one in list i.e. Windows Server 2008 R2
Enterprise.
So some of the scripts which required to SSH into VM are failing.

Can I get the JIRA ID for this issue to track?

Thanks and Regards
-- Umesh Kute


On Fri, Jan 3, 2014 at 5:19 PM, Santhosh Edukulla <
santhosh.edukulla@citrix.com> wrote:

> Umesh,
>
> This could be probably due to the bug under get_template function under
> marvin/integration/lib/common.py. Though, the ostype description is used
> and corresponding id is retrieved.
>
> But the later part, listTemplate API call returning the list and we are
> picking up either the template which is ready or matching with id we
> retrieved. This case is what could be causing the issue you mentioned.
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com]
> Sent: Friday, January 03, 2014 5:04 AM
> To: Santhosh Edukulla; users@cloudstack.apache.org
> Cc: Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thanks for your help Santhosh!!!
>
> You are right...
> The public IP address range was exhausted. After cleaning up the
> resources, I was able to run the sample script "test_deploy_vm.py"
> successfully.
>
> One question - i have provided the "ostype": 'CentOS 6.4 (64-bit)'. What
> is the use of this parameter?
>
> When observed in management server logs and on cloudstack UI (while
> running script), VM was created of type: "Windows Server 2008 R2 Enterprise
> with SQL 2012 Web Edition". This is the first one in the list.
>
> Does it choose the one which we provided in script or picks it from the
> template list that is returned as a result of response to listTemplate API
> call?
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Thu, Jan 2, 2014 at 7:22 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com>> wrote:
> Umesh,
>
> 1. It seems you have exhausted few of CloudStack Resources. These
> resources usage should show up on your cloudstack dashboard. Anything
> appears in Red are exhausted resources.
>
> 2. Few of the cases could be EX: Guest VM IPs\Management ip addresses  are
> exhausted,
>
> 3. Check for these resources in Red on your dashboard EX:
> http://localhost:8080/client/->Dashboard and clean up them or add new
> resources.
>
>
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>]
> Sent: Thursday, January 02, 2014 7:06 AM
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
> Cc: Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thank you once again Santhosh & Chandan.
>
> I have gone through the management server logs. The deployment of VM got
> fired to the setup correctly and there are couple of errors in the
> management-server log.
> I am summarizing those below:
>
> test data in "test_deploy_vm.py"
>  def __init__(self):
>         self.testdata = {
>             #data to create an account
>             "account": {
>                 "email": "test@test.com<ma...@test.com><mailto:
> test@test.com<ma...@test.com>>",
>                 "firstname": "Test",
>                 "lastname": "User",
>                 "username": "test",
>                 "password": "password",
>             },
>             #data reqd for virtual machine creation
>             "virtual_machine" : {
>                 "name" : "testvmshr",
>                 "displayname" : "Test VM shr",
>             },
>             #small service offering
>             "service_offering": {
>                 "small": {
>                     "name": "SOSmall",
>                     "displaytext": "Small Instance",
>                     "cpunumber": 1,
>                     "cpuspeed": 2000,
>                     "memory": 1024,
>                 },
>             },
>             "ostype": 'CentOS 6.4 (64-bit)',
>         }
>
>
> 1. Account is successfully created
> 2. Service offering is successfully created
> 3. Management server logs - management-server.log has following error:
>
>
> 2014-01-02 01:43:40,693 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Lock is released for network Ntwk[326|Guest|15] as a part of network
> shutdown
> 2014-01-02 01:43:40,695 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Lock is released for network id 326 as a part of network implement
> 2014-01-02 01:43:40,695 INFO  [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Insufficient capacity
> com.cloud.exception.InsufficientAddressCapacityException: Insufficient
> address capacityScope=interface com.cloud.dc.DataCenter; id=1
> at
> com.cloud.network.NetworkManagerImpl.fetchNewPublicIp(NetworkManagerImpl.java:479)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.network.NetworkManagerImpl.assignDedicateIpAddress(NetworkManagerImpl.java:613)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.network.NetworkManagerImpl.assignSourceNatIpAddressToGuestNetwork(NetworkManagerImpl.java:582)
> at
> com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:2013)
> at
> com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1939)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2120)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:887)
> at
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:679)
> 2014-01-02 01:43:40,703 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Cleaning up resources for the vm VM[User|testvmshr] in Starting state
>
> 4. When i checked the database for the network id 326 in table "networks",
> it has following entry:
>
> | 326 | test-TestDeployVM-test_deploy_vm-QQ91N0-network |
> b7cb9e31-835f-47e3-9585-97e3b4084e4d |
> test-TestDeployVM-test_deploy_vm-QQ91N0-network | Guest        | Vlan
>            | NULL          | 10.1.1.1       | 10.1.1.0/24<
> http://10.1.1.0/24><http://10.1.1.0/24>     | Dhcp   |
>  15 |                 200 |              1 | ExternalGuestNetworkGuru |
> Destroy     |     326 |         1 |        305 | 8.8.8.8 | 8.8.4.4 | NULL
>    |          0 | Account  | cs131cloud.internal |
> ecf5b617-04da-469b-b378-f53e05d8cc53 | Isolated   |                0 |
> 2014-01-02 06:43:39 | 2014-01-02 06:43:46 |                 0 |   NULL |
> NULL        | NULL     | NULL         |               1 |           NULL |
>
>
> Basically it tries to create a network offering (id=15) : "HA Isolated
> Network With Source Nat"
>
>
> 5. I think the script creates a network shown in above table:
> "test-TestDeployVM-test_deploy_vm-QQ91N0-network".
>
> I am not sure why it still gives the Insufficient address capacityScope
> exception.
>
> 6. One more thing i observed. I have provided the "ostype": 'CentOS 6.4
> (64-bit)'. But in DeployVMCmd it uses the template id:
> "03ffb96f-2cfa-11e3-a4f0-f245a5b3ba0f" which is for template "Windows
> Server 2008 R2 Enterprise with SQL 2012 Web Edition".
>
>
> I am attaching the management-server logs and script logs for references.
>
> If somebody can help me what's wrong here, would really be helpful.
>
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Thu, Jan 2, 2014 at 2:59 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>>> wrote:
> 1. Is it still failing post this registration?
>
> 2. If yes, may be you can verify\provide the management server logs.
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>>]
> Sent: Thursday, January 02, 2014 4:16 AM
> To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><ma...@cloudstack.apache.org>>
> Cc: Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thanks Santhosh.
> Yes, I have registered the following template which i am using.
>
> "ostype": 'CentOS 6.4 (64-bit)',
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Mon, Dec 30, 2013 at 5:50 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com><mailto:
> santhosh.edukulla@citrix.com<ma...@citrix.com>>> wrote:
>
> > Umesh,
> >
> > One question : Did you registered the template for ostype:     "ostype":
> > 'CentOS 5.3 (64-bit)'?
> >
> > Regards,
> > Santhosh
> > ________________________________________
> > From: umesh kute [umeshvkute@gmail.com<mailto:umeshvkute@gmail.com
> ><ma...@gmail.com>>]
> > Sent: Monday, December 30, 2013 6:32 AM
> > To: Chandan Purushothama
> > Cc: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><ma...@cloudstack.apache.org>>;
> Sudha Ponnaganti
> > Subject: Re: Regarding cloudstack automation
> >
> > Hi Chandan,
> > Thanks for your response.
> > I have the latest Marvin repository (December 20th). I am able to proceed
> > further. There was an issue of firewall for that machine and it got
> > resolved.
> >
> > But now i am getting another error when i tried to run the script
> > "test_deploy_vm.py"
> >
> > I have attached the log. Can somebody please have a look on it and help
> me
> > in resolving the issue?
> >
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > test_deploy_vm (integration.smoke.test_deploy_vm.TestDeployVM): CRITICAL:
> > EXCEPTION: test_deploy_vm: Traceback (most recent call last):
> >   File "/usr/local/lib/python2.7/unittest/case.py", line 327, in run
> >     testMethod()
> >   File
> > "/DataDisk/temp/cloudstack/test/integration/smoke/test_deploy_vm.py",
> line
> > 116, in test_deploy_vm
> >     templateid=self.template.id<http://self.template.id><
> http://self.template.id><http://self.template.id>
> >   File
> > "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py",
> > line 415, in create
> >     virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> > line 593, in deployVirtualMachine
> >     response = self.connection.marvinRequest(command,
> > response_type=response, method=method)
> >   File
> > "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> > line 280, in marvinRequest
> >     response = self.poll(asyncJobId, response_type)
> >   File
> > "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> > line 86, in poll
> >     "asyncquery", asyncResonse.jobresult)
> > cloudstackAPIException: Execute cmd: asyncquery failed, due to:
> {errorcode
> > : 533, errortext : u'Unable to create a deployment for
> VM[User|testvmshr]'}
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > PFA entire logs.
> >
> > Please let me know in case if anything is required.
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> > On Sun, Dec 29, 2013 at 10:32 PM, Chandan Purushothama <
> > Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>><mailto:Chandan.Purushothama@citrix.com
> <ma...@citrix.com><mailto:
> Chandan.Purushothama@citrix.com<ma...@citrix.com>>>>
> > wrote:
> >
> > Hello Umesh,
> >
> > I had a similar experience with an older Marvin build. I updated mine to
> > the latest and tried again and it worked. I recommend you to kindly try
> > again with the latest Marvin build and see if you are able to work with
> the
> > automation framework,
> >
> > Thank you,
> > Chandan
> >
> >
> > -------- Original message --------
> > From: umesh kute
> > Date:12/26/2013 12:29 AM (GMT-08:00)
> > To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>>,Sudha
> > Ponnaganti
> > Subject: Re: Regarding cloudstack automation
> >
> > Hi All,
> > I have created a Marvin setup on CentOS6.3 by following the document:
> >
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> >
> > All the pre-requisites are installed successfully.
> >
> > I tried to run the sample script test_deploy_vm.py
> > (cloudstack/test/integration/smoke/), I am getting following error:
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > [root@localhost smoke]# nosetests --with-marvin
> > --marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg
> --load
> > test_deploy_vm.py
> >
> >  Exception Occurred Under __deployDC :
> > HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> > with url: /client/api?account=admin&command=listUsers&response=json
> (Caused
> > by <class 'socket.error'>: [Errno 110] Connection timed out)
> > Traceback (most recent call last):
> >   File "/usr/local/bin/nosetests", line 9, in <module>
> >     load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> > line 118, in __init__
> >     **extra_args)
> >   File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
> >     self.runTests()
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> > line 197, in runTests
> >     result = self.testRunner.run(self.test)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> > line 61, in run
> >     test(result)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> > line 45, in __call__
> >     return self.run(*arg, **kwarg)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> > line 138, in run
> >     result.addError(self, err)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
> > line 124, in addError
> >     plugin_handled = plugins.handleError(self.test, err)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> > line 99, in __call__
> >     return self.call(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> > line 167, in simple
> >     result = meth(*arg, **kw)
> >   File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
> > line 155, in handleError
> >     self.tcRunLogger.fatal("%s: %s: %s" %
> > AttributeError: 'NoneType' object has no attribute 'fatal'
> >
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > The logs are generated at /tmp and the log has following error.
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > 2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
> > {'account': 'admin'}
> > 2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
> > http://10.88.91.100:8096/client/api :
> > HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> > with url: /client/api?account=admin&command=listUsers&response=json
> (Caused
> > by <class 'socket.error'>: [Errno 110] Connection timed out)
> >
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > Please note: I have opened the integration port 8096 on management
> server.
> > Also, changed the global settings integration.api.port
> > on cloudstack GUI to 8096 and restarted the management server.
> >
> > Still I am getting the above issue. I am not sure if i missed any
> > configuration.
> >
> > Can somebody please help me with resolution of this issue?
> > Appreciate your help here!!!
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> > On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>><mailto:
> > umeshvkute@gmail.com<ma...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>> wrote:
> >
> > > Thanks a lot Sudha for your quick response.
> > > I will setup the Marvin on local machine and get back in case if I face
> > > any challenges in setup.
> > >
> > > Thanks and Regards
> > > -- Umesh Kute
> > >
> > >
> > >
> > > On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
> > > sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> >><mailto:sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><ma...@citrix.com>>>>
> wrote:
> > >
> > >> Hi Umesh,
> > >>
> > >> Looks like you have started on right track - Marvin is the framework
> to
> > >> use for functional or integration automation.
> > >> There are sizable number of test cases exist and you can review them.
> > >>  There are some wiki pages already written explaining Marvin [1]. Also
> > best
> > >> practices are published by community as well [2]. You can contribute
> to
> > it
> > >> as much as you can.
> > >>
> > >> Besides this, there is Junit framework (unit Test), Selenium framework
> > >> (UI automation) which are not as popular as Marvin. Marvin is perfect
> > for
> > >> majority of the validation. You can use simulator as well with Marvin.
> > >>
> > >> Please do pursue these and post questions to the community if you run
> in
> > >> to any issues in setting up env and running tests. There are jobs
> setup
> > by
> > >> various community members to test Master or current releases in
> various
> > >> labs and can help answer questions.
> > >>
> > >> [1]
> > >>
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> > >>
> > >>
> > >> Thanks
> > >> /Sudha
> > >>
> > >>
> > >> -----Original Message-----
> > >> From: umesh kute [mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>>]
> > >> Sent: Saturday, December 07, 2013 10:29 PM
> > >> To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><ma...@cloudstack.apache.org>>>
> > >> Subject: Regarding cloudstack automation
> > >>
> > >> Hi All,
> > >> Good morning !!!
> > >> I am working as QA engineer and I am new to the cloudstack community.
> > >> We have started using cloudstack and deployed it in our
> infrastructure.
> > >>
> > >> Can somebody please help me in identifying the good automation
> > >> framework/tool/anything? The main intention is we want to automate the
> > >> infrastructure validation related cases (for e.g. create/update/delete
> > >> cases for instances, project, network, etc...)
> > >>
> > >> It would be good if you can help in identifying it.
> > >>
> > >> Please note: I have gone through cloudmonkey. But i haven't found much
> > >> help on it. May be i need to search a bit more.. I am also going
> through
> > >> the marvin and planning to setup it. If apart from these two, if
> anyone
> > has
> > >> different view please suggest.
> > >>
> > >> Also, if somebody has any pointers on cloudmonkey and marvin or any
> more
> > >> info on this (like, if it would suffice the infrastructure validation
> > >> related cases i mentioned above) any pros/cons would really be helpful
> > for
> > >> me...
> > >>
> > >> Appreciate any help on this and looking forward for the response on
> > >> this!!!
> > >>
> > >> Thanks and Regards
> > >> -- Umesh Kute
> > >>
> > >
> > >
> >
> >
>
>

RE: Regarding cloudstack automation

[Santhosh Edukulla <sa...@citrix.com>]

Umesh,

This could be probably due to the bug under get_template function under marvin/integration/lib/common.py. Though, the ostype description is used and corresponding id is retrieved.

But the later part, listTemplate API call returning the list and we are picking up either the template which is ready or matching with id we retrieved. This case is what could be causing the issue you mentioned.

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com]
Sent: Friday, January 03, 2014 5:04 AM
To: Santhosh Edukulla; users@cloudstack.apache.org
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks for your help Santhosh!!!

You are right...
The public IP address range was exhausted. After cleaning up the resources, I was able to run the sample script "test_deploy_vm.py" successfully.

One question - i have provided the "ostype": 'CentOS 6.4 (64-bit)'. What is the use of this parameter?

When observed in management server logs and on cloudstack UI (while running script), VM was created of type: "Windows Server 2008 R2 Enterprise with SQL 2012 Web Edition". This is the first one in the list.

Does it choose the one which we provided in script or picks it from the template list that is returned as a result of response to listTemplate API call?

Thanks and Regards
-- Umesh Kute


On Thu, Jan 2, 2014 at 7:22 PM, Santhosh Edukulla <sa...@citrix.com>> wrote:
Umesh,

1. It seems you have exhausted few of CloudStack Resources. These resources usage should show up on your cloudstack dashboard. Anything appears in Red are exhausted resources.

2. Few of the cases could be EX: Guest VM IPs\Management ip addresses  are exhausted,

3. Check for these resources in Red on your dashboard EX: http://localhost:8080/client/->Dashboard and clean up them or add new resources.


Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>]
Sent: Thursday, January 02, 2014 7:06 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thank you once again Santhosh & Chandan.

I have gone through the management server logs. The deployment of VM got fired to the setup correctly and there are couple of errors in the management-server log.
I am summarizing those below:

test data in "test_deploy_vm.py"
 def __init__(self):
        self.testdata = {
            #data to create an account
            "account": {
                "email": "test@test.com<ma...@test.com>>",
                "firstname": "Test",
                "lastname": "User",
                "username": "test",
                "password": "password",
            },
            #data reqd for virtual machine creation
            "virtual_machine" : {
                "name" : "testvmshr",
                "displayname" : "Test VM shr",
            },
            #small service offering
            "service_offering": {
                "small": {
                    "name": "SOSmall",
                    "displaytext": "Small Instance",
                    "cpunumber": 1,
                    "cpuspeed": 2000,
                    "memory": 1024,
                },
            },
            "ostype": 'CentOS 6.4 (64-bit)',
        }


1. Account is successfully created
2. Service offering is successfully created
3. Management server logs - management-server.log has following error:


2014-01-02 01:43:40,693 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Lock is released for network Ntwk[326|Guest|15] as a part of network shutdown
2014-01-02 01:43:40,695 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Lock is released for network id 326 as a part of network implement
2014-01-02 01:43:40,695 INFO  [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Insufficient capacity
com.cloud.exception.InsufficientAddressCapacityException: Insufficient address capacityScope=interface com.cloud.dc.DataCenter; id=1
at com.cloud.network.NetworkManagerImpl.fetchNewPublicIp(NetworkManagerImpl.java:479)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.assignDedicateIpAddress(NetworkManagerImpl.java:613)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.assignSourceNatIpAddressToGuestNetwork(NetworkManagerImpl.java:582)
at com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:2013)
at com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1939)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2120)
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:887)
at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2014-01-02 01:43:40,703 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Cleaning up resources for the vm VM[User|testvmshr] in Starting state

4. When i checked the database for the network id 326 in table "networks", it has following entry:

| 326 | test-TestDeployVM-test_deploy_vm-QQ91N0-network | b7cb9e31-835f-47e3-9585-97e3b4084e4d | test-TestDeployVM-test_deploy_vm-QQ91N0-network | Guest        | Vlan                  | NULL          | 10.1.1.1       | 10.1.1.0/24<http://10.1.1.0/24><http://10.1.1.0/24>     | Dhcp   |                  15 |                 200 |              1 | ExternalGuestNetworkGuru | Destroy     |     326 |         1 |        305 | 8.8.8.8 | 8.8.4.4 | NULL      |          0 | Account  | cs131cloud.internal | ecf5b617-04da-469b-b378-f53e05d8cc53 | Isolated   |                0 | 2014-01-02 06:43:39 | 2014-01-02 06:43:46 |                 0 |   NULL | NULL        | NULL     | NULL         |               1 |           NULL |


Basically it tries to create a network offering (id=15) : "HA Isolated Network With Source Nat"


5. I think the script creates a network shown in above table: "test-TestDeployVM-test_deploy_vm-QQ91N0-network".

I am not sure why it still gives the Insufficient address capacityScope exception.

6. One more thing i observed. I have provided the "ostype": 'CentOS 6.4 (64-bit)'. But in DeployVMCmd it uses the template id: "03ffb96f-2cfa-11e3-a4f0-f245a5b3ba0f" which is for template "Windows Server 2008 R2 Enterprise with SQL 2012 Web Edition".


I am attaching the management-server logs and script logs for references.

If somebody can help me what's wrong here, would really be helpful.


Thanks and Regards
-- Umesh Kute


On Thu, Jan 2, 2014 at 2:59 PM, Santhosh Edukulla <sa...@citrix.com>>> wrote:
1. Is it still failing post this registration?

2. If yes, may be you can verify\provide the management server logs.
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>]
Sent: Thursday, January 02, 2014 4:16 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks Santhosh.
Yes, I have registered the following template which i am using.

"ostype": 'CentOS 6.4 (64-bit)',

Thanks and Regards
-- Umesh Kute


On Mon, Dec 30, 2013 at 5:50 PM, Santhosh Edukulla <
santhosh.edukulla@citrix.com<ma...@citrix.com>>> wrote:

> Umesh,
>
> One question : Did you registered the template for ostype:     "ostype":
> 'CentOS 5.3 (64-bit)'?
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>>]
> Sent: Monday, December 30, 2013 6:32 AM
> To: Chandan Purushothama
> Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi Chandan,
> Thanks for your response.
> I have the latest Marvin repository (December 20th). I am able to proceed
> further. There was an issue of firewall for that machine and it got
> resolved.
>
> But now i am getting another error when i tried to run the script
> "test_deploy_vm.py"
>
> I have attached the log. Can somebody please have a look on it and help me
> in resolving the issue?
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> test_deploy_vm (integration.smoke.test_deploy_vm.TestDeployVM): CRITICAL:
> EXCEPTION: test_deploy_vm: Traceback (most recent call last):
>   File "/usr/local/lib/python2.7/unittest/case.py", line 327, in run
>     testMethod()
>   File
> "/DataDisk/temp/cloudstack/test/integration/smoke/test_deploy_vm.py", line
> 116, in test_deploy_vm
>     templateid=self.template.id<http://self.template.id><http://self.template.id><http://self.template.id>
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py",
> line 415, in create
>     virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> line 593, in deployVirtualMachine
>     response = self.connection.marvinRequest(command,
> response_type=response, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 280, in marvinRequest
>     response = self.poll(asyncJobId, response_type)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 86, in poll
>     "asyncquery", asyncResonse.jobresult)
> cloudstackAPIException: Execute cmd: asyncquery failed, due to: {errorcode
> : 533, errortext : u'Unable to create a deployment for VM[User|testvmshr]'}
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> PFA entire logs.
>
> Please let me know in case if anything is required.
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Sun, Dec 29, 2013 at 10:32 PM, Chandan Purushothama <
> Chandan.Purushothama@citrix.com<ma...@citrix.com>>>>
> wrote:
>
> Hello Umesh,
>
> I had a similar experience with an older Marvin build. I updated mine to
> the latest and tried again and it worked. I recommend you to kindly try
> again with the latest Marvin build and see if you are able to work with the
> automation framework,
>
> Thank you,
> Chandan
>
>
> -------- Original message --------
> From: umesh kute
> Date:12/26/2013 12:29 AM (GMT-08:00)
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>,Sudha
> Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi All,
> I have created a Marvin setup on CentOS6.3 by following the document:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
>
> All the pre-requisites are installed successfully.
>
> I tried to run the sample script test_deploy_vm.py
> (cloudstack/test/integration/smoke/), I am getting following error:
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> [root@localhost smoke]# nosetests --with-marvin
> --marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg --load
> test_deploy_vm.py
>
>  Exception Occurred Under __deployDC :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
> Traceback (most recent call last):
>   File "/usr/local/bin/nosetests", line 9, in <module>
>     load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 118, in __init__
>     **extra_args)
>   File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
>     self.runTests()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 197, in runTests
>     result = self.testRunner.run(self.test)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 61, in run
>     test(result)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 45, in __call__
>     return self.run(*arg, **kwarg)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 138, in run
>     result.addError(self, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
> line 124, in addError
>     plugin_handled = plugins.handleError(self.test, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 99, in __call__
>     return self.call(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 167, in simple
>     result = meth(*arg, **kw)
>   File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
> line 155, in handleError
>     self.tcRunLogger.fatal("%s: %s: %s" %
> AttributeError: 'NoneType' object has no attribute 'fatal'
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> The logs are generated at /tmp and the log has following error.
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
> {'account': 'admin'}
> 2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
> http://10.88.91.100:8096/client/api :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Please note: I have opened the integration port 8096 on management server.
> Also, changed the global settings integration.api.port
> on cloudstack GUI to 8096 and restarted the management server.
>
> Still I am getting the above issue. I am not sure if i missed any
> configuration.
>
> Can somebody please help me with resolution of this issue?
> Appreciate your help here!!!
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <um...@gmail.com>><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>>> wrote:
>
> > Thanks a lot Sudha for your quick response.
> > I will setup the Marvin on local machine and get back in case if I face
> > any challenges in setup.
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> >
> > On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
> > sudha.ponnaganti@citrix.com<ma...@citrix.com>>>> wrote:
> >
> >> Hi Umesh,
> >>
> >> Looks like you have started on right track - Marvin is the framework to
> >> use for functional or integration automation.
> >> There are sizable number of test cases exist and you can review them.
> >>  There are some wiki pages already written explaining Marvin [1]. Also
> best
> >> practices are published by community as well [2]. You can contribute to
> it
> >> as much as you can.
> >>
> >> Besides this, there is Junit framework (unit Test), Selenium framework
> >> (UI automation) which are not as popular as Marvin. Marvin is perfect
> for
> >> majority of the validation. You can use simulator as well with Marvin.
> >>
> >> Please do pursue these and post questions to the community if you run in
> >> to any issues in setting up env and running tests. There are jobs setup
> by
> >> various community members to test Master or current releases in various
> >> labs and can help answer questions.
> >>
> >> [1]
> >>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> >>
> >>
> >> Thanks
> >> /Sudha
> >>
> >>
> >> -----Original Message-----
> >> From: umesh kute [mailto:umeshvkute@gmail.com<ma...@gmail.com>>]
> >> Sent: Saturday, December 07, 2013 10:29 PM
> >> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>
> >> Subject: Regarding cloudstack automation
> >>
> >> Hi All,
> >> Good morning !!!
> >> I am working as QA engineer and I am new to the cloudstack community.
> >> We have started using cloudstack and deployed it in our infrastructure.
> >>
> >> Can somebody please help me in identifying the good automation
> >> framework/tool/anything? The main intention is we want to automate the
> >> infrastructure validation related cases (for e.g. create/update/delete
> >> cases for instances, project, network, etc...)
> >>
> >> It would be good if you can help in identifying it.
> >>
> >> Please note: I have gone through cloudmonkey. But i haven't found much
> >> help on it. May be i need to search a bit more.. I am also going through
> >> the marvin and planning to setup it. If apart from these two, if anyone
> has
> >> different view please suggest.
> >>
> >> Also, if somebody has any pointers on cloudmonkey and marvin or any more
> >> info on this (like, if it would suffice the infrastructure validation
> >> related cases i mentioned above) any pros/cons would really be helpful
> for
> >> me...
> >>
> >> Appreciate any help on this and looking forward for the response on
> >> this!!!
> >>
> >> Thanks and Regards
> >> -- Umesh Kute
> >>
> >
> >
>
>

Re: Regarding cloudstack automation

[umesh kute <um...@gmail.com>]

Thanks for your help Santhosh!!!

You are right...
The public IP address range was exhausted. After cleaning up the resources,
I was able to run the sample script "test_deploy_vm.py" successfully.

One question - i have provided the "ostype": 'CentOS 6.4 (64-bit)'. What is
the use of this parameter?

When observed in management server logs and on cloudstack UI (while running
script), VM was created of type: "Windows Server 2008 R2 Enterprise with
SQL 2012 Web Edition". This is the first one in the list.

Does it choose the one which we provided in script or picks it from the
template list that is returned as a result of response to listTemplate API
call?

Thanks and Regards
-- Umesh Kute


On Thu, Jan 2, 2014 at 7:22 PM, Santhosh Edukulla <
santhosh.edukulla@citrix.com> wrote:

> Umesh,
>
> 1. It seems you have exhausted few of CloudStack Resources. These
> resources usage should show up on your cloudstack dashboard. Anything
> appears in Red are exhausted resources.
>
> 2. Few of the cases could be EX: Guest VM IPs\Management ip addresses  are
> exhausted,
>
> 3. Check for these resources in Red on your dashboard EX:
> http://localhost:8080/client/->Dashboard and clean up them or add new
> resources.
>
>
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com]
> Sent: Thursday, January 02, 2014 7:06 AM
> To: users@cloudstack.apache.org
> Cc: Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thank you once again Santhosh & Chandan.
>
> I have gone through the management server logs. The deployment of VM got
> fired to the setup correctly and there are couple of errors in the
> management-server log.
> I am summarizing those below:
>
> test data in "test_deploy_vm.py"
>  def __init__(self):
>         self.testdata = {
>             #data to create an account
>             "account": {
>                 "email": "test@test.com<ma...@test.com>",
>                 "firstname": "Test",
>                 "lastname": "User",
>                 "username": "test",
>                 "password": "password",
>             },
>             #data reqd for virtual machine creation
>             "virtual_machine" : {
>                 "name" : "testvmshr",
>                 "displayname" : "Test VM shr",
>             },
>             #small service offering
>             "service_offering": {
>                 "small": {
>                     "name": "SOSmall",
>                     "displaytext": "Small Instance",
>                     "cpunumber": 1,
>                     "cpuspeed": 2000,
>                     "memory": 1024,
>                 },
>             },
>             "ostype": 'CentOS 6.4 (64-bit)',
>         }
>
>
> 1. Account is successfully created
> 2. Service offering is successfully created
> 3. Management server logs - management-server.log has following error:
>
>
> 2014-01-02 01:43:40,693 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Lock is released for network Ntwk[326|Guest|15] as a part of network
> shutdown
> 2014-01-02 01:43:40,695 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Lock is released for network id 326 as a part of network implement
> 2014-01-02 01:43:40,695 INFO  [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Insufficient capacity
> com.cloud.exception.InsufficientAddressCapacityException: Insufficient
> address capacityScope=interface com.cloud.dc.DataCenter; id=1
> at
> com.cloud.network.NetworkManagerImpl.fetchNewPublicIp(NetworkManagerImpl.java:479)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.network.NetworkManagerImpl.assignDedicateIpAddress(NetworkManagerImpl.java:613)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.network.NetworkManagerImpl.assignSourceNatIpAddressToGuestNetwork(NetworkManagerImpl.java:582)
> at
> com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:2013)
> at
> com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1939)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2120)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:887)
> at
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:679)
> 2014-01-02 01:43:40,703 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
> Cleaning up resources for the vm VM[User|testvmshr] in Starting state
>
> 4. When i checked the database for the network id 326 in table "networks",
> it has following entry:
>
> | 326 | test-TestDeployVM-test_deploy_vm-QQ91N0-network |
> b7cb9e31-835f-47e3-9585-97e3b4084e4d |
> test-TestDeployVM-test_deploy_vm-QQ91N0-network | Guest        | Vlan
>            | NULL          | 10.1.1.1       | 10.1.1.0/24<
> http://10.1.1.0/24>     | Dhcp   |                  15 |
> 200 |              1 | ExternalGuestNetworkGuru | Destroy     |     326 |
>       1 |        305 | 8.8.8.8 | 8.8.4.4 | NULL      |          0 | Account
>  | cs131cloud.internal | ecf5b617-04da-469b-b378-f53e05d8cc53 | Isolated
> |                0 | 2014-01-02 06:43:39 | 2014-01-02 06:43:46 |
>       0 |   NULL | NULL        | NULL     | NULL         |               1
> |           NULL |
>
>
> Basically it tries to create a network offering (id=15) : "HA Isolated
> Network With Source Nat"
>
>
> 5. I think the script creates a network shown in above table:
> "test-TestDeployVM-test_deploy_vm-QQ91N0-network".
>
> I am not sure why it still gives the Insufficient address capacityScope
> exception.
>
> 6. One more thing i observed. I have provided the "ostype": 'CentOS 6.4
> (64-bit)'. But in DeployVMCmd it uses the template id:
> "03ffb96f-2cfa-11e3-a4f0-f245a5b3ba0f" which is for template "Windows
> Server 2008 R2 Enterprise with SQL 2012 Web Edition".
>
>
> I am attaching the management-server logs and script logs for references.
>
> If somebody can help me what's wrong here, would really be helpful.
>
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Thu, Jan 2, 2014 at 2:59 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com>> wrote:
> 1. Is it still failing post this registration?
>
> 2. If yes, may be you can verify\provide the management server logs.
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>]
> Sent: Thursday, January 02, 2014 4:16 AM
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
> Cc: Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thanks Santhosh.
> Yes, I have registered the following template which i am using.
>
> "ostype": 'CentOS 6.4 (64-bit)',
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Mon, Dec 30, 2013 at 5:50 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com<ma...@citrix.com>> wrote:
>
> > Umesh,
> >
> > One question : Did you registered the template for ostype:     "ostype":
> > 'CentOS 5.3 (64-bit)'?
> >
> > Regards,
> > Santhosh
> > ________________________________________
> > From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>]
> > Sent: Monday, December 30, 2013 6:32 AM
> > To: Chandan Purushothama
> > Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>;
> Sudha Ponnaganti
> > Subject: Re: Regarding cloudstack automation
> >
> > Hi Chandan,
> > Thanks for your response.
> > I have the latest Marvin repository (December 20th). I am able to proceed
> > further. There was an issue of firewall for that machine and it got
> > resolved.
> >
> > But now i am getting another error when i tried to run the script
> > "test_deploy_vm.py"
> >
> > I have attached the log. Can somebody please have a look on it and help
> me
> > in resolving the issue?
> >
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > test_deploy_vm (integration.smoke.test_deploy_vm.TestDeployVM): CRITICAL:
> > EXCEPTION: test_deploy_vm: Traceback (most recent call last):
> >   File "/usr/local/lib/python2.7/unittest/case.py", line 327, in run
> >     testMethod()
> >   File
> > "/DataDisk/temp/cloudstack/test/integration/smoke/test_deploy_vm.py",
> line
> > 116, in test_deploy_vm
> >     templateid=self.template.id<http://self.template.id><
> http://self.template.id>
> >   File
> > "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py",
> > line 415, in create
> >     virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> > line 593, in deployVirtualMachine
> >     response = self.connection.marvinRequest(command,
> > response_type=response, method=method)
> >   File
> > "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> > line 280, in marvinRequest
> >     response = self.poll(asyncJobId, response_type)
> >   File
> > "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> > line 86, in poll
> >     "asyncquery", asyncResonse.jobresult)
> > cloudstackAPIException: Execute cmd: asyncquery failed, due to:
> {errorcode
> > : 533, errortext : u'Unable to create a deployment for
> VM[User|testvmshr]'}
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > PFA entire logs.
> >
> > Please let me know in case if anything is required.
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> > On Sun, Dec 29, 2013 at 10:32 PM, Chandan Purushothama <
> > Chandan.Purushothama@citrix.com<mailto:Chandan.Purushothama@citrix.com
> ><mailto:Chandan.Purushothama@citrix.com<mailto:
> Chandan.Purushothama@citrix.com>>>
> > wrote:
> >
> > Hello Umesh,
> >
> > I had a similar experience with an older Marvin build. I updated mine to
> > the latest and tried again and it worked. I recommend you to kindly try
> > again with the latest Marvin build and see if you are able to work with
> the
> > automation framework,
> >
> > Thank you,
> > Chandan
> >
> >
> > -------- Original message --------
> > From: umesh kute
> > Date:12/26/2013 12:29 AM (GMT-08:00)
> > To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><mailto:users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >>,Sudha
> > Ponnaganti
> > Subject: Re: Regarding cloudstack automation
> >
> > Hi All,
> > I have created a Marvin setup on CentOS6.3 by following the document:
> >
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> >
> > All the pre-requisites are installed successfully.
> >
> > I tried to run the sample script test_deploy_vm.py
> > (cloudstack/test/integration/smoke/), I am getting following error:
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > [root@localhost smoke]# nosetests --with-marvin
> > --marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg
> --load
> > test_deploy_vm.py
> >
> >  Exception Occurred Under __deployDC :
> > HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> > with url: /client/api?account=admin&command=listUsers&response=json
> (Caused
> > by <class 'socket.error'>: [Errno 110] Connection timed out)
> > Traceback (most recent call last):
> >   File "/usr/local/bin/nosetests", line 9, in <module>
> >     load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> > line 118, in __init__
> >     **extra_args)
> >   File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
> >     self.runTests()
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> > line 197, in runTests
> >     result = self.testRunner.run(self.test)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> > line 61, in run
> >     test(result)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> > line 45, in __call__
> >     return self.run(*arg, **kwarg)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> > line 138, in run
> >     result.addError(self, err)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
> > line 124, in addError
> >     plugin_handled = plugins.handleError(self.test, err)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> > line 99, in __call__
> >     return self.call(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> > line 167, in simple
> >     result = meth(*arg, **kw)
> >   File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
> > line 155, in handleError
> >     self.tcRunLogger.fatal("%s: %s: %s" %
> > AttributeError: 'NoneType' object has no attribute 'fatal'
> >
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > The logs are generated at /tmp and the log has following error.
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > 2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
> > {'account': 'admin'}
> > 2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
> > http://10.88.91.100:8096/client/api :
> > HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> > with url: /client/api?account=admin&command=listUsers&response=json
> (Caused
> > by <class 'socket.error'>: [Errno 110] Connection timed out)
> >
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > Please note: I have opened the integration port 8096 on management
> server.
> > Also, changed the global settings integration.api.port
> > on cloudstack GUI to 8096 and restarted the management server.
> >
> > Still I am getting the above issue. I am not sure if i missed any
> > configuration.
> >
> > Can somebody please help me with resolution of this issue?
> > Appreciate your help here!!!
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> > On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com><mailto:
> > umeshvkute@gmail.com<ma...@gmail.com>>> wrote:
> >
> > > Thanks a lot Sudha for your quick response.
> > > I will setup the Marvin on local machine and get back in case if I face
> > > any challenges in setup.
> > >
> > > Thanks and Regards
> > > -- Umesh Kute
> > >
> > >
> > >
> > > On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
> > > sudha.ponnaganti@citrix.com<mailto:sudha.ponnaganti@citrix.com
> ><ma...@citrix.com>>>
> wrote:
> > >
> > >> Hi Umesh,
> > >>
> > >> Looks like you have started on right track - Marvin is the framework
> to
> > >> use for functional or integration automation.
> > >> There are sizable number of test cases exist and you can review them.
> > >>  There are some wiki pages already written explaining Marvin [1]. Also
> > best
> > >> practices are published by community as well [2]. You can contribute
> to
> > it
> > >> as much as you can.
> > >>
> > >> Besides this, there is Junit framework (unit Test), Selenium framework
> > >> (UI automation) which are not as popular as Marvin. Marvin is perfect
> > for
> > >> majority of the validation. You can use simulator as well with Marvin.
> > >>
> > >> Please do pursue these and post questions to the community if you run
> in
> > >> to any issues in setting up env and running tests. There are jobs
> setup
> > by
> > >> various community members to test Master or current releases in
> various
> > >> labs and can help answer questions.
> > >>
> > >> [1]
> > >>
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> > >>
> > >>
> > >> Thanks
> > >> /Sudha
> > >>
> > >>
> > >> -----Original Message-----
> > >> From: umesh kute [mailto:umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>]
> > >> Sent: Saturday, December 07, 2013 10:29 PM
> > >> To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> ><ma...@cloudstack.apache.org>>
> > >> Subject: Regarding cloudstack automation
> > >>
> > >> Hi All,
> > >> Good morning !!!
> > >> I am working as QA engineer and I am new to the cloudstack community.
> > >> We have started using cloudstack and deployed it in our
> infrastructure.
> > >>
> > >> Can somebody please help me in identifying the good automation
> > >> framework/tool/anything? The main intention is we want to automate the
> > >> infrastructure validation related cases (for e.g. create/update/delete
> > >> cases for instances, project, network, etc...)
> > >>
> > >> It would be good if you can help in identifying it.
> > >>
> > >> Please note: I have gone through cloudmonkey. But i haven't found much
> > >> help on it. May be i need to search a bit more.. I am also going
> through
> > >> the marvin and planning to setup it. If apart from these two, if
> anyone
> > has
> > >> different view please suggest.
> > >>
> > >> Also, if somebody has any pointers on cloudmonkey and marvin or any
> more
> > >> info on this (like, if it would suffice the infrastructure validation
> > >> related cases i mentioned above) any pros/cons would really be helpful
> > for
> > >> me...
> > >>
> > >> Appreciate any help on this and looking forward for the response on
> > >> this!!!
> > >>
> > >> Thanks and Regards
> > >> -- Umesh Kute
> > >>
> > >
> > >
> >
> >
>

RE: Regarding cloudstack automation

[Santhosh Edukulla <sa...@citrix.com>]

Umesh,

1. It seems you have exhausted few of CloudStack Resources. These resources usage should show up on your cloudstack dashboard. Anything appears in Red are exhausted resources. 

2. Few of the cases could be EX: Guest VM IPs\Management ip addresses  are exhausted, 

3. Check for these resources in Red on your dashboard EX: http://localhost:8080/client/->Dashboard and clean up them or add new resources.


Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com]
Sent: Thursday, January 02, 2014 7:06 AM
To: users@cloudstack.apache.org
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thank you once again Santhosh & Chandan.

I have gone through the management server logs. The deployment of VM got fired to the setup correctly and there are couple of errors in the management-server log.
I am summarizing those below:

test data in "test_deploy_vm.py"
 def __init__(self):
        self.testdata = {
            #data to create an account
            "account": {
                "email": "test@test.com<ma...@test.com>",
                "firstname": "Test",
                "lastname": "User",
                "username": "test",
                "password": "password",
            },
            #data reqd for virtual machine creation
            "virtual_machine" : {
                "name" : "testvmshr",
                "displayname" : "Test VM shr",
            },
            #small service offering
            "service_offering": {
                "small": {
                    "name": "SOSmall",
                    "displaytext": "Small Instance",
                    "cpunumber": 1,
                    "cpuspeed": 2000,
                    "memory": 1024,
                },
            },
            "ostype": 'CentOS 6.4 (64-bit)',
        }


1. Account is successfully created
2. Service offering is successfully created
3. Management server logs - management-server.log has following error:


2014-01-02 01:43:40,693 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Lock is released for network Ntwk[326|Guest|15] as a part of network shutdown
2014-01-02 01:43:40,695 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Lock is released for network id 326 as a part of network implement
2014-01-02 01:43:40,695 INFO  [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Insufficient capacity
com.cloud.exception.InsufficientAddressCapacityException: Insufficient address capacityScope=interface com.cloud.dc.DataCenter; id=1
at com.cloud.network.NetworkManagerImpl.fetchNewPublicIp(NetworkManagerImpl.java:479)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.assignDedicateIpAddress(NetworkManagerImpl.java:613)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.assignSourceNatIpAddressToGuestNetwork(NetworkManagerImpl.java:582)
at com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:2013)
at com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1939)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2120)
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:887)
at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2014-01-02 01:43:40,703 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ]) Cleaning up resources for the vm VM[User|testvmshr] in Starting state

4. When i checked the database for the network id 326 in table "networks", it has following entry:

| 326 | test-TestDeployVM-test_deploy_vm-QQ91N0-network | b7cb9e31-835f-47e3-9585-97e3b4084e4d | test-TestDeployVM-test_deploy_vm-QQ91N0-network | Guest        | Vlan                  | NULL          | 10.1.1.1       | 10.1.1.0/24<http://10.1.1.0/24>     | Dhcp   |                  15 |                 200 |              1 | ExternalGuestNetworkGuru | Destroy     |     326 |         1 |        305 | 8.8.8.8 | 8.8.4.4 | NULL      |          0 | Account  | cs131cloud.internal | ecf5b617-04da-469b-b378-f53e05d8cc53 | Isolated   |                0 | 2014-01-02 06:43:39 | 2014-01-02 06:43:46 |                 0 |   NULL | NULL        | NULL     | NULL         |               1 |           NULL |


Basically it tries to create a network offering (id=15) : "HA Isolated Network With Source Nat"


5. I think the script creates a network shown in above table: "test-TestDeployVM-test_deploy_vm-QQ91N0-network".

I am not sure why it still gives the Insufficient address capacityScope exception.

6. One more thing i observed. I have provided the "ostype": 'CentOS 6.4 (64-bit)'. But in DeployVMCmd it uses the template id: "03ffb96f-2cfa-11e3-a4f0-f245a5b3ba0f" which is for template "Windows Server 2008 R2 Enterprise with SQL 2012 Web Edition".


I am attaching the management-server logs and script logs for references.

If somebody can help me what's wrong here, would really be helpful.


Thanks and Regards
-- Umesh Kute


On Thu, Jan 2, 2014 at 2:59 PM, Santhosh Edukulla <sa...@citrix.com>> wrote:
1. Is it still failing post this registration?

2. If yes, may be you can verify\provide the management server logs.
________________________________________
From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>]
Sent: Thursday, January 02, 2014 4:16 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks Santhosh.
Yes, I have registered the following template which i am using.

"ostype": 'CentOS 6.4 (64-bit)',

Thanks and Regards
-- Umesh Kute


On Mon, Dec 30, 2013 at 5:50 PM, Santhosh Edukulla <
santhosh.edukulla@citrix.com<ma...@citrix.com>> wrote:

> Umesh,
>
> One question : Did you registered the template for ostype:     "ostype":
> 'CentOS 5.3 (64-bit)'?
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com<ma...@gmail.com>]
> Sent: Monday, December 30, 2013 6:32 AM
> To: Chandan Purushothama
> Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi Chandan,
> Thanks for your response.
> I have the latest Marvin repository (December 20th). I am able to proceed
> further. There was an issue of firewall for that machine and it got
> resolved.
>
> But now i am getting another error when i tried to run the script
> "test_deploy_vm.py"
>
> I have attached the log. Can somebody please have a look on it and help me
> in resolving the issue?
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> test_deploy_vm (integration.smoke.test_deploy_vm.TestDeployVM): CRITICAL:
> EXCEPTION: test_deploy_vm: Traceback (most recent call last):
>   File "/usr/local/lib/python2.7/unittest/case.py", line 327, in run
>     testMethod()
>   File
> "/DataDisk/temp/cloudstack/test/integration/smoke/test_deploy_vm.py", line
> 116, in test_deploy_vm
>     templateid=self.template.id<http://self.template.id><http://self.template.id>
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py",
> line 415, in create
>     virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> line 593, in deployVirtualMachine
>     response = self.connection.marvinRequest(command,
> response_type=response, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 280, in marvinRequest
>     response = self.poll(asyncJobId, response_type)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 86, in poll
>     "asyncquery", asyncResonse.jobresult)
> cloudstackAPIException: Execute cmd: asyncquery failed, due to: {errorcode
> : 533, errortext : u'Unable to create a deployment for VM[User|testvmshr]'}
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> PFA entire logs.
>
> Please let me know in case if anything is required.
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Sun, Dec 29, 2013 at 10:32 PM, Chandan Purushothama <
> Chandan.Purushothama@citrix.com<ma...@citrix.com>>>
> wrote:
>
> Hello Umesh,
>
> I had a similar experience with an older Marvin build. I updated mine to
> the latest and tried again and it worked. I recommend you to kindly try
> again with the latest Marvin build and see if you are able to work with the
> automation framework,
>
> Thank you,
> Chandan
>
>
> -------- Original message --------
> From: umesh kute
> Date:12/26/2013 12:29 AM (GMT-08:00)
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>,Sudha
> Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi All,
> I have created a Marvin setup on CentOS6.3 by following the document:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
>
> All the pre-requisites are installed successfully.
>
> I tried to run the sample script test_deploy_vm.py
> (cloudstack/test/integration/smoke/), I am getting following error:
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> [root@localhost smoke]# nosetests --with-marvin
> --marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg --load
> test_deploy_vm.py
>
>  Exception Occurred Under __deployDC :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
> Traceback (most recent call last):
>   File "/usr/local/bin/nosetests", line 9, in <module>
>     load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 118, in __init__
>     **extra_args)
>   File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
>     self.runTests()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 197, in runTests
>     result = self.testRunner.run(self.test)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 61, in run
>     test(result)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 45, in __call__
>     return self.run(*arg, **kwarg)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 138, in run
>     result.addError(self, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
> line 124, in addError
>     plugin_handled = plugins.handleError(self.test, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 99, in __call__
>     return self.call(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 167, in simple
>     result = meth(*arg, **kw)
>   File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
> line 155, in handleError
>     self.tcRunLogger.fatal("%s: %s: %s" %
> AttributeError: 'NoneType' object has no attribute 'fatal'
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> The logs are generated at /tmp and the log has following error.
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
> {'account': 'admin'}
> 2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
> http://10.88.91.100:8096/client/api :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Please note: I have opened the integration port 8096 on management server.
> Also, changed the global settings integration.api.port
> on cloudstack GUI to 8096 and restarted the management server.
>
> Still I am getting the above issue. I am not sure if i missed any
> configuration.
>
> Can somebody please help me with resolution of this issue?
> Appreciate your help here!!!
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <um...@gmail.com><mailto:
> umeshvkute@gmail.com<ma...@gmail.com>>> wrote:
>
> > Thanks a lot Sudha for your quick response.
> > I will setup the Marvin on local machine and get back in case if I face
> > any challenges in setup.
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> >
> > On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
> > sudha.ponnaganti@citrix.com<ma...@citrix.com>>> wrote:
> >
> >> Hi Umesh,
> >>
> >> Looks like you have started on right track - Marvin is the framework to
> >> use for functional or integration automation.
> >> There are sizable number of test cases exist and you can review them.
> >>  There are some wiki pages already written explaining Marvin [1]. Also
> best
> >> practices are published by community as well [2]. You can contribute to
> it
> >> as much as you can.
> >>
> >> Besides this, there is Junit framework (unit Test), Selenium framework
> >> (UI automation) which are not as popular as Marvin. Marvin is perfect
> for
> >> majority of the validation. You can use simulator as well with Marvin.
> >>
> >> Please do pursue these and post questions to the community if you run in
> >> to any issues in setting up env and running tests. There are jobs setup
> by
> >> various community members to test Master or current releases in various
> >> labs and can help answer questions.
> >>
> >> [1]
> >>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> >>
> >>
> >> Thanks
> >> /Sudha
> >>
> >>
> >> -----Original Message-----
> >> From: umesh kute [mailto:umeshvkute@gmail.com<ma...@gmail.com>]
> >> Sent: Saturday, December 07, 2013 10:29 PM
> >> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>>
> >> Subject: Regarding cloudstack automation
> >>
> >> Hi All,
> >> Good morning !!!
> >> I am working as QA engineer and I am new to the cloudstack community.
> >> We have started using cloudstack and deployed it in our infrastructure.
> >>
> >> Can somebody please help me in identifying the good automation
> >> framework/tool/anything? The main intention is we want to automate the
> >> infrastructure validation related cases (for e.g. create/update/delete
> >> cases for instances, project, network, etc...)
> >>
> >> It would be good if you can help in identifying it.
> >>
> >> Please note: I have gone through cloudmonkey. But i haven't found much
> >> help on it. May be i need to search a bit more.. I am also going through
> >> the marvin and planning to setup it. If apart from these two, if anyone
> has
> >> different view please suggest.
> >>
> >> Also, if somebody has any pointers on cloudmonkey and marvin or any more
> >> info on this (like, if it would suffice the infrastructure validation
> >> related cases i mentioned above) any pros/cons would really be helpful
> for
> >> me...
> >>
> >> Appreciate any help on this and looking forward for the response on
> >> this!!!
> >>
> >> Thanks and Regards
> >> -- Umesh Kute
> >>
> >
> >
>
>

Re: Regarding cloudstack automation

[umesh kute <um...@gmail.com>]

Thank you once again Santhosh & Chandan.

I have gone through the management server logs. The deployment of VM got
fired to the setup correctly and there are couple of errors in the
management-server log.
I am summarizing those below:

test data in "test_deploy_vm.py"
 def __init__(self):
        self.testdata = {
            #data to create an account
            "account": {
                "email": "test@test.com",
                "firstname": "Test",
                "lastname": "User",
                "username": "test",
                "password": "password",
            },
            #data reqd for virtual machine creation
            "virtual_machine" : {
                "name" : "testvmshr",
                "displayname" : "Test VM shr",
            },
            #small service offering
            "service_offering": {
                "small": {
                    "name": "SOSmall",
                    "displaytext": "Small Instance",
                    "cpunumber": 1,
                    "cpuspeed": 2000,
                    "memory": 1024,
                },
            },
            "ostype": 'CentOS 6.4 (64-bit)',
        }


1. Account is successfully created
2. Service offering is successfully created
3. Management server logs - management-server.log has following error:


2014-01-02 01:43:40,693 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
Lock is released for network Ntwk[326|Guest|15] as a part of network
shutdown
2014-01-02 01:43:40,695 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
Lock is released for network id 326 as a part of network implement
2014-01-02 01:43:40,695 INFO  [cloud.vm.VirtualMachineManagerImpl]
(Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
Insufficient capacity
com.cloud.exception.InsufficientAddressCapacityException: Insufficient
address capacityScope=interface com.cloud.dc.DataCenter; id=1
at
com.cloud.network.NetworkManagerImpl.fetchNewPublicIp(NetworkManagerImpl.java:479)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
com.cloud.network.NetworkManagerImpl.assignDedicateIpAddress(NetworkManagerImpl.java:613)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
com.cloud.network.NetworkManagerImpl.assignSourceNatIpAddressToGuestNetwork(NetworkManagerImpl.java:582)
at
com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:2013)
at
com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1939)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2120)
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:887)
at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
at
org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
at
org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2014-01-02 01:43:40,703 DEBUG [cloud.vm.VirtualMachineManagerImpl]
(Job-Executor-109:job-26355 = [ 78b8af27-89dc-426e-bba7-acf693f071f2 ])
Cleaning up resources for the vm VM[User|testvmshr] in Starting state

4. When i checked the database for the network id 326 in table "networks",
it has following entry:

| 326 | test-TestDeployVM-test_deploy_vm-QQ91N0-network |
b7cb9e31-835f-47e3-9585-97e3b4084e4d |
test-TestDeployVM-test_deploy_vm-QQ91N0-network | Guest        | Vlan
           | NULL          | 10.1.1.1       | 10.1.1.0/24     | Dhcp   |
               15 |                 200 |              1 |
ExternalGuestNetworkGuru | Destroy     |     326 |         1 |        305 |
8.8.8.8 | 8.8.4.4 | NULL      |          0 | Account  | cs131cloud.internal
| ecf5b617-04da-469b-b378-f53e05d8cc53 | Isolated   |                0 |
2014-01-02 06:43:39 | 2014-01-02 06:43:46 |                 0 |   NULL |
NULL        | NULL     | NULL         |               1 |           NULL |


Basically it tries to create a network offering (id=15) : "HA Isolated
Network With Source Nat"


5. I think the script creates a network shown in above table:
"test-TestDeployVM-test_deploy_vm-QQ91N0-network".

I am not sure why it still gives the Insufficient address capacityScope
exception.

6. One more thing i observed. I have provided the "ostype": 'CentOS 6.4
(64-bit)'. But in DeployVMCmd it uses the template id:
"03ffb96f-2cfa-11e3-a4f0-f245a5b3ba0f" which is for template "Windows
Server 2008 R2 Enterprise with SQL 2012 Web Edition".


I am attaching the management-server logs and script logs for references.

If somebody can help me what's wrong here, would really be helpful.


Thanks and Regards
-- Umesh Kute


On Thu, Jan 2, 2014 at 2:59 PM, Santhosh Edukulla <
santhosh.edukulla@citrix.com> wrote:

> 1. Is it still failing post this registration?
>
> 2. If yes, may be you can verify\provide the management server logs.
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com]
> Sent: Thursday, January 02, 2014 4:16 AM
> To: users@cloudstack.apache.org
> Cc: Chandan Purushothama; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Thanks Santhosh.
> Yes, I have registered the following template which i am using.
>
> "ostype": 'CentOS 6.4 (64-bit)',
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Mon, Dec 30, 2013 at 5:50 PM, Santhosh Edukulla <
> santhosh.edukulla@citrix.com> wrote:
>
> > Umesh,
> >
> > One question : Did you registered the template for ostype:     "ostype":
> > 'CentOS 5.3 (64-bit)'?
> >
> > Regards,
> > Santhosh
> > ________________________________________
> > From: umesh kute [umeshvkute@gmail.com]
> > Sent: Monday, December 30, 2013 6:32 AM
> > To: Chandan Purushothama
> > Cc: users@cloudstack.apache.org; Sudha Ponnaganti
> > Subject: Re: Regarding cloudstack automation
> >
> > Hi Chandan,
> > Thanks for your response.
> > I have the latest Marvin repository (December 20th). I am able to proceed
> > further. There was an issue of firewall for that machine and it got
> > resolved.
> >
> > But now i am getting another error when i tried to run the script
> > "test_deploy_vm.py"
> >
> > I have attached the log. Can somebody please have a look on it and help
> me
> > in resolving the issue?
> >
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > test_deploy_vm (integration.smoke.test_deploy_vm.TestDeployVM): CRITICAL:
> > EXCEPTION: test_deploy_vm: Traceback (most recent call last):
> >   File "/usr/local/lib/python2.7/unittest/case.py", line 327, in run
> >     testMethod()
> >   File
> > "/DataDisk/temp/cloudstack/test/integration/smoke/test_deploy_vm.py",
> line
> > 116, in test_deploy_vm
> >     templateid=self.template.id<http://self.template.id>
> >   File
> > "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py",
> > line 415, in create
> >     virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> > line 593, in deployVirtualMachine
> >     response = self.connection.marvinRequest(command,
> > response_type=response, method=method)
> >   File
> > "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> > line 280, in marvinRequest
> >     response = self.poll(asyncJobId, response_type)
> >   File
> > "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> > line 86, in poll
> >     "asyncquery", asyncResonse.jobresult)
> > cloudstackAPIException: Execute cmd: asyncquery failed, due to:
> {errorcode
> > : 533, errortext : u'Unable to create a deployment for
> VM[User|testvmshr]'}
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > PFA entire logs.
> >
> > Please let me know in case if anything is required.
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> > On Sun, Dec 29, 2013 at 10:32 PM, Chandan Purushothama <
> > Chandan.Purushothama@citrix.com<ma...@citrix.com>>
> > wrote:
> >
> > Hello Umesh,
> >
> > I had a similar experience with an older Marvin build. I updated mine to
> > the latest and tried again and it worked. I recommend you to kindly try
> > again with the latest Marvin build and see if you are able to work with
> the
> > automation framework,
> >
> > Thank you,
> > Chandan
> >
> >
> > -------- Original message --------
> > From: umesh kute
> > Date:12/26/2013 12:29 AM (GMT-08:00)
> > To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org
> >,Sudha
> > Ponnaganti
> > Subject: Re: Regarding cloudstack automation
> >
> > Hi All,
> > I have created a Marvin setup on CentOS6.3 by following the document:
> >
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> >
> > All the pre-requisites are installed successfully.
> >
> > I tried to run the sample script test_deploy_vm.py
> > (cloudstack/test/integration/smoke/), I am getting following error:
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > [root@localhost smoke]# nosetests --with-marvin
> > --marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg
> --load
> > test_deploy_vm.py
> >
> >  Exception Occurred Under __deployDC :
> > HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> > with url: /client/api?account=admin&command=listUsers&response=json
> (Caused
> > by <class 'socket.error'>: [Errno 110] Connection timed out)
> > Traceback (most recent call last):
> >   File "/usr/local/bin/nosetests", line 9, in <module>
> >     load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> > line 118, in __init__
> >     **extra_args)
> >   File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
> >     self.runTests()
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> > line 197, in runTests
> >     result = self.testRunner.run(self.test)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> > line 61, in run
> >     test(result)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 176, in __call__
> >     return self.run(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> > line 223, in run
> >     test(orig)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> > line 45, in __call__
> >     return self.run(*arg, **kwarg)
> >   File
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> > line 138, in run
> >     result.addError(self, err)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
> > line 124, in addError
> >     plugin_handled = plugins.handleError(self.test, err)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> > line 99, in __call__
> >     return self.call(*arg, **kw)
> >   File
> >
> >
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> > line 167, in simple
> >     result = meth(*arg, **kw)
> >   File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
> > line 155, in handleError
> >     self.tcRunLogger.fatal("%s: %s: %s" %
> > AttributeError: 'NoneType' object has no attribute 'fatal'
> >
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > The logs are generated at /tmp and the log has following error.
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > 2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
> > {'account': 'admin'}
> > 2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
> > http://10.88.91.100:8096/client/api :
> > HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> > with url: /client/api?account=admin&command=listUsers&response=json
> (Caused
> > by <class 'socket.error'>: [Errno 110] Connection timed out)
> >
> >
> >
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > Please note: I have opened the integration port 8096 on management
> server.
> > Also, changed the global settings integration.api.port
> > on cloudstack GUI to 8096 and restarted the management server.
> >
> > Still I am getting the above issue. I am not sure if i missed any
> > configuration.
> >
> > Can somebody please help me with resolution of this issue?
> > Appreciate your help here!!!
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> > On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <umeshvkute@gmail.com<mailto:
> > umeshvkute@gmail.com>> wrote:
> >
> > > Thanks a lot Sudha for your quick response.
> > > I will setup the Marvin on local machine and get back in case if I face
> > > any challenges in setup.
> > >
> > > Thanks and Regards
> > > -- Umesh Kute
> > >
> > >
> > >
> > > On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
> > > sudha.ponnaganti@citrix.com<ma...@citrix.com>>
> wrote:
> > >
> > >> Hi Umesh,
> > >>
> > >> Looks like you have started on right track - Marvin is the framework
> to
> > >> use for functional or integration automation.
> > >> There are sizable number of test cases exist and you can review them.
> > >>  There are some wiki pages already written explaining Marvin [1]. Also
> > best
> > >> practices are published by community as well [2]. You can contribute
> to
> > it
> > >> as much as you can.
> > >>
> > >> Besides this, there is Junit framework (unit Test), Selenium framework
> > >> (UI automation) which are not as popular as Marvin. Marvin is perfect
> > for
> > >> majority of the validation. You can use simulator as well with Marvin.
> > >>
> > >> Please do pursue these and post questions to the community if you run
> in
> > >> to any issues in setting up env and running tests. There are jobs
> setup
> > by
> > >> various community members to test Master or current releases in
> various
> > >> labs and can help answer questions.
> > >>
> > >> [1]
> > >>
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> > >>
> > >>
> > >> Thanks
> > >> /Sudha
> > >>
> > >>
> > >> -----Original Message-----
> > >> From: umesh kute [mailto:umeshvkute@gmail.com]
> > >> Sent: Saturday, December 07, 2013 10:29 PM
> > >> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
> > >> Subject: Regarding cloudstack automation
> > >>
> > >> Hi All,
> > >> Good morning !!!
> > >> I am working as QA engineer and I am new to the cloudstack community.
> > >> We have started using cloudstack and deployed it in our
> infrastructure.
> > >>
> > >> Can somebody please help me in identifying the good automation
> > >> framework/tool/anything? The main intention is we want to automate the
> > >> infrastructure validation related cases (for e.g. create/update/delete
> > >> cases for instances, project, network, etc...)
> > >>
> > >> It would be good if you can help in identifying it.
> > >>
> > >> Please note: I have gone through cloudmonkey. But i haven't found much
> > >> help on it. May be i need to search a bit more.. I am also going
> through
> > >> the marvin and planning to setup it. If apart from these two, if
> anyone
> > has
> > >> different view please suggest.
> > >>
> > >> Also, if somebody has any pointers on cloudmonkey and marvin or any
> more
> > >> info on this (like, if it would suffice the infrastructure validation
> > >> related cases i mentioned above) any pros/cons would really be helpful
> > for
> > >> me...
> > >>
> > >> Appreciate any help on this and looking forward for the response on
> > >> this!!!
> > >>
> > >> Thanks and Regards
> > >> -- Umesh Kute
> > >>
> > >
> > >
> >
> >
>

RE: Regarding cloudstack automation

[Santhosh Edukulla <sa...@citrix.com>]

1. Is it still failing post this registration?

2. If yes, may be you can verify\provide the management server logs.
________________________________________
From: umesh kute [umeshvkute@gmail.com]
Sent: Thursday, January 02, 2014 4:16 AM
To: users@cloudstack.apache.org
Cc: Chandan Purushothama; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Thanks Santhosh.
Yes, I have registered the following template which i am using.

"ostype": 'CentOS 6.4 (64-bit)',

Thanks and Regards
-- Umesh Kute


On Mon, Dec 30, 2013 at 5:50 PM, Santhosh Edukulla <
santhosh.edukulla@citrix.com> wrote:

> Umesh,
>
> One question : Did you registered the template for ostype:     "ostype":
> 'CentOS 5.3 (64-bit)'?
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com]
> Sent: Monday, December 30, 2013 6:32 AM
> To: Chandan Purushothama
> Cc: users@cloudstack.apache.org; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi Chandan,
> Thanks for your response.
> I have the latest Marvin repository (December 20th). I am able to proceed
> further. There was an issue of firewall for that machine and it got
> resolved.
>
> But now i am getting another error when i tried to run the script
> "test_deploy_vm.py"
>
> I have attached the log. Can somebody please have a look on it and help me
> in resolving the issue?
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> test_deploy_vm (integration.smoke.test_deploy_vm.TestDeployVM): CRITICAL:
> EXCEPTION: test_deploy_vm: Traceback (most recent call last):
>   File "/usr/local/lib/python2.7/unittest/case.py", line 327, in run
>     testMethod()
>   File
> "/DataDisk/temp/cloudstack/test/integration/smoke/test_deploy_vm.py", line
> 116, in test_deploy_vm
>     templateid=self.template.id<http://self.template.id>
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py",
> line 415, in create
>     virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> line 593, in deployVirtualMachine
>     response = self.connection.marvinRequest(command,
> response_type=response, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 280, in marvinRequest
>     response = self.poll(asyncJobId, response_type)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 86, in poll
>     "asyncquery", asyncResonse.jobresult)
> cloudstackAPIException: Execute cmd: asyncquery failed, due to: {errorcode
> : 533, errortext : u'Unable to create a deployment for VM[User|testvmshr]'}
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> PFA entire logs.
>
> Please let me know in case if anything is required.
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Sun, Dec 29, 2013 at 10:32 PM, Chandan Purushothama <
> Chandan.Purushothama@citrix.com<ma...@citrix.com>>
> wrote:
>
> Hello Umesh,
>
> I had a similar experience with an older Marvin build. I updated mine to
> the latest and tried again and it worked. I recommend you to kindly try
> again with the latest Marvin build and see if you are able to work with the
> automation framework,
>
> Thank you,
> Chandan
>
>
> -------- Original message --------
> From: umesh kute
> Date:12/26/2013 12:29 AM (GMT-08:00)
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>,Sudha
> Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi All,
> I have created a Marvin setup on CentOS6.3 by following the document:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
>
> All the pre-requisites are installed successfully.
>
> I tried to run the sample script test_deploy_vm.py
> (cloudstack/test/integration/smoke/), I am getting following error:
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> [root@localhost smoke]# nosetests --with-marvin
> --marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg --load
> test_deploy_vm.py
>
>  Exception Occurred Under __deployDC :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
> Traceback (most recent call last):
>   File "/usr/local/bin/nosetests", line 9, in <module>
>     load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 118, in __init__
>     **extra_args)
>   File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
>     self.runTests()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 197, in runTests
>     result = self.testRunner.run(self.test)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 61, in run
>     test(result)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 45, in __call__
>     return self.run(*arg, **kwarg)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 138, in run
>     result.addError(self, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
> line 124, in addError
>     plugin_handled = plugins.handleError(self.test, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 99, in __call__
>     return self.call(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 167, in simple
>     result = meth(*arg, **kw)
>   File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
> line 155, in handleError
>     self.tcRunLogger.fatal("%s: %s: %s" %
> AttributeError: 'NoneType' object has no attribute 'fatal'
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> The logs are generated at /tmp and the log has following error.
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
> {'account': 'admin'}
> 2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
> http://10.88.91.100:8096/client/api :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Please note: I have opened the integration port 8096 on management server.
> Also, changed the global settings integration.api.port
> on cloudstack GUI to 8096 and restarted the management server.
>
> Still I am getting the above issue. I am not sure if i missed any
> configuration.
>
> Can somebody please help me with resolution of this issue?
> Appreciate your help here!!!
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>> wrote:
>
> > Thanks a lot Sudha for your quick response.
> > I will setup the Marvin on local machine and get back in case if I face
> > any challenges in setup.
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> >
> > On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
> > sudha.ponnaganti@citrix.com<ma...@citrix.com>> wrote:
> >
> >> Hi Umesh,
> >>
> >> Looks like you have started on right track - Marvin is the framework to
> >> use for functional or integration automation.
> >> There are sizable number of test cases exist and you can review them.
> >>  There are some wiki pages already written explaining Marvin [1]. Also
> best
> >> practices are published by community as well [2]. You can contribute to
> it
> >> as much as you can.
> >>
> >> Besides this, there is Junit framework (unit Test), Selenium framework
> >> (UI automation) which are not as popular as Marvin. Marvin is perfect
> for
> >> majority of the validation. You can use simulator as well with Marvin.
> >>
> >> Please do pursue these and post questions to the community if you run in
> >> to any issues in setting up env and running tests. There are jobs setup
> by
> >> various community members to test Master or current releases in various
> >> labs and can help answer questions.
> >>
> >> [1]
> >>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> >>
> >>
> >> Thanks
> >> /Sudha
> >>
> >>
> >> -----Original Message-----
> >> From: umesh kute [mailto:umeshvkute@gmail.com]
> >> Sent: Saturday, December 07, 2013 10:29 PM
> >> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
> >> Subject: Regarding cloudstack automation
> >>
> >> Hi All,
> >> Good morning !!!
> >> I am working as QA engineer and I am new to the cloudstack community.
> >> We have started using cloudstack and deployed it in our infrastructure.
> >>
> >> Can somebody please help me in identifying the good automation
> >> framework/tool/anything? The main intention is we want to automate the
> >> infrastructure validation related cases (for e.g. create/update/delete
> >> cases for instances, project, network, etc...)
> >>
> >> It would be good if you can help in identifying it.
> >>
> >> Please note: I have gone through cloudmonkey. But i haven't found much
> >> help on it. May be i need to search a bit more.. I am also going through
> >> the marvin and planning to setup it. If apart from these two, if anyone
> has
> >> different view please suggest.
> >>
> >> Also, if somebody has any pointers on cloudmonkey and marvin or any more
> >> info on this (like, if it would suffice the infrastructure validation
> >> related cases i mentioned above) any pros/cons would really be helpful
> for
> >> me...
> >>
> >> Appreciate any help on this and looking forward for the response on
> >> this!!!
> >>
> >> Thanks and Regards
> >> -- Umesh Kute
> >>
> >
> >
>
>

Re: Regarding cloudstack automation

[umesh kute <um...@gmail.com>]

Thanks Santhosh.
Yes, I have registered the following template which i am using.

"ostype": 'CentOS 6.4 (64-bit)',

Thanks and Regards
-- Umesh Kute


On Mon, Dec 30, 2013 at 5:50 PM, Santhosh Edukulla <
santhosh.edukulla@citrix.com> wrote:

> Umesh,
>
> One question : Did you registered the template for ostype:     "ostype":
> 'CentOS 5.3 (64-bit)'?
>
> Regards,
> Santhosh
> ________________________________________
> From: umesh kute [umeshvkute@gmail.com]
> Sent: Monday, December 30, 2013 6:32 AM
> To: Chandan Purushothama
> Cc: users@cloudstack.apache.org; Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi Chandan,
> Thanks for your response.
> I have the latest Marvin repository (December 20th). I am able to proceed
> further. There was an issue of firewall for that machine and it got
> resolved.
>
> But now i am getting another error when i tried to run the script
> "test_deploy_vm.py"
>
> I have attached the log. Can somebody please have a look on it and help me
> in resolving the issue?
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> test_deploy_vm (integration.smoke.test_deploy_vm.TestDeployVM): CRITICAL:
> EXCEPTION: test_deploy_vm: Traceback (most recent call last):
>   File "/usr/local/lib/python2.7/unittest/case.py", line 327, in run
>     testMethod()
>   File
> "/DataDisk/temp/cloudstack/test/integration/smoke/test_deploy_vm.py", line
> 116, in test_deploy_vm
>     templateid=self.template.id<http://self.template.id>
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py",
> line 415, in create
>     virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> line 593, in deployVirtualMachine
>     response = self.connection.marvinRequest(command,
> response_type=response, method=method)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 280, in marvinRequest
>     response = self.poll(asyncJobId, response_type)
>   File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 86, in poll
>     "asyncquery", asyncResonse.jobresult)
> cloudstackAPIException: Execute cmd: asyncquery failed, due to: {errorcode
> : 533, errortext : u'Unable to create a deployment for VM[User|testvmshr]'}
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> PFA entire logs.
>
> Please let me know in case if anything is required.
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Sun, Dec 29, 2013 at 10:32 PM, Chandan Purushothama <
> Chandan.Purushothama@citrix.com<ma...@citrix.com>>
> wrote:
>
> Hello Umesh,
>
> I had a similar experience with an older Marvin build. I updated mine to
> the latest and tried again and it worked. I recommend you to kindly try
> again with the latest Marvin build and see if you are able to work with the
> automation framework,
>
> Thank you,
> Chandan
>
>
> -------- Original message --------
> From: umesh kute
> Date:12/26/2013 12:29 AM (GMT-08:00)
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>,Sudha
> Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
> Hi All,
> I have created a Marvin setup on CentOS6.3 by following the document:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
>
> All the pre-requisites are installed successfully.
>
> I tried to run the sample script test_deploy_vm.py
> (cloudstack/test/integration/smoke/), I am getting following error:
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> [root@localhost smoke]# nosetests --with-marvin
> --marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg --load
> test_deploy_vm.py
>
>  Exception Occurred Under __deployDC :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
> Traceback (most recent call last):
>   File "/usr/local/bin/nosetests", line 9, in <module>
>     load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 118, in __init__
>     **extra_args)
>   File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
>     self.runTests()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 197, in runTests
>     result = self.testRunner.run(self.test)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 61, in run
>     test(result)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 45, in __call__
>     return self.run(*arg, **kwarg)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 138, in run
>     result.addError(self, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
> line 124, in addError
>     plugin_handled = plugins.handleError(self.test, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 99, in __call__
>     return self.call(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 167, in simple
>     result = meth(*arg, **kw)
>   File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
> line 155, in handleError
>     self.tcRunLogger.fatal("%s: %s: %s" %
> AttributeError: 'NoneType' object has no attribute 'fatal'
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> The logs are generated at /tmp and the log has following error.
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
> {'account': 'admin'}
> 2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
> http://10.88.91.100:8096/client/api :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Please note: I have opened the integration port 8096 on management server.
> Also, changed the global settings integration.api.port
> on cloudstack GUI to 8096 and restarted the management server.
>
> Still I am getting the above issue. I am not sure if i missed any
> configuration.
>
> Can somebody please help me with resolution of this issue?
> Appreciate your help here!!!
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <umeshvkute@gmail.com<mailto:
> umeshvkute@gmail.com>> wrote:
>
> > Thanks a lot Sudha for your quick response.
> > I will setup the Marvin on local machine and get back in case if I face
> > any challenges in setup.
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> >
> > On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
> > sudha.ponnaganti@citrix.com<ma...@citrix.com>> wrote:
> >
> >> Hi Umesh,
> >>
> >> Looks like you have started on right track - Marvin is the framework to
> >> use for functional or integration automation.
> >> There are sizable number of test cases exist and you can review them.
> >>  There are some wiki pages already written explaining Marvin [1]. Also
> best
> >> practices are published by community as well [2]. You can contribute to
> it
> >> as much as you can.
> >>
> >> Besides this, there is Junit framework (unit Test), Selenium framework
> >> (UI automation) which are not as popular as Marvin. Marvin is perfect
> for
> >> majority of the validation. You can use simulator as well with Marvin.
> >>
> >> Please do pursue these and post questions to the community if you run in
> >> to any issues in setting up env and running tests. There are jobs setup
> by
> >> various community members to test Master or current releases in various
> >> labs and can help answer questions.
> >>
> >> [1]
> >>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> >>
> >>
> >> Thanks
> >> /Sudha
> >>
> >>
> >> -----Original Message-----
> >> From: umesh kute [mailto:umeshvkute@gmail.com]
> >> Sent: Saturday, December 07, 2013 10:29 PM
> >> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
> >> Subject: Regarding cloudstack automation
> >>
> >> Hi All,
> >> Good morning !!!
> >> I am working as QA engineer and I am new to the cloudstack community.
> >> We have started using cloudstack and deployed it in our infrastructure.
> >>
> >> Can somebody please help me in identifying the good automation
> >> framework/tool/anything? The main intention is we want to automate the
> >> infrastructure validation related cases (for e.g. create/update/delete
> >> cases for instances, project, network, etc...)
> >>
> >> It would be good if you can help in identifying it.
> >>
> >> Please note: I have gone through cloudmonkey. But i haven't found much
> >> help on it. May be i need to search a bit more.. I am also going through
> >> the marvin and planning to setup it. If apart from these two, if anyone
> has
> >> different view please suggest.
> >>
> >> Also, if somebody has any pointers on cloudmonkey and marvin or any more
> >> info on this (like, if it would suffice the infrastructure validation
> >> related cases i mentioned above) any pros/cons would really be helpful
> for
> >> me...
> >>
> >> Appreciate any help on this and looking forward for the response on
> >> this!!!
> >>
> >> Thanks and Regards
> >> -- Umesh Kute
> >>
> >
> >
>
>

RE: Regarding cloudstack automation

[Santhosh Edukulla <sa...@citrix.com>]

Umesh,

One question : Did you registered the template for ostype:     "ostype": 'CentOS 5.3 (64-bit)'? 

Regards,
Santhosh
________________________________________
From: umesh kute [umeshvkute@gmail.com]
Sent: Monday, December 30, 2013 6:32 AM
To: Chandan Purushothama
Cc: users@cloudstack.apache.org; Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Hi Chandan,
Thanks for your response.
I have the latest Marvin repository (December 20th). I am able to proceed further. There was an issue of firewall for that machine and it got resolved.

But now i am getting another error when i tried to run the script "test_deploy_vm.py"

I have attached the log. Can somebody please have a look on it and help me in resolving the issue?

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
test_deploy_vm (integration.smoke.test_deploy_vm.TestDeployVM): CRITICAL: EXCEPTION: test_deploy_vm: Traceback (most recent call last):
  File "/usr/local/lib/python2.7/unittest/case.py", line 327, in run
    testMethod()
  File "/DataDisk/temp/cloudstack/test/integration/smoke/test_deploy_vm.py", line 116, in test_deploy_vm
    templateid=self.template.id<http://self.template.id>
  File "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py", line 415, in create
    virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
  File "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py", line 593, in deployVirtualMachine
    response = self.connection.marvinRequest(command, response_type=response, method=method)
  File "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py", line 280, in marvinRequest
    response = self.poll(asyncJobId, response_type)
  File "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py", line 86, in poll
    "asyncquery", asyncResonse.jobresult)
cloudstackAPIException: Execute cmd: asyncquery failed, due to: {errorcode : 533, errortext : u'Unable to create a deployment for VM[User|testvmshr]'}
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

PFA entire logs.

Please let me know in case if anything is required.

Thanks and Regards
-- Umesh Kute


On Sun, Dec 29, 2013 at 10:32 PM, Chandan Purushothama <Ch...@citrix.com>> wrote:

Hello Umesh,

I had a similar experience with an older Marvin build. I updated mine to the latest and tried again and it worked. I recommend you to kindly try again with the latest Marvin build and see if you are able to work with the automation framework,

Thank you,
Chandan


-------- Original message --------
From: umesh kute
Date:12/26/2013 12:29 AM (GMT-08:00)
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>,Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Hi All,
I have created a Marvin setup on CentOS6.3 by following the document:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python

All the pre-requisites are installed successfully.

I tried to run the sample script test_deploy_vm.py
(cloudstack/test/integration/smoke/), I am getting following error:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[root@localhost smoke]# nosetests --with-marvin
--marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg --load
test_deploy_vm.py

 Exception Occurred Under __deployDC :
HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
with url: /client/api?account=admin&command=listUsers&response=json (Caused
by <class 'socket.error'>: [Errno 110] Connection timed out)
Traceback (most recent call last):
  File "/usr/local/bin/nosetests", line 9, in <module>
    load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
line 118, in __init__
    **extra_args)
  File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
    self.runTests()
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
line 197, in runTests
    result = self.testRunner.run(self.test)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
line 61, in run
    test(result)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 176, in __call__
    return self.run(*arg, **kw)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 223, in run
    test(orig)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 176, in __call__
    return self.run(*arg, **kw)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 223, in run
    test(orig)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 176, in __call__
    return self.run(*arg, **kw)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 223, in run
    test(orig)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 176, in __call__
    return self.run(*arg, **kw)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 223, in run
    test(orig)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 176, in __call__
    return self.run(*arg, **kw)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 223, in run
    test(orig)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 176, in __call__
    return self.run(*arg, **kw)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 223, in run
    test(orig)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
line 45, in __call__
    return self.run(*arg, **kwarg)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
line 138, in run
    result.addError(self, err)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
line 124, in addError
    plugin_handled = plugins.handleError(self.test, err)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
line 99, in __call__
    return self.call(*arg, **kw)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
line 167, in simple
    result = meth(*arg, **kw)
  File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
line 155, in handleError
    self.tcRunLogger.fatal("%s: %s: %s" %
AttributeError: 'NoneType' object has no attribute 'fatal'

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

The logs are generated at /tmp and the log has following error.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
{'account': 'admin'}
2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
http://10.88.91.100:8096/client/api :
HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
with url: /client/api?account=admin&command=listUsers&response=json (Caused
by <class 'socket.error'>: [Errno 110] Connection timed out)

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Please note: I have opened the integration port 8096 on management server.
Also, changed the global settings integration.api.port
on cloudstack GUI to 8096 and restarted the management server.

Still I am getting the above issue. I am not sure if i missed any
configuration.

Can somebody please help me with resolution of this issue?
Appreciate your help here!!!

Thanks and Regards
-- Umesh Kute


On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <um...@gmail.com>> wrote:

> Thanks a lot Sudha for your quick response.
> I will setup the Marvin on local machine and get back in case if I face
> any challenges in setup.
>
> Thanks and Regards
> -- Umesh Kute
>
>
>
> On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
> sudha.ponnaganti@citrix.com<ma...@citrix.com>> wrote:
>
>> Hi Umesh,
>>
>> Looks like you have started on right track - Marvin is the framework to
>> use for functional or integration automation.
>> There are sizable number of test cases exist and you can review them.
>>  There are some wiki pages already written explaining Marvin [1]. Also best
>> practices are published by community as well [2]. You can contribute to it
>> as much as you can.
>>
>> Besides this, there is Junit framework (unit Test), Selenium framework
>> (UI automation) which are not as popular as Marvin. Marvin is perfect for
>> majority of the validation. You can use simulator as well with Marvin.
>>
>> Please do pursue these and post questions to the community if you run in
>> to any issues in setting up env and running tests. There are jobs setup by
>> various community members to test Master or current releases in various
>> labs and can help answer questions.
>>
>> [1]
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
>>
>>
>> Thanks
>> /Sudha
>>
>>
>> -----Original Message-----
>> From: umesh kute [mailto:umeshvkute@gmail.com]
>> Sent: Saturday, December 07, 2013 10:29 PM
>> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
>> Subject: Regarding cloudstack automation
>>
>> Hi All,
>> Good morning !!!
>> I am working as QA engineer and I am new to the cloudstack community.
>> We have started using cloudstack and deployed it in our infrastructure.
>>
>> Can somebody please help me in identifying the good automation
>> framework/tool/anything? The main intention is we want to automate the
>> infrastructure validation related cases (for e.g. create/update/delete
>> cases for instances, project, network, etc...)
>>
>> It would be good if you can help in identifying it.
>>
>> Please note: I have gone through cloudmonkey. But i haven't found much
>> help on it. May be i need to search a bit more.. I am also going through
>> the marvin and planning to setup it. If apart from these two, if anyone has
>> different view please suggest.
>>
>> Also, if somebody has any pointers on cloudmonkey and marvin or any more
>> info on this (like, if it would suffice the infrastructure validation
>> related cases i mentioned above) any pros/cons would really be helpful for
>> me...
>>
>> Appreciate any help on this and looking forward for the response on
>> this!!!
>>
>> Thanks and Regards
>> -- Umesh Kute
>>
>
>

Re: Regarding cloudstack automation

[umesh kute <um...@gmail.com>]

Hi Chandan,
Thanks for your response.
I have the latest Marvin repository (December 20th). I am able to proceed
further. There was an issue of firewall for that machine and it got
resolved.

But now i am getting another error when i tried to run the script
"test_deploy_vm.py"

I have attached the log. Can somebody please have a look on it and help me
in resolving the issue?

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
test_deploy_vm (integration.smoke.test_deploy_vm.TestDeployVM): CRITICAL:
EXCEPTION: test_deploy_vm: Traceback (most recent call last):
  File "/usr/local/lib/python2.7/unittest/case.py", line 327, in run
    testMethod()
  File
"/DataDisk/temp/cloudstack/test/integration/smoke/test_deploy_vm.py", line
116, in test_deploy_vm
    templateid=self.template.id
  File
"/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py",
line 415, in create
    virtual_machine = apiclient.deployVirtualMachine(cmd, method=method)
  File
"/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
line 593, in deployVirtualMachine
    response = self.connection.marvinRequest(command,
response_type=response, method=method)
  File
"/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
line 280, in marvinRequest
    response = self.poll(asyncJobId, response_type)
  File
"/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
line 86, in poll
    "asyncquery", asyncResonse.jobresult)
cloudstackAPIException: Execute cmd: asyncquery failed, due to: {errorcode
: 533, errortext : u'Unable to create a deployment for VM[User|testvmshr]'}
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

PFA entire logs.

Please let me know in case if anything is required.

Thanks and Regards
-- Umesh Kute


On Sun, Dec 29, 2013 at 10:32 PM, Chandan Purushothama <
Chandan.Purushothama@citrix.com> wrote:

>
>  Hello Umesh,
>
>  I had a similar experience with an older Marvin build. I updated mine to
> the latest and tried again and it worked. I recommend you to kindly try
> again with the latest Marvin build and see if you are able to work with the
> automation framework,
>
>  Thank you,
> Chandan
>
>
> -------- Original message --------
> From: umesh kute
> Date:12/26/2013 12:29 AM (GMT-08:00)
> To: users@cloudstack.apache.org,Sudha Ponnaganti
> Subject: Re: Regarding cloudstack automation
>
>  Hi All,
> I have created a Marvin setup on CentOS6.3 by following the document:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
>
> All the pre-requisites are installed successfully.
>
> I tried to run the sample script test_deploy_vm.py
> (cloudstack/test/integration/smoke/), I am getting following error:
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> [root@localhost smoke]# nosetests --with-marvin
> --marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg --load
> test_deploy_vm.py
>
>  Exception Occurred Under __deployDC :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
> Traceback (most recent call last):
>   File "/usr/local/bin/nosetests", line 9, in <module>
>     load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 118, in __init__
>     **extra_args)
>   File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
>     self.runTests()
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 197, in runTests
>     result = self.testRunner.run(self.test)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
> line 61, in run
>     test(result)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 176, in __call__
>     return self.run(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
> line 223, in run
>     test(orig)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 45, in __call__
>     return self.run(*arg, **kwarg)
>   File
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
> line 138, in run
>     result.addError(self, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
> line 124, in addError
>     plugin_handled = plugins.handleError(self.test, err)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 99, in __call__
>     return self.call(*arg, **kw)
>   File
>
> "/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
> line 167, in simple
>     result = meth(*arg, **kw)
>   File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
> line 155, in handleError
>     self.tcRunLogger.fatal("%s: %s: %s" %
> AttributeError: 'NoneType' object has no attribute 'fatal'
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> The logs are generated at /tmp and the log has following error.
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
> {'account': 'admin'}
> 2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
> http://10.88.91.100:8096/client/api :
> HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
> with url: /client/api?account=admin&command=listUsers&response=json (Caused
> by <class 'socket.error'>: [Errno 110] Connection timed out)
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Please note: I have opened the integration port 8096 on management server.
> Also, changed the global settings integration.api.port
> on cloudstack GUI to 8096 and restarted the management server.
>
> Still I am getting the above issue. I am not sure if i missed any
> configuration.
>
> Can somebody please help me with resolution of this issue?
> Appreciate your help here!!!
>
> Thanks and Regards
> -- Umesh Kute
>
>
> On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <um...@gmail.com> wrote:
>
> > Thanks a lot Sudha for your quick response.
> > I will setup the Marvin on local machine and get back in case if I face
> > any challenges in setup.
> >
> > Thanks and Regards
> > -- Umesh Kute
> >
> >
> >
> > On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
> > sudha.ponnaganti@citrix.com> wrote:
> >
> >> Hi Umesh,
> >>
> >> Looks like you have started on right track - Marvin is the framework to
> >> use for functional or integration automation.
> >> There are sizable number of test cases exist and you can review them.
> >>  There are some wiki pages already written explaining Marvin [1]. Also
> best
> >> practices are published by community as well [2]. You can contribute to
> it
> >> as much as you can.
> >>
> >> Besides this, there is Junit framework (unit Test), Selenium framework
> >> (UI automation) which are not as popular as Marvin. Marvin is perfect
> for
> >> majority of the validation. You can use simulator as well with Marvin.
> >>
> >> Please do pursue these and post questions to the community if you run in
> >> to any issues in setting up env and running tests. There are jobs setup
> by
> >> various community members to test Master or current releases in various
> >> labs and can help answer questions.
> >>
> >> [1]
> >>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> >>
> >>
> >> Thanks
> >> /Sudha
> >>
> >>
> >> -----Original Message-----
> >> From: umesh kute [mailto:umeshvkute@gmail.com <um...@gmail.com>]
> >> Sent: Saturday, December 07, 2013 10:29 PM
> >> To: users@cloudstack.apache.org
> >> Subject: Regarding cloudstack automation
> >>
> >> Hi All,
> >> Good morning !!!
> >> I am working as QA engineer and I am new to the cloudstack community.
> >> We have started using cloudstack and deployed it in our infrastructure.
> >>
> >> Can somebody please help me in identifying the good automation
> >> framework/tool/anything? The main intention is we want to automate the
> >> infrastructure validation related cases (for e.g. create/update/delete
> >> cases for instances, project, network, etc...)
> >>
> >> It would be good if you can help in identifying it.
> >>
> >> Please note: I have gone through cloudmonkey. But i haven't found much
> >> help on it. May be i need to search a bit more.. I am also going through
> >> the marvin and planning to setup it. If apart from these two, if anyone
> has
> >> different view please suggest.
> >>
> >> Also, if somebody has any pointers on cloudmonkey and marvin or any more
> >> info on this (like, if it would suffice the infrastructure validation
> >> related cases i mentioned above) any pros/cons would really be helpful
> for
> >> me...
> >>
> >> Appreciate any help on this and looking forward for the response on
> >> this!!!
> >>
> >> Thanks and Regards
> >> -- Umesh Kute
> >>
> >
> >
>

RE: Regarding cloudstack automation

[Chandan Purushothama <Ch...@citrix.com>]

Hello Umesh,

I had a similar experience with an older Marvin build. I updated mine to the latest and tried again and it worked. I recommend you to kindly try again with the latest Marvin build and see if you are able to work with the automation framework,

Thank you,
Chandan


-------- Original message --------
From: umesh kute
Date:12/26/2013 12:29 AM (GMT-08:00)
To: users@cloudstack.apache.org,Sudha Ponnaganti
Subject: Re: Regarding cloudstack automation

Hi All,
I have created a Marvin setup on CentOS6.3 by following the document:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python

All the pre-requisites are installed successfully.

I tried to run the sample script test_deploy_vm.py
(cloudstack/test/integration/smoke/), I am getting following error:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[root@localhost smoke]# nosetests --with-marvin
--marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg --load
test_deploy_vm.py

 Exception Occurred Under __deployDC :
HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
with url: /client/api?account=admin&command=listUsers&response=json (Caused
by <class 'socket.error'>: [Errno 110] Connection timed out)
Traceback (most recent call last):
  File "/usr/local/bin/nosetests", line 9, in <module>
    load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
line 118, in __init__
    **extra_args)
  File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
    self.runTests()
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
line 197, in runTests
    result = self.testRunner.run(self.test)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
line 61, in run
    test(result)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 176, in __call__
    return self.run(*arg, **kw)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 223, in run
    test(orig)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 176, in __call__
    return self.run(*arg, **kw)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 223, in run
    test(orig)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 176, in __call__
    return self.run(*arg, **kw)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 223, in run
    test(orig)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 176, in __call__
    return self.run(*arg, **kw)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 223, in run
    test(orig)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 176, in __call__
    return self.run(*arg, **kw)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 223, in run
    test(orig)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 176, in __call__
    return self.run(*arg, **kw)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 223, in run
    test(orig)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
line 45, in __call__
    return self.run(*arg, **kwarg)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
line 138, in run
    result.addError(self, err)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
line 124, in addError
    plugin_handled = plugins.handleError(self.test, err)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
line 99, in __call__
    return self.call(*arg, **kw)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
line 167, in simple
    result = meth(*arg, **kw)
  File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
line 155, in handleError
    self.tcRunLogger.fatal("%s: %s: %s" %
AttributeError: 'NoneType' object has no attribute 'fatal'

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

The logs are generated at /tmp and the log has following error.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
{'account': 'admin'}
2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
http://10.88.91.100:8096/client/api :
HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
with url: /client/api?account=admin&command=listUsers&response=json (Caused
by <class 'socket.error'>: [Errno 110] Connection timed out)

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Please note: I have opened the integration port 8096 on management server.
Also, changed the global settings integration.api.port
on cloudstack GUI to 8096 and restarted the management server.

Still I am getting the above issue. I am not sure if i missed any
configuration.

Can somebody please help me with resolution of this issue?
Appreciate your help here!!!

Thanks and Regards
-- Umesh Kute


On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <um...@gmail.com> wrote:

> Thanks a lot Sudha for your quick response.
> I will setup the Marvin on local machine and get back in case if I face
> any challenges in setup.
>
> Thanks and Regards
> -- Umesh Kute
>
>
>
> On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
> sudha.ponnaganti@citrix.com> wrote:
>
>> Hi Umesh,
>>
>> Looks like you have started on right track - Marvin is the framework to
>> use for functional or integration automation.
>> There are sizable number of test cases exist and you can review them.
>>  There are some wiki pages already written explaining Marvin [1]. Also best
>> practices are published by community as well [2]. You can contribute to it
>> as much as you can.
>>
>> Besides this, there is Junit framework (unit Test), Selenium framework
>> (UI automation) which are not as popular as Marvin. Marvin is perfect for
>> majority of the validation. You can use simulator as well with Marvin.
>>
>> Please do pursue these and post questions to the community if you run in
>> to any issues in setting up env and running tests. There are jobs setup by
>> various community members to test Master or current releases in various
>> labs and can help answer questions.
>>
>> [1]
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
>>
>>
>> Thanks
>> /Sudha
>>
>>
>> -----Original Message-----
>> From: umesh kute [mailto:umeshvkute@gmail.com]
>> Sent: Saturday, December 07, 2013 10:29 PM
>> To: users@cloudstack.apache.org
>> Subject: Regarding cloudstack automation
>>
>> Hi All,
>> Good morning !!!
>> I am working as QA engineer and I am new to the cloudstack community.
>> We have started using cloudstack and deployed it in our infrastructure.
>>
>> Can somebody please help me in identifying the good automation
>> framework/tool/anything? The main intention is we want to automate the
>> infrastructure validation related cases (for e.g. create/update/delete
>> cases for instances, project, network, etc...)
>>
>> It would be good if you can help in identifying it.
>>
>> Please note: I have gone through cloudmonkey. But i haven't found much
>> help on it. May be i need to search a bit more.. I am also going through
>> the marvin and planning to setup it. If apart from these two, if anyone has
>> different view please suggest.
>>
>> Also, if somebody has any pointers on cloudmonkey and marvin or any more
>> info on this (like, if it would suffice the infrastructure validation
>> related cases i mentioned above) any pros/cons would really be helpful for
>> me...
>>
>> Appreciate any help on this and looking forward for the response on
>> this!!!
>>
>> Thanks and Regards
>> -- Umesh Kute
>>
>
>

Re: Regarding cloudstack automation

[umesh kute <um...@gmail.com>]

Hi All,
I have created a Marvin setup on CentOS6.3 by following the document:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python

All the pre-requisites are installed successfully.

I tried to run the sample script test_deploy_vm.py
(cloudstack/test/integration/smoke/), I am getting following error:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[root@localhost smoke]# nosetests --with-marvin
--marvin-config=/DataDisk/temp/cloudstack/tools/marvin/dist/demo.cfg --load
test_deploy_vm.py

 Exception Occurred Under __deployDC :
HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
with url: /client/api?account=admin&command=listUsers&response=json (Caused
by <class 'socket.error'>: [Errno 110] Connection timed out)
Traceback (most recent call last):
  File "/usr/local/bin/nosetests", line 9, in <module>
    load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
line 118, in __init__
    **extra_args)
  File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
    self.runTests()
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
line 197, in runTests
    result = self.testRunner.run(self.test)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/core.py",
line 61, in run
    test(result)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 176, in __call__
    return self.run(*arg, **kw)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 223, in run
    test(orig)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 176, in __call__
    return self.run(*arg, **kw)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 223, in run
    test(orig)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 176, in __call__
    return self.run(*arg, **kw)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 223, in run
    test(orig)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 176, in __call__
    return self.run(*arg, **kw)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 223, in run
    test(orig)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 176, in __call__
    return self.run(*arg, **kw)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 223, in run
    test(orig)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 176, in __call__
    return self.run(*arg, **kw)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/suite.py",
line 223, in run
    test(orig)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
line 45, in __call__
    return self.run(*arg, **kwarg)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/case.py",
line 138, in run
    result.addError(self, err)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/proxy.py",
line 124, in addError
    plugin_handled = plugins.handleError(self.test, err)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
line 99, in __call__
    return self.call(*arg, **kw)
  File
"/usr/local/lib/python2.7/site-packages/nose-1.3.0-py2.7.egg/nose/plugins/manager.py",
line 167, in simple
    result = meth(*arg, **kw)
  File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py",
line 155, in handleError
    self.tcRunLogger.fatal("%s: %s: %s" %
AttributeError: 'NoneType' object has no attribute 'fatal'

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

The logs are generated at /tmp and the log has following error.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2013-12-26 13:40:51,797 - DEBUG - CSLog - sending GET request: listUsers
{'account': 'admin'}
2013-12-26 13:41:54,825 - DEBUG - CSLog - Connection refused. Reason:
http://10.88.91.100:8096/client/api :
HTTPConnectionPool(host='10.88.91.100', port=8096): Max retries exceeded
with url: /client/api?account=admin&command=listUsers&response=json (Caused
by <class 'socket.error'>: [Errno 110] Connection timed out)

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Please note: I have opened the integration port 8096 on management server.
Also, changed the global settings integration.api.port
on cloudstack GUI to 8096 and restarted the management server.

Still I am getting the above issue. I am not sure if i missed any
configuration.

Can somebody please help me with resolution of this issue?
Appreciate your help here!!!

Thanks and Regards
-- Umesh Kute


On Mon, Dec 9, 2013 at 1:57 PM, umesh kute <um...@gmail.com> wrote:

> Thanks a lot Sudha for your quick response.
> I will setup the Marvin on local machine and get back in case if I face
> any challenges in setup.
>
> Thanks and Regards
> -- Umesh Kute
>
>
>
> On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
> sudha.ponnaganti@citrix.com> wrote:
>
>> Hi Umesh,
>>
>> Looks like you have started on right track - Marvin is the framework to
>> use for functional or integration automation.
>> There are sizable number of test cases exist and you can review them.
>>  There are some wiki pages already written explaining Marvin [1]. Also best
>> practices are published by community as well [2]. You can contribute to it
>> as much as you can.
>>
>> Besides this, there is Junit framework (unit Test), Selenium framework
>> (UI automation) which are not as popular as Marvin. Marvin is perfect for
>> majority of the validation. You can use simulator as well with Marvin.
>>
>> Please do pursue these and post questions to the community if you run in
>> to any issues in setting up env and running tests. There are jobs setup by
>> various community members to test Master or current releases in various
>> labs and can help answer questions.
>>
>> [1]
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
>>
>>
>> Thanks
>> /Sudha
>>
>>
>> -----Original Message-----
>> From: umesh kute [mailto:umeshvkute@gmail.com]
>> Sent: Saturday, December 07, 2013 10:29 PM
>> To: users@cloudstack.apache.org
>> Subject: Regarding cloudstack automation
>>
>> Hi All,
>> Good morning !!!
>> I am working as QA engineer and I am new to the cloudstack community.
>> We have started using cloudstack and deployed it in our infrastructure.
>>
>> Can somebody please help me in identifying the good automation
>> framework/tool/anything? The main intention is we want to automate the
>> infrastructure validation related cases (for e.g. create/update/delete
>> cases for instances, project, network, etc...)
>>
>> It would be good if you can help in identifying it.
>>
>> Please note: I have gone through cloudmonkey. But i haven't found much
>> help on it. May be i need to search a bit more.. I am also going through
>> the marvin and planning to setup it. If apart from these two, if anyone has
>> different view please suggest.
>>
>> Also, if somebody has any pointers on cloudmonkey and marvin or any more
>> info on this (like, if it would suffice the infrastructure validation
>> related cases i mentioned above) any pros/cons would really be helpful for
>> me...
>>
>> Appreciate any help on this and looking forward for the response on
>> this!!!
>>
>> Thanks and Regards
>> -- Umesh Kute
>>
>
>

Re: Regarding cloudstack automation

[umesh kute <um...@gmail.com>]

Thanks a lot Sudha for your quick response.
I will setup the Marvin on local machine and get back in case if I face any
challenges in setup.

Thanks and Regards
-- Umesh Kute



On Sun, Dec 8, 2013 at 4:05 PM, Sudha Ponnaganti <
sudha.ponnaganti@citrix.com> wrote:

> Hi Umesh,
>
> Looks like you have started on right track - Marvin is the framework to
> use for functional or integration automation.
> There are sizable number of test cases exist and you can review them.
>  There are some wiki pages already written explaining Marvin [1]. Also best
> practices are published by community as well [2]. You can contribute to it
> as much as you can.
>
> Besides this, there is Junit framework (unit Test), Selenium framework (UI
> automation) which are not as popular as Marvin. Marvin is perfect for
> majority of the validation. You can use simulator as well with Marvin.
>
> Please do pursue these and post questions to the community if you run in
> to any issues in setting up env and running tests. There are jobs setup by
> various community members to test Master or current releases in various
> labs and can help answer questions.
>
> [1]
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
>
>
> Thanks
> /Sudha
>
>
> -----Original Message-----
> From: umesh kute [mailto:umeshvkute@gmail.com]
> Sent: Saturday, December 07, 2013 10:29 PM
> To: users@cloudstack.apache.org
> Subject: Regarding cloudstack automation
>
> Hi All,
> Good morning !!!
> I am working as QA engineer and I am new to the cloudstack community.
> We have started using cloudstack and deployed it in our infrastructure.
>
> Can somebody please help me in identifying the good automation
> framework/tool/anything? The main intention is we want to automate the
> infrastructure validation related cases (for e.g. create/update/delete
> cases for instances, project, network, etc...)
>
> It would be good if you can help in identifying it.
>
> Please note: I have gone through cloudmonkey. But i haven't found much
> help on it. May be i need to search a bit more.. I am also going through
> the marvin and planning to setup it. If apart from these two, if anyone has
> different view please suggest.
>
> Also, if somebody has any pointers on cloudmonkey and marvin or any more
> info on this (like, if it would suffice the infrastructure validation
> related cases i mentioned above) any pros/cons would really be helpful for
> me...
>
> Appreciate any help on this and looking forward for the response on this!!!
>
> Thanks and Regards
> -- Umesh Kute
>

RE: Regarding cloudstack automation

[Sudha Ponnaganti <su...@citrix.com>]

Hi Umesh,

Looks like you have started on right track - Marvin is the framework to use for functional or integration automation.
There are sizable number of test cases exist and you can review them.  There are some wiki pages already written explaining Marvin [1]. Also best practices are published by community as well [2]. You can contribute to it as much as you can. 

Besides this, there is Junit framework (unit Test), Selenium framework (UI automation) which are not as popular as Marvin. Marvin is perfect for majority of the validation. You can use simulator as well with Marvin. 

Please do pursue these and post questions to the community if you run in to any issues in setting up env and running tests. There are jobs setup by various community members to test Master or current releases in various labs and can help answer questions. 

[1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python


Thanks
/Sudha


-----Original Message-----
From: umesh kute [mailto:umeshvkute@gmail.com] 
Sent: Saturday, December 07, 2013 10:29 PM
To: users@cloudstack.apache.org
Subject: Regarding cloudstack automation

Hi All,
Good morning !!!
I am working as QA engineer and I am new to the cloudstack community.
We have started using cloudstack and deployed it in our infrastructure.

Can somebody please help me in identifying the good automation framework/tool/anything? The main intention is we want to automate the infrastructure validation related cases (for e.g. create/update/delete cases for instances, project, network, etc...)

It would be good if you can help in identifying it.

Please note: I have gone through cloudmonkey. But i haven't found much help on it. May be i need to search a bit more.. I am also going through the marvin and planning to setup it. If apart from these two, if anyone has different view please suggest.

Also, if somebody has any pointers on cloudmonkey and marvin or any more info on this (like, if it would suffice the infrastructure validation related cases i mentioned above) any pros/cons would really be helpful for me...

Appreciate any help on this and looking forward for the response on this!!!

Thanks and Regards
-- Umesh Kute