{"id":14461,"date":"2023-11-04T00:31:31","date_gmt":"2023-11-03T21:31:31","guid":{"rendered":"https:\/\/kifarunix.com\/?p=14461"},"modified":"2024-03-10T15:15:39","modified_gmt":"2024-03-10T12:15:39","slug":"easily-extend-linux-root-partition-on-openstack-instance","status":"publish","type":"post","link":"https:\/\/kifarunix.com\/easily-extend-linux-root-partition-on-openstack-instance\/","title":{"rendered":"Easily Extend Linux Root Partition on OpenStack Instance"},"content":{"rendered":"\n<p>In this tutorial, we will show you an easy way to extend Linux root partition on OpenStack instance. In OpenStack, it is possible to extend or shrink virtual machine instance disk based on your usage requirements. OpenStack virtual machine disks can be expanded\/extended or shrinked by attaching a specific <a href=\"https:\/\/docs.openstack.org\/nova\/zed\/user\/flavors.html\" target=\"_blank\" rel=\"noreferrer noopener\">flavor<\/a> to the instance. We will however only focus on expanding the root partition in this guide. We will discuss about shrinking in another guide.<\/p>\n\n\n\n<div class=\"wp-block-rank-math-toc-block\" id=\"rank-math-toc\"><h2>Table of Contents<\/h2><nav><ul><li><a href=\"#extending-linux-root-partition-on-open-stack-instance\">Extending Linux Root Partition on OpenStack Instance<\/a><ul><li><a href=\"#create-required-flavor\">Create Required Flavor<\/a><\/li><li><a href=\"#change-update-replace-instance-flavor\">Change\/Update\/Replace Instance Flavor<\/a><\/li><li><a href=\"#resize-linux-root-partition-on-open-stack-instance\">Resize Linux Root Partition on OpenStack Instance<\/a><ul><li><a href=\"#manually-extend-root-partition\">Manually Extend Root Partition<\/a><\/li><li><a href=\"#automatically-extend-root-partition\">Automatically Extend Root Partition<\/a><\/li><\/ul><\/li><\/ul><\/li><\/ul><\/nav><\/div>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"extending-linux-root-partition-on-open-stack-instance\">Extending Linux Root Partition on OpenStack Instance<\/h2>\n\n\n\n<p>For demonstration purposes, we have an instance running on OpenStack with the following highlighted resources allocated;<\/p>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1911\" height=\"881\" src=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/openstack-instance-resources.png\" alt=\"\" class=\"wp-image-19085\" title=\"\" srcset=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/openstack-instance-resources.png?v=1698854072 1911w, https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/openstack-instance-resources-768x354.png?v=1698854072 768w, https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/openstack-instance-resources-1536x708.png?v=1698854072 1536w\" sizes=\"(max-width: 1911px) 100vw, 1911px\" \/><\/figure><\/div>\n\n\n<p>As you can see, the instance resources are 1GB of RAM, 1 vCPU, and 3GB of Disk;<\/p>\n\n\n\n<p>You can also get the instance details from the command line;<\/p>\n\n\n\n<p>First of all, load the OpenStack credentials<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>   source $HOME\/kolla-ansible\/bin\/activate\n   source \/etc\/kolla\/admin-openrc.sh<\/code><\/pre>\n\n\n\n<p>Then use the openstack commands to get the Flavour assigned;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>openstack server list -c Name -c Status -c Flavor --name jammy<\/code><\/pre>\n\n\n\n<p>Where <strong><code>jammy<\/code><\/strong> is the name of the instance. It can be a different name for your instance.<\/p>\n\n\n\n<p>Sample output;<\/p>\n\n\n\n<pre class=\"scroll-sz\"><code>+-------+--------+---------+\n| Name  | Status | Flavor  |\n+-------+--------+---------+\n| jammy | ACTIVE | custom1 |\n+-------+--------+---------+\n<\/code><\/pre>\n\n\n\n<p>To get the details of the OpenStack flavor on command line;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>openstack flavor show custom1<\/code><\/pre>\n\n\n\n<p>Sample output;<\/p>\n\n\n\n<pre class=\"scroll-box\"><code>+----------------------------+--------------------------------------+\n| Field                      | Value                                |\n+----------------------------+--------------------------------------+\n| OS-FLV-DISABLED:disabled   | False                                |\n| OS-FLV-EXT-DATA:ephemeral  | 0                                    |\n| access_project_ids         | None                                 |\n| description                | None                                 |\n| disk                       | 3                                    |\n| id                         | 60a3dea9-81a5-4e83-9164-08ee992862de |\n| name                       | custom1                              |\n| os-flavor-access:is_public | True                                 |\n| properties                 |                                      |\n| ram                        | 1024                                 |\n| rxtx_factor                | 1.0                                  |\n| swap                       |                                      |\n| vcpus                      | 1                                    |\n+----------------------------+--------------------------------------+\n<\/code><\/pre>\n\n\n\n<p>Similarly, login to the instance from the openstack console and confirm the disk details;<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1814\" height=\"871\" src=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/openstack-instance-console.png\" alt=\"\" class=\"wp-image-19086\" title=\"\" srcset=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/openstack-instance-console.png?v=1698862529 1814w, https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/openstack-instance-console-768x369.png?v=1698862529 768w, https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/openstack-instance-console-1536x738.png?v=1698862529 1536w\" sizes=\"(max-width: 1814px) 100vw, 1814px\" \/><\/figure>\n\n\n\n<p>So how can you easily extend\/resize Linux root partition on OpenStack instance?<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"create-required-flavor\">Create Required Flavor<\/h3>\n\n\n\n<p>To extend linux root partition, the first thing you need to is to ensure you have a required flavor already created for your instances.<\/p>\n\n\n\n<p>For example, the flavor specs of our instance at the moment is 1GB RAM, 1 vCPU and 3GB Disk.<\/p>\n\n\n\n<p>In this example, we will update the flavor of the instance to a new one with the specs 1GB RAM, 1 vCPU and 10GB Disk.<\/p>\n\n\n\n<p>At the moment, we don&#8217;t have a flavor with the new required resources;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>openstack flavor list<\/code><\/pre>\n\n\n\n<pre class=\"scroll-sz\"><code>+--------------------------------------+---------+------+------+-----------+-------+-----------+\n| ID                                   | Name    |  RAM | Disk | Ephemeral | VCPUs | Is Public |\n+--------------------------------------+---------+------+------+-----------+-------+-----------+\n| 60a3dea9-81a5-4e83-9164-08ee992862de | custom1 | 1024 |    3 |         0 |     1 | True      |\n| c92170b6-95a0-4fdf-9f61-dc002a87c9ae | mini    | 1024 |    5 |         0 |     1 | True      |\n+--------------------------------------+---------+------+------+-----------+-------+-----------+\n<\/code><\/pre>\n\n\n\n<p>You can also check available flavors from horizon dashboard under <strong>Admin &gt; Compute &gt; Flavors<\/strong>.<\/p>\n\n\n\n<p>As such, you can create your flavor from command line or from the horizon dashboard.<\/p>\n\n\n\n<p>To create from command line (update the command to match your required resource size);<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>openstack flavor create --ram 1024 --disk 10 --vcpus 1 --public &lt;flavor_name&gt;<\/code><\/pre>\n\n\n\n<p>Or from the horizon <strong>Admin &gt; Flavors &gt; Create Flavor<\/strong>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"change-update-replace-instance-flavor\">Change\/Update\/Replace Instance Flavor<\/h3>\n\n\n\n<p>To change the flavor of the instance, you can either do it from the horizon dashboard or from the command line.<\/p>\n\n\n\n<p>Before you can proceed, ensure that the instance is not booting from the volume. Consider the instances below. Jammy is booting from the image while cirros is booting from the volume.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>openstack server list<\/code><\/pre>\n\n\n\n<pre class=\"scroll-sz\"><code>+--------------------------------------+--------+--------+-------------------------+--------------------------+---------+\n| ID                                   | Name   | Status | Networks                | Image                    | Flavor  |\n+--------------------------------------+--------+--------+-------------------------+--------------------------+---------+\n| e7e0864c-6bc6-45cc-bedb-35770e9f037c | jammy  | ACTIVE | DEMO_NET=192.168.50.112 | jammy                    | custom1 |\n| 344897e5-d391-413a-af1f-edcb360f5b48 | cirros | ACTIVE | DEMO_NET=192.168.50.109 | N\/A (booted from volume) | custom2 |\n+--------------------------------------+--------+--------+-------------------------+--------------------------+---------+\n<\/code><\/pre>\n\n\n\n<p>If you try to change flavor of the instance booting from the volume, the changes wont reflect in the instance filesystem.<\/p>\n\n\n\n<p>Thus, to change the flavor of the instance from the Horizon;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Navigate to respective <strong>Project<\/strong> where the instance is running and go to <strong>Compute &gt; Instances<\/strong>.<\/li>\n\n\n\n<li>Under <strong>Actions<\/strong> column of the instance, click the drop down and click <strong>Resize Instance<\/strong>.<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1872\" height=\"870\" src=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/resize-instance-openstack.png\" alt=\"\" class=\"wp-image-19088\" title=\"\" srcset=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/resize-instance-openstack.png?v=1698864788 1872w, https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/resize-instance-openstack-768x357.png?v=1698864788 768w, https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/resize-instance-openstack-1536x714.png?v=1698864788 1536w\" sizes=\"(max-width: 1872px) 100vw, 1872px\" \/><\/figure>\n\n\n\n<ul class=\"wp-block-list\">\n<li>This will open the Resize Wizard.<\/li>\n\n\n\n<li>On the instance resize wizard, select <strong>New Flavor<\/strong>. Under <strong>Advanced Options<\/strong>, leave disk partition as automatic.<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1851\" height=\"741\" src=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/select-new-flavor.png\" alt=\"\" class=\"wp-image-19089\" title=\"\" srcset=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/select-new-flavor.png?v=1698864803 1851w, https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/select-new-flavor-768x307.png?v=1698864803 768w, https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/select-new-flavor-1536x615.png?v=1698864803 1536w\" sizes=\"(max-width: 1851px) 100vw, 1851px\" \/><\/figure>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Click <strong>Resize<\/strong> to extend Linux root partition.<\/li>\n\n\n\n<li>You should now see the instance status resizing.<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1850\" height=\"599\" src=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/instance-resizing.png\" alt=\"\" class=\"wp-image-19090\" title=\"\" srcset=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/instance-resizing.png?v=1698864814 1850w, https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/instance-resizing-768x249.png?v=1698864814 768w, https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/instance-resizing-1536x497.png?v=1698864814 1536w\" sizes=\"(max-width: 1850px) 100vw, 1850px\" \/><\/figure>\n\n\n\n<ul class=\"wp-block-list\">\n<li>When done resizing, you will be prompted to confirm resizing or revert. Hence, click <strong>Confirm Resize<\/strong>.<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1858\" height=\"534\" src=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/confirm-instance-resize.png\" alt=\"\" class=\"wp-image-19091\" title=\"\" srcset=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/confirm-instance-resize.png?v=1698864837 1858w, https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/confirm-instance-resize-768x221.png?v=1698864837 768w, https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/confirm-instance-resize-1536x441.png?v=1698864837 1536w\" sizes=\"(max-width: 1858px) 100vw, 1858px\" \/><\/figure>\n\n\n\n<p>And that is it.<\/p>\n\n\n\n<p>You can also change flavor of the instance from the command line;<\/p>\n\n\n\n<p>List the flavors and find out the one you want to use;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>openstack flavor list<\/code><\/pre>\n\n\n\n<pre class=\"scroll-sz\"><code>+--------------------------------------+---------+------+------+-----------+-------+-----------+\n| ID                                   | Name    |  RAM | Disk | Ephemeral | VCPUs | Is Public |\n+--------------------------------------+---------+------+------+-----------+-------+-----------+\n| 60a3dea9-81a5-4e83-9164-08ee992862de | custom1 | 1024 |    3 |         0 |     1 | True      |\n| b2f23a43-de35-4971-97de-36fc53adb9a2 | custom2 | 1024 |   10 |         0 |     1 | True      |\n| c92170b6-95a0-4fdf-9f61-dc002a87c9ae | mini    | 1024 |    5 |         0 |     1 | True      |\n+--------------------------------------+---------+------+------+-----------+-------+-----------+\n<\/code><\/pre>\n\n\n\n<p>Once you have identified the flavor to use, get the server\/instance name;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>openstack server list<\/code><\/pre>\n\n\n\n<pre class=\"scroll-sz\"><code>+--------------------------------------+--------+--------+-------------------------+--------------------------+---------+\n| ID                                   | Name   | Status | Networks                | Image                    | Flavor  |\n+--------------------------------------+--------+--------+-------------------------+--------------------------+---------+\n| 5dec3f57-33ec-4cce-9242-d6edaa6cf879 | cirros | ACTIVE | DEMO_NET=192.168.50.123 | N\/A (booted from volume) | custom1 |\n| d8e589da-09a7-49be-83fc-5b7ea838511c | jammy  | ACTIVE | DEMO_NET=192.168.50.104 | ubuntu22-minimal         | mini    |\n+--------------------------------------+--------+--------+-------------------------+--------------------------+---------+\n<\/code><\/pre>\n\n\n\n<p>So, now I want to update the flavor of <strong>jammy<\/strong> instance from <strong>mini<\/strong> to <strong>custom2<\/strong>. You can do this by using the <strong><code>openstack server resize<\/code><\/strong> command.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>openstack server resize &#91;-h] &#91;--flavor &lt;flavor&gt;] &#91;--wait] &lt;server&gt;<\/code><\/pre>\n\n\n\n<p>A resize operation is implemented by creating a new server and copying the contents of the original disk into a new one. It is a two-step process for the user: the first step is to perform the resize, and the second step is to either confirm (verify) success and release the old server or to declare a revert to release the new server and restart the old one.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>openstack server resize --flavor  custom2 jammy<\/code><\/pre>\n\n\n\n<p>You can then confirm the server resize to verify success of resize operation and release the old server.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>openstack server resize confirm jammy<\/code><\/pre>\n\n\n\n<p>Confirm again;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>openstack server list<\/code><\/pre>\n\n\n\n<p>Check the assigned flavor.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"resize-linux-root-partition-on-open-stack-instance\">Resize Linux Root Partition on OpenStack Instance<\/h3>\n\n\n\n<p>You can now open the instance console from OpenStack dashboard and proceed to expand the disk.<\/p>\n\n\n\n<p>We will discuss two ways in which you can easily resize Linux root partition after you have updated or replaced the flavor.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Manually extend Root Partition<\/li>\n\n\n\n<li>Automatically extend Root Partition<\/li>\n<\/ol>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"manually-extend-root-partition\">Manually Extend Root Partition<\/h4>\n\n\n\n<p>Consider our jammy instance, we have adjusted the flavor from 1vcpu, 1G ram, 5G disk to 1vcpu, 1G ram and 10G disk;<\/p>\n\n\n\n<p>Let&#8217;s confirm the new size from the console;<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1892\" height=\"659\" src=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/confirm-instance-resize-1.png\" alt=\"\" class=\"wp-image-19109\" title=\"\" srcset=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/confirm-instance-resize-1.png?v=1699042073 1892w, https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/confirm-instance-resize-1-768x268.png?v=1699042073 768w, https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/confirm-instance-resize-1-1536x535.png?v=1699042073 1536w\" sizes=\"(max-width: 1892px) 100vw, 1892px\" \/><\/figure>\n\n\n\n<p>In our previous guides, we covered how to <a href=\"https:\/\/kifarunix.com\/?s=extend+disk\" target=\"_blank\" rel=\"noreferrer noopener\">extend\/shrink disks<\/a>. However, for the purposes of the demonstrating the manual extension;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>open the disk using fdisk or what disk management tool of your choice e.g., <strong><code>fdisk \/dev\/vda<\/code><\/strong>.<\/li>\n\n\n\n<li>delete the root partition, which is partition 3 for my instance; <strong>d<\/strong><\/li>\n\n\n\n<li>create new partition, <strong>n<\/strong><\/li>\n\n\n\n<li>select same parition number. e.g <strong>3<\/strong>.<\/li>\n\n\n\n<li>use all remaining sectors<\/li>\n\n\n\n<li><strong>IMPORTANT<\/strong>: when asked whether to remove the partition signature, say <strong>No<\/strong>!<\/li>\n\n\n\n<li>Write the changes to the disk.<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1214\" height=\"796\" src=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/extend-disk.png\" alt=\"\" class=\"wp-image-19110\" title=\"\" srcset=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/extend-disk.png?v=1699043712 1214w, https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/extend-disk-768x504.png?v=1699043712 768w\" sizes=\"(max-width: 1214px) 100vw, 1214px\" \/><\/figure>\n\n\n\n<p>Next, extend the filesystem.<\/p>\n\n\n\n<p>If it is non-lvm, ext4\/3\/xfs;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>resize2fs \/dev\/vda3<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>xfs_growfs \/dev\/vda3<\/code><\/pre>\n\n\n\n<p>confirm again;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>df -hT -P \/<\/code><\/pre>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1383\" height=\"414\" src=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/disk-extended-manually.png\" alt=\"Easily Extend Linux Root Partition on OpenStack Instance\" class=\"wp-image-19111\" title=\"\" srcset=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/disk-extended-manually.png?v=1699044015 1383w, https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/disk-extended-manually-768x230.png?v=1699044015 768w\" sizes=\"(max-width: 1383px) 100vw, 1383px\" \/><\/figure>\n\n\n\n<p>if it is LVM, check our guides for reference.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"automatically-extend-root-partition\">Automatically Extend Root Partition<\/h4>\n\n\n\n<p>To enable instance automatic disk extension when flavors are changed, you need to install the Cloud-init package in the OpenStack instance, before changing the flavor. One of its key functions is facilitating automatic disk resizing. Cloud-init processes user data or metadata provided during instance creation, enabling it to detect and respond to disk size changes dynamically.<\/p>\n\n\n\n<p>You can install cloud-init as follows<\/p>\n\n\n\n<p>Ubuntu\/Debian<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>apt install cloud-init cloud-initramfs-growroot<\/code><\/pre>\n\n\n\n<p>CentOS\/RHEL\/<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>yum install cloud-init cloud-initramfs-growroot<\/code><\/pre>\n\n\n\n<p>Now, when you change your instance flavor, it should automatically resize your disk!<\/p>\n\n\n\n<p>And that brings us to a close of our guide on how to easily extend\/resize Linux root partition on OpenStack instance. If using extended\/logical partitions, it may not automatically resize. try and see!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In this tutorial, we will show you an easy way to extend Linux root partition on OpenStack instance. In OpenStack, it is possible to extend<\/p>\n","protected":false},"author":1,"featured_media":19088,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rank_math_lock_modified_date":false,"footnotes":""},"categories":[121,1885,1886],"tags":[7278,7280,7279,7277,7276],"class_list":["post-14461","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-howtos","category-cloud-compute","category-openstack","tag-cloud-init-disk-resize-openstack","tag-cloud-initramfs-growroot","tag-clpud-init","tag-extend-openstack-instance-disk","tag-resize-openstack-instance-disk","generate-columns","tablet-grid-50","mobile-grid-100","grid-parent","grid-50","resize-featured-image"],"_links":{"self":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts\/14461"}],"collection":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/comments?post=14461"}],"version-history":[{"count":27,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts\/14461\/revisions"}],"predecessor-version":[{"id":20891,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts\/14461\/revisions\/20891"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/media\/19088"}],"wp:attachment":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/media?parent=14461"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/categories?post=14461"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/tags?post=14461"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}