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

Metal³ (Metal Kubed) CI and Gating #260

Closed
3 of 14 tasks
intlabs opened this issue May 15, 2019 · 5 comments
Closed
3 of 14 tasks

Metal³ (Metal Kubed) CI and Gating #260

intlabs opened this issue May 15, 2019 · 5 comments
Labels
integration case Something want to test in OpenLab

Comments

@intlabs
Copy link

intlabs commented May 15, 2019

Metal³ (Metal Kubed) CI and Gating

What is your focus?

  • Performance
  • Scale
  • Reliability
  • Resiliency
  • Integration
  • Multi-Cloud
  • Operational Tooling
  • Edge or IoT
  • Machine Learning
  • Artificial Intelligence
  • Application Ecosystem
  • Other

If this is for an open source project what is it?

This would be for the Metal³ project (pronounced: Metal Kubed).

Brief project description

Metal³ provides components that allow you to do bare metal host management for Kubernetes. Metal³ works as a Kubernetes application, meaning it runs on Kubernetes and is managed through Kubernetes interfaces.

Is project code 100% open source? If so, what is the URL or URLs where it is located?

Yes, the code is hosted here: https://github.com/metal3-io

What kind of machines (VMs or Baremetal) and how many do you expect to use?

Initially, it would make sense to target single machines (either BM or VM's that support nested virtualization) to validate the e2e integration of the project - these would need to be sized to allow three small nested VMs, driven by vbmc as an analog to physical hardware, to be created within them.

What OS are you planning to use?

The current development/e2e environment targets CentOS, though it would be strongly desirable to support a Debian derived distribution as well.

Any special network configuration you expect or anticipate implementing?

None

Any architecture or other specifications/requirements (CPU, RAM, GPU, etc)?

The machines will need to be sized to allow three VMs (4vCPU, 8Gb RAM) to be created in addition to the support services.

What testing are you planning to implement or need assistance implementing?

The testing will be e2e integration testing of the Metal³ project to manage bare-metal nodes via Kubernetes custom resource objects.

How will this testing advance application and/or tooling built on-top of open infrastructure?

This testing will enable the validation of bare-metal node management via Kubernetes.

Will you publish blog or paper from your testing?

  • Yes
  • No - if no, how will you present your results?

Any other relevant details we should know about while preparing the infrastructure?

None

@intlabs intlabs added the integration case Something want to test in OpenLab label May 15, 2019
@intlabs intlabs changed the title metal3 (metalkubed) CI and Gating Metal³ (Metal Kubed) CI and Gating May 15, 2019
@hogepodge
Copy link

/lgtm

1 similar comment
@stmcginnis
Copy link

/lgtm

@mrhillsman
Copy link
Contributor

@intlabs please find general instructions for setting up the CI here - https://docs.openlabtesting.org/publications/contributors/connect-to-openlab

@intlabs
Copy link
Author

intlabs commented May 16, 2019

Will by Monday @mrhillsman! Thanks so much for all your help and support :)

@kiwik kiwik added this to To Do in OpenLab Status Board via automation May 17, 2019
@kiwik
Copy link
Contributor

kiwik commented May 17, 2019

@intlabs if you have any question, feel free to raise it in OpenLab IRC channel #askopenlab on freenode, @theopenlab/dev team stand by :)

OpenLab Status Board automation moved this from To Do to Done Feb 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
integration case Something want to test in OpenLab
Projects
Development

No branches or pull requests

6 participants