This is a collection of packages needed to maintain and run additional software components of the Cloud related CI jobs.
It is a central place to collect these dependencies only by linking to packages maintained elsewhere (preferably Factory, devel-projects).

The images and packages are built in sub-projects named after the distributions for which they are built. This project should in general be empty.

A massively scalable cloud operating system. This project is only a container and includes the following sub-projects:

Cloud:OpenStack:Factory - The current stable version for openSUSE (openSUSE:Factory devel project)
Cloud:OpenStack:Master - Latest packaged upstream version and bleeding-edge development
Cloud:OpenStack:Train - The OpenStack Train release
Cloud:OpenStack:Stein - The OpenStack Stein release
Cloud:OpenStack:Rocky - The OpenStack Rocky release
Cloud:OpenStack:Queens - The OpenStack Queens release - EOL
Cloud:OpenStack:Pike - The OpenStack Pike release
Cloud:OpenStack:Ocata - The OpenStack Ocata release - EOL
Cloud:OpenStack:Newton - The OpenStack Newton release
Cloud:OpenStack:Mitaka - The OpenStack Mitaka release EOL
Cloud:OpenStack:Liberty - The OpenStack Liberty release EOL
Cloud:OpenStack:Kilo - The OpenStack Kilo release - EOL
Cloud:OpenStack:Juno - The OpenStack Juno release - EOL
Cloud:OpenStack:Icehouse - The OpenStack Icehouse release - EOL
Cloud:OpenStack:Havana - The OpenStack Havana release - EOL
Cloud:OpenStack:Grizzly - The OpenStack Grizzly release - EOL
Cloud:OpenStack:Folsom - The OpenStack Folsom release - EOL
Cloud:OpenStack:Essex - The OpenStack Essex release - EOL

There is also Cloud:OpenStack:Upstream:Master (and other subprojects under Cloud:OpenStack:Upstream). These packages are automatically generated from the RPM-packaging project (see https://wiki.openstack.org/wiki/Rpm-packaging)
Some further links that may be of interest:

OpenStack project: http://www.openstack.org
OpenStack releases: https://releases.openstack.org/
SUSE Cloud product: http://suse.com/cloud
http://en.opensuse.org/openSUSE:OpenStack_and_Crowbar_development_process

A massively scalable cloud operating system.

Contains always the latest stable OpenStack release based on the SUSE Cloud product and is used as a devel project for openSUSE:Factory.

##################################################################
MOST OF THE PACKAGES ARE MAINTAINED AT https://opendev.org/openstack/rpm-packaging/ .
Please use the gerrit workflow to submit patches
##################################################################

OpenStack project: http://www.openstack.org
SUSE Cloud product: http://suse.com/cloud

If you add this repository to your openSUSE installation, make sure it has a higher repository priority in zypper. Otherwise you will end up using the wrong dependencies depending on your openSUSE release.

DON'T SUBMIT HERE DIRECTLY, USE Cloud:OpenStack:Havana:Staging!

Staging projects are for automated package builds of their respective stable release (i.e OpenStack Havana). New packages come from either:

- The trackupstream Jenkins Job, following the upstream commits in the stable branche
- Packagers, doing security / bug fixes

Each package submission triggers a testsuite run. Once that passed, the package submission should be safe to go to the stable branch. This means that direct package submissions to stable projects are a taboo (i.e. no submissions to Cloud:OpenStack:Havana)!

If you add this repository to your openSUSE installation, make sure it has a higher repository priority in zypper. Otherwise you will end up using the wrong dependencies depending on your openSUSE release.

DON'T SUBMIT HERE DIRECTLY, USE Cloud:OpenStack:Juno:Staging!

Staging projects are for automated package builds of their respective stable release (i.e OpenStack Juno). New packages come from either:

- The trackupstream Jenkins Job, following the upstream commits in the stable branche
- Packagers, doing security / bug fixes

Each package submission triggers a testsuite run. Once that passed, the package submission should be safe to go to the stable branch. This means that direct package submissions to stable projects are a taboo (i.e. no submissions to Cloud:OpenStack:Juno)!

A massively scalable cloud operating system. Contains always the latest upstream OpenStack code.

OpenStack project: https://www.openstack.org

If you add this repository to your openSUSE installation, make sure it has a higher repository priority in zypper. Otherwise you will end up using the wrong dependencies depending on your openSUSE release.

DON'T SUBMIT HERE DIRECTLY, USE Cloud:OpenStack:Pike:Staging!

Staging projects are for automated package builds of their respective stable release (i.e OpenStack Pike). New packages come from either:

- The trackupstream Jenkins Job, following the upstream commits in the stable branches
- Packagers, doing security / bug fixes

Each package submission triggers a testsuite run. Once that passed, the package submission should be safe to go to the stable branch. This means that direct package submissions to stable projects are a taboo (i.e. no submissions to Cloud:OpenStack:Pike)!

Staging projects are for automated package builds of their respective stable release (i.e OpenStack Rocky). New packages come from either:

- The trackupstream Jenkins Job, following the upstream commits in the stable branches
- Packagers, doing security / bug fixes

Each package submission triggers a testsuite run. Once that passed, the package submission should be safe to go to the stable branch. This means that direct package submissions to stable projects are a taboo (i.e. no submissions to Cloud:OpenStack:Rocky)!

If you add this repository to your openSUSE installation, make sure it has a higher repository priority in zypper. Otherwise you will end up using the wrong dependencies depending on your openSUSE release.

DON'T SUBMIT HERE DIRECTLY, USE Cloud:OpenStack:Train:Staging!

If you add this repository to your openSUSE installation, make sure it has a higher repository priority in zypper. Otherwise you will end up using the wrong dependencies depending on your openSUSE release.

DON'T SUBMIT HERE DIRECTLY, USE Cloud:OpenStack:Zed:Staging!

If you add this repository to your openSUSE installation, make sure it has a higher repository priority in zypper. Otherwise you will end up using the wrong dependencies depending on your openSUSE release.

DON'T SUBMIT HERE DIRECTLY, USE Cloud:OpenStack:Ussuri:Staging!

If you add this repository to your openSUSE installation, make sure it has a higher repository priority in zypper. Otherwise you will end up using the wrong dependencies depending on your openSUSE release.

DON'T SUBMIT HERE DIRECTLY, USE Cloud:OpenStack:Victoria:Staging!

If you add this repository to your openSUSE installation, make sure it has a higher repository priority in zypper. Otherwise you will end up using the wrong dependencies depending on your openSUSE release.

DON'T SUBMIT HERE DIRECTLY, USE Cloud:OpenStack:Wallaby:Staging!

If you add this repository to your openSUSE installation, make sure it has a higher repository priority in zypper. Otherwise you will end up using the wrong dependencies depending on your openSUSE release.

DON'T SUBMIT HERE DIRECTLY, USE Cloud:OpenStack:Xena:Staging!

If you add this repository to your openSUSE installation, make sure it has a higher repository priority in zypper. Otherwise you will end up using the wrong dependencies depending on your openSUSE release.

DON'T SUBMIT HERE DIRECTLY, USE Cloud:OpenStack:Yoga:Staging!

If you add this repository to your openSUSE installation, make sure it has a higher repository priority in zypper. Otherwise you will end up using the wrong dependencies depending on your openSUSE release.

DON'T SUBMIT HERE DIRECTLY, USE Cloud:OpenStack:Zed:Staging!

Cloud related tools such as instance initialization code, CLI tools to interact with Cloud frameworks, etc.

Dependencies for packages maintained in this repository are collected in TLA-TARGET-aggregate packages if there is more than 1 dependency we need from a given project.

Where:

TLA is a Three-Letter-Acronym for the origin project from which the packages within are aggregated.
TARGET is the build target for which these packages are aggregated

For example dlp-sle12-aggregates collects all the packages that are pulled from devel:languages:python for SLE 12 base distribution build targets

Configuration and customization of cloud instance

Configuration and customization of cloud instance