{"id":5557,"date":"2021-07-29T08:00:42","date_gmt":"2021-07-29T15:00:42","guid":{"rendered":"https:\/\/www.www.pogolinux.com\/blog\/?p=5557"},"modified":"2026-10-13T17:01:33","modified_gmt":"2026-10-14T00:01:33","slug":"ceph-storage-cluster-scale-up-versus-scale-out","status":"publish","type":"post","link":"https:\/\/www.pogolinux.com\/blog\/ceph-storage-cluster-scale-up-versus-scale-out\/","title":{"rendered":"How to Choose Between Scale-up Open ZFS vs. Scale-out Ceph Storage Clusters"},"content":{"rendered":"<p>Many enterprise and midsized organizations are evaluating Ceph to address the exponential rise in data created outside the data center. However, deploying, managing and administering a large-scale storage cluster infrastructure can be daunting, even for an experienced organization.<\/p>\n<p><a href=\"https:\/\/www.pogolinux.com\/blog\/why-ceph-storage-cluster-data-center-cloud-edge-computing\/\">Ceph&#8217;s elastic architecture<\/a> features the ability to expand a storage cluster by simply adding or removing hardware \u2013 even while the system is online or under a heavy load. As a result, efficiently scaling a Ceph hardware architecture is critical to reduce overspending while maintaining the ability to accommodate peak capacity and performance requirements in distributed workloads, such as that artificial intelligence, dynamic cloud, IoT and edge computing.<\/p>\n<p><em>Researching Ceph storage cluster solutions to achieve new levels of performance and efficiency? Here&#8217;s what data center administrators need to know to evaluate <a href=\"https:\/\/www.pogolinux.com\/products\/osnexus\/overview\" target=\"_blank\" rel=\"noopener noreferrer\">OSNEXUS object storage solutions<\/a>. Questions? Drop us an email at <a href=\"mailto:sales@www.pogolinux.com\">sales@www.pogolinux.com<\/a><\/em><\/p>\n<p><a href=\"https:\/\/www.brighttalk.com\/webcast\/12587\/545266\" target=\"_blank\" rel=\"noopener noreferrer nofollow\"><img loading=\"lazy\" decoding=\"async\" class=\"alignright wp-image-5941 size-full\" src=\"https:\/\/www.pogolinux.com\/blog\/wp-content\/uploads\/2022\/04\/storage-events_22-Q2-webinar-multi-tenant-architecture-object-storage.jpg\" alt=\"\" width=\"725\" height=\"300\"><\/a><\/p>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_89 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/www.pogolinux.com\/blog\/ceph-storage-cluster-scale-up-versus-scale-out\/#%E2%9A%96%EF%B8%8F_Choosing_Scale-up_vs_Scale-out_Architectures\" >&#x2696;&#xfe0f; Choosing Scale-up vs. Scale-out Architectures<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/www.pogolinux.com\/blog\/ceph-storage-cluster-scale-up-versus-scale-out\/#%E2%9A%A1_QuantaStor_Ceph_Storage_Clusters\" >&#x26a1; QuantaStor Ceph Storage Clusters<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/www.pogolinux.com\/blog\/ceph-storage-cluster-scale-up-versus-scale-out\/#%F0%9F%93%8B_Expansion_Considerations\" >&#x1f4cb; Expansion Considerations<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/www.pogolinux.com\/blog\/ceph-storage-cluster-scale-up-versus-scale-out\/#%F0%9F%93%88_Scale-out_Architecture_Benefits\" >&#x1f4c8; Scale-out Architecture Benefits<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/www.pogolinux.com\/blog\/ceph-storage-cluster-scale-up-versus-scale-out\/#%F0%9F%93%8A_Scale-up_Cluster_Benefits\" >&#x1f4ca; Scale-up Cluster Benefits<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/www.pogolinux.com\/blog\/ceph-storage-cluster-scale-up-versus-scale-out\/#Choosing_an_Ceph_Storage_Cluster_Management_Solution\" >Choosing an Ceph Storage Cluster Management Solution<\/a><\/li><\/ul><\/li><\/ul><\/nav><\/div>\n<h2 style=\"font-size: 22px; line-height: 175%;\"><span class=\"ez-toc-section\" id=\"%E2%9A%96%EF%B8%8F_Choosing_Scale-up_vs_Scale-out_Architectures\"><\/span>&#x2696;&#xfe0f; Choosing Scale-up vs. Scale-out Architectures<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p style=\"margin-bottom: 10px;\">Pogo Linux has worked with many IT departments who have turned to Ceph as a highly-available, open source storage cluster solution to expand distributed storage environments on-premises, on public and private clouds, and at the edge. In that process, we&#8217;ve identified key tradeoffs of scale-up vs. scale-out approaches to help data center operators select the best software and hardware architecture for various workload and services environments.<\/p>\n<p style=\"margin-bottom: 10px;\">In this article, we&#8217;ll share some of that expertise, by explaining the different approaches to a successful software-defined storage strategy \u2013 whether that&#8217;s scale-up, scale-out, or a combination of the two \u2013 as both options have technical merit based on individual use-case.<\/p>\n<p style=\"margin-bottom: 10px;\">To begin, we look at the budget, capacity, performance, storage protocol and high-availability requirements for each workload and match that to a best fit for scale-up or scale-out storage cluster options:<\/p>\n<h3><img loading=\"lazy\" decoding=\"async\" class=\"wp-image-5676 size-full alignleft\" src=\"https:\/\/www.pogolinux.com\/blog\/wp-content\/uploads\/2021\/07\/diagram-quantastor-scaled-architecture.jpg\" alt=\"\" width=\"725\" height=\"125\"><\/h3>\n<p>&nbsp;<\/p>\n<p><em><span style=\"text-decoration: underline;\">A scale-up cluster vertically scales<\/span><\/em>, like a traditional SAN\/NAS file system (file, block), by adding hardware resources (storage media and expansion enclosures) to a two server configuration. They provide a compact and cost-effective solution that is <span style=\"font-weight: bold;\">ideal for workloads with performance requirements up to 3GB\/sec and capacity up to 2 petabytes per storage pool.<\/span><\/p>\n<p>Conversely, <em><span style=\"text-decoration: underline;\">a scale-out cluster horizontally scales<\/span><\/em> across racks while delivering file, block and object storage. These systems expand by adding server nodes, storage media and\/or storage enclosures (JBODs\/JBOFs). Scale-out architectures provide a single namespace so that all capacity can be accessed via a single NAS folder or S3-compatible bucket.<\/p>\n<p>This architecture has the benefit of scaling performance and capacity as additional servers and storage media are added to the cluster. As such, scale-out architectures are <span style=\"font-weight: bold;\">ideal for object storage and use-cases that need unbound capacity and performance<\/span> to meet the needs of large-scale HPC, research archives, or CDN&#8217;s that require <span style=\"font-weight: bold;\">the ability to scale to 100 petabytes or more<\/span>.<\/p>\n<h2 style=\"font-size: 22px; line-height: 175%;\"><span class=\"ez-toc-section\" id=\"%E2%9A%A1_QuantaStor_Ceph_Storage_Clusters\"><\/span>&#x26a1; QuantaStor Ceph Storage Clusters<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Fortunately, the OSNEXUS QuantaStor software-defined storage (SDS) platform supports both scale-up (<em>OpenZFS<\/em>) and scale-out (<em>Ceph<\/em>) architectures, and provides the fastest way for organizations to start small and grow to their storage environment to hyperscale size with ease.<\/p>\n<p>The QuantaStor platform bare-metal installs on each storage server, either as an upgrade for RHEL\/CentOS 8, or as an all-in-one, bare-metal ISO installed on Ubuntu LTS. Deploying new storage clusters, creating storage pools for file, block and object storage has never been easier, and can be done completely via the QuantaStor web user interface in minutes with no prior Linux or Ceph experience.<\/p>\n<ul>\n<li><strong>Storage Grid<\/strong> \u2013 The QuantaStor storage grid simplifies management by combining storage servers into a &#8220;grid&#8221; so that they can be collectively managed across sites as one.<\/li>\n<li><strong>Security<\/strong> \u2013 More importantly, the storage grid technology makes it easy for organizations to implement strong NIST complaint security enforcement practices for hybrid cloud strategies.<\/li>\n<li><strong>Management<\/strong> \u2013 Where alternative storage solutions offer a simple dashboard, QuantaStor provides a comprehensive web management interface that&#8217;s simultaneously accessible from all systems within a given storage grid with no additional software to install.<\/li>\n<\/ul>\n<h2 style=\"font-size: 22px; line-height: 175%;\"><span class=\"ez-toc-section\" id=\"%F0%9F%93%8B_Expansion_Considerations\"><\/span>&#x1f4cb; Expansion Considerations<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p style=\"margin-bottom: 10px;\">QuantaStor supports all major storage media types (NVMe, eSATA, NL-SAS) to enable easy and cost-effective expansion of scale-up or scale-out storage cluster environments.<\/p>\n<ul>\n<li><strong>Grow Capacity<\/strong> \u2013 For capacity-focused architectures, add high-density JBOD expansion enclosures directly on the network or direct-attached storage (DAS) systems with SAS-SATA interfaces to any server node appliance.<\/li>\n<li><strong>Increase Performance<\/strong> \u2013 For performance-built architectures, add all-flash storage via NVMe-over-Fabrics (NVMe-oF) or SAS-based expansion enclosures.<\/li>\n<\/ul>\n<p>QuantaStor servers within the storage grid can be comprised of a heterogeneous mix of hardware from different OEM vendors to deliver unprecedented hardware flexibility and agility to expand. Storage grids may also include multiple independent scale-up and scale-out clusters using a mix of storage media types, making it easy to deploy storage pools to meet specific workloads.<\/p>\n<h3><img loading=\"lazy\" decoding=\"async\" class=\"wp-image-5678 size-full alignleft\" src=\"https:\/\/www.pogolinux.com\/blog\/wp-content\/uploads\/2021\/07\/21-Q2-blog-article-framework_quantastor_multisite-locations.jpg\" alt=\"\" width=\"725\" height=\"400\"><\/h3>\n<h2 style=\"font-size: 22px; line-height: 175%;\"><span class=\"ez-toc-section\" id=\"%F0%9F%93%88_Scale-out_Architecture_Benefits\"><\/span>&#x1f4c8; Scale-out Architecture Benefits<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p style=\"margin-bottom: 10px;\">The concept of horizontally &#8216;scaling out&#8217; the hardware architecture means <span style=\"text-decoration: underline;\"><em>adding more components to the solution in parallel to spread out a load<\/em><\/span>. <a href=\"https:\/\/www.pogolinux.com\/products\/osnexus\/scale-out-designer\" target=\"_blank\" rel=\"noopener noreferrer\">Scale-out SAN\/NAS clusters<\/a> are unified storage platform (file, block, object), designed to <strong>grow in performance with unbound capacity<\/strong> by adding more server nodes to the cluster.<\/p>\n<h3><img loading=\"lazy\" decoding=\"async\" class=\"wp-image-5599 size-full alignleft\" src=\"https:\/\/www.pogolinux.com\/blog\/wp-content\/uploads\/2021\/04\/21-Q2-blog-article-framework_quantastor_object-storage.jpg\" alt=\"f\" width=\"725\" height=\"400\" \/><\/h3>\n<p>Without capacity constraints, scale-out configurations can keep scaling and are more versatile than scale-up solutions, as they provide simultaneous support for file, block and S3-compatible object storage environments.<\/p>\n<p>In single \u2018shared-nothing\u2019 storage design, QuantaStor users can aggregate storage from multiple appliances to manage a broad range of applications, including OpenStack cloud deployments.<\/p>\n<ul>\n<li><strong>Storage Protocols<\/strong> \u2013 QuantaStor integrates with standard Ceph 14\/15\/16 storage technology to support all file (NFS, SMB, CephFS), block (iSCSI, FC, NVMe-oF, RBD) and object storage (S3-compatible) storage protocols.<\/li>\n<li><strong>Architecture<\/strong> \u2013 A scale-up cluster storage architecture is generally composed of 4 or more head-nodes that combine compute, networking and storage resources that are configured for high-availability (active\/active replication).<\/li>\n<li><strong> Scalability<\/strong> \u2013 The QuantaStor storage grid expands to <span style=\"text-decoration: underline;\"><em>over 100 petabytes per storage grid<\/em><\/span>.<\/li>\n<li><strong>Expansion<\/strong> \u2013 Grow capacity by adding JBOD-JBOF expansion enclosures directly on the network via composable fabric (NVMe-oF RDMA), or DAS systems.<\/li>\n<li><strong>High-Availability<\/strong> \u2013 Scale-out architecture are implicitly highly-available at a file-system level with erasure-coding and replica-based data distribution technology to enable high-availability and fault-tolerance. At the same time, QuantaStor&#8217;s cluster VIF management technology ensures continuous access to NFS, SMB, iSCSI and NVMe-oF clients, while FC ALUA is used to provide continuous availability to FC connected hosts.<\/li>\n<\/ul>\n<p><em><strong>Upfront Cost<\/strong><\/em> \u2013 In terms of total hardware deployed, this initial higher-cost investment \u2013 coupled with server and networking port add-ons \u2013 is much greater than a scale-up configurations. The larger footprint to get started is the primary challenge to deploying a scale-out Ceph-based QuantaStor cluster architecture.<\/p>\n<h2 style=\"font-size: 22px; line-height: 175%;\"><span class=\"ez-toc-section\" id=\"%F0%9F%93%8A_Scale-up_Cluster_Benefits\"><\/span>&#x1f4ca; Scale-up Cluster Benefits<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p style=\"margin-bottom: 10px;\">The concept of vertically &#8216;scaling up&#8217; the hardware architecture means <span style=\"text-decoration: underline;\"><em>making the solution larger or faster to handle a greater load<\/em><\/span>. <a href=\"https:\/\/www.pogolinux.com\/products\/osnexus\/scale-up-designer\" target=\"_blank\" rel=\"noopener noreferrer\">Scale-up storage clusters<\/a> are traditional SAN\/NAS for file and block storage, designed to <strong>grow in performance and capacity under 4 petabytes by adding hardware resources (compute, networking, storage) to a cluster<\/strong>.<\/p>\n<p style=\"margin-bottom: 10px;\">In a lower-cost, compact footprint, QuantaStor users can aggregate storage from multiple appliances to support group shares in a global namespace, manage unified storage environments, or automation data replication.<\/p>\n<ul>\n<li><strong>Storage Protocols<\/strong> \u2013 QuantaStor scale-up storage configurations integrate with <span style=\"text-decoration: underline;\"><em>OpenZFS storage technology<\/em><\/span> to deliver file (NFS\/SMB) and block (iSCSI, FC, NVMe-oF TCP) storage capabilities.<\/li>\n<li><strong>Architecture<\/strong> \u2013 Scale-up clusters are composed of 2 or more QuantaStor servers that manage one (or more) storage pools that can dynamically move between servers (head-node controllers) for high-availability.<\/li>\n<li><strong>Scalability<\/strong> \u2013 The QuantaStor storage grid expands to <span style=\"text-decoration: underline;\"><em>over 100 petabytes per storage grid<\/em><\/span>, and may be comprised of scale-up and scale-out storage pools.<\/li>\n<li><strong> Expansion<\/strong> \u2013 Add JBOF-JBOD expansion enclosures via DAS or NVMe-oF to any server \u2013 <span style=\"text-decoration: underline;\"><em>up to 600+ devices, up to 8 petabytes per cluster<\/em><\/span>.<\/li>\n<li><strong>High-Availability<\/strong> \u2013 Scale-up architecture uses head-node controllers configured for I\/O fencing and highly-parallelized HA failover system to ensures automatic failover of ZFS-based storage pools. At the same time, remote replication schedules make it easy to replicate file and block storage on the storage grid. Using HA failover and data replication, storage pools can be automatically moved between QuantaStor appliances.<\/li>\n<li><strong>Limitations<\/strong> \u2013 Scale-up configurations are limited by the bandwidth of server architecture in the cluster. Using 100GbE and fast storage media most use cases may be addressed, but workloads requiring rack-scale and multi-rack configurations often benefit from a single namespace scale-out design.<\/li>\n<\/ul>\n<p><em><strong>Upfront Cost<\/strong><\/em> \u2013 For solution requirements less than 2 petabytes, the compact footprint of a scale-up architecture is more cost-effective than an equivalent scale-out configuration. In terms of total hardware deployed, this lower-cost investment to get started is the primary benefit to deploying a scale-up OpenZFS-based QuantaStor cluster.<\/p>\n<p style=\"text-align: center;\"><iframe loading=\"lazy\" src=\"https:\/\/www.youtube.com\/embed\/VqFXk0AqdJ8\" width=\"560\" height=\"315\" frameborder=\"0\" allowfullscreen=\"allowfullscreen\"><span data-mce-type=\"bookmark\" style=\"display: inline-block; width: 0px; overflow: hidden; line-height: 0;\" class=\"mce_SELRES_start\">\ufeff<\/span><\/iframe><\/p>\n<h3><span class=\"ez-toc-section\" id=\"Choosing_an_Ceph_Storage_Cluster_Management_Solution\"><\/span>Choosing an Ceph Storage Cluster Management Solution<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Low latency or high transfer rates are of little benefit if they swamp the target application. While these systems generate IOPS approaching the millions, the reality is that there are very few workloads that require more than the performance of these systems. However, there is an emerging class of workloads that can take advantage of all the performance and low latency of an end-to-end NVMe system.<\/p>\n<p>If you&#8217;d like to learn more about how to maximize your data center infrastructure by up to 90% while minimizing its footprint, give us a call at <strong>(888) 828-7646<\/strong>, email us at <a href=\"mailto:sales@www.pogolinux.com\">sales@www.pogolinux.com<\/a> or <a href=\"https:\/\/www.pogolinux.com\/blog\/book-meeting\/\">book a time calendar<\/a> to speak. We&#8217;ve helped organizations of all sizes deploy composable solutions for just about every IT budget.<\/p>\n<p><a href=\"https:\/\/www.pogolinux.com\/products\/osnexus\/overview\" target=\"_blank\" rel=\"noopener noreferrer\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft wp-image-5603 size-full\" src=\"https:\/\/www.pogolinux.com\/blog\/wp-content\/uploads\/2020\/12\/blog-article-footer_osnexus-quantastor-object-storage.jpg\" alt=\"\" width=\"725\" height=\"200\"><\/a><\/p>\n<p><script charset=\"utf-8\" type=\"text\/javascript\" src=\"\/\/js.hsforms.net\/forms\/shell.js\"><\/script><br \/>\n<script>\n  hbspt.forms.create({\n\tregion: \"na1\",\n\tportalId: \"5988479\",\n\tformId: \"0015f2c7-3f98-4b70-98a8-8abf1e36333b\"\n});\n<\/script><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Many enterprise and midsized organizations are evaluating Ceph to address the exponential rise in data created outside the data center. However, deploying, managing and administering a large-scale storage cluster infrastructure can be daunting, even for an experienced organization. Ceph&#8217;s elastic architecture features the ability to expand a storage cluster by simply adding or removing hardware&#8230;<\/p>\n","protected":false},"author":6,"featured_media":3744,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"content-type":"","footnotes":""},"categories":[105,240],"tags":[],"class_list":["post-5557","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-object-storage","category-osnexus"],"_links":{"self":[{"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/posts\/5557","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/comments?post=5557"}],"version-history":[{"count":36,"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/posts\/5557\/revisions"}],"predecessor-version":[{"id":5945,"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/posts\/5557\/revisions\/5945"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/media\/3744"}],"wp:attachment":[{"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/media?parent=5557"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/categories?post=5557"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/tags?post=5557"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}