Compare commits

...

13 Commits

Author SHA1 Message Date
Kyriakos Akriotis
e1bb544225 fix internal url for keycloak/github 2024-02-05 07:01:56 +01:00
Kyriakos Akriotis
38555f5653 - finalize keycloak/github blueprint 2024-02-02 08:45:21 +01:00
Kyriakos Akriotis
c4ae24d28a - added keycloak/github extra depths in chapters 2024-02-01 14:27:08 +01:00
Kyriakos Akriotis
5fd8051bca - added keycloak/github assets 2023-12-12 17:47:01 +01:00
Kyriakos Akriotis
6944ae18cd - added keycloak/github integration draft 2023-12-12 17:46:13 +01:00
Kyriakos Akriotis
5a756dbeff - added overview 2023-12-12 11:56:21 +01:00
Kyriakos Akriotis
b46ef02fab - added meta information 2023-12-12 11:40:04 +01:00
Kyriakos Akriotis
53febe8358 - deploy keycloak draft + assets 2023-12-12 11:38:16 +01:00
Kyriakos Akriotis
5490932cf5 - deploy keycloak draft 2023-12-12 11:36:52 +01:00
Kyriakos Akriotis
3cb7057891 - remove .vscode folder 2023-11-23 16:49:30 +01:00
Kyriakos Akriotis
06282c636d - added categories structure and summaries 2023-11-23 14:54:18 +01:00
b482777f06 - best practices scaffold 2023-07-24 14:10:12 +02:00
3cfed3b83d - templates & test commit 2023-07-24 12:58:24 +02:00
60 changed files with 1858 additions and 7 deletions

Binary file not shown.

After

Width:  |  Height:  |  Size: 111 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 154 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 134 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 188 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 180 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 91 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 220 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 160 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 246 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 222 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 236 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 180 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 166 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 216 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 177 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 216 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 160 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 123 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 116 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 230 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 186 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 84 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 200 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 87 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 141 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 320 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 185 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 104 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 97 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 363 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 255 KiB

File diff suppressed because it is too large Load Diff

View File

@ -0,0 +1,85 @@
. meta::
:description: add a SEO description here
:keywords: add SEO keywords here, and list additionally all OTC services used
==================
Article (Internal)
==================
.. Introduction
Introduction
============
| > *There are no further requirements for an article except to include the following sections at the **end**, and to follow all general Open Telekom Architecture Center content requirements.*
| > *An Open Telekom Cloud Architecture Center article template, for **external** creators, requires the following sections at the end of the article:*
.. topic:: TL;DR
| >> Make a brief summary of what is the article about
.. Main Article
.. Components
| > *No header required here*
| > *(Expected to list all the Open Telekom Cloud components used, but it could be optional if it just an architectural paradigm.*
.. Sections 1..n
| > *You can name the Section titles as it seems fit to the workflow of the article.*
Section 1
=========
Section 2
=========
Section n
=========
.. Next steps & Related Resources
Next Steps
==========
| > *(Expected, but it could be optional if you don't want the article stops here and doesn't connect with other resources)*
| > *Add site-relative links to Architecture Center related articles but NOT to external or third-party resources*
| > *If there are additional resources like Cloud Topology Designer solution or Github repos, list them first with the aforementioned order*
.. seealso::
`Link1 <https://www.t-systems.com>`_
`Link2 <https://www.t-systems.com>`_
Resources
=========
.. Resources
| > *If there are additional deployable resources like Cloud Topology Designer solution or Github repos, list them first with the aformentioned order*
.. seealso::
`Link1 <https://www.t-systems.com>`_
`Link2 <https://www.t-systems.com>`_
.. References
References
==========
| > *Add site-relative links to Architecture Center articles*
| > *Add links to external or third-party resources*
.. seealso::
`Link1 <https://www.t-systems.com>`_
`Link2 <https://www.t-systems.com>`_
| > **REMOVE ALL THE LINES THAT START WITH "| >"**

File diff suppressed because it is too large Load Diff

View File

@ -0,0 +1,14 @@
Computing
=========
The Computing section offers essential insights for optimizing computing resources. Discover guidelines for selecting
appropriate instance types, managing virtual machines efficiently, and leveraging auto-scaling capabilities for dynamic
workloads. Learn best practices for designing resilient and high-performance computing architectures, ensuring optimal
utilization of resources while maintaining cost-effectiveness. This section serves as a comprehensive guide for architects
and developers to fine-tune their computing strategies, enhancing the overall efficiency and reliability of applications
in the Open Telekom Cloud environment.
.. toctree::
:maxdepth: 1

View File

@ -0,0 +1,14 @@
Data Analytics
==============
This section provides strategic guidance for optimizing data processing workflows. Explore recommendations for selecting
and configuring data analytics services, ensuring efficient and scalable processing of large datasets. Learn about best
practices for data storage, retrieval, and integration to enhance overall analytics performance. This section is a
valuable resource for architects and data professionals, offering insights into designing robust and cost-effective data
analytics architectures within the Open Telekom Cloud, fostering informed decision-making and actionable insights.
.. toctree::
:maxdepth: 1

View File

@ -0,0 +1,20 @@
Best Practices
==============
Welcome to the Best Practices section of Open Telekom Cloud's Architecture Center.
Here we provides crucial guidelines for optimizing cloud-based solutions.
Best Practices emphasize architectural principles that enhance reliability, scalability, and security.
Explore our recommended strategies for resource management, such as efficient utilization of compute
and storage resources. Gain insights into designing for high availability and fault tolerance
to ensure robust system performance. This section serves as a valuable resource for architects and developers
to implement cloud solutions that align with industry best practices and maximize the benefits of the public cloud
infrastructure.
.. toctree::
:maxdepth: 1
computing/index.rst
data-analytics/index.rst
network/index.rst
security/index.rst
storage/index.rst

View File

@ -0,0 +1,15 @@
Network
=======
Network Best Practices outline key strategies for optimizing network configurations. Explore guidelines for designing
resilient and high-performance network architectures, including considerations for security and scalability.
Learn about best practices for leveraging Virtual Private Clouds (VPCs), network segmentation, and load balancing to
enhance overall network efficiency. This section serves as a valuable resource for architects and network administrators,
providing insights into building robust and secure network infrastructures within the Open Telekom Cloud environment,
ensuring reliable and seamless connectivity for applications and services.
.. toctree::
:maxdepth: 1

View File

@ -30,9 +30,6 @@ internal credentials.
Overview
========
.. graphviz:: dot/cce_vault_overview.dot
:layout: dot
TLS secrets are kept in the Vault. They are being read by Vault Agent component
running as a sidecar in Zookeeper service pod and writes certificates onto the
file system. Zookeeper services reads certificates populated by Agent. Vault

File diff suppressed because it is too large Load Diff

View File

@ -0,0 +1,18 @@
Security
========
The Security Best Practices offer comprehensive guidance on fortifying cloud environments. Explore recommendations for
implementing robust identity and access management, encryption protocols, and network security measures. Learn about
best practices for securing data at rest and in transit, as well as strategies for monitoring and responding to
security incidents. This section is a crucial resource for architects and cybersecurity professionals, providing
insights into designing and maintaining resilient security postures within the Open Telekom Cloud, ensuring the
confidentiality, integrity, and availability of sensitive information.
.. toctree::
:maxdepth: 1
cce_vault.rst
deploy_keycloak.rst
keycloak_github.rst

File diff suppressed because it is too large Load Diff

View File

@ -0,0 +1,12 @@
Storage
=======
Storage Best Practices offer key insights into optimizing storage solutions. Explore guidelines for selecting
appropriate storage types, managing data lifecycle, and implementing redundancy for enhanced durability. Learn about
best practices for achieving optimal performance and cost-effectiveness in storage configurations. This section is a
valuable resource for architects and storage administrators, providing essential strategies to design resilient and
scalable storage architectures within the Open Telekom Cloud environment, ensuring efficient data management and retrieval.
.. toctree::
:maxdepth: 1

View File

@ -9,6 +9,7 @@
extensions = [
'sphinx.ext.graphviz',
'otcdocstheme',
# 'sphinx.ext.intersphinx',
]
# openstackdocstheme options

View File

@ -1,8 +1,8 @@
Blueprints
==========
Architecture Center
===================
Users sometimes identify use cases that can be solved in a standardized way to
save research time and effort. Blueprints are a series of best practices,
save research time and effort. Architecture Center offers a collection of series of best practices,
curated by the Open Telekom Cloud engineering and architecture teams. While
they are not covered directly by the `Service description
<https://open-telekom-cloud.com/service-description>`_, they are tested and
@ -12,4 +12,6 @@ validated recommendations from our experts.
.. toctree::
:maxdepth: 1
cce_vault.rst
best-practices/index.rst
use-cases/index.rst
industry/index.rst

View File

@ -0,0 +1,12 @@
Automotive
==========
The Automotive section showcases tailored solutions for the automotive sector. Explore practical examples demonstrating
how the platform supports the industry's unique requirements, from connected car technologies to manufacturing
processes. This section provides architects with insights into designing scalable and secure cloud architectures to
enhance innovation and efficiency in the automotive domain. Discover recommended best practices, empowering users to
leverage Open Telekom Cloud for optimized performance and transformative capabilities within the automotive industry's
dynamic landscape.
.. toctree::
:maxdepth: 1

View File

@ -0,0 +1,12 @@
Education
=========
The Education section highlights tailored cloud solutions for the education sector. Explore practical examples
showcasing how the platform supports e-learning applications, research initiatives, and administrative processes.
This section provides architects with insights into designing scalable and cost-effective cloud architectures to meet
the diverse needs of educational institutions. Discover recommended best practices, empowering users to leverage
Open Telekom Cloud for enhanced collaboration, resource efficiency, and innovation within the dynamic landscape of the
education industry.
.. toctree::
:maxdepth: 1

View File

@ -0,0 +1,11 @@
Finance
=======
The Finance section offers targeted cloud solutions for the financial sector. Explore practical examples demonstrating
how the platform supports secure and compliant financial applications, from digital banking to risk management. This
section provides architects with insights into designing robust, scalable, and regulatory-compliant cloud architectures
tailored to financial industry requirements. Discover recommended best practices, empowering users to leverage
Open Telekom Cloud for optimized performance, security, and innovation within the dynamic landscape of the financial sector.
.. toctree::
:maxdepth: 1

View File

@ -0,0 +1,10 @@
Government
==========
The Government section focuses on tailored cloud solutions for the public sector. Explore practical examples showcasing
how the platform supports secure and compliant government applications, from citizen services to data management. This
section provides architects with insights into designing resilient, scalable, and regulatory-compliant cloud
architectures tailored to governmental requirements.
.. toctree::
:maxdepth: 1

View File

@ -0,0 +1,11 @@
Healthcare
==========
The Healthcare section showcases specialized cloud solutions for the healthcare sector. Explore practical examples
illustrating how the platform supports secure and compliant healthcare applications, from electronic health records to
medical research. This section provides architects with insights into designing robust, scalable, and
regulatory-compliant cloud architectures tailored to the unique needs of the healthcare industry.
.. toctree::
:maxdepth: 1

Some files were not shown because too many files have changed in this diff Show More