Shulou(Shulou.com)05/31 Report--

This article introduces the relevant knowledge of "what is the definition of cloud and CNCF charter". In the operation of actual cases, many people will encounter such a dilemma. Next, let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

The definition of Cloud Native

Pivotal is the proponent of cloud native applications, and launched the Pivotal Cloud Foundry cloud native application platform and Spring open source Java development framework, becoming a pioneer and pathfinder in cloud native application architecture.

The original definition of Pivotal

As early as 2015, Matt Stine of Pivotal wrote a pamphlet called migrating to Cloud Native Application Architecture, which discusses several main features of Cloud Native Application Architecture, which meets 12-factor applications:

Micro service oriented architecture

Self-service agile architecture

API-based collaboration

Anti-vulnerability

I have translated this book in 2017, see migrating to cloud native application architecture for details.

The original definition of CNCF

In 2015, Google dominated the Cloud native computing foundation (CNCF). At first, CNCF's definition of cloud native (Cloud Native) included the following three aspects:

Application containerization

Micro service oriented architecture

Application supports container choreography and scheduling

Redefinition-Cloud Native (Cloud Native)

By 2018, with the continuous state of cloud native ecology in only a few years, all major cloud computing providers have joined the foundation, and Cloud Native Landscape shows that cloud native is intentionally encroaching on previously non-cloud native applications. With more and more members and projects in the CNCF Foundation, this definition has limited the development of cloud native ecology, and CNCF has repositioned the cloud native.

The following is CNCF's redefinition of cloud natives (in Chinese and English):

Cloud native technologies empower organizations to build and run scalable applications in modern, dynamic environments such as public, private, and hybrid clouds. Containers, service meshes, microservices, immutable infrastructure, and declarative APIs exemplify this approach.

Cloud native technologies help companies and organizations build and run resilient applications in new dynamic environments such as public, private, and hybrid clouds. Representative technologies of cloud natives include containers, service grids, microservices, immutable infrastructure, and declarative API.

These techniques enable loosely coupled systems that are resilient, manageable, and observable. Combined with robust automation, they allow engineers to make high-impact changes frequently and predictably with minimal toil.

These technologies can build loosely coupled systems with good fault tolerance, easy to manage and easy to observe. Combined with reliable automation, cloud native technology makes it easy for developers to make frequent and predictable major changes to the system.

The Cloud Native Computing Foundation seeks to drive adoption of this paradigm by fostering and sustaining an ecosystem of open source, vendor-neutral projects. We democratize state-of-the-art patterns to make these innovations accessible for everyone.

The Cloud Native Computing Foundation (CNCF) is committed to fostering and maintaining a vendor-neutral open source ecosystem to promote cloud native technologies. We make these innovations available to the public by embracing cutting-edge models.

Note: the Chinese translation of this definition has not been formally determined. For more information, please see Cloud Native Definition in Chinese.

CNCF charter

CNCF (Cloud Native Computing Foundation) is a foundation under the Linux Foundation. Joining CNCF means joining the Linux Foundation at the same time (which also means you have to pay part of the Linux Foundation). For enterprises or organizations that want to join the CNCF Foundation, the first thing to do is to understand the CNCF Constitution, just like as a citizen of a country, you must abide by the country's constitution. The reason why CNCF has grown to such a scale in just three years is largely related to its excellent community governance and mode of operation. Understanding the charter can help us understand how CNCF works and can come in handy when we do our own open source project governance.

The charter was last updated on May 15, 2018, as detailed in https://www.cncf.io/about/charter/. The introduction to the CNCF charter below is quoted from how CNCF works, with changes.

1. The mission of CNCF

CNCF does not deviate from its theme, the core is to solve technical problems: the foundation's mission is to create and promote the adoption of a new computing model, which is optimized for modern distributed system environments and can scale to tens of thousands of self-healing multi-tenant nodes.

The so-called cloud native system must have the following attributes:

Application containerization: applications and processes in the software container are run as separate application deployment units and as a mechanism for achieving high-level resource isolation. Generally improve the developer's experience, promote code and component reuse, and simplify the operation and maintenance work for Cloud Yuan is a domestic application.

Dynamic management: active scheduling and frequent management by centralized scheduling, which fundamentally improve machine efficiency and resource utilization, while reducing the costs related to operation and maintenance.

Micro-service oriented: loosely coupled with explicitly described dependencies (for example, through service endpoints), you can improve the overall agility and maintainability of the application. CNCF will shape the development of technology, promote the development of advanced technology of application management, and make technology ubiquitous and easy to use through reliable interfaces.

2. The role played by CNCF

CNCF actually plays a role on the basis of the open source community and is responsible for:

A) Project management

Ensure that technology is available to the community and that there is no miscellaneous impact

Ensure that technology brands (trademarks and logos) are noticed and used by community members, with special emphasis on a unified user experience and a high level of application compatibility

B) promote the development and evolution of ecosystems

Assess which technologies can be incorporated into the vision of cloud native computing applications, encourage the community to deliver such technologies, and integrate them, and actively advance the summary progress.

Provide a way to cultivate common technical standards for each part

C) promote underlying technologies and application definitions and management methods, including through events and conferences, marketing (SEM, direct marketing), training courses and developer certification

D) serving the community by making technology accessible and reliable

The aim is to provide a fully integrated and qualified build for each component through a clearly defined rhythm of the reference architecture.

3. The values of CNCF

CNCF strives to follow the following principles:

Speed is better than time, and one of the original intentions of the foundation is to allow the project to develop rapidly so that users can actively use it.

Open up! CNCF is based on openness and a high degree of transparency and operates independently of any other group. CNCF accepts all contributors according to the content and advantages of contribution, and follows the values of open source, the technology exported by CNCF can be used and benefited by everyone, and the technology community and its decisions should be highly transparent.

Fairness: CNCF will try its best to avoid bad influences, bad behavior, and "pay-as-you-go" decisions.

Strong technical identity: CNCF will achieve and maintain a high degree of technical identity and synchronize it to all shared projects.

Clear boundaries: CNCF sets clear goals and, in some cases, what is not the goal of the foundation, and will help the entire ecosystem operate and let people understand the focus of new innovation.

Scalable: ability to support all deployment sizes, from small developer-centric environments to enterprise and service provider sizes. This means that some optional components may not be deployed in some deployments, but the overall design and architecture should still apply.

Platform neutrality: projects developed by CNCF are not targeted at a particular platform, but are designed to support a variety of architectures and operating systems.

4. Membership system

Members in CNCF include platinum, gold, silver, end-user, academic and non-profit members, and different levels of members have different voting rights in the board.

A) Platinum member: appoint 1 representative in the CNCF Council and 1 voting representative in each subcommittee and event of the Council, which can be highlighted on the website; if also an end user member will inherit all the rights of the end user member

B) Gold members: for every five gold medal members in the foundation, members of this level may appoint one representative and a maximum of three; if also an end user member will inherit all the rights of the end user member

C) Silver members: for every 10 silver members in the foundation, members of this level may appoint 1 representative and a maximum of 3; if also an end-user member will inherit all the rights of the end-user member

D) end users: participate in the end-user consulting community; nominate a representative to the end-user Technical Advisory Committee

E) academic and non-profit members: academic and non-profit members are limited to academic and non-profit institutions respectively and are subject to the approval of the Council. Academic and non-profit members have the right to recognize their organizations as members in support of the CNCF mission and any other rights or interests determined by the Council.

5. The council

A) the CNCF Council is responsible for marketing, business supervision and budget approval, not technical aspects, except for working with TOC to determine the scope of CNCF work, completion schedule a) and update the CNCF website

B) responsible for day-to-day affairs

Negotiate the overall scope of CNCF with TOC

Trademark and copyright protection

Marketing, preaching and ecosystem building

Create and execute brand commitment projects, if necessary

Supervise operation and business development

Fund-raising and financial management

C) the voting members of the Council shall be composed of representatives of members and communities:

Members' representatives include:

Each platinum member appoints a representative

Gold and silver medals elected representatives

Representatives of the technical community include:

Chairman of the Technical Supervision Committee

Two submitters were selected from the CNCF project in accordance with the procedures approved by the then incumbent governing Council.

The board may expand platinum membership at the price of platinum membership and conduct annual audits for up to five years of startups with annual revenues of less than $50 million, which are seen as strategic technology contributors to the board.

Only people from a group of affiliated companies can act as member representatives. Only people from a group of affiliated companies can act as technical community representatives.

D) responsibilities

Approve the budget to guide the use of funds raised by all sources of income for technology, market, or community investment to advance the mission of the CNCF Fund

Elect the President of the Council to preside over the meeting, approve budget-approved expenditures and manage day-to-day operations

Vote on a decision or matter of the Council

Define and implement the Foundation's intellectual property (copyright, patent or trademark) policies

Direct marketing and evangelization through events, news and analyst campaigns, online, social media and other marketing activities

Supervise operation and business development

Establish and oversee any committee created to advance the mission of CNCF

Establish and implement a brand compliance plan (if any) based on CNCF requirements (which may include certification testing) to use the brand logo established by TOC

Adopt guidelines or policies for the use of trademarks

Provide overall financial management.

E) use of the income of the Foundation

Marketing, users expand the adoption of projects in CNCF

Key facilities construction, operation and management of project infrastructure

Promote the use of project implementations in CNCF for container-based computing

6. Technical Supervision Committee (TOC) a) requirements

The CNCF Technical Oversight Committee, in order to remain neutral, reached the following consensus:

Define and maintain the technical vision of CNCF.

Approve new projects within the scope of CNCF developed by the Council and create a conceptual framework for the project.

Correct the development direction of the project and make a decision to delete or archive the project.

Receive feedback from the end-user committee and reflect it in the project.

Adjust the interface of the component under scientific management (reference before code standardization)

Define common practices, if any, that are implemented in CNCF projects.

B) composition of the Technical Oversight Committee

TOC consists of up to 9 members.

The selected TOC members will cover key technical areas: container technology, operating system, technical operation and maintenance, distributed systems, user-level application design, and so on.

The Council will elect six TOC members, the end user TAB will elect one TOC member, and the first seven TOC members shall elect two additional TOC members.

If more than two TOC members are from the same group of affiliated companies, whether at the time of the election or from a subsequent job change, they will jointly decide who should step down, or if there is no basis for negotiation, lots shall be drawn.

C) Operation model

The TOC will elect the chairman of the TOC, which is mainly responsible for the agenda and convening meetings of the TOC.

TOC will discuss important hot issues face-to-face every quarter.

TOC may meet as needed to discuss emerging issues. The TOC audit may raise the following questions:

Any TOC member

Any member of the board

Maintainer or top project leader of the established CNCF project

Executive Director of CNCF

End-user Technical Advisory Committee received a majority of votes

Be transparent: TOC meetings, mailing lists, and meeting minutes are all publicly accessible.

Simple TOC issues can be resolved through brief discussion and simple majority voting. TOC discussions can be conducted via email or TOC meetings.

After reviewing comments and optional virtual discussion / debate options, seek consensus and vote if necessary.

The goal is to get TOC to find ways to reach a consensus within TOC and the community. The TOC decision of a meeting that meets the quorum requirement shall be adopted in a manner exceeding 50 per cent of the attendance of TOC members.

The TOC meeting requires a quorum of 2/3 of the total number of TOC to vote or take any decision. If the TOC meeting fails to meet the quorum requirement, it can be discussed, but there should be no vote or decision.

TOC decided that it could be made electronically without a meeting, but how many votes would be required to pass a vote to reach the quorum of the meeting. In electronic voting, if any two TOC members request a meeting to discuss the decision, the electronic voting is invalid at the end of the meeting, and a new vote can be initiated after the meeting to discuss that the decision has been completed.

D) nomination criteria

Open source contributors nominated by TOC should have the following conditions:

Commit to have sufficient available time to participate in CNCF TOC activities, including fairly early input at the time of the establishment of CNCF, and then continue to invest time, with adequate preparation and review prior to quarterly TOC meetings.

Demonstrated a high level of professional experience within the scope of CNCF.

Prove that they are qualified to receive additional staff or community members to assist them in their work in TOC.

Remain neutral in the discussion and propose that the goals and success of CNCF should be balanced with the company's goals or any particular project in CNCF.

E) procedures for the nomination and election of TOC members

TOC consists of nine TOC members: six elected by the board, one elected by the end user TAB and two elected by the initial seven TOC members.

Nomination: each individual (entity or member) eligible to nominate a TOC member may nominate up to 2 technical representatives (from suppliers, end users, or any other field), up to one of whom may be from their respective company. Nominees must agree in advance to be added to the list of candidates.

The initial seven TOC members (six members elected by the Council plus one member elected by the end-user TAB) shall use the nomination procedure to nominate and elect two TOC members.

Nominees are required to provide up to an one-page introduction, including the nominee's name, contact information and supporting statements, confirming the nomination experience in the CNCF field.

The Council, end-user TAB and TOC shall determine schedules and dates for nominations, ballots and any other details of the TOC election nomination and election process.

A minimum of 14 calendar days will be retained during the evaluation period, and TOC nominees can contact and / or evaluate candidates.

Election: after the end of the evaluation period, the Council, the end-user tag and the first seven TOC members shall vote on each candidate. Valid voting requires the number of votes required to meet the quorum of the meeting. Each candidate needs to support more than 50% of the number of voters to confirm that the nominee meets the eligibility criteria. Candidates approved by a majority shall be qualified members of the TOC.

If the number of qualified nominees is equal to or less than the number of optional TOC seats, the nominee shall be approved after the end of the nomination period. If there are more qualified candidates than the Council, end-user TAB or TOC optional open TOC seats, then the group shall vote for TOC members through Condorcet. Condorcet voting should be run using the Condorcet-IRV method through the Cornell online Service (http://civs.cs.cornell.edu/).

If the number of eligible candidates for open TOC seats available for election by the Council, end-user TAB or TOC is low, the panel will initiate another round of nominations, with each member or individual eligible to nominate up to one candidate.

F) constraints

The term of office of the members of TOC is two years, and the term of office of the first six elected TOC members elected by the Council is three years. The initial term of office of TOC members elected by the end users TAB and TOC is 2 years.

TOC members may be removed by 2/3 of the votes of other TOC members, and affected individuals will not be able to vote.

Any TOC member will be automatically suspended from voting for three consecutive meetings until he attends two consecutive meetings. For the avoidance of doubt, suspended TOC members are eligible to vote at the second consecutive meeting.

The constitution, model, method and composition of the TOC can be amended by two-thirds of the votes of the entire council.

The TOC agenda will be set by TOC. However, it is expected that the initial TOC discussions and decisions will include:

Evaluate the technologies included in CNCF

Determine the acceptance criteria for the incorporation of new technologies into CNCF

Define the process for approving technology as a contribution to a standard API

Identify direct gaps that require further investigation

7. End user community

A) end-user members of CNCF have the right to coordinate and promote the important activities of CNCF users as consumers of CNCF designs. Each end user participant can be invited to participate in any member or non-member that is an end user. End-user participants will help advise the Technical Advisory Committee and the CNCF community on user-related topics.

B) the end-user Technical Advisory Committee is elected by members of the end-user community

C) members of the end-user community will be approved by the Executive Director of CNCF or, in the absence of the Executive Director of CNCF, by the Executive Director of Linux Foundation.

8. End-user Technical Advisory Committee ("end-user TAB")

A) composition: end user TAB shall consist of 7 representatives from end user participants plus 1 member of TOC to facilitate promotion from end user TAB to TOC.

B) Election: in order to encourage end-user participation in CNCF, the first seven end-user members may appoint a representative to participate in the initial end-user TAB and assign CNCF directors to any remaining seats of any end-user participant. After the first year, all end-user participants can nominate 1 representative and the end-user community should vote for end-user TAB members that use the current end-user TAB approval process.

C) after a 2/3 vote, the end user TAB can change the size of the end user community, provided there are at least 7 possible representatives.

D) end-user representatives should be nominated on the basis of business and technical acumen Candidates should have important practical experience in building and operating infrastructure and applications that embody CNCF principles.

E) the end user TAB will discuss and advance the topic, focusing on identifying gaps and priorities between the TOC and CNCF developer communities.

F) will also focus on proactively promoting topics of concern to end-users, promoting market adoption of CNCF, organizing meetings for end-users or advising the Council.

G) if the end user TAB wishes, it can approve the subcommittee special interest group ("SIG") to solve industry or professional topics.

H) the end-user TAB is the main importer of the Technical Oversight Committee and should make decisions and plans together with other importers and feedback of the Technical Oversight Committee. These recommendations are only advisory, and at no time can the recommendations of the end user TAB be used to command or guide any TOC or project participant to take any action or outcome.

I) in order to facilitate bilateral interaction with TOC, the end-user Technical Advisory Committee shall elect a TOC representative. The end user TAB can invite anyone to participate in an end user meeting, SIG, or other discussion.

9. CNCF Project

Usually, it is the member companies of CNCF and members of the open source community that bring the project to the technical oversight committee of CNCF for discussion and then decide whether or not to be accepted by CNCF. Projects to be contributed to CNCF must be based on standards established by the Technical Oversight Committee and, of course, approved by the Board. The goal of CNCF is that projects donated to CNCF and existing projects in CNCF are to some extent related and can be integrated.

There are three ways to associate with CNCF:

It is already under the control of CNCF. After all, CNCF is neutral and is committed to becoming the place where everyone belongs.

A) all aspects of the project are handled by CNCF

B) the project is marketed by CNCF

C) projects are core components to solve cloud native computing problems, such as Kubernetes, Mesos, etcd, etc.

Associate XM with CNCF through API or specification

A) include components that CNCF may provide or enable multiple options

B) the project is called an integral part of CNCF integration, not a project sponsored by CNCF

C) Integration and compliance are defined by API or specification

D) the development of the project or component is developed by the upstream community and maintains a certain degree of activity

Used by CNCF

A) the project or component is licensed under an open source license approved by OSI, is well managed, and is used as a component in CNCF.

B) the project is not marketed by CNCF

C) the development of the project or component is developed by the upstream community and maintains a certain degree of activity

Existing open source projects should continue to maintain their existing technical governance structure in order to maintain cohesion and speed. However, after being approved by the Technical Supervision Committee, some adaptation will be made appropriately.

A standard agreement to achieve submitter status should be established between projects according to the level of the individual and the duration of contribution. Because the submitter is the selection pool of maintainers, with a certain degree of contribution, and with the recognition of peers, the submitter can be promoted to maintainer.

New open source projects initiated by CNCF should complete the project proposal template adopted by TOC and be approved by TOC for inclusion in CNCF. TOC members should have sufficient time to discuss and review new project proposals. The new project proposal should include details of the roles in the project, proposed governance for the project, and be consistent with the roles and values of CNCF.

10. Market committee

A) constitute that the Market Committee will be open to all members and shall elect the Chairman of the Market Committee to set the agenda for the meeting, conduct general discussions and help the Committee achieve its objectives. The Market Committee should seek consensus as much as possible. Any issues on which consensus cannot be reached in the Market Committee shall be referred to the Council.

B) responsibilities: the Market Committee, on behalf of the Board, is responsible for the design, development and execution of related marketing work.

C) if the Market Committee becomes too large to operate effectively, the Market Committee may choose to elect market directors and delegate decision-making power to market directors.

11. Intellectual property policy

A) any project that joins CNCF must transfer its trademark and logo assets to the ownership of the Linux Foundation.

B) each project should determine whether approved CNCF CLA is required. For projects that choose to use CLA, all code contributors will assume their obligations under the Apache Contributor license Agreement and will modify them only if necessary to determine that CNCF is the recipient of the donation and shall be approved by the Board. Please refer to the CNCF participant license agreement available on https://github.com/cncf/cla.

C) all new inbound codes submitted to CNCF shall (I) be signed by the developer's original certificate (http://developercertificate.org and (ii) under the Apache license version 2.0 (available from http://developercertificate.org and http://www.apache.org/licenses/LICENSE-2.0) in addition to and shall not supersede the obligations under the contribution license agreement set forth in (b) above.

D) all outbound codes will be provided under the Apache license version 2.0.

E) all projects that are evaluated for inclusion in CNCF must be fully licensed under an open source license approved by OSI, and if the license for the project included in CNCF is not version 2.0 of the Apache license, approval from the Council is required.

F) all documentation will be provided by CNCF under the Creative Commons signature 4.0 International license.

G) if alternative inbound or outbound licenses are required to comply with leveraged open source project licenses or other licenses are required to achieve the mission of CNCF, the Board may approve the use of alternative licenses for project donations accepted or provided in exceptional circumstances.

twelve。 Antitrust guide

A) all members shall comply with the requirements of the Linux Foundation as set out in the antitrust policy of the Linux Foundation provided on the http://www.linuxfoundation.org/antitrust-policy.

B) all members should encourage the open participation of any organization that can meet the requirements of the members, regardless of their competitive interests. In other words, the Council shall not seek to exclude members on the basis of any criteria, requirements or reasons other than those applicable to all members.

13. Code of conduct

All participants must agree to abide by the Linux Foundation Code of Conduct. TSC can vote for its own CNCF code of conduct.

14. Affiliated company

A) definition:

"subsidiary" means any entity in which a member directly or indirectly owns more than 50% of the securities or member interests of the entity in question.

"affiliated company" means any entity controlled or controlled by a member, or an entity jointly controlled by a third party with a member and, in all cases, directly or indirectly has more control than ownership

"affiliated company" means the affiliated company of each member.

B) only the legal entity and its subsidiary that has implemented the participating agreement are entitled to the rights and privileges of the member, provided that the member and its subsidiary are treated together as a single member.

C) only one member belonging to a group of affiliated companies has the right to appoint or nominate representatives of the Council at one time to participate in category elections.

D) if a member is a foundation, alliance, open source project, member organization, user group or other entity of a member or sponsor, the rights and privileges granted to that member can only be extended to the employee representatives of that member, not to its members or sponsors, unless otherwise approved by the Council from time to time in specific circumstances.

E) membership shall not be transferable, non-transferable and non-transferable unless the existing member transfers its existing membership interests and obligations to its successors in most of its business and / or assets, whether by merger, sale or otherwise, as long as the assignee agrees to abide by the articles of association of CNCF and the articles and policies required by Linux Foundation members.

15. Budget

A) the Council shall approve the annual budget and will not undertake to exceed the funds raised. The budget should be in line with the non-profit mission of the Linux Foundation.

B) the Linux Foundation shall report budgetary expenditure on a regular basis

16. Routine and administrative expenses

A) the Linux Foundation shall take care of any fees, funds and other cash receipts.

B) General and administrative costs will be used to raise funds to cover financial, accounting and operating costs GambiA fees shall be equal to 9 per cent of CNCF's total down-front revenue of $1000000 and 6 per cent of CNCF's total revenue exceeding $1000000.

17. General rules and actions

To participate in CNCF, you should:

A) demonstrate plans and approaches for coordination with the open source project developer community, including on brands, logos and other iconic themes that represent the community

B) the goal of maintaining community cohesion in a professional manner, while maintaining the goodwill and respect of the Linux Foundation in the open source software community

C) respect the rights of all trademark owners, including any brand and guidelines for use

D) participate in all news and analyst relations activities of the Linux Foundation

E) provide the Linux Foundation with information on project participation, including participation in project sponsorship activities, as requested

F) directly participate in any site under the Foundation.

G) operate in accordance with the rules and procedures approved by the Council, provided that these rules and procedures are not inconsistent with the purposes and policies of the Linux Foundation and do not prejudice the Linux Foundation.

18. Amendment

These statutes may be amended by 2/3 votes of all members of the Council (excluding abstention), provided that any such amendment is not inconsistent with the purposes or policies of the Linux Foundation and does not adversely affect the Linux Foundation.

Schedule A: propose a vision of CNCF scope

The primary goal behind CNCF is to support and accelerate the adoption of "cloud native computing". The following is a preliminary scope designed to clarify the core concepts of "cloud native computing" that CNCF will strive to implement. This initial scope should be a document published on the CNCF website.

The CNCF community firmly believes that cloud native computing contains three core attributes:

Containerized packaging and distribution

Dynamic scheduling

Micro-service oriented

Note: the definition of cloud natives is being reconfigured and is different from the above.

Cloud native computing systems support computing based on these core attributes and include the following ideals:

Openness and scalability

A well-defined API at the boundaries of the standardization subsystem

Minimum obstacles to application lifecycle management

This is the end of the content of "what is the definition of Cloud Native and CNCF Charter". Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.