summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThierry Carrez <thierry@openstack.org>2018-08-09 14:55:52 +0200
committerThierry Carrez <thierry@openstack.org>2018-08-09 14:55:52 +0200
commite0567c8f8c2d7ba4d7915ea30c9cefa8b8526ba2 (patch)
tree3c281038abe0dc4b8d0fa96f8267b357a8497867
parent222ff497eacfc52c2133040a5899eaa0555ae4c7 (diff)
Complete OpenStack components tab
Include all components.
-rw-r--r--openstack_components.yaml291
1 files changed, 254 insertions, 37 deletions
diff --git a/openstack_components.yaml b/openstack_components.yaml
index a342780..0d10837 100644
--- a/openstack_components.yaml
+++ b/openstack_components.yaml
@@ -5,7 +5,10 @@ tabs:
5 - name: OpenStack services 5 - name: OpenStack services
6 map-bucket: openstack 6 map-bucket: openstack
7 prelude: > 7 prelude: >
8 Those services deliver APIs targeted to cloud end users. 8 An OpenStack deployment contains a number of components providing
9 APIs to access infrastructure resources. This page lists the various
10 services that can be deployed to provide such resources to cloud
11 end users.
9 categories: 12 categories:
10 13
11 - category: Compute 14 - category: Compute
@@ -20,9 +23,9 @@ tabs:
20 containers. 23 containers.
21 project-team: nova 24 project-team: nova
22 dependencies: 25 dependencies:
23 - keystone
24 - cinder 26 - cinder
25 - neutron 27 - neutron
28 - glance
26 see-also: 29 see-also:
27 - ironic 30 - ironic
28 31
@@ -39,8 +42,14 @@ tabs:
39 the need to explore the complexities of different container 42 the need to explore the complexities of different container
40 technologies. 43 technologies.
41 project-team: zun 44 project-team: zun
42 dependencies: 45
43 - keystone 46 - name: qinling
47 title: Functions Service
48 desc: >
49 Qinling provides a platform to support serverless functions
50 (like AWS Lambda).
51 project-team: qinling
52 since: rocky
44 53
45 - category: Bare metal 54 - category: Bare metal
46 components: 55 components:
@@ -53,12 +62,38 @@ tabs:
53 resources, including bare metal, virtual machines, and 62 resources, including bare metal, virtual machines, and
54 containers. 63 containers.
55 project-team: ironic 64 project-team: ironic
65 dependencies:
66 - glance
56 see-also: 67 see-also:
57 - nova 68 - nova
58 69
70 - name: cyborg
71 title: Accelerators resource management
72 desc: >
73 Cyborg provides a general purpose management framework for
74 acceleration resources (i.e. various types of accelerators such
75 as GPU, FPGA, ASIC, NP, SoCs, NVMe/NOF SSDs, ODP, DPDK/SPDK and
76 so on).
77 project-team: cyborg
78 dependencies:
79 - nova
80
59 - category: Storage 81 - category: Storage
60 components: 82 components:
61 83
84 - name: swift
85 title: Object store
86 desc: >
87 Swift is a highly available, distributed, eventually consistent
88 object/blob store. Organizations can use Swift to store lots of
89 data efficiently, safely, and cheaply. It's built for scale and
90 optimized for durability, availability, and concurrency across
91 the entire data set. Swift is ideal for storing unstructured
92 data that can grow without bound.
93 project-team: swift
94 see-also:
95 - storlets
96
62 - name: cinder 97 - name: cinder
63 title: Block Storage 98 title: Block Storage
64 desc: > 99 desc: >
@@ -70,11 +105,16 @@ tabs:
70 the use of either a reference implementation (LVM) or plugin 105 the use of either a reference implementation (LVM) or plugin
71 drivers for other storage. 106 drivers for other storage.
72 project-team: cinder 107 project-team: cinder
73 dependencies:
74 - keystone
75 see-also: 108 see-also:
76 - nova 109 - nova
77 110
111 - name: manila
112 title: Shared filesystems
113 desc: >
114 Manila provides coordinated access to shared or distributed file
115 systems.
116 project-team: manila
117
78 - category: Networking 118 - category: Networking
79 components: 119 components:
80 120
@@ -85,12 +125,31 @@ tabs:
85 delivering networking-as-a-service (NaaS) in virtual compute 125 delivering networking-as-a-service (NaaS) in virtual compute
86 environments. 126 environments.
87 project-team: neutron 127 project-team: neutron
88 dependencies:
89 - keystone
90 see-also: 128 see-also:
91 - nova 129 - nova
92 130
93 - category: Common services 131 - name: octavia
132 title: Load balancer
133 desc: >
134 Octavia is an open source, operator-scale load balancing solution
135 designed to work with OpenStack. Octavia was borne out of the
136 Neutron LBaaS project, and starting with the Liberty release of
137 OpenStack, Octavia has become the reference implementation for
138 Neutron LBaaS version 2. Octavia accomplishes its delivery of
139 load balancing services by managing a fleet of virtual machines,
140 containers, or bare metal servers —collectively known as
141 amphorae— which it spins up on demand. This on-demand, horizontal
142 scaling feature differentiates Octavia from other load balancing
143 solutions, thereby making Octavia truly suited “for the cloud.”
144 project-team: octavia
145
146 - name: designate
147 title: DNS service
148 desc: >
149 Designate provides DNS-as-a-service for OpenStack.
150 project-team: designate
151
152 - category: Shared services
94 components: 153 components:
95 154
96 - name: keystone 155 - name: keystone
@@ -102,6 +161,53 @@ tabs:
102 supports LDAP, OAuth, OpenID Connect, SAML and SQL. 161 supports LDAP, OAuth, OpenID Connect, SAML and SQL.
103 project-team: keystone 162 project-team: keystone
104 163
164 - name: glance
165 title: Image service
166 desc: >
167 Glance image services include discovering, registering, and
168 retrieving virtual machine images. Glance has a RESTful API
169 that allows querying of VM image metadata as well as retrieval
170 of the actual image. VM images made available through Glance
171 can be stored in a variety of locations from simple filesystems
172 to object-storage systems like the OpenStack Swift project.
173 project-team: glance
174 see-also:
175 - nova
176 - swift
177
178 - name: barbican
179 title: Key management
180 desc: >
181 Barbican is the OpenStack Key Manager service. It provides secure
182 storage, provisioning and management of secret data, such as
183 passwords, encryption keys, X.509 Certificates and raw binary
184 data.
185 project-team: barbican
186
187 - name: karbor
188 title: Application Data Protection as a Service
189 desc: >
190 Karbor deals with protecting the Data and Meta-Data that
191 comprises an OpenStack-deployed application against loss/damage
192 (e.g. backup, replication) - not to be confused with Application
193 Security or DLP. It does that by providing a standard framework
194 of APIs and services that enables vendors to introduce various
195 data protection services into a coherent and unified flow for
196 the user.
197 project-team: karbor
198
199 - name: searchlight
200 title: Indexing and Search
201 desc: >
202 The Searchlight project provides indexing and search capabilities
203 across OpenStack resources. Its goal is to achieve high
204 performance and flexible querying combined with near real-time
205 indexing. It uses Elasticsearch, a real-time distributed indexing
206 and search engine built on Apache Lucene, but adds OpenStack
207 authentication and Role Based Access Control to provide
208 appropriate protection of data.
209 project-team: searchlight
210
105 - category: Orchestration 211 - category: Orchestration
106 components: 212 components:
107 213
@@ -116,8 +222,60 @@ tabs:
116 OpenStack Telemetry services, so you can include a scaling group 222 OpenStack Telemetry services, so you can include a scaling group
117 as a resource in a template. 223 as a resource in a template.
118 project-team: heat 224 project-team: heat
119 dependencies: 225
120 - keystone 226 - name: senlin
227 title: Clustering service
228 desc: >
229 Senlin is a clustering service for OpenStack clouds. It creates
230 and operates clusters of homogeneous objects exposed by other
231 OpenStack services. The goal is to make orchestration of
232 collections of similar objects easier.
233 project-team: senlin
234
235 - name: mistral
236 title: Workflow service
237 desc: >
238 Mistral is a workflow service. Most business processes consist
239 of multiple distinct interconnected steps that need to be
240 executed in a particular order in a distributed environment.
241 One can describe such process as a set of tasks and task
242 relations (via YAML-based language) and upload such description
243 to Mistral so that it takes care of state management, correct
244 execution order, parallelism, synchronization and high
245 availability.
246 project-team: mistral
247
248 - name: zaqar
249 title: Messaging Service
250 desc: >
251 Zaqar is a multi-tenant cloud messaging service for web and
252 mobile developers. The service features a fully RESTful API,
253 which developers can use to send messages between various
254 components of their SaaS and mobile applications. Underlying
255 this API is an efficient messaging engine designed with
256 scalability and security in mind. Other OpenStack components
257 can integrate with Zaqar to surface events to end users and to
258 communicate with guest agents that run in the "over-cloud" layer.
259 Cloud operators can leverage Zaqar to provide equivalents of
260 SQS and SNS to their customers.
261 project-team: zaqar
262
263 - name: blazar
264 title: Resource reservation service
265 desc: >
266 Blazar is a resource reservation service for OpenStack. Blazar
267 enables users to reserve a specific type/amount of resources for
268 a specific time period and it leases these resources to users
269 based on their reservations.
270 project-team: blazar
271
272 - name: aodh
273 title: Alarming Service
274 desc: >
275 Aodh's goal is to enable the ability to trigger actions based
276 on defined rules against sample or event data collected by
277 Ceilometer.
278 project-team: Telemetry
121 279
122 - category: Workload provisioning 280 - category: Workload provisioning
123 components: 281 components:
@@ -134,7 +292,23 @@ tabs:
134 project-team: magnum 292 project-team: magnum
135 dependencies: 293 dependencies:
136 - heat 294 - heat
137 - keystone 295
296 - name: sahara
297 title: Big Data Processing Framework Provisioning
298 desc: >
299 The sahara project aims to provide users with a simple means
300 to provision data processing frameworks (such as Hadoop, Spark
301 and Storm) on OpenStack. This is accomplished by specifying
302 configuration parameters such as the framework version, cluster
303 topology, node hardware details and more.
304 project-team: sahara
305
306 - name: trove
307 title: Database as a Service
308 desc: >
309 Trove is a database-as-a-service provisioning relational and
310 non-relational database engines.
311 project-team: trove
138 312
139 - category: Application lifecycle 313 - category: Application lifecycle
140 components: 314 components:
@@ -149,8 +323,40 @@ tabs:
149 down, and nova-compute host failure. Masakari also provides an 323 down, and nova-compute host failure. Masakari also provides an
150 API service to manage and control the automated rescue mechanism. 324 API service to manage and control the automated rescue mechanism.
151 project-team: masakari 325 project-team: masakari
326
327 - name: murano
328 title: Application Catalog
329 desc: >
330 Murano enables application developers and cloud administrators
331 to publish various cloud-ready applications in a browsable
332 catalog. Cloud users -- including inexperienced ones -- can then
333 use the catalog to compose reliable application environments
334 with the push of a button. Murano uses OpenStack Heat to
335 orchestrate infrastructure resources for the application.
336 project-team: murano
152 dependencies: 337 dependencies:
153 - keystone 338 - heat
339
340 - name: solum
341 title: Software Development Lifecycle Automation
342 desc: >
343 To make cloud services easier to consume and integrate with
344 your application development process by automating the
345 source-to-image process, and simplifying app-centric deployment.
346 project-team: solum
347
348 - name: freezer
349 title: Backup, Restore, and Disaster Recovery
350 desc: >
351 Freezer is a distributed backup, restore and disaster recovery
352 as a service platform. It is designed to be multi OS (Linux,
353 Windows, OSX...), focused on providing efficiency and flexibility
354 for block based backups, file based incremental backups,
355 point-in-time actions, jobs synchronization (i.e. backup
356 synchronization over multiple nodes) and many other features.
357 It is aimed at being useful for all environments, including
358 large ephemeral Clouds.
359 project-team: freezer
154 360
155 - category: API proxies 361 - category: API proxies
156 components: 362 components:
@@ -173,8 +379,6 @@ tabs:
173 which is extensible and provides a web based user interface to 379 which is extensible and provides a web based user interface to
174 OpenStack services. 380 OpenStack services.
175 project-team: horizon 381 project-team: horizon
176 dependencies:
177 - keystone
178 382
179 - name: Operations services 383 - name: Operations services
180 map-bucket: openstack-operations 384 map-bucket: openstack-operations
@@ -194,9 +398,7 @@ tabs:
194 collects is intended to be used to create different views 398 collects is intended to be used to create different views
195 and help solve various telemetry use cases. Aodh and Gnocchi 399 and help solve various telemetry use cases. Aodh and Gnocchi
196 are two examples of services extending Ceilometer data. 400 are two examples of services extending Ceilometer data.
197 project-team: telemetry 401 project-team: Telemetry
198 dependencies:
199 - keystone
200 see-also: 402 see-also:
201 - aodh 403 - aodh
202 404
@@ -208,9 +410,7 @@ tabs:
208 OpenStack resources at a given time. Its aim is to enable a 410 OpenStack resources at a given time. Its aim is to enable a
209 scalable means of storing both short and long term data for use 411 scalable means of storing both short and long term data for use
210 cases such as auditing and system debugging. 412 cases such as auditing and system debugging.
211 project-team: telemetry 413 project-team: Telemetry
212 dependencies:
213 - keystone
214 414
215 - name: monasca 415 - name: monasca
216 title: Monitoring 416 title: Monitoring
@@ -221,8 +421,6 @@ tabs:
221 metrics processing and querying and has a streaming alarm engine 421 metrics processing and querying and has a streaming alarm engine
222 and notification engine. 422 and notification engine.
223 project-team: monasca 423 project-team: monasca
224 dependencies:
225 - keystone
226 424
227 - category: Optimization/policy tools 425 - category: Optimization/policy tools
228 components: 426 components:
@@ -235,8 +433,36 @@ tabs:
235 a complete optimization loop—including everything from a metrics 433 a complete optimization loop—including everything from a metrics
236 receiver, optimization processor and an action plan applier. 434 receiver, optimization processor and an action plan applier.
237 project-team: watcher 435 project-team: watcher
238 dependencies: 436
239 - keystone 437 - name: vitrage
438 title: RCA (Root Cause Analysis service)
439 desc: >
440 Vitrage is the OpenStack RCA (Root Cause Analysis) service for
441 organizing, analyzing and expanding OpenStack alarms & events,
442 yielding insights regarding the root cause of problems and
443 deducing their existence before they are directly detected.
444 project-team: vitrage
445
446 - name: congress
447 title: Governance
448 desc: >
449 Congress is an OpenStack project to provide policy as a service
450 across any collection of cloud services in order to offer
451 governance and compliance for dynamic infrastructures.
452 project-team: congress
453
454 - name: rally
455 title: Benchmark service
456 desc: >
457 Rally is a benchmarking and performance analysis tool for
458 OpenStack that can be used to automate measuring and profiling
459 focused on how new code changes affect OpenStack performance,
460 detect scaling and performance issues, and investigate how
461 different deployment architectures and hardware affect OpenStack
462 performance. It can be used as a basic tool for an OpenStack
463 CI/CD system that would continuously improve its SLA, performance
464 and stability.
465 project-team: rally
240 466
241 - category: Billing / Business logic 467 - category: Billing / Business logic
242 components: 468 components:
@@ -247,8 +473,6 @@ tabs:
247 CloudKitty is a rating-as-a-service project designed to translate 473 CloudKitty is a rating-as-a-service project designed to translate
248 metrics to prices. CloudKitty supports multiple collectors, 474 metrics to prices. CloudKitty supports multiple collectors,
249 multiple rating policies and multiple outputs. 475 multiple rating policies and multiple outputs.
250 dependencies:
251 - keystone
252 476
253 - category: Multi-region tools 477 - category: Multi-region tools
254 components: 478 components:
@@ -261,8 +485,6 @@ tabs:
261 high availability, dual ISPs for internet link redundancy, 485 high availability, dual ISPs for internet link redundancy,
262 east-west traffic isolation, cross Nuetron L2 network for NFV, 486 east-west traffic isolation, cross Nuetron L2 network for NFV,
263 and cloud capacity expansion. 487 and cloud capacity expansion.
264 dependencies:
265 - neutron
266 488
267 - name: Add-ons to services 489 - name: Add-ons to services
268 prelude: > 490 prelude: >
@@ -286,7 +508,6 @@ tabs:
286 project-team: storlets 508 project-team: storlets
287 dependencies: 509 dependencies:
288 - swift 510 - swift
289 - keystone
290 511
291 - category: Neutron plug-ins 512 - category: Neutron plug-ins
292 components: 513 components:
@@ -302,8 +523,8 @@ tabs:
302 523
303 - name: Bridges for adjacent tech 524 - name: Bridges for adjacent tech
304 prelude: > 525 prelude: >
305 This software lets other open infrastructure stacks leverage OpenStack 526 Software in this section facilitates integration of OpenStack components
306 components. 527 in adjacent open infrastructure stacks.
307 categories: 528 categories:
308 529
309 - category: Containers 530 - category: Containers
@@ -328,9 +549,8 @@ tabs:
328 persistence storage provider for virtual machine, baremetal 549 persistence storage provider for virtual machine, baremetal
329 and Docker container. 550 and Docker container.
330 project-team: fuxi 551 project-team: fuxi
331 dependencies:
332 - cinder
333 see-also: 552 see-also:
553 - cinder
334 - manila 554 - manila
335 555
336 - category: NFV 556 - category: NFV
@@ -346,6 +566,3 @@ tabs:
346 Framework and provides a functional stack to Orchestrate Network 566 Framework and provides a functional stack to Orchestrate Network
347 Services end-to-end using VNFs. 567 Services end-to-end using VNFs.
348 project-team: tacker 568 project-team: tacker
349 dependencies:
350 - nova
351 - neutron