Re: [openstack-dev] Nominate Vladimir Khlyunev for fuel-qa core

[Artem Panchenko]

+1

On Tue, Aug 2, 2016 at 1:52 PM, Dmitry Tyzhnenko 
wrote:

> +1
>
> On Tue, Aug 2, 2016 at 12:51 PM, Artur Svechnikov <
> asvechni...@mirantis.com> wrote:
>
>> +1
>>
>> Best regards,
>> Svechnikov Artur
>>
>> On Tue, Aug 2, 2016 at 12:40 PM, Andrey Sledzinskiy <
>> asledzins...@mirantis.com> wrote:
>>
>>> Hi,
>>> I'd like to nominate Vladimir Khlyunev for fuel-qa [0] core.
>>>
>>> Vladimir has become a valuable member of fuel-qa project in quite short
>>> period of time. His solid expertise and constant contribution gives me no
>>> choice but to nominate him for fuel-qa core.
>>>
>>> If anyone has any objections, speak now or forever hold your peace
>>>
>>> [0]
>>> http://stackalytics.com/?company=mirantis=all=fuel-qa_id=vkhlyunev
>>> 
>>>
>>> --
>>> Thanks,
>>> Andrey Sledzinskiy
>>> QA Engineer,
>>> Mirantis, Kharkiv
>>>
>>>
>>> __
>>> 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
>>>
>>>
>>
>> __
>> 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
>>
>>
>
>
> --
> WBR,
> Dmitry T.
> Fuel QA Engineer
> http://www.mirantis.com
>
> __
> 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
>
>
__
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

Re: [openstack-dev] [Fuel] Nominate Alexey Stepanov for fuel-qa and fuel-devops core

[Artem Panchenko]

+1

On 15.07.16 16:25, Tatyana Leontovich wrote:

+1

On Fri, Jul 15, 2016 at 4:08 PM, Anastasia Urlapova 
<aurlap...@mirantis.com <mailto:aurlap...@mirantis.com>> wrote:


+1

On Fri, Jul 15, 2016 at 4:02 PM, Andrey Sledzinskiy
<asledzins...@mirantis.com <mailto:asledzins...@mirantis.com>> wrote:

Hi,
I'd like to nominate Alexey Stepanovfor fuel-qa [0] and
fuel-devops [1] core.

Alexey is doing great job improving fuel-qa and fuel-devops
projects.
He's become an expert in code base in very short terms so I
think he deserves to be a part of fuel-qa/fuel-devops core team.

Please, vote for Alexey!

[0]

http://stackalytics.com/?release=all=fuel-qa_id=astepanov-m=marks

[1]

http://stackalytics.com/?release=all=fuel-devops_id=astepanov-m=marks


-- 
Thanks,

Andrey Sledzinskiy
QA Engineer,
Mirantis, Kharkiv


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




__
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


--
Artem Panchenko
QA Engineer

__
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

Re: [openstack-dev] [Fuel] Diagnostic snapshot generation is broken due to lack of disk space

[Artem Panchenko]

Guys,

I want to pay your attention that we need to not only fix snapshots 
generation issue, but also prevent caused by it unexpected services 
failures (see details in a duplicate [0] of original [1] bug), which 
would become a challenge for not experienced users (for example he/she 
won't be able to authenticate in GUI or CLI some time after snapshot 
generation is started). I get this issue on our bare-metal lab (10 
slaves) each time I have an environment which is running more than 2 days.


Links usage for files copying doesn't help in such case, because tarball 
is still saved on /var partition. Also, if I want to workaround this 
issue, I have to perform a lot of actions: s hrink 'os-varlog' volume 
(because it's the biggest [2] one) in order to increase unallocated disk 
space, resize its FS, create new volume, create FS, mount it to 
/var/www/nailgun/dump and update fstab. Not easy way to make "Generate 
Diagnostic Snapshot " button work, right?


So, if we are going to address this diagnostic snapshot issue in 8.0, I 
want to remind you about b) option :)



b) Make the snapshot location share the diskspace of /var/log?


Thanks!

[0] https://bugs.launchpad.net/fuel/+bug/1530131
[1] https://bugs.launchpad.net/fuel/+bug/1529182
[2] http://paste.openstack.org/show/484895/

On 18.01.16 13:20, Maciej Kwiek wrote:
Igor: It seems that fqdn -> ipaddr will indeed be resolved. Please 
share your feedback in review: https://review.openstack.org/#/c/266964/3


On Fri, Jan 15, 2016 at 4:25 PM, Igor Kalnitsky 
<ikalnit...@mirantis.com <mailto:ikalnit...@mirantis.com>> wrote:


Sheena -

What do you mean by *targeted*? Shotgun's designed to be a *targeted*
solution. If someone wants more *precise* targets - it's easy to
specify them in Nailgun's settings.yaml.

- Igor

On Fri, Jan 15, 2016 at 5:02 PM, Sheena Gregson
<sgreg...@mirantis.com <mailto:sgreg...@mirantis.com>> wrote:
> I’ve also seen the request multiple times to be able to provide more
> targeted snapshots which might also (partially) solve this
problem as it
> would require significantly less disk space to grab logs from a
subset of
> nodes for a specific window of time, instead of the more robust
grab-all
> solution we have now.
>
>
>
> From: Maciej Kwiek [mailto:mkw...@mirantis.com
<mailto:mkw...@mirantis.com>]
> Sent: Thursday, January 14, 2016 5:59 AM
> To: OpenStack Development Mailing List (not for usage questions)
> <openstack-dev@lists.openstack.org
<mailto:openstack-dev@lists.openstack.org>>
> Subject: Re: [openstack-dev] [Fuel] Diagnostic snapshot
generation is broken
> due to lack of disk space
>
>
>
> Igor,
>
>
>
> I will investigate this, thanks!
>
>
>
> Artem,
>
>
>
> I guess that if we have an untrusted user on master node, he
could just put
> something he wants to be in the snapshot in /var/log without
having to time
> the attack carefully with tar execution.
>
>
>
> I want to use links for directories, this saves me the trouble
of creating
> hardlinks for every single file in the directory. Although with how
> exclusion is currently implemented it can cause deleting log
files from
> original directories, need to check this out.
>
>
>
> About your PS: whole /var/log on master node (not in container)
is currently
> downloaded, I think we shouldn't change this as we plan to drop
containers
> in 9.0.
>
>
>
> Cheers,
>
> Maciej
>
>
>
> On Thu, Jan 14, 2016 at 12:32 PM, Artem Panchenko
<apanche...@mirantis.com <mailto:apanche...@mirantis.com>>
> wrote:
>
> Hi,
>
> using symlinks is a bit dangerous, here is a quote from the man you
> mentioned [0]:
>
>> The `--dereference' option is unsafe if an untrusted user can
modify
>> directories while tar is running.
>
> Hard links usage is much safer, because you can't use them for
directories.
> But at the same time implementation in shotgun would be more
complicated
> than with symlinks.
>
> Anyway, in order to determine what linking to use we need to
decide where
> (/var/log or another partition) diagnostic snapshot will be stored.
>
> p.s.
>
>>This doesn't really give us much right now, because most of the
logs are
>> fetched from master node via ssh due to shotgun being run in
mcollective
>> container
>
>
>
> AFAIK '/var/log/docker-logs/' is ava

Re: [openstack-dev] [Fuel] Diagnostic snapshot generation is broken due to lack of disk space

[Artem Panchenko]

https://github.com/openstack/fuel-web/blob/2855a9ba925c146b4802ab3cd2185f1dce2d8a6a/nailgun/nailgun/settings.yaml#L717



__
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




__
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




__
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



__
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



__
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



__
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


__
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


--
Artem Panchenko
QA Engineer

__
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

Re: [openstack-dev] [Fuel] Diagnostic snapshot generation is broken due to lack of disk space

[Artem Panchenko]

Hi,

doesn't matter how /var partition is big, diagnostic snapshot still 
could occupy all its space if there are lots of logs on slave nodes. 
Although, we can try to control disk space usage by snapshot in shotgun, 
but IMHO it's much safer to keep all related to logs staff away from 
critical system files, so I'm voting for 2nd (b) option. By the way it 
will allow us to use hard links for fast copying of files before 
creating tarball, because one partition for storing logs and snapshot 
will be used.


Thanks!

On 12.01.16 12:47, Maciej Kwiek wrote:

Hi!

I need some advice on how to tackle this issue. There is a bug [1] 
describing the problem with creating a diagnostic snapshot. The issue 
is that /var/log has 100GB available, while /var (where diagnostic 
snapshot is being generated - /var/www/nailgun/dump/fuel-snapshot 
according to [2]) has 10GB available, so dumping the logs can be an 
issue when logs size exceed free space in /var.


There are several things we could do, but I am unsure on which course 
to take. Should we

a) Allocate more disk space for /var/www (or for whole /var)?
b) Make the snapshot location share the diskspace of /var/log?
c) Something else? What?

Please share your thoughts on this.

Cheers,
Maciej Kwiek

[1] https://bugs.launchpad.net/fuel/+bug/1529182
[2] 
https://github.com/openstack/fuel-web/blob/2855a9ba925c146b4802ab3cd2185f1dce2d8a6a/nailgun/nailgun/settings.yaml#L717



__
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


--
Artem Panchenko
QA Engineer

__
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