<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Infrastructure on CloudBolt Documentation</title>
		<link>https://docs.cloudbolt.io/docs/cmp/configure/infrastructure/</link>
		<description>Recent content in Infrastructure on CloudBolt Documentation</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<atom:link href="https://docs.cloudbolt.io/docs/cmp/configure/infrastructure/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Resource pools</title>
				<link>https://docs.cloudbolt.io/docs/cmp/configure/infrastructure/resource-pools/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://docs.cloudbolt.io/docs/cmp/configure/infrastructure/resource-pools/</guid>
				<description>&lt;p&gt;Instead of generating a hostname or letting a parameter be filled in on the order form, you can prepare the values in advance and let CMP allocate them. A pool is attached to one or more environments, and each server built into those environments claims one set of values from it. A set is claimed by a single server, so the same value is never handed out twice.&lt;/p&gt;&#xA;&lt;h2 id=&#34;add-a-resource-pool&#34;&gt;Add a resource pool&lt;/h2&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;Go to &lt;strong&gt;Admin&lt;/strong&gt; &amp;gt; &lt;strong&gt;Resource Pools&lt;/strong&gt;.&lt;/li&gt;&#xA;&lt;li&gt;Select &lt;strong&gt;Add a resource pool&lt;/strong&gt;.&lt;/li&gt;&#xA;&lt;li&gt;Fill in the fields, then select &lt;strong&gt;Create&lt;/strong&gt;.&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;p&gt;The &lt;strong&gt;Scope&lt;/strong&gt; column reads &lt;strong&gt;Local&lt;/strong&gt; for any pool you create here, meaning it applies across the environments you attach it to.&lt;/p&gt;</description>
			</item>
			<item>
				<title>OS builds</title>
				<link>https://docs.cloudbolt.io/docs/cmp/configure/infrastructure/os-builds/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://docs.cloudbolt.io/docs/cmp/configure/infrastructure/os-builds/</guid>
				<description>&lt;p&gt;One OS build can gather the equivalent template or image from several resource handlers, so an order form can offer a choice of operating system rather than a list of platform-specific template names. The build also controls which environments offer it. Cloud Management Platform (CMP) uses the build to decide what to deploy from, and users never see the underlying template names.&lt;/p&gt;&#xA;&lt;h2 id=&#34;add-an-os-build&#34;&gt;Add an OS build&lt;/h2&gt;&#xA;&lt;p&gt;Managing OS builds needs the &lt;code&gt;osbuild.manage&lt;/code&gt; permission.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Container orchestrators</title>
				<link>https://docs.cloudbolt.io/docs/cmp/configure/infrastructure/container-orchestrators/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://docs.cloudbolt.io/docs/cmp/configure/infrastructure/container-orchestrators/</guid>
				<description>&lt;p&gt;Two technologies are supported: &lt;strong&gt;Kubernetes&lt;/strong&gt; and &lt;strong&gt;OpenShift&lt;/strong&gt;. A hosted service such as Google Kubernetes Engine or Azure Kubernetes Service is added as a Kubernetes orchestrator. Once a cluster is connected, a blueprint can include a container object, and CMP deploys it to the cluster and manages it alongside the rest of the resource.&lt;/p&gt;&#xA;&lt;h2 id=&#34;add-a-container-orchestrator&#34;&gt;Add a container orchestrator&lt;/h2&gt;&#xA;&lt;p&gt;Managing container orchestrators needs the &lt;code&gt;containerorchestrator.manage&lt;/code&gt; permission.&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;Go to &lt;strong&gt;Admin&lt;/strong&gt; &amp;gt; &lt;strong&gt;Container Orchestrators&lt;/strong&gt;.&lt;/li&gt;&#xA;&lt;li&gt;Select &lt;strong&gt;Add&lt;/strong&gt;, then choose a technology.&lt;/li&gt;&#xA;&lt;li&gt;Fill in the connection details, then select &lt;strong&gt;Save&lt;/strong&gt;.&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;h3 id=&#34;connection-details&#34;&gt;Connection details&lt;/h3&gt;&#xA;&lt;div class=&#34;table-scroll&#34;&gt;&#xA;&lt;div class=&#34;table-responsive&#34;&gt;&#xA;&lt;table&gt;&#xA;  &lt;thead&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;th&gt;Field&lt;/th&gt;&#xA;          &lt;th&gt;Description&lt;/th&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/thead&gt;&#xA;  &lt;tbody&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;strong&gt;Name&lt;/strong&gt;&lt;/td&gt;&#xA;          &lt;td&gt;The name under which the orchestrator is listed.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;strong&gt;Protocol, IP address, Port&lt;/strong&gt;&lt;/td&gt;&#xA;          &lt;td&gt;How CMP reaches the cluster&amp;rsquo;s API.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;strong&gt;Account username, Password&lt;/strong&gt;&lt;/td&gt;&#xA;          &lt;td&gt;An account authorized to run commands on the cluster. OpenShift labels the username field &lt;strong&gt;Username&lt;/strong&gt; and requires both.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;strong&gt;Environments&lt;/strong&gt;&lt;/td&gt;&#xA;          &lt;td&gt;The environments in which this orchestrator is available.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/tbody&gt;&#xA;&lt;/table&gt;&#xA;&lt;/div&gt;&#xA;&lt;/div&gt;&#xA;&lt;p&gt;The rest of the form depends on the technology:&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
