d4cd8c4202
Now that the StarlingX [1] and STX-Openstack [2] builds are functional on the f/antelope branch, we can move the STX-Openstack manifest to the master branch. [1] https://mirror.starlingx.windriver.com/mirror/starlingx/feature/antelope/debian/monolithic/latest_build/outputs/ [2] https://mirror.starlingx.windriver.com/mirror/starlingx/feature/antelope/debian/openstack/latest_build/outputs/ Test Plan: PASS: Initialize repo with custom manifest PASS: Perform a repo sync Story: 2010797 Task: 48249 Change-Id: I1e7e7d31ab42fd4dc7263e194c6e0ed2d7f2569b Signed-off-by: Lucas de Ataides <lucas.deataidesbarreto@windriver.com> |
||
---|---|---|
.gitignore | ||
.gitreview | ||
.zuul.yaml | ||
README.rst | ||
bindep.txt | ||
common.xml | ||
compiler.xml | ||
containers.xml | ||
default.xml | ||
distro.xml | ||
flock.xml | ||
stx-openstack.xml | ||
test-requirements.txt | ||
tox.ini |
README.rst
StarlingX Manifest
Download
The StarlingX source code can be downloaded from the default manifest XML file, by using the git-repo tool1, with the following commands:
export MANIFEST_URL="https://opendev.org/starlingx/manifest.git"
export MANIFEST_BRANCH="master"
export MANIFEST="default.xml"
repo init -u ${MANIFEST_URL} -b ${MANIFEST_BRANCH} -m ${MANIFEST}
repo sync
StarlingX Build Environment
The StarlingX Build Environment2 is a set of containers designed to run in a Kubernetes environment.
As an alternative, a Vagrant-based StarlingX Build Environment is available in the starlingx/tis-repo3.
Layered Build
Build layering4 is a feature to accelerate development within StarlingX. It optimizes the build of a small set of most-used top level packages, while avoiding rebuild of a large amount of infrequently used packages.
The packages are partitioned into the following layers, according to the corresponding manifests:
- compiler: Low level build tools: compilers, scripts, and packaging tools;
- distro: Linux and third party packages, e.g. ceph, openstack;
- flock: Basic StarlingX packages. These are the most used ones.
Reserved Manifests
The following manifests are reserved:
- common: packages always included in the build, regardless of layer;
- containers: packages to build containers;
- default: used as a means to download the StarlingX source code.
Developer Notes
When updating XML files, please remember to update the appropriate .gitignore file in https://opendev.org/starlingx/root otherwise the "repo status" command will show the new repo as an untracked change.
When updating the default.xml manifest, please also remember to update the appropriate layer manifest as well.