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

[Andreas Jaeger]

My spider I found a few directories that were completely missing and
we'll migrate those over later today manually. Once that's done I rerun
the spider and send the result here so that people can fix documents or
file bugs.

I also fixed a few broken links myself.


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

[Tom Fifield]

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



On Tue, Jan 10, 2017 at 10:25 PM, Tom Fifield > wrote:

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



On Tue, Jan 10, 2017 at 10:13 PM, Tom Fifield 
>> 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



>


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



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

>

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


>




--

Read my blog: justwrite.click 
Subscribe to Docs|Code: docslikecode.com
 





--

Read my blog: justwrite.click 
Subscribe to Docs|Code: 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

[Anne Gentle]

On Tue, Jan 10, 2017 at 10:25 PM, Tom Fifield  wrote:

> On 11/01/17 12:21, Anne Gentle wrote:
>
>>
>>
>> On Tue, Jan 10, 2017 at 10:13 PM, Tom Fifield > > 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
>> > 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


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

Anne

>
>> ___
>> OpenStack-docs mailing list
>> openstack-d...@lists.openstack.org
>> 
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>> 
>>
>>
>>
>>
>> --
>>
>> Read my blog: justwrite.click 
>> Subscribe to Docs|Code: docslikecode.com 
>>
>
>


-- 

Read my blog: justwrite.click 
Subscribe to Docs|Code: 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

[Anne Gentle]

On Tue, Jan 10, 2017 at 10:21 PM, Anne Gentle  wrote:

>
>
> On Tue, Jan 10, 2017 at 10:13 PM, Tom Fifield  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/' %}
>
>
Here's a patch based on that ^^ working theory:
https://review.openstack.org/418672

See if you think that'll fix it... not sure how to test locally.

Thanks - Anne


>
>
>> eg http://docs.openstack.org/kilo/networking-guide/scenario_leg
>> acy_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.
>
> Anne
>
>
>>
>>
>> ___
>> OpenStack-docs mailing list
>> openstack-d...@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>
>
>
>
> --
>
> Read my blog: justwrite.click 
> Subscribe to Docs|Code: docslikecode.com
>



-- 

Read my blog: justwrite.click 
Subscribe to Docs|Code: 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

[Tom Fifield]

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



On Tue, Jan 10, 2017 at 10:13 PM, Tom Fifield > 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



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

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





--

Read my blog: justwrite.click 
Subscribe to Docs|Code: 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

[Anne Gentle]

On Tue, Jan 10, 2017 at 10:13 PM, Tom Fifield  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
>
>
> 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.

Anne


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



-- 

Read my blog: justwrite.click 
Subscribe to Docs|Code: 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

[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] [OpenStack-docs] [infra][docs] Steps to migrate docs.o.o to new AFS based server

[Anne Gentle]

On Tue, Jan 10, 2017 at 2:07 PM, Andreas Jaeger  wrote:

> On 2017-01-03 20:43, Andreas Jaeger wrote:
> > we discussed in today's infra meeting to move forward as follows:
> >
> > 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) Merge https://review.openstack.org/400887 to release afs volumes
> >and create read-only volumes (jeblair)
> >
> > 3) Change IP address of docs.openstack.org to point to the new site.
> >
> > 4) Update 404 handler to not point to archived site anymore
> >
> > 5) Update archived content so that we can still access any
> >content that wasn't published recently:
> >a) Resync the mirror at http://files.openstack.org/docs-old/
> >
> > 6) Check that all links on docs.o.o work correctly
> >
> > infra-root volunteers for some steps are still needed, this will be
> > discussed on #openstack-infra later this week,
>
> Paul just changed DNS, so docs.openstack.org is pointing to the new site.
>
> In case of any problems, please report them as reply to this email or
> directly on #openstack-infra.
>

Looks great - and fast. Nice. Great work everyone and thank you so much.

Should I spider-walk it to test the links, or did you already?

Anne


>
> 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
>



-- 

Read my blog: justwrite.click 
Subscribe to Docs|Code: 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

[Andreas Jaeger]

On 2017-01-03 20:43, Andreas Jaeger wrote:
> we discussed in today's infra meeting to move forward as follows:
> 
> 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) Merge https://review.openstack.org/400887 to release afs volumes
>and create read-only volumes (jeblair)
> 
> 3) Change IP address of docs.openstack.org to point to the new site.
> 
> 4) Update 404 handler to not point to archived site anymore
> 
> 5) Update archived content so that we can still access any
>content that wasn't published recently:
>a) Resync the mirror at http://files.openstack.org/docs-old/
> 
> 6) Check that all links on docs.o.o work correctly
> 
> infra-root volunteers for some steps are still needed, this will be
> discussed on #openstack-infra later this week,

Paul just changed DNS, so docs.openstack.org is pointing to the new site.

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

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

[James E. Blair]

Andreas Jaeger  writes:

> we discussed in today's infra meeting to move forward as follows:
>
> 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) Merge https://review.openstack.org/400887 to release afs volumes
>and create read-only volumes (jeblair)

Item #2 is done.  files.openstack.org (including
developer.openstack.org) is now serving from the read-only replicas.
These are updated every 5 minutes if needed (so there may be a delay of
5, or in the worst case, 10 minutes after a publishing job finishes
before all the content shows up).  But the replicas are in two data
centers so our fault tolerance is increased (though we should add a
files02.openstack.org, also in a different data center, into rotation to
really make that robust -- that's easy to do at any time).

> 3) Change IP address of docs.openstack.org to point to the new site.
>
> 4) Update 404 handler to not point to archived site anymore
>
> 5) Update archived content so that we can still access any
>content that wasn't published recently:
>a) Resync the mirror at http://files.openstack.org/docs-old/
>
> 6) Check that all links on docs.o.o work correctly
>
> infra-root volunteers for some steps are still needed, this will be
> discussed on #openstack-infra later this week,
>
> Andreas

___
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

[Andreas Jaeger]

we discussed in today's infra meeting to move forward as follows:

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) Merge https://review.openstack.org/400887 to release afs volumes
   and create read-only volumes (jeblair)

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

4) Update 404 handler to not point to archived site anymore

5) Update archived content so that we can still access any
   content that wasn't published recently:
   a) Resync the mirror at http://files.openstack.org/docs-old/

6) Check that all links on docs.o.o work correctly

infra-root volunteers for some steps are still needed, this will be
discussed on #openstack-infra later this week,

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

[Andreas Jaeger]

On 01/03/2017 03:57 PM, Andreas Jaeger wrote:
> On 01/03/2017 03:43 PM, Jeremy Stanley wrote:
>> On 2017-01-03 08:01:42 +0100 (+0100), Andreas Jaeger wrote:
>> [...]
>>> 3) Create docs-archived content so that we can still access any
>>>content that wasn't published recently:
>>>a) Resync the mirror at http://files.openstack.org/docs-old/
>>>b) Serve the content via docs-archived.openstack.org (see
>>>   https://review.openstack.org/416148 )
>>>c) Add external IP address
>>>c) Update 404 handler to point to docs-archived.
>> [...]
>>
>> I'm a little unclear on what step "c" is supposed to be there... all
>> our servers already have "external" (globally routable) IP
>> addresses.
> 
> Add docs-archived.openstack.org DNS entry.
> 
>> As for step "d" that could presumably get confusing if someone
>> requests a page that doesn't exist at either site, since they'll get
>> an error about a missing page at docs-archive.o.o instead of
>> docs.o.o (maybe that's fine, I don't have much insight into reader
>> expectations). Is the longer-term plan to review analytics for page
>> hits against docs-archive to figure out what else should be copied
>> over to docs.o.o manually, or incorporated/reintroduced into
>> documentation builds?
> 
> Have a look what happens currently:
> http://docs-beta.openstack.org/bla
> 
> Yes, it could be confusing. The idea was to wait for bug reports - and I
> don't really expect any since all links should work (I run a spider on
> docs-beta).
> 
> We will not add anything again in documentation builds, this is really
> historic data,

We just discussed this in the infra meeting and since we can rebuild old
documentation if really needed manually (which might be tricky since it
needs older tools and maybe older packages/distro), we do not need
docs-archived. We have all the content on files.openstack.org/docs-old
and can access it there - via anonymous AFS or http,

new plan coming in a minute,
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

[Andreas Jaeger]

On 01/03/2017 03:43 PM, Jeremy Stanley wrote:
> On 2017-01-03 08:01:42 +0100 (+0100), Andreas Jaeger wrote:
> [...]
>> 3) Create docs-archived content so that we can still access any
>>content that wasn't published recently:
>>a) Resync the mirror at http://files.openstack.org/docs-old/
>>b) Serve the content via docs-archived.openstack.org (see
>>   https://review.openstack.org/416148 )
>>c) Add external IP address
>>c) Update 404 handler to point to docs-archived.
> [...]
> 
> I'm a little unclear on what step "c" is supposed to be there... all
> our servers already have "external" (globally routable) IP
> addresses.

Add docs-archived.openstack.org DNS entry.

> As for step "d" that could presumably get confusing if someone
> requests a page that doesn't exist at either site, since they'll get
> an error about a missing page at docs-archive.o.o instead of
> docs.o.o (maybe that's fine, I don't have much insight into reader
> expectations). Is the longer-term plan to review analytics for page
> hits against docs-archive to figure out what else should be copied
> over to docs.o.o manually, or incorporated/reintroduced into
> documentation builds?

Have a look what happens currently:
http://docs-beta.openstack.org/bla

Yes, it could be confusing. The idea was to wait for bug reports - and I
don't really expect any since all links should work (I run a spider on
docs-beta).

We will not add anything again in documentation builds, this is really
historic data,

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

[Jeremy Stanley]

On 2017-01-03 08:01:42 +0100 (+0100), Andreas Jaeger wrote:
[...]
> 3) Create docs-archived content so that we can still access any
>content that wasn't published recently:
>a) Resync the mirror at http://files.openstack.org/docs-old/
>b) Serve the content via docs-archived.openstack.org (see
>   https://review.openstack.org/416148 )
>c) Add external IP address
>c) Update 404 handler to point to docs-archived.
[...]

I'm a little unclear on what step "c" is supposed to be there... all
our servers already have "external" (globally routable) IP
addresses.

As for step "d" that could presumably get confusing if someone
requests a page that doesn't exist at either site, since they'll get
an error about a missing page at docs-archive.o.o instead of
docs.o.o (maybe that's fine, I don't have much insight into reader
expectations). Is the longer-term plan to review analytics for page
hits against docs-archive to figure out what else should be copied
over to docs.o.o manually, or incorporated/reintroduced into
documentation builds?
-- 
Jeremy Stanley

___
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

[Andreas Jaeger]

On 01/02/2017 08:22 PM, Andreas Jaeger wrote:
> [...]
> I've put this topic on the agenda for tomorrow's infra team meeting,
> https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting . Docs team
> members are welcome to join!

In preparation for the meeting, I've updated the plan:

The following needs 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 content so that we can still access any
   content that wasn't published recently:
   a) Resync the mirror at http://files.openstack.org/docs-old/
   b) Serve the content via docs-archived.openstack.org (see
  https://review.openstack.org/416148 )
   c) Add external IP address
   c) Update 404 handler to point to docs-archived.

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

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. (https://review.openstack.org/416149,
   https://review.openstack.org/416152)

Note, see our etherpad here as well:
https://etherpad.openstack.org/p/afs-docs
and spec:
http://specs.openstack.org/openstack-infra/infra-specs/specs/doc-publishing.html

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

[Andreas Jaeger]

On 01/02/2017 07:07 PM, Jeremy Stanley wrote:
> On 2016-12-28 19:09:04 +0100 (+0100), Andreas Jaeger wrote:
> [...]
>> 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.
> [...]
> 
> I don't think this is technically possible with CloudSites, as each
> domain name seems (last time I tried when api.o.o got renamed to
> developer.o.o) to require creating a separate site with its own
> content. I tried to check now to see whether they have a rename
> option at least, but the old credentials I have on record for the
> CloudSites admin portal seem to no longer work and instead claim we
> aren't signed up for the service (maybe I'm trying the wrong account
> and some other Infra sysadmin has the correct credentials on hand?).
> 
> What we _can_ do is just not delete it immediately, and then you can
> temporarily override /etc/hosts locally to associate docs.o.o with
> 98.129.229.216 if you need to access it. Also keep in mind though
> that Rackspace is eager to see us delete the content for those sites
> because they're extremely large (at least by their standards), so
> the sooner we can remove them entirely the better.

Looking at previous plans, we have already mirrored once (need to
refresh) http://files.openstack.org/docs-old/, so we can replace that
step with:
a) Resync the mirror
b) Serve the content via docs-archived.openstack.org

I've put this topic on the agenda for tomorrow's infra team meeting,
https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting . Docs team
members are welcome to join!

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

[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

[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