Re: CPU Sockets and Cores
Look at: https://issues.apache.org/jira/browse/CLOUDSTACK-904 2014-10-25 5:49 GMT+02:00 Michael Phillips mphilli7...@hotmail.com: All, The following pertains to cloudstack + vmware. Currently when using a multi CPU compute service offering, cloudstack creates the CPUs on the vm using all sockets. This can be an issue for operating systems that have physical CPU sockets limits. It can also be a license issue for certain software as well. An easy work around would be to let the admin define the socket to core ratio in the compute service offering. Are there in plans to implement such a feature in any upcoming cloudstack releases? -- Regards, Tomasz Zięba Twitter: @TZieba LinkedIn: pl.linkedin.com/pub/tomasz-zięba-ph-d/3b/7a8/ab6/ http://pl.linkedin.com/pub/tomasz-zi%C4%99ba-ph-d/3b/7a8/ab6/
Re: vm.password.length issue in 4.4.1-SNAPSHOT
Amogh,
I know. In reality it will be used by people until the end of time, you know
how it is.
It's not costing us anything to default to better values rather than just wash
our hands of it.
My 2 pence
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
From: Amogh Vasekar amogh.vase...@citrix.com
To: dev@cloudstack.apache.org
Cc: laszlo hornyak laszlo.horn...@gmail.com
Sent: Saturday, 25 October, 2014 01:41:47
Subject: Re: vm.password.length issue in 4.4.1-SNAPSHOT
Do note that the password generated here is considered temporary, as
previously pointed out by Chiradeep in another thread.
Thanks
Amogh
On 10/24/14 5:31 PM, Nux! n...@li.nux.ro wrote:
Imho, considering the password is not very secure (it's missing symbols),
we should increase the length.
For my personal stuff I default to 15 chars.
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
From: Amogh Vasekar amogh.vase...@citrix.com
To: dev@cloudstack.apache.org
Cc: laszlo hornyak laszlo.horn...@gmail.com
Sent: Saturday, 25 October, 2014 00:37:07
Subject: Re: vm.password.length issue in 4.4.1-SNAPSHOT
Hi Laszlo,
Any comments on the below? I agree adding 3 characters is a bug and
willing to fix it.
In addition, Ian, I believe we should set a minimum allowed value for
the
config value vm.password.length. Any objections to setting the minimum
to
8, the previous default?
Thanks
Amogh
On 10/13/14 5:34 PM, Ian Duffy i...@ianduffy.ie wrote:
The only other usage of it is within
server/src/com/cloud/server/ConfigurationServerImpl.java
Its used for creating a Secondary storage vm copy password.
I'm seeing absolutely no reason why we have 3 values going in no matter
what, I'm willing to say its a bug. I'm curious to why the tests are
written to deal with it though
On 14 October 2014 00:26, Nux! n...@li.nux.ro wrote:
Well, it's a bit messy, but still better than the old password length.
Ideally this should get clarified/fixed, but for now I am happy with
my
long+3 password! :)
Cheers,
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
From: Ian Duffy i...@ianduffy.ie
To: CloudStack Dev dev@cloudstack.apache.org
Cc: laszlo hornyak laszlo.horn...@gmail.com
Sent: Monday, 13 October, 2014 19:54:53
Subject: Re: vm.password.length issue in 4.4.1-SNAPSHOT
Hey Nux,
So I passed this work off to a util class that was already present
in
the
code base PasswordGenerator
@Override
public String generateRandomPassword() {
Integer passwordLength =
Integer.parseInt(_configDao.getValue(vm.password.length));
return
PasswordGenerator.generateRandomPassword(passwordLength);
}
Not a clue why but the generateRandomPassword method creates a
random
3-character string first then loops through to generate n random
characters.
public static String generateRandomPassword(int num) {
Random r = new SecureRandom();
StringBuilder password = new StringBuilder();
// Generate random 3-character string with a lowercase
character,
// uppercase character, and a digit
password.append(generateLowercaseChar(r)).append(generateUppercaseChar(
r)
).append(generateDigit(r));
// Generate a random n-character string with only lowercase
// characters
for (int i = 0; i num; i++) {
password.append(generateLowercaseChar(r));
}
return password.toString();
}
The unit tests seem to accommodate for this aswell:
// actual length is requested length + 3
Assert.assertTrue(PasswordGenerator.generateRandomPassword(0).length()
==
3);
Assert.assertTrue(PasswordGenerator.generateRandomPassword(1).length()
==
4);
I'm guessing there's some reasoning for this CCing Laszlo who
according
to git log did some work on this class.
Thanks,
Ian
On 13 October 2014 19:39, Nux! n...@li.nux.ro wrote:
Hello,
First of all THANKS! to whoever made this feature happen (Ian I
guess).
Now we can set more secure passwords generated for our instances.
Second, the feature works, but with a small glitch, the number
seems
to
be
affected by some sort of offset. I.e. if I set the password to be
15
chars
in length then the generated password will actually be 18 chars.
In order to get a 15 chars long passwd I had to set
vm.password.length
to
12. Bug or feature? :)
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
pfSense CloudStack
Hello, Is it possible to install pfSense to a local install of Cloudstack. I have it installed on Xen right now (pfsense). I am looking for others who MAY have done this. Looking forward to responses, Mo
Re: pfSense CloudStack
Hello, Recent FreeBSD has proper support for Xen HVM and KVM VirtIO therefore it runs nicely, not sure how old PfSense is though. You run it on Xen or Xenserver now? Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: mo+cloudstack mo+cloudst...@daoenix.com To: dev dev@cloudstack.apache.org Sent: Saturday, 25 October, 2014 14:34:02 Subject: pfSense CloudStack Hello, Is it possible to install pfSense to a local install of Cloudstack. I have it installed on Xen right now (pfsense). I am looking for others who MAY have done this. Looking forward to responses, Mo
Re: pfSense CloudStack
I do, I had to get away from the verizon router; so I installed Xen Server on an old computer I had and tossed on a few VMs, including pfSense. So I am just trying to figure out how to populate VMs with CLoudstack, whilst using pfSense. I would assume you would need to be an advanced mode, as basic wouldn’t support it? I’ve also considered doing a regular KVM install and doing everything command line. -- Mo Sent with Airmail On October 25, 2014 at 9:42:00 AM, Nux! (n...@li.nux.ro) wrote: Hello, Recent FreeBSD has proper support for Xen HVM and KVM VirtIO therefore it runs nicely, not sure how old PfSense is though. You run it on Xen or Xenserver now? Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: mo+cloudstack mo+cloudst...@daoenix.com To: dev dev@cloudstack.apache.org Sent: Saturday, 25 October, 2014 14:34:02 Subject: pfSense CloudStack Hello, Is it possible to install pfSense to a local install of Cloudstack. I have it installed on Xen right now (pfsense). I am looking for others who MAY have done this. Looking forward to responses, Mo
Re: pfSense CloudStack
If you want to use PFSense as a Cloudstack virtual router for your instances it will not work (though awesome idea). It might be better to just use a standalone hypervisor. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Mo m...@daoenix.com To: dev@cloudstack.apache.org, Nux! n...@li.nux.ro Sent: Saturday, 25 October, 2014 15:01:12 Subject: Re: pfSense CloudStack I do, I had to get away from the verizon router; so I installed Xen Server on an old computer I had and tossed on a few VMs, including pfSense. So I am just trying to figure out how to populate VMs with CLoudstack, whilst using pfSense. I would assume you would need to be an advanced mode, as basic wouldn’t support it? I’ve also considered doing a regular KVM install and doing everything command line. -- Mo Sent with Airmail On October 25, 2014 at 9:42:00 AM, Nux! (n...@li.nux.ro) wrote: Hello, Recent FreeBSD has proper support for Xen HVM and KVM VirtIO therefore it runs nicely, not sure how old PfSense is though. You run it on Xen or Xenserver now? Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: mo+cloudstack mo+cloudst...@daoenix.com To: dev dev@cloudstack.apache.org Sent: Saturday, 25 October, 2014 14:34:02 Subject: pfSense CloudStack Hello, Is it possible to install pfSense to a local install of Cloudstack. I have it installed on Xen right now (pfsense). I am looking for others who MAY have done this. Looking forward to responses, Mo
Re: pfSense CloudStack
I use it this way right now: Verizon Fios Xen server pfSense, which provides internet into my home. What I would like to do is. Verizon Fios CloudStack pfSense provide internet to the home. I understand the Virtual Router built into CS, would still do it’s thing; but I still wonder if a VM of pfsense would be possible and do what I am doing with it right now. Perhaps, like you said a stand alone might be best. -- Mo Sent with Airmail On October 25, 2014 at 10:03:40 AM, Nux! (n...@li.nux.ro) wrote: If you want to use PFSense as a Cloudstack virtual router for your instances it will not work (though awesome idea). It might be better to just use a standalone hypervisor. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Mo m...@daoenix.com To: dev@cloudstack.apache.org, Nux! n...@li.nux.ro Sent: Saturday, 25 October, 2014 15:01:12 Subject: Re: pfSense CloudStack I do, I had to get away from the verizon router; so I installed Xen Server on an old computer I had and tossed on a few VMs, including pfSense. So I am just trying to figure out how to populate VMs with CLoudstack, whilst using pfSense. I would assume you would need to be an advanced mode, as basic wouldn’t support it? I’ve also considered doing a regular KVM install and doing everything command line. -- Mo Sent with Airmail On October 25, 2014 at 9:42:00 AM, Nux! (n...@li.nux.ro) wrote: Hello, Recent FreeBSD has proper support for Xen HVM and KVM VirtIO therefore it runs nicely, not sure how old PfSense is though. You run it on Xen or Xenserver now? Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: mo+cloudstack mo+cloudst...@daoenix.com To: dev dev@cloudstack.apache.org Sent: Saturday, 25 October, 2014 14:34:02 Subject: pfSense CloudStack Hello, Is it possible to install pfSense to a local install of Cloudstack. I have it installed on Xen right now (pfsense). I am looking for others who MAY have done this. Looking forward to responses, Mo
Review Request 27191: CLOUDSTACK-7786 : Fixed the script 'test_haproxy.py' to be run only on hardware
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27191/ --- Review request for cloudstack, sangeetha hariharan and Santhosh Edukulla. Bugs: CLOUDSTACK-7786 https://issues.apache.org/jira/browse/CLOUDSTACK-7786 Repository: cloudstack-git Description --- Test Cases are trying to validate SSH access and failing. These Test Cases are not meant to be run on SImulator due to their validation requirements. Hence they cannot be run with Simulator Diffs - test/integration/component/test_haproxy.py 2778902 Diff: https://reviews.apache.org/r/27191/diff/ Testing --- Changed the tags on Tests. Testing not done Thanks, Chandan Purushothama
Review Request 27192: CLOUDSTACK-7787: Fixed the script 'test_lb_secondary_ip.py' to be run only on hardware
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27192/ --- Review request for cloudstack, sangeetha hariharan and Santhosh Edukulla. Bugs: CLOUDSTACK-7787 https://issues.apache.org/jira/browse/CLOUDSTACK-7787 Repository: cloudstack-git Description --- Test Cases are trying to validate SSH access and failing. These Test Cases are not meant to be run on SImulator due to their validation requirements. Hence they cannot be run with Simulator Diffs - test/integration/component/test_lb_secondary_ip.py 23ff1ee Diff: https://reviews.apache.org/r/27192/diff/ Testing --- Changed the tags on Tests. Testing not done Thanks, Chandan Purushothama
Review Request 27193: CLOUDSTACK-7788: Fixed the script 'test_dynamic_compute_offering.py' to be run only on hardware
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27193/ --- Review request for cloudstack, sangeetha hariharan and Santhosh Edukulla. Bugs: CLOUDSTACK-7788 https://issues.apache.org/jira/browse/CLOUDSTACK-7788 Repository: cloudstack-git Description --- Test Cases are trying to perform operations that can only be done on hardware and supported hypervisors. These Test Cases are not meant to be run on SImulator due to their validation requirements. Hence they cannot be run with Simulator Diffs - test/integration/component/test_dynamic_compute_offering.py a3e2d56 Diff: https://reviews.apache.org/r/27193/diff/ Testing --- Changed the tags on Tests. Testing not done Thanks, Chandan Purushothama
Review Request 27195: CLOUDSTACK-7788: Fixed the script test_escalations_instances.py - Regular Users should not use expunge parameter for destroying a VM
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27195/ --- Review request for cloudstack and sangeetha hariharan. Bugs: CLOUDSTACK-7788 https://issues.apache.org/jira/browse/CLOUDSTACK-7788 Repository: cloudstack-git Description --- Regular Users do not have permissions to expunge a VM with expunge parameter. It is only available for admin to use. Correct the test script accordingly Diffs - test/integration/component/test_escalations_instances.py 1aaa688 Diff: https://reviews.apache.org/r/27195/diff/ Testing --- @Desc: Test List Instances pagination ... === TestName: test_01_list_instances_pagination | Status : SUCCESS === ok @Desc: Test List Running VM's ... === TestName: test_02_list_Running_vm | Status : SUCCESS === ok @Desc: Test List Stopped VM's ... === TestName: test_03_list_Stopped_vm | Status : SUCCESS === ok @Desc: Test List Destroyed VM's ... === TestName: test_04_list_Destroyed_vm | Status : SUCCESS === ok @Desc: Test List VM by Id ... === TestName: test_05_list_vm_by_id | Status : SUCCESS === ok @Desc: Test List VM's by Name ... === TestName: test_06_list_vm_by_name | Status : SUCCESS === ok @Desc: Test List VM's by Name and State ... === TestName: test_07_list_vm_by_name_state | Status : SUCCESS === ok @Desc: Test List VM by Zone. ... === TestName: test_08_list_vm_by_zone | Status : SUCCESS === ok @Desc: Test List VM by Zone. ... === TestName: test_09_list_vm_by_zone_name | Status : SUCCESS === ok @Desc: Test List VM by Zone. ... === TestName: test_10_list_vm_by_zone_name_state | Status : SUCCESS === ok Thanks, Chandan Purushothama
Re: Review Request 27195: CLOUDSTACK-7788: Fixed the script test_escalations_instances.py - Regular Users should not use expunge parameter for destroying a VM
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27195/#review58510 --- Can we have the sleep interval calculated from the expunge global config parameters? - sangeetha hariharan On Oct. 25, 2014, 2:59 p.m., Chandan Purushothama wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27195/ --- (Updated Oct. 25, 2014, 2:59 p.m.) Review request for cloudstack and sangeetha hariharan. Bugs: CLOUDSTACK-7788 https://issues.apache.org/jira/browse/CLOUDSTACK-7788 Repository: cloudstack-git Description --- Regular Users do not have permissions to expunge a VM with expunge parameter. It is only available for admin to use. Correct the test script accordingly Diffs - test/integration/component/test_escalations_instances.py 1aaa688 Diff: https://reviews.apache.org/r/27195/diff/ Testing --- @Desc: Test List Instances pagination ... === TestName: test_01_list_instances_pagination | Status : SUCCESS === ok @Desc: Test List Running VM's ... === TestName: test_02_list_Running_vm | Status : SUCCESS === ok @Desc: Test List Stopped VM's ... === TestName: test_03_list_Stopped_vm | Status : SUCCESS === ok @Desc: Test List Destroyed VM's ... === TestName: test_04_list_Destroyed_vm | Status : SUCCESS === ok @Desc: Test List VM by Id ... === TestName: test_05_list_vm_by_id | Status : SUCCESS === ok @Desc: Test List VM's by Name ... === TestName: test_06_list_vm_by_name | Status : SUCCESS === ok @Desc: Test List VM's by Name and State ... === TestName: test_07_list_vm_by_name_state | Status : SUCCESS === ok @Desc: Test List VM by Zone. ... === TestName: test_08_list_vm_by_zone | Status : SUCCESS === ok @Desc: Test List VM by Zone. ... === TestName: test_09_list_vm_by_zone_name | Status : SUCCESS === ok @Desc: Test List VM by Zone. ... === TestName: test_10_list_vm_by_zone_name_state | Status : SUCCESS === ok Thanks, Chandan Purushothama
Re: Review Request 27193: CLOUDSTACK-7788: Fixed the script 'test_dynamic_compute_offering.py' to be run only on hardware
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27193/#review58512 --- Ship it! Ship It! - sangeetha hariharan On Oct. 25, 2014, 2:38 p.m., Chandan Purushothama wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27193/ --- (Updated Oct. 25, 2014, 2:38 p.m.) Review request for cloudstack, sangeetha hariharan and Santhosh Edukulla. Bugs: CLOUDSTACK-7788 https://issues.apache.org/jira/browse/CLOUDSTACK-7788 Repository: cloudstack-git Description --- Test Cases are trying to perform operations that can only be done on hardware and supported hypervisors. These Test Cases are not meant to be run on SImulator due to their validation requirements. Hence they cannot be run with Simulator Diffs - test/integration/component/test_dynamic_compute_offering.py a3e2d56 Diff: https://reviews.apache.org/r/27193/diff/ Testing --- Changed the tags on Tests. Testing not done Thanks, Chandan Purushothama
Re: Review Request 27193: CLOUDSTACK-7788: Fixed the script 'test_dynamic_compute_offering.py' to be run only on hardware
On Oct. 25, 2014, 4:16 p.m., sangeetha hariharan wrote: Ship It! In this case, simulator does not support for scale operation which is the reason for the failures. Please log a ticket to have simulator support for this operation. - sangeetha --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27193/#review58512 --- On Oct. 25, 2014, 2:38 p.m., Chandan Purushothama wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27193/ --- (Updated Oct. 25, 2014, 2:38 p.m.) Review request for cloudstack, sangeetha hariharan and Santhosh Edukulla. Bugs: CLOUDSTACK-7788 https://issues.apache.org/jira/browse/CLOUDSTACK-7788 Repository: cloudstack-git Description --- Test Cases are trying to perform operations that can only be done on hardware and supported hypervisors. These Test Cases are not meant to be run on SImulator due to their validation requirements. Hence they cannot be run with Simulator Diffs - test/integration/component/test_dynamic_compute_offering.py a3e2d56 Diff: https://reviews.apache.org/r/27193/diff/ Testing --- Changed the tags on Tests. Testing not done Thanks, Chandan Purushothama
Re: Review Request 27193: CLOUDSTACK-7788: Fixed the script 'test_dynamic_compute_offering.py' to be run only on hardware
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27193/ --- (Updated Oct. 25, 2014, 4:21 p.m.) Review request for cloudstack, sangeetha hariharan and Santhosh Edukulla. Bugs: CLOUDSTACK-7788 https://issues.apache.org/jira/browse/CLOUDSTACK-7788 Repository: cloudstack-git Description (updated) --- Test Cases are trying to perform operations that can only be done on hardware and supported hypervisors. These Test Cases are not meant to be run on SImulator. Hence they cannot be run with Simulator Diffs - test/integration/component/test_dynamic_compute_offering.py a3e2d56 Diff: https://reviews.apache.org/r/27193/diff/ Testing --- Changed the tags on Tests. Testing not done Thanks, Chandan Purushothama
Re: Review Request 27192: CLOUDSTACK-7787: Fixed the script 'test_lb_secondary_ip.py' to be run only on hardware
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27192/#review58515 --- Ship it! This patch looks good. All test cases requiring to ssh to VMs for validation has been marked for not being picked up by simulator runs. - sangeetha hariharan On Oct. 25, 2014, 2:23 p.m., Chandan Purushothama wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27192/ --- (Updated Oct. 25, 2014, 2:23 p.m.) Review request for cloudstack, sangeetha hariharan and Santhosh Edukulla. Bugs: CLOUDSTACK-7787 https://issues.apache.org/jira/browse/CLOUDSTACK-7787 Repository: cloudstack-git Description --- Test Cases are trying to validate SSH access and failing. These Test Cases are not meant to be run on SImulator due to their validation requirements. Hence they cannot be run with Simulator Diffs - test/integration/component/test_lb_secondary_ip.py 23ff1ee Diff: https://reviews.apache.org/r/27192/diff/ Testing --- Changed the tags on Tests. Testing not done Thanks, Chandan Purushothama
Re: Review Request 27191: CLOUDSTACK-7786 : Fixed the script 'test_haproxy.py' to be run only on hardware
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27191/#review58516 --- Ship it! Ship It! - sangeetha hariharan On Oct. 25, 2014, 2:12 p.m., Chandan Purushothama wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27191/ --- (Updated Oct. 25, 2014, 2:12 p.m.) Review request for cloudstack, sangeetha hariharan and Santhosh Edukulla. Bugs: CLOUDSTACK-7786 https://issues.apache.org/jira/browse/CLOUDSTACK-7786 Repository: cloudstack-git Description --- Test Cases are trying to validate SSH access and failing. These Test Cases are not meant to be run on SImulator due to their validation requirements. Hence they cannot be run with Simulator Diffs - test/integration/component/test_haproxy.py 2778902 Diff: https://reviews.apache.org/r/27191/diff/ Testing --- Changed the tags on Tests. Testing not done Thanks, Chandan Purushothama
Re: Review Request 27191: CLOUDSTACK-7786 : Fixed the script 'test_haproxy.py' to be run only on hardware
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27191/#review58517 --- Ship it! Ship It! - sangeetha hariharan On Oct. 25, 2014, 2:12 p.m., Chandan Purushothama wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27191/ --- (Updated Oct. 25, 2014, 2:12 p.m.) Review request for cloudstack, sangeetha hariharan and Santhosh Edukulla. Bugs: CLOUDSTACK-7786 https://issues.apache.org/jira/browse/CLOUDSTACK-7786 Repository: cloudstack-git Description --- Test Cases are trying to validate SSH access and failing. These Test Cases are not meant to be run on SImulator due to their validation requirements. Hence they cannot be run with Simulator Diffs - test/integration/component/test_haproxy.py 2778902 Diff: https://reviews.apache.org/r/27191/diff/ Testing --- Changed the tags on Tests. Testing not done Thanks, Chandan Purushothama
Re: Review Request 27195: CLOUDSTACK-7788: Fixed the script test_escalations_instances.py - Regular Users should not use expunge parameter for destroying a VM
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27195/ --- (Updated Oct. 25, 2014, 6:50 p.m.) Review request for cloudstack and sangeetha hariharan. Changes --- Incorporated the changes requested in the review comments Bugs: CLOUDSTACK-7788 https://issues.apache.org/jira/browse/CLOUDSTACK-7788 Repository: cloudstack-git Description --- Regular Users do not have permissions to expunge a VM with expunge parameter. It is only available for admin to use. Correct the test script accordingly Diffs (updated) - test/integration/component/test_escalations_instances.py 1aaa688 Diff: https://reviews.apache.org/r/27195/diff/ Testing --- @Desc: Test List Instances pagination ... === TestName: test_01_list_instances_pagination | Status : SUCCESS === ok @Desc: Test List Running VM's ... === TestName: test_02_list_Running_vm | Status : SUCCESS === ok @Desc: Test List Stopped VM's ... === TestName: test_03_list_Stopped_vm | Status : SUCCESS === ok @Desc: Test List Destroyed VM's ... === TestName: test_04_list_Destroyed_vm | Status : SUCCESS === ok @Desc: Test List VM by Id ... === TestName: test_05_list_vm_by_id | Status : SUCCESS === ok @Desc: Test List VM's by Name ... === TestName: test_06_list_vm_by_name | Status : SUCCESS === ok @Desc: Test List VM's by Name and State ... === TestName: test_07_list_vm_by_name_state | Status : SUCCESS === ok @Desc: Test List VM by Zone. ... === TestName: test_08_list_vm_by_zone | Status : SUCCESS === ok @Desc: Test List VM by Zone. ... === TestName: test_09_list_vm_by_zone_name | Status : SUCCESS === ok @Desc: Test List VM by Zone. ... === TestName: test_10_list_vm_by_zone_name_state | Status : SUCCESS === ok Thanks, Chandan Purushothama
Re: Review Request 27195: CLOUDSTACK-7788: Fixed the script test_escalations_instances.py - Regular Users should not use expunge parameter for destroying a VM
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27195/#review58525 --- Ship it! Ship It! - sangeetha hariharan On Oct. 25, 2014, 6:50 p.m., Chandan Purushothama wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27195/ --- (Updated Oct. 25, 2014, 6:50 p.m.) Review request for cloudstack and sangeetha hariharan. Bugs: CLOUDSTACK-7788 https://issues.apache.org/jira/browse/CLOUDSTACK-7788 Repository: cloudstack-git Description --- Regular Users do not have permissions to expunge a VM with expunge parameter. It is only available for admin to use. Correct the test script accordingly Diffs - test/integration/component/test_escalations_instances.py 1aaa688 Diff: https://reviews.apache.org/r/27195/diff/ Testing --- @Desc: Test List Instances pagination ... === TestName: test_01_list_instances_pagination | Status : SUCCESS === ok @Desc: Test List Running VM's ... === TestName: test_02_list_Running_vm | Status : SUCCESS === ok @Desc: Test List Stopped VM's ... === TestName: test_03_list_Stopped_vm | Status : SUCCESS === ok @Desc: Test List Destroyed VM's ... === TestName: test_04_list_Destroyed_vm | Status : SUCCESS === ok @Desc: Test List VM by Id ... === TestName: test_05_list_vm_by_id | Status : SUCCESS === ok @Desc: Test List VM's by Name ... === TestName: test_06_list_vm_by_name | Status : SUCCESS === ok @Desc: Test List VM's by Name and State ... === TestName: test_07_list_vm_by_name_state | Status : SUCCESS === ok @Desc: Test List VM by Zone. ... === TestName: test_08_list_vm_by_zone | Status : SUCCESS === ok @Desc: Test List VM by Zone. ... === TestName: test_09_list_vm_by_zone_name | Status : SUCCESS === ok @Desc: Test List VM by Zone. ... === TestName: test_10_list_vm_by_zone_name_state | Status : SUCCESS === ok Thanks, Chandan Purushothama
