Commit 021463ab authored by Dimitrios Giannopoulos's avatar Dimitrios Giannopoulos
Browse files

Deployed 1ab4add6 to develop in public with MkDocs 1.6.0 and mike 2.1.2

parent d3f4c6a5

public/develop/search/search_index.json

+1 −1

File changed.

Preview size limit exceeded, changes collapsed.

public/develop/service_design/kubernetes/helm/HELM_Installation_aaS_Jenkins_Example/index.html

+20 −19
Original line number Original line Diff line number Diff line
@@ -1893,9 +1893,9 @@ 
</li>

</li>

      

      

        <li class="md-nav__item">

        <li class="md-nav__item">

  <a href="#order-the-service" class="md-nav__link">

  <a href="#order-the-jenkins-service" class="md-nav__link">

    <span class="md-ellipsis">

    <span class="md-ellipsis">

      Order the service

      Order the Jenkins Service

    </span>

    </span>

  </a>

  </a>
@@ -2757,9 +2757,9 @@ 
</li>

</li>

      

      

        <li class="md-nav__item">

        <li class="md-nav__item">

  <a href="#order-the-service" class="md-nav__link">

  <a href="#order-the-jenkins-service" class="md-nav__link">

    <span class="md-ellipsis">

    <span class="md-ellipsis">

      Order the service

      Order the Jenkins Service

    </span>

    </span>

  </a>

  </a>
@@ -2800,13 +2800,13 @@ 
5. Assign **Application@argoproj.io/v1alpha1@kubernetes@https://10.10.10.144:6443/** as a related Resource Specification

5. Assign **Application@argoproj.io/v1alpha1@kubernetes@https://10.10.10.144:6443/** as a related Resource Specification

</code></pre>

</code></pre>

<blockquote>

<blockquote>

<p>Please note that the <em>https://10.10.10.144:6443/</em> part of the Resource Specification's name will vary in different Kubernetes installations. </p>

<p>Please note that the <em>https://10.10.10.144:6443/</em> part of the Resource Specification's name will vary in different Kubernetes environments. </p>

</blockquote>

</blockquote>

<p><img alt="img02.png" src="../img02.png" /></p>

<p><img alt="img02.png" src="../img02.png" /></p>

<p>Now, we shall focus on the Characteristics' configuration of the created Service Specification. This can be achieved from the the "Service Specification Characteristics" tab.</p>

<p>Now, we shall focus on the Characteristics' configuration of the created Service Specification. This can be achieved from the the "Service Specification Characteristics" tab.</p>

<p>Specifically, we need to map the lifecycle of ArgoCD Application (e.g. Progressing, Healthy, etc.) to TMF Resource State (e.g. reserved, active, etc.).</p>

<p>Specifically, we need to map the lifecycle of ArgoCD Application (e.g. Progressing, Healthy, etc.) to TMF Resource State (e.g. reserved, active, etc.).</p>

<p>In ArgoCD, the field <strong>status.health.status</strong> has the value that we need to check (Healty, Progressing, etc) for the lifecycle of the application. This is captured by the <strong>_CR_CHECK_FIELD</strong> characteristic.</p>

<p>In ArgoCD, the field <strong>status.health.status</strong> has the value that we need to check (Healty, Progressing, etc) for the lifecycle of the application. This is captured by the <strong>_CR_CHECK_FIELD</strong> characteristic.</p>

<p>Also, the different ArgoCD lifycycle states must be captured by the respective <strong>_CR_CHECKVAL_xxx</strong> characteristics, as show in the figure below.</p>

<p>Also, the different ArgoCD lifycycle states must be captured by the respective <strong>_CR_CHECKVAL_xxx</strong> characteristics, as show in the figure below:</p>

<p><img alt="img05.png" src="../img05.png" /></p>

<p><img alt="img05.png" src="../img05.png" /></p>

<p>After the state mapping, we must provide the template that ArgoCD will use to deploy the Jenkins HELM Chart as an ArgoCD application. For this, we must populate the <strong>_CR_SPEC</strong> characteristic. The _CR_SPEC can be designed first in a YAML or json editor for better parsing. </p>

<p>After the state mapping, we must provide the template that ArgoCD will use to deploy the Jenkins HELM Chart as an ArgoCD application. For this, we must populate the <strong>_CR_SPEC</strong> characteristic. The _CR_SPEC can be designed first in a YAML or json editor for better parsing. </p>

<p>Let's see a YAML definition:</p>

<p>Let's see a YAML definition:</p>
@@ -2862,13 +2862,14 @@ spec: 
<blockquote>

<blockquote>

<p><strong>NOTE 3</strong>: The namespace that ArgoCD will use to deploy the Jenkins HELM Chart is the "opencrdtest".</p>

<p><strong>NOTE 3</strong>: The namespace that ArgoCD will use to deploy the Jenkins HELM Chart is the "opencrdtest".</p>

</blockquote>

</blockquote>

<p><code>yaml

<pre><code class="language-yaml">destination:

 destination:

  namespace: opencrdtest

    namespace: opencrdtest</code></p>

</code></pre>

<p><strong>The latter implies that ArgoCD will always install Jenkins in the same namespace.</strong></p>

<p><strong>The latter implies that ArgoCD will always install Jenkins in the same namespace.</strong></p>

<p><strong>To avoid this we will create a simple LCM rule (pre-provision) to change the namespace accordingly with a unique ID, generated with every new Service Order.</strong></p>

<p><strong>To avoid this we will create a simple LCM rule (pre-provision) to change the namespace accordingly with a unique ID, generated with every new Service Order.</strong></p>

<p>The LCM rule can be created from the "Life Cycle Rules" tab, pressing the "Create new rule" button. The following image contains the LCM rule that needs to be created for this purpose:</p>

<p>The LCM rule can be created from the "Life Cycle Rules" tab, pressing the "Create new rule" button. The following image contains the LCM rule that needs to be created for this purpose:</p>

<p><img alt="img06.png" src="../img06.png" /></p>

<p><img alt="img06.png" src="../img06.png" /></p>

<p>Let's create it step-by-step:</p>

<ol>

<ol>

<li>Drag-Drop the _CR_SPEC block (Set characteristic value) of jenkinsrfs from the Service &gt; Text blocks</li>

<li>Drag-Drop the _CR_SPEC block (Set characteristic value) of jenkinsrfs from the Service &gt; Text blocks</li>

<li>Drag-Drop the Text &gt; Formatted text block and attach it after the block from the previous step</li>

<li>Drag-Drop the Text &gt; Formatted text block and attach it after the block from the previous step</li>
@@ -2890,11 +2891,11 @@ spec: 
</ol>

</ol>

<p><img alt="img03.png" src="../img03.png" /></p>

<p><img alt="img03.png" src="../img03.png" /></p>

<p><img alt="img04.png" src="../img04.png" /></p>

<p><img alt="img04.png" src="../img04.png" /></p>

<p>Next, expose it through an already created Service Catalog and Service Category so as to make it visible to the users, thus available for ordering.</p>

<p>Next, the designer must expose it through an already created Service Catalog and Service Category so as to make it visible to the users, thus available for ordering.</p>

<p><img alt="img061.png" src="../img061.png" /></p>

<p><img alt="img061.png" src="../img061.png" /></p>

<h2 id="order-the-service">Order the service</h2>

<h2 id="order-the-jenkins-service">Order the Jenkins Service</h2>

<p>Order the service from the assigned Service Catalog &gt; Service Category. </p>

<p>Order the service from the previously assigned Service Catalog &gt; Service Category. </p>

<p>As soon as the Service Order is in <strong>ACKNOWLEDGED</strong> state, it will be processed and eventually completed rendering the services active, as seen in the figure below:</p>

<p>As soon as the Service Order is in <strong>ACKNOWLEDGED</strong> state (may require user intervention as the initial Service Order state is "INITIAL"), it will be processed and eventually completed rendering the services active, as seen in the figure below:</p>

<p><img alt="img07.png" src="../img07.png" /></p>

<p><img alt="img07.png" src="../img07.png" /></p>

<h2 id="access-the-jenkins-installation">Access the Jenkins installation</h2>

<h2 id="access-the-jenkins-installation">Access the Jenkins installation</h2>

<p>Starting from the Service Order overview and specifically the Order Item #1 tab &gt; Supporting Services, select the ResourceFacingService (jenkinsrfs).</p>

<p>Starting from the Service Order overview and specifically the Order Item #1 tab &gt; Supporting Services, select the ResourceFacingService (jenkinsrfs).</p>