aboutsummaryrefslogtreecommitdiffstats
path: root/ci/pingtests
AgeCommit message (Collapse)AuthorFilesLines
2017-02-14Deploy Manila with CephMDS in scenario004Giulio Fidente1-0/+12
Adds the Manila and CephMDS services into scenario004 and a few resources in the pingtest to test the Manila deployment. Also adds Pacemaker to scenario004 which is needed for ManilaShare. Co-Authored-By: jprovazn@redhat.com Depends-On: Ia2ece0163a3c25eb28bc0b471cd1797d52fe4e3c Change-Id: I70515c5b9ce2668a684649ecd40421b69078ee83 Related-Bug: #1644784
2017-02-02Moving the validation for using the template alias version for all templatesCarlos Camacho1-1/+1
Currently we are applying this validation for the services templates, this submission moves it to run with all templates. Also fixed those templates not using the alias name. Change-Id: I3a2c0ce6adcc8061fdc51f73fdc6b9748c0fead9
2017-01-24Import multinode + pingtest from tripleo-ciEmilien Macchi1-0/+142
* Import multinode-3nodes roles data * Import multinode * Import tenantvm_floatingip pingtest We are importing these files from tripleo-ci because they contain some informations that need to be versionned (TripleO services, data binding, etc), specific to TripleO versions. Change-Id: I9d4ab144f98e8bd46cad2c29411d1270f6469b91
2017-01-24scenario002: updating volume encryption providerEmilien Macchi1-1/+1
https://review.openstack.org/#/c/416672 made the new luks provider required. Let's use it. Closes-Bug: #1658755 Change-Id: Icc7c3c933af6621959ce3e6af99c73b4afd87509
2016-12-23Bump template version for all templates to "ocata"Steven Hardy4-4/+4
Heat now supports release name aliases, so we can replace the inconsistent mix of date related versions with one consistent version that aligns with the supported version of heat for this t-h-t branch. This should also help new users who sometimes copy/paste old templates and discover intrinsic functions in the t-h-t docs don't work because their template version is too old. Change-Id: Ib415e7290fea27447460baa280291492df197e54
2016-12-02Merge "scenario001: deploy Cinder with RBD backend"Jenkins1-1/+11
2016-12-02Merge "Add Zaqar to scenario002"Jenkins1-0/+5
2016-12-02Merge "Implement scenario004 with Ceph Rados Gateway scenario"Jenkins1-0/+127
2016-12-01scenario001: deploy Cinder with RBD backendEmilien Macchi1-1/+11
Improve scenario001 with Cinder + RBD coverage. Also remove Barbican bits, we don't deploy Barbican in scenario001, but 002. Change-Id: Ib9cadbefcb3ddcdb4812f47ff5496e74b2bd888d
2016-12-01Implement scenario004 with Ceph Rados Gateway scenarioEmilien Macchi1-0/+127
Like Puppet OpenStack CI, implement scenario004 with Ceph RGW scenario, where Glance uses it as a image storage backend. Change-Id: If055ca225c456a738c5726ef1e76a4a4f9c566a8
2016-12-01scenario001/pingtest: remove gnocchi_res_alarmEmilien Macchi1-13/+15
The resource is failing and it prevents us to add more coverage. Until we figure what's wrong with it, let's disable it. Change-Id: If89775bf67d686327d0d27222e0c9179be74a668
2016-11-30Add Zaqar to scenario002Brad P. Crochet1-0/+5
Install Zaqar into the overcloud and create a queue with OS::Zaqar::Queue in order to test the Zaqar composable service. Change-Id: I9027d17fa3d75e6c3e23d6636642abadac8730ac Depends-On: Ia5ca4fe317339dd05b0fa3d5abebca6ca5066bce
2016-11-30Merge "Add Mistral to scenario003"Jenkins1-0/+19
2016-11-30Add Mistral to scenario003Brad P. Crochet1-0/+19
Install Mistral into the test overcloud and create a workflow to verify the Mistral installation. This does not currently actually execute the workflow. It merely tests that it can be created. Change-Id: Ia03a605bcfd92498bf299d3042dca7c9932f5b63 Depends-On: Id5ff9cb498b5a47af38413d211ff0ed6ccd0015b
2016-11-29Test encrypted volumes in scenario002Juan Antonio Osorio Robles1-0/+16
This effectively adds barbican-api to the deployment in scenario002 and uses it to provide encrypted volumes for cinder that a nova instance boots from in the test. Change-Id: I132e346755fb49c9563247b4404be06b97f77872
2016-11-25Import TripleO CI environments from tripleo-ciEmilien Macchi3-0/+446
Import TripleO CI environments from tripleo-ci into THT for some reasons: 1) THT is branched while tripleo-ci is not. Having them here would allow to make scenarios able to evolve over the releases without adding more scenarios. 2) Help our developers to run TripleO CI scenarios themselves from THT by exposing the templates here. The whole discussion is here: http://lists.openstack.org/pipermail/openstack-dev/2016-November/107816.html Change-Id: I3527a64c0c8f56ca77115d32849fa23fe710112d