Skip to content

Commit de15abf

Browse files
sayjadhasayjadha
committed
AAP-28919: Incorporated PM feedback
1 parent f189248 commit de15abf

File tree

3 files changed

+68
-34
lines changed

3 files changed

+68
-34
lines changed

‎lightspeed/modules/con_gs-develop-ansible-content.adoc‎

Lines changed: 28 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -3,25 +3,37 @@
33
[id="con-gs-develop-ansible-content_{context}"]
44
= Develop Ansible content
55

6-
As a Red Hat organization administrator, you can start a free 90-day trial of {LightspeedShortName} cloud service. Alternatively, you can set up {LightspeedShortName} cloud service or on-premise deployment.
6+
After the organization administrators have set up {LightspeedShortName}, automation developers can use the Ansible Lightspeed service to develop and use custom automation content.
77

8-
Perform one of the following tasks to set up {LightspeedShortName} for your organization:
8+
Perform the following tasks to develop Ansible content:
99

10-
[cols="25%,60%,15%",options="header"]
11-
|===
12-
|Task |Description |Persona
13-
|Start a free 90-day trial of {LightspeedShortName}
14-
|Set up a free trial of {LightspeedShortName}; this is especially useful as you do not need a trial or paid subscription to {ibmwatsonxcodeassistant}.
10+
. Install and configure the Ansible VS Code extension
11+
. Develop Ansible content
1512

16-
After your 90-day trial expires, you must set up the cloud service or on-premise deployment to continue accessing the Ansible Lightspeed service.
17-
|Organization administrator
13+
== Installing and configuring Ansible VS Code extension
14+
To access {LightspeedShortName}, all Ansible users must install and configure the Ansible VS Code extension in their VS Code editor. For the procedure, see xref:con-configure-vs-code-extension_developing-ansible-content[Install and configure the Ansible VS Code extension].
1815

19-
|Set up the cloud service
20-
|Set up a Red Hat Ansible Lightspeed cloud service and connect it to your {ibmwatsonxcodeassistant} instance.
21-
|Organization administrator
16+
== Developing Ansible content
17+
After installing and configuring the Ansible VS Code extension, automation developers can create custom Ansible content.
2218

23-
|Set up the on-premise deployment
24-
|Set up a Red Hat Ansible Lightspeed on-premise deployment and connect it to your {ibmwatsonxcodeassistant} instance.
25-
|Organization administrator
19+
You can perform the following tasks:
2620

27-
|===
21+
* Log in to the Ansible Lightspeed service as an automation developer
22+
+
23+
Once configured, you can xref:log-into-portal-auto-dev_developing-ansible-content[use the Ansible VS Code extension to access the Ansible Lightspeed service].
24+
25+
* Create single or multitask recommendations
26+
+
27+
You can xref:con-task-recommendations_developing-ansible-content[generate single-task or multitask code recommendations] for your task intent using the Ansible VS Code extension.
28+
29+
* Create an Ansible playbook and view playbook explanations
30+
+
31+
You can xref:playbook-generation_developing-ansible-content[create Ansible playbooks and view explanations for new or existing playbooks] by using the Ansible VS Code extension.
32+
33+
* Provide feedback on the Ansible Lightspeed service
34+
+
35+
You can xref:provide-feedback_developing-ansible-content[submit feedback on the quality of the code recommendations] to further improve the Ansible Lightspeed service.
36+
37+
* Log out of the Ansible Lightspeed service
38+
+
39+
To xref:logging-into-portal-auto-dev_developing-ansible-content[log out of the Ansible Lightspeed service], you must log out of both the Ansible Lightspeed VS Code extension and the Ansible Lightspeed portal.

‎lightspeed/modules/con_gs-set-up-lightspeed.adoc‎

Lines changed: 37 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -1,27 +1,47 @@
11
:_content-type: CONCEPT
22

33
[id="con-gs-set-up-lightspeed_{context}"]
4-
= Set up {LightspeedShortName}
4+
= Configuring and managing the Ansible Lightspeed service
55

6-
As a Red Hat organization administrator, you can start a free 90-day trial of {LightspeedShortName} cloud service. Alternatively, you can set up {LightspeedShortName} cloud service or on-premise deployment.
6+
As a Red Hat organization administrator, perform the following tasks to set up and manage {LightspeedShortName} for your organization:
77

8-
Perform one of the following tasks to set up {LightspeedShortName} for your organization:
8+
. Choose your deployment
9+
. Administer the Ansible Lightspeed service
910

10-
[cols="25%,60%,15%",options="header"]
11-
|===
12-
|Task |Description |Persona
13-
|Start a free 90-day trial of {LightspeedShortName}
14-
|Set up a free trial of {LightspeedShortName}; this is especially useful as you do not need a trial or paid subscription to {ibmwatsonxcodeassistant}.
11+
== Choosing your deployment
1512

16-
After your 90-day trial expires, you must set up the cloud service or on-premise deployment to continue accessing the Ansible Lightspeed service.
17-
|Organization administrator
13+
As an organization administrator, choose your deployment from the following options:
1814

19-
|Set up the cloud service
20-
|Set up a Red Hat Ansible Lightspeed cloud service and connect it to your {ibmwatsonxcodeassistant} instance.
21-
|Organization administrator
15+
* Start a free 90-day trial of Red Hat Ansible Lightspeed
16+
+
17+
This is especially useful as you do not need a trial or paid subscription to {ibmwatsonxcodeassistant}. After your 90-day trial expires, you must set up the cloud service or on-premise deployment to continue accessing the Ansible Lightspeed service.
18+
For more information, see xref:start-lightspeed-trial_lightspeed-user-guide[Starting a trial of {LightspeedShortName}].
2219

23-
|Set up the on-premise deployment
24-
|Set up a Red Hat Ansible Lightspeed on-premise deployment and connect it to your {ibmwatsonxcodeassistant} instance.
25-
|Organization administrator
20+
* Set up a Red Hat Ansible Lightspeed cloud service or on-premise deployment
21+
Configure the Red Hat Ansible Lightspeed cloud service or on-premise deployment and connect it to your IBM watsonx Code Assistant instance. You must have a trial or paid subscription to both Red Hat Ansible Automation Platform and IBM watsonx Code Assistant.
22+
For additional information, see xref:configure-lightspeed-cloud-service_set-up-lightspeed[Setting up the cloud service] and xref:configuring-lightspeed-onpremise_set-up-lightspeed[Setting up an on-premise deployment].
2623

27-
|===
24+
== Managing the Ansible Lightspeed Service
25+
As an organization administrator, you can manage the Ansible Lightspeed service after you have deployed the {LightspeedShortName} cloud service or on-premise deployment for your organization.
26+
27+
You can perform the following tasks:
28+
29+
* Log in to the Ansible Lightspeed admin portal
30+
+
31+
Use the Ansible Lightspeed admin portal to xref:log-in-administrator-portal_administering-ansible-lightspeed[access and manage the Ansible Lightspeed service].
32+
33+
* View the Admin dashboard telemetry data
34+
+
35+
xref:view-manage-admin-dashboard-telemetry_administering-ansible-lightspeed[View the operational telemetry and Admin dashboard telemetry data] from the Ansible Lightspeed Admin dashboard.
36+
37+
* Disable the Admin dashboard telemetry
38+
+
39+
If you no longer want to collect the telemetry data for your organization, you can xref:disable-admin-dashboard-telemetry_administering-ansible-lightspeed[disable the Admin dashboard telemetry].
40+
41+
* Configure custom models for your organization
42+
+
43+
xref:configure-custom-models_administering-ansible-lightspeed[Create and use fine-tuned, custom models] that are trained on your organization's existing Ansible content.
44+
45+
* Log out of the Ansible Lightspeed service
46+
+
47+
To log out of the Ansible Lightspeed service, you must xref:log-out-of-portal_administering-ansible-lightspeed[log out of both the Ansible Lightspeed VS Code extension and the Ansible Lightspeed portal].

‎lightspeed/modules/con_gs-system-requirements.adoc‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,9 @@
11
:_content-type: CONCEPT
22

33
[id="con-gs-system-requirements_{context}"]
4-
= Evaluate the system requirements
4+
= Licensing requirements
5+
6+
Check the licensing requirements for your {LightspeedShortName} deployment.
57

68
[discrete]
79
== Trial account

0 commit comments

Comments
 (0)