From b33e32d9adc2411d91492d9de50ee9f7476dbbf0 Mon Sep 17 00:00:00 2001 From: "OLYMPUS\\kam" Date: Fri, 27 Oct 2017 14:20:49 +0900 Subject: [PATCH 01/11] spelling --- docs/class1/module1/lab4.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/class1/module1/lab4.rst b/docs/class1/module1/lab4.rst index 85da2671..2871b655 100644 --- a/docs/class1/module1/lab4.rst +++ b/docs/class1/module1/lab4.rst @@ -185,7 +185,7 @@ Resource URI. #. Click the ``Step 6: Get Self IPs`` item in the collection. Click the ``Send`` button to GET the Self IP collection. Examine the response to - make sure both Self IPs have been created and associaited with the + make sure both Self IPs have been created and associated with the appropriate vlan. Task 4 - Create Routes From 0c958efeac5dc4f4c034e74cf1253a9af75d3dbd Mon Sep 17 00:00:00 2001 From: "OLYMPUS\\kam" Date: Fri, 27 Oct 2017 14:22:01 +0900 Subject: [PATCH 02/11] ensure this request is sent too --- docs/class1/module1/lab7.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/class1/module1/lab7.rst b/docs/class1/module1/lab7.rst index 59a35fbe..9c6d95b6 100644 --- a/docs/class1/module1/lab7.rst +++ b/docs/class1/module1/lab7.rst @@ -101,9 +101,9 @@ Task 2 - Modify a Transaction |image76| #. Click the ``Step 9: Change Eval Order 4 -> 1`` request in the folder. - Examine the request method, URI and JSON body. We will PATCH our - transaction resource and change the value of the ``evalOrder`` attribute - from ``4`` to ``1`` to move to the first position of the transaction queue: + Examine the request method, URI and JSON body then click :guilabel:`Send`. + We will PATCH our transaction resource and change the value of the ``evalOrder`` + attribute from ``4`` to ``1`` to move to the first position of the transaction queue: |image77| From 349609f52542dab2888617d2f0a4e52f69edeba6 Mon Sep 17 00:00:00 2001 From: "OLYMPUS\\kam" Date: Fri, 27 Oct 2017 14:25:01 +0900 Subject: [PATCH 03/11] style changes --- docs/class1/module1/lab7.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/class1/module1/lab7.rst b/docs/class1/module1/lab7.rst index 9c6d95b6..9979c485 100644 --- a/docs/class1/module1/lab7.rst +++ b/docs/class1/module1/lab7.rst @@ -101,7 +101,7 @@ Task 2 - Modify a Transaction |image76| #. Click the ``Step 9: Change Eval Order 4 -> 1`` request in the folder. - Examine the request method, URI and JSON body then click :guilabel:`Send`. + Examine the request method, URI, JSON body, then click :guilabel:`Send`. We will PATCH our transaction resource and change the value of the ``evalOrder`` attribute from ``4`` to ``1`` to move to the first position of the transaction queue: From b93fb6d74e74a2c37d65ba18f6fb7a0b83c3d2ef Mon Sep 17 00:00:00 2001 From: "OLYMPUS\\kam" Date: Sun, 29 Oct 2017 01:45:35 +0900 Subject: [PATCH 04/11] comma. runner button is on top left of postman window afaict --- docs/class1/module3/lab1.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/class1/module3/lab1.rst b/docs/class1/module3/lab1.rst index 7792157e..e2bccd80 100644 --- a/docs/class1/module3/lab1.rst +++ b/docs/class1/module3/lab1.rst @@ -47,8 +47,8 @@ existing BIG-IP devices from your lab environment. Tenants & Connectors ^^^^^^^^^^^^^^^^^^^^ -iWorkflow implements a Tenant/Provider interface to enable abstracted deployment -of L4-7 into various environment. In conjunction iWorkflow Connectors serve as +iWorkflow implements a Tenant/Provider interface to enable abstracted deployments +of L4-7 into various environments. In conjunction, iWorkflow Connectors serve as the L1-3 Network and Device Onboarding automation component in the automation toolchain. In this lab we will create a ‘BIG-IP Connector’ for the BIG-IP devices in the lab environment. This connector will then allow you to drive a @@ -82,7 +82,7 @@ requests contained in the ``Lab 3.1 - iWorkflow Onboarding`` folder. Perform the following steps to build the cluster: -#. Click the :guilabel:`Runner` button at the top right of your Postman window: +#. Click the :guilabel:`Runner` button at the top left of your Postman window: |image97| From 48a20d310b38ff30e278b581ca68ec78c3bf7e5d Mon Sep 17 00:00:00 2001 From: "OLYMPUS\\kam" Date: Sun, 29 Oct 2017 01:46:05 +0900 Subject: [PATCH 05/11] style updates, runner button is on top left of postman window afaict --- docs/class1/module3/lab2.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/class1/module3/lab2.rst b/docs/class1/module3/lab2.rst index d3422762..cb6ab26e 100644 --- a/docs/class1/module3/lab2.rst +++ b/docs/class1/module3/lab2.rst @@ -40,7 +40,7 @@ The templates used in this lab all have a version number appended to the name in your environment. Explicitly versioning the templates allows for migration between template versions in a stable manner. Without versioning any changes to the template could result in *every* deployment associated with the template -being modified at the same time. With versioning the application owner or F5 +being modified at the same time. With versioning, the application owner or F5 administrator can choose to either migrate all deployments at the same time OR perform the migration on a per deployment manner. @@ -51,7 +51,7 @@ In this task we will use the Runner to quickly create our sample Service Templates. Perform the following steps to complete this task: -#. Click the :guilabel:`Runner` button at the top right of your Postman window. +#. Click the :guilabel:`Runner` button at the top left of your Postman window. #. Select :menuselection:`F5 Programmability: Class 1 --> Lab 3.2 - Create a Declarative Service Catalog` folder. @@ -120,7 +120,7 @@ Perform the following steps to complete this task: |image50| - In the case of the fields shown in the example: + In the case of the fields shown in the above example: - ``pool__DefaultPoolIndex``: A value of ``0`` will be sent during a deployment @@ -182,7 +182,7 @@ Perform the following steps to complete this task: #. Finally, to assist in designing a Tenant interface, iWorkflow allows you to preview what the Tenant UI would look like for a Service Template. To view - preview for click the :guilabel:`Tenant Preview` button: + preview, click the :guilabel:`Tenant Preview` button: |image52| @@ -191,7 +191,7 @@ Perform the following steps to complete this task: :guilabel:`Tenant Editable` fields are shown. Because the true deployment details are filtered from the Tenant, the Service Deployment requires much less **Domain Specific Knowledge**. Keep in mind that while the Tenant - interface may be simple, you can leverage advanced functionality in the + interface may be simple, you can still leverage advanced functionality in the Service Template. |image53| @@ -217,7 +217,7 @@ appropriate Monitors, Profiles and Options for the use case. - HTTPS Offload and Load Balancing to a Single Pool * - ``f5-fasthttp-lb-v1.0`` - Performance-enhanced HTTP Load Balancing to a Single Pool - * - ``f5-fastl4-udp-lb-v1.0`` + * - ``f5-fastl4-tcp-lb-v1.0`` - Generic L4 TCP Load Balancing to a Single Pool * - ``f5-fastl4-udp-lb-v1.0`` - Generic L4 UDP Load Balancing to a Single Pool From 635534d4cf201e250f840d53520225e08f5d64de Mon Sep 17 00:00:00 2001 From: "OLYMPUS\\kam" Date: Sun, 29 Oct 2017 01:47:05 +0900 Subject: [PATCH 06/11] periods. fix the service template name for f5-fastl4-tcp-lb --- docs/class1/module3/lab3.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/class1/module3/lab3.rst b/docs/class1/module3/lab3.rst index 052f270e..108108fb 100644 --- a/docs/class1/module3/lab3.rst +++ b/docs/class1/module3/lab3.rst @@ -90,7 +90,7 @@ Tenant API you must authenticate with a Tenant User (``tenant`` in this case). Perform the following steps to complete this task: #. In Postman expand the ``Lab 3.3 - Deploy L4-7 Services`` folder in the - collection + collection. #. Click the ``Authenticate and Obtain Token for Tenant User`` request and examine the JSON request :guilabel:`Body`. Notice that we are sending the @@ -168,7 +168,7 @@ Perform the following steps to complete this task: |image60| -#. Click the :guilabel:`Send` button to **Update** the Service Deployment +#. Click the :guilabel:`Send` button to **Update** the Service Deployment. #. Update the iWorkflow Tenant UI and notice that the Service has been updated: @@ -189,7 +189,7 @@ Perform the following steps to complete this task: #. We will send a ``GET`` request to the Resource URI for the existing deployment. -#. Click the :guilabel:`Send` button to **Read** the Service Deployment +#. Click the :guilabel:`Send` button to **Read** the Service Deployment. #. Examine the JSON Response :guilabel:`Body` to see the state of the current Service Deployment: @@ -206,7 +206,7 @@ Perform the following steps to complete this task: #. We will send a ``DELETE`` request to the Resource URI for the existing deployment. -#. Click the :guilabel:`Send` button to **Delete** the Service Deployment +#. Click the :guilabel:`Send` button to **Delete** the Service Deployment. #. Update the iWorkflow Tenant UI and verify that the Service has been deleted: @@ -240,7 +240,7 @@ modifying the requests as needed. - HTTPS Offload and Load Balancing to a Single Pool * - ``f5-fasthttp-lb`` - Performance-enhanced HTTP Load Balancing to a Single Pool - * - ``f5-fastl4-udp-lb`` + * - ``f5-fastl4-tcp-lb`` - Generic L4 TCP Load Balancing to a Single Pool * - ``f5-fastl4-udp-lb`` - Generic L4 UDP Load Balancing to a Single Pool From 6ac3e9bc6d8291f2a2c96563bed7e60ce8f540c2 Mon Sep 17 00:00:00 2001 From: "OLYMPUS\\kam" Date: Sun, 29 Oct 2017 01:48:33 +0900 Subject: [PATCH 07/11] style changes, suggestion to improve clarity of the term "drive rich deployments", which may not be easy to understand for some --- docs/class1/module3/module3.rst | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/class1/module3/module3.rst b/docs/class1/module3/module3.rst index 88590049..87f1d267 100644 --- a/docs/class1/module3/module3.rst +++ b/docs/class1/module3/module3.rst @@ -38,8 +38,8 @@ further abstract Application Services and deliver those services, with a **Declarative** interface to Consumers. When moving to an iWorkflow based toolchain it’s important to understand -that L1-3 Automation (Device Onboarding, Networking, etc) and L4-7 -(Deployment of Virtual Servers, Pools, etc) are separated and delivered +that automation in L1-3 (Device Onboarding, Networking, etc) and L4-7 +(Deployment of Virtual Servers, Pools, etc) is separated and delivered by different features. Layer 1-3 Networking and Device Onboarding @@ -65,8 +65,8 @@ iWorkflow enables generic functionality in all of these environments by using a **BIG-IP Cloud Connector**. This connector allows iWorkflow to utilize BIG-IP devices running on any of these environments. -.. NOTE:: F5 BIG-IP also supports integration with Container Ecosystems, - however, in these environments iWorkflow may use may not be required. For +.. NOTE:: F5 BIG-IP also supports integration with Container Ecosystems. + However, in these environments iWorkflow may use may not be required. For more information you can refer to: - Container Ecosystems: @@ -84,11 +84,11 @@ Layer 4-7 Application Service Delivery L4-7 Application Service Delivery is accomplished by: -- **Declarative:** Consuming F5 iApp templates from BIG-IP devices and +- **Declarative:** Consuming F5 iApp templates on BIG-IP devices and creating a Service Catalog. - **Imperative:** Consuming the iWorkflow REST Proxy to drive API calls to - BIG-IP devices + BIG-IP devices. The labs in the module will focus on the high level features in place to achieve full L4-7 automation. As mentioned above, iApp Templates are a key @@ -96,11 +96,11 @@ component of the chain of linked tools (toolchain) we are building. In this Module we will focus on building a **Service Catalog** using the App Services iApp template you learned about in Module 2. The focus in Module 2 -was showing how to drive rich deployments, however, a large amount of F5 -**Domain Specific Knowledge** was still required to drive the deployments. -From a conceptual view iApp templates alone do not fully satisfy the requirement +was showing how to deploy advanced configurations. However, a large amount of F5 +**Domain Specific Knowledge** was still required to build each deployment. +From a conceptual point of view, iApp templates alone do not fully satisfy the requirement for a fully **Declarative** interface because while the iApp template simplifies -the underlying **Imperative** actions it does not allow the administrator to +the underlying **Imperative** actions, it does not allow the administrator to build an **Interface** that minimizes or eliminates the need for **Domain Specific Knowledge**. From 1a34e4055ab989c4d9b61312f89507d0317a1434 Mon Sep 17 00:00:00 2001 From: "OLYMPUS\\kam" Date: Sun, 29 Oct 2017 01:51:07 +0900 Subject: [PATCH 08/11] add "the" --- docs/class1/module3/lab2.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/class1/module3/lab2.rst b/docs/class1/module3/lab2.rst index cb6ab26e..3a7f1abf 100644 --- a/docs/class1/module3/lab2.rst +++ b/docs/class1/module3/lab2.rst @@ -182,7 +182,7 @@ Perform the following steps to complete this task: #. Finally, to assist in designing a Tenant interface, iWorkflow allows you to preview what the Tenant UI would look like for a Service Template. To view - preview, click the :guilabel:`Tenant Preview` button: + the preview, click the :guilabel:`Tenant Preview` button: |image52| From 0386f79cbd8230673f9d3b00470c70d8d4b754b1 Mon Sep 17 00:00:00 2001 From: "OLYMPUS\\kam" Date: Sun, 29 Oct 2017 01:54:40 +0900 Subject: [PATCH 09/11] clarify sentence --- docs/class1/module3/module3.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/class1/module3/module3.rst b/docs/class1/module3/module3.rst index 87f1d267..f76eb862 100644 --- a/docs/class1/module3/module3.rst +++ b/docs/class1/module3/module3.rst @@ -96,7 +96,7 @@ component of the chain of linked tools (toolchain) we are building. In this Module we will focus on building a **Service Catalog** using the App Services iApp template you learned about in Module 2. The focus in Module 2 -was showing how to deploy advanced configurations. However, a large amount of F5 +was to show how to deploy advanced configurations. However, a large amount of F5 **Domain Specific Knowledge** was still required to build each deployment. From a conceptual point of view, iApp templates alone do not fully satisfy the requirement for a fully **Declarative** interface because while the iApp template simplifies From 11a094dc13d814a04ad59b82c84b9630803a98d0 Mon Sep 17 00:00:00 2001 From: Hitesh Patel <0xHiteshPatel@users.noreply.github.com> Date: Sat, 28 Oct 2017 11:59:39 -0500 Subject: [PATCH 10/11] Update lab1.rst Small updates --- docs/class1/module3/lab1.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/class1/module3/lab1.rst b/docs/class1/module3/lab1.rst index e2bccd80..d0bf70c7 100644 --- a/docs/class1/module3/lab1.rst +++ b/docs/class1/module3/lab1.rst @@ -48,8 +48,8 @@ Tenants & Connectors ^^^^^^^^^^^^^^^^^^^^ iWorkflow implements a Tenant/Provider interface to enable abstracted deployments -of L4-7 into various environments. In conjunction, iWorkflow Connectors serve as -the L1-3 Network and Device Onboarding automation component in the automation +of L4-7 Services into various environments. In conjunction, iWorkflow Connectors +serve as the L1-3 Network and Device Onboarding automation component in the automation toolchain. In this lab we will create a ‘BIG-IP Connector’ for the BIG-IP devices in the lab environment. This connector will then allow you to drive a fully automated deployment from the iWorkflow Service Catalog. From c5dfe00b238df41a0ddc71a325f0ce4833d30426 Mon Sep 17 00:00:00 2001 From: Hitesh Patel <0xHiteshPatel@users.noreply.github.com> Date: Sat, 28 Oct 2017 12:02:44 -0500 Subject: [PATCH 11/11] Small updates --- docs/class1/module3/module3.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/class1/module3/module3.rst b/docs/class1/module3/module3.rst index f76eb862..d9a12af0 100644 --- a/docs/class1/module3/module3.rst +++ b/docs/class1/module3/module3.rst @@ -66,8 +66,8 @@ a **BIG-IP Cloud Connector**. This connector allows iWorkflow to utilize BIG-IP devices running on any of these environments. .. NOTE:: F5 BIG-IP also supports integration with Container Ecosystems. - However, in these environments iWorkflow may use may not be required. For - more information you can refer to: + However, in these environments iWorkflow may not be required. For more + information you can refer to: - Container Ecosystems: