Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFE] TODO list for turning this into a Flatcar App #3

Closed
11 of 12 tasks
t-lo opened this issue Jul 17, 2024 · 1 comment
Closed
11 of 12 tasks

[RFE] TODO list for turning this into a Flatcar App #3

t-lo opened this issue Jul 17, 2024 · 1 comment
Labels
kind/feature A feature request.

Comments

@t-lo
Copy link
Member

t-lo commented Jul 17, 2024

Current situation

Automation largely works but is based on Ubuntu, so the OS won't self-update after provisioning. Also, there's no way to provision w/o manual interaction with the instance afterwards.

Impact

Provisioning needs manual attention.

Ideal future situation

Deployment is fully configurable before provisioning, provisioning is automated for Flatcar. OS and Sysext update concepts are integrated and allow for customisation (maintenance windows).

Implementation options

  • Basic automation for provisioning on Flatcar
    • Automation uses system jitsi system user, /opt/jitsi exclusively.
    • Automation is self-contained, i.e. does not need to check out this repo on the node
    • Automation cleans up installer (this repo) after successful installation.
  • Automation gaps are closed
    • Set-up script identifies host IP address and passes it to Jitsi config
    • Set-up script waits for hostname to resolve to host IP before starting installation.
      This allows orchestration to create a DNS entry for the freshly deployed host w/o race condition with Jitsi's ACME cert request.
  • Automation is customisable, uses templates / env vars
    • hostname and letsencrypt email
    • optionally the Jitsi version to deploy
    • optionally user and password (default to jitsi and auto-generation)
    • optionally banner, logo, and watermark (skip if not present)
@t-lo
Copy link
Member Author

t-lo commented Aug 7, 2024

Mostly done, closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature A feature request.
Projects
None yet
Development

No branches or pull requests

1 participant