summaryrefslogtreecommitdiffstats
path: root/ci/kolla_patches
AgeCommit message (Collapse)AuthorFilesLines
2018-04-01kolla-build-vm.sh is ready for QueensZhijiang Hu2-0/+104
This PS does: 1. Set default build target to stable/queens, but still fix to pike for OPNFV master branch, please see line:83 2. Create mappings between branch name and version number in code, since upstream kolla does not do it automatically using git tag for us start from Queens relese. Therefore, we do not need to let the user to define the version code and then check it with git tag command return value any more. So -t argument is deleted. 3. Support building Queens images. 4. Arrange patches in sub-directories name by version code so that user can use this one script to patch and build any version they want. But for OPNFV Jenkins, only the version for the current branch can be built according to the -j argument. 5. Upgrade DPDK version from 16.11 to 17.02. 6. Call cleanup_registry_server before pack_registry_data, this is resonable for keeping registry data stable. Change-Id: Ic5a7e2da261d456a2a1481ad0e765a7ce28b8121 Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
2018-01-24Sync kolla patchesZhijiang Hu1-3/+101
Change-Id: I1f13f72d4e75fa7414c571e6db080d0f08f47a96 Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
2018-01-05Add upstream patchesZhijiang Hu1-0/+88
When we building kolla images in OPNFV jenkins job, we need to clone code directly from openstack/kolla project and patch it with necessary patches needed by OPNFV. This is the first patch focus on ODL and DPDK integration. To use it, please clone openstack/kolla's stable/pike branch first then apply patch by using git apply command. This PS also solved git clone risk found by Anteater by deleting url variable in git clone command. Change-Id: I9d02f0d4919b53fb33233399ed4efd57d27b21a1 Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>