beaker-project / beaker-infrastructure Goto Github PK

At this moment it is possible to read data from the new node via SSL, however, DNS resolution is a problem. To make it easier for everyone it would be better to create new virtual host for osci.io. So people can validate changes and status. For production, we will revoke certs + drop vhost.

So what we need is

• New VHOST osci.io
• New cert with SAN refers to beaker-project.org + beaker-project.osci.io

This codebase is quite outdated at this point.

We are quite far from the latest available Ansible, and it is likely that the toolchain will no longer work properly.
Rebase the playbooks and repository to the latest major release available and adjust the playbooks to work again.

Expired on June 11th,

Expires On	Thursday, June 11, 2020 at 10:24:23 AM

Hi @duck-rh,
I tried to sync some content to the upstream node, however, I'm not able to use my SSH key to connect.
Relevant debug

debug1: Offering public key: [email protected] ED25519 SHA256:XyRx2lEnjRRRQSfJ02mqGPte0yrgjCnpaw+HM5HPovI agent
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password

Hi @duck-rh,

Can you please store Ansible Vault key to GH repo secrets[0]?
This will help us to automate the sync of this repo (merged changes) and upstream server.

[0] https://github.com/beaker-project/beaker-infrastructure/settings/secrets/actions

We are close to migrating everything from one host to another, so we started to use .osci.io so we can see results directly on the new machine. However, we having problems with HTTPS now.

@duck-rh is it possible to create certs for ssl? let's encrypt for example?
Ping me if you have any questions.