starlingx
/
manifest
Code Issues Proposed changes

Create stx-openstack manifest 

As discussed in [1], as part of the STX-Openstack upversion to Antelope
, we have to decouple the platform and the application builds in
separate manifests, in order to not clash the upversioned packages on
the application side, with the ones on the platform.

The purpose of this change is to introduce this new manifest, containing
the required repositories for a successfull build of the STX-Openstack
application.

For the test plan, despite this change being on the
`starlingx/manifest` repo, I wanted to make sure that all required
repositories for a successfull STX-Openstack build were present,
hence why the test plan is not the usual for this repository.

[1] https://lists.starlingx.io/pipermail/starlingx-discuss/2023-June/014214.html

Test Plan:
PASS: Initialize repo with custom manifest
PASS: Compare STX-Openstack tarball generated by this manifest against
      an official one and make sure no charts or FluxCD manifests are
      missing

On build environment:
  PASS: Download all dependencies (downloader -s -b -B std,rt)
  PASS: Build all packages (build-pkgs -c -a)
  PASS: Build wheels
  PASS: Build all STX-Openstack Docker images
  PASS: Build STX-Openstack tarball
  PASS: Upload / apply STX-Openstack

Story: 2010797
Task: 48249

Change-Id: I58510c120c35c0e894aeeef100df37c8c1c749c9
Signed-off-by: Lucas de Ataides <lucas.deataidesbarreto@windriver.com>
This commit is contained in:
Lucas de Ataides 2023-08-17 14:18:16 -03:00
parent 03866644f5
commit 9cd38ccdda
1 changed files with 37 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

37
stx-openstack.xml Normal file
View File

@ -0,0 +1,37 @@
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="starlingx" fetch="https://opendev.org/starlingx"/>
<remote name="stx-staging" fetch="https://github.com/starlingx-staging"/>
<remote name="openstack" fetch="https://opendev.org/openstack"/>
<remote name="docker" fetch="https://github.com/docker"/>
<!-- note, you can also provide personal overrides for your own github -->
<!-- for tests/experiments -->
<default revision="f/antelope" remote="starlingx"/>
<project remote="starlingx" name="root.git" path="cgcs-root"/>
<project remote="starlingx" name="tools.git" path="stx-tools"/>
<project remote="starlingx" name="public-keys.git" path="cgcs-root/public-keys"/>
<project remote="starlingx" name="compile.git" path="cgcs-root/stx/compile"/>
<project remote="starlingx" name="config.git" path="cgcs-root/stx/config"/>
<project remote="starlingx" name="config-files.git" path="cgcs-root/stx/config-files"/>
<project remote="starlingx" name="docs.git" path="cgcs-root/stx/docs"/>
<project remote="starlingx" name="fault.git" path="cgcs-root/stx/fault"/>
<project remote="starlingx" name="helm-charts.git" path="cgcs-root/stx/helm-charts"/>
<project remote="starlingx" name="integ.git" path="cgcs-root/stx/integ"/>
<project remote="starlingx" name="kernel.git" path="cgcs-root/stx/kernel"/>
<project remote="starlingx" name="openstack-armada-app.git" path="cgcs-root/stx/openstack-armada-app"/>
<project remote="starlingx" name="update.git" path="cgcs-root/stx/update"/>
<project remote="starlingx" name="utilities.git" path="cgcs-root/stx/utilities"/>
<project remote="starlingx" name="virt.git" path="cgcs-root/stx/virt"/>
<project remote="stx-staging" name="stx-ceph.git" revision="stx/v14.2.22" path="cgcs-root/stx/git/ceph"/>
<project remote="docker" revision="refs/tags/v2.6.2" name="distribution.git" path="cgcs-root/stx/git/docker-distribution"/>
</manifest>