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

Request for cluster access for Cloud Native Buildpacks (Sandbox) #108

Closed
sclevine opened this issue Mar 7, 2019 · 11 comments
Closed

Request for cluster access for Cloud Native Buildpacks (Sandbox) #108

sclevine opened this issue Mar 7, 2019 · 11 comments

Comments

@sclevine
Copy link

sclevine commented Mar 7, 2019

First and Last Name

Stephen Levine

Email

slevine@pivotal.io

Company/Organization

Pivotal

Job Title

Staff Software Engineer

Project Title (i.e., summary of what do you want to do, not what is the name of the open source project you're working with)

Cloud Native Buildpacks CI

Briefly describe the project (i.e., what is the detail of what you're planning to do with these servers?)

We plan to use packet machines as concource.ci workers to test that our pack CLI (https://github.com/buildpack/pack) works properly on Windows. The CNCF partially funds a GCP account for testing Cloud Native Buildpacks, and we'd like to use Packet to reduce GCP infrastructure costs and test on Windows machines that can run nested VMs.

Is the code that you're going to run 100% open source? If so, what is the URL or URLs where it is located? What is your association with that project?

Yes, it is all open source.
We plan to run pack and pack tests here: https://github.com/buildpack/pack.
We plan to run lifecycle and lifecycle tests here: https://github.com/buildpack/lifecycle.
I am a project owner listed here: https://github.com/buildpack/spec/blob/master/OWNERS.

What kind of machines and how many do you expect to use (see: https://www.packet.com/bare-metal/)?

We would like 1 or 2 packet cloud Memory machines.

What OS and networking are you planning to use (see: https://support.packet.com/kb/articles/supported-operating-systems)?

We would like to use Windows Server 2016.

Any other relevant details we should know about?

N/A

@dankohn
Copy link
Contributor

dankohn commented Mar 7, 2019 via email

@taylorwaggoner
Copy link
Contributor

@sclevine I have created your project in Packet and sent you an invitation. Please let me know if you'd like to add any team members. Thanks!

@taylorwaggoner
Copy link
Contributor

@sclevine thanks! Unfortunately I can only mark individuals as a "Collaborator" on your project, so everyone will have the same access. Thanks!

@sclevine
Copy link
Author

sclevine commented Mar 7, 2019

Thanks again. No worries, that's perfect.

@vielmetti
Copy link
Collaborator

@sclevine @idvoretskyi

We have a maintenance need for your instance "rhel-openshift-gh-runner", regarding RHUI.

Existing customers will need to either (1) Replace the RHUI client package after downloading the updated RPM. OR (2) Redeploy their server on to a replacement server which will automatically be running the latest RHUI client version.

RHEL7 customers will need to remove the packet RHUI client (packet-rhui-client-rhel7-base-2.0-1) and install the EM client

http://rhui-rhua.dfw2.platformequinix.net/em-rhui-client-rhel7-2.0-1.noarch.rpm

RHEL8 customers will need to remove the packet RHUI client (packet-rhui-client-rhel8-base-2.1-1) and install the EM client

http://rhui-rhua.dfw2.platformequinix.net/em-rhui-client-rhel8-2.0-1.noarch.rpm

Please let me know if you need more details, and when this package update has been complete. It looks like the machine in question was provisioned in January 2021, but I don't know which human did that work.

@vielmetti
Copy link
Collaborator

Email sent. @sclevine I don't know if you are also on Slack.

@jromero
Copy link

jromero commented Sep 8, 2021

Hi @vielmetti, I'm the human responsible. 😁

I'll try to have this done by EOW if that's okay.

@vielmetti
Copy link
Collaborator

@jromero Glad to have made contact! That timeframe will be great.

@jromero
Copy link

jromero commented Sep 13, 2021

@vielmetti, sorry for the delay. Our machine has been destroyed. We are re-evaluating whether we need to spin another RHEL machine up in its place. Regardless, it sounds like this issue is now resolved.

@vielmetti
Copy link
Collaborator

Thanks @jromero - that works out perfectly for us. Closing this issue.

@vielmetti vielmetti added this to the Cloud Native Buildpacks milestone Oct 20, 2021
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

No branches or pull requests

5 participants