+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 feature developments
> (e.g. Config-DB enha
+1
Aleksey Kasatkin
On Mon, Sep 12, 2016 at 5:01 PM, Alex Schultz wrote:
> +1
>
> On Wed, Sep 7, 2016 at 5:07 PM, Maksim Malchuk
> wrote:
> > Hello,
> >
> > I would like to nominate Stanislaw Bogatkin to fuel-library core due to
> his
> > significant
+1
Aleksey Kasatkin
On Sat, Sep 10, 2016 at 4:49 PM, Sergey Vasilenko
wrote:
> +1
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@list
Hi,
-1 to the proposal. We have the ability (and we use it) to add guys to
several core groups. So, AFAIC, Vladimir's pros point #1 is covered. IMO,
pros point #2 looks questionable and not so important. Cons could be worse
(agree with Lukasz).
Thanks,
Aleksey Kasatkin
On Tue, Sep 6,
+1
Aleksey Kasatkin
On Mon, Jul 25, 2016 at 7:46 PM, Igor Kalnitsky
wrote:
> Vitaly's doing a great job. +2, no doubts!
>
> On Mon, Jul 25, 2016 at 6:27 PM, Tatyana Leontovich
> wrote:
> > A huge +1
> >
> > On Mon, Jul 25, 2016 at 4:33 PM, Yegor Kotko
>
Well, the agreement is reached. I've added Artur to fuel-web-core group.
Let's continue discussion on time management questions if it will
become an issue.
Artur, congratulations!
Aleksey Kasatkin
On Fri, Jun 10, 2016 at 2:18 AM, Evgeniy L wrote:
> Hi Dmitry,
>
> It depe
n for
HugePages support and of NUMA/CPU pinning support) and in bug-fixing in
Fuel project.
Core reviewers, please reply back with +1/-1.
[1] http://stackalytics.com/report/contribution/fuel-web/90
Best regards,
Aleksey Kas
+1
Aleksey Kasatkin
On Thu, Jun 9, 2016 at 9:51 AM, Sergey Vasilenko
wrote:
> +1
>
> /sv
> On Jun 9, 2016 09:24, "Julia Aranovich" wrote:
>
>> +1
>>
>> On Wed, Jun 8, 2016 at 8:52 PM Bulat Gaifullin
>> wrote:
>>
>>> Hey Fue
Matthew,
It's great that we have this test. But why to rerun it for no changes?
It was executed only when a new patch was published for CR or CR was
rebased.
Now it is executed on "fuel:recheck".
Agree, adding a plugin would be helpful.
Aleksey Kasatkin
On Fri, Apr 22,
patch/rebase only.
Its run takes about 1.5 hour and there is little sense to run it more than
once for the same patch.
Thanks,
Aleksey Kasatkin
On Fri, Apr 22, 2016 at 10:59 AM, Dmitry Kaiharodsev <
dkaiharod...@mirantis.com> wrote:
> Hi to all,
>
> please be informed that re
:
ep: br-mon
...
network_scheme:
custom:
roles:
influxdb_vip: br-mon
...
...
I hope, this helps.
Regards,
Aleksey Kasatkin
On Wed, Apr 20, 2016 at 12:16 PM, Simon Pasquier
wrote:
> Hi,
> I've got a question regarding network templates and VIP.
Hi Ryan,
Thank you. We had a talk with Evgeniy. As a preliminary plan, we will have
meetings with all interested people from Networking team.
Regards,
Aleksey Kasatkin
On Tue, Mar 15, 2016 at 7:46 PM, Ryan Moe wrote:
> Hi Aleksey,
>
>
>
>> What is the status of maki
Hi,
I'm agree with Alex, keys should remain immutable. 'node-{uid}' is Okay, we
have a method for this in Nailgun already. It should be a very simple fix
in Nailgun.
Thanks,
Aleksey Kasatkin
On Tue, Mar 15, 2016 at 3:19 PM, Kyrylo Galanov
wrote:
> Hi,
>
> I would li
he whole task. And as 2.1 is in progress already, 2.3 seems to be
rejected..?
I'd like to participate in design discussions. Please add me into meetings.
Thanks,
[0] https://review.openstack.org/#/q/topic:bp/network-config-refactoring
[1] https://review.openstack.org/#/c/290767/
Alekse
iov
Aleksey Kasatkin
On Tue, Mar 1, 2016 at 6:27 PM, Aleksandr Didenko
wrote:
> Hi,
>
> I'd like to to request a feature freeze exception for "Support for SR-IOV
> for improved networking performance" feature [0].
>
> Part of this feature is already merged [1]. We
+1
Aleksey Kasatkin
On Thu, Feb 25, 2016 at 11:59 PM, Sergey Vasilenko
wrote:
> +1
>
>
> /sv
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsu
+1
Aleksey Kasatkin
On Mon, Feb 8, 2016 at 12:04 PM, Tatyana Leontovich <
tleontov...@mirantis.com> wrote:
> +1
>
>
>
> On Mon, Feb 8, 2016 at 11:54 AM, Igor Kalnitsky
> wrote:
>
>> Hey Fuelers,
>>
>> I'd like to nominate Fedor Zhadaev
> jsonpatch
There were +1's regarding overriding VIPs above. I'd stick with that. It is
done for tasks now. But we will need to check conflicts between plugins
there (as for tasks).
Aleksey Kasatkin
On Fri, Jan 29, 2016 at 1:23 PM, Roman Prykhodchenko wrote:
> Frankly, I
ybe find a way to do exactly this.
Aleksey Kasatkin
On Thu, Jan 28, 2016 at 6:28 PM, Aleksandr Didenko
wrote:
> > How are we handling this now for multiple plugins?
>
> OK, so right now we can only add VIPs to array, we can't remove them. So
> overriding would disable such p
Roman, please provide more details on how VIPs are overridden. And how do
you deal with multiple plugins.
Aleksey Kasatkin
On Thu, Jan 28, 2016 at 5:58 PM, Aleksey Kasatkin
wrote:
> Good idea, overally.
>
> How about multiple plugins? We don't have any sequence or priorities
Good idea, overally.
How about multiple plugins? We don't have any sequence or priorities
between them.
What if one plugin assumes that VIP is present but other one wants to
remove it?
Aleksey Kasatkin
On Thu, Jan 28, 2016 at 4:02 PM, Sergii Golovatiuk wrote:
> +1 to overrid
Folks, you are welcome to review a spec: https://review.openstack.org/254796
Aleksey Kasatkin
On Fri, Nov 6, 2015 at 6:03 PM, Aleksey Kasatkin
wrote:
> Mike, Vladimir,
>
> Yes,
> 1. We need to add IPs on-the-fly (need to add POST functionality) ,
> otherwise it will be VIP-l
+ Konstantin
Aleksey Kasatkin
On Wed, Dec 23, 2015 at 7:38 PM, Aleksandr Didenko
wrote:
> Hi,
>
> just finished deployment of multirack env with ceph and external LB (not a
> standard multi-rack deployment scheme, actually, but still):
>
> http://paste.openstack.org/show/
+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 at 5:05 PM, Tatyana Leontovich <
>
+1
Aleksey Kasatkin
On Wed, Dec 23, 2015 at 3:57 PM, Aleksandr Didenko
wrote:
> +1
>
> On Wed, Dec 23, 2015 at 2:52 PM, Tatyana Leontovich <
> tleontov...@mirantis.com> wrote:
>
>> Absolutely agree
>>
>> +1
>>
>>
>>
>>
>&g
Corresponding ticket:
https://bugs.launchpad.net/fuel/+bug/1528613 (Prohibit creation of
Nova-Network enabled 8.0 environments)
Aleksey Kasatkin
On Tue, Dec 22, 2015 at 4:22 PM, Sheena Gregson
wrote:
> I agree – I don’t think we can change the user’s ability to manage old
> releases.
Sergii,
We could remove it completely from nailgun if support for 7.0 and earlier
is not required.
Aleksey Kasatkin
On Tue, Dec 22, 2015 at 3:27 AM, Sergii Golovatiuk wrote:
> Hi,
>
> Finally we can deprecate nova-network ...
> We should remove it from UI, nailgun logic and t
+1.
Aleksey Kasatkin
On Mon, Dec 14, 2015 at 12:49 PM, Vladimir Sharshov
wrote:
> Hi,
>
> +1 from me to Bulat.
>
> On Mon, Dec 14, 2015 at 1:03 PM, Igor Kalnitsky
> wrote:
>
>> Hi Fuelers,
>>
>> I'd like to nominate Bulat Gaifulin [1] for
>&g
+1.
No doubts. )
Aleksey Kasatkin
On Tue, Dec 1, 2015 at 5:49 PM, Dmitry Pyzhov wrote:
> Guys,
>
> I propose to promote Roman Prykhodchenko to python-fuelclient cores. He is
> the main contributor and maintainer of this repo. And he did a great job
> making changes t
It can be selected but we have no tests for deployment which are run on
periodical basis. So, we do not have any recent status.
Also, serializer in Nailgun for Nova-Network is now not in use (it is not
tested how serialization will work in 8.0).
Aleksey Kasatkin
On Tue, Dec 1, 2015 at 9:36 AM
.
Aleksey Kasatkin
On Fri, Oct 23, 2015 at 3:42 PM, Sheena Gregson
wrote:
> As a reminder: there are no individual networking options that can be used
> with both vCenter and KVM/QEMU hypervisors once we deprecate nova-network.
>
>
>
> The code for vCenter as a stand-alone deplo
We have more generic ticket: https://bugs.launchpad.net/fuel/+bug/1354803
and corresponding CR: https://review.openstack.org/#/c/245941/
Aleksey Kasatkin
On Fri, Nov 20, 2015 at 11:24 AM, Aleksey Kasatkin
wrote:
> It's not about Public networks only. There can be the same problem with
It's not about Public networks only. There can be the same problem with
other networks as well.
It's required to check all the networks (across all node groups).
But it is done just for Public network now (and VIPs for plugins are not
taken into account).
Aleksey Kasatkin
On Fri, No
#x27;]).
This VIP will be allocated
in the network that 'ceph/vip' is mapped to and in the node group where
ceph nodes are located. ceph nodes cannot be located
in more than one node group then (as VIP cannot migrate between node groups
now).
Aleksey Kasatkin
On Fri, Nov 6, 2015 at 10:
match the
network role of the VIP?
Use '--force' parameter to change it. PUT will fail otherwise.
Guys, please review this and share your comments here,
Thanks,
Aleksey Kasatkin
On Tue, Nov 3, 2015 at 10:47 AM, Aleksey Kasatkin
wrote:
> Igor,
>
> > For VIP allocation w
s of the VIP matches some IP range that corresponds
to the network which is different from the one that network role bound to
the VIP has.
E.g. IP address matches the 'public' network but VIP is bound to
'management/vip' role
which is mapped to 'management' network.
T
th the
network from another
environment? overlaps with the network of current environment which does
not match the
network role of the VIP?
My opinion that those should pass with a warning message.
Please share your proposals and comments on this,
Thanks,
Aleksey Kasatkin
Sergii,
1. We only have auto-doc for developers which should be changed
automatically.
2. We do not have proper API versioning. We didn't decide yet how to
resolve it. Let's discuss versioning in "[Fuel] Changing APIs and API
versioning" thread.
Aleksey Kasatkin
On Wed,
> Then we should close [1] as invalid, shoudn’t we?
AFAIC, no. We should check whether there is enough IPs for nodes /
VIPs with current network configuration.
I'd propose to add a handler for allocation of VIPs if VIPs can be useful
before deployment.
I'm not sure what are the case
+ Pavlo, Andrey.
Aleksey Kasatkin
On Mon, Oct 19, 2015 at 6:45 AM, wrote:
> Hello,
>
>
>
> I’m currently searching for information about Ironic Fuel plugin :
> https://github.com/openstack/fuel-plugin-ironic I don’t find any
> documentation on it.
>
>
>
> I’
run CheckBeforeDeployment task
separately (only within ApplyChanges for now). It will help the user to
diagnose different problems. It seems to be a subject for another
discussion/ticket though.
Thanks,
Aleksey Kasatkin
On Mon, Oct 19, 2015 at 11:28 AM, Igor Kalnitsky
wrote:
> Hi Roman,
>
+1 to Sebastian. And, AFAIK, there is no user docs (or about no docs) on
CLI v2. Even for 7.0 new features were documented using CLI v1.
Aleksey Kasatkin
On Fri, Oct 16, 2015 at 3:38 PM, Igor Kalnitsky
wrote:
> +1 to Sebastian.
>
> On Wed, Oct 14, 2015 at 12:13 PM, Sebastian K
Hi,
Just a remark: python-fuelclient is missing here.
Aleksey Kasatkin
On Sun, Sep 20, 2015 at 3:56 PM, Mike Scherbakov
wrote:
> Hi all,
> as of my larger proposal on improvements to code review workflow [1], we
> need to have cores for repositories, not for the whole Fuel. It is
Evgeniy, thank you for solution proposal.
Aleksey Kasatkin
On Tue, Jul 28, 2015 at 7:39 PM, Aleksey Kasatkin
wrote:
> Okey, will do fix for validation first.
>
>
> Aleksey Kasatkin
>
>
> On Tue, Jul 28, 2015 at 7:30 PM, Evgeniy L wrote:
>
>> Aleks
Okey, will do fix for validation first.
Aleksey Kasatkin
On Tue, Jul 28, 2015 at 7:30 PM, Evgeniy L wrote:
> Aleksey, here is working version [1].
>
> >> Evgeniy, do we need to remove jinja before July 30th ?
>
> With this issue feature can leave, and it won't have
Evgeniy, do we need to remove jinja before July 30th ?
Aleksey Kasatkin
On Tue, Jul 28, 2015 at 6:40 PM, Aleksey Kasatkin
wrote:
> AFAIU, string.Template doesn't help.
>
> This seems to be helpful:
>
> import re
> def interp(string, params):
> for item in re.finda
e better options for this?
Aleksey Kasatkin
On Tue, Jul 28, 2015 at 1:12 PM, Sergey Vasilenko
wrote:
> If we need only substitution, probably it's better to use standard
>> templating
>> in python [1], there is a way to redefine tokens, so you will be able to
>>
ut jinja or ERB. It is just a token for substitution of
values. There is no jinja nor ERB features granted within template language.
Aleksey Kasatkin
On Tue, Jul 28, 2015 at 12:25 PM, Sergey Vasilenko
wrote:
>
> On Tue, Jul 28, 2015 at 11:52 AM, Evgeniy L wrote:
>
>> Hi Al
Evgeniy, I need some response in
https://bugs.launchpad.net/fuel/+bug/1476779
AFAIC, it can be 30th (Thursday) for basic validation of template itself
(regardless of present nodes and their node roles) but including known node
roles/network roles for particular environment.
Aleksey Kasatkin
On
least validation cannot be completed tomorrow. We can test tokens
today.
For some basic validation - the is a chance, but no certaincy.
Aleksey Kasatkin
On Mon, Jul 27, 2015 at 1:00 PM, Igor Kalnitsky
wrote:
> Evgeniy,
>
> > 3. Change tokens in template language
>
> I'm no
+1 for an exception. Do we have time estimate though?
Aleksey Kasatkin
On Fri, Jul 24, 2015 at 2:46 PM, Sebastian Kalinowski <
skalinow...@mirantis.com> wrote:
> +1 for this exception - as Evgeniy said it is developed not in the core
> but in extension and risk is low.
>
>
those to FFE ?
Aleksey Kasatkin
On Fri, Jul 24, 2015 at 2:12 PM, Sebastian Kalinowski <
skalinow...@mirantis.com> wrote:
> I agree here with Evgeniy. Even if it's not a trivial change, we cannot
> leave a new API in such shape.
>
> 2015-07-24 11:41 GMT+02:00 Evgeniy L :
>
Yes, it is the only CR left (https://review.openstack.org/#/c/204321/).
It is tested manually, is on review and should be merged today or the next
workday.
Aleksey Kasatkin
On Thu, Jul 23, 2015 at 9:18 PM, Mike Scherbakov
wrote:
> Looks like the only CLI part left:
>
ns related to this
request.
Thanks in advance.
[1] https://blueprints.launchpad.net/fuel/+spec/templates-for-networking
[2] https://review.openstack.org/#/c/204321/
[3] https://review.openstack.org/#/c/203602/
[4] https://review.openstack.org/#/c/201217/
--
Best regards,
Alekse
7;,
'operational',
'error',
'remove',
'update',
'update_error'
)
[1]
https://github.com/stackforge/fuel-web/blob/master/nailgun/nailgun/consts.py
Aleksey Kasatkin
On Wed, May 27, 2015 at 4:00 PM, Oleg Gelbukh wrote:
> E
27;t related to
'deployment'
state of cluster (as well as the first one in the table).
Also, we should be careful with the order of nodes deployment/reset. I'm
not sure whether it is written in our docs that cluster may be
non-functional if user tries to deploy nodes in the wrong ord
1/ +1
2/ +1
3/ +1
Aleksey Kasatkin
On Tue, Apr 14, 2015 at 12:26 PM, Tatyana Leontovich <
tleontov...@mirantis.com> wrote:
>
> 3/ +1
>
> On Tue, Apr 14, 2015 at 11:49 AM, Sergii Golovatiuk <
> sgolovat...@mirantis.com> wrote:
>
>> +1 for separating
+1
Aleksey Kasatkin
On Tue, Apr 14, 2015 at 1:20 PM, Anastasia Urlapova
wrote:
> Andrey,
> congratulations on your new role!
>
>
> Nastya.
>
> On Tue, Apr 14, 2015 at 12:28 PM, Yegor Kotko wrote:
>
>> +1
>>
>> On Tue, Apr 14, 2015 at
/fuel/+bug/1355764 for this BP) is can be closed
almost without doubt. But some of them can be solved separately somehow or
have workarounds. Sometimes scope of BP can be changed (e.g. split to
several BPs) or its timeline is changed so bugs should not be lost without
care.
Aleksey Kasatkin
On
o with API versioning yet.
Aleksey Kasatkin
On Thu, Feb 19, 2015 at 12:05 PM, Vitaly Kramskikh
wrote:
> I think all these operations for nodes (grouping, sorting, filtering) can
> be done on the backend, but we can do it completely on the UI side and
> shouldn't wait for backen
+1 for this option. I use log while creating new tests sometimes.
Aleksey Kasatkin
On Mon, Jan 19, 2015 at 3:37 PM, Roman Prykhodchenko wrote:
> Hi folks,
>
> at the moment run_test.sh script removes Nailgun's log file after running.
> The question is whether it is necessary
might be not supported by network checker.
Agree, this should be done on backend.
Aleksey Kasatkin
On Thu, Jan 15, 2015 at 10:54 PM, Lukasz Oles wrote:
> Big +1, it would save me a lot of debugging time :)
>
> On Thu, Jan 15, 2015 at 5:20 PM, Vitaly Kramskikh
> wrote:
> >
+1 to show "as is". We don't get benefits from parsing now (like filtering
by value of particular parameter, date/time intervals). It only adds
complexity.
Aleksey Kasatkin
On Mon, Dec 15, 2014 at 1:40 PM, Tomasz Napierala
wrote:
>
> Also +1 here.
> In huge envs we al
+1
Aleksey Kasatkin
Hi everyone!
>
> I would like to propose Igor Kalnitsky as a core reviewer on the
> Fuel-web team. Igor has been working on openstack patching,
> nailgun, fuel upgrade and provided a lot of good reviews [1]. In
> addition he's also very active in
Agree for Bogdan and Sergii
Aleksey Kasatkin
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
track assign_ips() and assign_vip() usage to see all calls to them.
Aleksey Kasatkin
> -- Forwarded message --
> From: zh...@certusnet.com.cn
> Date: Fri, Aug 1, 2014 at 10:36 AM
> Subject: [openstack-dev] Networks Generating In Fuel
> To: openstack-dev
&g
same.
Regards,
Aleksey Kasatkin
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
67 matches
Mail list logo
