James Fehlig's avatar

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

James Fehlig's avatar

James Fehlig

jfehlig

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

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

Configuration and customization of cloud instance

Configuration and customization of cloud instance

QEMU is a quick emulator, using dynamic translation (TCG). It also serves as frontend for KVM and as backend for Xen device emulation.

Note that this package is based on a Git patch queue and the .spec file is thus generated from qemu.spec.in.

Maintainer

Xen is a virtual machine monitor for x86 that supports execution of
multiple guest operating systems with unprecedented levels of
performance and resource isolation.

This package contains the Xen Hypervisor. (tm)

Modern computers are sufficiently powerful to use virtualization to
present the illusion of many smaller virtual machines (VMs), each
running a separate operating system instance. Successful partitioning
of a machine to support the concurrent execution of multiple operating
systems poses several challenges. Firstly, virtual machines must be
isolated from one another: It is not acceptable for the execution of
one to adversely affect the performance of another. This is
particularly true when virtual machines are owned by mutually
untrusting users. Secondly, it is necessary to support a variety of
different operating systems to accommodate the heterogeneity of popular
applications. Thirdly, the performance overhead introduced by
virtualization should be small.

Xen uses a technique called paravirtualization: The guest OS is
modified, mainly to enhance performance.

The Xen hypervisor (microkernel) does not provide device drivers for
your hardware (except for CPU and memory). This job is left to the
kernel that's running in domain 0. Thus the domain 0 kernel is
privileged; it has full hardware access. It's started immediately after
Xen starts up. Other domains have no access to the hardware; instead
they use virtual interfaces that are provided by Xen (with the help of
the domain 0 kernel).

Xen does support booting other Operating Systems; ports of NetBSD
(Christian Limpach), FreeBSD (Kip Macy), and Plan 9 (Ron Minnich)
exist. A port of Windows XP was developed for an earlier version of
Xen, but is not available for release due to license restrictions.

In addition to this package you need to install the kernel-xen and
xen-tools to use Xen. Xen 3 also supports running unmodified guests
using full virtualization, if appropriate hardware is present. Install
xen-tools-ioemu if you want to use this.

[Hypervisor is a trademark of IBM]

Bugowner

QEMU is a quick emulator, using dynamic translation (TCG). It also serves as frontend for KVM and as backend for Xen device emulation.

Note that this package is based on a Git patch queue and the .spec file is thus generated from qemu.spec.in.

home:gygyegy22w7612:branches:openSUSE:Factory:staging

openSUSE Build Service is sponsored by