383a5bec4b
Currently for both upstream-training and training-guide directory
slides are stored in the subdirectories of landing web pages.
It is not easy to capture the directory structure and this requires
Sphinx conf file to have unnecessary excluded entries.
This commits reorganizes each directory to the following structure.
It follows the convention in the documentation project.
doc/upstream-training:
(previous)
+-- README.rst
+-- website RST files
+-- conf.py (for website)
+-- build/
+-- source/
+-- slide RST files
+-- conf.py (for slides)
+-- _assets/
+-- _static/
+-- locale/
(new)
+-- README.rst
+-- build/
+-- source/
+-- website/
| +-- website RST files
| +-- conf.py (for website)
| +-- _assets/
+-- slides/
| +-- slide RST files
| +-- conf.py (for slides)
| +-- _assets/
| +-- _static/
+-- locales/
training-guide directory is reorganized similarly.
training-guide _assets/README has been removed as it is used.
Also updates tox.ini to share target command definitions.
We do not need to have same things in many places.
Note that this commit does not change the build document paths.
Change-Id: I5a21f170c06d8f71f1f2d0df354e6d6280cb29d0
1.2 KiB
1.2 KiB
OpenStack as Software
OpenStack
- Software package that provides a cloud platform for
- Public/Private cloud
- Various use cases including Enterprise/Telecom/etc.
- Infrastructure as a Service (IaaS)
- Additional services built upon IaaS
The OpenStack Package
- Flexibility
- Core services (Compute, Networking, Block and Object Storage, etc.)
- Building Blocks: build as you need
- REST APIs
- Software Development Kits (SDKs)
- Documentation
- Packaging
- Distributions
OpenStack from Telecom/NFV perspective
- NFV = Network Function Virtualization
OpenStack from Telecom/NFV perspective
- Virtual Infrastructure Manager (VIM) + NFV Infrastructure (NFVI)
- Most of the OpenStack services
- Virtual Network Functions Manager (VNFM)
- Orchestration service
- Application Catalog service
- Workflow service