Bruce,

Thanks for you input, I’ve mapped the Hummingbird’s components to repos as well as existing sub-projects below:

Components of HB	Related sub-project	Landed in repos
New personality	Flock services project	config
Networking	Networking project/ Security project	integ
Provisioning	Containers project	ansible-playbook
Management	Flock services project/ Containers project	config/metal/fault
Storage	Non-openstack project	TBD
App orchestration	Containers project	TBD
Dist-cloud collaboration	Distributed cloud project	distcloud

As you can see, the components will be landed in multiple repos across multiple sub-projects.

Mingyuan

From: Jones, Bruce E <bruce.e.jones@intel.com>
Sent: Friday, June 5, 2020 1:42
To: Qi, Mingyuan <mingyuan.qi@intel.com>; starlingx-discuss@lists.starlingx.io
Subject: RE: Hummingbird: A project for small node management

Mingyuan, thank you for bringing this proposal forward.

I’d like to explore the idea of creating a sub-project for this.

Do you have an estimate as to which repos the project will be working in? Are there new repos to be created? Will the changes land in other sub-project areas? If so, which?

If we can figure out where the code lands, that would help us figure out which existing sub-project (if any) should be the home for this code, or if a new sub-project is needed.

brucej

From: Qi, Mingyuan <mingyuan.qi@intel.com>
Sent: Thursday, June 4, 2020 12:34 AM
To: starlingx-discuss@lists.starlingx.io
Subject: [Starlingx-discuss] Hummingbird: A project for small node management

Hi,

In Tuesday’s PTG, I have introduced the proposal of a sub-project for small node management: Hummingbird.

I put the document link here[0] for community members who are interested in the detail info but haven’t joined Tuesday PTG.

The target of Hummingbird project is to bring the ability of edge node(small node) management to StarlingX.

The project gets the name “Hummingbird” from hummingbird’s characteristics: Tiny, stably hovering and echo to “starling”.

Here are 3 reasons that having Hummingbird as a sub-project:

A bunch of technical areas such as containerization, networking, storage and flock services are converged in Hummingbird. The implementation of Hummingbird needs to be well coordinated among these technologies.
Hummingbird will be developed in a long term across multiple releases. The development pace of delivering features for small node management could be well discussed in the form of a sub-project.
Current sub-projects are organized in fundamental technologies. A sub-project based on individual functionality comes from a different perspective, for example like the projects in Openstack. It will enhance the collaboration of the members in different technology background in the community.

All above aim to bring the small node management to StarlingX in a well scheduled and quality ensured way.

It’s a brand new proposal and I hope you could find something interesting in the doc. Welcome your questions and inputs.

[0] https://drive.google.com/file/d/1VpglICCzI_PSGdCC12Y7MzhSE8cAolTM/view?usp=sharing

Best Regards,

Mingyuan