Rename Parallels Cloud Server to Virtuozzo¶
Within Parallels company rebranding, Parallels Cloud Server product, whose support was merged in Kilo, was renamed to Virtuozzo 1. Moreover, Parallels Service provider business was renamed and became Odin 2. Thus, there was no Parallels name left for this product.
We need to address this change in nova/libvirt driver accordingly to avoid confusion of users and make things be actual.
It is worth noting though, that Virtuozzo is based on opensource and free OpenVz project and supporting Virtuozzo means supporting OpenVz also.
No priority defined for this change yet.
Libvirt section in nova.conf will change
vz. We set minimal required version of libvirt to work with
virt_type to 1.3.0 since it is the first version that supports ‘vz’ uri.
The code will hold both names:
vz for next release
M release cycle there should be left only
We can leave it as is and have
parallels virt_type but this approach
will leave confusion for user forever.
Data model impact¶
REST API impact¶
Other end user impact¶
Other deployer impact¶
Deployer can use libvirt virt_type
parallels in Liberty release cycle,
but will have to switch to
vz in next
M release. This action is
going to be fulfilled by Virtuozzo deployment system.
Primary assignee: Maxim Nestratov <firstname.lastname@example.org>
Test cases. Implementation: https://review.openstack.org/#/c/184311/
Unit test cases need to be updated. Already addressed in pending implementation.
OpenStack Configuration Reference. http://docs.openstack.org/kilo/config-reference/content/compute-nova-conf.html
OpenStack Configuration Reference. http://docs.openstack.org/kilo/config-reference/content/list-of-compute-config-options.html