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

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

2016-12-29 Thread Andreas Jaeger 
On 12/29/2016 02:29 PM, Anne Gentle wrote:
> 
> 
> On Wed, Dec 28, 2016 at 12:09 PM, Andreas Jaeger  > wrote:
> 
> [cross-posting to both infra and docs mailing lists]
> 
> We're running since several weeks developer.openstack.org
>  using the
> OpenStack Infra server and I reviewed what is needed to make the final
> switch. An analysis of missing pages showed that only 4 repos have not
> been published (step 1 below), we need to copy those over.
> 
> Once that is done, we can do the switch
> 
> 
> The following steps need to be done:
> 
> 1) update some missing content since a few projects haven't published
>content since we started:
>http://users.suse.com/~aj/missing-docs.tar.bz2
>  is a copy from
>docs.o.o that needs to be added to our AFS tree.
> 
> 
> I looked at the files and seems fine. The project names are: pylockfile,
> python-aodhclient, python-barbicanclient, python-cinderclient, and
> python-manilaclient.
>  
> 
> 
> 2) Change IP address of docs.openstack.org
>  to point to the new site.
> 
> 3) Create docs-archived.openstack.org
>  pointing to the old CloudDocs
>docs site so that we can still access any content that wasn't
>published recently. Update 404 handler to point to docs-archived.
> 
> 
> This is one step where I'm not sure how it works - but if you know what
> to do it's all good.

Step 3 needs probably login to the CloudSites admin interface - no idea
how that works.

> Do we need to do any notification step to Cloud Sites through a ticket
> to let them know the traffic will change? Might be good to let them know
> proactively.

No idea ;(

they were more concerned with the size of our site (number of files) in
the past.

> 
> Later (most can be done independently, so not using numbers), we
> should do:
> 
> A) Set up https for docs.openstack.org 
> and developer.openstack.org 
> 
> 
> 
> B) Stop publishing to CloudDocs site docs-archived but keep site as
>is.
>Archive all content on it.
> 
> 
> Let me know if you need help with this step - not sure how this is done
> but you can tell me and I'll do the work. :)

This should be similar to 415506 below.


>  
> 
>Remove docs-archived.openstack.org
> 
> 
> C) Stop publishing to old CloudDocs developer.openstack.org
>  page (
>https://review.openstack.org/415506
>  )
> 
> D) Remove docs-beta and developer-beta aliases and IP addresses, those
>are not needed anymore.
> 
> Is anything missing?
> 
> 
> When the change happens we should probably check the analytics the next
> day to ensure collection is still happening smoothly. Might not be a
> step exactly but it's B.1 and C.1 I suppose.

Yeah, we should keep our eyes open.

> 
> 
> Otherwise, let's move forward once an infra admin has time. Since we
> continue publishing to both sites for a time, we can always migrate back
> if needed.  Infra team, please go ahead if there's no veto - but let's
> not do it this year anymore;)
> 
> 
> Good thinking and planning! Thanks a bunch.
> Anne

thanks,
Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Felix Imendörffer, Jane Smithard, Graham Norton,
   HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


___
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

2016-12-29 Thread Alexandra Settle 
Looks good, Andreas.

Let me know if I can do anything from the docs side to make the transition 
smoother. 

Thanks!

Alex

On 12/28/16, 6:09 PM, "Andreas Jaeger"  wrote:

[cross-posting to both infra and docs mailing lists]

We're running since several weeks developer.openstack.org using the
OpenStack Infra server and I reviewed what is needed to make the final
switch. An analysis of missing pages showed that only 4 repos have not
been published (step 1 below), we need to copy those over.

Once that is done, we can do the switch


The following steps need to be done:

1) update some missing content since a few projects haven't published
   content since we started:
   http://users.suse.com/~aj/missing-docs.tar.bz2 is a copy from
   docs.o.o that needs to be added to our AFS tree.

2) Change IP address of docs.openstack.org to point to the new site.

3) Create docs-archived.openstack.org pointing to the old CloudDocs
   docs site so that we can still access any content that wasn't
   published recently. Update 404 handler to point to docs-archived.


Later (most can be done independently, so not using numbers), we should do:

A) Set up https for docs.openstack.org and developer.openstack.org

B) Stop publishing to CloudDocs site docs-archived but keep site as
   is.
   Archive all content on it.

   Remove docs-archived.openstack.org

C) Stop publishing to old CloudDocs developer.openstack.org page (
   https://review.openstack.org/415506 )

D) Remove docs-beta and developer-beta aliases and IP addresses, those
   are not needed anymore.

Is anything missing?

Otherwise, let's move forward once an infra admin has time. Since we
continue publishing to both sites for a time, we can always migrate back
if needed.  Infra team, please go ahead if there's no veto - but let's
not do it this year anymore;)

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Felix Imendörffer, Jane Smithard, Graham Norton,
   HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


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


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