Page History

...

https://issues.apache.org/jira/browse/CLOUDSTACK-6282

2. Deploy DataCenter Changes:

• Separating TestClient from

...

• deploy Data Center: Earlier, testclient creation is also part of deployDatacenter. It is not part of this module

...

• responsibility to create test client in general. Now with this separation, testclient creation is

...

•  moved to cloudstackTestClient module and is responsible for creating and providing the test client for regression run. Added changes to both deployDataCenter and cloudstackTestClient. Fixed few misc issues and did some clean up here. Now deployDC will just take the required configuration and parameters and create the

...

• Data Center we needed.

...

•  
  
  
• Delete Data Center:

...

•   There is no way to delete a data center created earlier in current deploy Data Center. Added a new

...

• delete Data Center Interface to delete the earlier created

...

• data center. If user wants to delete a

...

• Data Center created and recreate, deleting has to be manual earlier. With this change, he can delete a data center created earlier. It will be useful at many places for testing to destroy and recreate with new settings etc.

...

• 
  Usage: python deployDataCenter.py -i <path_to_marvin_config> -r<path_to_exported_create_config>

• Data Center creation as Transaction : At any given point of time during deploy data center, if an issue happens half way through, earlier created entries were still available in CS, it wont clean up i.e., data center is half created, Again, if tried to recreate , the earlier existing entries

...

• won't allowed to recreate. Now, data center works as transaction, either all entries are created as part of data center run or none, added a clean up to delete the half created data center. 
  
  
• Export the created Data Center: Export the created Data Center as configuration, so that user can use it to further delete the data center with these exported entries etc. So, we can create, export,delete,recreate etc

...

• for our testing. This will  help in testing. With this change, once deploy Data Center finishes, it exports the created configuration to a path mentioned under input config file.

4. Logging enhancements: During the regression run,earlier we had various and a little confusing log options. Now, marvin run logs will be streamlined at one place. Here, for the entire run, we will see different logs viz., run\results\exceptions+passfail log all at one place. We have added MarvinLog to explicitly provide logging facility to Marvin. Before running test suites, we just need to configure the path for logs. MarvinInit along with MarvinLog will now create all logs required for the run under this path. Before every run, it will clean up the previously created MarvinLogs folder before proceeding with run. MarvinLogs folder will be created at the mentioned and configured path and all test suites will dump different logs here.  Each test run will now have a test module name for log for easy identification. Logs for Run info, exception information ,results information etc are all provided here. So, all logs separated by different category help resolve issues quickly. The log folder path once configured, will be used to provide logs separately for each test module. All Test script Exceptions will now be caught at one place under exception\failed log. It will help identify script issues vs product issues. Added few more log levels here.

...