From fa96f60fb4fa1ff3f5980dbf86172428ef20ba74 Mon Sep 17 00:00:00 2001 From: Jim McCarron Date: Fri, 15 Dec 2023 09:57:34 -0500 Subject: [PATCH] api workflows --- docs/automating_rseries.rst | 2 +- docs/initial_setup_of_rseries_platform_layer.rst | 4 ++-- docs/introduction.rst | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/automating_rseries.rst b/docs/automating_rseries.rst index 843a9da..2426f18 100644 --- a/docs/automating_rseries.rst +++ b/docs/automating_rseries.rst @@ -14,7 +14,7 @@ If you want to see what API functions are available you can view the API referen The API workflows section has an index which maps to all the common API workflow examples in the rSeries planning guide. In addtion, there is an accompanying Postman collection which can be downloaded and used within your own environment if you want to become familiar with the F5OS API. -`F5 rSeries API Workflows `_ +`F5 rSeries API Workflows `_ Below is a smaple of some of the workflows available in the link above, and there are many more. diff --git a/docs/initial_setup_of_rseries_platform_layer.rst b/docs/initial_setup_of_rseries_platform_layer.rst index 90acdc3..fd5abfb 100644 --- a/docs/initial_setup_of_rseries_platform_layer.rst +++ b/docs/initial_setup_of_rseries_platform_layer.rst @@ -1471,12 +1471,12 @@ You'll get the following confirmation that the license has been installed succes Automatic Licensing via API =========================== -You can very easily apply a license automatically with the following API call. This assumes the VELOS system controllers are on the network, have internet access and DNS has been configured. This will allow the system to resolve the domain name for the F5 licensing server to apply the license. +You can very easily apply a license automatically with the following API call. This assumes the rSeries appliance is on the network, has Internet access and DNS has been configured. This will allow the system to resolve the domain name for the F5 licensing server to apply the license. .. code-block:: bash - POST https://{{velos_chassis1_system_controller_ip}}:8888/restconf/data/openconfig-system:system/f5-system-licensing:licensing/f5-system-licensing-install:install + POST https://{{rseries_appliance1_ip}}:8888/restconf/data/openconfig-system:system/f5-system-licensing:licensing/f5-system-licensing-install:install In the body of the API call add your Base Registration Key: diff --git a/docs/introduction.rst b/docs/introduction.rst index fe40fd3..f1b67de 100644 --- a/docs/introduction.rst +++ b/docs/introduction.rst @@ -18,7 +18,7 @@ A major difference between rSeries and iSeries is the introduction of a new Kube rSeries continues to provide hardware acceleration and offload capabilities in a similar way that iSeries does, however, more modern Field Programmable Gate Arrays (FPGA's), CPU, and crypto offload capabilities have been introduced. The new F5OS platform layer allows rSeries to run different types of tenants within the same appliance. As an example, rSeries will be able to run: • Existing TMOS/BIG-IP tenants (specific software releases) -• Future support for next-generation BIG-IP (BIG-IP Next) +• Support for next-generation BIG-IP (BIG-IP Next) tenants • Future possibility of running approved 3rd party tenants