RUD for MiqTemplate (or just read & update) about manageiq-api

[andyvesel]

@skateman @abellotti I was trying to update a template with PUT/PATCH requests, but it only updates attributes for local MIQ database and doesn't make any calls to Fog, so the image can't be updated on the Openstack side. Do we need it to be implemented this way?
I'm kind of stuck on this issue. So I'll appreciate any thorough and obvious details about this.

[skateman]

IMO we should somehow merge the two functionalities (i.e. the one @andyvesel created and the universal one I was trying to do) and call the openstack-specific stuff when needed.

[himdel]

What @skateman said :)

Just, 2 more points:

• please make sure you come up with an interface which can be generalized to any provider, no openstack-specific code in the API
• the UiWorker is not guaranteed to be able to communicate with any external provider, and the same goes for the API => the API call should create a task to talk to the provider

[andyvesel]

@himdel which means that CRUD code, that implemented here should be moved to main repo, it would be correct way?

[himdel]

I'm sorry, that is more of a providers question.
(I think as long as update_image exists in the core, and returns an exception unless overriden, that's fine, but...)

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 6 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions!

[martinpovolny]

Ok, so this is relevant for:

ManageIQ/manageiq-ui-classic#3944

Where we need to be able to create openstack images. Do we need an API action that can upload the image? Or just pass in a URL of it?

[martinpovolny]

Anyway it seems that for this to move forward work in needed from the core and provider (openstack) side.

[himdel]

Where we need to be able to create openstack images. Do we need an API action that can upload the image? Or just pass in a URL of it?

This was never specified, and uploading would involve uploading a multi-gig image to the api appliance, potentially moving it to a different worker appliance and only then uploading to the provider. So, a public URL might be enough. (Cc @Loicavenel, https://bugzilla.redhat.com/show_bug.cgi?id=1487114)

[mfeifer]

cc @agrare

[himdel]

The BZ was closed as WONTFIX,
closing this issue to match https://bugzilla.redhat.com/show_bug.cgi?id=1487114