Skip to content

Commit

Permalink
1st update - Attributes. (#2720)
Browse files Browse the repository at this point in the history 
* Updated with appropriate references to payg and byos attribs and fixed some working.
Co-authored-by: stephenmogg <[email protected]>
Co-authored-by: Joseph Cayouette <[email protected]>
  • Loading branch information
@stephenmogg
stephenmogg authored Feb 5, 2024
1 parent 1f65cc6 commit cc5c295
Show file tree
Hide file tree
Showing 6 changed files with 66 additions and 68 deletions.
6 changes: 3 additions & 3 deletions modules/specialized-guides/pages/public-cloud-guide/faq/faq-appendix.adoc
View file
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
= Appendix

== Countries that can transact {productname} through the Cloud Marketplace
== Countries that can transact {productname} {payg} through the Cloud Marketplace

Countries that can and cannot transact via the cloud marketplaces:
link:https://documentation.suse.com/sle-public-cloud/all/html/public-cloud/countrylist.html#[Supported Country List]
Countries that can transact via the cloud marketplaces:
link:https://documentation.suse.com/sle-public-cloud/all/html/public-cloud/countrylist.html#[Supported Country List]
46 changes: 23 additions & 23 deletions modules/specialized-guides/pages/public-cloud-guide/faq/faq-billing-general.adoc
View file
Original file line number Diff line number Diff line change
Expand Up @@ -5,18 +5,18 @@

**Last updated:** {lastupdate}

== I have an existing {productname} subscription; can I use this on the cloud?
== I have an existing {productname} {byos} subscription; can I use this on the cloud?

BYOS (Bring Your Own Subscription) {productname} deployments are supported on the cloud, however, billing will not be via the Cloud Marketplace.
{byos} {byoslongform} {productname} deployments are supported on the cloud, however, billing will not be via the Cloud Marketplace.

Once the existing subscription term ends, you can purchase {productname} via the Cloud Provider Marketplace and manage your instances with a {productname} deployment that is billed via the Cloud.
Once the existing subscription term ends, you can purchase {productname} {payg} via the Cloud Provider Marketplace and manage your instances with a {productname} deployment that is billed via the Cloud.

== I have an existing deployment covered by a {productname} subscription; can I use this new listing in the cloud for a separate deployment of {productname}?
== I have an existing deployment covered by a {byos} {productname} subscription; can I use this new listing in the cloud for a separate deployment of {productname} {payg}?

Yes, the listing works independently from your existing {productname} subscriptions. Please remember that support processes may be different for deployments using your existing subscription and those billed via the Cloud and there is currently no process for migrating deployments.
Yes, the listing works independently from your existing {byos} {productname} subscriptions. Please remember that support processes may be different for deployments using your existing {byos} subscription and those billed via the Cloud and there is currently no process for migrating deployments.


== Tell me more about how the billing for {productname} works via the Cloud Providers?
== Tell me more about how the billing for {productname} {payg} works via the Cloud Providers?

When purchasing {productname} via the {availability} Marketplaces, the billing is as follows:

Expand All @@ -25,23 +25,23 @@ When purchasing {productname} via the {availability} Marketplaces, the billing i
* The peak usage total is recorded for the month.
* There is a monthly usage charge for each instance in the count.

== I have existing SLES for SAP instances procured via the Cloud Provider Marketplace, is there a cost to manage these instance with {productname}?
== I have existing SLES for SAP instances procured via the Cloud Provider Marketplace, is there a cost to manage these instance with {productname} {payg}?

SLES for SAP Applications PAYG/on-demand instances when purchased via the Cloud Marketplace, include Lifecycle Management(LCM) entitlements for {productname}.
SLES for SAP Applications PAYG/on-demand instances, when purchased via the Cloud Marketplace, include Lifecycle Management(LCM) entitlements for {productname}.

The {productname} billing engine recognizes the embedded LCM entitlements and does not include them in the count. This means there are no additional charges to manage these with the {productname} listing.
The {productname} {payg} billing engine recognizes the embedded LCM entitlements and does not include them in the count. This means there are no additional charges to manage these with the {productname} {payg} listing.

However, if {productname} Monitoring is required for these instances, additional charges will apply for this feature.

== Is there a way to try {productname} before purchasing?
== Is there a way to try {productname} {payg} before purchasing?

If using the {productname} listing in the Cloud Marketplace, billing will commence from the time of deployment and when applicable client instances are on-boarded to {productname}.
If using the {productname} {payg} listing in the Cloud Marketplace, billing will commence from the time of deployment and when applicable client instances are on-boarded to {productname}.

There is the {productname} BYOS listing in the Cloud Marketplace that can be used, a trial subscription key can be obtained via the SUSE Website. This deployment cannot be directly converted to allow billing via Cloud Marketplaces.
There is the {productname} {byos} listing in the Cloud Marketplace that can be used, a trial subscription key can be obtained via the SUSE Website. This deployment cannot be directly converted to allow billing via Cloud Marketplaces.

To benefit from monthly billing via the Cloud Marketplace, {productname} needs to be redeployed using the version from the Cloud Marketplace.
To benefit from monthly billing via the Cloud Marketplace, {productname} needs to be redeployed using the version from the {payg} listing in the Cloud Marketplace.

== How does SUSE calculate the ‘number of managed instances’ to bill for?
== How does SUSE calculate the amount of managed instances to bill for?

Billing is based on the number of managed instances.

Expand Down Expand Up @@ -71,33 +71,33 @@ Below are 3 examples of how the average node count is calculated.

== Are special commercial terms available?

It is depending on the deployment and the cloud provider, as every Cloud Service Provider (CSP) has its own commercial terms and possibilities.
It is dependent on the deployment and the cloud provider, as every Cloud Service Provider (CSP) has its own commercial terms and possibilities.

It may be possible to secure special commercial terms such as an annual subscription. For example, AWS can offer {productname} via a Private Offer. Please contact SUSE for more information.
It may be possible to secure special commercial terms such as an annual subscription. For example, AWS can offer {productname} {payg} via a Private Offer. Please contact SUSE for more information.

== Can my spending on {productname} count towards my committed spend with the cloud provider?
== Can my spending on {productname} {payg} count towards my committed spend with the cloud provider?

There are such programs at the cloud providers:

*Azure MACC Program
*AWS Enterprise Discount Program
*Google CUD
* Azure MACC Program
* AWS Enterprise Discount Program
* Google CUD

Yes, it can. Please contact your Cloud Provider Sales Team for more details.

== How do I purchase {productname} / LCM subscriptions for additional managed instances?

Once {productname} has been deployed from the marketplace listing and billing is active, there is no need to make a specific purchase to manage additional instances. Billing is dynamic and based on the number of instances {productname} is managing. Just on-board additional instances to {productname} as needed, this will be reflected in your Cloud Marketplace bill.
Once {productname} {payg} has been deployed from the marketplace listing and billing is active, there is no need to make a specific purchase to manage additional instances. Billing is dynamic and based on the number of instances {productname} is managing. Just on-board additional instances to {productname} as needed, this will be reflected in your Cloud Marketplace bill.

== Is this an annual commitment, will it auto-renew?

By default, the {productname} listing on the Cloud is billed on a monthly cycle, based on usage. Billing is ongoing for as long as {productname} is deployed and instances are registered.
By default, the {productname} {payg} listing on the Cloud is billed on a monthly cycle, based on usage. Billing is ongoing for as long as {productname} is deployed and instances are registered.

== Is there a volume discount / tiered pricing built into the Cloud Listing?

Currently, there is no volume discount available.

== I no longer require support; how can I end the subscription?
== I no longer require support; how can I end the {productname} {payg} subscription?

If you no longer require support, there are 2 options:

Expand Down
32 changes: 16 additions & 16 deletions modules/specialized-guides/pages/public-cloud-guide/faq/faq-billing-products.adoc
View file
Original file line number Diff line number Diff line change
Expand Up @@ -3,49 +3,49 @@
:sectnums!:
:lastupdate: October 2023

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

Currently, it is *not possible* to migrate an existing 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.
Customers can simply deploy a new {productname} {payg} 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}.
It is simple to open a support case with SUSE for {productname} {payg}.

Create a ‘supportconfig’ via {productname} instance CLI and upload the output to the SUSE Customer Center (SCC) at the following link:
Create a ‘supportconfig’ via {productname} {payg} 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?
== Are there any differences between the {productname} {payg} 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 {productname} {payg} 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?
== Does the {productname} {payg} 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?
== How do I get fixes and updates for {productname} {payg}, 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.
{productname} {payg}, 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.
Billing will occur from the downstream {productname} {payg} instance, where managed instances are connected.

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

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.

Expand All @@ -66,12 +66,12 @@ These credentials should be added to the {productname} configuration to enable t

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.
Please note: Whilst the SUSE Manger Proxy usage is included as part of the {productname} {payg} 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.
== Can I have a {productname} {payg} 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.
No, to benefit from Cloud Marketplace billing, the {productname} {payg} instance must reside on the Cloud. Any {productname} instances on premises will require their own subscriptions.

== What client Operating Systems are Supported with {productname}?
== What client Operating Systems are Supported with {productname} {payg}?
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]
16 changes: 8 additions & 8 deletions modules/specialized-guides/pages/public-cloud-guide/faq/faq-billing-technical.adoc
View file
Original file line number Diff line number Diff line change
Expand Up @@ -7,32 +7,32 @@

== 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.
No, all components needed to handle the billing are part of the {productname} {payg} code base.

== What is the deployment mechanism for {productname} on the Cloud Marketplace?
== What is the deployment mechanism for {productname} {payg} 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.
The Cloud Marketplace listing for {productname} {payg} will deploy 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.
The Cloud Marketplace listing for {productname} {payg} 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.
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.
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} {payg} 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?
== I have purchased multiple {payg} - {payglongform} 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.
Existing deployments *cannot* be directly converted or updated to provide billing via the Cloud Marketplace. To benefit from monthly billing, {productname} {payg} must be deployed directly from the Cloud Marketplace.
Loading

0 comments on commit cc5c295

Please sign in to comment.