Bernhard Wiedemann's avatar

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

Bernhard Wiedemann's avatar

Bernhard Wiedemann

bmwiedemann

Member of the group
Involved Projects and Packages
Maintainer Bugowner

Zstd, short for Zstandard, is a lossless compression algorithm,
targeting real-time compression scenarios at zlib-level compression ratio.

Zstd can also offer stronger compression ratios at the cost of
compression speed. Speed vs. compression trade-off is configurable by
small increments. Decompression speed is preserved and remains
roughly the same at all settings, a property shared by most LZ
compression algorithms, such as zlib or lzma.

Maintainer

Bareos (Backup Archiving Recovery Open Sourced) is a reliable, cross-network open source software for backup, archiving and recovery of data for all well-established operating systems.

Maintainer

Tools for configuring the console using X Window System key maps

Maintainer

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).

Maintainer

Eucalyptus 2.0 is an open source Linux-based software architecture that implements scalable, efficiency-enhancing private and hybrid clouds within an organization's IT infrastructure. Eucalyptus provides Infrastructure as a Service (IaaS). This means that users can provision their own collections of resources (hardware, storage, and network) via Eucalyptus’ self-service interface on an as-needed basis. A Eucalyptus cloud is deployed across an enterprise’s “on-premise” data center and is accessed by users over enterprise intranet. Thus, with a Eucalyptus private cloud, sensitive data remains secure from external intrusion behind the enterprise firewall.

Eucalyptus was designed from the ground up to be easy to install and as non-intrusive as possible. The software framework is highly modular, with industry-standard, language-agnostic communication. Eucalyptus is also unique by providing a virtual network overlay that both isolates network traffic of different users and allows two or more clusters to appear to belong to the same Local Area Network (LAN). Eucalyptus also interoperates seamlessly with Amazon’s EC2 and S3 public cloud services and thus offers the enterprise a hybrid cloud capability.

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)!

Staging projects are for automated package builds of their respective stable release (i.e OpenStack Icehouse). 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:Icehouse)!

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: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: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!

Maintainer

Configuration and customization of cloud instance

Configuration and customization of cloud instance

openSUSE Build Service is sponsored by