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

(WIP) VPN deployment using puppet #1031

Draft
wants to merge 7 commits into
base: production
Choose a base branch
from

Conversation

dtapiacl
Copy link
Contributor

This is PR was created to deploy the vpn service at Rubin Observatory.

Ticket of reference: IT-4981

@dtapiacl dtapiacl added the enhancement New feature or request label Jan 12, 2024
@dtapiacl dtapiacl self-assigned this Jan 12, 2024
@dtapiacl dtapiacl force-pushed the IT-4981_openvpnas_puppet branch 2 times, most recently from 6d8104a to 59a56d2 Compare January 12, 2024 15:07
Copy link
Member

@jhoblitt jhoblitt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the plan for configuring openvpn?

@dtapiacl
Copy link
Contributor Author

dtapiacl commented Jan 30, 2024

What is the plan for configuring openvpn?

Hey @jhoblitt, the VPN service was already previously configured by @hstockeb. I imported the database configuration onto this deployment to get it up and running. @hstockeb could provide more information for its specific configuration and setup.

@jhoblitt
Copy link
Member

@dtapiacl Multiple openvpn modules on the puppet forge support configuration. It would be a good idea to automate as much of the configuration as possible as a DR measure. Installing the packages is a good first step but the configuration is much more valuable.

@jhoblitt
Copy link
Member

@dtapiacl To be pedantic, I see 3 good courses of action. 1) use an existing forge module to configure openvpn. 2) modify/fix an existing forge module to configure openvpn. 3) write a new module to manage openvpn and publish it the forge. Option #3 should only be a last resort after attempting option 1/2.

It is not a good idea to add profile(s) to this the control repo that duplicate the functionality of existing forge modules. Every line of code has a maintenance burden. As a general rule, we should try to add the minimum on-going maintenance requirement as possible onto our fellow engineers.

@dtapiacl dtapiacl changed the title (vpn.ls.lsst.org) VPN deployment using puppet (WIP) VPN deployment using puppet Feb 20, 2024
Copy link
Member

@jhoblitt jhoblitt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would like to see configuration of the service and to use a forge module. E.g. https://forge.puppet.com/modules/puppet/openvpn/readme

@dtapiacl dtapiacl force-pushed the IT-4981_openvpnas_puppet branch 13 times, most recently from 64d1e95 to de44d04 Compare March 6, 2024 15:59
@dtapiacl dtapiacl force-pushed the IT-4981_openvpnas_puppet branch 3 times, most recently from fcf0448 to b8ed3bf Compare March 6, 2024 17:56
@dtapiacl dtapiacl force-pushed the IT-4981_openvpnas_puppet branch 2 times, most recently from 9dfe0e6 to 2311740 Compare April 22, 2024 17:50
@dtapiacl dtapiacl marked this pull request as draft June 11, 2024 03:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants