Steve Kowalik's avatar

You are behind a proxy. You can modify other data related to your profile by this link.

Steve Kowalik's avatar

Steve Kowalik

StevenK

Member of the groups
Involved Projects and Packages
Maintainer

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.

Maintainer

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!

Maintainer

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!

Maintainer

Configuration and customization of cloud instance

Configuration and customization of cloud instance

This project provides generic python modules. The Python interpreter itself is developed at devel:languages:python:Factory.

If you happen to have collection of python packages send an email to opensuse-packaging to discuss wether it would not be better to provide them subproject within devel:languages:python namespace instead of storing them here.

The Python packaging policies are found at http://en.opensuse.org/openSUSE:Packaging_Python and https://en.opensuse.org/openSUSE:Packaging_Python_Singlespec

The project is focused on maintaining reasonable closeness to upstream
versions while at the same time trying to make packages available for openSUSE distribution.

The main focus is openSUSE Tumbleweed and packages that are not in there will be periodically pruned from the project.

Backporting of packages against older distribution releases should not be happening in this project, only build verification. If a package is needed on any of the older openSUSE products then maintenance update is to be created. Alternatively for SLE products submission by an interested party should be done by openSUSE:Backports project.
If you just need the newest packages, please consider using devel:languages:python:backports instead.

This is due to the size of this project and likeness of errors caused by adding this whole repository.

This project is building the Tumbleweed versions of python modules for older distributions. Submission should happen to the respective devel project for the Tumbleweed package instead.

The packages in here are automatically polled from OBS openSUSE:Factory repository and removed/added as they live there.

Script to generate the content:

https://github.com/openSUSE/python-backports-generate

Development project for python interpreting parsers for openSUSE Tumbleweed.

Testing builds are again done against older distributions to verify backporting potential. Do NOT add on your machines.

openSUSE Build Service is sponsored by