abh1sar commented on PR #12758: URL: https://github.com/apache/cloudstack/pull/12758#issuecomment-4073216241
> I have yet to add it to the GUI, if you have any suggestions for the GUI design, you are free to give your opinion. The GUI for the native backup offerings will be added in the future. > I would definitely not want two kinds of backup offering displayed separately in the UI. The way this could be approached is to have a unified view of two offerings with a `type` field differentiating between the two. The create offering form fields can be populated depending on the type chosen. But if we are having a unified view in the UI, why have separate APIs at all? the backup offering API itself can have a `type` fields and all the extra fields which are required. > A provider is native if the backup implementation is made by ACS. Thus, the current native providers would be NAS and KNIB. Veeam and Networker are external providers. > But NAS doesn't use native backup offerings, so this is still confusing. > They are used to configure the details that would be configured in the backup provider if it was an external provider, such as Veeam for example. > I don't think we are gaining much from defining a new native backup offering api. I highly recommend having a single Backup offering API and database tables. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
