Working with Providers
Webscale uses external services, such as cloud providers and Docker registries, to provide functionality and implement features. To connect to an external service, you must create a provider. External services require authentication to access them. Each provider has a set of credentials to authenticate to the corresponding service.
You can define providers for your account through the Webscale Control Panel. After you create a provider, you can use them in blueprints for data planes and clusters. You can also use providers to implement features such as Webscale CDN.
Webscale uses blueprints to connect to and define the Webscale usage of cloud providers. Applications that are associated with a data plane are connected to the providers for their data plane. As you create blueprints, the data planes, clusters, and applications connected with the provider will display in the providers list.
Webscale supports the following public cloud service providers: Amazon, Azure, Google and CloudSigma.
Customers with applications hosted in the Stratus cloud environment will also have access to the Stratus provider type.
Providers can also be used to store credentials to access Docker registries.
After you create a provider, it will display in your list of providers. In addition, you can edit and delete them through the Providers tab on the account settings page.
- Create providers
- Provider settings
- Edit providers
- Delete providers
When you create a Webscale provider, enter a name and select a cloud service provider type. After you select a type, the Add Providers dialog box adds settings specific to it. For a provider with the Amazon EC2 type, you can enable Webscale CDN and CloudEDGE Workers.
The tables that follow this procedure contain descriptions of provider type settings. The provider type settings include your logins for the cloud service provider accounts. For help with determining the values for other settings, contact support.
To create a provider
- On the Webscale Control Panel page, click the menu icon on upper left of the screen.
- On the sidebar menu, select Providers.
- On the Providers tab, click Add Provider.
- Select the provider type. The settings specific to the provider type display.
- Enter settings information.
- Click Save.
Following are tables that contain the settings for each provider type.
|Region||A geographic area that contains at least two distinct physical locations (known as “availability zones”), each of which contains clustered data centers. With the distributed data centers of the availability zones, a region provides high availability for the designated area.||Required|
|Access key id||Used to access your AWS account||Required|
|Secret access key||Used to access your AWS account||Required|
|Use elastic IP||Enables using static IP addresses||Optional|
|VPC||Virtual Private Cloud. Identifies a virtual network of shared resources allocated within an Amazon Web Services (AWS) public cloud environment||Optional|
|Use for CDN||Enables Webscale CDN for your provider if you also specify the AWS S3 bucket for CDN logs. After you enable CDN for the provider, you can enable this feature for all applications that use the provider.||Optional|
|S3 Bucket Name||Name of the AWS S3 bucket for your Webscale CDN logs||Optional. Displays if you select the Use for CDN checkbox.|
|Use for handlers||Enables handlers for your provider. After you enable handlers for the provider, you can create handlers for your account.||Optional|
|Use for Security Monitoring||Enables AWS GuardDuty security monitoring for your provider.||Optional|
|Use for Kubernetes||Creates an EKS service for the provider.||Optional|
|Cluster Name||Name of the Amazon EKS cluster to use when creating Kubernetes targeted clusters.||Optional. Displays if you select the Use for Kubernetes checkbox.|
|Use for ECR||Creates an ECR docker registry service for the provider.||Optional|
|Docker registry endpoint||The fully qualified ECR endpoint in the format:
||Required if Use for ECR is checked.|
|Repositories||A list of ECR repository names as they appear in AWS.||At least one is required if Use for ECR is checked.|
|Tenant id||Unique identifier for your Azure tenant, which represents your organization in Azure Active Directory. A tenant is automatically created when your organization signs up for a Microsoft cloud service subscription. Not an organization or domain name||Required|
|Client id||Unique identifier for the application that is set up through the Azure Active Directory||Required|
|Client secret||Password exclusive to the application and authorization server||Required|
|Subscription||Logical container used to provision resources in Azure||Optional|
|Location||Location within a geographic area designed to provide cloud services to the area||Required|
|Email address||Used to access your account||Required|
|Password||Used to access your account||Required|
|Use static ip||Enables using static IP addresses with the account||Optional|
|VLAN||Created from one or more local area networks, a Virtual Local Area Network (VLAN) combines collections of devices into one logical network||Optional|
|Project ID||Unique identifier for your project, which organizes all of your Google Cloud resources||Required|
|Email address||Email address associated with your project||Required|
|Private key||Private RSA key that enables generating a token to access your Google Cloud account||Required|
|Network||Virtual Private Cloud (VPC) network that distributes traffic from Webscale||Required|
Webscale clusters cannot be deployed to a Stratus environment without configuring a Stratus Provider. If your environment is hosted in the Stratus cloud environment, contact support to setup your Stratus Provider.
|Cluster Name||The name of the Stratus cluster.||Required|
|Docker Registry Endpoint||The fully qualified endpoint at which the registry is accessible.||Required.|
|Public||If checked, indicates that credentials are not required to access the registry.||Optional|
|Repositories||A list of repositories accessible at the endpoint specified.||At least one is required.|
|Username||The username used to access the docker registry.||Required if Public is not checked.|
|Password||The password used to access the docker registry.||Required if Public is not checked.|
Note:For DockerHub, the Docker registry endpoint is
index.docker.io. DockerHub Public repository names are often prepended with
library/. For example:
Warning:Editing a provider, which defines the relationship between your Webscale account and cloud service, can result in serious problems. Proceed with caution and contact support before editing a provider.
To edit a provider
On the Webscale Control Panel page, click the menu icon on the upper left of the screen.
On the sidebar menu, select Providers.
On the Providers tab, click the Edit button for the provider.
In the Edit provider dialog box, modify settings.
You cannot delete providers used in blueprints. To delete a provider in use, discard any blueprints that include the provider before deleting it.
Warning:Deleting a provider, which defines the relationship between your Webscale account and cloud service, can result in serious problems. Proceed with caution and contact support before deleting a provider.
To delete a provider
On the Webscale Control Panel page, click the menu icon on upper left of the screen.
On the sidebar menu, select Providers.
On the Providers tab, click the **Edit **button for the provider.
In the Edit provider dialog box, click Delete.
To confirm deleting the provider, click Yes.
Have questions not answered here? Please Contact Support to get more help.
Was this page helpful?
Glad to hear it! Have any more feedback? Please share it here.
Sorry to hear that. Have any more feedback? Please share it here.