├── .gitignore ├── OWNERS ├── MEMBERS ├── README.md ├── REPOSITORIES ├── GOVERNANCE.md └── LICENSE /.gitignore: -------------------------------------------------------------------------------- 1 | .idea 2 | -------------------------------------------------------------------------------- /OWNERS: -------------------------------------------------------------------------------- 1 | # Owners 2 | 3 | adrianchiris 4 | davecremins 5 | dcbw 6 | dougbtv 7 | killianmuldoon 8 | moshe010 9 | rdower 10 | RossGLPT 11 | s1061123 12 | seware 13 | sfblackl-intel 14 | sureshkrishnan 15 | szollin 16 | -------------------------------------------------------------------------------- /MEMBERS: -------------------------------------------------------------------------------- 1 | adrianchiris 2 | amorenoz 3 | aneeshkp 4 | Ayush21298 5 | bpickard22 6 | clarkek 7 | coveralls 8 | crandles 9 | davecremins 10 | dcbw 11 | dougbtv 12 | edcdavid 13 | Eoghan1232 14 | eoghanlawless 15 | e0ne 16 | jdambly 17 | jnunyez 18 | josephdrichard 19 | jzding 20 | kenyis 21 | killianmuldoon 22 | kmabda 23 | lmilleri 24 | maiqueb 25 | martinkennelly 26 | michaeloreillyintel 27 | MikeSpreitzer 28 | mlguerrero12 29 | moshe010 30 | mukesh-dua 31 | nocturnalastro 32 | npwg-robot 33 | oshoval 34 | phoracek 35 | plwhite 36 | qinqon 37 | RamLavi 38 | rdavid 39 | rdower 40 | rkamudhan 41 | RossGLPT 42 | s1061123 43 | SchSeba 44 | seware 45 | sfblackl-intel 46 | sureshkrishnan 47 | szollin 48 | tliron 49 | ykulazhenkov 50 | zeeke 51 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Network Plumbing Working Group 2 | 3 | The Network Plumbing Working Group (NPWG) was formed at Kubecon NA '17 in Austin to initially work towards implementing 4 | a common standard addressing how one may attach multiple networks to pods in Kubernetes. Our work has culminated in a 5 | de-facto standard CRD. 6 | 7 | ## Meetings 8 | 9 | * Join us for our bi-weekly meeting at 9:30AM US Eastern Time on Thursday, opposite weeks from the SIG-Network meeting. You can find the connection information in the agenda document. 10 | * [Meeting notes and Agenda](https://docs.google.com/document/d/1oE93V3SgOGWJ4O1zeD1UmpeToa0ZiiO6LqRAmZBPFWM/edit) 11 | * [Meeting recordings](https://www.youtube.com/results?sp=CAI%253D&search_query=network+plumbing+wg): In youtube. 12 | 13 | ### Topic Specific meetings 14 | 15 | #### K8s Network & Resource Management 16 | 17 | Weekly, Monday and Tuesday on alternating weeks: 18 | 19 | - Time: 15:00 - 16:00 GMT / 10:00-11:00 ET / 07:00-08:00 PST every other Monday 20 | - Time: 14:00 - 15:00 GMT / 09:00-10:00 ET / 06:00-07:00 PST on every other Tuesday 21 | 22 | [Agenda and connection info](https://docs.google.com/document/d/1sJQMHbxZdeYJPgAWK1aSt6yzZ4K_8es7woVIrwinVwI/edit#) 23 | 24 | #### Additional Discussion (Currently on pause) 25 | 26 | [Paused until further notice] Every 2 weeks on Tuesday, 15:30-16:30 GMT 27 | [Agenda and connection info](https://www.google.com/url?q=https://docs.google.com/document/d/129FUXBHvKMOVwsvjgYzZX4CorsN_uJwHTdo8DXs1Tpk/edit%23&sa=D&source=calendar&ust=1607275227216000&usg=AOvVaw1FEnxaPipTtJRA0Db_m-OE) 28 | 29 | #### Multus CNI Maintainers Meeting 30 | 31 | Every 2 weeks on Thursday, 14:30-15:30 GMT 32 | [Agenda and connection info](https://www.google.com/url?q=https://docs.google.com/document/d/17-vkuoObBFBb6feXNA7tjTaKr-rs8ea0VTnqvlEdCv8/edit%23&sa=D&source=calendar&ust=1607275227216000&usg=AOvVaw39f1xzq2JtmpQUf5KEaZ5d) 33 | 34 | #### PTP Meeting 35 | 36 | Every week on Wednesday, 15:00-15:30 GMT 37 | [Agenda and connection info](https://docs.google.com/document/d/16NrFkjCTjX8ffNrkkLeLq9e8kO9-IrbkUdEskqU5gVE/edit?tab=t.0) 38 | 39 | ## Members and Maintainers 40 | 41 | * [Members](MEMBERS) 42 | * [GitHub Organization Owners](OWNERS) 43 | 44 | 45 | ## Working Items 46 | 47 | * Multi-Network CRD Specification 48 | * [Repositories](https://github.com/k8snetworkplumbingwg/multi-net-spec): Finalized version of the Multi-Network Specification. 49 | * [Working doc](https://docs.google.com/document/d/1Ny03h6IDVy_e_vmElOqR7UdTPAG_RNydhVE1Kx54kFQ/edit) 50 | * Multi-Network Reference Implementations 51 | * [Multus CNI](http://multus-cni.io) 52 | 53 | ## Contact 54 | 55 | * [Slack](https://join.slack.com/t/npwg-team/shared_invite/zt-1u2vmsn2b-tKdOokdPY73zn9B32JoAOg): Join #general channel to discuss multus-cni and other related topics. 56 | * [Mailing list](https://groups.google.com/forum/#!forum/network-plumbing-working-group) 57 | * [Open Community Issues/PRs](https://github.com/k8snetworkplumbingwg/community/issues) 58 | -------------------------------------------------------------------------------- /REPOSITORIES: -------------------------------------------------------------------------------- 1 | ## ACTIVE 2 | sriov-cni https://github.com/k8snetworkplumbingwg/sriov-cni 3 | multus-cni https://github.com/k8snetworkplumbingwg/multus-cni 4 | bond-cni https://github.com/k8snetworkplumbingwg/bond-cni 5 | sriovnet https://github.com/k8snetworkplumbingwg/sriovnet 6 | sriov-network-device-plugin https://github.com/k8snetworkplumbingwg/sriov-network-device-plugin 7 | ovs-cni https://github.com/k8snetworkplumbingwg/ovs-cni 8 | multi-net-spec https://github.com/k8snetworkplumbingwg/multi-net-spec 9 | network-attachment-definition-client https://github.com/k8snetworkplumbingwg/network-attachment-definition-client 10 | net-attach-def-admission-controller https://github.com/k8snetworkplumbingwg/net-attach-def-admission-controller 11 | community https://github.com/k8snetworkplumbingwg/community 12 | k8s-net-attach-def-controller https://github.com/k8snetworkplumbingwg/k8s-net-attach-def-controller 13 | reference-deployment https://github.com/k8snetworkplumbingwg/reference-deployment 14 | kubemacpool https://github.com/k8snetworkplumbingwg/kubemacpool 15 | whereabouts https://github.com/k8snetworkplumbingwg/whereabouts 16 | toc https://github.com/k8snetworkplumbingwg/toc 17 | network-resources-injector https://github.com/k8snetworkplumbingwg/network-resources-injector 18 | ib-sriov-cni https://github.com/k8snetworkplumbingwg/ib-sriov-cni 19 | net-service-controller https://github.com/k8snetworkplumbingwg/net-service-controller 20 | rdma-cni https://github.com/k8snetworkplumbingwg/rdma-cni 21 | helm-charts https://github.com/k8snetworkplumbingwg/helm-charts 22 | multusctl https://github.com/k8snetworkplumbingwg/multusctl 23 | multi-networkpolicy https://github.com/k8snetworkplumbingwg/multi-networkpolicy 24 | sriov-network-metrics-exporter https://github.com/k8snetworkplumbingwg/sriov-network-metrics-exporter 25 | multi-networkpolicy-iptables https://github.com/k8snetworkplumbingwg/multi-networkpolicy-iptables 26 | device-info-spec https://github.com/k8snetworkplumbingwg/device-info-spec 27 | govdpa https://github.com/k8snetworkplumbingwg/govdpa 28 | accelerated-bridge-cni https://github.com/k8snetworkplumbingwg/accelerated-bridge-cni 29 | sriov-network-operator https://github.com/k8snetworkplumbingwg/sriov-network-operator 30 | kubectl-multinet https://github.com/k8snetworkplumbingwg/kubectl-multinet 31 | resource-mgmt-utils https://github.com/k8snetworkplumbingwg/resource-mgmt-utils 32 | plugins https://github.com/k8snetworkplumbingwg/plugins 33 | multus-service https://github.com/k8snetworkplumbingwg/multus-service 34 | multi-networkpolicy-tc https://github.com/k8snetworkplumbingwg/multi-networkpolicy-tc 35 | multus-dynamic-networks-controller https://github.com/k8snetworkplumbingwg/multus-dynamic-networks-controller 36 | cni-log https://github.com/k8snetworkplumbingwg/cni-log 37 | net-ebpf-playground https://github.com/k8snetworkplumbingwg/net-ebpf-playground 38 | ptp-operator https://github.com/k8snetworkplumbingwg/ptp-operator 39 | linuxptp-daemon https://github.com/k8snetworkplumbingwg/linuxptp-daemon 40 | bridge-operator https://github.com/k8snetworkplumbingwg/bridge-operator 41 | ipamclaims https://github.com/k8snetworkplumbingwg/ipamclaims 42 | 43 | ## ARCHIVED 44 | -------------------------------------------------------------------------------- /GOVERNANCE.md: -------------------------------------------------------------------------------- 1 | # Network Plumbing Working Group Governance 2 | 3 | ## OVERVIEW 4 | The K8s Network Plumbing Working Group follows the example set out by the Kubernetes and wider CNCF communities. Governance of the NPWG is lightweight so that process doesn't impede contribution. 5 | 6 | The intention is to provide a common ground for GitHub software repositories under https://github.com/k8snetworkplumbingwg. These repositories encompass the work that's being done across the working group. As the group grows in size and as the stakeholders diversify, having a solid framework for contribution should benefit the group as a whole. 7 | 8 | Note: This document is adapted [from an original proposal](https://docs.google.com/document/d/1lIWOK-W6fb1VZiSjO1BoFUs0TmoVwgd4XuVc6mtJk2c). 9 | 10 | ## MISSION STATEMENT 11 | The Network Plumbing Working Group's goal is to advance vendor-neutral open source and open standards in regards to networking capabilities for workloads running in Kubernetes. This includes creation of specifications for technologies, the development & tooling of these vendor-neutral technologies, building reference implementations, creation of proof-of-concept technologies to help drive the discussion, and furthering the specifications and implementations of those specifications. As appropriate, these technologies should work towards integration into core technologies, such as Kubernetes. 12 | 13 | The Network Plumbing Working Group is responsible for maintaining and updating the specifications we have created, as well as maintenance of software that is created by members and maintainers of the Network Plumbing Working Group. 14 | 15 | ## GOVERNANCE 16 | 17 | ### Meetings and voting 18 | Meetings are held bi-weekly. The agenda document which contains time and connection details is [here](./README.md#meetings). 19 | 20 | For any action that requires a vote, quorum must be achieved. To achieve quorum, 3 or more members shall be available to vote, and there shall be no more than 50% representation among voters of members in employment of the same employer. In order to make changes to the governance document, there shall be 5 or more members available to vote and there shall be no more than 50% representation of members in employment of the same employer. 21 | 22 | An organization owner must be present to decide if there is quorum to make a decision. 23 | 24 | ### Project repositories 25 | Active and archived repositories are listed in [REPOSITORIES](REPOSITORIES). This file has the form: 26 | ```markdown 27 | ## ACTIVE REPOSITORIES 28 | repo-one http://link-to-repo-one.com 29 | repo-two http://link-to-repo-two.com 30 | 31 | ## ARCHIVED REPOSITORIES 32 | repo-three http://link-to-repo-three.com 33 | ... 34 | ``` 35 | 36 | ### Adding or archiving a repository 37 | To begin, donate, or archive a repository a proposal is made at the [NPWG community meeting](./README.md#meetings). If the group approves the change a PR will be made to the [REPOSITORIES](REPOSITORIES) file in the community repository. The PR will stay open until the next NPWG community meeting at which time it can be merged by another vote. This allows the wider community - including those who aren't able to attend the regular community meeting - to have their say on governance changes. Once the PR is merged it's the responsibility of an organization owner to reflect the changes in GitHub. This process is followed for adding, donating or archiving repositories. 38 | 39 | ### Process for accepting pull requests 40 | Pull requests should be approved by 2 or more maintainers employed by distinct employers before being merged. Maintainers may approve their own pull requests, however these pull requests must also be reviewed and approved by one or more other maintainers. 41 | 42 | ### Project roles 43 | There are four defined roles in the NPWG - two at the organization level and two at the repository level. 44 | 45 | #### Organization owner 46 | This is an owner of the NPWG organization as listed in the community [OWNERS](OWNERS) file. These people are responsible for the long term health of the project and day-to-day administrative tasks. An organization owner must be present at the NPWG community meeting to hold votes that require quorum - including those on changing OWNERS files and on adding or archiving repositories. 47 | 48 | The group of all owners should not have more than 50% representation by a single organization. Owners are responsible for creating repositories as well as setting GitHub roles for maintainers. Owners must not delete, rename, make private, or transfer ownership of any repositories outside of the GitHub organization, nor take any other disruptive action without a vote during a bi-weekly meeting. 49 | 50 | #### Organization member 51 | Anyone is free to contribute to the Network Plumbing Working Group at any time. Contribution to the working group happens across a number of vectors, which include but are not limited to: The Network Plumbing Working Group's Google Groups email list, bi-weekly meetings and GitHub. Any member of the group is invited to join the discussion, and to submit patches to GitHub. 52 | 53 | A "member" of the Network Plumbing Working Group has the right to vote given any decision the group makes. 54 | 55 | Members shall be documented in the community repository. 56 | 57 | #### Repository admin 58 | This is a person with `Admin` rights in a GitHub repository. They are responsible for the long term health of a repository. They are also responsible for periodic administrative tasks such as reflecting changes in OWNERS file to the GitHub settings of a repository. 59 | 60 | #### Repository maintainer 61 | This is a person with `Maintain` rights in a GitHub repository. They are responsible for the day-to-day health of a repository. Tasks expected from maintainers include issue triage, code reviews, PR approvals and attending relevant community meetings. 62 | 63 | ### Updating project roles 64 | Adding a member can be done by opening a PR to [MEMBERS](./MEMBERS) in this repo. Other changes to project roles will be proposed at the [NPWG community meeting](./README.md#meetings). If the group approves the change a PR will be made to the OWNERS file of the relevant repository. The PR will stay open until the next NPWG community meeting at which time it can be merged by another vote. This allows the wider community - including those who aren't able to attend the regular community meeting - to have their say on governance changes. Once the PR is merged it's the responsibility of a repository admin or organization owner to reflect the changes in the GitHub project settings of the relevant repository. This process is followed for adding, updating or removing members from the project roles they hold. 65 | 66 | ### OWNERS file structure 67 | The OWNERS file in this repository has the form: 68 | 69 | ```markdown 70 | # OWNERS 71 | owner-one 72 | ... 73 | ``` 74 | 75 | Other repositories under the NPWG have OWNERS files of the form: 76 | 77 | ```markdown 78 | ## ADMINS: People who control settings for the repo. 79 | admin-one 80 | ... 81 | 82 | ## Maintainers: People who can merge code in this repo. 83 | maintainer-one 84 | maintainer-two 85 | ... 86 | ``` -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | 178 | APPENDIX: How to apply the Apache License to your work. 179 | 180 | To apply the Apache License to your work, attach the following 181 | boilerplate notice, with the fields enclosed by brackets "[]" 182 | replaced with your own identifying information. (Don't include 183 | the brackets!) The text should be enclosed in the appropriate 184 | comment syntax for the file format. We also recommend that a 185 | file or class name and description of purpose be included on the 186 | same "printed page" as the copyright notice for easier 187 | identification within third-party archives. 188 | 189 | Copyright [yyyy] [name of copyright owner] 190 | 191 | Licensed under the Apache License, Version 2.0 (the "License"); 192 | you may not use this file except in compliance with the License. 193 | You may obtain a copy of the License at 194 | 195 | http://www.apache.org/licenses/LICENSE-2.0 196 | 197 | Unless required by applicable law or agreed to in writing, software 198 | distributed under the License is distributed on an "AS IS" BASIS, 199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 200 | See the License for the specific language governing permissions and 201 | limitations under the License. 202 | --------------------------------------------------------------------------------