Skip to content

Commit

Permalink
review changes
Browse files Browse the repository at this point in the history
  • Loading branch information
@immortalcodes
immortalcodes committed Sep 11, 2024
1 parent 2ca3243 commit 3ee81cf
Showing 1 changed file with 58 additions and 46 deletions.
104 changes: 58 additions & 46 deletions templates/openstack/architecture.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ <h1>OpenStack architecture</h1>
The best recipe for a successful cloud deployment is to follow a proven design guide from an experienced and trusted advisor. Canonical's reference architecture for OpenStack has been successfully deployed across hundreds of customers and thousands of sites.
</p>
</div>
<hr class="is-muted" />
<hr class="p-rule--muted" />
<a class="p-button--positive"
href="https://ubuntu.com/engage/dell-openstack-reference-architecture">Check the reference architecture</a>
</div>
Expand All @@ -50,11 +50,13 @@ <h2>Is OpenStack complex?</h2>
<p>Keep reading to learn how Canonical OpenStack helps you bypass all this complexity.</p>
</div>
</div>
</div>
<div class="u-fixed-width">
<div class="p-image-container u-hide--small u-hide--medium">
{{ image(url="https://assets.ubuntu.com/v1/943a8b94-is-openstack-complex-img.png",
alt="",
width="1280",
height="534",
width="2464",
height="1027",
hi_def=True,
attrs={"class": "p-image-container__image"},
loading="lazy") | safe
Expand All @@ -74,7 +76,9 @@ <h2>Why Canonical OpenStack?</h2>
If you want to use OpenStack, but don't necessarily want to deal with its internals, you're in the right place. Canonical effectively tames the complexity of the upstream OpenStack project and delivers its distilled excellence in the form of a human-friendly product &mdash; Canonical OpenStack.
</p>
<hr class="p-rule--muted" />
<a href="/openstack">Explore Canonical OpenStack&nbsp;&rsaquo;</a>
<p>
<a href="/openstack">Explore Canonical OpenStack&nbsp;&rsaquo;</a>
</p>
</div>
<hr class="p-rule--muted u-hide--medium u-hide--small" />
<div class="p-equal-height-row">
Expand Down Expand Up @@ -125,8 +129,8 @@ <h2>OpenStack under the hood</h2>
<div class="p-image-container--cinematic is-highlighted u-hide--medium u-hide--small">
{{ image(url="https://assets.ubuntu.com/v1/ccb38017-openstack-under-the-hood.png",
alt="",
width="640",
height="268",
width="1200",
height="501",
hi_def=True,
attrs={"class": "p-image-container__image"},
loading="lazy") | safe
Expand All @@ -144,7 +148,7 @@ <h2>OpenStack under the hood</h2>
In order to minimise its footprint, Canonical OpenStack ships with only the key features enabled by default. Additional features, such as CaaS or a Load Balancer can be enabled post-deployment with a single terminal command.
</p>
</div>
<hr class="is-muted" />
<hr class="p-rule--muted" />
<a class="p-button--positive" href="/openstack/docs">Access supported features</a>
</div>
</div>
Expand Down Expand Up @@ -175,8 +179,8 @@ <h2>OpenStack components</h2>
<div class="p-image-container u-hide--medium u-hide--small">
{{ image(url="https://assets.ubuntu.com/v1/aa31dc00-1.2.2.png",
alt="",
width="960",
height="545",
width="1349",
height="769",
hi_def=True,
attrs={"class": "p-image-container__image"},
loading="lazy") | safe
Expand All @@ -202,52 +206,60 @@ <h2>How does it work?</h2>
</p>
</div>
</div>
<div class="row p-section--shallow">
<div class="col-start-large-4 col-9 col-medium-6">
<ol class="p-stepped-list--detailed">
<li class="p-stepped-list__item">
<div class="row">
<hr class="p-rule--muted u-hide--large" />
<div class="col-3 col-medium-3">
<h3 class="p-heading--5 p-stepped-list__title">The user requests resources</h3>
</div>
<div class="col-6 col-medium-3">
<p class="p-stepped-list__content">OpenStack enables on-demand resource provisioning. This means that users can request them at any time through the client, dashboard or APIs. No admin intervention is required. No ticket is needed to process users' requests. Provisioning happens behind the scenes. OpenStack takes care of everything.</p>
</div>
<div class="col-start-large-4 col-9 col-medium-6">
<ol class="p-stepped-list--detailed">
<li class="p-stepped-list__item">
<div class="row">
<hr class="p-rule--muted u-hide--large" />
<div class="col-3 col-medium-3">
<h3 class="p-heading--5 p-stepped-list__title">The user requests resources</h3>
</div>
</li>
<hr class="p-rule--muted u-hide--large" />
<li class="p-stepped-list__item">
<div class="row">
<div class="col-3 col-medium-3">
<h3 class="p-heading--5 p-stepped-list__title">OpenStack handles the request</h3>
</div>
<div class="col-6 col-medium-3">
<p class="p-stepped-list__content">Depending on the type of a request, one or another service gets involved in its processing. Each service manages its own domain and provides all necessary functions to handle the given task. This includes user authentication, authorization, resource scheduling, metrics collection, etc.</p>
</div>
<div class="col-6 col-medium-3">
<p class="p-stepped-list__content">
OpenStack enables on-demand resource provisioning. This means that users can request them at any time through the client, dashboard or APIs. No admin intervention is required. No ticket is needed to process users' requests. Provisioning happens behind the scenes. OpenStack takes care of everything.
</p>
</div>
</li>
<hr class="p-rule--muted u-hide--large" />
<li class="p-stepped-list__item">
<div class="row">
<div class="col-3 col-medium-3">
<h3 class="p-heading--5 p-stepped-list__title">OpenStack provisions resources</h3>
</div>
<div class="col-6 col-medium-3">
<p class="p-stepped-list__content">In order to provision the actual resource (a VM, a block storage volume, a snapshot or an external IP address), OpenStack relies on other technologies. This includes the <a href="https://ubuntu.com/server/docs/virtualisation-with-qemu">KVM</a> hypervisor, <a href="https://ubuntu.com/blog/data-centre-networking-what-is-ovn">OVN</a> for networking, <a href="https://ubuntu.com/ceph">Ceph</a> for storage and many, many more.</p>
</div>
</div>
</li>
<hr class="p-rule--muted u-hide--large" />
<li class="p-stepped-list__item">
<div class="row">
<div class="col-3 col-medium-3">
<h3 class="p-heading--5 p-stepped-list__title">OpenStack handles the request</h3>
</div>
</li>
</ol>
</div>
<div class="col-6 col-medium-3">
<p class="p-stepped-list__content">
Depending on the type of a request, one or another service gets involved in its processing. Each service manages its own domain and provides all necessary functions to handle the given task. This includes user authentication, authorization, resource scheduling, metrics collection, etc.
</p>
</div>
</div>
</li>
<hr class="p-rule--muted u-hide--large" />
<li class="p-stepped-list__item">
<div class="row">
<div class="col-3 col-medium-3">
<h3 class="p-heading--5 p-stepped-list__title">OpenStack provisions resources</h3>
</div>
<div class="col-6 col-medium-3">
<p class="p-stepped-list__content">
In order to provision the actual resource (a VM, a block storage volume, a snapshot or an external IP address), OpenStack relies on other technologies. This includes the <a href="https://ubuntu.com/server/docs/virtualisation-with-qemu">KVM</a> hypervisor, <a href="https://ubuntu.com/blog/data-centre-networking-what-is-ovn">OVN</a> for networking, <a href="https://ubuntu.com/ceph">Ceph</a> for storage and many, many more.
</p>
</div>
</div>
</li>
</ol>
</div>
</section>

<section class="p-section--deep">
<div class="row--50-50">
<hr />
<div class="col">
<h2>Get started<br /> with Canonical OpenStack</h2>
<h2>
Get started
<br />
with Canonical OpenStack
</h2>
</div>
<div class="col">
<div class="p-section--shallow">
Expand All @@ -256,7 +268,7 @@ <h2>Get started<br /> with Canonical OpenStack</h2>
With Canonical OpenStack you can get started on your journey on a single physical machine. Simply try it out and continue learning through some practical exercises.
</p>
</div>
<hr class="is-muted" />
<hr class="p-rule--muted" />
<a class="p-button--positive" href="/openstack/docs/single-node">Start today</a>
</div>
</div>
Expand Down

0 comments on commit 3ee81cf

Please sign in to comment.