<?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 How does price calculation work for OpenStack VMs in HPE Morpheus Enterprise Software</title>
    <link>https://community.hpe.com/t5/hpe-morpheus-enterprise-software/how-does-price-calculation-work-for-openstack-vms/m-p/7250217#M3391</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;Was working on a customer use case and thought would share it here. Hope will be useful to some of you &lt;IMG src="https://emoji.discourse-cdn.com/twitter/slightly_smiling_face.png?v=12" title=":slightly_smiling_face:" class="emoji" alt=":slightly_smiling_face:" loading="lazy" width="20" height="20" /&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Use Case:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;When creating the VM on OpenStack, the Price shown was incorrect.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Analysis:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;We performed a test VM deployment using the OpenStack service plan “dg-openstack-test-flavor” which had a custom OpenStack Price set named “DG_OpenStack_Test” as attached below.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;&lt;DIV class="lightbox-wrapper"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="DG_OpenStack_Test"&gt;&lt;img src="https://community.hpe.com/t5/image/serverpage/image-id/150407i38C7576651CAA15F/image-size/large?v=v2&amp;amp;px=2000" role="button" title="e3c80eca4dfd9c7831078b2c6c63dd404cbb5d73.png" alt="e3c80eca4dfd9c7831078b2c6c63dd404cbb5d73.png" /&gt;&lt;/span&gt;&lt;/DIV&gt;&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Initially, “DG_OpenStack_Test” price-set had following prices attached.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;&lt;DIV class="lightbox-wrapper"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Non_Working_Price_Set"&gt;&lt;img src="https://community.hpe.com/t5/image/serverpage/image-id/150474iEAB193AAA3085B62/image-size/large?v=v2&amp;amp;px=2000" role="button" title="622433c8c0ad2d6e8bcdf6d284a855b941a3ce4c.png" alt="622433c8c0ad2d6e8bcdf6d284a855b941a3ce4c.png" /&gt;&lt;/span&gt;&lt;/DIV&gt;&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Prices:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;vCPU – $1/MB/Month&lt;BR /&gt;
RAM – $1/MB/Month&lt;BR /&gt;
Storage – $1/GB/Month&lt;/P&gt;
&lt;P&gt;So, when we deployed the VM using this service plan, we noticed that it was not calculating the price for “Storage”.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Resources Used:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;vCPU – 1&lt;BR /&gt;
RAM – 2048 MB&lt;BR /&gt;
Storage – 10 GB&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Price Calculation:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;vCPU + RAM = 2049 =&amp;gt; $2049&lt;/P&gt;
&lt;P&gt;Storage calculation (10 GB) was missing. So, the actual total should have been $2050.&lt;/P&gt;
&lt;P&gt;We then realised that the Standard disk type price is probably not something OpenStack would look for but rather “Openstack Volume” and “Openstack Local” disk type prices.&lt;/P&gt;
&lt;P&gt;Considering this we added prices for “Openstack Volume” and “Openstack Local” disk types.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;&lt;DIV class="lightbox-wrapper"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Working_Price_Set"&gt;&lt;img src="https://community.hpe.com/t5/image/serverpage/image-id/149617i7CE7D9842D9C3A0E/image-size/large?v=v2&amp;amp;px=2000" role="button" title="4b35d19093f12d6ff4bf8db029d0d4d931434fb3.png" alt="4b35d19093f12d6ff4bf8db029d0d4d931434fb3.png" /&gt;&lt;/span&gt;&lt;/DIV&gt;&lt;P&gt;&lt;/P&gt;
&lt;P&gt;We then created a new VM with the updated prise-set and selected a “volume” type on instance creation and this time the price shown was correct as it calculated the price for storage.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;New Price Calculation:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;1 vCPU + 2048 RAM + 10 GB = 2050 =&amp;gt; $2050&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Note:&lt;/STRONG&gt; When using Morpheus provided “Custom OpenStack Price Set” the prices will be calculated correctly as it already has the required prices for disk type.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;&lt;DIV class="lightbox-wrapper"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Custom_OpenStack_Price_Set"&gt;&lt;img src="https://community.hpe.com/t5/image/serverpage/image-id/149764iEE29367BA1E3C71E/image-size/large?v=v2&amp;amp;px=2000" role="button" title="dc783a9d0f1a1faeed95344ac6b06d3b80941277.png" alt="dc783a9d0f1a1faeed95344ac6b06d3b80941277.png" /&gt;&lt;/span&gt;&lt;/DIV&gt;&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 24 May 2023 16:35:26 GMT</pubDate>
    <dc:creator>dgaharwar</dc:creator>
    <dc:date>2023-05-24T16:35:26Z</dc:date>
    <item>
      <title>How does price calculation work for OpenStack VMs</title>
      <link>https://community.hpe.com/t5/hpe-morpheus-enterprise-software/how-does-price-calculation-work-for-openstack-vms/m-p/7250217#M3391</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;Was working on a customer use case and thought would share it here. Hope will be useful to some of you &lt;IMG src="https://emoji.discourse-cdn.com/twitter/slightly_smiling_face.png?v=12" title=":slightly_smiling_face:" class="emoji" alt=":slightly_smiling_face:" loading="lazy" width="20" height="20" /&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Use Case:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;When creating the VM on OpenStack, the Price shown was incorrect.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Analysis:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;We performed a test VM deployment using the OpenStack service plan “dg-openstack-test-flavor” which had a custom OpenStack Price set named “DG_OpenStack_Test” as attached below.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;&lt;DIV class="lightbox-wrapper"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="DG_OpenStack_Test"&gt;&lt;img src="https://community.hpe.com/t5/image/serverpage/image-id/150407i38C7576651CAA15F/image-size/large?v=v2&amp;amp;px=2000" role="button" title="e3c80eca4dfd9c7831078b2c6c63dd404cbb5d73.png" alt="e3c80eca4dfd9c7831078b2c6c63dd404cbb5d73.png" /&gt;&lt;/span&gt;&lt;/DIV&gt;&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Initially, “DG_OpenStack_Test” price-set had following prices attached.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;&lt;DIV class="lightbox-wrapper"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Non_Working_Price_Set"&gt;&lt;img src="https://community.hpe.com/t5/image/serverpage/image-id/150474iEAB193AAA3085B62/image-size/large?v=v2&amp;amp;px=2000" role="button" title="622433c8c0ad2d6e8bcdf6d284a855b941a3ce4c.png" alt="622433c8c0ad2d6e8bcdf6d284a855b941a3ce4c.png" /&gt;&lt;/span&gt;&lt;/DIV&gt;&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Prices:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;vCPU – $1/MB/Month&lt;BR /&gt;
RAM – $1/MB/Month&lt;BR /&gt;
Storage – $1/GB/Month&lt;/P&gt;
&lt;P&gt;So, when we deployed the VM using this service plan, we noticed that it was not calculating the price for “Storage”.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Resources Used:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;vCPU – 1&lt;BR /&gt;
RAM – 2048 MB&lt;BR /&gt;
Storage – 10 GB&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Price Calculation:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;vCPU + RAM = 2049 =&amp;gt; $2049&lt;/P&gt;
&lt;P&gt;Storage calculation (10 GB) was missing. So, the actual total should have been $2050.&lt;/P&gt;
&lt;P&gt;We then realised that the Standard disk type price is probably not something OpenStack would look for but rather “Openstack Volume” and “Openstack Local” disk type prices.&lt;/P&gt;
&lt;P&gt;Considering this we added prices for “Openstack Volume” and “Openstack Local” disk types.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;&lt;DIV class="lightbox-wrapper"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Working_Price_Set"&gt;&lt;img src="https://community.hpe.com/t5/image/serverpage/image-id/149617i7CE7D9842D9C3A0E/image-size/large?v=v2&amp;amp;px=2000" role="button" title="4b35d19093f12d6ff4bf8db029d0d4d931434fb3.png" alt="4b35d19093f12d6ff4bf8db029d0d4d931434fb3.png" /&gt;&lt;/span&gt;&lt;/DIV&gt;&lt;P&gt;&lt;/P&gt;
&lt;P&gt;We then created a new VM with the updated prise-set and selected a “volume” type on instance creation and this time the price shown was correct as it calculated the price for storage.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;New Price Calculation:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;1 vCPU + 2048 RAM + 10 GB = 2050 =&amp;gt; $2050&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Note:&lt;/STRONG&gt; When using Morpheus provided “Custom OpenStack Price Set” the prices will be calculated correctly as it already has the required prices for disk type.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;&lt;DIV class="lightbox-wrapper"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Custom_OpenStack_Price_Set"&gt;&lt;img src="https://community.hpe.com/t5/image/serverpage/image-id/149764iEE29367BA1E3C71E/image-size/large?v=v2&amp;amp;px=2000" role="button" title="dc783a9d0f1a1faeed95344ac6b06d3b80941277.png" alt="dc783a9d0f1a1faeed95344ac6b06d3b80941277.png" /&gt;&lt;/span&gt;&lt;/DIV&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 24 May 2023 16:35:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-morpheus-enterprise-software/how-does-price-calculation-work-for-openstack-vms/m-p/7250217#M3391</guid>
      <dc:creator>dgaharwar</dc:creator>
      <dc:date>2023-05-24T16:35:26Z</dc:date>
    </item>
    <item>
      <title>Re: How does price calculation work for OpenStack VMs</title>
      <link>https://community.hpe.com/t5/hpe-morpheus-enterprise-software/how-does-price-calculation-work-for-openstack-vms/m-p/7250218#M3392</link>
      <description>&lt;P&gt;Thanks &lt;A class="mention" href="https://community.hpe.com/u/dgaharwar"&gt;@dgaharwar&lt;/A&gt; !&lt;/P&gt;</description>
      <pubDate>Thu, 25 May 2023 09:05:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-morpheus-enterprise-software/how-does-price-calculation-work-for-openstack-vms/m-p/7250218#M3392</guid>
      <dc:creator>cdtaylor</dc:creator>
      <dc:date>2023-05-25T09:05:45Z</dc:date>
    </item>
  </channel>
</rss>

