构建 Ansible 清单:主机分组、变量继承与多来源合并

原文:Ansible 社区文档团队,How to build your inventory。本文为中文翻译整理,按 2026 年 10 月 5 日读取的 latest 文档核对;保留各节技术内容,合并重复语法示例,并明确标注编辑补充。上游文档仓库提供 GNU GPL v3 许可。译文与补充修改日期:2026-10-05。

Ansible 通过 inventory(清单)确定基础设施中的受管节点,也就是主机。清单由一个或多个来源组合而成;来源可以是命令行传入的主机名、静态文件、目录、动态脚本,或库存插件支持的服务。清单不仅列出主机,也定义主机对应的变量和组。建立清单后,再用主机模式选择自动化任务的目标。

最简单的形式是一个列出主机与组的文件,默认位置为 /etc/ansible/hosts。使用 -i <路径或表达式> 或配置系统可以指定其他来源。规模增长后,可以由插件动态查询云资源,也可以同时使用静态与动态来源,或将多个来源放进同一个目录。

Ansible 清单从多个来源聚合主机与组,再按 all、父组、子组、主机的优先级合并变量,最后选择目标主机。
清单读取、变量合并和目标选择的关系。未完纪原创技术示意图。

1. 用 INI 或 YAML 描述主机和组

支持哪些格式取决于已启用的 inventory 插件。INI 与 YAML 是最常用的内置格式。INI 中方括号内的名称是组名,组名应遵循合法变量名的命名规则:

mail.example.com

[webservers]
foo.example.com
bar.example.com

[dbservers]
one.example.com
two.example.com
three.example.com

同一份清单用 YAML 可以写成:

ungrouped:
  hosts:
    mail.example.com:
webservers:
  hosts:
    foo.example.com:
    bar.example.com:
dbservers:
  hosts:
    one.example.com:
    two.example.com:
    three.example.com:

即使没有显式定义组,Ansible 也会创建 all 和 ungrouped:前者包含所有主机,后者包含不属于其他组的主机。因此,每台主机至少属于两个组:all 加 ungrouped,或 all 加一个自定义组。上例中 mail.example.com 属于 all 和 ungrouped,two.example.com 属于 all 和 dbservers。默认组可能是隐式存在的,不一定出现在 group_names 等列表中。

一台主机可以同时属于多个组。实际维护时可按三个维度分组:做什么(web、数据库、应用栈或微服务)、在哪里(数据中心、地区,方便关联 DNS 或存储)、处于哪个阶段(prod、test 等,减少误操作环境的机会)。例如在前述 YAML 之外增加:

east:
  hosts:
    foo.example.com:
    one.example.com:
    two.example.com:
west:
  hosts:
    bar.example.com:
    three.example.com:
prod:
  hosts:
    foo.example.com:
    one.example.com:
    two.example.com:
test:
  hosts:
    bar.example.com:
    three.example.com:

此时 one.example.com 同时属于 dbservers、east、prod。组的含义是同一台主机的不同分类,而不是复制出多台主机。

2. 用父子组和范围减少重复

已有 atlanta_prod、denver_prod 等组时,可建立 production 父组。以后只需调整子组中的主机,父组成员会相应改变。INI 使用 :children,YAML 使用 children:。例如把上节的 prod/test 改成以下定义,即可重用地区分组:

[prod:children]
east

[test:children]
west
prod:
  children:
    east:
test:
  children:
    west:

子组中的主机自动成为父组成员;一个组可以有多个父组和子组,但不能形成环。同一主机可以属于多个组,运行时仍只处理该主机的一个实例。主机和组的标识在整份清单中是全局的,在不同分支中重复定义不会创建独立副本,而会追加信息,或由后来的定义覆盖冲突值。

INI 和 YAML 插件都支持主机范围。下面两种写法都表示 www01 到 www50,且端点包含在范围内:

[webservers]
www[01:50].example.com
webservers:
  hosts:
    www[01:50].example.com:

数字范围可以指定步长。www[01:50:2].example.com 展开为 www01、www03……www49,不包含 www00、www02 或 www50。数字是否保留前导零由书写方式决定。字母范围也可使用,例如:

[databases]
db-[a:f].example.com

3. 合并多个来源,控制读取顺序

命令行可以重复使用 -i,也可以通过 ANSIBLE_INVENTORY 环境变量或 ansible.cfg 的 DEFAULT_HOST_LIST 指定多个来源。例如原文以一次任务同时读取 staging 和 production:

ansible-playbook get_logs.yml -i staging -i production

编辑提醒:这条命令会运行 playbook,并把两个环境都纳入可匹配的目标范围。文件名 get_logs.yml 不保证任务只读;使用前应审查其实际内容与主机匹配结果。

当一份文件过长,或多个团队需要各自维护来源时,可以按团队或项目分文件,再把目录作为统一来源:

inventory/
  openstack.yml          # OpenStack inventory 插件配置
  dynamic-inventory.py   # 动态清单脚本
  on-prem                # 静态主机与组
  parent-groups          # 静态父子组定义
ansible-playbook example.yml -i inventory

这些来源也可单独使用,或只选其中一部分。Ansible 会聚合目录内可识别的内容;默认忽略某些目录和扩展名,规则由 INVENTORY_IGNORE_PATTERNS 与 INVENTORY_IGNORE_EXTS 调整,也可在 ansible.cfg 中配置整个目录。

目录中的文件按名称的字母顺序从上层开始读取;显式传入的来源按传入顺序读取。Ansible 遇到主机、组和变量时就建立定义,必要时最后补上 all 与 ungrouped。某些插件要求先出现被引用的组或主机;YAML 与 INI 插件在处理完每个来源时会丢弃没有关联主机的空组,因此父子组跨文件定义时要核对顺序,否则可能解析失败。同一变量重复定义时,后来的定义会覆盖前面的值。

4. 主机变量、连接参数与别名

与某一台主机相关的设置,可以直接写在 inventory 中。以下 INI 与 YAML 等价:

[atlanta]
host1 http_port=80 maxRequestsPerChild=808
host2 http_port=303 maxRequestsPerChild=909
atlanta:
  hosts:
    host1:
      http_port: 80
      maxRequestsPerChild: 808
    host2:
      http_port: 303
      maxRequestsPerChild: 909

非标准 SSH 端口也适合作为主机变量。原文给出 badwolf.example.com:5309 的简写,以及控制 connection、shell、become 插件的连接变量:

[targets]
localhost              ansible_connection=local
other1.example.com     ansible_connection=ssh ansible_user=myuser
other2.example.com     ansible_connection=ssh ansible_user=myotheruser

inventory_hostname 是清单中主机的唯一标识,可以是 IP、域名,也可以是短别名。实际连接地址和端口可分别指定:

jumper ansible_port=5555 ansible_host=192.0.2.50
targets:
  hosts:
    jumper:
      ansible_port: 5555
      ansible_host: 192.0.2.50

针对 jumper 的任务会连接 192.0.2.50 的 5555 端口。也可以定义两个别名指向同一地址:

jumper1 ansible_port=5555 ansible_host=192.0.2.50
jumper2 ansible_port=5555 ansible_host=192.0.2.50

此时 Ansible 把它们视为不同的清单标识,任务可能并行落到同一台机器。对更新文件、部署服务等操作,应避免无意创建这样的重复目标。

5. INI 变量的类型取决于位置

在主机所在行使用 key=value 时,INI 插件会尝试把值解析为 Python 字面量,例如字符串、数字、元组、列表、字典、布尔值或 None。一行可以有多个参数,含空白的值需要引号,具体遵循 Python shlex 的解析规则。

在 :vars 段内,值则按字符串处理。例如 var=FALSE 得到的是字符串 FALSE;这里每行只接受一个赋值,等号后其余内容都属于该值。任务若依赖特定类型,应在消费变量时用过滤器显式转换,不要依赖 INI 中看起来像布尔值或数字的写法。YAML 对变量值的处理更一致,适合避免此类歧义。

6. 组变量、继承和分文件存储

一组主机共享的值可以放入组变量:

[atlanta]
host1
host2

[atlanta:vars]
ntp_server=ntp.atlanta.example.com
proxy=proxy.atlanta.example.com
atlanta:
  hosts:
    host1:
    host2:
  vars:
    ntp_server: ntp.atlanta.example.com
    proxy: proxy.atlanta.example.com

执行前,Ansible 会把清单变量展开到每台主机。如果主机属于多个组,会读取所有相关组变量,并按合并规则解决冲突。父组也能定义变量,子组同名变量的优先级更高。原文的嵌套示例如下;其中 self_destruct_countdown、escape_pods 只是虚构变量名,没有对应的执行动作:

[atlanta]
host1
host2

[raleigh]
host2
host3

[southeast:children]
atlanta
raleigh

[southeast:vars]
some_server=foo.southeast.example.com
halon_system_timeout=30
self_destruct_countdown=60
escape_pods=2

[usa:children]
southeast
northeast
southwest
northwest
usa:
  children:
    southeast:
      children:
        atlanta:
          hosts:
            host1:
            host2:
        raleigh:
          hosts:
            host2:
            host3:
      vars:
        some_server: foo.southeast.example.com
        halon_system_timeout: 30
        self_destruct_countdown: 60
        escape_pods: 2
    northeast:
    northwest:
    southwest:

直接把变量写在清单中适合入门;分开维护通常更稳妥。默认的 host_group_vars 变量插件会从 inventory 或 playbook 相对目录加载 host_vars、group_vars。变量文件使用 YAML 语法,扩展名可以是 .yml、.yaml、.json,也可以没有扩展名,并可承载列表与字典。若 /etc/ansible/hosts 中的 foosball 属于 raleigh 和 webservers,则相关路径为:

/etc/ansible/group_vars/raleigh
/etc/ansible/group_vars/webservers
/etc/ansible/host_vars/foosball

例如 raleigh 文件可以写:

---
ntp_server: acme.example.org
database_server: storage.example.org

也可将组或主机名作为目录,Ansible 会按字典序读取其中的文件:

/etc/ansible/group_vars/raleigh/db_settings
/etc/ansible/group_vars/raleigh/cluster_settings

这适合把大文件拆开,也便于只用 Ansible Vault 加密其中的敏感变量。ansible-playbook 会考虑 playbook 目录中的这些变量目录;ansible、ansible-console 等没有 playbook 路径的命令,可用 --playbook-dir 指定。若清单目录和 playbook 目录同时提供变量,playbook 相对目录的值覆盖清单相对目录的值。清单及变量文件应共同纳入版本控制。

7. 清单变量如何合并

一个 play 开始前,Ansible 将变量合并到具体主机。运行任务时主要关注主机和任务,组本身不再作为独立变量容器参与执行。默认行为是覆盖同名变量,包括组或主机定义的变量;字典行为还受 DEFAULT_HASH_BEHAVIOUR 影响。以下仅为 inventory 实体之间的优先级,从低到高排列,不能代替 Ansible 所有变量来源的完整优先级:

  1. all 组;
  2. 父组;
  3. 子组;
  4. 主机。

同一父子层级的组默认按字母顺序合并,后加载组覆盖先加载组。例如 b_group 会覆盖 a_group 的同名变量。可以在清单来源中设置 ansible_group_priority 调整同级组顺序;默认值为 1,值越大越晚合并:

a_group:
  vars:
    testvar: a
    ansible_group_priority: 10
b_group:
  vars:
    testvar: b

若主机同时属于这两个组,结果为 testvar=a。这个优先级必须写在 inventory 来源中,不能放入 group_vars,因为加载 group_vars 本身就需要使用该值。

多个来源的合并顺序同样影响结果:若 staging 的 all 组定义 myvar=1,而 production 定义 myvar=2,-i staging -i production 得到 2,反向传入得到 1。目录内可用文件名前缀控制:

inventory/
  01-openstack.yml
  02-dynamic-inventory.py
  03-static-inventory
  group_vars/
    all.yml

在三个来源分别给 all.myvar 赋值为 1、2、3 的情况下,第三个来源的 3 最后生效;其他更高优先级变量来源仍可能覆盖它。完整规则见 变量优先级文档。

8. 控制连接、权限提升与远端环境

默认 SSH 插件不能提供交互通道,让用户手动输入解密 SSH 密钥的口令;原文建议使用 ssh-agent。以下是原文列出的行为参数:

参数 用途与边界
ansible_connection 连接插件名称,默认 ssh;可用 ssh、paramiko 或其他插件。
ansible_host 与清单别名不同的实际域名或 IP。不要让其依赖 inventory_hostname;确有类似需要时,原文建议 inventory_hostname_short,以兼容委派。
ansible_port / ansible_user 连接端口及登录用户名;SSH 默认端口 22。
ansible_password 连接认证密码。不得明文存储,应使用 Vault。
ansible_ssh_private_key_file SSH 私钥路径,可用于多密钥或不使用 ssh-agent 的场景。
ansible_ssh_common_args 追加到 sftp、scp、ssh 的共同参数,可用于配置 ProxyCommand。
ansible_sftp_extra_args / ansible_scp_extra_args / ansible_ssh_extra_args 分别追加到相应命令的参数。
ansible_ssh_pipelining 是否启用 SSH pipelining,可覆盖 ansible.cfg 中的设置。
ansible_ssh_executable 覆盖系统 SSH 可执行程序或 ssh_connection 中的 ssh_executable;原文标记为 2.2 加入。
ansible_become 控制权限提升;原文列出历史 ansible_sudo / ansible_su 对应关系。
ansible_become_method / ansible_become_user 权限提升插件及提升后的用户。
ansible_become_password 权限提升密码;不得明文存储,应使用 Vault。
ansible_become_exe / ansible_become_flags 权限提升程序及其参数;flags 也可在 ansible.cfg 的 privilege_escalation 节设置。
ansible_shell_type 目标 Shell 语法类型;默认按 sh 风格生成命令。只有 shell_executable 已改为非 Bourne 兼容 Shell 时才考虑修改。
ansible_python_interpreter 指定远端 Python 路径,用于多解释器或特殊安装路径。
ansible_*_interpreter 其他语言解释器的路径,如 Ruby、Perl,替换相应模块的 shebang。
ansible_shell_executable 远端执行使用的 Shell,覆盖 ansible.cfg 的 executable,默认 /bin/sh;仅在 /bin/sh 不可用或无法经 sudo 运行等必要场景修改。原文标记为 2.1 加入。
some_host         ansible_port=2222 ansible_user=manager
aws_host          ansible_ssh_private_key_file=/home/example/.ssh/aws.pem
freebsd_host      ansible_python_interpreter=/usr/local/bin/python
ruby_module_host  ansible_ruby_interpreter=/usr/bin/ruby.1.9.3

版本注:原文解释 interpreter 时仍提到 Python 2.X、python2.6,示例也含 Ruby 1.9.3。这些属于历史说明,不是当前支持版本建议。应按已安装 ansible-core 的支持矩阵选择远端解释器,不能照抄旧路径。SSH 也不是唯一传输方式,设置 ansible_connection=<连接插件名称> 即可选择其他受支持插件。

9. 按环境、功能与地点组织实际清单

多环境管理时,一份 inventory 只放一个环境的主机,可以减少把测试任务误发到其他环境的机会。例如:

# inventory_test
[dbservers]
db01.test.example.com
db02.test.example.com

[appservers]
app01.test.example.com
app02.test.example.com
app03.test.example.com
# inventory_staging
[dbservers]
db01.staging.example.com
db02.staging.example.com

[appservers]
app01.staging.example.com
app02.staging.example.com
app03.staging.example.com

针对测试环境中的应用服务器运行 site.yml,原文使用:

ansible-playbook -i inventory_test -l appservers site.yml

按功能分组可以让规则只作用于数据库服务器。原文的 iptables 示例为:

- hosts: dbservers
  tasks:
    - name: Allow access from 10.0.0.1
      ansible.builtin.iptables:
        chain: INPUT
        jump: ACCEPT
        source: 10.0.0.1

静态审查:该任务会修改防火墙,不是只读检查;它没有限定协议、端口或目的地址,表达的是允许指定源地址的宽泛规则。实际开放范围还取决于规则位置与已有规则,不能作为通用生产防火墙方案。应按业务收窄规则并保留可靠的回退通道;本文未执行该任务。

按地点分组则可以让同一数据中心中的不同角色一起执行任务:

[dc1]
db01.test.example.com
app01.test.example.com

[dc2]
db02.test.example.com

这些维度通常会同时使用:今天更新某个数据中心的所有节点,明天更新所有地区的应用服务器。分组表达结构,最终操作范围仍由选用的 inventory、playbook 的 hosts 和命令行限制共同决定。

10. 编辑核查与进一步阅读

本文只做静态审核,没有连接任何主机或运行 Ansible。主要风险是多来源意外扩大目标、同地址多别名导致并发写入、变量覆盖改变连接身份、明文密码,以及将可执行的动态 inventory 或 ProxyCommand 当成普通数据。示例没有发现真实硬编码秘密;这不等于代码或依赖不存在其他漏洞。清单来源、插件、Shell 参数应视为可信配置,敏感信息交给 Vault,并限制解密权限。

原文还指向 Inventory 插件、动态清单、临时命令、Playbook 与 完整目录示例。本文合并了重复的语法展示,补充安全和历史版本标记;没有把这些扩展链接当作已执行或已验证的环境。

文档许可与修改说明

原文:Ansible 社区文档贡献者。本文于2026-10-05翻译整理并补充静态风险说明,按上游文档仓库 GNU GPL v3 许可分发。原始文档及可编辑源文件;上游许可。以下保留完整许可证。

                    GNU GENERAL PUBLIC LICENSE
                       Version 3, 29 June 2007

 Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
 Everyone is permitted to copy and distribute verbatim copies
 of this license document, but changing it is not allowed.

                            Preamble

  The GNU General Public License is a free, copyleft license for
software and other kinds of works.

  The licenses for most software and other practical works are designed
to take away your freedom to share and change the works.  By contrast,
the GNU General Public License is intended to guarantee your freedom to
share and change all versions of a program--to make sure it remains free
software for all its users.  We, the Free Software Foundation, use the
GNU General Public License for most of our software; it applies also to
any other work released this way by its authors.  You can apply it to
your programs, too.

  When we speak of free software, we are referring to freedom, not
price.  Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
them if you wish), that you receive source code or can get it if you
want it, that you can change the software or use pieces of it in new
free programs, and that you know you can do these things.

  To protect your rights, we need to prevent others from denying you
these rights or asking you to surrender the rights.  Therefore, you have
certain responsibilities if you distribute copies of the software, or if
you modify it: responsibilities to respect the freedom of others.

  For example, if you distribute copies of such a program, whether
gratis or for a fee, you must pass on to the recipients the same
freedoms that you received.  You must make sure that they, too, receive
or can get the source code.  And you must show them these terms so they
know their rights.

  Developers that use the GNU GPL protect your rights with two steps:
(1) assert copyright on the software, and (2) offer you this License
giving you legal permission to copy, distribute and/or modify it.

  For the developers' and authors' protection, the GPL clearly explains
that there is no warranty for this free software.  For both users' and
authors' sake, the GPL requires that modified versions be marked as
changed, so that their problems will not be attributed erroneously to
authors of previous versions.

  Some devices are designed to deny users access to install or run
modified versions of the software inside them, although the manufacturer
can do so.  This is fundamentally incompatible with the aim of
protecting users' freedom to change the software.  The systematic
pattern of such abuse occurs in the area of products for individuals to
use, which is precisely where it is most unacceptable.  Therefore, we
have designed this version of the GPL to prohibit the practice for those
products.  If such problems arise substantially in other domains, we
stand ready to extend this provision to those domains in future versions
of the GPL, as needed to protect the freedom of users.

  Finally, every program is threatened constantly by software patents.
States should not allow patents to restrict development and use of
software on general-purpose computers, but in those that do, we wish to
avoid the special danger that patents applied to a free program could
make it effectively proprietary.  To prevent this, the GPL assures that
patents cannot be used to render the program non-free.

  The precise terms and conditions for copying, distribution and
modification follow.

                       TERMS AND CONDITIONS

  0. Definitions.

  "This License" refers to version 3 of the GNU General Public License.

  "Copyright" also means copyright-like laws that apply to other kinds of
works, such as semiconductor masks.

  "The Program" refers to any copyrightable work licensed under this
License.  Each licensee is addressed as "you".  "Licensees" and
"recipients" may be individuals or organizations.

  To "modify" a work means to copy from or adapt all or part of the work
in a fashion requiring copyright permission, other than the making of an
exact copy.  The resulting work is called a "modified version" of the
earlier work or a work "based on" the earlier work.

  A "covered work" means either the unmodified Program or a work based
on the Program.

  To "propagate" a work means to do anything with it that, without
permission, would make you directly or secondarily liable for
infringement under applicable copyright law, except executing it on a
computer or modifying a private copy.  Propagation includes copying,
distribution (with or without modification), making available to the
public, and in some countries other activities as well.

  To "convey" a work means any kind of propagation that enables other
parties to make or receive copies.  Mere interaction with a user through
a computer network, with no transfer of a copy, is not conveying.

  An interactive user interface displays "Appropriate Legal Notices"
to the extent that it includes a convenient and prominently visible
feature that (1) displays an appropriate copyright notice, and (2)
tells the user that there is no warranty for the work (except to the
extent that warranties are provided), that licensees may convey the
work under this License, and how to view a copy of this License.  If
the interface presents a list of user commands or options, such as a
menu, a prominent item in the list meets this criterion.

  1. Source Code.

  The "source code" for a work means the preferred form of the work
for making modifications to it.  "Object code" means any non-source
form of a work.

  A "Standard Interface" means an interface that either is an official
standard defined by a recognized standards body, or, in the case of
interfaces specified for a particular programming language, one that
is widely used among developers working in that language.

  The "System Libraries" of an executable work include anything, other
than the work as a whole, that (a) is included in the normal form of
packaging a Major Component, but which is not part of that Major
Component, and (b) serves only to enable use of the work with that
Major Component, or to implement a Standard Interface for which an
implementation is available to the public in source code form.  A
"Major Component", in this context, means a major essential component
(kernel, window system, and so on) of the specific operating system
(if any) on which the executable work runs, or a compiler used to
produce the work, or an object code interpreter used to run it.

  The "Corresponding Source" for a work in object code form means all
the source code needed to generate, install, and (for an executable
work) run the object code and to modify the work, including scripts to
control those activities.  However, it does not include the work's
System Libraries, or general-purpose tools or generally available free
programs which are used unmodified in performing those activities but
which are not part of the work.  For example, Corresponding Source
includes interface definition files associated with source files for
the work, and the source code for shared libraries and dynamically
linked subprograms that the work is specifically designed to require,
such as by intimate data communication or control flow between those
subprograms and other parts of the work.

  The Corresponding Source need not include anything that users
can regenerate automatically from other parts of the Corresponding
Source.

  The Corresponding Source for a work in source code form is that
same work.

  2. Basic Permissions.

  All rights granted under this License are granted for the term of
copyright on the Program, and are irrevocable provided the stated
conditions are met.  This License explicitly affirms your unlimited
permission to run the unmodified Program.  The output from running a
covered work is covered by this License only if the output, given its
content, constitutes a covered work.  This License acknowledges your
rights of fair use or other equivalent, as provided by copyright law.

  You may make, run and propagate covered works that you do not
convey, without conditions so long as your license otherwise remains
in force.  You may convey covered works to others for the sole purpose
of having them make modifications exclusively for you, or provide you
with facilities for running those works, provided that you comply with
the terms of this License in conveying all material for which you do
not control copyright.  Those thus making or running the covered works
for you must do so exclusively on your behalf, under your direction
and control, on terms that prohibit them from making any copies of
your copyrighted material outside their relationship with you.

  Conveying under any other circumstances is permitted solely under
the conditions stated below.  Sublicensing is not allowed; section 10
makes it unnecessary.

  3. Protecting Users' Legal Rights From Anti-Circumvention Law.

  No covered work shall be deemed part of an effective technological
measure under any applicable law fulfilling obligations under article
11 of the WIPO copyright treaty adopted on 20 December 1996, or
similar laws prohibiting or restricting circumvention of such
measures.

  When you convey a covered work, you waive any legal power to forbid
circumvention of technological measures to the extent such circumvention
is effected by exercising rights under this License with respect to
the covered work, and you disclaim any intention to limit operation or
modification of the work as a means of enforcing, against the work's
users, your or third parties' legal rights to forbid circumvention of
technological measures.

  4. Conveying Verbatim Copies.

  You may convey verbatim copies of the Program's source code as you
receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice;
keep intact all notices stating that this License and any
non-permissive terms added in accord with section 7 apply to the code;
keep intact all notices of the absence of any warranty; and give all
recipients a copy of this License along with the Program.

  You may charge any price or no price for each copy that you convey,
and you may offer support or warranty protection for a fee.

  5. Conveying Modified Source Versions.

  You may convey a work based on the Program, or the modifications to
produce it from the Program, in the form of source code under the
terms of section 4, provided that you also meet all of these conditions:

    a) The work must carry prominent notices stating that you modified
    it, and giving a relevant date.

    b) The work must carry prominent notices stating that it is
    released under this License and any conditions added under section
    7.  This requirement modifies the requirement in section 4 to
    "keep intact all notices".

    c) You must license the entire work, as a whole, under this
    License to anyone who comes into possession of a copy.  This
    License will therefore apply, along with any applicable section 7
    additional terms, to the whole of the work, and all its parts,
    regardless of how they are packaged.  This License gives no
    permission to license the work in any other way, but it does not
    invalidate such permission if you have separately received it.

    d) If the work has interactive user interfaces, each must display
    Appropriate Legal Notices; however, if the Program has interactive
    interfaces that do not display Appropriate Legal Notices, your
    work need not make them do so.

  A compilation of a covered work with other separate and independent
works, which are not by their nature extensions of the covered work,
and which are not combined with it such as to form a larger program,
in or on a volume of a storage or distribution medium, is called an
"aggregate" if the compilation and its resulting copyright are not
used to limit the access or legal rights of the compilation's users
beyond what the individual works permit.  Inclusion of a covered work
in an aggregate does not cause this License to apply to the other
parts of the aggregate.

  6. Conveying Non-Source Forms.

  You may convey a covered work in object code form under the terms
of sections 4 and 5, provided that you also convey the
machine-readable Corresponding Source under the terms of this License,
in one of these ways:

    a) Convey the object code in, or embodied in, a physical product
    (including a physical distribution medium), accompanied by the
    Corresponding Source fixed on a durable physical medium
    customarily used for software interchange.

    b) Convey the object code in, or embodied in, a physical product
    (including a physical distribution medium), accompanied by a
    written offer, valid for at least three years and valid for as
    long as you offer spare parts or customer support for that product
    model, to give anyone who possesses the object code either (1) a
    copy of the Corresponding Source for all the software in the
    product that is covered by this License, on a durable physical
    medium customarily used for software interchange, for a price no
    more than your reasonable cost of physically performing this
    conveying of source, or (2) access to copy the
    Corresponding Source from a network server at no charge.

    c) Convey individual copies of the object code with a copy of the
    written offer to provide the Corresponding Source.  This
    alternative is allowed only occasionally and noncommercially, and
    only if you received the object code with such an offer, in accord
    with subsection 6b.

    d) Convey the object code by offering access from a designated
    place (gratis or for a charge), and offer equivalent access to the
    Corresponding Source in the same way through the same place at no
    further charge.  You need not require recipients to copy the
    Corresponding Source along with the object code.  If the place to
    copy the object code is a network server, the Corresponding Source
    may be on a different server (operated by you or a third party)
    that supports equivalent copying facilities, provided you maintain
    clear directions next to the object code saying where to find the
    Corresponding Source.  Regardless of what server hosts the
    Corresponding Source, you remain obligated to ensure that it is
    available for as long as needed to satisfy these requirements.

    e) Convey the object code using peer-to-peer transmission, provided
    you inform other peers where the object code and Corresponding
    Source of the work are being offered to the general public at no
    charge under subsection 6d.

  A separable portion of the object code, whose source code is excluded
from the Corresponding Source as a System Library, need not be
included in conveying the object code work.

  A "User Product" is either (1) a "consumer product", which means any
tangible personal property which is normally used for personal, family,
or household purposes, or (2) anything designed or sold for incorporation
into a dwelling.  In determining whether a product is a consumer product,
doubtful cases shall be resolved in favor of coverage.  For a particular
product received by a particular user, "normally used" refers to a
typical or common use of that class of product, regardless of the status
of the particular user or of the way in which the particular user
actually uses, or expects or is expected to use, the product.  A product
is a consumer product regardless of whether the product has substantial
commercial, industrial or non-consumer uses, unless such uses represent
the only significant mode of use of the product.

  "Installation Information" for a User Product means any methods,
procedures, authorization keys, or other information required to install
and execute modified versions of a covered work in that User Product from
a modified version of its Corresponding Source.  The information must
suffice to ensure that the continued functioning of the modified object
code is in no case prevented or interfered with solely because
modification has been made.

  If you convey an object code work under this section in, or with, or
specifically for use in, a User Product, and the conveying occurs as
part of a transaction in which the right of possession and use of the
User Product is transferred to the recipient in perpetuity or for a
fixed term (regardless of how the transaction is characterized), the
Corresponding Source conveyed under this section must be accompanied
by the Installation Information.  But this requirement does not apply
if neither you nor any third party retains the ability to install
modified object code on the User Product (for example, the work has
been installed in ROM).

  The requirement to provide Installation Information does not include a
requirement to continue to provide support service, warranty, or updates
for a work that has been modified or installed by the recipient, or for
the User Product in which it has been modified or installed.  Access to a
network may be denied when the modification itself materially and
adversely affects the operation of the network or violates the rules and
protocols for communication across the network.

  Corresponding Source conveyed, and Installation Information provided,
in accord with this section must be in a format that is publicly
documented (and with an implementation available to the public in
source code form), and must require no special password or key for
unpacking, reading or copying.

  7. Additional Terms.

  "Additional permissions" are terms that supplement the terms of this
License by making exceptions from one or more of its conditions.
Additional permissions that are applicable to the entire Program shall
be treated as though they were included in this License, to the extent
that they are valid under applicable law.  If additional permissions
apply only to part of the Program, that part may be used separately
under those permissions, but the entire Program remains governed by
this License without regard to the additional permissions.

  When you convey a copy of a covered work, you may at your option
remove any additional permissions from that copy, or from any part of
it.  (Additional permissions may be written to require their own
removal in certain cases when you modify the work.)  You may place
additional permissions on material, added by you to a covered work,
for which you have or can give appropriate copyright permission.

  Notwithstanding any other provision of this License, for material you
add to a covered work, you may (if authorized by the copyright holders of
that material) supplement the terms of this License with terms:

    a) Disclaiming warranty or limiting liability differently from the
    terms of sections 15 and 16 of this License; or

    b) Requiring preservation of specified reasonable legal notices or
    author attributions in that material or in the Appropriate Legal
    Notices displayed by works containing it; or

    c) Prohibiting misrepresentation of the origin of that material, or
    requiring that modified versions of such material be marked in
    reasonable ways as different from the original version; or

    d) Limiting the use for publicity purposes of names of licensors or
    authors of the material; or

    e) Declining to grant rights under trademark law for use of some
    trade names, trademarks, or service marks; or

    f) Requiring indemnification of licensors and authors of that
    material by anyone who conveys the material (or modified versions of
    it) with contractual assumptions of liability to the recipient, for
    any liability that these contractual assumptions directly impose on
    those licensors and authors.

  All other non-permissive additional terms are considered "further
restrictions" within the meaning of section 10.  If the Program as you
received it, or any part of it, contains a notice stating that it is
governed by this License along with a term that is a further
restriction, you may remove that term.  If a license document contains
a further restriction but permits relicensing or conveying under this
License, you may add to a covered work material governed by the terms
of that license document, provided that the further restriction does
not survive such relicensing or conveying.

  If you add terms to a covered work in accord with this section, you
must place, in the relevant source files, a statement of the
additional terms that apply to those files, or a notice indicating
where to find the applicable terms.

  Additional terms, permissive or non-permissive, may be stated in the
form of a separately written license, or stated as exceptions;
the above requirements apply either way.

  8. Termination.

  You may not propagate or modify a covered work except as expressly
provided under this License.  Any attempt otherwise to propagate or
modify it is void, and will automatically terminate your rights under
this License (including any patent licenses granted under the third
paragraph of section 11).

  However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
provisionally, unless and until the copyright holder explicitly and
finally terminates your license, and (b) permanently, if the copyright
holder fails to notify you of the violation by some reasonable means
prior to 60 days after the cessation.

  Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.

  Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License.  If your rights have been terminated and not permanently
reinstated, you do not qualify to receive new licenses for the same
material under section 10.

  9. Acceptance Not Required for Having Copies.

  You are not required to accept this License in order to receive or
run a copy of the Program.  Ancillary propagation of a covered work
occurring solely as a consequence of using peer-to-peer transmission
to receive a copy likewise does not require acceptance.  However,
nothing other than this License grants you permission to propagate or
modify any covered work.  These actions infringe copyright if you do
not accept this License.  Therefore, by modifying or propagating a
covered work, you indicate your acceptance of this License to do so.

  10. Automatic Licensing of Downstream Recipients.

  Each time you convey a covered work, the recipient automatically
receives a license from the original licensors, to run, modify and
propagate that work, subject to this License.  You are not responsible
for enforcing compliance by third parties with this License.

  An "entity transaction" is a transaction transferring control of an
organization, or substantially all assets of one, or subdividing an
organization, or merging organizations.  If propagation of a covered
work results from an entity transaction, each party to that
transaction who receives a copy of the work also receives whatever
licenses to the work the party's predecessor in interest had or could
give under the previous paragraph, plus a right to possession of the
Corresponding Source of the work from the predecessor in interest, if
the predecessor has it or can get it with reasonable efforts.

  You may not impose any further restrictions on the exercise of the
rights granted or affirmed under this License.  For example, you may
not impose a license fee, royalty, or other charge for exercise of
rights granted under this License, and you may not initiate litigation
(including a cross-claim or counterclaim in a lawsuit) alleging that
any patent claim is infringed by making, using, selling, offering for
sale, or importing the Program or any portion of it.

  11. Patents.

  A "contributor" is a copyright holder who authorizes use under this
License of the Program or a work on which the Program is based.  The
work thus licensed is called the contributor's "contributor version".

  A contributor's "essential patent claims" are all patent claims
owned or controlled by the contributor, whether already acquired or
hereafter acquired, that would be infringed by some manner, permitted
by this License, of making, using, or selling its contributor version,
but do not include claims that would be infringed only as a
consequence of further modification of the contributor version.  For
purposes of this definition, "control" includes the right to grant
patent sublicenses in a manner consistent with the requirements of
this License.

  Each contributor grants you a non-exclusive, worldwide, royalty-free
patent license under the contributor's essential patent claims, to
make, use, sell, offer for sale, import and otherwise run, modify and
propagate the contents of its contributor version.

  In the following three paragraphs, a "patent license" is any express
agreement or commitment, however denominated, not to enforce a patent
(such as an express permission to practice a patent or covenant not to
sue for patent infringement).  To "grant" such a patent license to a
party means to make such an agreement or commitment not to enforce a
patent against the party.

  If you convey a covered work, knowingly relying on a patent license,
and the Corresponding Source of the work is not available for anyone
to copy, free of charge and under the terms of this License, through a
publicly available network server or other readily accessible means,
then you must either (1) cause the Corresponding Source to be so
available, or (2) arrange to deprive yourself of the benefit of the
patent license for this particular work, or (3) arrange, in a manner
consistent with the requirements of this License, to extend the patent
license to downstream recipients.  "Knowingly relying" means you have
actual knowledge that, but for the patent license, your conveying the
covered work in a country, or your recipient's use of the covered work
in a country, would infringe one or more identifiable patents in that
country that you have reason to believe are valid.

  If, pursuant to or in connection with a single transaction or
arrangement, you convey, or propagate by procuring conveyance of, a
covered work, and grant a patent license to some of the parties
receiving the covered work authorizing them to use, propagate, modify
or convey a specific copy of the covered work, then the patent license
you grant is automatically extended to all recipients of the covered
work and works based on it.

  A patent license is "discriminatory" if it does not include within
the scope of its coverage, prohibits the exercise of, or is
conditioned on the non-exercise of one or more of the rights that are
specifically granted under this License.  You may not convey a covered
work if you are a party to an arrangement with a third party that is
in the business of distributing software, under which you make payment
to the third party based on the extent of your activity of conveying
the work, and under which the third party grants, to any of the
parties who would receive the covered work from you, a discriminatory
patent license (a) in connection with copies of the covered work
conveyed by you (or copies made from those copies), or (b) primarily
for and in connection with specific products or compilations that
contain the covered work, unless you entered into that arrangement,
or that patent license was granted, prior to 28 March 2007.

  Nothing in this License shall be construed as excluding or limiting
any implied license or other defenses to infringement that may
otherwise be available to you under applicable patent law.

  12. No Surrender of Others' Freedom.

  If conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License.  If you cannot convey a
covered work so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you may
not convey it at all.  For example, if you agree to terms that obligate you
to collect a royalty for further conveying from those to whom you convey
the Program, the only way you could satisfy both those terms and this
License would be to refrain entirely from conveying the Program.

  13. Use with the GNU Affero General Public License.

  Notwithstanding any other provision of this License, you have
permission to link or combine any covered work with a work licensed
under version 3 of the GNU Affero General Public License into a single
combined work, and to convey the resulting work.  The terms of this
License will continue to apply to the part which is the covered work,
but the special requirements of the GNU Affero General Public License,
section 13, concerning interaction through a network will apply to the
combination as such.

  14. Revised Versions of this License.

  The Free Software Foundation may publish revised and/or new versions of
the GNU General Public License from time to time.  Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.

  Each version is given a distinguishing version number.  If the
Program specifies that a certain numbered version of the GNU General
Public License "or any later version" applies to it, you have the
option of following the terms and conditions either of that numbered
version or of any later version published by the Free Software
Foundation.  If the Program does not specify a version number of the
GNU General Public License, you may choose any version ever published
by the Free Software Foundation.

  If the Program specifies that a proxy can decide which future
versions of the GNU General Public License can be used, that proxy's
public statement of acceptance of a version permanently authorizes you
to choose that version for the Program.

  Later license versions may give you additional or different
permissions.  However, no additional obligations are imposed on any
author or copyright holder as a result of your choosing to follow a
later version.

  15. Disclaimer of Warranty.

  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

  16. Limitation of Liability.

  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.

  17. Interpretation of Sections 15 and 16.

  If the disclaimer of warranty and limitation of liability provided
above cannot be given local legal effect according to their terms,
reviewing courts shall apply local law that most closely approximates
an absolute waiver of all civil liability in connection with the
Program, unless a warranty or assumption of liability accompanies a
copy of the Program in return for a fee.

                     END OF TERMS AND CONDITIONS

            How to Apply These Terms to Your New Programs

  If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.

  To do so, attach the following notices to the program.  It is safest
to attach them to the start of each source file to most effectively
state the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.

    <one line to give the program's name and a brief idea of what it does.>
    Copyright (C) <year>  <name of author>

    This program is free software: you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
    the Free Software Foundation, either version 3 of the License, or
    (at your option) any later version.

    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    GNU General Public License for more details.

    You should have received a copy of the GNU General Public License
    along with this program.  If not, see <https://www.gnu.org/licenses/>.

Also add information on how to contact you by electronic and paper mail.

  If the program does terminal interaction, make it output a short
notice like this when it starts in an interactive mode:

    <program>  Copyright (C) <year>  <name of author>
    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
    This is free software, and you are welcome to redistribute it
    under certain conditions; type `show c' for details.

The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License.  Of course, your program's commands
might be different; for a GUI interface, you would use an "about box".

  You should also get your employer (if you work as a programmer) or school,
if any, to sign a "copyright disclaimer" for the program, if necessary.
For more information on this, and how to apply and follow the GNU GPL, see
<https://www.gnu.org/licenses/>.

  The GNU General Public License does not permit incorporating your program
into proprietary programs.  If your program is a subroutine library, you
may consider it more useful to permit linking proprietary applications with
the library.  If this is what you want to do, use the GNU Lesser General
Public License instead of this License.  But first, please read
<https://www.gnu.org/licenses/why-not-lgpl.html>.
© 版权声明
THE END
喜欢就支持一下吧
点赞0 分享
评论 抢沙发

请登录后发表评论

    暂无评论内容