Difference between revisions of "JP-Ops-Team"
(Information sharing page for OpenStack operators (especially Japanese operators)) |
|||
Line 1: | Line 1: | ||
− | == OpenStack | + | ==OpenStack Operators Team of Japan Information Sharing Wiki== |
− | Operators Team of | ||
The purpose of this page is to share operational tips, know-hows, best practices from OpenStack operators, especially from Japan, which would help other operators or to create operator specific documents in the future. | The purpose of this page is to share operational tips, know-hows, best practices from OpenStack operators, especially from Japan, which would help other operators or to create operator specific documents in the future. | ||
Line 9: | Line 8: | ||
* a blog post | * a blog post | ||
* a wiki page | * a wiki page | ||
+ | |||
+ | Topics: | ||
+ | * Upgrade | ||
+ | * Logging/Monitoring | ||
+ | * Architecture |
Revision as of 08:17, 1 August 2017
OpenStack Operators Team of Japan Information Sharing Wiki
The purpose of this page is to share operational tips, know-hows, best practices from OpenStack operators, especially from Japan, which would help other operators or to create operator specific documents in the future. The idea came from OpsWorkshop held in OpenStack Days Tokyo 2017, where we all agreed that sharing existing documents are an easy and effective way to start collecting ops knowledge.
To start with, you can add:
- a link to your documents/slides
- a blog post
- a wiki page
Topics:
- Upgrade
- Logging/Monitoring
- Architecture