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)
NSM and Tungsten Fabric from LFN.
Briefly describe the project (i.e., what is the detail of what you're planning to do with these servers?)
We already have resources for NSM's CI on packet. We would like to extend the usage to build NSM+TF integration. The cost outlay would be approximately $900/month.
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, I am involved with NSM (CNCF sandbox) and TF is in the LFN umbrella. We will have people from the TF community accessing these systems.
First and Last Name
Frederick Kautz
Email
frederick@kautz.dev
Company/Organization
NSM
Job Title
Committer
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)
NSM and Tungsten Fabric from LFN.
Briefly describe the project (i.e., what is the detail of what you're planning to do with these servers?)
We already have resources for NSM's CI on packet. We would like to extend the usage to build NSM+TF integration. The cost outlay would be approximately $900/month.
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, I am involved with NSM (CNCF sandbox) and TF is in the LFN umbrella. We will have people from the TF community accessing these systems.
What kind of machines and how many do you expect to use (see: https://www.packet.com/bare-metal/)?
3x c1.small.x86
What OS and networking are you planning to use (see: https://support.packet.com/kb/articles/supported-operating-systems)?
Centos
Any other relevant details we should know about?
This is primarily for approval of the extending the usage from CI to development.
The goal is to use these for initial shared development. Once complete, the goal is to shift these workloads into CI only.