Not all Versioned Object Model names match their ORM counterparts

[Gorka Eguileor]

There are a couple of Versioned Objects which names do not match their ORM counterparts:

 ORM VolumeTypes -> VO VolumeType
 ORM Cgsnapshot -> VO CGSnapshot

Which makes it impossible to do automatic Versioned Object to ORM conversion.

We also have a problem with BackupImport since its real ORM counterpart is Backup, but this can be easily fixed by looking at the VO parent and getting its model.

[Sean McGinnis (sean-mcginnis)]

Unassigning due to no activity.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/576389

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/576389
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=e396560f33cd97ca1609b19e7087f746983d5928
Submitter: Zuul
Branch: master

commit e396560f33cd97ca1609b19e7087f746983d5928
Author: wanghao <email address hidden>
Date: Tue Jun 19 14:53:56 2018 +0800

    Keep ORM names matching their VO counterparts

    Now cinder had some Versioned Objects which names do not
    match their ORM counterparts. In method: get_model_for_versioned_object,
    we handles those exceptions.

    This patch fix this issue to keep the names match.

    Change-Id: Icf709d87be99df95e5b52204032b730cd790096c
    Closes-Bug: #1493112

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/cinder 13.0.0.0b3 development milestone.