Skip to content

Commit

Permalink
Add public cloud faq (#2721)
Browse files Browse the repository at this point in the history
* update public cloud guide faq

* update
  • Loading branch information
jcayouette authored Jan 19, 2024
1 parent 9540281 commit 4835dc6
Show file tree
Hide file tree
Showing 4 changed files with 122 additions and 2 deletions.
4 changes: 2 additions & 2 deletions modules/specialized-guides/nav-specialized-guides-guide.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -33,8 +33,8 @@ endif::[]
**** xref:specialized-guides:public-cloud-guide/faq/faq-listings.adoc[Public Cloud Listings]
**** Billing
***** xref:specialized-guides:public-cloud-guide/faq/faq-billing-general.adoc[General]
***** xref:specialized-guides:public-cloud-guide/faq/faq-technical-billing.adoc[Technical]
***** xref:specialized-guides:public-cloud-guide/faq/faq-technical-product.adoc[Products]
***** xref:specialized-guides:public-cloud-guide/faq/faq-billing-technical.adoc[Technical]
***** xref:specialized-guides:public-cloud-guide/faq/faq-billing-products.adoc[Products]
**** xref:specialized-guides:public-cloud-guide/faq/faq-miscellaneous.adoc[Miscellaneous]
**** xref:specialized-guides:public-cloud-guide/faq/faq-appendix.adoc[Appendix]
*** xref:public-cloud-guide/payg-support.adoc[Public Cloud Support]
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,77 @@
= Billing - Products
:availability: AWS & Azure
:sectnums!:
:lastupdate: October 2023

== How do I migrate an existing {productname} instance to the PAYG version?

Currently, it is *not possible* to migrate an existing instance to the PAYG version.

Customers can simply deploy a new {productname} instance from the Cloud Marketplace and re-onboard all instances using the standard process.

link:https://documentation.suse.com/suma/4.3/en/suse-manager/client-configuration/client-config-overview.html[Client configuration overview]

== How do I get support?

It is simple to open a support case with SUSE for {productname}.

Create a ‘supportconfig’ via {productname} instance CLI and upload the output to the SUSE Customer Center (SCC) at the following link:

https://scc.suse.com/cloudsupport

Providing Marketplace billing is active, a support case will be opened.

== Are there any differences between the {productname} product on the Cloud Marketplaces compared to the versions I can run in my own data center?

The {productname} product available in the Cloud Marketplace is the same product, with similar functionality that you would run on-premises or with a manual installation.

The only exceptions being the ability to bill via the Cloud Marketplace and connect to the SUSE Update Infrastructure for {productname} product updates.

It is also worth checking the list of supported client operating systems to ensure your needs are met.

== Does the {productname} instance need to run 24/7?

It is recommended that the {productname} instance always remains active.

== How do I get fixes and updates for {productname}, do I need a subscription key?

{productname}, when deployed via the Cloud Marketplace will automatically connect to the SUSE Update Infrastructure, no separate {productname} Subscription Key is required.

Updates to the {productname} instance can be applied from those channels using standard SUSE tooling (i.e. zypper).

== Is the use of {productname} Hub supported with this listing?

Yes, {productname} Hub is recommended for customer with more than 10,000 managed clients. If the {productname} Hub instance has no connected clients, there will be no charge for the {productname} software components / Hub etc.

Billing will occur from the downstream {productname} instance, where managed instances are connected.

== Can I manage Bring Your Own Subscription (BYOS) SLES instances in the Cloud with {productname}?

To manage BYOS instances, SCC credentials with entitlement to valid SLES or SLES for SAP subscriptions will be required. These credentials should be added to the {productname} configuration to enable this functionality.

== I have a hybrid setup; can I manage instances (workloads) outside of the cloud?

Yes, it is possible to manage instances, in the cloud, on premises or both.

To enable management of SUSE workloads in an on-premises data center, SCC credentials with entitlement to valid SLES or SLES for SAP subscriptions will be required.

These credentials should be added to the {productname} configuration to enable this functionality.

[NOTE]
====
Egress data charges may apply when managing workloads outside of the Cloud Provider's network.
====

== Are there additional charges for using a {productname} Proxy?

With a hybrid landscape, egress data charges may apply when managing workloads outside of the Cloud Provider. To reduce these costs, SUSE recommend the use of the containerized proxy.

Please note: Whilst the SUSE Manger Proxy usage is included as part of the {productname} subscription, an LCM+ subscription will be billed if the proxy is also a managed workload, so in other words it counted as a managed client.

== Can I have a {productname} Server on premises and bill via the Cloud Marketplace.

No, to benefit from Cloud Marketplace billing, the {productname} instance must reside on the Cloud. Any {productname} instances on premises will require their own subscriptions.

== What client Operating Systems are Supported with {productname}?
Please refer to the product documentation for a full list of supported clients.
link:https://documentation.suse.com/suma/4.3/ja/suse-manager/specialized-guides/public-cloud-guide/payg/payg-overview.html[{payg} Overview]
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
= Billing - Technical
:availability: AWS & Azure
:sectnums!:
:lastupdate: October 2023

**Last updated:** {lastupdate}

== Do I need any special or additional infrastructure to set up {productname} billing via the Cloud Marketplaces?

No, all components needed to handle the billing are part of the {productname} code base.

== What is the deployment mechanism for {productname} on the Cloud Marketplace?

The Cloud Marketplace listing for {productname} will deploy an special image which fires up a {productname} instance, together with the embedded billing engine.

== What version of {productname} is installed when using the Marketplace listing?

The Cloud Marketplace listing for {productname} is tied to a specific version of {productname} (4.3.8 at launch). Future listings will typically include the latest version available at the time of product/image creation. Please check the listing for further information.

== I need a prior version of {productname} installed; can I still use the listing?

No, there is no choice over the {productname} version when deploying using the Cloud Marketplace listing. If a prior version of {productname} is required, this will need to be installed manually using the standard documentation and BYOS billing.

== How often is the listing updated (including the version of {productname} etc.)?

The Marketplace listing is tied to a specific version of {productname}, which is the latest version available at the time of the listing.

Typically, the listing in the Cloud Marketplace is updated quarterly, or more frequently if there are security issues.

It is worth noting that the image update process may not be fully aligned to the {productname} product maintenance releases (every 6-8 weeks), so {productname} instances should be patched regularly after deployment.

== I have purchased multiple SUSE products from the Cloud Provider Marketplace (i.e. Rancher, NeuVector and {productname}), does the Marketplace billing method still work?

Yes, the billing mechanism for the products is independent. Each deployment will be billed separately via the cloud Marketplace.

== I already have an existing {productname} deployment; how can I get this deployment to bill via the Cloud Marketplace?

Existing deployments *cannot* be directly converted or updated to provide billing via the Cloud Marketplace. To benefit from monthly billing, {productname} must be deployed newly from the Cloud Marketplace.
Original file line number Diff line number Diff line change
Expand Up @@ -15,8 +15,13 @@ This brings the value of running {productname} to cloud customers, with the bene

* xref:specialized-guides:public-cloud-guide/faq/faq-listings.adoc[Public Cloud Listings]
* xref:specialized-guides:public-cloud-guide/faq/faq-billing-general.adoc[Billing - General]
<<<<<<< HEAD
* xref:specialized-guides:public-cloud-guide/faq/faq-billing-technical.adoc[Billing - Technical]
* xref:specialized-guides:public-cloud-guide/faq/faq-billing-products.adoc[Billing - Products]
=======
* xref:specialized-guides:public-cloud-guide/faq/faq-technical-billing.adoc[Billing - Technical]
* xref:specialized-guides:public-cloud-guide/faq/faq-technical-product.adoc[Billing - Products]
>>>>>>> master
* xref:specialized-guides:public-cloud-guide/faq/faq-miscellaneous.adoc[Miscellaneous]
* xref:specialized-guides:public-cloud-guide/faq/faq-appendix.adoc[Appendix]
Expand Down

0 comments on commit 4835dc6

Please sign in to comment.