<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic vCD Architecture Scale-Out in VMware vCloud Director Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-vCloud-Director/vCD-Architecture-Scale-Out/m-p/504164#M2276</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm looking at deploying a vCD environment, initially starting with just a single cell and single RabbitMQ server to gauge actual demand/use of vCD functionality. I will be using the 9.7 appliance with an embedded PSQL database. An external NFS transfer server will also be deployed. No load-balancer required as yet since we only have one cell anyway.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is can we build out an environment at a later date when we actually need to expand? For instance, deploy a single cell now and expand to 2, 3, n-number cells with a load-balancer in front. Can we do the same with RabbitMQ too? I can't seem to find any information regarding cell/environment expansion. It appears that the vCD architecture is designed to support scaling-out but just wanted to confirm.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your time!&lt;/P&gt;&lt;P&gt;Kam&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 13 May 2019 05:54:30 GMT</pubDate>
    <dc:creator>KFM</dc:creator>
    <dc:date>2019-05-13T05:54:30Z</dc:date>
    <item>
      <title>vCD Architecture Scale-Out</title>
      <link>https://communities.vmware.com/t5/VMware-vCloud-Director/vCD-Architecture-Scale-Out/m-p/504164#M2276</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm looking at deploying a vCD environment, initially starting with just a single cell and single RabbitMQ server to gauge actual demand/use of vCD functionality. I will be using the 9.7 appliance with an embedded PSQL database. An external NFS transfer server will also be deployed. No load-balancer required as yet since we only have one cell anyway.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is can we build out an environment at a later date when we actually need to expand? For instance, deploy a single cell now and expand to 2, 3, n-number cells with a load-balancer in front. Can we do the same with RabbitMQ too? I can't seem to find any information regarding cell/environment expansion. It appears that the vCD architecture is designed to support scaling-out but just wanted to confirm.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your time!&lt;/P&gt;&lt;P&gt;Kam&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 May 2019 05:54:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCloud-Director/vCD-Architecture-Scale-Out/m-p/504164#M2276</guid>
      <dc:creator>KFM</dc:creator>
      <dc:date>2019-05-13T05:54:30Z</dc:date>
    </item>
    <item>
      <title>Re: vCD Architecture Scale-Out</title>
      <link>https://communities.vmware.com/t5/VMware-vCloud-Director/vCD-Architecture-Scale-Out/m-p/504165#M2277</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Kam,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes, this is possible with the appliances. However, there are a few caveats:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. There's a known bug right now on the 9.7 appliance with SSL certs. There will be a patch available soon, but this limits the use of H5 client without a load balancer and single cell. Workaround is to utilize a load balancer, which is always used for production deployments.&lt;/P&gt;&lt;P&gt;2. RMQ is not included in the appliance, so I presume you are manually installing it post-deployment. If that's the case, carry on.&lt;/P&gt;&lt;P&gt;3. The single appliance OVA has different roles and you can always expand the cell and/or PgSQL role. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Daniel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 May 2019 12:31:32 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCloud-Director/vCD-Architecture-Scale-Out/m-p/504165#M2277</guid>
      <dc:creator>paluszekd</dc:creator>
      <dc:date>2019-05-13T12:31:32Z</dc:date>
    </item>
    <item>
      <title>Re: vCD Architecture Scale-Out</title>
      <link>https://communities.vmware.com/t5/VMware-vCloud-Director/vCD-Architecture-Scale-Out/m-p/504166#M2278</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Daniel,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It certainly does help, thank you! Sounds like we may have to deploy a LB in front of the cell. I guess it would have to be deployed anyway when we eventually deploy additional cells so no harm done doing it from the start.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 May 2019 01:46:13 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCloud-Director/vCD-Architecture-Scale-Out/m-p/504166#M2278</guid>
      <dc:creator>KFM</dc:creator>
      <dc:date>2019-05-15T01:46:13Z</dc:date>
    </item>
    <item>
      <title>Re: vCD Architecture Scale-Out</title>
      <link>https://communities.vmware.com/t5/VMware-vCloud-Director/vCD-Architecture-Scale-Out/m-p/504167#M2279</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You got it. Enjoy, let us know if you need anything else.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Daniel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 May 2019 12:42:28 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCloud-Director/vCD-Architecture-Scale-Out/m-p/504167#M2279</guid>
      <dc:creator>paluszekd</dc:creator>
      <dc:date>2019-05-15T12:42:28Z</dc:date>
    </item>
  </channel>
</rss>

