<?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 Feature request, official feature request thread? in HPE Morpheus Enterprise</title>
    <link>https://community.hpe.com/t5/hpe-morpheus-enterprise/feature-request-official-feature-request-thread/m-p/7256596#M5091</link>
    <description>&lt;P&gt;Is there an official feature request section?&lt;/P&gt;&lt;P&gt;1. Move VM auto-start from cloud level to VM level.&lt;/P&gt;&lt;P&gt;1.2. Should include a start order&lt;/P&gt;&lt;P&gt;It just isn't realistic to globally start or not start all VM's. There are plenty of circumstances where starting all VM's every time could be disastrous. Especially during server upgrades/migrations/testing. This functionality *seems* to be configurable on individual VM's with "virsh autostart (--disable) at CLI but this isn't realistic for your average admin and should be accessible in VMEM.&lt;/P&gt;&lt;P&gt;2. Allow "Default" Backup target, deployment archive target, virtual store image tag to be applied to local datastore&lt;/P&gt;&lt;P&gt;Currently these tags can only be applied on a File Share which requires creating an NFS share on a local host even though Morpheus can see the local data store just fine without setting up an NFS share.&lt;/P&gt;&lt;P&gt;Kind regards.&lt;/P&gt;</description>
    <pubDate>Fri, 03 Oct 2025 18:05:27 GMT</pubDate>
    <dc:creator>BretH</dc:creator>
    <dc:date>2025-10-03T18:05:27Z</dc:date>
    <item>
      <title>Feature request, official feature request thread?</title>
      <link>https://community.hpe.com/t5/hpe-morpheus-enterprise/feature-request-official-feature-request-thread/m-p/7256596#M5091</link>
      <description>&lt;P&gt;Is there an official feature request section?&lt;/P&gt;&lt;P&gt;1. Move VM auto-start from cloud level to VM level.&lt;/P&gt;&lt;P&gt;1.2. Should include a start order&lt;/P&gt;&lt;P&gt;It just isn't realistic to globally start or not start all VM's. There are plenty of circumstances where starting all VM's every time could be disastrous. Especially during server upgrades/migrations/testing. This functionality *seems* to be configurable on individual VM's with "virsh autostart (--disable) at CLI but this isn't realistic for your average admin and should be accessible in VMEM.&lt;/P&gt;&lt;P&gt;2. Allow "Default" Backup target, deployment archive target, virtual store image tag to be applied to local datastore&lt;/P&gt;&lt;P&gt;Currently these tags can only be applied on a File Share which requires creating an NFS share on a local host even though Morpheus can see the local data store just fine without setting up an NFS share.&lt;/P&gt;&lt;P&gt;Kind regards.&lt;/P&gt;</description>
      <pubDate>Fri, 03 Oct 2025 18:05:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-morpheus-enterprise/feature-request-official-feature-request-thread/m-p/7256596#M5091</guid>
      <dc:creator>BretH</dc:creator>
      <dc:date>2025-10-03T18:05:27Z</dc:date>
    </item>
    <item>
      <title>Re: Feature request, official feature request thread?</title>
      <link>https://community.hpe.com/t5/hpe-morpheus-enterprise/feature-request-official-feature-request-thread/m-p/7257308#M5106</link>
      <description>&lt;P&gt;Hey Bret - there is not but we do have people watching conversations and add suggestions to our internal engineering tool. I'll make sure what you've suggested gets reviewed.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Thanks for taking the time and apologies for the late reply as I was on vacation for a week and spent a week getting unburied from being on vacation. LOL!&lt;/P&gt;</description>
      <pubDate>Mon, 20 Oct 2025 18:35:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-morpheus-enterprise/feature-request-official-feature-request-thread/m-p/7257308#M5106</guid>
      <dc:creator>CalvinZito</dc:creator>
      <dc:date>2025-10-20T18:35:26Z</dc:date>
    </item>
  </channel>
</rss>

