RE: Spannish translation mangled

[Nuno Tavares]

Hi Milamber,

I'm a bit lost here. I'm looking at the ES translation, I see that the double 
encoding is fixed, but not some of the other translations I did (before 
uploading).

Also, we have people working on transifex... what happens when I upload my 
file? Are the translations preserved, or will they be overritten? How soon are 
the changes from them being committed to the code (so when I look at the code I 
have the most up-to-date version, since I'm going to upload it)?

-NT


Kind regards,

Nuno Tavares
Senior DevOps Infra Specialist
LeaseWeb Technologies B.V.

T: +31 20 316 0235
M:
E: n.tava...@tech.leaseweb.com
W: http://www.leaseweb.com

Luttenbergweg 8, 1101 EC Amsterdam, Netherlands



From: Milamber [milam...@apache.org]
Sent: Wednesday, February 10, 2016 11:30 PM
To: dev@cloudstack.apache.org
Subject: Re: Spannish translation mangled

Hello,

On transifex website, you can click on "Join Team" button to start to
help in this project.
https://www.transifex.com/ke4qqq/CloudStack_UI/

Milamber

On 10/02/2016 21:13, Marco Sinhoreli wrote:
> I can help with Spanish and Portuguese (Portugal) translation too.
> Somebody can add me in both please?
>
> Thank you!
>
>
>
> *Marco Sinhoreli*
>
> Consultant Manager
>
> marco.sinhor...@shapeblue.com 
>
> mobile: +55 21 98276 3636
>
> Praia de Botafogo 501, bloco 1 - sala 101 – Botafogo
>
> Rio de Janeiro, RJ - Brazil - CEP 22250-040
>
> office: + 55 21 2586 6390 | fax: +55 21 2586 6002
>
> http://www.shapeblue.com/ | twitter: @shapeblue
>
>
> De: Laszlo Hornyak
> Responder para: "dev@cloudstack.apache.org
> "
> Data: quarta-feira, 10 de fevereiro de 2016 18:25
> Para: "dev@cloudstack.apache.org "
> Assunto: Re: Spannish translation mangled
>
> Hi,
>
> Might be a related issue, but looks like now I am translating either
> from Spanish or from Portuguese, but anyway it is a nice challenge...
> Can you give me back the original English?
>
> Inline image 1
>
>
> Thank you,
> Laszlo
>
> On Wed, Feb 10, 2016 at 2:45 PM, Marco Sinhoreli
> >
> wrote:
>
> Hi folks,
>
> Any issue in transifex? It’s showing 5% complete. Before Brazilian
> Portuguese was 100%. Many others languages are only 5% complete.
>
> Best regards,
>
> Marco Sinhoreli
> Consultant Manager
> marco.sinhor...@shapeblue.com 
> mobile: +55 21 98276 3636 
>
> Praia de Botafogo 501, bloco 1 - sala 101 – Botafogo
> Rio de Janeiro, RJ - Brazil - CEP 22250-040
> office: + 55 21 2586 6390  | fax:
> +55 21 2586 6002 
> http://www.shapeblue.com/ | twitter: @shapeblue
>
>
>
>
>
>
>
>
>
> Em [DATE], "[NAME]" <[ADDRESS]> escreveu:
>
> >Hi Milamber,
> >
> >Thanks, and sorry for the extra-trouble...
> >I did the push with: tx push -s -t
> >.. after linking the source, resource was 48xmessagesproperties.
> >
> >I'm not sure if I did something wrong.. didn't check that branch
> before, but it's showing only 5% of strings in "translated state",
> while the other branches are ~60%...
> >Shouldn't Transifex catchup on the already translated strings?
> >
> >I also updated the PR, btw.
> >
> >-NT
> >
> >Kind regards,
> >
> >Nuno Tavares
> >Senior DevOps Infra Specialist
> >LeaseWeb Technologies B.V.
> >
> >T: +31 20 316 0235 
> >M:
> >E: n.tava...@tech.leaseweb.com 
> >W: http://www.leaseweb.com
> >
> >Luttenbergweg 8, 1101 EC Amsterdam, Netherlands
> >
> >
> >
> >From: Milamber [milam...@apache.org ]
> >Sent: Wednesday, February 10, 2016 8:14 AM
> >To: dev@cloudstack.apache.org 
> >Subject: Re: Spannish translation mangled
> >
> >Nuno, you are now Mainteners in the Web UI project. You can
> upload the
> >resources files to fix this charset issue.
> >
> >On 10/02/2016 06:58, Nuno Tavares wrote:
> >> Hi Milamber,
> >>
> >> Not sure where I find my ID... but I'm this guys over here:
> >> https://www.transifex.com/user/profile/ntavares/
> 
> >> :)
> >>
> >> -NT
> >>
> >> Kind regards,
> >>
> >> Nuno Tavares
> >> Senior DevOps Infra Specialist
> >> LeaseWeb Technologies B.V.
> >>
> >> T: +31 20 316 0235 
> >> M:
> >> E: n.tava...@tech.leaseweb.com 
> >> W: http://www.leaseweb.com
> >>
> >> Luttenbergweg 8, 1101 

[GitHub] cloudstack pull request: CLOUDSTACK-8717: Failed to start instance...

[pritisarap12]

Github user pritisarap12 commented on the pull request:

https://github.com/apache/cloudstack/pull/667#issuecomment-182778439
  
Testcase results:

Test Restore VM on VMWare ... === TestName: test_01_recover_VM | Status : 
SUCCESS ===
ok

--
Ran 1 test in 414.293s

OK



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

RE: Important Pending Items

[Raja Pullela]

Hi Sebastien,

On item (3) - the BVTs have been running consistently (with same passrates) and 
haven't had the time to automate the process of reporting to an external site.  
  
Bharat and Sanjeev are working on CI - running BVTs/Regression, working on 
getting it run automatically and consistently.  
Hope to see it ready soon.

Best,
Raja
-Original Message-
From: Sebastien Goasguen [mailto:run...@gmail.com] 
Sent: Wednesday, February 10, 2016 2:29 PM
To: dev@cloudstack.apache.org
Subject: Important Pending Items

Morning folks,

We have several crucial pending items, that we need to resolve before moving on:

1- We need an RM for master ( just saw some commits there that should be 
reverted or merged properly in other branches).

2- We need to automate writing release notes, pushing/tagging new docs when 
release come out and announcing releases on website. Currently neither 4.7 nor 
4.8 have been announced.

3- CI is still almost inexistent

-Sebastien

[GitHub] cloudstack pull request: CLOUDSTACK-8717: Failed to start instance...

[nitt10prashant]

Github user nitt10prashant commented on the pull request:

https://github.com/apache/cloudstack/pull/667#issuecomment-182784773
  
LGTM ..based on code review and result .


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Important Pending Items

[Bharat Kumar]

Hi Paul,

The goals and functionality of the CI on which we are working are the same 
(please review the 
FS
 ), The difference being the method of implementation. We are not using nested 
virtualisation to create test environments. The work on CI began long back but 
unfortunately due to other priorities we could not work on a continuous basis 
and bring it to completion.

I agree that we should come to a consensus on what the community wants from the 
CI. IMHO the basic and immediate requirement would be to have a stable system 
to test the PRs and post results. Once we have this, we can
talk about providing test setups to the community and next steps. I think the 
availability of hardware has been a big hurdle (even if we use virtualisation).

Instead of working independently on the same thing let us work on this 
together. I will share what we have currently, we can use it, or parts of it 
(some of it is there at https://github.com/bvbharatk/cloudstack-automation, but 
it is not organised as in cannot be run out of the box). While virtualisation 
is good from the ease of orchestration and resource utilisation point of view, 
it has other problems like compatibility/dependencies issues. Also it might tie 
the CI to a particular Hypervisor like ESXi as you have pointed out.

So let us discuss on how to proceed further, and get things rolling.

Thanks,
Bharat.


On 11-Feb-2016, at 9:44 PM, Paul Angus 
> wrote:

Hi Bharat,

Early last week I opened a discussion thread around the aims of Trillian which 
we had begun working on as a CI/CD platform for the community hardware (as well 
as individual use). Please could you elaborate on where there is/isn't 
cross-over? In terms of functionality and goals rather than method. It would be 
great to get community consensus around what we want from our centralised CI/CD.


Project: Trillian
We have been working on PoC of a CI environment design which will:
* Provide fast build or rebuild of environments for testing.
* Enable multiple independent concurrent builds
* Be available on-demand through automation or individual request.
* Be capable of fully utilising all available hardware
* Flexible enough to be used to build super-realistic development environments.
We intend to contribute and maintain our work within the Apache repos. However, 
we are currently building the POC, figuring out the requirements (and quirks) 
of the individual pieces, before pushing something concrete for to the 
community to review.

We envision that Trillian would cater for a number of use cases:
1. CloudStack community integration testing of master against multiple 
deployment scenarios (using ASF infra)
2. CloudStack community integration testing of PRs against multiple deployment 
scenarios (using ASF infra)
3. Organisations/individuals running the full suites of tests available in 
Marvin against any physical environment they have.
4. Organisations/individuals deploying and running the full suites of tests 
available in Marvin against virtualised infrastructures which can be deployed 
by Marvin.
As we intend Trillian to test multiple environments concurrently, we use nested 
virtualization on ESXi hosts (our testing has shown that this is the only 
hypervisor which can support the nested virtualisation of all other hypervisors 
with reasonable performance). We use Ansible to deploy and configure all 
aspects of the build as this will greatly lower the barrier to entry for 
independent testers.
We use CloudStack to provision the management server and virtualised (nested) 
hosts on the physical hosts. We are creating Ansible playbooks and roles which 
can:
1. Create guest instances using Rene's Ansible 2.0 CloudStack modules - a 
Marvin VM, a Mgmt Server (CentOS or Ubuntu), any number of compute hosts (KVM, 
vSphere or XenServer. Hyper-V later)
2. Configure hosts (inc. installing the relevant CloudStack agent where 
required)
3. Install required ACS packages on management server
4. Configure a zone (including adding the compute hosts) via Marvin.
5. Run the required Marvin tests.
6. Return the results
We may need to propose enhancements to Marvin in order to sync the 
configuration of hosts with the configuration used by Marvin.

Using virtualised test environments, we can have multiple test scenarios 
running concurrently. To do this we have found that it is necessary to create 
pools or ranges of VLANs and IP addresses and allocate them to environments. So 
for any given physical environment which will be used for testing in, we take 
the total range(s) of IPs and VLANs available and carve them into 
non-overlapping chunks suitable for concurrent use as mgmt, public and guest 
networks. These are stored in a MariaDB database. When a range is being used in 
a testing environment, that range is marked as 

New Ideas on Cloudstack

[Keerthiraja SJ]

Hi All,

I would like to bring up some ideas about to integrate the
http://www.projectcalico.org into cloudstack to next step ahead.

How really will this help. I need all your feedback on this.

Thanks,
Keerthi

[GitHub] cloudstack pull request: CLOUDSTACK-6928: fix issue disk I/O throt...

[rodrigo93]

Github user rodrigo93 commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/1410#discussion_r52655615
  
--- Diff: 
engine/orchestration/src/org/apache/cloudstack/engine/orchestration/VolumeOrchestrator.java
 ---
@@ -1054,9 +1075,28 @@ public void 
prepareForMigration(VirtualMachineProfile vm, DeployDestination dest
 }
 
 for (VolumeVO vol : vols) {
-DataTO volTO = volFactory.getVolume(vol.getId()).getTO();
-DiskTO disk = new DiskTO(volTO, vol.getDeviceId(), 
vol.getPath(), vol.getVolumeType());
 VolumeInfo volumeInfo = volFactory.getVolume(vol.getId());
+DataTO volTO = volumeInfo.getTO();
--- End diff --

Hi @ustcweizhou,
Isn't it better to create a single method for lines from 1079 to 1099 seem 
that you use it more than once?
I can see that you replicated these lines from 1381 to 1401 and I can see 
them in the following file 
server/src/com/cloud/storage/VolumeApiServiceImpl.java as well.
Maybe you could transform those lines in a method in a common superclass if 
possible. This would save some replicated code.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: CLOUDSTACK-8717: Failed to start instance...

[remibergsma]

Github user remibergsma commented on the pull request:

https://github.com/apache/cloudstack/pull/667#issuecomment-183022736
  
Don't merge stuff without responding to the comments. Look at your commits, 
two with the same title? How does that help? I asked to squash them on Aug 14 
and now you just merge it... weird. I will revert it.



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Important Pending Items

[Bharat Kumar]

Hi Sebastien,

As Raja said, we are actively working on it and we will share the code on 
github soon.

Thanks,
Bharat.


> On 11-Feb-2016, at 2:41 PM, Raja Pullela  wrote:
> 
> Hi Sebastien,
> 
> On item (3) - the BVTs have been running consistently (with same passrates) 
> and haven't had the time to automate the process of reporting to an external 
> site.
> Bharat and Sanjeev are working on CI - running BVTs/Regression, working on 
> getting it run automatically and consistently.  
> Hope to see it ready soon.
> 
> Best,
> Raja
> -Original Message-
> From: Sebastien Goasguen [mailto:run...@gmail.com] 
> Sent: Wednesday, February 10, 2016 2:29 PM
> To: dev@cloudstack.apache.org
> Subject: Important Pending Items
> 
> Morning folks,
> 
> We have several crucial pending items, that we need to resolve before moving 
> on:
> 
> 1- We need an RM for master ( just saw some commits there that should be 
> reverted or merged properly in other branches).
> 
> 2- We need to automate writing release notes, pushing/tagging new docs when 
> release come out and announcing releases on website. Currently neither 4.7 
> nor 4.8 have been announced.
> 
> 3- CI is still almost inexistent
> 
> -Sebastien

[GitHub] cloudstack pull request: CLOUDSTACK-8717: Failed to start instance...

[sanju1010]

Github user sanju1010 commented on the pull request:

https://github.com/apache/cloudstack/pull/667#issuecomment-182802497
  
LGTM !!

Test Restore VM on VMWare ... === TestName: test_01_recover_VM | Status : 
SUCCESS ===
ok
 
--
Ran 1 test in 435.223s
 
OK



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: CLOUDSTACK-8717: Failed to start instance...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cloudstack/pull/667


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Build failed in Jenkins: build-master-jdk18 #477

[jenkins]

See 

Changes:

[priti.sarap] CLOUDSTACK-8717: Failed to start instance after restoring the 
running

[priti.sarap] CLOUDSTACK-8717: Failed to start instance after restoring the 
running

--
[...truncated 425 lines...]
Tests run: 10, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.555 sec - in 
com.cloud.utils.ScriptTest
Running com.cloud.utils.log.CglibThrowableRendererTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.206 sec - in 
com.cloud.utils.log.CglibThrowableRendererTest
Running com.cloud.utils.UuidUtilsTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.027 sec - in 
com.cloud.utils.UuidUtilsTest
Running com.cloud.utils.crypto.RSAHelperTest
2016-02-11 11:10:44,688 INFO  [utils.crypt.RSAHelper] (main:) [ignored]error 
during public key encryption: Unsupported format
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.931 sec - in 
com.cloud.utils.crypto.RSAHelperTest
Running com.cloud.utils.crypto.EncryptionSecretKeyCheckerTest
2016-02-11 11:10:44,864 DEBUG [utils.crypt.EncryptionSecretKeyChecker] (main:) 
Encryption Type: null
2016-02-11 11:10:44,864 DEBUG [utils.crypt.EncryptionSecretKeyChecker] (main:) 
Encryption Type: file
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.046 sec - in 
com.cloud.utils.crypto.EncryptionSecretKeyCheckerTest
Running com.cloud.utils.PropertiesUtilsTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.023 sec - in 
com.cloud.utils.PropertiesUtilsTest
Running com.cloud.utils.exception.ExceptionUtilTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec - in 
com.cloud.utils.exception.ExceptionUtilTest
Running com.cloud.utils.storage.QCOW2UtilsTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec - in 
com.cloud.utils.storage.QCOW2UtilsTest
Running com.cloud.utils.encoding.UrlEncoderTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec - in 
com.cloud.utils.encoding.UrlEncoderTest
Running com.cloud.utils.UriUtilsTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.063 sec - in 
com.cloud.utils.UriUtilsTest
Running com.cloud.utils.HttpUtilsTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.13 sec - in 
com.cloud.utils.HttpUtilsTest
Running com.cloud.utils.backoff.impl.ConstantTimeBackoffTest
2016-02-11 11:10:45,219 INFO  [backoff.impl.ConstantTimeBackoff] (Thread-1:) 
Thread Thread-1 interrupted while waiting for retry
2016-02-11 11:10:45,326 DEBUG [backoff.impl.ConstantTimeBackoffTest] (main:) 
thread started
2016-02-11 11:10:45,326 DEBUG [backoff.impl.ConstantTimeBackoffTest] 
(Thread-2:) before
2016-02-11 11:10:45,427 DEBUG [backoff.impl.ConstantTimeBackoffTest] (main:) 
testing wakeup
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.323 sec - in 
com.cloud.utils.backoff.impl.ConstantTimeBackoffTest
Running com.cloud.utils.ProcessUtilTest
2016-02-11 11:10:45,430 INFO  [backoff.impl.ConstantTimeBackoff] (Thread-2:) 
Thread Thread-2 interrupted while waiting for retry
2016-02-11 11:10:45,430 DEBUG [backoff.impl.ConstantTimeBackoffTest] 
(Thread-2:) after
2016-02-11 11:10:45,434 DEBUG [cloud.utils.ProcessUtil] (main:) 
environment.properties could not be opened
2016-02-11 11:10:45,442 DEBUG [cloud.utils.ProcessUtil] (main:) 
environment.properties could not be opened
2016-02-11 11:10:45,442 DEBUG [cloud.utils.ProcessUtil] (main:) Executing: bash 
-c ps -p 123456 
2016-02-11 11:10:45,514 DEBUG [cloud.utils.ProcessUtil] (main:) Exit value is 1
2016-02-11 11:10:45,514 DEBUG [cloud.utils.ProcessUtil] (main:)   PID TTY   
   TIME CMD
2016-02-11 11:10:45,516 DEBUG [cloud.utils.ProcessUtil] (main:) Executing: bash 
-c echo $PPID 
2016-02-11 11:10:45,522 DEBUG [cloud.utils.ProcessUtil] (main:) Execution is 
successful.
2016-02-11 11:10:45,528 DEBUG [cloud.utils.ProcessUtil] (main:) 
environment.properties could not be opened
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.099 sec - in 
com.cloud.utils.ProcessUtilTest
Running com.cloud.utils.PasswordGeneratorTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec - in 
com.cloud.utils.PasswordGeneratorTest
Running com.cloud.utils.rest.HttpUriRequestBuilderTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.065 sec - in 
com.cloud.utils.rest.HttpUriRequestBuilderTest
Running com.cloud.utils.rest.HttpStatusCodeHelperTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 sec - in 
com.cloud.utils.rest.HttpStatusCodeHelperTest
Running com.cloud.utils.rest.RESTServiceConnectorTest
2016-02-11 11:10:45,828 DEBUG [utils.rest.RESTServiceConnector] (main:) 
Executing retrieve object on /somepath
2016-02-11 11:10:45,829 DEBUG [utils.rest.BasicRestClient] (main:) Executig GET 
request on https://localhost:443/somepath
2016-02-11 

RE: Important Pending Items

[Paul Angus]

Hi Bharat,

Early last week I opened a discussion thread around the aims of Trillian which 
we had begun working on as a CI/CD platform for the community hardware (as well 
as individual use). Please could you elaborate on where there is/isn't 
cross-over? In terms of functionality and goals rather than method. It would be 
great to get community consensus around what we want from our centralised CI/CD.


Project: Trillian
We have been working on PoC of a CI environment design which will:
* Provide fast build or rebuild of environments for testing.
* Enable multiple independent concurrent builds
* Be available on-demand through automation or individual request.
* Be capable of fully utilising all available hardware
* Flexible enough to be used to build super-realistic development environments.
We intend to contribute and maintain our work within the Apache repos. However, 
we are currently building the POC, figuring out the requirements (and quirks) 
of the individual pieces, before pushing something concrete for to the 
community to review.

We envision that Trillian would cater for a number of use cases:
1. CloudStack community integration testing of master against multiple 
deployment scenarios (using ASF infra)
2. CloudStack community integration testing of PRs against multiple deployment 
scenarios (using ASF infra)
3. Organisations/individuals running the full suites of tests available in 
Marvin against any physical environment they have.
4. Organisations/individuals deploying and running the full suites of tests 
available in Marvin against virtualised infrastructures which can be deployed 
by Marvin.
As we intend Trillian to test multiple environments concurrently, we use nested 
virtualization on ESXi hosts (our testing has shown that this is the only 
hypervisor which can support the nested virtualisation of all other hypervisors 
with reasonable performance). We use Ansible to deploy and configure all 
aspects of the build as this will greatly lower the barrier to entry for 
independent testers.
We use CloudStack to provision the management server and virtualised (nested) 
hosts on the physical hosts. We are creating Ansible playbooks and roles which 
can:
1. Create guest instances using Rene's Ansible 2.0 CloudStack modules - a 
Marvin VM, a Mgmt Server (CentOS or Ubuntu), any number of compute hosts (KVM, 
vSphere or XenServer. Hyper-V later)
2. Configure hosts (inc. installing the relevant CloudStack agent where 
required)
3. Install required ACS packages on management server
4. Configure a zone (including adding the compute hosts) via Marvin.
5. Run the required Marvin tests.
6. Return the results
We may need to propose enhancements to Marvin in order to sync the 
configuration of hosts with the configuration used by Marvin.

Using virtualised test environments, we can have multiple test scenarios 
running concurrently. To do this we have found that it is necessary to create 
pools or ranges of VLANs and IP addresses and allocate them to environments. So 
for any given physical environment which will be used for testing in, we take 
the total range(s) of IPs and VLANs available and carve them into 
non-overlapping chunks suitable for concurrent use as mgmt, public and guest 
networks. These are stored in a MariaDB database. When a range is being used in 
a testing environment, that range is marked as 'inuse' in the database. When 
creating a test environment, Trillian looks in the database for the next 
available VLAN range, the next available public IP range and so on. The 
returned values are used to populate a Marvin cfg file which in turn will be 
used to both build the environment and when running the Marvin testing. When 
the virtualised infra is cleaned up, the database will be updated to reflect 
that the used ranges are available again.
This initiative has only recently been started, and as stated earlier we are 
currently figuring out the requirements (and quirks) of the individual pieces 
and looking for the most suitable wrapper to glue it all together.
Also I have found that Marvin requires a little work to make the output more 
meaningful/readable (especially in the case of errors and exceptions) and to 
make it a little more intelligent about the tests it can/can't run based on the 
chosen infrastructure components. I have also found unreachable or very slow 
ISO and template paths hardcoded into Marvin or individual tests.
We plan to enhance tests to address these issues and also reduce runtimes where 
possible.


[ShapeBlue]
Paul Angus
VP Technology   ,   ShapeBlue


d:  +44 203 617 0528 | s: +44 203 603 
0540 |  
m:  +44 7711 418784

e:  paul.an...@shapeblue.com | t: 
@cloudyangus  |
  w:  www.shapeblue.com

a:  53 Chandos Place, Covent 

[GitHub] cloudstack pull request: Squashing two commits in to single commit

[pritisarap12]

GitHub user pritisarap12 opened a pull request:

https://github.com/apache/cloudstack/pull/1411

Squashing two commits in to single commit

CLOUDSTACK-8717: Failed to start instance after restoring the running 
instance
-Modified code to add tag to aonly one cluster wide SP
-Added validateList function
-Added code to clear tags in tearDown class

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/pritisarap12/cloudstack 
CLOUDSTACK-8717-Failed-to-start-instance-after-restoring-the-running-instance

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1411.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1411


commit 8c7f5ab93d56c2aa0cde194509b728511173f7a9
Author: Priti Sarap 
Date:   2015-08-07T12:27:54Z

Squashing two commits in to single commit

CLOUDSTACK-8717: Failed to start instance after restoring the running 
instance
-Modified code to add tag to aonly one cluster wide SP
-Added validateList function
-Added code to clear tags in tearDown class




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---