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 synchronous Ruby AMQP client that enables interaction with AMQP-compliant brokers.

Authors:
Chris Duncan, Eric Lindvall, Jakub Stastny aka botanicus, Michael S. Klishin, Stefan Kaes

See also http://rubygems.org/gems/bunny

A systems integration framework, built to bring the benefits of configuration management to your entire infrastructure.

Lint tool for Opscode Chef cookbooks.

Author: Andrew Crump

Based on http://rubygems.org/gems/foodcritic

knife-solo adds a handful of commands that aim to make working with chef-solo as powerful as chef-server

A framework for writing bundlers, which are tools that resolve, fetch, install, and isolate a project's dependencies, in Ruby.

OSSP uuid is a ISO-C:1999 application programming interface (API) and
corresponding command line interface (CLI) for the generation of DCE 1.1,
ISO/IEC 11578:1996 and RFC 4122 compliant Universally Unique Identifier (UUID).
It supports DCE 1.1 variant UUIDs of version 1 (time and node based), version 3
(name based, MD5), version 4 (random number based) and version 5 (name based,
SHA-1). Additional API bindings are provided for the languages ISO-C++:1998,
Perl:5 and PHP:4/5. Optional backward compatibility exists for the ISO-C
DCE-1.1 and Perl Data::UUID APIs.

UUIDs are 128 bit numbers which are intended to have a high likelihood of
uniqueness over space and time and are computationally difficult to guess. They
are globally unique identifiers which can be locally generated without
contacting a global registration authority. UUIDs are intended as unique
identifiers for both mass tagging objects with an extremely short lifetime and
to reliably identifying very persistent objects across a network.

Authors:
--------
Ralf S. Engelschall

not ready for production!!!

Stable branch of the Chef 10 packages.

Chef is an open source systems integration framework built to bring the benefits of configuration management to your entire infrastructure. You write source code to describe how you want each part of your infrastructure to be built, then apply those descriptions to your servers. The result is a fully automated infrastructure: when a new server comes on line, the only thing you have to do is tell Chef what role it should play in your architecture.

Development project for the latest Chef version. In our approach to make Chef a part of openSUSE, the development of the Chef 11 core packages now happens mostly in the appropriate project, devel:languages:erlang.

Chef is an open source systems integration framework built to bring the benefits of configuration management to your entire infrastructure. You write source code to describe how you want each part of your infrastructure to be built, then apply those descriptions to your servers. The result is a fully automated infrastructure: when a new server comes on line, the only thing you have to do is tell Chef what role it should play in your architecture.

- Subproject 'Master' contains the development version.
- Subproject 'Stable' contains the latest released versions.
- Subproject 'Snapshots' contains previous released versions (to be used for migration tests, but not maintained anymore).
- Subproject 'Utils' contains several utilities to build, develop or release Uyuni.
- Subproject 'Test-Packages' contains packages to be used for testing.

The packages here should always come from `systemsmanagement`. This project is here just so if something breaks at `systemsmanagement` we don't break our builds , and we can promote from there when the problem is fixed. In short: this is a staging area.

The project is locked so the package does not rebuild automatically.

For promotion from server:monitoring

1. Run: osc unlock systemsmanagement:Uyuni:grafana grafana
2. Run: osc copypac server:monitoring grafana systemsmanagement:Uyuni:grafana
3. Run: osc lock systemsmanagement:Uyuni:grafana grafana

Pull request build job PR#47 to branch uyuni-main of uyuni/Uyuni