From cboylan at sapwetik.org  Mon Feb  3 21:22:40 2020
From: cboylan at sapwetik.org (Clark Boylan)
Date: Mon, 03 Feb 2020 13:22:40 -0800
Subject: [OpenStack-Infra] Meeting Agenda for February 4, 2020
Message-ID: <59010708-1430-42f7-b607-b8d88e611369@www.fastmail.com>

We will meet at 19:00UTC on February 4, 2020 in #openstack-meeting with this agenda:

== Agenda for next meeting ==

* Announcements

* Actions from last meeting
** Clarkb out Wednesday February 5, 2020.

* Specs approval

* Priority Efforts (Standing meeting agenda items. Please expand if you have subtopics.)
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/update-config-management.html Update Config Management]
*** topic:update-cfg-mgmt
*** Zuul as CD engine
** OpenDev
*** Progress on Governance changes
**** https://review.opendev.org/#/c/703134/ Split OpenDev out of OpenStack governance.
**** https://review.opendev.org/#/c/703488 Updates to our project documentation with governance info
*** Possible gitea/go-git bug in current version of gitea we are running https://storyboard.openstack.org/#!/story/2006849
*** Gitea has added a commit cache and closed the slow performance bug. We should consider an upgrade as soon as is reasonable.

* General topics
** Trusty Upgrade Progress (clarkb 20200204)
*** Status.o.o mostly done. Needs new gerritlib release for e-r IRC bot to get Gerrit events.
*** Wiki updates
*** Refstack getting docker'd due to stale puppet needing a rewrite anyway. Need changes in refstack to land and make docker image buildable.
** static.openstack.org (ianw,corvus,mnaser,fungi 20200204)
*** Publishing updates
** New Arm64 cloud (ianw 20200204)
*** nb03 unable to talk to https://us.linaro.cloud:5000 (still)
** New Airship CI cloud (clarkb 20200204)

* Open discussion


From as3525 at att.com  Wed Feb  5 15:10:27 2020
From: as3525 at att.com (SCHIEFELBEIN, ANDREW)
Date: Wed, 5 Feb 2020 15:10:27 +0000
Subject: [OpenStack-Infra] docs.airshipit.org setup
Message-ID: <CBF7BB196BA55C44BEAFBA486F876C62556FA359@MOSTLS1MSGUSREG.ITServices.sbc.com>

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 <ashlee at openstack.org<mailto:ashlee at openstack.org>> wrote:

Hi all,

On Monday's WC call, the topic of getting docs.airshipit.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__docs.airshipit.org_&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=N91viwPDWZdWAxEBELozNY8am4TZ9iG1JB9M4NC9koI&s=A56bG6h749nd0yo0LfFSiH-n-ILVNnRipig7q-bmfQU&e=> 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<https://urldefense.proofpoint.com/v2/url?u=http-3A__docs.airshipit.org_&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=N91viwPDWZdWAxEBELozNY8am4TZ9iG1JB9M4NC9koI&s=A56bG6h749nd0yo0LfFSiH-n-ILVNnRipig7q-bmfQU&e=> 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<https://urldefense.proofpoint.com/v2/url?u=http-3A__docs.airshipit.org_&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=N91viwPDWZdWAxEBELozNY8am4TZ9iG1JB9M4NC9koI&s=A56bG6h749nd0yo0LfFSiH-n-ILVNnRipig7q-bmfQU&e=> 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 at lists.openstack.org<mailto:openstack-infra at lists.openstack.org> mailing list.

Let me know if you have any questions!

Ashlee

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-infra/attachments/20200205/be7a9eb1/attachment.html>

From fungi at yuggoth.org  Fri Feb  7 18:47:57 2020
From: fungi at yuggoth.org (Jeremy Stanley)
Date: Fri, 7 Feb 2020 18:47:57 +0000
Subject: [OpenStack-Infra] docs.airshipit.org setup
In-Reply-To: <CBF7BB196BA55C44BEAFBA486F876C62556FA359@MOSTLS1MSGUSREG.ITServices.sbc.com>
References: <CBF7BB196BA55C44BEAFBA486F876C62556FA359@MOSTLS1MSGUSREG.ITServices.sbc.com>
Message-ID: <20200207184756.7zsimj2eqqqw7gz6@yuggoth.org>

[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 +0000 (+0000), 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-infra/attachments/20200207/a2f65902/attachment.sig>

From MM9745 at att.com  Fri Feb  7 18:56:01 2020
From: MM9745 at att.com (MCEUEN, MATT)
Date: Fri, 7 Feb 2020 18:56:01 +0000
Subject: [OpenStack-Infra] docs.airshipit.org setup
In-Reply-To: <20200207184756.7zsimj2eqqqw7gz6@yuggoth.org>
References: <CBF7BB196BA55C44BEAFBA486F876C62556FA359@MOSTLS1MSGUSREG.ITServices.sbc.com>
 <20200207184756.7zsimj2eqqqw7gz6@yuggoth.org>
Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970ADD484@MOSTLS1MSGUSRFF.ITServices.sbc.com>

Thanks very much for doing all the heavy lifting, Jeremy!  Happy to be a guinea pig for the new process - we'll keep an eye on the changes below, and please let us know if there's anything else we can do to help.

Thanks,
Matt 

-----Original Message-----
From: Jeremy Stanley <fungi at yuggoth.org> 
Sent: Friday, February 7, 2020 12:48 PM
To: openstack-infra at lists.openstack.org
Cc: SCHIEFELBEIN, ANDREW <as3525 at att.com>; MCEUEN, MATT <MM9745 at att.com>; BAILEY, ALEXANDER <ab805p at att.com>; DURWAY, LINDSEY <ld178u at att.com>
Subject: Re: [OpenStack-Infra] docs.airshipit.org setup

[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 +0000 (+0000), 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


From cboylan at sapwetik.org  Mon Feb 10 22:31:01 2020
From: cboylan at sapwetik.org (Clark Boylan)
Date: Mon, 10 Feb 2020 14:31:01 -0800
Subject: [OpenStack-Infra] Meeting Agenda for February 11, 2020
Message-ID: <01c1723e-c609-4bff-8b56-738686fdc828@www.fastmail.com>

We will meet on February 11, 2020 at 19:00 UTC in #openstack-meeting with this agenda.

== Agenda for next meeting ==

* Announcements

* Actions from last meeting

* Specs approval

* Priority Efforts (Standing meeting agenda items. Please expand if you have subtopics.)
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/update-config-management.html Update Config Management]
*** topic:update-cfg-mgmt
*** Zuul as CD engine
** OpenDev
*** Progress on Governance changes
**** https://review.opendev.org/#/c/703134/ Split OpenDev out of OpenStack governance.
**** https://review.opendev.org/#/c/703488 Updates to our project documentation with governance info
*** Possible gitea/go-git bug in current version of gitea we are running https://storyboard.openstack.org/#!/story/2006849
*** Gitea has added a commit cache and closed the slow performance bug. We should consider an upgrade as soon as is reasonable.

* General topics
** Vancouver PTG attendance. (clarkb 20200211)
*** That time of year where we need to decide if we are going and if so how much time and space we need.
** Trusty Upgrade Progress (clarkb 20200211)
*** Status.o.o mostly done. Needs new gerritlib release for e-r IRC bot to get Gerrit events.
*** Wiki updates
*** Refstack needs changes to upstream code base to make it deployable on our docker python-base image.
** static.openstack.org (ianw,corvus,mnaser,fungi 20200211)
*** Publishing updates
** New Arm64 cloud (ianw 20200211)
*** nb03 unable to talk to https://us.linaro.cloud:5000 (still)
** New Airship CI cloud (clarkb 20200211)

* Open discussion


From fungi at yuggoth.org  Thu Feb 13 21:20:02 2020
From: fungi at yuggoth.org (Jeremy Stanley)
Date: Thu, 13 Feb 2020 21:20:02 +0000
Subject: [OpenStack-Infra] Your review.opendev.org account is temporarily
	disabled
Message-ID: <20200213212002.bvwurdkadaujt24p@yuggoth.org>

You seem to have a misconfigured Zuul service using your Gerrit
account, leaving errors like the following on many projects for the
past ~12 hours:

    Unable to freeze job graph: Decryption failed.
    https://review.opendev.org/707499

I have temporarily deactivated your account (ID 30112) and closed
all established Gerrit API connections for it. Please reply when you
have corrected the problem and we can reenable your account at that
time. Thanks for your attention in this matter.
-- 
Jeremy Stanley
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-infra/attachments/20200213/376f6c2b/attachment.sig>

From cboylan at sapwetik.org  Mon Feb 17 21:29:14 2020
From: cboylan at sapwetik.org (Clark Boylan)
Date: Mon, 17 Feb 2020 13:29:14 -0800
Subject: [OpenStack-Infra] Meeting Agenda for February 18, 2020
Message-ID: <d9bf445c-dbae-43dc-b160-e8e214eaeac0@www.fastmail.com>

We will meet at 19:00 UTC February 18, 2020 in #openstack-meeting with this agenda:

== Agenda for next meeting ==

* Announcements

* Actions from last meeting

* Specs approval

* Priority Efforts (Standing meeting agenda items. Please expand if you have subtopics.)
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/update-config-management.html Update Config Management]
*** topic:update-cfg-mgmt
*** Zuul as CD engine
** OpenDev
*** Progress on Governance changes
**** https://review.opendev.org/#/c/703134/ Split OpenDev out of OpenStack governance.
**** https://review.opendev.org/#/c/703488 Updates to our project documentation with governance info
*** Upgrade gitea to 1.10.3 https://review.opendev.org/#/c/705804/

* General topics
** Vancouver PTG attendance. (clarkb 20200218)
*** That time of year where we need to decide if we are going and if so how much time and space we need.
** Trusty Upgrade Progress (clarkb 20200218)
*** Wiki updates
** static.openstack.org (ianw,corvus,mnaser,fungi 20200218)
*** static.openstack.org transition should be complete
*** still tasks remaining (haproxy redirects, few other publishing sites)
** New Airship CI cloud (clarkb 20200218)
** pip-and-virtualenv removal (ianw 20200218)
*** https://etherpad.openstack.org/p/pTFF4U9Klz : clarkb writeup of major issues
*** possible removal plan: use py3 venv (built in) on all platforms for build-time "utility" installs (glean, bindep, stackviz, whatever); ship images without any non-distro-packaged tools; add for backwards compatibility via base jobs
*** https://review.opendev.org/707499 : discussion in comments
*** https://review.opendev.org/707513 : use venv for glean
*** https://review.opendev.org/707750 : use venv in project-config elements; drop pip-and-virtualenv inclusion from element and move to individual configs; add node type with no pip-and-virtualenv.  this can be used for job testing.

* Open discussion
** Need to clarify logging requirements from https://docs.openstack.org/infra/system-config/third_party.html -- mainly the "logs must be browsable; logs requiring download, installation or login to access are not acceptable" phrase. (ssbarnea 20200217)
*** Does it apply to any logs or only tempest ones? Current indentation seems wrong, was this expected to be top level?
*** Is ever accepted to produce combined .tar.gz files with host-logs?
*** In which conditions it would be acceptable to archive a big log file? Example publishing a 1GB single log file is clearly not of any use for browsing it. I suspect after certain size is ok to archive them but this is not mentioned. What would be the magic threshold?


From cboylan at sapwetik.org  Mon Feb 24 22:19:17 2020
From: cboylan at sapwetik.org (Clark Boylan)
Date: Mon, 24 Feb 2020 14:19:17 -0800
Subject: [OpenStack-Infra] Meeting Agenda for February 25, 2020
Message-ID: <eed76106-adf3-4791-80ef-3e04bb41db40@www.fastmail.com>

We will meet at 19:00 UTC Tuesday, February 25 in #openstack-meeting with this agenda. See you there.

== Agenda for next meeting ==

* Announcements

* Actions from last meeting

* Specs approval
** https://review.opendev.org/#/c/709579/ Cleaning up python dev tools on our CI images.
*** https://etherpad.openstack.org/p/pTFF4U9Klz : clarkb writeup of major issues
*** https://review.opendev.org/707499 : discussion in comments
*** https://review.opendev.org/707513 : use venv for glean
*** https://review.opendev.org/707750 : use venv in project-config elements; drop pip-and-virtualenv inclusion from element and move to individual configs; add node type with no pip-and-virtualenv.  this can be used for job testing.
** https://review.opendev.org/#/c/709236/ Website activity stats

* Priority Efforts (Standing meeting agenda items. Please expand if you have subtopics.)
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/update-config-management.html Update Config Management]
*** topic:update-cfg-mgmt
*** Zuul as CD engine
** OpenDev
*** Progress on Governance changes
**** https://review.opendev.org/#/c/703134/ Split OpenDev out of OpenStack governance.
**** https://review.opendev.org/#/c/703488 Updates to our project documentation with governance info

* General topics
** Xwiki for opendev (ttx 20200224)
** Vancouver PTG attendance. (clarkb 20200225)
*** Request space for a small group in Vancouver. Mentioned that we can be flexible, but having some official time is useful so that people can find us with questions. Then with a small group it is easy enough to meet in an ad hoc fashion (this worked well in Shanghai).
** Trusty Upgrade Progress (clarkb 20200225)
*** Wiki updates
** static.openstack.org (ianw,corvus,mnaser,fungi 20200225)
*** static.openstack.org transition should be complete
*** still tasks remaining (haproxy redirects, few other publishing sites)

* Open discussion