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

Add docs section on deploying a local pulp #42

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

sd109
Copy link
Member

@sd109 sd109 commented Jan 25, 2024

No description provided.

README.rst Outdated Show resolved Hide resolved
README.rst Outdated Show resolved Hide resolved
README.rst Outdated Show resolved Hide resolved
README.rst Outdated Show resolved Hide resolved
README.rst Outdated Show resolved Hide resolved
README.rst Outdated Show resolved Hide resolved
@Alex-Welsh Alex-Welsh requested a review from MoteHue January 26, 2024 10:17
MoteHue
MoteHue previously approved these changes Jan 26, 2024
Copy link
Contributor

@MoteHue MoteHue left a comment

Choose a reason for hiding this comment

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

Would be nice as a future task to just pass in Ark creds and have the rest handled automatically, but as an initial pulp on seed support this looks good to me 👍

@Alex-Welsh
Copy link
Contributor

I realised it's actually quite easy to add those changes to the deployment script so I just put the command in there

@jackhodgkiss
Copy link
Contributor

We could also consider a standalone Pulp server for the eventuality of multiple separate multinode environments or short lived environments. Otherwise we would be downloading 10s GiBs everytime a multinode environment is created and disposed of.

Possible implementation would be some separate Terraform that creates this server.

@Alex-Welsh
Copy link
Contributor

We could also consider a standalone Pulp server for the eventuality of multiple separate multinode environments or short lived environments. Otherwise we would be downloading 10s GiBs everytime a multinode environment is created and disposed of.

Possible implementation would be some separate Terraform that creates this server.

Maybe some TF in SKC to deploy a pulp server on their cloud? Separating it from the multinodes sounds like a good idea. It might also come in handy for in-cloud CI runners or highly secure environments where VMs have no internet access

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

Successfully merging this pull request may close these issues.

4 participants