You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the VM Snapshots view, one of the buttons along side the other options in the list, there should exist a "Save as Template" option, as exists in XCP-ng Center.
On the VM view, along the top row of the buttons along side the other options, there should exist a "Save as Template" option, as exists in XCP-ng Center.
Current behavior
In the VM Snapshot view list, there is no button along side the other options to "Save as Template", as is possible with XCP-ng Center.
On the VM view, along the top row of the buttons along side the other options, there is no option to "Save as Template", as is possible with XCP-ng Center.
The text was updated successfully, but these errors were encountered:
hvilches
changed the title
[Feature Request] Give XOA ability to Create/Save Template
[Feature Request] Give XO ability to Create/Save Template
Mar 28, 2020
olivierlambert
changed the title
[Feature Request] Give XO ability to Create/Save Template
Give XO ability to Create/Save Template from snapshot
Mar 29, 2020
olivierlambert
changed the title
Give XO ability to Create/Save Template from snapshot
Create/Save Template from snapshot
Mar 29, 2020
Context
Expected behavior
On the VM Snapshots view, one of the buttons along side the other options in the list, there should exist a "Save as Template" option, as exists in XCP-ng Center.
On the VM view, along the top row of the buttons along side the other options, there should exist a "Save as Template" option, as exists in XCP-ng Center.
Current behavior
In the VM Snapshot view list, there is no button along side the other options to "Save as Template", as is possible with XCP-ng Center.
On the VM view, along the top row of the buttons along side the other options, there is no option to "Save as Template", as is possible with XCP-ng Center.
The text was updated successfully, but these errors were encountered: