adding new best pratice metadata

Reviewed-by: Gode, Sebastian <sebastian.gode@t-systems.com>
Co-authored-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
Co-committed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>

otc_metadata/data/documents/cce-best-practice.yaml

@@ -0,0 +1,10 @@
+---
+hc_location: bestpractice/cce
+environment: internal
+html_location: docs/cce/best-practice
+link: /cloud-container-engine/best-practice/
+pdf_name: cce-best-practice
+rst_location: doc/best-practice/source
+service_type: cce
+title: Best Practice
+type: best-practice

otc_metadata/data/documents/css-best-practice.yaml

@@ -0,0 +1,10 @@
+---
+hc_location: bestpractice/css
+environment: internal
+html_location: docs/css/best-practice
+link: /cloud-search-service/best-practice/
+pdf_name: css-best-practice
+rst_location: doc/best-practice/source
+service_type: css
+title: Best Practice
+type: best-practice

otc_metadata/data/documents/dc-best-practice.yaml

@@ -0,0 +1,10 @@
+---
+hc_location: bestpractice/dc
+environment: internal
+html_location: docs/dc/best-practice
+link: /direct-connect/best-practice/
+pdf_name: dc-best-practice
+rst_location: doc/best-practice/source
+service_type: dc
+title: Best Practice
+type: best-practice

otc_metadata/data/documents/dds-best-practice.yaml

@@ -0,0 +1,10 @@
+---
+hc_location: bestpractice/dds
+environment: internal
+html_location: docs/dds/best-practice
+link: /document-database-service/best-practice/
+pdf_name: dds-best-practice
+rst_location: doc/best-practice/source
+service_type: dds
+title: Best Practice
+type: best-practice

otc_metadata/data/documents/dns-best-practice.yaml

@@ -0,0 +1,10 @@
+---
+hc_location: bestpractice/dns
+environment: internal
+html_location: docs/dns/best-practice
+link: /domain-name-service/best-practice/
+pdf_name: dns-best-practice
+rst_location: doc/best-practice/source
+service_type: dns
+title: Best Practice
+type: best-practice

otc_metadata/data/documents/elb-best-practice.yaml

@@ -0,0 +1,10 @@
+---
+hc_location: bestpractice/elb
+environment: internal
+html_location: docs/elb/best-practice
+link: /elastic-load-balancing/best-practice/
+pdf_name: elb-best-practice
+rst_location: doc/best-practice/source
+service_type: elb
+title: Best Practice
+type: best-practice

otc_metadata/data/documents/evs-best-practice.yaml

@@ -0,0 +1,10 @@
+---
+hc_location: bestpractice/evs
+environment: internal
+html_location: docs/evs/best-practice
+link: /elastic-volume-service/best-practice/
+pdf_name: evs-best-practice
+rst_location: doc/best-practice/source
+service_type: evs
+title: Best Practice
+type: best-practice

otc_metadata/data/documents/natgw-best-practice.yaml

@@ -0,0 +1,10 @@
+---
+hc_location: bestpractice/natgw
+environment: internal
+html_location: docs/natgw/best-practice
+link: /nat-gateway/best-practice/
+pdf_name: natgw-best-practice
+rst_location: doc/best-practice/source
+service_type: natgw
+title: Best Practice
+type: best-practice

otc_metadata/data/documents/swr-best-practice.yaml

@@ -0,0 +1,10 @@
+---
+hc_location: bestpractice/swr
+environment: internal
+html_location: docs/swr/best-practice
+link: /software-repository-container/best-practice/
+pdf_name: swr-best-practice
+rst_location: doc/best-practice/source
+service_type: swr
+title: Best Practice
+type: best-practice

otc_metadata/data/documents/vpc-best-practice.yaml

@@ -0,0 +1,10 @@
+---
+hc_location: bestpractice/vpc
+environment: internal
+html_location: docs/vpc/best-practice
+link: /virtual-private-cloud/best-practice/
+pdf_name: vpc-best-practice
+rst_location: doc/best-practice/source
+service_type: vpc
+title: Best Practice
+type: best-practice