<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 28, 2016 at 12:09 PM, Andreas Jaeger <span dir="ltr"><<a href="mailto:aj@suse.com" target="_blank">aj@suse.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">[cross-posting to both infra and docs mailing lists]<br>
<br>
We're running since several weeks <a href="http://developer.openstack.org" rel="noreferrer" target="_blank">developer.openstack.org</a> using the<br>
OpenStack Infra server and I reviewed what is needed to make the final<br>
switch. An analysis of missing pages showed that only 4 repos have not<br>
been published (step 1 below), we need to copy those over.<br>
<br>
Once that is done, we can do the switch<br>
<br>
<br>
The following steps need to be done:<br>
<br>
1) update some missing content since a few projects haven't published<br>
content since we started:<br>
<a href="http://users.suse.com/~aj/missing-docs.tar.bz2" rel="noreferrer" target="_blank">http://users.suse.com/~aj/<wbr>missing-docs.tar.bz2</a> is a copy from<br>
docs.o.o that needs to be added to our AFS tree.<br></blockquote><div><br></div><div>I looked at the files and seems fine. The project names are: pylockfile, python-aodhclient, python-barbicanclient, python-cinderclient, and python-manilaclient.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
2) Change IP address of <a href="http://docs.openstack.org" rel="noreferrer" target="_blank">docs.openstack.org</a> to point to the new site.<br>
<br>
3) Create <a href="http://docs-archived.openstack.org" rel="noreferrer" target="_blank">docs-archived.openstack.org</a> pointing to the old CloudDocs<br>
docs site so that we can still access any content that wasn't<br>
published recently. Update 404 handler to point to docs-archived.<br>
<br></blockquote><div><br></div><div>This is one step where I'm not sure how it works - but if you know what to do it's all good.</div><div> </div><div>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.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Later (most can be done independently, so not using numbers), we should do:<br>
<br>
A) Set up https for <a href="http://docs.openstack.org" rel="noreferrer" target="_blank">docs.openstack.org</a> and <a href="http://developer.openstack.org" rel="noreferrer" target="_blank">developer.openstack.org</a></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
B) Stop publishing to CloudDocs site docs-archived but keep site as<br>
is.<br>
Archive all content on it.<br>
<br></blockquote><div><br></div><div>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. :)</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Remove <a href="http://docs-archived.openstack.org" rel="noreferrer" target="_blank">docs-archived.openstack.org</a><br>
<br>
C) Stop publishing to old CloudDocs <a href="http://developer.openstack.org" rel="noreferrer" target="_blank">developer.openstack.org</a> page (<br>
<a href="https://review.openstack.org/415506" rel="noreferrer" target="_blank">https://review.openstack.org/<wbr>415506</a> )<br>
<br>
D) Remove docs-beta and developer-beta aliases and IP addresses, those<br>
are not needed anymore.<br>
<br>
Is anything missing?</blockquote><div><br></div><div>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.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Otherwise, let's move forward once an infra admin has time. Since we<br>
continue publishing to both sites for a time, we can always migrate back<br>
if needed. Infra team, please go ahead if there's no veto - but let's<br>
not do it this year anymore;)<br></blockquote><div><br></div><div>Good thinking and planning! Thanks a bunch.</div><div>Anne</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="HOEnZb"><font color="#888888"><br>
Andreas<br>
--<br>
Andreas Jaeger aj@{<a href="http://suse.com" rel="noreferrer" target="_blank">suse.com</a>,<a href="http://opensuse.org" rel="noreferrer" target="_blank">opensuse.org</a>} Twitter: jaegerandi<br>
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany<br>
GF: Felix Imendörffer, Jane Smithard, Graham Norton,<br>
HRB 21284 (AG Nürnberg)<br>
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126<br>
<br>
<br>
______________________________<wbr>_________________<br>
OpenStack-docs mailing list<br>
<a href="mailto:OpenStack-docs@lists.openstack.org">OpenStack-docs@lists.<wbr>openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-docs</a><br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><br></div><div>Read my blog: <a href="https://justwriteclick.com" target="_blank">justwrite.click</a></div><div>Subscribe to Docs|Code: <a href="http://docslikecode.com" target="_blank">docslikecode.com</a> </div></div></div></div></div></div></div>
</div></div>