- Apr 30, 2018
-
-
ZhijunWei authored
refer to https://review.openstack.org/#/c/564169/ Change-Id: I093b0b8fd3b34c9b35149c9e4ae945a8e0e67f53
-
- Mar 08, 2018
-
-
Jeffrey Zhang authored
This reverts commit 2a4ce0b8. Change-Id: I52efd29791a230df1ce7e3acde4b7184aec34150
-
- Feb 23, 2018
-
-
Jeffrey Zhang authored
We have pin keyston to queens release which supports UUID token through https://review.openstack.org/546475, let us use UUID in queens and migrate to fernet in rocky cycle. This reverts commit df0bf190. Change-Id: Ifb0112315b5047461ce0bf02c754cc0beac52d9a
-
- Feb 19, 2018
-
-
Eduardo Gonzalez authored
we have gates currently broken due using rocky keystone code. we have no way to test our release until we branch out queens. this change doesnt change globals default, only our gates tests. Change-Id: I189aa8cafc73a365668d79e4b186aac21da63a6f
-
- Jan 23, 2018
-
-
Jeffrey Zhang authored
Use the same router will result in conflict in the CI environment. Change-Id: Id1ba69ebbf67b4cead855adbe440343c05ea3d1e Closes-Bug: #1744913
-
- Dec 27, 2017
-
-
Michal (inc0) Jastrzebski authored
Another step to migrate to new CI Change-Id: Id9bf9b4b1114f5be66f6c028a0db16d869efeceb Depends-On: Iaacdca31b27b7033ec08499bcea7061b9d3ec279
-
- Nov 16, 2017
-
-
Jeffrey Zhang authored
Change-Id: Id71c1ecda9f8647a0eb290fe02a12afb3df09988
-
- Oct 18, 2017
-
-
Jeffrey Zhang authored
Partial-Bug: #1720601 Change-Id: Ibc20a6ae8c645ff82f3c14a6286073dffd4cfae2
-
- Jun 19, 2017
-
-
Michal (inc0) Jastrzebski authored
First non-trivial scenario we'll be testing in gates will be cinder + ceph. This patchset is supposed to create framework to easily add new testing scenarios. Change-Id: I6790eaf5cf3297af04a64e4169a39b6e2cd1890f
-
- Jun 15, 2017
-
-
Jeffrey Zhang authored
This reverts commit 94a882ba. Upstream has fix this issue by Ice89ad9dd486ad5fcac534ef5f7d8aae3b6b0f97 Change-Id: Ib17f93e4030c6f7da4e32ee84fcc5f7139e57895 Closes-Bug: #1694420
-
- Jun 05, 2017
-
-
Michal (inc0) Jastrzebski authored
This patches changes deploy_gate quite a bit so in reality all deployments will now assume multinode (even if it's single node). After that we will refactor it even further to enable easy addition of new scenerios. Change-Id: I1faada46e6a7aa026128b2f01d77eabb04759439
-