;
> > On Wed, Feb 22, 2017 at 12:36 AM Булат Гайфуллин
> > wrote:
> >>
> >> +1
> >>
> >> 2017-02-21 17:01 GMT+03:00 Alexey Shtokolov :
> >>>
> >>> Hey fellow fuelers,
> >>>
> >>> I'd like to nomi
+1
On Thu, Feb 25, 2016 at 12:32 PM, Bulat Gaifullin
wrote:
> +1
>
> Regards,
> Bulat Gaifullin
> Mirantis Inc.
>
>
>
> On 24 Feb 2016, at 16:02, Aleksandr Didenko wrote:
>
> +1
>
> On Wed, Feb 24, 2016 at 1:50 PM, Vladimir Kuklin
> wrote:
>
>> Fellow Fuelers
>>
>> I would like to kindly ask y
+1
On Tue, Feb 9, 2016 at 12:28 PM, Anastasia Urlapova
wrote:
> +1
>
> On Tue, Feb 9, 2016 at 11:51 AM, Evgeniy L wrote:
>
>> +1
>>
>> On Mon, Feb 8, 2016 at 7:58 PM, Vladimir Kozhukalov <
>> vkozhuka...@mirantis.com> wrote:
>>
>>> +1 to enable it ASAP.
>>>
>>> It will also affect our deploymen
t, it's better to
> ask Alexander Kislitsky.
>
> Thanks,
> Igor
>
> On Wed, Dec 30, 2015 at 2:57 PM, Vitaly Kramskikh
> wrote:
> > Hi,
> >
> > We have a long-living issue with deadlocks in nailgun which used to
> almost
> > harmless and caused rare
+1
On Wed, Dec 23, 2015 at 8:15 PM, Aleksey Kasatkin
wrote:
> +1
>
> Aleksey Kasatkin
>
>
> On Wed, Dec 23, 2015 at 5:28 PM, Aleksandr Didenko
> wrote:
>
>> +1
>>
>> On Wed, Dec 23, 2015 at 4:21 PM, Andrey Sledzinskiy <
>> asledzins...@mirantis.com> wrote:
>>
>>> +1
>>>
>>> On Wed, Dec 23, 2015
Dear colleagues,
I'd like to get rid of group fuel-astute on launchpad. In group only 2
active members. Actually they are members of fuel-python team. Bugs for
fuel-astute project always concern to fuel-web project. Bugs assigned to
fuel-astute can stay without attention for a long time. Thus I pr
Also feature_groups is used for selecting usage statistics collector. If
'mirantis' is in feature_groups we are using one instance of statistics
collector and another collector instance in other case.
On Thu, Jun 18, 2015 at 7:04 PM, Vitaly Kramskikh
wrote:
> Hi,
>
> Yes, it is possible to chang
w how much effort we should apply to implement this, but on
> first look it seems ok. I mean, we save "tasks" to send in some queue
> and then send them if and only iff HTTP handler reports success.
> Currently, we send it, but there are few places where HTTP handler may
>
em by re-factoring our architecture. Perhaps, we could
> send tasks to Astute when the handler is done? What do you think?
>
> Thanks,
> igor
>
> On Wed, May 6, 2015 at 12:15 PM, Lukasz Oles wrote:
> > On Wed, May 6, 2015 at 10:51 AM, Alexander Kislitsky
>
Hi!
The refactoring of transactions management in Nailgun is critically
required for scaling.
First of all I propose to wrap HTTP handlers by begin/commit/rollback
decorator.
After that we should introduce transactions wrapping decorator into Task
execute/message calls.
And the last one is the wr
Andrew shows great attention to the details. +1 for him.
On Mon, Apr 13, 2015 at 11:22 AM, Anastasia Urlapova wrote:
> Guys,
> I would like to nominate Andrey Skedzinskiy[1] for
> fuel-qa[2]/fuel-devops[3] core team.
>
> Andrey is one of the strongest reviewers, under his watchful eye are such
>
+1 for moving fuel_development into separate repo.
On Thu, Mar 19, 2015 at 5:02 PM, Evgeniy L wrote:
> Hi folks,
>
> I agree, lets create separate repo with its own cores and remove
> fuel_development from fuel-web.
>
> But in this case I'm not sure if we should merge the patch which
> has links
Folks,
We are collecting OpenStack workloads stats. For authentication in the
keystone we are using admin user credentials from Nailgun. Credentials can
be changed directly in the OpenStack and we will loose possibility of
fetching information.
This issue can be fixed by creation additional user
Tests to run on
> commits, nightly builds, integration with nightly system tests?
>
> Should it be part of Fuel CI or completely independent?
>
>
> On Thu, Jan 29, 2015 at 11:55 AM, Alexander Kislitsky
> wrote:
> > Hi, guys
> >
> > All our plugins reposi
Hi, guys
All our plugins repositories are moved to stackforge. Each plugin has
separate repo and now can be maintained independently from core product
cycle and without core-team attraction.
Here is a map of migration:
https://github.com/stackforge/fuel-plugins/tree/master/external_glusterfs
->
Guys, definitely we shouldn't delete tasks.
+1 for warning.
On Fri, Jan 16, 2015 at 3:58 PM, Evgeniy L wrote:
> Hi,
>
> 1) +1 for warning
>
> 2) I don't think that we should delete tasks, it's a history which can be
> useful,
> for example for stats feature, also it's useful for debugging, but
We had used Flask in the fuel-stats. It was easy and pleasant and all
project requirements was satisfied. And I saw difficulties and workarounds
with Pecan, when Nick integrated it into Nailgun.
So +1 for Flask.
On Tue, Dec 2, 2014 at 11:00 PM, Nikolay Markov
wrote:
> Michael, we already solved
Hi!
You are right, we are talking about
https://blueprints.launchpad.net/fuel/+spec/monitoring-system
We want to estimate required time for merging HA implementation into
current code. If it possible we will try to distribute HA solution in
current release. In other case it will be delivered in n
18.07.2014
Participants:
Szymon Banka,
Bartek Kupidura,
Dmitry Nikishov
Alexander Kislitsky
Discussed limitation of current implementation, timelines, integration
workflow.
Colleagues going to build custom ISO with current Zabbix monitoring
implementation, test it, add review comments.
On next
16.07.2014 meeting results:
Participants:
L. Oles
N. Markov
V. Kramskikh
A. Kislitsky
Acceptance points of authentication in FUEL:
1.
Each project (nailgun, CLI, UI, OSTF) should authenticate in Keystone
and use received token in other services requests
2.
Authentication can be
20 matches
Mail list logo