<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Ceph and Portworx. &#8211; Best DevOps</title>
	<atom:link href="https://www.bestdevops.com/tag/ceph-and-portworx/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.bestdevops.com</link>
	<description>Lets Learn, Do it &#38; Share! Thats a Best DevOps!!!</description>
	<lastBuildDate>Tue, 13 Oct 2026 04:23:59 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.3</generator>
	<item>
		<title>Agile Stacks Extends DevOps Automation Platform to GCP, Azure, and OpenShift</title>
		<link>https://www.bestdevops.com/agile-stacks-extends-reach-of-devops-automation-platform/</link>
					<comments>https://www.bestdevops.com/agile-stacks-extends-reach-of-devops-automation-platform/#respond</comments>
		
		<dc:creator><![CDATA[anil]]></dc:creator>
		<pubDate>Sat, 22 Jun 2019 09:42:41 +0000</pubDate>
				<category><![CDATA[DevOps]]></category>
		<category><![CDATA[DevOps News]]></category>
		<category><![CDATA[Agile Stacks]]></category>
		<category><![CDATA[AWS]]></category>
		<category><![CDATA[Ceph and Portworx.]]></category>
		<category><![CDATA[GitLab]]></category>
		<category><![CDATA[Harbor]]></category>
		<category><![CDATA[Jenkins]]></category>
		<category><![CDATA[Kubeflow]]></category>
		<category><![CDATA[Minio]]></category>
		<category><![CDATA[Spinnaker]]></category>
		<guid isPermaLink="false">http://www.bestdevops.com/?p=5570</guid>

					<description><![CDATA[Agile Stacks expanded its DevOps automation platform beyond AWS to cover Google Cloud Platform, Microsoft Azure, and Red Hat OpenShift, aiming to unify CI/CD pipelines across hybrid cloud environments through its SuperHub automation hub and GitOps framework.]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph"><em>Originally reported on devops.com, June 2019. Source article covers announcements made at HPE Discover 2019.</em></p>



<h2 class="wp-block-heading">Overview</h2>



<p class="wp-block-paragraph">Agile Stacks announced at the <strong>HPE Discover 2019</strong> conference that it was expanding its DevOps automation platform to support <strong>Google Cloud Platform (GCP)</strong>, <strong>Microsoft Azure</strong>, and <strong>Red Hat OpenShift</strong> — the Kubernetes distribution — alongside its existing support for <strong>Amazon Web Services (AWS)</strong>. The move positions the company to help enterprises manage DevOps pipelines across heterogeneous, hybrid cloud environments from a single control plane.</p>



<p class="wp-block-paragraph">Hewlett-Packard Enterprise (HPE), an investor in Agile Stacks, used the same conference to outline how Kubernetes sits at the center of its own evolving hybrid cloud strategy — making the timing of the announcement strategically significant.</p>



<h2 class="wp-block-heading">What the Agile Stacks Platform Does</h2>



<p class="wp-block-paragraph">According to company CEO John Mathon, the Agile Stacks platform provides a framework for automating the creation of DevOps pipelines across multiple tools and CI/CD platforms. Key capabilities include:</p>



<ul class="wp-block-list">
<li><strong>Service Catalog:</strong> More than 80 DevOps tools and platforms available out of the box, including Kubeflow, Jenkins, GitLab, Spinnaker, Harbor, Minio, Ceph, and Portworx.</li>
<li><strong>Composable Stacks:</strong> DevOps teams configure custom stacks from catalog components. Each component is auto-configured to handle deployment, upgrades, rollbacks, promotions, cloning, backups, test-script generation, merges, performance testing, vulnerability scanning, and functional testing.</li>
<li><strong>GitOps Framework:</strong> An extensible GitOps-based integration layer ties together tools from multiple vendors, reducing the automation silos that typically emerge when organizations adopt best-of-breed tooling.</li>
<li><strong>Automated Cloud Tagging:</strong> Cost visibility across clouds is improved through automated cloud tagging applied via the SuperHub, helping teams track cloud spending without manual overhead.</li>
</ul>



<h2 class="wp-block-heading">The SuperHub: Automating DevOps Automation</h2>



<p class="wp-block-paragraph">At the core of the platform is the <strong>SuperHub</strong> automation hub. Rather than requiring DevOps engineers to wire together individual tools manually, SuperHub orchestrates the entire pipeline lifecycle — from initial provisioning through ongoing operations — using composable, version-controlled stack definitions.</p>



<p class="wp-block-paragraph">Mathon described the product philosophy as &#8220;automating the DevOps automation.&#8221; Organizations that have matured their DevOps practices typically accumulate tools from multiple vendors. Without a unifying layer, those tools create isolated automation islands that can work at cross-purposes. The SuperHub and its GitOps framework are designed to resolve that fragmentation, allowing tooling choices to evolve as organizational DevOps maturity improves.</p>



<h2 class="wp-block-heading">Addressing Hybrid Cloud Complexity</h2>



<p class="wp-block-paragraph">The multi-cloud expansion reflects a broader industry reality: as Kubernetes adoption accelerates, organizations increasingly want to run workloads across public clouds and on-premises infrastructure simultaneously. However, each platform carries its own DevOps tooling assumptions and operational patterns, which compounds complexity for platform and DevOps engineering teams.</p>



<p class="wp-block-paragraph">Mathon argued that hybrid cloud adoption will ultimately push many organizations to standardize DevOps practices enterprise-wide — something that is difficult to achieve without a platform layer that abstracts away provider-specific differences. Agile Stacks positions its platform as that abstraction layer, enabling consistent pipeline behavior whether workloads run on AWS, GCP, Azure, OpenShift, or on-premises Kubernetes clusters.</p>



<h2 class="wp-block-heading">Lowering the Barrier to DevOps Adoption</h2>



<p class="wp-block-paragraph">Beyond serving mature DevOps organizations, Mathon noted that Agile Stacks aims to reduce the initial complexity that prevents less experienced teams from adopting DevOps practices at all. By providing pre-integrated, auto-configured stacks through a service catalog, teams can get functional pipelines running without deep expertise in every individual tool.</p>



<p class="wp-block-paragraph">This is particularly relevant for enterprises that are simultaneously navigating their first hybrid cloud deployments and trying to establish consistent delivery practices — two challenges that, when tackled together, can be overwhelming without appropriate tooling.</p>



<h2 class="wp-block-heading">Key Takeaways</h2>



<ul class="wp-block-list">
<li>Agile Stacks extended its platform to GCP, Azure, and Red Hat OpenShift in June 2019, adding to existing AWS support.</li>
<li>The SuperHub automation hub uses composable, GitOps-managed stacks to orchestrate end-to-end DevOps pipelines.</li>
<li>A service catalog of 80+ tools — including Jenkins, GitLab, Spinnaker, and Kubeflow — is available out of the box.</li>
<li>Automated cloud tagging through SuperHub provides cost tracking across multi-cloud environments.</li>
<li>The platform targets both DevOps-mature organizations struggling with tool fragmentation and newer adopters facing initial setup complexity.</li>
<li>HPE is an investor in Agile Stacks and is aligning its own hybrid cloud strategy around Kubernetes.</li>
</ul>
]]></content:encoded>
					
					<wfw:commentRss>https://www.bestdevops.com/agile-stacks-extends-reach-of-devops-automation-platform/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
