Re: [OpenStack-Infra] Ask.o.o Email not getting through?

2017-05-01 Thread Tom Fifield

On 01/05/17 23:36, James E. Blair wrote:

Tom Fifield <t...@openstack.org> writes:


Hello infra,

Exploratory question here, no idea what's actually going on.

We have a prospective new user on Ask OpenStack, who despite trying
multiple auth methods (Launchpad & Google) multiple times did not
receive a confirmation email.

I checked and there have been several new users created within the
same day, so it does not seem like a general email problem.


May I ask if there is anything revealing in the logs around
m...@tiferrei.com ?


The MTA reports a DNS failure for that domain.  The problem appears to
be related to DNSSEC on that domain.  It looks like the domain
previously had invalid signing keys, but they have been removed.
However, DNS resolvers may still have those keys cached.  The caching
resolver that ask.o.o is using indicates it has a bit over 8 hours
remaining.  Google's public DNS servers indicate almost 24 hours
remaining in their cache.

Assuming the user's DNS configuration is and remains correct, the
problem should be corrected on ask.o.o within 9 hours, and they should
see other DNS related failures abate as they reach the original
expiration time of the erroneous DS records.



Thank you very much!!


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

[OpenStack-Infra] Ask.o.o Email not getting through?

2017-05-01 Thread Tom Fifield

Hello infra,

Exploratory question here, no idea what's actually going on.

We have a prospective new user on Ask OpenStack, who despite trying 
multiple auth methods (Launchpad & Google) multiple times did not 
receive a confirmation email.


I checked and there have been several new users created within the same 
day, so it does not seem like a general email problem.



May I ask if there is anything revealing in the logs around 
m...@tiferrei.com ?



Regards,


Tom

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Ask.o.o down

2017-02-20 Thread Tom Fifield



On 廿十七年二月廿一日 暮 03:11, Tom Fifield wrote:



On 廿十七年二月十四日 暮 04:19, Joshua Hesketh wrote:



On Tue, Feb 14, 2017 at 7:15 PM, Tom Fifield <t...@openstack.org
<mailto:t...@openstack.org>> wrote:

On 14/02/17 16:11, Joshua Hesketh wrote:

Hey Tom,

Where is that script being fired from (a quick grep doesn't find
it), or
is it a tool people are using?

If it's a tool we'd need to make sure whoever is using it gets
a new
version to rule it out.


Indeed.


It's fired from a PHP service on www.openstack.org
<http://www.openstack.org> itself, which writes to the Member
database:


https://github.com/OpenStackweb/openstack-org/blob/master/auc-metrics/code/services/ActiveModeratorService.php


<https://github.com/OpenStackweb/openstack-org/blob/master/auc-metrics/code/services/ActiveModeratorService.php>




Right. I wonder if somebody could check the logs to see if the process
times out. Sadly looking at that code it looks like any output messages
from the script will be discarded.



... and my patch was deployed, but the site is down today. So, looks
like it wasn't that.


Though, is it staying down for less time? It came back up just now - 
normally it'd be down for another 45mins.


Interesting traffic spikes at:
http://cacti.openstack.org/cacti/graph.php?action=view_graph_id=2549_id=all

seem to correlate with the outage. Perhaps we can set up some tcpdumps?




The next step is to update the copy of the script it references:


https://github.com/OpenStackweb/openstack-org/blob/master/auc-metrics/lib/uc-recognition/tools/get_active_moderator.py


<https://github.com/OpenStackweb/openstack-org/blob/master/auc-metrics/lib/uc-recognition/tools/get_active_moderator.py>


I am not sure if this is in place using git submodules or manually,
but will figure it out and get that updated.




 - Josh

On Tue, Feb 14, 2017 at 7:07 PM, Tom Fifield <t...@openstack.org
<mailto:t...@openstack.org>
<mailto:t...@openstack.org <mailto:t...@openstack.org>>> wrote:

On 14/02/17 16:06, Joshua Hesketh wrote:

Hey,

I've brought the service back up, but have no new clues
as to why.


Cheers.

Going to try: https://review.openstack.org/#/c/433478/
<https://review.openstack.org/#/c/433478/>
<https://review.openstack.org/#/c/433478/
<https://review.openstack.org/#/c/433478/>>
to see if this script is culprit.


        - Josh

On Tue, Feb 14, 2017 at 6:50 PM, Tom Fifield
<t...@openstack.org <mailto:t...@openstack.org>
<mailto:t...@openstack.org <mailto:t...@openstack.org>>
<mailto:t...@openstack.org <mailto:t...@openstack.org>
<mailto:t...@openstack.org <mailto:t...@openstack.org>>>> wrote:

    On 10/02/17 22:39, Jeremy Stanley wrote:

On 2017-02-10 16:08:51 +0800 (+0800), Tom
Fifield wrote:
[...]

Down again, this time with "Network is
unreachable".

[...]

I'm not finding any obvious errors on the
server nor
relevant
maintenance notices/trouble tickets from the
service
provider to
explain this. I do see conspicuous gaps in
network
traffic volume
and system load from ~06:45 to ~08:10 UTC
according to
cacti:


http://cacti.openstack.org/?tree_id=1_id=156
<http://cacti.openstack.org/?tree_id=1_id=156>
<http://cacti.openstack.org/?tree_id=1_id=156
<http://cacti.openstack.org/?tree_id=1_id=156>>

<http://cacti.openstack.org/?tree_id=1_id=156
<http://cacti.openstack.org/?tree_id=1_id=156>
<http://cacti.openstack.org/?tree_id=1_id=156
<http://cacti.openstack.org/?tree_id=1_id=156>>>

Skipping back through previous days I find some
similar gaps
starting anywhere from 06:30 to 07:00 and ending
between
07:00 and
08:00 but they don't seem to occur every day and
I'm not
having much
luck finding a pattern. It _is_ conspicuously
close to when
/etc/cron.daily scripts get fired from the
crontab so
might coincide
with log rotation/service restarts? The graphs
don't
show these gaps
correlating with any spikes in CPU, memory or
disk
  

Re: [OpenStack-Infra] Ask.o.o down

2017-02-20 Thread Tom Fifield



On 廿十七年二月十四日 暮 04:19, Joshua Hesketh wrote:



On Tue, Feb 14, 2017 at 7:15 PM, Tom Fifield <t...@openstack.org
<mailto:t...@openstack.org>> wrote:

On 14/02/17 16:11, Joshua Hesketh wrote:

Hey Tom,

Where is that script being fired from (a quick grep doesn't find
it), or
is it a tool people are using?

If it's a tool we'd need to make sure whoever is using it gets a new
version to rule it out.


Indeed.


It's fired from a PHP service on www.openstack.org
<http://www.openstack.org> itself, which writes to the Member database:


https://github.com/OpenStackweb/openstack-org/blob/master/auc-metrics/code/services/ActiveModeratorService.php

<https://github.com/OpenStackweb/openstack-org/blob/master/auc-metrics/code/services/ActiveModeratorService.php>



Right. I wonder if somebody could check the logs to see if the process
times out. Sadly looking at that code it looks like any output messages
from the script will be discarded.



... and my patch was deployed, but the site is down today. So, looks 
like it wasn't that.





The next step is to update the copy of the script it references:


https://github.com/OpenStackweb/openstack-org/blob/master/auc-metrics/lib/uc-recognition/tools/get_active_moderator.py

<https://github.com/OpenStackweb/openstack-org/blob/master/auc-metrics/lib/uc-recognition/tools/get_active_moderator.py>

I am not sure if this is in place using git submodules or manually,
but will figure it out and get that updated.




 - Josh

On Tue, Feb 14, 2017 at 7:07 PM, Tom Fifield <t...@openstack.org
<mailto:t...@openstack.org>
<mailto:t...@openstack.org <mailto:t...@openstack.org>>> wrote:

On 14/02/17 16:06, Joshua Hesketh wrote:

Hey,

I've brought the service back up, but have no new clues
as to why.


Cheers.

Going to try: https://review.openstack.org/#/c/433478/
<https://review.openstack.org/#/c/433478/>
<https://review.openstack.org/#/c/433478/
<https://review.openstack.org/#/c/433478/>>
to see if this script is culprit.


        - Josh

On Tue, Feb 14, 2017 at 6:50 PM, Tom Fifield
<t...@openstack.org <mailto:t...@openstack.org>
<mailto:t...@openstack.org <mailto:t...@openstack.org>>
<mailto:t...@openstack.org <mailto:t...@openstack.org>
<mailto:t...@openstack.org <mailto:t...@openstack.org>>>> wrote:

    On 10/02/17 22:39, Jeremy Stanley wrote:

On 2017-02-10 16:08:51 +0800 (+0800), Tom
Fifield wrote:
[...]

Down again, this time with "Network is
unreachable".

[...]

I'm not finding any obvious errors on the server nor
relevant
maintenance notices/trouble tickets from the service
provider to
explain this. I do see conspicuous gaps in network
traffic volume
and system load from ~06:45 to ~08:10 UTC
according to
cacti:


http://cacti.openstack.org/?tree_id=1_id=156
<http://cacti.openstack.org/?tree_id=1_id=156>
<http://cacti.openstack.org/?tree_id=1_id=156
<http://cacti.openstack.org/?tree_id=1_id=156>>

<http://cacti.openstack.org/?tree_id=1_id=156
<http://cacti.openstack.org/?tree_id=1_id=156>
<http://cacti.openstack.org/?tree_id=1_id=156
<http://cacti.openstack.org/?tree_id=1_id=156>>>

Skipping back through previous days I find some
similar gaps
starting anywhere from 06:30 to 07:00 and ending
between
07:00 and
08:00 but they don't seem to occur every day and
I'm not
having much
luck finding a pattern. It _is_ conspicuously
close to when
/etc/cron.daily scripts get fired from the
crontab so
might coincide
with log rotation/service restarts? The graphs don't
show these gaps
correlating with any spikes in CPU, memory or disk
activity so it
doesn't seem to be resource starvation (at least
not for
any common
resources we're tracking).


Indeed. It's down again today during the same timeslot.

Another idea for the cron-based theor

Re: [OpenStack-Infra] The new openstack.cl...@gmail.com user

2017-02-14 Thread Tom Fifield

On 14/02/17 22:33, Paul Belanger wrote:

On Tue, Feb 14, 2017 at 03:42:53PM +0530, Amrith Kumar wrote:

It appears that a user registered as "openstack.cl...@gmail.com" has emerged
as a new bot that is posting a comment on numerous reviews with comments
like:[1]

"Patch Set 1: Code-Review-1

Not urgent to merge just before Ocata is released. And please save load to
the CI system."

"Patch Set 1: Code-Review-1

With more than 50 same topics. Such work seems to be for some marketing
slides. Why not submit the same corrections in one patch?"

"Patch Set 1: Code-Review-1

Such work seems to be for some marketing slides, not for OpenStack
technology. Why not submit the same corrections in one patch?"

Would someone in Infra or the TC please take a look into who this anonymous
user is? I believe that to post reviews, one must register and sign a CLA.
Could someone look into who may have signed this CLA?

Thanks,

-amrith

[1]
https://review.openstack.org/#/q/reviewer:%22OpenStack+Clean+%253Copenstack.
clean%2540gmail.com%253E%22



--
Amrith Kumar
amrith.ku...@gmail.com
+1-978-563-9590
GPG: 0x5e48849a9d21a29b


I've gone a head a disabled the account for now. Until we can look more into it.


I noticed that the account only comments on contributors from ZTE. Maybe 
it's something someone set up to help their colleagues there?



___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


Re: [OpenStack-Infra] Ask.o.o down

2017-02-14 Thread Tom Fifield

On 14/02/17 16:11, Joshua Hesketh wrote:

Hey Tom,

Where is that script being fired from (a quick grep doesn't find it), or
is it a tool people are using?

If it's a tool we'd need to make sure whoever is using it gets a new
version to rule it out.


Indeed.


It's fired from a PHP service on www.openstack.org itself, which writes 
to the Member database:


https://github.com/OpenStackweb/openstack-org/blob/master/auc-metrics/code/services/ActiveModeratorService.php

The next step is to update the copy of the script it references:

https://github.com/OpenStackweb/openstack-org/blob/master/auc-metrics/lib/uc-recognition/tools/get_active_moderator.py

I am not sure if this is in place using git submodules or manually, but 
will figure it out and get that updated.






 - Josh

On Tue, Feb 14, 2017 at 7:07 PM, Tom Fifield <t...@openstack.org
<mailto:t...@openstack.org>> wrote:

On 14/02/17 16:06, Joshua Hesketh wrote:

Hey,

I've brought the service back up, but have no new clues as to why.


Cheers.

Going to try: https://review.openstack.org/#/c/433478/
<https://review.openstack.org/#/c/433478/>
to see if this script is culprit.


- Josh

On Tue, Feb 14, 2017 at 6:50 PM, Tom Fifield <t...@openstack.org
<mailto:t...@openstack.org>
<mailto:t...@openstack.org <mailto:t...@openstack.org>>> wrote:

On 10/02/17 22:39, Jeremy Stanley wrote:

    On 2017-02-10 16:08:51 +0800 (+0800), Tom Fifield wrote:
[...]

Down again, this time with "Network is unreachable".

[...]

I'm not finding any obvious errors on the server nor
relevant
maintenance notices/trouble tickets from the service
provider to
explain this. I do see conspicuous gaps in network
traffic volume
and system load from ~06:45 to ~08:10 UTC according to
cacti:

http://cacti.openstack.org/?tree_id=1_id=156
<http://cacti.openstack.org/?tree_id=1_id=156>
<http://cacti.openstack.org/?tree_id=1_id=156
<http://cacti.openstack.org/?tree_id=1_id=156>>

Skipping back through previous days I find some similar gaps
starting anywhere from 06:30 to 07:00 and ending between
07:00 and
08:00 but they don't seem to occur every day and I'm not
having much
luck finding a pattern. It _is_ conspicuously close to when
/etc/cron.daily scripts get fired from the crontab so
might coincide
with log rotation/service restarts? The graphs don't
show these gaps
correlating with any spikes in CPU, memory or disk
activity so it
doesn't seem to be resource starvation (at least not for
any common
resources we're tracking).


Indeed. It's down again today during the same timeslot.

Another idea for the cron-based theory:



https://github.com/openstack/uc-recognition/blob/master/tools/get_active_moderator.py

<https://github.com/openstack/uc-recognition/blob/master/tools/get_active_moderator.py>


<https://github.com/openstack/uc-recognition/blob/master/tools/get_active_moderator.py

<https://github.com/openstack/uc-recognition/blob/master/tools/get_active_moderator.py>>

loops through the list of Ask OpenStack users via the API on
a cron
running on www.openstack.org <http://www.openstack.org>
<http://www.openstack.org>. Not sure
when that cron runs, but if it's similar, this could
potentially be
a high-load generator.




Regards,


Tom


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
<mailto:OpenStack-Infra@lists.openstack.org>
<mailto:OpenStack-Infra@lists.openstack.org
<mailto:OpenStack-Infra@lists.openstack.org>>

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra>

<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra>>







___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


Re: [OpenStack-Infra] Ask.o.o down

2017-02-14 Thread Tom Fifield

On 14/02/17 16:06, Joshua Hesketh wrote:

Hey,

I've brought the service back up, but have no new clues as to why.


Cheers.

Going to try: https://review.openstack.org/#/c/433478/
to see if this script is culprit.



- Josh

On Tue, Feb 14, 2017 at 6:50 PM, Tom Fifield <t...@openstack.org
<mailto:t...@openstack.org>> wrote:

On 10/02/17 22:39, Jeremy Stanley wrote:

On 2017-02-10 16:08:51 +0800 (+0800), Tom Fifield wrote:
[...]

Down again, this time with "Network is unreachable".

[...]

I'm not finding any obvious errors on the server nor relevant
maintenance notices/trouble tickets from the service provider to
explain this. I do see conspicuous gaps in network traffic volume
and system load from ~06:45 to ~08:10 UTC according to cacti:

http://cacti.openstack.org/?tree_id=1_id=156
<http://cacti.openstack.org/?tree_id=1_id=156>

Skipping back through previous days I find some similar gaps
starting anywhere from 06:30 to 07:00 and ending between 07:00 and
08:00 but they don't seem to occur every day and I'm not having much
luck finding a pattern. It _is_ conspicuously close to when
/etc/cron.daily scripts get fired from the crontab so might coincide
with log rotation/service restarts? The graphs don't show these gaps
correlating with any spikes in CPU, memory or disk activity so it
doesn't seem to be resource starvation (at least not for any common
resources we're tracking).


Indeed. It's down again today during the same timeslot.

Another idea for the cron-based theory:


https://github.com/openstack/uc-recognition/blob/master/tools/get_active_moderator.py

<https://github.com/openstack/uc-recognition/blob/master/tools/get_active_moderator.py>

loops through the list of Ask OpenStack users via the API on a cron
running on www.openstack.org <http://www.openstack.org>. Not sure
when that cron runs, but if it's similar, this could potentially be
a high-load generator.




Regards,


Tom


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
<mailto:OpenStack-Infra@lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra>





___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


Re: [OpenStack-Infra] Ask.o.o down

2017-02-10 Thread Tom Fifield

On 10/02/17 16:41, Marton Kiss wrote:

Hi Tom

Still not working from your end? Works perfectly from here.


It is back now.



Marton

On Fri, Feb 10, 2017 at 9:14 AM Tom Fifield <t...@openstack.org
<mailto:t...@openstack.org>> wrote:

On 10/02/17 16:08, Tom Fifield wrote:
> On 13/01/17 14:41, Tom Fifield wrote:
>> As at 2017-01-13 0641Z, Ask.o.o is refusing connections (at least on
>> IPv4) - tried from a couple of different hosts
>>
>> fifieldt@docwork2:~$ wget ask.openstack.org
<http://ask.openstack.org>
>> --2017-01-13 06:40:49--  http://ask.openstack.org/
>> Resolving ask.openstack.org <http://ask.openstack.org>
(ask.openstack.org <http://ask.openstack.org>)... 23.253.72.95,
>> 2001:4800:7815:103:be76:4eff:fe05:89f3
>> Connecting to ask.openstack.org <http://ask.openstack.org>
(ask.openstack.org <http://ask.openstack.org>)|23.253.72.95|:80...
>> failed: Connection refused.
>
> Down again, this time with "Network is unreachable".

Sorry, it is still connection refused as before. The network unreachable
bit is my end's IPv6 connectivity :)


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
<mailto:OpenStack-Infra@lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra




___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


Re: [OpenStack-Infra] Ask.o.o down

2017-02-10 Thread Tom Fifield

On 13/01/17 14:41, Tom Fifield wrote:

As at 2017-01-13 0641Z, Ask.o.o is refusing connections (at least on
IPv4) - tried from a couple of different hosts

fifieldt@docwork2:~$ wget ask.openstack.org
--2017-01-13 06:40:49--  http://ask.openstack.org/
Resolving ask.openstack.org (ask.openstack.org)... 23.253.72.95,
2001:4800:7815:103:be76:4eff:fe05:89f3
Connecting to ask.openstack.org (ask.openstack.org)|23.253.72.95|:80...
failed: Connection refused.


Down again, this time with "Network is unreachable".


fifieldt@docwork2:~$ wget ask.openstack.org
--2017-02-10 08:07:10--  http://ask.openstack.org/
Resolving ask.openstack.org (ask.openstack.org)... 23.253.72.95, 
2001:4800:7815:103:be76:4eff:fe05:89f3
Connecting to ask.openstack.org (ask.openstack.org)|23.253.72.95|:80... 
failed: Connection refused.
Connecting to ask.openstack.org 
(ask.openstack.org)|2001:4800:7815:103:be76:4eff:fe05:89f3|:80... 
failed: Network is unreachable.




fifieldt@docwork2:~$ traceroute ask.openstack.org
traceroute to ask.openstack.org (23.253.72.95), 30 hops max, 60 byte packets
[snip]
11  xe-0-2-4.bdr1.a.sjc.aarnet.net.au (202.158.194.162)  160.649 ms 
160.670 ms  160.560 ms
12  xe-0-8-0-21.r01.snjsca04.us.bb.gin.ntt.net (128.241.219.153) 
161.276 ms  161.056 ms  161.216 ms
13  ae-10.r23.snjsca04.us.bb.gin.ntt.net (129.250.3.174)  161.199 ms 
161.050 ms  161.157 ms
14  ae-7.r23.dllstx09.us.bb.gin.ntt.net (129.250.4.155)  200.216 ms 
200.287 ms  200.261 ms
15  ae-26.r01.dllstx04.us.bb.gin.ntt.net (129.250.6.129)  199.711 ms 
199.693 ms  200.515 ms
16  ae-0.rackspace.dllstx04.us.bb.gin.ntt.net (129.250.207.118)  199.738 
ms  199.764 ms  199.303 ms

17  * * *
18  74.205.108.121 (74.205.108.121)  200.814 ms 
be41.coreb.dfw1.rackspace.net (74.205.108.117)  201.289 ms  202.648 ms
19  po1.corea-core10.core10.dfw3.rackspace.net (74.205.108.49)  201.402 
ms  202.792 ms po2.coreb-core10.core10.dfw3.rackspace.net 
(74.205.108.51)  201.389 ms
20  core9.aggr160a-4.dfw2.rackspace.net (98.129.84.201)  205.857 ms 
core9.aggr160b-4.dfw2.rackspace.net (98.129.84.203)  203.025 ms  204.921 ms
21  ask.openstack.org (23.253.72.95)  200.853 ms !X  202.494 ms !X 
200.562 ms !X



fifieldt@usagi:~$ traceroute ask.openstack.org
traceroute to ask.openstack.org (23.253.72.95), 30 hops max, 60 byte packets
[snip]
12  las-b21-link.telia.net (62.115.125.142)  137.764 ms  136.495 ms 
133.458 ms
13  dls-b21-link.telia.net (62.115.123.138)  203.140 ms 
dls-b21-link.telia.net (62.115.123.136)  166.356 ms 
dls-b21-link.telia.net (62.115.122.20)  168.077 ms
14  rackspace-ic-302090-dls-bb1.c.telia.net (62.115.33.78)  189.567 ms 
187.802 ms  178.015 ms
15  10.25.1.71 (10.25.1.71)  188.676 ms  184.027 ms 10.25.1.66 
(10.25.1.66)  172.849 ms
16  74.205.108.121 (74.205.108.121)  167.863 ms 
be41.corea.dfw1.rackspace.net (74.205.108.113)  186.449 ms 
74.205.108.121 (74.205.108.121)  167.069 ms
17  po1.corea-core9.core9.dfw3.rackspace.net (74.205.108.45)  204.053 ms 
 204.352 ms  182.891 ms
18  core9.aggr160b-4.dfw2.rackspace.net (98.129.84.203)  211.036 ms 
core10.aggr160b-4.dfw2.rackspace.net (98.129.84.207)  206.673 ms 
core10.aggr160a-4.dfw2.rackspace.net (98.129.84.205)  178.904 ms
19  ask.openstack.org (23.253.72.95)  200.364 ms !X  201.845 ms !X 
186.189 ms !X



___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


Re: [OpenStack-Infra] Ask.o.o down

2017-02-10 Thread Tom Fifield

On 10/02/17 16:08, Tom Fifield wrote:

On 13/01/17 14:41, Tom Fifield wrote:

As at 2017-01-13 0641Z, Ask.o.o is refusing connections (at least on
IPv4) - tried from a couple of different hosts

fifieldt@docwork2:~$ wget ask.openstack.org
--2017-01-13 06:40:49--  http://ask.openstack.org/
Resolving ask.openstack.org (ask.openstack.org)... 23.253.72.95,
2001:4800:7815:103:be76:4eff:fe05:89f3
Connecting to ask.openstack.org (ask.openstack.org)|23.253.72.95|:80...
failed: Connection refused.


Down again, this time with "Network is unreachable".


Sorry, it is still connection refused as before. The network unreachable 
bit is my end's IPv6 connectivity :)



___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


Re: [OpenStack-Infra] debugging post jobs

2017-01-26 Thread Tom Fifield

On 26/01/17 15:45, Andreas Jaeger wrote:

On 2017-01-26 08:24, Tom Fifield  wrote:

Hi infra,

I'm debugging a sphinx document change
(https://review.openstack.org/#/c/424706/ ) that uses a static-*-publish
job (jenkins/jobs/static-publish-jobs.yaml) in the post pipeline.

I can see the gate passing just fine
(http://docs-draft.openstack.org/06/424706/2/gate/gate-governance-uc-docs-ubuntu-xenial/c00670c//doc/build/html/
), and the change has merged into the repository successfully. However,
the target site isn't updated after >24 hours.

That indicates to me that the the static-*-publish post job has failed,
but I'm not sure where to look to find the logs for that. Any hints?


http://docs.openstack.org/infra/manual/developers.html#automated-testing
explains that in the step 1.

BUT:

Yesterday some CI systems needed a restart due to problems caused by one
provider AFAIK and that lost the post queue. So, this might not have run
at all.

If that change is critical, just push a new one up,


Phew, I thought I was going insane there - there is indeed no log 
directory for the commit. There's another patch in the queue, so no 
problems!



___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


[OpenStack-Infra] debugging post jobs

2017-01-25 Thread Tom Fifield

Hi infra,

I'm debugging a sphinx document change 
(https://review.openstack.org/#/c/424706/ ) that uses a static-*-publish 
job (jenkins/jobs/static-publish-jobs.yaml) in the post pipeline.


I can see the gate passing just fine 
(http://docs-draft.openstack.org/06/424706/2/gate/gate-governance-uc-docs-ubuntu-xenial/c00670c//doc/build/html/ 
), and the change has merged into the repository successfully. However, 
the target site isn't updated after >24 hours.


That indicates to me that the the static-*-publish post job has failed, 
but I'm not sure where to look to find the logs for that. Any hints?


Regards,


Tom

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


Re: [OpenStack-Infra] Ask.o.o down

2017-01-12 Thread Tom Fifield

... and at 0700Z it is back ...

On 13/01/17 14:41, Tom Fifield wrote:

As at 2017-01-13 0641Z, Ask.o.o is refusing connections (at least on
IPv4) - tried from a couple of different hosts

fifieldt@docwork2:~$ wget ask.openstack.org
--2017-01-13 06:40:49--  http://ask.openstack.org/
Resolving ask.openstack.org (ask.openstack.org)... 23.253.72.95,
2001:4800:7815:103:be76:4eff:fe05:89f3
Connecting to ask.openstack.org (ask.openstack.org)|23.253.72.95|:80...
failed: Connection refused.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra



___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


[OpenStack-Infra] Ask.o.o down

2017-01-12 Thread Tom Fifield
As at 2017-01-13 0641Z, Ask.o.o is refusing connections (at least on 
IPv4) - tried from a couple of different hosts


fifieldt@docwork2:~$ wget ask.openstack.org
--2017-01-13 06:40:49--  http://ask.openstack.org/
Resolving ask.openstack.org (ask.openstack.org)... 23.253.72.95, 
2001:4800:7815:103:be76:4eff:fe05:89f3
Connecting to ask.openstack.org (ask.openstack.org)|23.253.72.95|:80... 
failed: Connection refused.


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


Re: [OpenStack-Infra] [OpenStack-docs] [infra][docs] Steps to migrate docs.o.o to new AFS based server

2017-01-10 Thread Tom Fifield

On 11/01/17 12:33, Anne Gentle wrote:



On Tue, Jan 10, 2017 at 10:25 PM, Tom Fifield <t...@openstack.org
<mailto:t...@openstack.org>> wrote:

On 11/01/17 12:21, Anne Gentle wrote:



On Tue, Jan 10, 2017 at 10:13 PM, Tom Fifield <t...@openstack.org
<mailto:t...@openstack.org>
<mailto:t...@openstack.org <mailto:t...@openstack.org>>> wrote:

On 11/01/17 04:07, Andreas Jaeger wrote:

In case of any problems, please report them as reply to this
email or
directly on #openstack-infra.


404 pages are missing styling:


I think I can fix this by setting the css directory
{% set cssdir = '../common/css/' %}



eg

http://docs.openstack.org/kilo/networking-guide/scenario_legacy_lb.html

<http://docs.openstack.org/kilo/networking-guide/scenario_legacy_lb.html>

<http://docs.openstack.org/kilo/networking-guide/scenario_legacy_lb.html

<http://docs.openstack.org/kilo/networking-guide/scenario_legacy_lb.html>>


Also, getting a ton of 404s in my regular meanderings :)
Might be
worth pulling the apache logs and re-directing the top 404s
to docs
that exist today ? Happy to do the analysis if logs can be
provided.


Can you further describe regular meanderings? Search, click, or on a
browser that doesn't have a cleared cache? That'll help troubleshoot
further - and/or get the logs too.


So, example task I'm doing at the moment is updating the user
survey's list of supported drivers for Neutron. A specific bit of
that work is fixing the relationship between ML2 and the plugins -
so working out whether a driver is an ML2 mechanism driver or not.

Clicking - from https://www.openstack.org/marketplace/drivers/
<https://www.openstack.org/marketplace/drivers/> - more than a a few
links there fail; also wiki pages they link to contain links that
now 404.

Searching - entering search terms like "OpenStack Linux Bridge ML2"
into google, and the first 3 results are all 404s:
docs.openstack.org/kilo/networking-guide/scenario_legacy_lb.html
<http://docs.openstack.org/kilo/networking-guide/scenario_legacy_lb.html>
docs.openstack.org/kilo/networking-guide/deploy_scenario4b.html
<http://docs.openstack.org/kilo/networking-guide/deploy_scenario4b.html>
docs.openstack.org/mitaka/networking-guide/config-ml2-plug-in.html
<http://docs.openstack.org/mitaka/networking-guide/config-ml2-plug-in.html>


These are truly 404s. The file names changed and apparently were
available previously because of the lack of deletion mechanisms
automatically along with no proper redirect.

I think we'll need to carefully update .htaccess for proper redirects to
exact file names to fix this "for real." Anyone else think that's the
solution? I'm a bit too tired to do it accurately tonight, but the lines
are
here: 
https://github.com/openstack/openstack-manuals/blob/b0eb5baf51098459a873146f059bb6e6340742b0/www/static/.htaccess#L481


Indeed they are 404s - the content was deleted.

This problem isn't actually caused by the server migration, but how 
older docs are managed. Rather than deleting the content and breaking 
links, the solution is doing doc versioning 'properly': 
https://bugs.launchpad.net/openstack-manuals/+bug/1621685




Anne


___
OpenStack-docs mailing list
openstack-d...@lists.openstack.org
<mailto:openstack-d...@lists.openstack.org>
<mailto:openstack-d...@lists.openstack.org
<mailto:openstack-d...@lists.openstack.org>>

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs>

<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs>>




--

Read my blog: justwrite.click <https://justwriteclick.com>
Subscribe to Docs|Code: docslikecode.com
<http://docslikecode.com> <http://docslikecode.com>





--

Read my blog: justwrite.click <https://justwriteclick.com>
Subscribe to Docs|Code: docslikecode.com <http://docslikecode.com>



___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


Re: [OpenStack-Infra] [OpenStack-docs] [infra][docs] Steps to migrate docs.o.o to new AFS based server

2017-01-10 Thread Tom Fifield

On 11/01/17 12:21, Anne Gentle wrote:



On Tue, Jan 10, 2017 at 10:13 PM, Tom Fifield <t...@openstack.org
<mailto:t...@openstack.org>> wrote:

On 11/01/17 04:07, Andreas Jaeger wrote:

In case of any problems, please report them as reply to this
email or
directly on #openstack-infra.


404 pages are missing styling:


I think I can fix this by setting the css directory
{% set cssdir = '../common/css/' %}



eg
http://docs.openstack.org/kilo/networking-guide/scenario_legacy_lb.html
<http://docs.openstack.org/kilo/networking-guide/scenario_legacy_lb.html>


Also, getting a ton of 404s in my regular meanderings :) Might be
worth pulling the apache logs and re-directing the top 404s to docs
that exist today ? Happy to do the analysis if logs can be provided.


Can you further describe regular meanderings? Search, click, or on a
browser that doesn't have a cleared cache? That'll help troubleshoot
further - and/or get the logs too.


So, example task I'm doing at the moment is updating the user survey's 
list of supported drivers for Neutron. A specific bit of that work is 
fixing the relationship between ML2 and the plugins - so working out 
whether a driver is an ML2 mechanism driver or not.


Clicking - from https://www.openstack.org/marketplace/drivers/ - more 
than a a few links there fail; also wiki pages they link to contain 
links that now 404.


Searching - entering search terms like "OpenStack Linux Bridge ML2" into 
google, and the first 3 results are all 404s:

docs.openstack.org/kilo/networking-guide/scenario_legacy_lb.html
docs.openstack.org/kilo/networking-guide/deploy_scenario4b.html
docs.openstack.org/mitaka/networking-guide/config-ml2-plug-in.html


Anne




___
OpenStack-docs mailing list
openstack-d...@lists.openstack.org
<mailto:openstack-d...@lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs>




--

Read my blog: justwrite.click <https://justwriteclick.com>
Subscribe to Docs|Code: docslikecode.com <http://docslikecode.com>



___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


Re: [OpenStack-Infra] [OpenStack-docs] [infra][docs] Steps to migrate docs.o.o to new AFS based server

2017-01-10 Thread Tom Fifield

On 11/01/17 04:07, Andreas Jaeger wrote:

In case of any problems, please report them as reply to this email or
directly on #openstack-infra.


404 pages are missing styling:

eg http://docs.openstack.org/kilo/networking-guide/scenario_legacy_lb.html


Also, getting a ton of 404s in my regular meanderings :) Might be worth 
pulling the apache logs and re-directing the top 404s to docs that exist 
today ? Happy to do the analysis if logs can be provided.


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


Re: [OpenStack-Infra] Logs for Ask.O.o - chasing false positive spam labeling

2017-01-05 Thread Tom Fifield

On 05/01/17 23:26, Jeremy Stanley wrote:

On 2017-01-02 23:03:07 + (+), Jeremy Stanley wrote:
[...]

We're basically ready to retry the previous upgrade now that some
issues have been identified/corrected by Marton. Change
https://review.openstack.org/408657 to trigger it is waiting on
https://review.openstack.org/416072 to grant him a shell account on
the production server for improved reactivity if it fails again, so
that he can collaborate with us more directly troubleshooting before
we have to make the call to fix or revert.

[...]

With much credit to Marton's efforts, we upgraded Askbot on
ask.openstack.org yesterday to a much more recent version (and it's
still up now a day later with no complaints AFAIK). It's worth
rechecking for further issues similar to what you experienced
previously, to see whether they're resolved now.



Wohoo! Many thanks - I just asked my test user to try it out

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


Re: [OpenStack-Infra] Logs for Ask.O.o - chasing false positive spam labeling

2017-01-02 Thread Tom Fifield

On 03/01/17 07:03, Jeremy Stanley wrote:

On 2016-12-30 12:38:02 +0800 (+0800), Tom Fifield wrote:

This problem (legitimate users having all posts flatly rejected as
spam) is still happening. Any progress?


We're basically ready to retry the previous upgrade now that some
issues have been identified/corrected by Marton. Change
https://review.openstack.org/408657 to trigger it is waiting on
https://review.openstack.org/416072 to grant him a shell account on
the production server for improved reactivity if it fails again, so
that he can collaborate with us more directly troubleshooting before
we have to make the call to fix or revert.


Excellent!


I've been doing what I can without access to the server, but my
latest attempt - completely deleting an account so it could be
re-created by the affected user - was thwarted by a 500 error. Did
that appear in the logs?


Given that I don't know the exact time you tried nor your IP
address, and am unsure what that failure would look like in the logs
aside from coming with a 500 error code this Apache access log entry
18 minutes before your E-mail's timestamp stands out:

[30/Dec/2016:04:20:40 +] "GET /admin/askbot/post/25842/
HTTP/1.1" 500 917
"https://ask.openstack.org/admin/auth/user/2253/delete/;
"Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:50.0) Gecko/20100101
Firefox/50.0"

I don't see anything related around that timeframe in the Apache
error log files, the Askbot application log, the Solr Jetty log...
though there's this in dmesg which is suspiciously close (timestamps
in dmesg aren't entirely reliable, so this could have happened 5
minutes earlier):

[Fri Dec 30 04:25:25 2016] apache2 invoked oom-killer:
gfp_mask=0x200da, order=0, oom_score_adj=0

And indeed, there's a spike in swap utilization around that time
which, given the five-minute granularity could certainly support the
notion that a runaway process ate all available virtual memory on
the system:

http://cacti.openstack.org/cacti/graph.php?action=zoom_graph_id=2546_id=2_type=_start=1483029900_end=1483156284_height=120_width=500_font_size=10
 >

The RAM usage graph suggests we were doing okay with a target
utilization of ~50% so something eating an additional 6GiB of memory
in a matter of a few minutes would definitely count as anomalous:

http://cacti.openstack.org/cacti/graph.php?action=zoom_graph_id=2544_id=2_type=_start=1483029900_end=1483156284_height=120_width=500_font_size=10
 >

Was the memory spike caused by that deletion? Or was the deletion
error coincidental and caused by a memory event which just happened
to be going on at the same time? I have insufficient knowledge of
the system to be able to say either way. It's possible there are
additional logs I don't know to look at which could tell us.



Ah, how silly of me to fail to specify information - apologies!


If you check for a POST after a GET of:

/admin/auth/user/2253/delete/

Around

2017-02-03 02:52

from

1.169.254.207

that should be it.


I believe the OOM error comes from trying to view any post in the django 
admin interface (/admin/askbot/post/%d/ ) -- those things essentially 
never stop loading for some reason.







___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


Re: [OpenStack-Infra] Logs for Ask.O.o - chasing false positive spam labeling

2016-12-29 Thread Tom Fifield

On 10/11/16 22:23, Jeremy Stanley wrote:

On 2016-11-10 09:19:32 + (+), Marton Kiss wrote:

Jeremy, I can apply and test this patch in a current test environment, it
was sitting there for a while. Usually the config changes of askbot broke
the site.

[...]

If you get a chance, that would be a big help. I have logs from the
failed upgrade, but the gist is that the git resource provider
didn't update /srv/dist/askbot (Puppet's log never even mentions it
trying to do so) and then then migrate command threw:

AttributeError: 'Settings' object has no attribute 'ASKBOT_MULTILINGUAL'

Which their upgrade FAQ says is an indication that the urls.py
template needs to be updated (and that makes sense given that the
git repo never moved to the newer commit we specified). I mulled
over possibilities with others in #openstack-infra, and Spencer
suggested that latest=>true may be causing calls into the provider
to short-circuit since it always returns true if a commit or tag is
passed. The next round, I was going to try dropping that from the
commit and tag cases in puppet-askbot and seeing if it helps.



Hi,

This problem (legitimate users having all posts flatly rejected as spam) 
is still happening. Any progress?


I've been doing what I can without access to the server, but my latest 
attempt - completely deleting an account so it could be re-created by 
the affected user - was thwarted by a 500 error. Did that appear in the 
logs?




Regards,


Tom

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


[OpenStack-Infra] Logs for Ask.O.o - chasing false positive spam labeling

2016-11-08 Thread Tom Fifield

Hi infra,

I've got another live report from someone whose post on Ask OpenStack is 
being flatly rejected as spam. This is despite the fact we have Ask set 
up to send spam to a moderation queue, and I've bumped up the account 
karma to a level which should bypass that anyway. Checking on the 
Akismet side of things (which provides the spam yay/nay), it is 
certainly chalking up a lot of spam hits (hundreds) that are not making 
it into the moderation queue.



Needless to say, it's a bit odd. Upstream apparently revamped the spam 
system in the version marked to upgrade to in: 
https://review.openstack.org/#/c/274032/


However, in order to make sure we're not losing up to 60% (akismet stat 
for October) of our potential legitimate posts while we wait for that, 
it would be great if there were some logs to try and find out what's 
going on.


Anyone able to dig and send me something?

(If you got curious and want something to grep for, try 
2001:638:70e:11:2ad2:44ff:*:* || 136.172.17.* )



Regards,


Tom

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


[OpenStack-Infra] Gerrit group adds for user-committee

2016-07-19 Thread Tom Fifield

Hello Infra!


Two new gerrit groups need the same list of people added to them:

https://review.openstack.org/#/admin/groups/1454,members

https://review.openstack.org/#/admin/groups/1453,members

They are:

shilla.sa...@gmail.com
emag...@gmail.com
j...@csail.mit.edu


Can we make it happen? :)




(NB: You can verify these names at 
https://www.openstack.org/foundation/user-committee/ if needed)




Regards,


Tom



___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


[OpenStack-Infra] Add tom@o.o to gerrit group 1361

2016-04-17 Thread Tom Fifield

Hi,

Following up from the successful merging of the governance and 
project-config repo patches, can I please get:


t...@openstack.org

Added to

https://review.openstack.org/#/admin/groups/1361,members

so other members can be added?


Regards,


Tom

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


Re: [OpenStack-Infra] Wiki.o.o sustaining spam attack

2016-03-22 Thread Tom Fifield

On 23/03/16 13:05, Tom Fifield wrote:

On 23/03/16 11:19, Tom Fifield wrote:

On 23/03/16 00:14, Paul Belanger wrote:

On Tue, Mar 22, 2016 at 03:32:23PM +0800, Tom Fifield wrote:

Hi all,


I'm sad to say that:

* spammers are back - 100-odd pages have gone in over the weekend
https://wiki.openstack.org/wiki/Special:NewPages

* Cleanup was ineffective, with many spam pages still existing on
the wiki
(scroll through the NewPages link above)


So, just a quick update to this.  We just landed 287323[1] which
installs
SmiteSpam[2]. If you are in the bureaucrat group on wiki.o.o you'll
be able to
access it.

Currently I've started the process on cleanup the wiki.  At the
moment, I've
blocked 54[3] account and delete 430+[4] pages. I'll send a follow up
email once
I am done for the day, but moving forward it will be easier for
admins to detect
the spam and stop it faster.

[1] https://review.openstack.org/#/c/287232/
[2] https://wiki.openstack.org/wiki/Special:SmiteSpam
[3] https://wiki.openstack.org/wiki/Special:Log/block
[4] https://wiki.openstack.org/wiki/Special:Log/delete



Cheers Paul! This looks like a very handy extension. I've deleted a
couple pages already



So, *sigh*. I've been trying to use

https://wiki.openstack.org/wiki/Special:Nuke

to delete pages matching

%1%800% (there are about 5000)

and it doesn't work :(

Everything appears to be fine, but the pages don't get deleted or appear
on the deletion log.


Also, appear to have exhausted the usefulness of smitespam for our 
particular case (though I suspect it will be good for the future). It 
appears to focus on pages with lots of external links, whereas our spam 
was mainly text-based, so even though many spam pages remain they aren't 
listed at smitespam.




___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


Re: [OpenStack-Infra] Wiki.o.o sustaining spam attack

2016-03-22 Thread Tom Fifield

On 23/03/16 11:19, Tom Fifield wrote:

On 23/03/16 00:14, Paul Belanger wrote:

On Tue, Mar 22, 2016 at 03:32:23PM +0800, Tom Fifield wrote:

Hi all,


I'm sad to say that:

* spammers are back - 100-odd pages have gone in over the weekend
https://wiki.openstack.org/wiki/Special:NewPages

* Cleanup was ineffective, with many spam pages still existing on the wiki
(scroll through the NewPages link above)


So, just a quick update to this.  We just landed 287323[1] which installs
SmiteSpam[2]. If you are in the bureaucrat group on wiki.o.o you'll be able to
access it.

Currently I've started the process on cleanup the wiki.  At the moment, I've
blocked 54[3] account and delete 430+[4] pages. I'll send a follow up email once
I am done for the day, but moving forward it will be easier for admins to detect
the spam and stop it faster.

[1] https://review.openstack.org/#/c/287232/
[2] https://wiki.openstack.org/wiki/Special:SmiteSpam
[3] https://wiki.openstack.org/wiki/Special:Log/block
[4] https://wiki.openstack.org/wiki/Special:Log/delete



Cheers Paul! This looks like a very handy extension. I've deleted a
couple pages already



So, *sigh*. I've been trying to use

https://wiki.openstack.org/wiki/Special:Nuke

to delete pages matching

%1%800% (there are about 5000)

and it doesn't work :(

Everything appears to be fine, but the pages don't get deleted or appear 
on the deletion log.



___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


Re: [OpenStack-Infra] Wiki.o.o sustaining spam attack

2016-03-22 Thread Tom Fifield
On 23/03/16 00:14, Paul Belanger wrote:
> On Tue, Mar 22, 2016 at 03:32:23PM +0800, Tom Fifield wrote:
>> Hi all,
>>
>>
>> I'm sad to say that:
>>
>> * spammers are back - 100-odd pages have gone in over the weekend
>> https://wiki.openstack.org/wiki/Special:NewPages
>>
>> * Cleanup was ineffective, with many spam pages still existing on the wiki
>> (scroll through the NewPages link above)
>>
> So, just a quick update to this.  We just landed 287323[1] which installs
> SmiteSpam[2]. If you are in the bureaucrat group on wiki.o.o you'll be able to
> access it.
> 
> Currently I've started the process on cleanup the wiki.  At the moment, I've
> blocked 54[3] account and delete 430+[4] pages. I'll send a follow up email 
> once
> I am done for the day, but moving forward it will be easier for admins to 
> detect
> the spam and stop it faster.
> 
> [1] https://review.openstack.org/#/c/287232/
> [2] https://wiki.openstack.org/wiki/Special:SmiteSpam
> [3] https://wiki.openstack.org/wiki/Special:Log/block
> [4] https://wiki.openstack.org/wiki/Special:Log/delete
> 

Cheers Paul! This looks like a very handy extension. I've deleted a
couple pages already

Regards,


Tom

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


Re: [OpenStack-Infra] Wiki.o.o sustaining spam attack

2016-03-22 Thread Tom Fifield

Hi all,


I'm sad to say that:

* spammers are back - 100-odd pages have gone in over the weekend
https://wiki.openstack.org/wiki/Special:NewPages

* Cleanup was ineffective, with many spam pages still existing on the 
wiki (scroll through the NewPages link above)




Regards,


Tom


On 28/02/16 01:11, JP Maxwell wrote:

Elizabeth

I hope you feel better.

Just FYI, this is going full force in IRC right now.  I’ve bowed out as
the approach I was suggesting didn’t get traction.

I proposed to manually iterate on this to confirm precisely which change
solves the spam problem.  Once that has been identified we can revert
and come up with a proper patch.  Right now the assumption is that
disabling manual accounts will solve the problem (and it might).  As a
result the team is trying to solve for the consequences of not having
manual accounts.  Some bots currently use manual accounts among other
issues.  If the assumption is correct, these efforts will be worth it.
  However, if it isn’t it will have been a great waste of energy.

In any case have a good weekend everyone.  I’m off to eat some delicious
central Texas BBQ!


*J.P. Maxwell* | tipit.net  | fibercove.com


On Sat, Feb 27, 2016 at 10:15 AM, Elizabeth K. Joseph
 wrote:

We'll be getting together on Monday around 1700 UTC to work through
this together in a debug session in #openstack-infra (I'm too sick
this weekend, plus we need a time when more infra-root folks with
the institutional knowledge are around).

On Feb 27, 2016 05:37, "Marton Kiss" > wrote:

Yeah, the Settings.php was overriden by the latest puppet run.
We need to wait for some infra guys to approve my patches and
make it permanent:
https://review.openstack.org/285669 Disable standard password
based auth
https://review.openstack.org/285672 Disable mobile frontend

M.

On Sat, Feb 27, 2016 at 2:27 PM JP Maxwell > wrote:

FYI. Still seeing the mobile view...

J.P. Maxwell | tipit.net  | fibercove.com


On Feb 27, 2016 6:53 AM, "Marton Kiss"
> wrote:

Yes, applied them manually. Let's wait a few hours, and
check for new spam content / user accounts.

M.
JP Maxwell >
(időpont: 2016. febr. 27., Szo, 13:50) ezt írta:

Cool. Are these applied? Any indication it has
stopped the spam? Should we clear out these non
launchpad accounts from the DB?

J.P. Maxwell | tipit.net  |
fibercove.com 

On Feb 27, 2016 6:47 AM, "Marton Kiss"
> wrote:

And the mobile frontend will be disabled
permanently with this patch:
https://review.openstack.org/285672 Disable
mobile frontend

M.

On Sat, Feb 27, 2016 at 1:39 PM Marton Kiss
> wrote:

I made some investigation, and it seems to
be that the spam pages are created by
accounts registered with password accounts,
and the launchpad openid auth is not
affected at all.

So the spam script is creating accounts like
this:
mysql> select * from user where user_name =
'CedricJamieson'\G;
*** 1. row
***
user_id: 7494
user_name: CedricJamieson
user_real_name: Cedric Jamieson
user_password:

:pbkdf2:sha256:1:128:Mlo9tdaP+38niZrrEka7Ow==:jEVnrTclkwIpE1RzJywDlrSvkY5G3idYwOwYRkv5O0J/MSHjY+gdhtKmArQ53v6/w7o8E1wXb2QOR6HdL5TPfOI1bswS/fYXVVYjPjkEEdxqZ8q9L5p2f3N6rEYpMfT5tk+wDiy+j5aimrHrGSga44hndAHgX9/SnqUyxlutDVY=
user_newpassword:
user_newpass_time: NULL
user_email: balashkina.evdok...@mail.ru

user_touched: 

Re: [OpenStack-Infra] Wiki.o.o sustaining spam attack

2016-02-22 Thread Tom Fifield

Cheers, that's exactly what we need someone to do.

On 23/02/16 15:34, JP Maxwell wrote:

OK - so per the info here, you have to set the type of Captcha and add
in editing and create page as triggers requiring Captcha.

As an example to use QuestyCaptcha a the bottom of the LocalSettings.php
file:

https://www.mediawiki.org/wiki/Extension:ConfirmEdit#QuestyCaptcha

And make sure the triggers are set:

https://www.mediawiki.org/wiki/Extension:ConfirmEdit#Configuration

So, for example (you might want to change the questions), but the below
should at least stop the bleeding?

require_once "$IP/extensions/ConfirmEdit/ConfirmEdit.php";

// Use this line ONLY if your MediaWiki version is 1.25 or newer:
//wfLoadExtension( 'ConfirmEdit/QuestyCaptcha' );
// Use this line ONLY if your MediaWiki version is older than 1.25:
require_once "$IP/extensions/ConfirmEdit/QuestyCaptcha.php";

$wgCaptchaClass = 'QuestyCaptcha';

// Add your questions in LocalSettings.php using this format
$wgCaptchaQuestions[] = array( 'question' => "A question?", 'answer' =>
"An Answer");
$wgCaptchaQuestions[] = array( 'question' => 'How much wood would a
woodchuck chuck if a woodchuck could chuck wood?', 'answer' => 'as much
wood as...' );
$wgCaptchaQuestions[] = array( 'question' => "What is this wiki's
name?", 'answer' => "$wgSitename" );
// You can also provide several acceptable answers to a given question
(the answers shall be in lowercase):
$wgCaptchaQuestions[] = array( 'question' => "2 + 2 ?", 'answer' =>
array( '4', 'four' ) );

$wgCaptchaTriggers['edit']  = true;
$wgCaptchaTriggers['create']= true;


J.P. Maxwell / tipit.net <http://www.tipit.net>


On Tue, Feb 23, 2016 at 12:55 AM, Tom Fifield <t...@openstack.org
<mailto:t...@openstack.org>> wrote:

For wiki.o.o, I believe this is at:

https://wiki.openstack.org/wiki/Special:Version

On 23/02/16 14:51, JP Maxwell wrote:

I did setup a wiki and have a look at this briefly.   Can you
confirm
what extensions you are loading?  When you setup the wiki it
generates a
localsettings.php file that lists the extensions:



Inline image 1

# Enabled Extensions. Most extensions are enabled by including
the base
extension file here
# but check specific extension documentation for more details
# The following extensions were automatically enabled:
wfLoadExtension( 'ConfirmEdit' );
wfLoadExtension( 'InputBox' );
wfLoadExtension( 'SpamBlacklist' );
wfLoadExtension( 'TitleBlacklist' );
wfLoadExtension( 'WikiEditor' );

I think if you have that ConfirmEdit extension you can enable
captcha
when creating new pages / editing existing ones.  In addition,
there do
seem to be some spam extensions that come built in.





___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


Re: [OpenStack-Infra] Wiki.o.o sustaining spam attack

2016-02-22 Thread Tom Fifield

Hi all,

Spam pages now outnumber content pages on our wiki.

I have stopped trying to keep up with deleting them, after putting in 
many, many hours.



Is there any chance someone can make the configuration changes I posted 
a couple weeks back, as an emergency measure?



*  update Apache web server configuration to block all spammer IPs in 
lists available from www.stopforumspam.com . Alternate, use the 
mediawiki plugin that does the same: 
https://www.mediawiki.org/wiki/Extension:StopForumSpam


* Configre the ConfirmEdit extension to set it to display a CAPTCHA when 
creating a new page:


$wgCaptchaTriggers['create']= true;



Regards,


Tom

On 15/02/16 22:05, Tom Fifield wrote:

Is there anyone who can help with this? There's still a ton of spam
going in, and manually cleaning it is a ton of effort.

On 12/02/16 06:40, Tom Fifield wrote:

OK, so, MediaWiki nas a nice manual on how to combat spam (
https://www.mediawiki.org/wiki/Manual:Combating_spam )

Would it be possible to get these implemented:

*  update Apache web server configuration to block all spammer IPs in
lists available from www.stopforumspam.com . Alternate, use the
mediawiki plugin that does the same:
https://www.mediawiki.org/wiki/Extension:StopForumSpam

* Configre the ConfirmEdit extension to set it to display a CAPTCHA when
creating a new page:

$wgCaptchaTriggers['create']= true;


Regards,


Tom


On 12/02/16 11:08, Tom Fifield wrote:

Hi,

Since about 11th January, wiki.o.o has been under attack by spammers.

They're creating new pages at a rate of more than 50 a day, with titles
that hint at calling certain phone numbers for various services.

If you look at

https://wiki.openstack.org/w/index.php?title=Special:NewPages

you'll see them.

It's across more than a dozen user accounts. I'm going to attempt some
cleaning, but we probably need to look for an extension to do something
about this pro-actively.



Regards,


Tom


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra



___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra



___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


Re: [OpenStack-Infra] Wiki.o.o sustaining spam attack

2016-02-15 Thread Tom Fifield
Is there anyone who can help with this? There's still a ton of spam 
going in, and manually cleaning it is a ton of effort.


On 12/02/16 06:40, Tom Fifield wrote:

OK, so, MediaWiki nas a nice manual on how to combat spam (
https://www.mediawiki.org/wiki/Manual:Combating_spam )

Would it be possible to get these implemented:

*  update Apache web server configuration to block all spammer IPs in
lists available from www.stopforumspam.com . Alternate, use the
mediawiki plugin that does the same:
https://www.mediawiki.org/wiki/Extension:StopForumSpam

* Configre the ConfirmEdit extension to set it to display a CAPTCHA when
creating a new page:

$wgCaptchaTriggers['create']= true;


Regards,


Tom


On 12/02/16 11:08, Tom Fifield wrote:

Hi,

Since about 11th January, wiki.o.o has been under attack by spammers.

They're creating new pages at a rate of more than 50 a day, with titles
that hint at calling certain phone numbers for various services.

If you look at

https://wiki.openstack.org/w/index.php?title=Special:NewPages

you'll see them.

It's across more than a dozen user accounts. I'm going to attempt some
cleaning, but we probably need to look for an extension to do something
about this pro-actively.



Regards,


Tom


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra



___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


Re: [OpenStack-Infra] Wiki.o.o sustaining spam attack

2016-02-11 Thread Tom Fifield
OK, so, MediaWiki nas a nice manual on how to combat spam ( 
https://www.mediawiki.org/wiki/Manual:Combating_spam )


Would it be possible to get these implemented:

*  update Apache web server configuration to block all spammer IPs in 
lists available from www.stopforumspam.com . Alternate, use the 
mediawiki plugin that does the same: 
https://www.mediawiki.org/wiki/Extension:StopForumSpam


* Configre the ConfirmEdit extension to set it to display a CAPTCHA when 
creating a new page:


$wgCaptchaTriggers['create']= true;


Regards,


Tom


On 12/02/16 11:08, Tom Fifield wrote:

Hi,

Since about 11th January, wiki.o.o has been under attack by spammers.

They're creating new pages at a rate of more than 50 a day, with titles
that hint at calling certain phone numbers for various services.

If you look at

https://wiki.openstack.org/w/index.php?title=Special:NewPages

you'll see them.

It's across more than a dozen user accounts. I'm going to attempt some
cleaning, but we probably need to look for an extension to do something
about this pro-actively.



Regards,


Tom


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra



___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


[OpenStack-Infra] Wiki.o.o sustaining spam attack

2016-02-11 Thread Tom Fifield

Hi,

Since about 11th January, wiki.o.o has been under attack by spammers.

They're creating new pages at a rate of more than 50 a day, with titles 
that hint at calling certain phone numbers for various services. As a 
result, google has started de-ranking o.o :)


If you look at

https://wiki.openstack.org/w/index.php?title=Special:NewPages

you'll see them.

It's across more than a dozen user accounts. I'm going to attempt some 
manual cleaning, but we probably need to look for an extension to do 
something about this pro-actively.




Regards,


Tom


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


[OpenStack-Infra] Scheduling a monthly meeting

2015-06-16 Thread Tom Fifield
Hi all,

A couple of things I'm working on at the moment would like to meet on a
monthly basis.

From irc-meetings:  Options for the `frequency` are `weekly`,
`biweekly-even`, and  `biweekly-odd` at the moment., and in
yaml2ical/recurrence.py [1] it's pretty clear that there's no support
for Monthly.

So ... first question: is there some enormous trap that means adding
support to the code for monthly meetings is best avoided/really hard?


According to ICAL examples[2], it looks like monthly is basically done
as based on a day, and a week-of-month position:

eg 1st Friday of the Month
  DTSTART;TZID=US-Eastern:19970905T09
  RRULE:FREQ=MONTHLY;BYDAY=1FR

eg Second to last Monday of the Month:

  DTSTART;TZID=US-Eastern:19970922T09
  RRULE:FREQ=MONTHLY;BYDAY=-2MO

So, second question, if one was to implement this, what schedule entry
format would be the best:

A)
schedule:
- time:   '1400'
  day:1st-Friday
  irc:openstack-meeting
  frequency:  monthly

B)
schedule:
- time:   '1400'
  day:Friday
  irc:openstack-meeting
  frequency:  monthly
  month-week:  1

C) other?


Thanks for your input!


Regards,


Tom

[1]
https://github.com/openstack-infra/yaml2ical/blob/master/yaml2ical/recurrence.py
[2] http://www.kanzaki.com/docs/ical/rrule.html

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


Re: [OpenStack-Infra] [openstack-dev] Need help! Zuul can not connect to port 29418 of review.openstack.org

2015-06-12 Thread Tom Fifield

On 12/06/15 17:04, liuxinguo wrote:

Hi,

Recentlyour CI can not connect to port 29418 of
review.openstack.org.app:ds:recently

Following are the failuer message, is there anyone know the reasion why
our CI can not cennect to 29418 of review.openstack.org?



That port on review.openstack.org currently appears to be blocked by 
China country-level firewall.


In this case, changing access from SSH to HTTPS could help avoid the
block, like in Clark's email:

http://lists.openstack.org/pipermail/openstack-dev/2014-September/045385.html


Regards,


Tom

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


Re: [OpenStack-Infra] I can not update the contact information.

2014-11-08 Thread Tom Fifield
On 08/11/14 10:17, Zebra wrote:
 Hi all
 
 Can anybody help me about why can not I update the contact information
 in http://review.ustack.com/?
 
 The server error Cannot store contact information returned. 
 
 And if I do not fill the Mailing Address, Country , Phone Number ,Fax
 Number, I can not commit my source code for review.
 
 Any suggestion will be appreciated.
 
 Thank you!

Please see this FAQ entry:

https://wiki.openstack.org/wiki/CLA-FAQ#When_trying_to_sign_the_new_ICLA_and_include_contact_information.2C_why_am_I.27m_getting_an_error_message_saying_that_my_E-mail_address_doesn.27t_correspond_to_a_Foundation_membership.3F

Regards,


Tom


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


[OpenStack-Infra] Changing the Gerrit Text for -1

2014-08-21 Thread Tom Fifield
Hi Infra,

I vaguely recall a discussion where it was stated that should someone
come up with a better phrase for the -1 text (I would prefer that you
didn't merge this), we could change the text to that.

The below suggestion has a few people agreeing with it. Perhaps we could
put in a patch to change the text, and see how it goes?

Regards,


Tom


 Forwarded Message 
Subject: Re: [openstack-dev] Criteria for giving a -1 in a review
Date: Thu, 21 Aug 2014 17:21:19 +0100
From: Daniel P. Berrange berra...@redhat.com
Reply-To: Daniel P. Berrange berra...@redhat.com, OpenStack
Development Mailing List (not for usage questions)
openstack-...@lists.openstack.org
To: OpenStack Development Mailing List (not for usage questions)
openstack-...@lists.openstack.org

On Thu, Aug 21, 2014 at 05:05:04PM +0100, Matthew Booth wrote:
 I would prefer that you didn't merge this.
 
 i.e. The project is better off without it.

A bit off topic, but I've never liked this message that gets added
as it think it sounds overly negative. It would better written
as

  This patch needs further work before it can be merged

as that gives a positive expectation that the work is still
wanted by the project in general

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


Re: [OpenStack-Infra] Changing the Gerrit Text for -1

2014-08-21 Thread Tom Fifield
On 22/08/14 13:20, Clark Boylan wrote:
 On Thu, Aug 21, 2014, at 09:26 PM, Tom Fifield wrote:
 Hi Infra,

 I vaguely recall a discussion where it was stated that should someone
 come up with a better phrase for the -1 text (I would prefer that you
 didn't merge this), we could change the text to that.

 The below suggestion has a few people agreeing with it. Perhaps we could
 put in a patch to change the text, and see how it goes?

 Regards,


 Tom


  Forwarded Message 
 Subject: Re: [openstack-dev] Criteria for giving a -1 in a review
 Date: Thu, 21 Aug 2014 17:21:19 +0100
 From: Daniel P. Berrange berra...@redhat.com
 Reply-To: Daniel P. Berrange berra...@redhat.com, OpenStack
 Development Mailing List (not for usage questions)
 openstack-...@lists.openstack.org
 To: OpenStack Development Mailing List (not for usage questions)
 openstack-...@lists.openstack.org

 On Thu, Aug 21, 2014 at 05:05:04PM +0100, Matthew Booth wrote:
 I would prefer that you didn't merge this.

 i.e. The project is better off without it.

 A bit off topic, but I've never liked this message that gets added
 as it think it sounds overly negative. It would better written
 as

   This patch needs further work before it can be merged

 as that gives a positive expectation that the work is still
 wanted by the project in general

 ___
 OpenStack-Infra mailing list
 OpenStack-Infra@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
 
 Unfortunately, the actual file that needs to be edited to enact this
 change isn't managed by our tooling. We still curate by hand because of
 a chicken and egg issue managing the All-Projects ACL file (you can't
 manage the file until you have the file in place...). But we do document
 what we expect to be in that file. I have gone ahead and proposed
 https://review.openstack.org/#/c/116176 and we can argue over the value
 there. If we agree one of the gerrit admins can update the All-Projects
 ACL file.


Awesome! I'll link your patch to the appropriate point in the thread.



___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


[OpenStack-Infra] Change in openstack/operations-guide[master]: Imported Translations from Transifex

2014-04-17 Thread Tom Fifield (Code Review)
Tom Fifield has posted comments on this change.

Change subject: Imported Translations from Transifex
..


Patch Set 1: Looks good to me (core reviewer); Approved

loving the new script

--
To view, visit https://review.openstack.org/88157
To unsubscribe, visit https://review.openstack.org/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: I52a9bdaf638dc095a8744c2df3eded6cca1f2673
Gerrit-PatchSet: 1
Gerrit-Project: openstack/operations-guide
Gerrit-Branch: master
Gerrit-Owner: OpenStack Proposal Bot openstack-infra@lists.openstack.org
Gerrit-Reviewer: Andreas Jaeger jaegera...@gmail.com
Gerrit-Reviewer: Jenkins
Gerrit-Reviewer: Tom Fifield t...@openstack.org

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


Re: [OpenStack-Infra] Request a a dedicated user account.

2013-11-28 Thread Tom Fifield

Hi all,

On 19/11/13 01:02, Russell Bryant wrote:

On 11/18/2013 03:41 AM, shaomei ji wrote:

Hi, We are setting up our CI infrastructure environment, and we need a
account to communicate with community, could you arrange a user accoun,
We especially need this account and your help, thanks very much.
  The detail info is as following:
  1) The public_key.txt
  2) Username for new account: cstlcd
   3) Display name: ibm_cd_team
4) Email:  jish...@cn.ibm.com mailto:jish...@cn.ibm.com


I know that IBM is big and has multiple teams working on OpenStack.  Is
this the only account to be used across all of IBM, or should be the
name be more specific to what your team is testing?


Just to update you, a few of us spoke with Shao Mei, and her colleagues 
at IBM today - here's the status:

* They're currently working on some things internally
* They will get a functional alias email
* The purpose is for testing some specific things, like DB2/QPID 
functionality

* The CI system build is going well

and this request will be updated in due course :)

Regards,


Tom




___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


Re: [OpenStack-Infra] Need help on Transifex setting

2013-08-28 Thread Tom Fifield

On 21/08/13 16:33, Ying Chun Guo wrote:

Hi,

Translation team wants to set shared glossary among all OpenStack
projects in Transifex.
Recently, Transifex introduced Organization. The same glossary or TM
can be used across
multiple projects belonging to the same organization. It��s possible to
designate specific
users as Organization Administrators. Each admin will be able to manage
glossary sharing
details[1]. The glossary can be bootstrapped by uploading a CSV file.

The glossary can be only shared among projects with the same source
language. Now under
OpenStack, the source language of some projects (Cinder, Glance,
Horizon, and Nova) are en_US,
and the source language of the others are en. The source language
en_US may cause issues. We
knew 1 bug[2] in Horizon.

So I need help to
* An admin to create a shared glossary among all projects under
OpenStack. The initial CSV file
can be gotten from translation team.


Since we still have  the en vs en_US problem, I have merged the 
glossaries into two:



openstack_2012-08-02 (English)

Ceilometer Heat Keystone Neutron OpenStack OpenStack Manuals savanna

horizon_2012-08-17 (English (United States))

Cinder Glance Horizon Nova



* Change the source language of projects from en_US to en. It cannot
be changed directly. The
new source file with source language as en has to be uploaded to
replace the old one by manual.


My understanding on what we need to do here is:

eg for Nova

0. Backup translations from nova project
1. Create a new project nova-new
2. Upload new translation source to nova-new, using language=en
3. Upload the translation backup to nova-new
4. test that translations have restored from backup OK
5. Rename nova to nova-old
6. Rename nova-new to nova
7. Test that everything in the toolchain works
8. delete nova-old

Repeat for: Cinder Glance Horizon

Does that make sense?


One other note from clarkb: where we do an extract_catalog in the 
jenkins scripts we may need to enforce the source locale [so it's always 
set consistently]




Regards,

Tom





Please let me know if anybody can help.

Thanks and regards
Ying Chun Guo (Daisy)

[1]: http://blog.transifex.com/post/57712611874/organizations
[2]: https://bugs.launchpad.net/horizon/+bug/1179526



___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra




___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra