Hi,
I would like to request a feature freeze exception for "Component
registry improvements" feature [0]
It's related only with components and hasn't any impact on other Fuel
parts. We have 2 patches [1], [2] which currently on review but
blocked with CI issue due separation of fuel-web and
Hi fuelers,
We want to throw KVM/QEMU options from Wizard and instead of them leave
only one: Libvirt [0]. Libvirt option enables QEMU by default and there are
still be possibility to change it on KVM in settings. It looks more
logically because both QEMU\KVM are options for libvirt which manage
Hi fuelers,
Currently we are working on feature component registry [1] which should
help us to prevent not logical compositions of different components in
wizard tab during cluster(environment) creation. Now we have a mechanizm
of 'restrictions' which is not flexible for components provided by
Actually it's an old issue
https://blueprints.launchpad.net/fuel/+spec/plugin-manager-as-separate-service
On 10/09/2015 11:53 AM, Sergii Golovatiuk wrote:
+1 to Roman.
--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser
On Fri, Oct 9, 2015 at 10:45 AM, Roman Prykhodchenko
Samuel,
AFAIK labels will not be related to tasks, it's just marks for filtering
nodes.
What roles means for you?
we have tasks (A, B, C, D) and on some nodes tasks A B D should be
executed, on some B C etc. So plugin can provide specials marks or tags or
sets (we call it roles) and link
tasks
to compute node 3. Then in the plugin
deployment moduel I would be able to setup a az called az1 with compute
nodes 1 and 2 and a az called az2 with compute node 3. It is not custom
role as these nodes are compute.
regards
Samuel
2015-06-24 20:20 GMT+02:00 Andriy Popovych apopov...@mirantis.com
