| 2015-12-15 14:37:55 |
Ruslan Khozinov |
bug |
|
|
added bug |
| 2015-12-15 14:37:55 |
Ruslan Khozinov |
attachment added |
|
when i’m choosing kvm, qemu is blocking https://bugs.launchpad.net/bugs/1526353/+attachment/4535108/+files/Screen%20Shot%202015-12-15%20at%2016.49.04.PNG |
|
| 2015-12-15 14:38:16 |
Ruslan Khozinov |
summary |
[PCE][component-registry] incompatible logic isn’t same as for fuel-core components |
[component-registry] incompatible logic isn’t same as for fuel-core components |
|
| 2015-12-15 14:38:36 |
Ruslan Khozinov |
description |
Example of component configuration:
- name: 'hypervisor:xen'
label: 'xen'
description: 'xen hyperviror'
compatible:
- name: 'hypervisor:libvirt:kvm'
incompatible:
- name: 'hypervisor:vmware'
- name: ‘hypervisor:libvirt:emu'
When I’m checking a xen hypervisor checkbox, others checkboxes are not blocked.
But when I’m checking kvm checkbox, then qemu checkbox is blocked (and vice versa).
So, I think the logic of blocking of checkboxes should be the same for core components and for plugin components.
I mean, when we check a checkbox incompatible checkboxes should be blocked. |
Example of component configuration:
- name: 'hypervisor:xen'
label: 'xen'
description: 'xen hyperviror'
compatible:
- name: 'hypervisor:libvirt:kvm'
incompatible:
- name: 'hypervisor:vmware'
- name: ‘hypervisor:libvirt:emu'
When I’m checking a xen hypervisor checkbox, others checkboxes are not blocked.
But when I’m checking kvm checkbox, then qemu checkbox is blocked (and vice versa).
So, I think the logic of blocking of checkboxes should be the same for core components and for plugin components.
I mean, when we check a checkbox incompatible checkboxes should be blocked. |
|
| 2015-12-15 14:39:47 |
Ruslan Khozinov |
description |
Example of component configuration:
- name: 'hypervisor:xen'
label: 'xen'
description: 'xen hyperviror'
compatible:
- name: 'hypervisor:libvirt:kvm'
incompatible:
- name: 'hypervisor:vmware'
- name: ‘hypervisor:libvirt:emu'
When I’m checking a xen hypervisor checkbox, others checkboxes are not blocked.
But when I’m checking kvm checkbox, then qemu checkbox is blocked (and vice versa).
So, I think the logic of blocking of checkboxes should be the same for core components and for plugin components.
I mean, when we check a checkbox incompatible checkboxes should be blocked. |
Fuel-build: 286
Example of component configuration:
- name: 'hypervisor:xen'
label: 'xen'
description: 'xen hyperviror'
compatible:
- name: 'hypervisor:libvirt:kvm'
incompatible:
- name: 'hypervisor:vmware'
- name: ‘hypervisor:libvirt:emu'
When I’m checking a xen hypervisor checkbox, others checkboxes are not blocked.
But when I’m checking kvm checkbox, then qemu checkbox is blocked (and vice versa).
So, I think the logic of blocking of checkboxes should be the same for core components and for plugin components.
I mean, when we check a checkbox incompatible checkboxes should be blocked. |
|
| 2015-12-15 14:41:32 |
Ruslan Khozinov |
attachment added |
|
I’m choosing an incompatible option with some of items https://bugs.launchpad.net/fuel/+bug/1526353/+attachment/4535109/+files/Screen%20Shot%202015-12-15%20at%2016.49.15.PNG |
|
| 2015-12-15 14:42:36 |
Ruslan Khozinov |
attachment added |
|
The xen option is blocked only if I’m choosing incompatible option https://bugs.launchpad.net/fuel/+bug/1526353/+attachment/4535111/+files/Screen%20Shot%202015-12-15%20at%2016.49.26.PNG |
|
| 2015-12-15 15:22:12 |
Andriy Popovych |
fuel: assignee |
Partner Centric Engineering (fuel-partner-engineering) |
Andriy Popovych (popovych-andrey) |
|
| 2015-12-15 17:17:56 |
Ilya Kutukov |
fuel: importance |
Undecided |
High |
|
| 2015-12-15 17:17:59 |
Ilya Kutukov |
fuel: status |
New |
Confirmed |
|
| 2015-12-15 22:34:49 |
Ruslan Khozinov |
description |
Fuel-build: 286
Example of component configuration:
- name: 'hypervisor:xen'
label: 'xen'
description: 'xen hyperviror'
compatible:
- name: 'hypervisor:libvirt:kvm'
incompatible:
- name: 'hypervisor:vmware'
- name: ‘hypervisor:libvirt:emu'
When I’m checking a xen hypervisor checkbox, others checkboxes are not blocked.
But when I’m checking kvm checkbox, then qemu checkbox is blocked (and vice versa).
So, I think the logic of blocking of checkboxes should be the same for core components and for plugin components.
I mean, when we check a checkbox incompatible checkboxes should be blocked. |
Fuel-build: 286
Example of component configuration:
- name: 'hypervisor:xen'
label: 'xen'
description: 'xen hyperviror'
compatible:
- name: 'hypervisor:libvirt:kvm'
incompatible:
- name: 'hypervisor:vmware'
- name: ‘hypervisor:libvirt:qemu'
When I’m checking a xen hypervisor checkbox, others checkboxes are not blocked.
But when I’m checking kvm checkbox, then qemu checkbox is blocked (and vice versa).
So, I think the logic of blocking of checkboxes should be the same for core components and for plugin components.
I mean, when we check a checkbox incompatible checkboxes should be blocked. |
|
| 2015-12-16 21:01:22 |
OpenStack Infra |
fuel: status |
Confirmed |
In Progress |
|
| 2016-02-01 08:51:12 |
OpenStack Infra |
fuel: assignee |
Andriy Popovych (popovych-andrey) |
Bulat Gaifullin (bgaifullin) |
|
| 2016-02-01 09:21:29 |
OpenStack Infra |
fuel: status |
In Progress |
Fix Committed |
|
| 2016-02-01 12:22:25 |
Andriy Popovych |
fuel: assignee |
Bulat Gaifullin (bgaifullin) |
Andriy Popovych (popovych-andrey) |
|
| 2016-02-02 14:41:55 |
Ilya Bumarskov |
tags |
area-partners |
area-partners area-pce-vcenter |
|
| 2016-02-03 13:57:21 |
Olesia Tsvigun |
fuel: status |
Fix Committed |
Fix Released |
|
