Skip to content

Add docs section on deploying a local pulp#42

Open
sd109 wants to merge 6 commits into
mainfrom
docs/non-sms-clouds
Open

Add docs section on deploying a local pulp#42
sd109 wants to merge 6 commits into
mainfrom
docs/non-sms-clouds

Conversation

@sd109

@sd109 sd109 commented Jan 25, 2024

Copy link
Copy Markdown

No description provided.

Comment thread README.rst Outdated
Comment thread README.rst Outdated
Comment thread README.rst Outdated
Comment thread README.rst Outdated
Comment thread README.rst Outdated
Comment thread README.rst Outdated
@Alex-Welsh Alex-Welsh requested a review from MoteHue January 26, 2024 10:17
MoteHue
MoteHue previously approved these changes Jan 26, 2024

@MoteHue MoteHue left a comment

Copy link
Copy Markdown
Contributor

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
Copy Markdown
Member

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
Copy Markdown
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
Copy Markdown
Member

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