Page History

...

1. Currently this infrastructure has limited capacity and with the increasing number of tests we sometimes run out of resources during a test run
2. Only advanced zone and basic zone with security groups are currently employed. Any external networking device etc is not employed in this testbed
3. No object storage or ceph storage

Enhancements

• run test fixes on idle environment upon checkin without deploy
• creating ones own slave vm appliance
• dogfooding the slave appliance run test fixes on idle environment upon checkin without deployvia packer
• custom zones - using a marvin config file
• logging enhancements = archiving + syslog
• digest emails via jenkins. controlling spam
• external devices (LB, VPX, FW)

Future

1. monitoring and status page for the infra
2. control all jenkins jobs via github using jenkins-job-builder
3. multiple internal jenkins environments on a single landing page jenkins.bacd.orgnot everyone deploys CloudStack the same
4. multiple hv environments with multiple hv configurations
5. multiple storage configurations - ceph, object store etc

Troubleshooting

Any of the several steps in the workflow can fail. If you find a failure, please bring the issue to notice on the dev@ mailing list.