Depending on the configuration of the system infrastructure that the Apprenda Platform is installed to, the Platform may be hosted on a Hybrid Cloud environment. This simply means that the Platform is hosted across two or more Clouds, and the servers/SQL nodes that comprise the Platform are categorized by which Cloud they belong to. Each Cloud is capable of independently hosting all levels of a deployed application (UI, service, and database) and will include its own Load Management and Platform Coordination configurations, but shares a single Core Database and Repository with the rest of the Platform infrastructure.
Practically speaking, working in a Hybrid Cloud environment will not entail any differences in Apprenda Platform functionality (except when defining how deployment decisions are made for guest applications, as described below). To view the Clouds comprising your Platform instance, from the System Operations Center, click the Infrastructure option in the top menu, and then choose the Clouds option. On a Hybrid Cloud environment, the Clouds overview page will look something like this:
From this page, you can see an overview of each Cloud’s characteristics and resource consumption, and you can click the Edit button to edit the properties of a Cloud:
From this window, you can change a Cloud’s properties, including its Name, Type, and other related info.
To see which servers belong to which Clouds, click the Infrastructure option in the top menu bar, and then click the Servers link. Each of the servers listed on the resulting Servers overview page is associated with a specific Cloud, as shown in the Cloud Name column:
Information on the location of Load Managers and Platform Coordination services for each cloud (as well as Platform-wide components, such as the Core Database and Repository) can be found on the Core Components section of the Servers and Database Nodes tabs.
Development Teams can choose which Cloud to deploy individual applications to through an application’s Cloud Affinity setting. By default, this setting is disabled for Development Teams, but it can be enabled by the Platform Administrator by setting the DeploymentSettings.AllowCloudAffinitySelection Registry setting to True (for more information on managing Registry settings, please see here). When this setting is enabled, Development Teams are able to set Cloud Affinity on a per-application basis, guaranteeing that all of an application’s deployed components must be hosted on the chosen Cloud.