Closed micahhausler closed 2 years ago
Thanks for the introduction @micahhausler. Let's differentiate repo goals via title and description (based on the current GH details):
PBnJ: Microservice that communicates with BMCs to control power, boot, etc
This service handles BMC interactions.
- machine and BMC power on/off/reset
- setting next boot device
- user management
- setting BMC network source
The gRPC PBnJ server listens by default on port 50051. This can be started with pbnj server. Use pbnj server --help for more runtime details.
How would we describe Rufio, and most importantly what is the backronym?
Loving Rufio
How would we describe Rufio, and most importantly what is the backronym?
The goals are largely the same, but the implementation and architecture is the difference.
Goals:
Implementation
How would we describe Rufio, and most importantly what is the backronym?
Rufio is a declarative state manager for BMCs.
Rufio is the leader of the Lost Boys in the 1991 movie Hook.
If we're going to re-brand PBnJ (or fork it) I would like to throw out the name "dust"
Pixie dust is the magic of flying in the clouds (as long as you have happy thoughts).
If you want a backronym
D ust U pdates S tate for T inkerbell
I :heart: Rufio. It has been 31 years and it's still too soon :cry:
I'm fine with either (they're both better than PBnJ) but wanted to suggest my idea from last year.
So the name tinkerbell I believe was chosen due to the fact that the whole platform is powered by PXE dust. 😂
There's also an existing ipxedust repository so things could get confusing.
I have no idea how I didn't even know that was a repo. I retract my suggestion. That would be very confusing.
What about 'brig' or 'roger'. Captain hook sailed a brig named Jolly Roger
For a backronym:
Rufio Utilizes Fancy IPMI Operations
I'm asking the CNCF for recommendations on the rufio
name.
Closing this now that we have the repo
Request for CNCF clarity submitted: https://cncfservicedesk.atlassian.net/servicedesk/customer/portal/1/CNCFSD-1261
As we at AWS (mainly @pokearu) have looked into refactoring PBnJ to run as a kubernetes controller (tinkerbell/pbnj#121), the paradigm is very different from the current "PBnJ as a server" architecture. I have a branch of pbnj adding some kubebuilder-generated scaffolding, but it became obvious to me that almost no code will be re-used, and there is a lot of modification to get the kubebuilder generated pieces to play nice. PBnJ has make targets that overlap with the kube-builder generated makefile, and existing make targets like
make image
would need to be refactored for multiple images.Given the difference in architecture and maintenance, I propose a new GitHub repo. This is similar to how Hook replaced OSIE.
I propose the name "Rufio" after the character from the 1991 movie Hook.