Skip to content

Commit 0fd1385

Browse files
EricPonvelleEricPonvelle
authored
Merge pull request #64901 from mletalie/OSDOCS-6943
[OSDOCS-6943]:OSD-GCP: Purchasing OSD through GCP Marketplace
2 parents e1279ac + 8dc8002 commit 0fd1385

File tree

4 files changed

+141
-5
lines changed

4 files changed

+141
-5
lines changed

‎modules/osd-create-cluster-gcp-account.adoc

Lines changed: 105 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,105 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * osd_install_access_delete_cluster/creating-a-gcp-cluster.adoc
4+
5+
:_content-type: PROCEDURE
6+
[id="osd-create-cluster-gcp-account_{context}"]
7+
= Creating a cluster on GCP with Google Cloud Marketplace
8+
9+
When creating an {product-title} (OSD) cluster on Google Cloud through the OpenShift Cluster Manager Hybrid Cloud Console, customers can select Google Cloud Marketplace as their preferred billing model. This billing model allows Red Hat customers to take advantage of their link:https://cloud.google.com/docs/cuds[Google Committed Use Discounts (CUD)] towards {product-title} purchased through the Google Cloud Marketplace. Additionally, OSD pricing is consumption-based and customers are billed directly through their Google Cloud account.
10+
11+
.Procedure
12+
13+
. Log in to {cluster-manager-url} and click *Create cluster*.
14+
15+
. In the *Cloud* tab, click *Create cluster* in the *Red Hat OpenShift Dedicated* row.
16+
17+
. Under *Billing model*, configure the subscription type and infrastructure type:
18+
.. Select the *On-Demand* subscription type.
19+
.. From the drop-down menu, select *Google Cloud Marketplace*.
20+
.. Select the *Customer Cloud Subscription* infrastructure type.
21+
.. Click *Next*.
22+
. On the *Cloud provider* page, read the provided prerequisites and the Google terms and conditions. Add your service account key.
23+
.. Click the *Review Google Terms and Agreements* link.
24+
.. To continue creating the cluster, click the checkbox indicating that you agree to the Google terms and agreements.
25+
.. Add your service account key.
26+
+
27+
[NOTE]
28+
====
29+
For more information about service account keys, click the information icon located next to *Service account key*.
30+
====
31+
.. Click *Next* to validate your cloud provider account and go to the *Cluster details* page.
32+
. On the *Cluster details* page, provide a name for your cluster and specify the cluster details:
33+
.. Add a *Cluster name*.
34+
.. Select a cluster version from the *Version* drop-down menu.
35+
.. Select a cloud provider region from the *Region* drop-down menu.
36+
.. Select a *Single zone* or *Multi-zone* configuration.
37+
.. Select a *Persistent storage* capacity for the cluster. For more information, see the _Storage_ section in the {product-title} service definition.
38+
.. Specify the number of *Load balancers* that you require for your cluster. For more information, see the _Load balancers_ section in the {product-title} service definition.
39+
.. Leave *Enable user workload monitoring* selected to monitor your own projects in isolation from Red Hat Site Reliability Engineer (SRE) platform metrics. This option is enabled by default.
40+
.. Optional: Select *Enable additional etcd encryption* if you require etcd key value encryption. With this option, the etcd key values are encrypted, but not the keys. This option is in addition to the control plane storage encryption that encrypts the etcd volumes in {product-title} clusters by default.
41+
+
42+
[NOTE]
43+
====
44+
By enabling etcd encryption for the key values in etcd, you incur a performance overhead of approximately 20%. The overhead is a result of introducing this second layer of encryption, in addition to the default control plane storage encryption that encrypts the etcd volumes. Consider enabling etcd encryption only if you specifically require it for your use case.
45+
====
46+
.. Click *Next*.
47+
48+
. On the *Machine pool* page, select a *Compute node instance type* and a *Compute node count*. The number and types of nodes that are available depend on your {product-title} subscription. If you are using multiple availability zones, the compute node count is per zone.
49+
+
50+
[NOTE]
51+
====
52+
After your cluster is created, you can change the number of compute nodes, but you cannot change the compute node instance type in a created machine pool. You can add machine pools after installation that use a customized instance type. The number and types of nodes available to you depend on your {product-title} subscription.
53+
====
54+
55+
. Optional: Expand *Edit node labels* to add labels to your nodes. Click *Add label* to add more node labels and select *Next*.
56+
57+
. In the *Cluster privacy* dialog, select *Public* or *Private* to use either public or private API endpoints and application routes for your cluster.
58+
59+
. Click *Next*.
60+
61+
. In the *CIDR ranges* dialog, configure custom classless inter-domain routing (CIDR) ranges or use the defaults that are provided.
62+
+
63+
[IMPORTANT]
64+
====
65+
CIDR configurations cannot be changed later. Confirm your selections with your network administrator before proceeding.
66+
67+
If the cluster privacy is set to *Private*, you cannot access your cluster until you configure private connections in your cloud provider.
68+
====
69+
70+
. On the *Cluster update strategy* page, configure your update preferences:
71+
.. Choose a cluster update method:
72+
** Select *Individual updates* if you want to schedule each update individually. This is the default option.
73+
** Select *Recurring updates* to update your cluster on your preferred day and start time, when updates are available.
74+
+
75+
[NOTE]
76+
====
77+
You can review the end-of-life dates in the update lifecycle documentation for {product-title}. For more information, see _{product-title} update lifecycle_.
78+
====
79+
+
80+
.. Provide administrator approval based on your cluster update method:
81+
** Individual updates: If you select an update version that requires approval, provide an administrator’s acknowledgment and click *Approve and continue*.
82+
** Recurring updates: If you selected recurring updates for your cluster, provide an administrator’s acknowledgment and click *Approve and continue*. {cluster-manager} does not start scheduled y-stream updates for minor versions without receiving an administrator’s acknowledgment.
83+
+
84+
For information about administrator acknowledgment, see xref:./../upgrading/osd-upgrading-cluster-prepare.adoc#upgrade-49-acknowledgement_osd-updating-cluster-prepare[Administrator acknowledgment when upgrading to OpenShift 4.9].
85+
.. If you opted for recurring updates, select a preferred day of the week and upgrade start time in UTC from the drop-down menus.
86+
.. Optional: You can set a grace period for *Node draining* during cluster upgrades. A *1 hour* grace period is set by default.
87+
.. Click *Next*.
88+
+
89+
[NOTE]
90+
====
91+
In the event of critical security concerns that significantly impact the security or stability of a cluster, Red Hat Site Reliability Engineering (SRE) might schedule automatic updates to the latest z-stream version that is not impacted. The updates are applied within 48 hours after customer notifications are provided. For a description of the critical impact security rating, see link:https://access.redhat.com/security/updates/classification[Understanding Red Hat security ratings].
92+
====
93+
94+
. Review the summary of your selections and click *Create cluster* to start the cluster installation. The installation takes approximately 30-40 minutes to complete.
95+
96+
.Verification
97+
98+
* You can monitor the progress of the installation in the *Overview* page for your cluster. You can view the installation logs on the same page. Your cluster is ready when the *Status* in the *Details* section of the page is listed as *Ready*.
99+
100+
ifeval::["{context}" == "osd-creating-a-cluster-on-aws"]
101+
:!osd-on-aws:
102+
endif::[]
103+
ifeval::["{context}" == "osd-creating-a-cluster-on-gcp"]
104+
:!osd-on-gcp:
105+
endif::[]

‎modules/sdpolicy-am-billing.adoc

Lines changed: 33 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,12 +3,41 @@
33
// * osd_architecture/osd_policy/osd-service-definition.adoc
44
:_content-type: CONCEPT
55
[id="billing_{context}"]
6-
= Billing
7-
Each {product-title} cluster requires a minimum annual base cluster purchase and there are two billing options available for each cluster: Standard and Customer Cloud Subscription (CCS).
6+
= Billing options
87

9-
Standard {product-title} clusters are deployed in to their own cloud infrastructure accounts, each owned by Red Hat. Red Hat is responsible for this account, and cloud infrastructure costs are paid directly by Red Hat. The customer only pays the Red Hat subscription costs.
8+
Customers have the option to purchase annual subscriptions of {product-title} (OSD) or consume on-demand through cloud marketplaces. Customers can decide to bring their own cloud infrastructure account, referred to as Customer Cloud Subscription (CCS), or deploy in cloud provider accounts owned by Red Hat. The table below provides additional information regarding billing, as well as the corresponding supported deployment options.
9+
[cols="2a,3a,3a",options="header"]
10+
|===
1011

11-
In the CCS model, the customer pays the cloud infrastructure provider directly for cloud costs and the cloud infrastructure account is part of a customer’s Organization, with specific access granted to Red Hat. In this model, the customer pays Red Hat for the CCS subscription and pays the cloud provider for the cloud costs. It is the customer's responsibility to pre-purchase or provide Reserved Instance (RI) compute instances to ensure lower cloud infrastructure costs.
12+
|OSD Subscription-type
13+
|Cloud infrastructure account
14+
|Billed through
15+
16+
.2+|Annual fixed capacity subscriptions through Red Hat |Red Hat cloud account
17+
18+
|Red Hat for consumption of both OSD subscriptions and cloud infrastructure
19+
20+
|Customer's own cloud account
21+
|Red Hat for consumption of the OSD subscriptions
22+
23+
Cloud provider for consumption of cloud infrastructure
24+
25+
|On-demand usage-based consumption through Google Cloud Marketplace
26+
27+
|Customer's own Google Cloud account
28+
|Google Cloud for both cloud infrastructure and Red Hat OSD subscriptions
29+
30+
|On-demand usage-based consumption through Red Hat Marketplace|Customer’s own cloud account| Red Hat for consumption of the OSD subscriptions
31+
32+
Cloud provider for consumption of cloud infrastructure
33+
34+
|===
35+
36+
[IMPORTANT]
37+
====
38+
39+
Customers that use their own cloud infrastructure account, referred to as Customer Cloud Subscription (CSS), are responsible to pre-purchase or provide Reserved Instance (RI) compute instances to ensure lower cloud infrastructure costs.
40+
====
1241

1342
Additional resources can be purchased for an OpenShift Dedicated Cluster, including:
1443

‎osd_getting_started/osd-getting-started.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,8 @@ Complete the steps in one of the following sections to deploy {product-title} in
3131

3232
* *xref:../osd_install_access_delete_cluster/creating-a-gcp-cluster.adoc#osd-create-gcp-cluster-ccs_osd-creating-a-cluster-on-gcp[Creating a cluster on GCP with CCS]*: You can install {product-title} in your own {GCP} account by using the CCS model.
3333

34+
* *xref:../osd_install_access_delete_cluster/creating-a-gcp-cluster.adoc#osd-create-cluster-gcp-account_osd-creating-a-cluster-on-gcp[Creating a cluster on GCP with Google Cloud Marketplace]*: You can install {product-title} in your own {GCP} account with Google Cloud Marketplace.
35+
3436
[id="osd-getting-started-create-cluster-red-hat-cloud-account"]
3537
=== Creating a cluster using a Red Hat cloud account
3638

‎osd_install_access_delete_cluster/creating-a-gcp-cluster.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,8 +16,8 @@ You can install {product-title} on {GCP} by using your own GCP account through t
1616
* You reviewed the xref:../osd_getting_started/osd-understanding-your-cloud-deployment-options.adoc#osd-understanding-your-cloud-deployment-options[{product-title} cloud deployment options].
1717

1818
include::modules/osd-create-cluster-ccs.adoc[leveloffset=+1]
19+
include::modules/osd-create-cluster-gcp-account.adoc[leveloffset=+1]
1920
include::modules/osd-create-cluster-red-hat-account.adoc[leveloffset=+1]
20-
2121
[id="additional-resources_{context}"]
2222
== Additional resources
2323

0 commit comments

Comments
 (0)