Hello,
as follow-up on the CentOS dojo in Geneva, I'm hereby requesting a bot account for the Opstools SIG.
There are listed two requirements[1]:
- the account name is the shortname for the SIG: I'm proposing opstools - The email on the account must be deliverable to someone who can change the certificate on the production environment.
The opstools SIG uses RDO gerrit for kicking off builds. So, either we'd need here the email address of someone with such access to RDO gerrit. I currently have no such login. Whatever works here, I'd be fine with it.
I did not create an account in ACO yet, since the email question is currently undecided.
[1] https://wiki.centos.org/SIGGuide#head-c256691b201cc88e4ffa53f3dee8c78b8cdca4...
On Wed, Feb 14, 2018 at 02:45:11PM +0100, Matthias Runge wrote:
Hello,
as follow-up on the CentOS dojo in Geneva, I'm hereby requesting a bot account for the Opstools SIG.
Iterating on this, I just created an account named opstools; I'll make sure, generated certificates will be stored on the corresponding setup.
What is the next step to get long living certificates for that account?
Matthias
On 23/02/18 12:42, Matthias Runge wrote:
On Wed, Feb 14, 2018 at 02:45:11PM +0100, Matthias Runge wrote:
Hello,
as follow-up on the CentOS dojo in Geneva, I'm hereby requesting a bot account for the Opstools SIG.
Iterating on this, I just created an account named opstools; I'll make sure, generated certificates will be stored on the corresponding setup.
What is the next step to get long living certificates for that account?
Matthias
Hi Matthias,
IIRC it was discussed during a cbs meeting and the goal was to *not* deviate from the actual process, even for bot accounts, so generated certs will still be valid for 6 months. It's also the reason why it has to be (re)generated with the centos-cert tool, and also that the email address for the bot account is a real one that someone is tracking, as we also send reminders when certificate is approaching expiry date
Cheers,