[OpenStack-Infra] docs.airshipit.org setup

[SCHIEFELBEIN, ANDREW]

Hail and well met OpenDev admins,
We would like to get the docs.airshipit.org vhost setup so that we can start to 
propagate docs out to this vanity url.  Is this something that someone can 
assist with?

Thanks
Andy Schiefelbein

On Nov 20, 2019, at 12:40 PM, Ashlee Ferguson 
mailto:ash...@openstack.org>> wrote:

Hi all,

On Monday's WC call, the topic of getting 
docs.airshipit.org
 setup came up, so I wanted to follow up with some next steps. Below is the 
info I collected from the OSF team. It'll be pretty quick to set up, but will 
require a volunteer's involvement from your team's side to coordinate it.

Someone will need to collaborate with the OpenDev sysadmins to get an Airship 
project volume created in our afs cell, then propose a change to add a 
docs.airshipit.org
 web virtual host to the files server and adjust the Zuul jobs to start pushing 
content there. Then someone from OSF will create a cname alias in dns for 
docs.airshipit.org
 to point at the files server hosting that site.

The best way to reach out to the sysadmins is either through #openstack-infra 
on freenode or by sending e-mail to the 
openstack-infra@lists.openstack.org 
mailing list.

Let me know if you have any questions!

Ashlee

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

Re: [OpenStack-Infra] docs.airshipit.org setup

[Jeremy Stanley]

[I'm leaving the Cc list intact because I'm not sure which of you
are subscribed to this mailing list; my apologies for any duplicate
copies you may receive.]

On 2020-02-05 15:10:27 + (+), SCHIEFELBEIN, ANDREW wrote:
[...]
> We would like to get the docs.airshipit.org vhost setup so that we
> can start to propagate docs out to this vanity url.  Is this
> something that someone can assist with?
[...]

We're in a bit of a transitional phase at the moment to a new and
much improved publication workflow, so I took the liberty of trying
to do this myself in order to make sure I understand it thoroughly
rather than possibly giving you bad/incomplete advice. The rough
steps are as follows (reviewers will hopefully tell me where I've
gotten it wrong):

0. Create a new volume in AFS to hold your content (done).

1. Add a job to our trusted Zuul config to push your content into
this new AFS volume; it has to be in the trusted config repo because
it gets access to a shared Kerberos principal. This is change
https://review.opendev.org/706598 .

2. Run the new publication job along with corresponding build jobs
in relevant pipelines from your airship/treasuremap repository's
Zuul configuration. The different docs build job is necessary as it
creates a content tarball artifact which is then passed directly to
the publication job in the promote pipeline rather than rerunning
the same build again after merge. This is change
https://review.opendev.org/706598 .

3. Add CNAME RRs in the airshipit.org DNS zone for the server which
will eventually serve your content and also for our automation
around Let's Encrypt domain validation (done).

4. Set up SSL cert management for the new site. This is change
https://review.opendev.org/706600 (it can merge in parallel with
steps 1-3 as it's independent of them).

5. Add an Apache vhost configuration on the server which will act as
a front-end for your content. This is change
https://review.opendev.org/706601 .

6. Enjoy an efficient, automated publication workflow to your own
custom documentation site.
-- 
Jeremy Stanley


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