VMware: image user functions for spawn()

[OpenStack Infra]

https://review.openstack.org/109754
commit f0a8517d49155d45ea2e29cf2dc12ad990711dd6
Author: Vui Lam <email address hidden>
Date: Thu Apr 24 13:57:47 2014 -0700

    VMware: image user functions for spawn()

    Refactor each mode of using cached images when configuring a newly
    created virtual machine into their own functions.

    DocImpact:
    vmware_linked_clone image property is ignored when spawning an
    image that is an ISO.

    partial-blueprint: vmware-spawn-refactor
    Change-Id: I863fc0ef644bcf579e74d6f567f14aed98a23c84

[Loic Dachary (dachary)]

Shouldn't this be closed ? The review above has been merged.

[Loic Dachary (dachary)]

nevermind... I did not understand the DocImpact relationship. Sorry for the noise :-)

[Alexandra Settle (alexandra-settle)]

Unassigning George from this bug due to inactivity. Low-hanging-fruit bugs are currently required by the Upstream University team.

Thanks,

Alex

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/239360
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=13032de2993dcb934d895307b78d1ff919fed5df
Submitter: Jenkins
Branch: master

commit 13032de2993dcb934d895307b78d1ff919fed5df
Author: Masaki Furuta <email address hidden>
Date: Mon Oct 26 16:27:41 2015 +0900

    Add note about vmware_linked_clone when spawning with ISO

    On refacrctoring on image user function for spawn(), adding reason why
    and condition where vmware_linked_clone property is ignored when
    spawning with ISO image.

    Closes-Bug: #1366325

    Change-Id: Icde3817189b64215d8203bd32217439c7a11403a
    Signed-off-by: Masaki Furuta <email address hidden>

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-manuals 15.0.0 release.