Skip to content

Commit 805eb91

Browse files
AkshayGadhaveRHAkshayGadhaveRH
authored
Update Google Compute Engine branding (theforeman#4496)
Replacing `Google GCE` with `GCE`, since `GCE` is an abbreviation of `Google Compute Engine`. JIRA: https://issues.redhat.com/browse/SAT-39786
1 parent 27d0afb commit 805eb91

6 files changed

+30
-30
lines changed

‎guides/common/assembly_provisioning-cloud-instances-gce.adoc‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,18 +8,18 @@
88
include::modules/con_provisioning-cloud-instances-on-google-compute-engine.adoc[]
99

1010
ifndef::satellite[]
11-
include::modules/proc_installing-google-gce-plugin.adoc[leveloffset=+1]
11+
include::modules/proc_installing-gce-plugin.adoc[leveloffset=+1]
1212
endif::[]
1313

14-
include::modules/proc_adding-a-google-gce-connection.adoc[leveloffset=+1]
14+
include::modules/proc_adding-a-gce-connection.adoc[leveloffset=+1]
1515

1616
include::modules/proc_adding-images-to-server.adoc[leveloffset=+1]
1717

18-
include::modules/proc_adding-google-gce-details-to-a-compute-profile.adoc[leveloffset=+1]
18+
include::modules/proc_adding-gce-details-to-a-compute-profile.adoc[leveloffset=+1]
1919

2020
include::modules/proc_creating-image-only-hosts.adoc[leveloffset=+1]
2121

22-
include::modules/proc_deleting-a-vm-on-google-gce.adoc[leveloffset=+1]
22+
include::modules/proc_deleting-a-vm-on-gce.adoc[leveloffset=+1]
2323

2424
:!gce-provisioning:
2525
:!CRname:

guides/common/modules/proc_adding-a-google-gce-connection.adoc renamed to guides/common/modules/proc_adding-a-gce-connection.adoc

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
:_mod-docs-content-type: PROCEDURE
22

3-
[id="Adding_a_Google_GCE_Connection_{context}"]
4-
= Adding a Google GCE connection to {ProjectServer}
3+
[id="Adding_a_GCE_Connection_{context}"]
4+
= Adding a GCE connection to {ProjectServer}
55

66
Use this procedure to add Google Compute Engine (GCE) as a compute resource in {Project}.
7-
To use the CLI instead of the {ProjectWebUI}, see the xref:cli-Adding_a_Google_GCE_Connection_{context}[].
7+
To use the CLI instead of the {ProjectWebUI}, see the xref:cli-Adding_a_GCE_Connection_{context}[].
88

99
.Procedure
10-
. In Google GCE, generate a service account key in JSON format.
10+
. In GCE, generate a service account key in JSON format.
1111
For more information, see https://cloud.google.com/iam/docs/creating-managing-service-account-keys[Create and manage service account keys] in the GCE documentation.
1212
. In the {ProjectWebUI}, navigate to *Infrastructure* > *Compute Resources* and click *Create Compute Resource*.
1313
. In the *Name* field, enter a name for the compute resource.
@@ -18,9 +18,9 @@ For more information, see https://cloud.google.com/iam/docs/creating-managing-se
1818
. From the *Zone* list, select the GCE zone to use.
1919
. Click *Submit*.
2020

21-
[id="cli-Adding_a_Google_GCE_Connection_{context}"]
21+
[id="cli-Adding_a_GCE_Connection_{context}"]
2222
.CLI procedure
23-
. In Google GCE, generate a service account key in JSON format.
23+
. In GCE, generate a service account key in JSON format.
2424
For more information, see https://cloud.google.com/iam/docs/creating-managing-service-account-keys[Create and manage service account keys] in the GCE documentation.
2525
. Use the `hammer compute-resource create` command to add a GCE compute resource to {Project}:
2626
+

guides/common/modules/proc_adding-google-gce-details-to-a-compute-profile.adoc renamed to guides/common/modules/proc_adding-gce-details-to-a-compute-profile.adoc

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,29 +1,29 @@
11
:_mod-docs-content-type: PROCEDURE
22

3-
[id="Adding_Google_GCE_Details_to_a_Compute_Profile_{context}"]
4-
= Adding Google GCE details to a compute profile
3+
[id="Adding_GCE_Details_to_a_Compute_Profile_{context}"]
4+
= Adding GCE details to a compute profile
55

6-
Use this procedure to add Google GCE hardware settings to a compute profile.
7-
When you create a host on Google GCE using this compute profile, these settings are automatically populated.
6+
Use this procedure to add Google Compute Engine (GCE) hardware settings to a compute profile.
7+
When you create a host on GCE using this compute profile, these settings are automatically populated.
88

9-
To use the CLI instead of the {ProjectWebUI}, see the xref:cli-Adding_Google_GCE_Details_to_a_Compute_Profile_{context}[].
9+
To use the CLI instead of the {ProjectWebUI}, see the xref:cli-Adding_GCE_Details_to_a_Compute_Profile_{context}[].
1010

1111
.Procedure
1212
. In the {ProjectWebUI}, navigate to *Infrastructure* > *Compute Profiles*.
1313
. In the Compute Profiles window, click the name of an existing compute profile, or click *Create Compute Profile*, enter a *Name*, and click *Submit*.
1414
. Click the name of the GCE compute resource.
1515
. From the *Machine Type* list, select the machine type to use for provisioning.
1616
. From the *Image* list, select the image to use for provisioning.
17-
. From the *Network* list, select the Google GCE network to use for provisioning.
17+
. From the *Network* list, select the GCE network to use for provisioning.
1818
. Optional: Select the *Associate Ephemeral External IP* checkbox to assign a dynamic ephemeral IP address that {Project} uses to communicate with the host.
1919
This public IP address changes when you reboot the host.
20-
If you need a permanent IP address, reserve a static public IP address on Google GCE and attach it to the host.
20+
If you need a permanent IP address, reserve a static public IP address on GCE and attach it to the host.
2121
. In the *Size (GB)* field, enter the size of the storage to create on the host.
2222
. Click *Submit* to save the compute profile.
2323

24-
[id="cli-Adding_Google_GCE_Details_to_a_Compute_Profile_{context}"]
24+
[id="cli-Adding_GCE_Details_to_a_Compute_Profile_{context}"]
2525
.CLI procedure
26-
. Create a compute profile to use with the Google GCE compute resource:
26+
. Create a compute profile to use with the GCE compute resource:
2727
+
2828
[options="nowrap" subs="+quotes"]
2929
----

guides/common/modules/proc_deleting-a-vm-on-google-gce.adoc renamed to guides/common/modules/proc_deleting-a-vm-on-gce.adoc

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,15 @@
11
:_mod-docs-content-type: PROCEDURE
22

3-
[id="Deleting_a_VM_on_Google_GCE_{context}"]
4-
= Deleting a VM on Google GCE
3+
[id="Deleting_a_VM_on_GCE_{context}"]
4+
= Deleting a VM on GCE
55

6-
You can delete VMs running on Google GCE on your {ProjectServer}.
6+
You can delete VMs running on Google Compute Engine (GCE) on your {ProjectServer}.
77

88
.Procedure
99
. In the {ProjectWebUI}, navigate to *Infrastructure > Compute Resources*.
10-
. Select your Google GCE provider.
10+
. Select your GCE provider.
1111
. On the *Virtual Machines* tab, click *Delete* from the *Actions* menu.
12-
This deletes the virtual machine from the Google GCE compute resource while retaining any associated hosts within {Project}.
12+
This deletes the virtual machine from the GCE compute resource while retaining any associated hosts within {Project}.
1313
If you want to delete the orphaned host, navigate to *Hosts > All Hosts* and delete the host manually.
1414

1515
include::snip_warning-destroy-vm-on-host-delete.adoc[]

guides/common/modules/proc_installing-google-gce-plugin.adoc renamed to guides/common/modules/proc_installing-gce-plugin.adoc

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,18 @@
11
:_mod-docs-content-type: PROCEDURE
22

3-
[id="Installing_Google_GCE_plugin_{context}"]
4-
= Installing Google GCE plugin
3+
[id="Installing_GCE_plugin_{context}"]
4+
= Installing GCE plugin
55

6-
Install the Google GCE plugin to attach an GCE compute resource provider to {Project}.
6+
Install the Google Compute Engine (GCE) plugin to attach a GCE compute resource provider to {Project}.
77
This allows you to manage and deploy hosts to GCE.
88

99
.Procedure
10-
. Install the Google GCE compute resource provider on your {ProjectServer}:
10+
. Install the GCE compute resource provider on your {ProjectServer}:
1111
+
1212
[options="nowrap", subs="+quotes,verbatim,attributes"]
1313
----
1414
# {foreman-installer} \
1515
--enable-foreman-cli-google \
1616
--enable-foreman-plugin-google
1717
----
18-
. Optional: In the {ProjectWebUI}, navigate to *Administer > About* and select the *Compute Resources* tab to verify the installation of the Google GCE plugin.
18+
. Optional: In the {ProjectWebUI}, navigate to *Administer > About* and select the *Compute Resources* tab to verify the installation of the GCE plugin.

‎guides/common/modules/ref_project-server-port-and-firewall-requirements.adoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ endif::[]
6262
| 80 | TCP | HTTP | Remote repository | Content Sync | Remote repositories
6363
| 389, 636 | TCP | LDAP, LDAPS | External LDAP Server | LDAP | LDAP authentication, necessary only if external authentication is enabled.
6464
The port can be customized if `LDAPAuthSource` is defined
65-
| 443 | TCP | HTTPS | Amazon EC2, Azure, Google GCE | Compute resources | Virtual machine interactions (query/create/destroy) (optional)
65+
| 443 | TCP | HTTPS | Amazon EC2, Azure, Google Compute Engine | Compute resources | Virtual machine interactions (query/create/destroy) (optional)
6666
ifdef::satellite[]
6767
ifeval::["{mode}" == "connected"]
6868
| 443 | TCP | HTTPS | console.redhat.com | Red{nbsp}Hat Cloud plugin API calls |

0 commit comments

Comments
 (0)