791 lines
30 KiB
YAML
791 lines
30 KiB
YAML
---
|
||
name: OpenStack Components
|
||
tabs:
|
||
|
||
- name: OpenStack services
|
||
prelude: >
|
||
An OpenStack deployment contains a number of components providing
|
||
APIs to access infrastructure resources. This page lists the various
|
||
services that can be deployed to provide such resources to cloud
|
||
end users.
|
||
categories:
|
||
|
||
- category: Compute
|
||
components:
|
||
|
||
- name: nova
|
||
title: Compute Service
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/nova/latest/
|
||
desc: >
|
||
To implement services and associated libraries to provide
|
||
massively scalable, on demand, self service access to compute
|
||
resources, including bare metal, virtual machines, and
|
||
containers.
|
||
project-team: nova
|
||
since: Austin
|
||
dependencies:
|
||
- keystone
|
||
- neutron
|
||
- glance
|
||
- placement
|
||
see-also:
|
||
- cinder
|
||
- ironic
|
||
- barbican
|
||
- designate
|
||
video:
|
||
id: 6l9_EC4bfD0
|
||
desc: >
|
||
Project Updates cover the latest changes in the project. See
|
||
what's new in Victoria, the latest OpenStack release, and
|
||
what you can expect to see from the project in the upcoming
|
||
release.
|
||
title: Nova Project Update
|
||
|
||
|
||
- name: zun
|
||
title: Containers Service
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/zun/latest/
|
||
desc: >
|
||
Zun provides an OpenStack API for launching and managing
|
||
containers backed by different container technologies.
|
||
Different from Magnum, Zun is for users who want to treat
|
||
containers as OpenStack-managed resource. Containers managed
|
||
by Zun are supposed to be integrated well with other OpenStack
|
||
resources, such as Neutron network and Cinder volume. Users
|
||
are provided a simplified APIs to manage containers without
|
||
the need to explore the complexities of different container
|
||
technologies.
|
||
project-team: zun
|
||
since: Pike
|
||
dependencies:
|
||
- keystone
|
||
- neutron
|
||
- kuryr
|
||
see-also:
|
||
- cinder
|
||
- glance
|
||
|
||
- category: Hardware Lifecycle
|
||
components:
|
||
|
||
- name: ironic
|
||
title: Bare Metal Provisioning Service
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/ironic/latest/
|
||
desc: >
|
||
To implement services and associated libraries to provide
|
||
massively scalable, on demand, self service access to compute
|
||
resources, including bare metal, virtual machines, and
|
||
containers.
|
||
project-team: ironic
|
||
since: Kilo
|
||
see-also:
|
||
- keystone
|
||
- nova
|
||
- cinder
|
||
- neutron
|
||
- glance
|
||
- swift
|
||
|
||
- name: cyborg
|
||
title: Lifecycle management of accelerators
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/cyborg/latest/
|
||
desc: >
|
||
Cyborg provides a general purpose management framework for
|
||
accelerators (including GPUs, FPGAs, ASIC-based devices, etc.)
|
||
project-team: cyborg
|
||
since: Rocky
|
||
dependencies:
|
||
- keystone
|
||
- glance
|
||
see-also:
|
||
- nova
|
||
|
||
- category: Storage
|
||
components:
|
||
|
||
- name: swift
|
||
title: Object store
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/swift/latest/
|
||
desc: >
|
||
Swift is a highly available, distributed, eventually consistent
|
||
object/blob store. Organizations can use Swift to store lots of
|
||
data efficiently, safely, and cheaply. It's built for scale and
|
||
optimized for durability, availability, and concurrency across
|
||
the entire data set. Swift is ideal for storing unstructured
|
||
data that can grow without bound.
|
||
project-team: swift
|
||
since: Austin
|
||
see-also:
|
||
- storlets
|
||
- barbican
|
||
- keystone
|
||
video:
|
||
id: _I7vC3oXqRw
|
||
desc: >
|
||
Project Updates cover the latest changes in the project. See
|
||
what's new in the latest OpenStack release, and what you can
|
||
expect to see from the project in the upcoming release.
|
||
title: Swift - Project Update
|
||
|
||
- name: cinder
|
||
title: Block Storage
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/cinder/latest/
|
||
desc: >
|
||
Cinder is a Block Storage service for OpenStack. It virtualizes
|
||
the management of block storage devices and provides end users
|
||
with a self service API to request and consume those resources
|
||
without requiring any knowledge of where their storage is
|
||
actually deployed or on what type of device. This is done through
|
||
the use of either a reference implementation (LVM) or plugin
|
||
drivers for other storage.
|
||
project-team: cinder
|
||
since: Folsom
|
||
dependencies:
|
||
- keystone
|
||
see-also:
|
||
- nova
|
||
- barbican
|
||
video:
|
||
id: 54f6SmUifdA
|
||
desc: >
|
||
Project Updates cover the latest changes in the project. See
|
||
what's new in Victoria, the latest OpenStack release, and
|
||
what you can expect to see from the project in the upcoming
|
||
release.
|
||
title: Cinder Project Update - Brian Rosmaita
|
||
|
||
- name: manila
|
||
title: Shared filesystems
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/manila/latest/
|
||
desc: >
|
||
Manila provides coordinated access to shared or distributed file
|
||
systems.
|
||
project-team: manila
|
||
since: Liberty
|
||
see-also:
|
||
- keystone
|
||
video:
|
||
id: D3NyRLbSnAw
|
||
desc: >
|
||
Project Updates cover the latest changes in the project. See
|
||
what's new in Victoria, the latest OpenStack release, and
|
||
what you can expect to see from the project in the upcoming
|
||
release.
|
||
title: Manila Project Update - Goutham Pacha Ravi
|
||
|
||
- category: Networking
|
||
components:
|
||
|
||
- name: neutron
|
||
title: Networking
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/neutron/latest/
|
||
desc: >
|
||
OpenStack Neutron is an SDN networking project focused on
|
||
delivering networking-as-a-service (NaaS) in virtual compute
|
||
environments.
|
||
project-team: neutron
|
||
since: Folsom
|
||
dependencies:
|
||
- keystone
|
||
see-also:
|
||
- nova
|
||
video:
|
||
id: oHRSxfyMuYc
|
||
desc: >
|
||
Project Updates cover the latest changes in the project. See
|
||
what's new in Victoria, the latest OpenStack release, and
|
||
what you can expect to see from the project in the upcoming
|
||
release.
|
||
title: Neutron Project Update - Slawek Kaplonski
|
||
|
||
- name: octavia
|
||
title: Load balancer
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/octavia/latest/
|
||
desc: >
|
||
Octavia is an open source, operator-scale load balancing solution
|
||
designed to work with OpenStack. Octavia was borne out of the
|
||
Neutron LBaaS project, and starting with the Liberty release of
|
||
OpenStack, Octavia has become the reference implementation for
|
||
Neutron LBaaS version 2. Octavia accomplishes its delivery of
|
||
load balancing services by managing a fleet of virtual machines,
|
||
containers, or bare metal servers —collectively known as
|
||
amphorae— which it spins up on demand. This on-demand, horizontal
|
||
scaling feature differentiates Octavia from other load balancing
|
||
solutions, thereby making Octavia truly suited “for the cloud.”
|
||
project-team: octavia
|
||
since: Liberty
|
||
dependencies:
|
||
- glance
|
||
- keystone
|
||
- neutron
|
||
- nova
|
||
see-also:
|
||
- barbican
|
||
- horizon
|
||
video:
|
||
id: tlaU_-xm-14
|
||
desc: >
|
||
Project Updates cover the latest changes in the project. See
|
||
what's new in the latest OpenStack release, and what you can
|
||
expect to see from the project in the upcoming release.
|
||
title: Octavia - Project Update
|
||
|
||
- name: designate
|
||
title: DNS service
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/designate/latest/
|
||
desc: >
|
||
Designate provides DNS-as-a-service for OpenStack.
|
||
project-team: designate
|
||
since: Liberty
|
||
dependencies:
|
||
- keystone
|
||
see-also:
|
||
- nova
|
||
- neutron
|
||
video:
|
||
id: A8p6FGJwNHM
|
||
desc: >
|
||
Project Updates cover the latest changes in the project. See
|
||
what's new in the latest OpenStack release, and what you can
|
||
expect to see from the project in the upcoming release.
|
||
title: Designate - Project Update
|
||
|
||
- category: Shared services
|
||
components:
|
||
|
||
- name: keystone
|
||
title: Identity service
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/keystone/latest/
|
||
desc: >
|
||
Keystone is an OpenStack service that provides API client
|
||
authentication, service discovery, and distributed multi-tenant
|
||
authorization by implementing OpenStack’s Identity API. It
|
||
supports LDAP, OAuth, OpenID Connect, SAML and SQL.
|
||
project-team: keystone
|
||
since: Essex
|
||
|
||
- name: Placement
|
||
title: Placement service
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/placement/latest/
|
||
desc: >
|
||
Placement is an OpenStack service that provides an HTTP API for
|
||
tracking cloud resource inventories and usages to help other
|
||
services effectively manage and allocate their resources.
|
||
project-team: nova
|
||
since: Stein
|
||
|
||
- name: glance
|
||
title: Image service
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/glance/latest/
|
||
desc: >
|
||
Glance image services include discovering, registering, and
|
||
retrieving virtual machine images. Glance has a RESTful API
|
||
that allows querying of VM image metadata as well as retrieval
|
||
of the actual image. VM images made available through Glance
|
||
can be stored in a variety of locations from simple filesystems
|
||
to object-storage systems like the OpenStack Swift project.
|
||
project-team: glance
|
||
since: Bexar
|
||
dependencies:
|
||
- keystone
|
||
see-also:
|
||
- nova
|
||
- swift
|
||
video:
|
||
id: 2TW_CzQEUZ4
|
||
desc: >
|
||
Project Updates cover the latest changes in the project. See
|
||
what's new in Victoria, the latest OpenStack release, and
|
||
what you can expect to see from the project in the upcoming
|
||
release.
|
||
title: Glance Project Update - Abhishek Kekane
|
||
|
||
- name: barbican
|
||
title: Key management
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/barbican/latest/
|
||
desc: >
|
||
Barbican is the OpenStack Key Manager service. It provides secure
|
||
storage, provisioning and management of secret data, such as
|
||
passwords, encryption keys, X.509 Certificates and raw binary
|
||
data.
|
||
project-team: barbican
|
||
since: Liberty
|
||
dependencies:
|
||
- keystone
|
||
see-also:
|
||
- cinder
|
||
- nova
|
||
- octavia
|
||
|
||
- category: Orchestration
|
||
components:
|
||
|
||
- name: heat
|
||
title: Orchestration
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/heat/latest/
|
||
desc: >
|
||
Heat orchestrates the infrastructure resources for a cloud
|
||
application based on templates in the form of text files that
|
||
can be treated like code. Heat provides both an OpenStack-native
|
||
ReST API and a CloudFormation-compatible Query API. Heat also
|
||
provides an autoscaling service that integrates with the
|
||
OpenStack Telemetry services, so you can include a scaling group
|
||
as a resource in a template.
|
||
project-team: heat
|
||
since: Havana
|
||
dependencies:
|
||
- keystone
|
||
see-also:
|
||
- aodh
|
||
- barbican
|
||
- cinder
|
||
- designate
|
||
- glance
|
||
- magnum
|
||
- manila
|
||
- mistral
|
||
- neutron
|
||
- nova
|
||
- octavia
|
||
- swift
|
||
- trove
|
||
- zaqar
|
||
- zun
|
||
|
||
- name: mistral
|
||
title: Workflow service
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/mistral/latest/
|
||
desc: >
|
||
Mistral is a workflow service. Most business processes consist
|
||
of multiple distinct interconnected steps that need to be
|
||
executed in a particular order in a distributed environment.
|
||
One can describe such process as a set of tasks and task
|
||
relations (via YAML-based language) and upload such description
|
||
to Mistral so that it takes care of state management, correct
|
||
execution order, parallelism, synchronization and high
|
||
availability.
|
||
project-team: mistral
|
||
since: Liberty
|
||
dependencies:
|
||
- keystone
|
||
video:
|
||
id: lV_QPfH_PyE
|
||
desc: >
|
||
Project Updates cover the latest changes in the project. See
|
||
what's new in the latest OpenStack release, and what you can
|
||
expect to see from the project in the upcoming release.
|
||
title: Mistral - Project Update
|
||
|
||
- name: zaqar
|
||
title: Messaging Service
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/zaqar/latest/
|
||
desc: >
|
||
Zaqar is a multi-tenant cloud messaging service for web and
|
||
mobile developers. The service features a fully RESTful API,
|
||
which developers can use to send messages between various
|
||
components of their SaaS and mobile applications. Underlying
|
||
this API is an efficient messaging engine designed with
|
||
scalability and security in mind. Other OpenStack components
|
||
can integrate with Zaqar to surface events to end users and to
|
||
communicate with guest agents that run in the "over-cloud" layer.
|
||
Cloud operators can leverage Zaqar to provide equivalents of
|
||
SQS and SNS to their customers.
|
||
project-team: zaqar
|
||
since: Liberty
|
||
dependencies:
|
||
- keystone
|
||
see-also:
|
||
- horizon
|
||
- swift
|
||
video:
|
||
id: SbKtx7siiNE
|
||
desc: >
|
||
Project Updates cover the latest changes in the project. See
|
||
what's new in the latest OpenStack release, and what you can
|
||
expect to see from the project in the upcoming release.
|
||
title: Zaqar - Project Update
|
||
|
||
- name: blazar
|
||
title: Resource reservation service
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/blazar/latest/
|
||
desc: >
|
||
Blazar is a resource reservation service for OpenStack. Blazar
|
||
enables users to reserve a specific type/amount of resources for
|
||
a specific time period and it leases these resources to users
|
||
based on their reservations.
|
||
project-team: blazar
|
||
since: Queens
|
||
dependencies:
|
||
- keystone
|
||
- nova
|
||
see-also:
|
||
- neutron
|
||
|
||
- name: aodh
|
||
title: Alarming Service
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/aodh/latest/
|
||
desc: >
|
||
Aodh's goal is to enable the ability to trigger actions based
|
||
on defined rules against sample or event data collected by
|
||
Ceilometer.
|
||
project-team: Telemetry
|
||
since: Liberty
|
||
dependencies:
|
||
- keystone
|
||
see-also:
|
||
- ceilometer
|
||
- heat
|
||
|
||
- category: Workload provisioning
|
||
components:
|
||
|
||
- name: magnum
|
||
title: Container Orchestration Engine Provisioning
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/magnum/latest/
|
||
desc: >
|
||
Magnum makes container orchestration engines such as Docker
|
||
Swarm, Kubernetes, and Apache Mesos available as first class
|
||
resources in OpenStack. Magnum uses Heat to orchestrate an OS
|
||
image which contains Docker and Kubernetes and runs that image
|
||
in either virtual machines or bare metal in a cluster
|
||
configuration.
|
||
project-team: magnum
|
||
since: Mitaka
|
||
dependencies:
|
||
- keystone
|
||
- heat
|
||
- nova
|
||
- neutron
|
||
- glance
|
||
see-also:
|
||
- cinder
|
||
- octavia
|
||
- barbican
|
||
|
||
- name: trove
|
||
title: Database as a Service
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/trove/latest/
|
||
desc: >
|
||
Trove is a database-as-a-service provisioning relational and
|
||
non-relational database engines.
|
||
project-team: trove
|
||
since: Icehouse
|
||
dependencies:
|
||
- cinder
|
||
- keystone
|
||
- glance
|
||
- nova
|
||
- swift
|
||
see-also:
|
||
- designate
|
||
video:
|
||
id: I5RSL-ApwKY
|
||
desc: >
|
||
Project Updates cover the latest changes in the project. See
|
||
what's new in the latest OpenStack release, and what you can
|
||
expect to see from the project in the upcoming release.
|
||
title: Trove - Project Update
|
||
|
||
- category: Application lifecycle
|
||
components:
|
||
|
||
- name: masakari
|
||
title: Instances High Availability Service
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/masakari/latest/
|
||
desc: >
|
||
Masakari provides Instances High Availability Service for
|
||
OpenStack clouds by automatically recovering failed Instances.
|
||
Currently, Masakari can recover KVM-based Virtual Machine(VM)s
|
||
from failure events such as VM process down, provisioning process
|
||
down, and nova-compute host failure. Masakari also provides an
|
||
API service to manage and control the automated rescue mechanism.
|
||
project-team: masakari
|
||
since: Rocky
|
||
dependencies:
|
||
- keystone
|
||
- nova
|
||
video:
|
||
id: 0RJ5q4C_DqE
|
||
desc: >
|
||
Project Updates cover the latest changes in the project. See
|
||
what's new in Victoria, the latest OpenStack release, and
|
||
what you can expect to see from the project in the upcoming
|
||
release.
|
||
title: Masakari Project Update - Radosław Piliszek
|
||
|
||
- category: Web frontends
|
||
components:
|
||
|
||
- name: horizon
|
||
title: Dashboard
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/horizon/latest/
|
||
desc: >
|
||
Horizon is the canonical implementation of OpenStack's dashboard,
|
||
which is extensible and provides a web based user interface to
|
||
OpenStack services.
|
||
project-team: horizon
|
||
support-teams:
|
||
- i18n
|
||
since: Essex
|
||
dependencies:
|
||
- keystone
|
||
video:
|
||
id: IMHghWqgly4
|
||
desc: >
|
||
Project Updates cover the latest changes in the project. See
|
||
what's new in the latest OpenStack release, and what you can
|
||
expect to see from the project in the upcoming release.
|
||
title: Horizon - Project Update
|
||
|
||
- name: skyline
|
||
title: Next generation dashboard (emerging technology)
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/skyline-console/latest/
|
||
desc: >
|
||
Skyline is an OpenStack dashboard optimized by UI and UE. It has
|
||
a modern technology stack and ecology, is easier for developers
|
||
to maintain and operate by users, and has higher concurrency
|
||
performance.
|
||
project-team: skyline
|
||
since: Yoga
|
||
dependencies:
|
||
- keystone
|
||
|
||
- name: Operations tooling
|
||
prelude: >
|
||
Those services deliver APIs primarily targeted to cloud admins and
|
||
deployers, to help with cloud operations.
|
||
categories:
|
||
|
||
- category: Monitoring services
|
||
components:
|
||
|
||
- name: ceilometer
|
||
title: Metering & Data Collection Service
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/ceilometer/latest/
|
||
desc: >
|
||
Ceilometer's goal is to efficiently collect, normalise and
|
||
transform data produced by OpenStack services. The data it
|
||
collects is intended to be used to create different views
|
||
and help solve various telemetry use cases. Aodh and Gnocchi
|
||
are two examples of services extending Ceilometer data.
|
||
project-team: Telemetry
|
||
since: Havana
|
||
see-also:
|
||
- aodh
|
||
|
||
- name: venus
|
||
title: Log Management
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/venus/latest/
|
||
desc: >
|
||
Venus provides a one-stop solution to log collection, cleaning,
|
||
indexing, analysis, alarm, visualization, report generation and
|
||
other needs, which involves helping operator or maintainer to
|
||
quickly solve retrieve problems, grasp the operational health
|
||
of the platform, and improve the level of platform management.
|
||
project-team: venus
|
||
since: Zed
|
||
dependencies:
|
||
- keystone
|
||
|
||
- category: Resource optimization
|
||
components:
|
||
|
||
- name: watcher
|
||
title: Optimization Service
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/watcher/latest/
|
||
desc: >
|
||
Watcher provides a flexible and scalable resource optimization
|
||
service for multi-tenant OpenStack-based clouds. Watcher provides
|
||
a complete optimization loop—including everything from a metrics
|
||
receiver, optimization processor and an action plan applier.
|
||
project-team: watcher
|
||
since: Newton
|
||
|
||
- name: vitrage
|
||
title: Root Cause Analysis service
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/vitrage/latest/
|
||
desc: >
|
||
Vitrage is the OpenStack service for Root Cause Analysis.
|
||
It is used to organize, analyze and visualize OpenStack alarms &
|
||
events, yield insights regarding the root cause of problems and
|
||
deduce their existence before they are directly detected.
|
||
project-team: vitrage
|
||
since: Newton
|
||
see-also:
|
||
- nova
|
||
- neutron
|
||
- cinder
|
||
- heat
|
||
- aodh
|
||
- trove
|
||
video:
|
||
id: friCH35Trow
|
||
desc: >
|
||
Project Updates cover the latest changes in the project. See
|
||
what's new in the latest OpenStack release, and what you can
|
||
expect to see from the project in the upcoming release.
|
||
title: Vitrage - Project Update
|
||
|
||
- category: Billing / Business logic
|
||
components:
|
||
|
||
- name: adjutant
|
||
title: Operations processes automation
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/adjutant/latest/
|
||
desc: >
|
||
Adjutant provides an extensible API framework for exposing to
|
||
users an organization’s automated business processes relating
|
||
to account management across OpenStack and external systems,
|
||
that can be adapted to the unique requirements of an
|
||
organization’s processes.
|
||
project-team: adjutant
|
||
since: Ussuri
|
||
|
||
- name: cloudkitty
|
||
title: Billing and chargebacks
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/cloudkitty/latest/
|
||
desc: >
|
||
CloudKitty is a rating-as-a-service project designed to translate
|
||
metrics to prices. CloudKitty supports multiple collectors,
|
||
multiple rating policies and multiple outputs.
|
||
project-team: cloudkitty
|
||
since: Mitaka
|
||
|
||
- category: Testing / Benchmark
|
||
components:
|
||
|
||
- name: rally
|
||
title: Benchmarking tool
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/rally/latest/
|
||
desc: >
|
||
Rally is a benchmarking and performance analysis tool for
|
||
OpenStack that can be used to automate measuring and profiling
|
||
focused on how new code changes affect OpenStack performance,
|
||
detect scaling and performance issues, and investigate how
|
||
different deployment architectures and hardware affect OpenStack
|
||
performance. It can be used as a basic tool for an OpenStack
|
||
CI/CD system that would continuously improve its SLA, performance
|
||
and stability.
|
||
project-team: rally
|
||
|
||
- name: tempest
|
||
title: The OpenStack Integration Test Suite
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/tempest/latest/
|
||
desc: >
|
||
Tempest is a set of integration tests to be run against
|
||
a live OpenStack cluster. Tempest has batteries of tests
|
||
for OpenStack API validation, scenarios, and other specific
|
||
tests useful in validating an OpenStack deployment.
|
||
Tempest should be able to run against any OpenStack cloud,
|
||
be it a single node, a 20 node LXC cloud, or a 1000 node KVM
|
||
cloud. Tempest provides plugin capability which means any
|
||
Tempest plugin can be pluged in and and run their test along
|
||
with Tempest tests.
|
||
project-team: Quality Assurance
|
||
since: Diablo
|
||
dependencies:
|
||
- keystone
|
||
video:
|
||
id: UJf66bQBT9A
|
||
desc: >
|
||
Project Updates cover the latest changes in the project. See
|
||
what's new in the latest OpenStack release, and what you can
|
||
expect to see from the project in the upcoming release.
|
||
title: QA - Project Update
|
||
|
||
- name: Add-ons to services
|
||
prelude: >
|
||
This software runs as an add-on or plug-in into other OpenStack
|
||
services.
|
||
categories:
|
||
|
||
- category: Swift add-ons
|
||
components:
|
||
|
||
- name: storlets
|
||
title: Computable object storage
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/storlets/latest/
|
||
desc: >
|
||
Openstack Storlets is an extension to Openstack Swift with the
|
||
ability to run user defined computations - called storlets -
|
||
inside the object store in a secure and isolated manner through
|
||
the use of Docker containers. A storlet is a compiled and
|
||
packaged code (e.g. a .jar file) that can be uploaded to Swift
|
||
as any other object. Once uploaded the storlet can be invoked
|
||
over data objects in Swift.
|
||
project-team: storlets
|
||
since: Queens
|
||
dependencies:
|
||
- swift
|
||
|
||
- name: Integration enablers
|
||
prelude: >
|
||
Software in this section facilitates integration of OpenStack components
|
||
in adjacent open infrastructure stacks.
|
||
categories:
|
||
|
||
- category: Containers
|
||
components:
|
||
|
||
- name: kuryr
|
||
title: OpenStack Networking integration for containers
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/kuryr/latest/
|
||
desc: >
|
||
Bridge between containers frameworks networking models to
|
||
OpenStack networking abstraction
|
||
project-team: kuryr
|
||
dependencies:
|
||
- neutron
|
||
|
||
- category: NFV
|
||
components:
|
||
|
||
- name: tacker
|
||
title: NFV Orchestration
|
||
docs-title: Docs
|
||
docs-url: https://docs.openstack.org/tacker/latest/
|
||
desc: >
|
||
Tacker provides a generic VNF Manager (VNFM) and an NFV
|
||
Orchestrator (NFVO) to deploy and operate Network Services
|
||
and Virtual Network Functions (VNFs) on an NFV infrastructure
|
||
platform like OpenStack. It is based on ETSI MANO Architectural
|
||
Framework and provides a functional stack to Orchestrate Network
|
||
Services end-to-end using VNFs.
|
||
project-team: tacker
|
||
since: Mitaka
|