+1
On Tue, Feb 21, 2017 at 4:32 PM Aleksey Kasatkin
wrote:
> +1
>
>
> Aleksey Kasatkin
>
>
> On Tue, Feb 21, 2017 at 2:25 PM, Ihor Kalnytskyi
> wrote:
>
> Hey fellow fuelers,
>
> I'd like to nominate Alexander Kislitsky to the fuel-web-core team.
> He's doing thorough review [1], participate in
Hi Nidhi,
This implemented https://blueprints.launchpad.net/fuel/+spec/dynamic-fields
blueprint provided an ability to use "text_list" and "textarea_list" UI
control types.
They are suitable for settings where the value is a list of strings.
These controls represent on UI a list of single or multi
Hello everyone,
We [Fuel UI team] are working now on UI implementation of deployment
history [1] and deployment graphs [2] features.
For our development process and covering the features by functional tests,
it is critical to extend fake Nailgun with emulation of a real deployment
execution [3].
+1
On Wed, Jun 8, 2016 at 8:52 PM Bulat Gaifullin
wrote:
> Hey Fuelers,
>
> I'd like to nominate Ilya Kutukov for the fuel-web-core team.
> Ilya`s doing good reviews with detailed feedback [1],
> and has implemented custom graph execution engine for Fuel.
> Also Ilya`s implemented new database m
+1
On Wed, Feb 24, 2016 at 4:57 PM Denis Egorenko
wrote:
> I'm not a fuel core member, but i also would like to vote +1 for Matthew.
> He's doing great job!
>
> 2016-02-24 16:02 GMT+03:00 Aleksandr Didenko :
>
>> +1
>>
>> On Wed, Feb 24, 2016 at 1:50 PM, Vladimir Kuklin
>> wrote:
>>
>>> Fellow
I support Vitaly's proposal with 'base' group name instead of 'controller'.
So, now we have the following suggestion for role list grouping:
BASE: controller, detach-* plugin roles, murano (if it will go to plugin)
COMPUTE: compute, virt, compute-vmware, ironic
STORAGE: cinder, cinder-block-device
t; This should cover all the cases even for very flexible roles allocation.
>
> On Fri, Jan 29, 2016 at 12:58 PM, Sergii Golovatiuk <
> sgolovat...@mirantis.com> wrote:
>
>> Hi,
>>
>>
>> On Fri, Jan 29, 2016 at 9:55 AM, Julia Aranovich > > wrote:
>>
Hi folks,
Our team has started a redesign of node roles panel [1] on Add Nodes/Edit
Roles screens in Fuel UI.
Currently, node roles panel takes a big part of the screen and User have to
scroll down to node list to check nodes and then scroll up again to check
roles. This becomes more actual for de
+1
On Tue, Dec 1, 2015 at 10:29 PM Sergii Golovatiuk
wrote:
> +1
>
> --
> Best regards,
> Sergii Golovatiuk,
> Skype #golserge
> IRC #holser
>
> On Tue, Dec 1, 2015 at 6:15 PM, Aleksey Kasatkin
> wrote:
>
>> +1.
>> No doubts. )
>>
>>
>> Aleksey Kasatkin
>>
>>
>> On Tue, Dec 1, 2015 at 5:49 PM,
Hi fuelers,
Currently Fuel UI team is working on blueprint [1] to give Fuel UI user an
ability to launch provisioning of environment nodes separately from
deployment (without choosing particular nodes for now).
In the process we were faced with the following issues. Some of them block
the bluepri
e fencing. A user may put IPMI credentials into
>> >> labels.
>> >> And there are more cases like that.
>> >>
>> >> Despite the original spec doesn't have this idea I propose to implement
>> >> that. Moreover, I've already di
have this functionality covered in
>> CLI
>>
>> 2015-07-23 19:46 GMT+02:00 Igor Kalnitsky :
>>
>>> Hi Julia,
>>>
>>> I'm ok with FF exception for CLI part. I don't think it can somehow
>>> decrease product quality, so as a core
Team,
I would like to request an exception from the Feature Freeze for CLI
changes of working with custom node labels added to fuelclient (fuel2) [1].
UI and Nailgun parts of the story are already merged [2].
There CLI request is being actively reviewed, the base flow is accepted.
There are minim
Samuel, I would like you to consider this proposal:
https://review.openstack.org/#/c/184076/6/specs/7.0/node-custom-attributes.rst
This is about support of custom node labels. I think plugins should be able
to assign its own labels to nodes via Nailgun API. Is it possible? Will it
suit your case?
-mode
On Thu, May 28, 2015 at 11:29 AM, Swann Croiset
wrote:
> Many thanks Julia for the quick fix!
>
> Is it possible to update my fuel master to test this patch? w/o download
> a new ISO and avoid to reinstall my env ?
>
> On Wed, May 27, 2015 at 6:04 PM, Julia Aranovich
>
__
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
--
Kind R
s (including Management and Public addresses) in the UI
> and group/sort by those addresses.
>
> --
> Best regards,
> Oleg Gelbukh
> Mirantis Labs
>
> On Sat, Feb 14, 2015 at 11:27 AM, Julia Aranovich > wrote:
>
>> Hi All,
>>
>> Currently we [Fuel UI t
real deployments.
We would like to introduce really usefull tools based on your feedback.
Best regards,
Julia
--
Kind Regards,
Julia Aranovich,
Software Engineer,
Mirantis, Inc
+7 (905) 388-82-61 (cell)
Skype: juliakirnosova
www.
on.
Please feel free and share your ideas and concerns if any.
Regards,
Julia
--
Kind Regards,
Julia Aranovich,
Software Engineer,
Mirantis, Inc
+7 (905) 388-82-61 (cell)
Skype: juliakirnosova
www.mirantis.ru
jaranov...@mirantis.com
_
>> --
>> Best regards,
>> Nick Markov
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:u
as a tooltip on Add Nodes screen.
And the second goal of my letter is to ask you to go through openstack.yaml
<https://github.com/stackforge/fuel-web/blob/master/nailgun/nailgun/fixtures/openstack.yaml>
file
and add an appropriate messages for restrictions. It will make Fuel UI more
clear and
21 matches
Mail list logo
