Skip to content

Commit

Permalink
1
Browse files Browse the repository at this point in the history
  • Loading branch information
sorinboia committed Nov 6, 2023
1 parent 3ad37e9 commit b54cdf3
Show file tree
Hide file tree
Showing 6 changed files with 24 additions and 6 deletions.
Binary file modified docs/_build/doctrees/environment.pickle
Binary file not shown.
2 changes: 1 addition & 1 deletion docs/_build/html/genindex.html
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@
<meta name="title" content="Index"/>
<meta name="product" content="F5 XC EMEA Workshop"/>
<meta name="version" content=""/>
<meta name="updated_date" content="2023-11-06 09:40:21"/>
<meta name="updated_date" content="2023-11-06 10:06:15"/>
<meta name="archived" content="Archived documents excluded"/>
<meta name="doc_type" content="Manual"/>
<meta name="lifecycle" content="release"/>
Expand Down
2 changes: 1 addition & 1 deletion docs/_build/html/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@
<meta name="title" content="F5 Distributed Cloud EMEA Workshop"/>
<meta name="product" content="F5 XC EMEA Workshop"/>
<meta name="version" content=""/>
<meta name="updated_date" content="2023-11-06 09:40:21"/>
<meta name="updated_date" content="2023-11-06 10:06:15"/>
<meta name="archived" content="Archived documents excluded"/>
<meta name="doc_type" content="Manual"/>
<meta name="lifecycle" content="release"/>
Expand Down
2 changes: 1 addition & 1 deletion docs/_build/html/search.html
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@
<meta name="title" content="Search"/>
<meta name="product" content="F5 XC EMEA Workshop"/>
<meta name="version" content=""/>
<meta name="updated_date" content="2023-11-06 09:40:21"/>
<meta name="updated_date" content="2023-11-06 10:06:15"/>
<meta name="archived" content="Archived documents excluded"/>
<meta name="doc_type" content="Manual"/>
<meta name="lifecycle" content="release"/>
Expand Down
2 changes: 1 addition & 1 deletion docs/_build/html/searchindex.js

Large diffs are not rendered by default.

22 changes: 20 additions & 2 deletions docs/class5/module1/lab2/lab2.rst
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,9 @@ The **Customer Edge** aka. **CE** will extend the F5 Cloud infrastructure into t
* Expose the onprem applications through F5 XC without exposing the app localy to the internet

1. First we need to register the **CE**.
Go to the **UDF deployment** click **Components** on the **F5XC CE ( On prem )** component click **Access**. A drop down will open, click **Site UI**, a new tab will shell access will open.

Go to the **UDF deployment** click **Components** on the **F5XC CE ( On prem )** component click **Access**. A drop down will open, click **Site UI**, a new tab will open.

Enter the default credentials as described bellow.

.. table::
Expand All @@ -35,7 +37,7 @@ The **Customer Edge** aka. **CE** will extend the F5 Cloud infrastructure into t
========================================== ========================================================================================
**Token** 771e948b-f6ef-4338-9b50-953762f7a2a7

**Cluster name** ce-k8s-$$makeId$$
**Cluster name** $$ceOnPrem.clusterName$$

**Hostname** master

Expand All @@ -48,3 +50,19 @@ The **Customer Edge** aka. **CE** will extend the F5 Cloud infrastructure into t

3. Make sure you have logged in the F5 XC console. If you haven't yet follow the instrictions found :doc:`here <../../../intro/steps/intro3>` and then return to the guide.

We will need to approve on the F5 XC console the newly deployed **CE**.

Go to **Multi-Cloud Network Connect** -> **Site Management** -> **Registrations** .

You will see in the **Pending Registrations** multiple **CE** entries that need to be approved.

On the line respective to the **Cluster Name** **$$ceOnPrem.clusterName$$** click the **V** and after that **Save and Exit**.

This will approve and trigger the initialization of the **CE**.

4. The initialization process takes around 15 - 20 minutes.

We can observe the status by going to **Multi-Cloud Network Connect** -> **Overview** -> **Sites**.

Once the health score of **$$ceOnPrem.clusterName$$** will reach 100% the **CE** will be fully operational.

0 comments on commit b54cdf3

Please sign in to comment.