openstack
/
tripleo-ipsec
Code Issues Proposed changes

Retire Tripleo: remove repo content 

TripleO project is retiring
- https://review.opendev.org/c/openstack/governance/+/905145

this commit remove the content of this project repo

Change-Id: I4a6e97bc88f71be3de9af767a86cdd7290e9a0c4
This commit is contained in:
Ghanshyam Mann 2024-02-24 11:33:18 -08:00
parent b5559c8c86
commit c992826604
37 changed files with 8 additions and 2176 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
.gitignore vendored
View File

@ -1,9 +0,0 @@
*.retry
*.swp
.eggs/
.tox/
tripleo_ipsec.egg-info/
# Hardcoded to be the file containing the secret
# We ignore it from here since it should be generated
# by the user.
ipsec-psk.yml

674
LICENSE
View File

@ -1,674 +0,0 @@
GNU GENERAL PUBLIC LICENSE
Version 3, 29 June 2007
Copyright (C) 2007 Free Software Foundation, Inc. <http://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 <http://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:
{project} Copyright (C) {year} {fullname}
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
<http://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
<http://www.gnu.org/philosophy/why-not-lgpl.html>.

190
README.rst
View File

@ -1,184 +1,10 @@
tripleo-ipsec
=============
This project is no longer maintained.
Ansible role to configure IPSEC tunnels for TripleO
The contents of this repository are still available in the Git
source code management system. To see the contents of this
repository before it reached its end of life, please check out the
previous commit with "git checkout HEAD^1".
* This sets up packages and firewall settings.
* Sets the configuration for the IPSEC tunnels in the overcloud nodes.
* Parses the given configuration file and starts the IPSEC tunnels.
In a final step, when pacemaker is enabled, it enables resource agents for each
Virtual IP which puts up/tears down IPSEC tunnels depending on the VIP
location.
Note that as of the latest code, this now relies on the usage of TripleO's
dynamic inventory. This means that it expects the inventory to tell the role
which networks are being set and which IPs do the hosts have. If the relevant
variables don't come from the inventory, the role will attempt to use the legacy
setup which autodiscovers these. However, this setup is not very reliable if
you're using custom networks.
Role Variables
--------------
* `ipsec_psk`: the Pre-Shared Key to be used for the IPSEC tunnels.
Note that is is sensible information and it's recommended that it's stored
securely on the host where the playbook runs from, e.g. using Ansible Vault.
One can generate this variable with the following command:
`openssl rand -base64 48`
* `ipsec_algorithm`: Defines the encryption algorithm to use in the phase2alg
configuration option for the tunnels. Defaults to: `aes_gcm128-null`.
The possible values should be checked in libreswan's documentation.
* `ipsec_configure_vips`: Determines whether or not the role should configure
the tunnels for the VIPs. Defaults to: `true`.
* `ipsec_skip_firewall_rules`: Determines whether the role should skip
or not the firewall rules. Defaults to: `false`.
* `ipsec_uninstall_tunnels`: Determines whether the role should remove the IPSEC
tunnels that were previously set. Defaults to: `false`.
* `ipsec_upgrade_tunnels`: Determines whether the role should upgrade the IPSEC
tunnels that were previously set. This means it'll remove all the tunnels
created in a previous run and replace them. Defaults to: `false`.
* `ipsec_setup_resource_agents`: Determines whether the role should create the
pacemaker resource agents or not. Defaults to: `true`.
* `ipsec_skip_networks`: Determines which networks should be skipped. defaults to `[]`.
* `ipsec_force_install_legacy`: Forces the legacy installation. Defaults to: `false`.
* `overcloud_controller_identifier`: This identifies which nodes are
controllers in the cluster and which aren't, and should be part of the
hostname of the controller. Defaults to: 'controller'. It's highly
recommended that there's a way to explicitly identify the nodes this way.
Note that this is only used in the legacy setup.
Example Playbook
----------------
Sample::
- hosts: servers
roles:
- tripleo-ipsec
Enabling ipsec tunnels in TripleO
=================================
The main playbook to be ran on the overcloud nodes is::
tests/deploy-ipsec-tripleo.yml
Which will deploy IPSEC on the overcloud nodes for the internal API network.
We'll use a PSK and an AES128 cipher.
Add the PSK to an ansible var file::
cat <<EOF > ipsec-psk.yml
ipsec_psk: $(openssl rand -base64 48)
EOF
Encrypt the file with ansible-vault (note that it'll prompt for a password):
ansible-vault encrypt ipsec-psk.yml
Having done this, now you can run the playbook::
ansible-playbook -i /usr/bin/tripleo-ansible-inventory --ask-vault-pass \
-e @ipsec-psk.yml tests/deploy-ipsec-tripleo.yml
Generating an inventory
-----------------------
The script */usr/bin/tripleo-ansible-inventory* generates a dynamic inventory
with the nodes in the overcloud. And However it comes with some inconveniences:
* In deployments older than Pike, it might be a bit slow to run. To address
this, in Ocata and Pike it's possible to generate a static inventory out of
the output of this command::
/usr/bin/tripleo-ansible-inventory --static-inventory nodes.txt
This will create a called nodes.txt with the static inventory, which we could
now use and save some time.
* Newton unfortunately only takes into account computes and controllers with
this command. So for this deployment we need to generate an inventory of our
own. we can do so with the following command::
cat <<EOF > nodes.txt
[undercloud]
localhost
[undercloud:vars]
ansible_connection = local
[overcloud:vars]
ansible_ssh_user = heat-admin
[overcloud]
$( openstack server list -c Networks -f value | sed 's/ctlplane=//')
EOF
This assumes that you're deploying this playbook from the undercloud itself.
Hence the undercloud group containing localhost.
Skipping networks
=================
The `ipsec_skip_networks` variable allows the user to skip the tunnel setup
for certain networks. This works by using the network name, which can vary
depending on your type of setup.
Using the dynamic inventory (Queens and beyond)
-----------------------------------------------
When using the dynamic inventory, the network names will be based on the names
that are set in your `network_data.yaml` file, from tripleo-heat-templates.
As mentioned in tripleo-heat-templates, this file will determine which networks
you're setting up in your overall TripleO deployment, and will even specify
which of those networks have VIPs attached to them.
The network names to use in the `ipsec_skip_networks` variable will be under
the `name_lower` section of each network definition.
For instance, if you want to skip the storage management network, you'll see
that the entry looks as follows::
- name: StorageMgmt
name_lower: storage_mgmt
vip: true
vlan: 40
ip_subnet: '172.16.3.0/24'
allocation_pools: [{'start': '172.16.3.4', 'end': '172.16.3.250'}]
ipv6_subnet: 'fd00:fd00:fd00:4000::/64'
ipv6_allocation_pools: [{'start': 'fd00:fd00:fd00:4000::10', 'end': 'fd00:fd00:fd00:4000:ffff:ffff:ffff:fffe'}]
So, in this case, the variable you'll put in your ansible variables file will
have the following entry::
ipsec_skip_networks:
- storage_mgmt
You can add more networks by adding more items to that list.
Legacy setups
-------------
If you're using a legacy setup (which would work in Newton), you'll need to
note that the network names are hardcoded; so you'll have the following
options available:
* internalapi
* storage
* storagemgmt
* ctlplane
You can also explicitly skip creating the Redis VIP by adding the `redis` word
to the list.
If you would want to skip the Storage and Storage Management networks, the
variable you'll put in your ansible variables file will have the
following entry::
ipsec_skip_networks:
- storage
- storagemgmt
For any further questions, please email
openstack-discuss@lists.openstack.org or join #openstack-dev on
OFTC.

11
defaults/main.yml
View File

@ -1,11 +0,0 @@
---
overcloud_controller_identifier: controller
ipsec_algorithm: 'aes_gcm128-null'
ipsec_configure_vips: true
ipsec_force_install_legacy: false
ipsec_setup_resource_agents: true
ipsec_skip_firewall_rules: false
ipsec_uninstall_tunnels: false
ipsec_upgrade_tunnels: false
use_opportunistic_ipsec: false
ipsec_skip_networks: []

192
files/ipsec-resource-agent.sh
View File

@ -1,192 +0,0 @@
#!/bin/sh
#
#
# IPSEC OCF RA. Handles IPSEC tunnels associated with a VIP
#
# Copyright (c) 2017 Red Hat Inc.
# All Rights Reserved.
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of version 2 of the GNU General Public License as
# published by the Free Software Foundation.
#
# This program is distributed in the hope that it would be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
#
# Further, this software is distributed without any warranty that it is
# free of the rightful claim of any third person regarding infringement
# or the like. Any license provided herein, whether implied or
# otherwise, applies only to this software file. Patent licenses, if
# any, provided herein do not apply to combinations of this program with
# other software, or any other product whatsoever.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write the Free Software Foundation,
# Inc., 59 Temple Place - Suite 330, Boston MA 02111-1307, USA.
#
#######################################################################
# Initialization:
: ${OCF_FUNCTIONS_DIR=${OCF_ROOT}/lib/heartbeat}
. ${OCF_FUNCTIONS_DIR}/ocf-shellfuncs
#######################################################################
# Defaults
OCF_RESKEY_confdir_default="/etc/ipsec.d/"
: ${OCF_RESKEY_confdir=${OCF_RESKEY_confdir_default}}
meta_data() {
cat <<END
<?xml version="1.0"?>
<!DOCTYPE resource-agent SYSTEM "ra-api-1.dtd">
<resource-agent name="ipsec">
<version>1.0</version>
<longdesc lang="en">
This is a Resource Agent to manage IPSEC tunnels associated with a Virtual IP
Address. It's meant to be collocated with a specific VIP, and will manage
setting up or down a specific tunnel.
</longdesc>
<shortdesc lang="en">Handles IPSEC tunnels for VIPs</shortdesc>
<parameters>
<parameter name="tunnel" unique="1" required="1">
<longdesc lang="en">
The name of the tunnel to be monitored.
</longdesc>
<shortdesc lang="en">Tunnel name</shortdesc>
<content type="string" default="" />
</parameter>
<parameter name="vip" unique="1" required="1">
<longdesc lang="en">
Virtual IP address that the tunnel is using.
</longdesc>
<shortdesc lang="en">VIP</shortdesc>
<content type="string" default="" />
</parameter>
<parameter name="confdir">
<longdesc lang="en">
The directory where the IPSEC tunnel configurations can be found.
</longdesc>
<shortdesc lang="en">Tunnel name</shortdesc>
<content type="string" default="${OCF_RESKEY_confdir_default}" />
</parameter>
<parameter name="fallbacktunnel" unique="1">
<longdesc lang="en">
The name of the tunnel to fall back to when the main tunnel is put down.
</longdesc>
<shortdesc lang="en">Tunnel name to fall back to</shortdesc>
<content type="string" default="" />
</parameter>
</parameters>
<actions>
<action name="start" timeout="20" />
<action name="stop" timeout="20" />
<action name="monitor" timeout="20" interval="10" depth="0" />
<action name="reload" timeout="20" />
<action name="meta-data" timeout="5" />
</actions>
</resource-agent>
END
}
#######################################################################
ipsec_usage() {
cat <<END
usage: $0 {start|stop|monitor|validate-all|meta-data}
Expects to have a fully populated OCF RA-compliant environment set. And
should have a collocation constraint with a VIP associated with the
tunnel.
END
}
ipsec_start() {
echo "Putting up ${OCF_RESKEY_tunnel}" >> /tmp/ipsec-agent.log
ipsec auto --add "${OCF_RESKEY_tunnel}" &>> /tmp/ipsec-agent.log
ipsec whack --listen &>> /tmp/ipsec-agent.log
local return_code=$?
if [ $return_code -eq 1 -o $return_code -eq 10 ]; then
ocf_log warn "${OCF_RESOURCE_INSTANCE} : Unable to add tunnel ${OCF_RESKEY_tunnel} with return code ${return_code}"
return $OCF_ERR_GENERIC
else
return $OCF_SUCCESS
fi
}
ipsec_stop() {
echo "Putting down ${OCF_RESKEY_tunnel}" >> /tmp/ipsec-agent.log
ipsec auto --down "${OCF_RESKEY_tunnel}" &>> /tmp/ipsec-agent.log
local return_code=$?
ocf_log info "${OCF_RESOURCE_INSTANCE} : Put down tunnel ${OCF_RESKEY_tunnel} with return code ${return_code}"
ipsec whack --listen &>> /tmp/ipsec-agent.log
if [ -n "${OCF_RESKEY_fallbacktunnel}" ]; then
echo "Putting up ${OCF_RESKEY_fallbacktunnel}" >> /tmp/ipsec-agent.log
# Run this in a subshell and let it run, This will end the stop
# operation And the start of the tunnel will hopefully start on the
# other node. Meanwhile, this will keep trying to put up the
# fallback tunnel up, and will eventually succeed or timeout in the
# background.
(ipsec auto --up "${OCF_RESKEY_fallbacktunnel}" &>> /tmp/ipsec-agent.log) &
disown
fi
return $OCF_SUCCESS
}
ipsec_monitor() {
# Monitor _MUST!_ differentiate correctly between running
# (SUCCESS), failed (ERROR) or _cleanly_ stopped (NOT RUNNING).
# That is THREE states, not just yes/no.
ipsec status | grep "$OCF_RESKEY_tunnel" | grep -q unoriented
state=$?
if [ "$state" == "0" ]; then
ip addr show | grep -q "${OCF_RESKEY_vip}"
hosting_vip=$?
if [ "hosting_vip" == "0" ]; then
ocf_log warn "${OCF_RESOURCE_INSTANCE} : tunnel ${OCF_RESKEY_tunnel} is unoriented"
return $OCF_ERR_GENERIC
else
return $OCF_NOT_RUNNING
fi
else
return $OCF_SUCCESS
fi
}
ipsec_validate() {
# The tunnel needs to be defined in the configuration
cat ${OCF_RESKEY_confdir}/*.conf | grep -q "conn $OCF_RESKEY_tunnel"
state=$?
if [ "$state" == "0" ]; then
return $OCF_SUCCESS
else
return $OCF_ERR_GENERIC
fi
}
case $__OCF_ACTION in
meta-data) meta_data
exit $OCF_SUCCESS
;;
start) ipsec_start;;
stop) ipsec_stop;;
monitor) ipsec_monitor;;
reload) ocf_log info "Reloading ${OCF_RESOURCE_INSTANCE} ..."
;;
usage|help) ipsec_usage
exit $OCF_SUCCESS
;;
*) ipsec_usage
exit $OCF_ERR_UNIMPLEMENTED
;;
esac
rc=$?
ocf_log debug "${OCF_RESOURCE_INSTANCE} $__OCF_ACTION : $rc"
exit $rc

21
handlers/main.yml
View File

@ -1,21 +0,0 @@
---
- name: Save iptables rules
shell: iptables-save > /etc/sysconfig/iptables
become: yes
- name: Restore iptables rules
command: iptables-restore
become: yes
- name: Restart ipsec
service:
name: ipsec
state: restarted
become: yes
- name: Listen for IPSEC connections
shell: ipsec whack --listen # noqa 305
become: yes
ignore_errors: true
when:
- inventory_hostname in groups['pacemaker']

21
meta/main.yml
View File

@ -1,21 +0,0 @@
galaxy_info:
author: Juan Antonio Osorio Robles
role_name: tripleo_ipsec
description: Ansible role to configure IPSEC tunnels for TripleO
company: Red Hat Inc.
issue_tracker_url: https://github.com/JAORMX/tripleo-fernet-key-rotation/issues
license: GPLv3
min_ansible_version: 2.4
platforms:
- name: EL
versions:
- 7
galaxy_tags:
- 'tripleo'
- 'openstack'
- 'ipsec'
dependencies: []

30
setup.cfg
View File

@ -1,30 +0,0 @@
[metadata]
name = tripleo-ipsec
summary = Ansible role for managing TripleO's IPSEC tunnels
description-file =
README.rst
author = Juan Antonio Osorio Robles
author-email = jaosorior@redhat.com
home-page = https://opendev.org/openstack/tripleo-ipsec
classifier =
Intended Audience :: Developers
Intended Audience :: System Administrators
License :: OSI Approved :: GNU General Public License v3 (GPLv3)
Operating System :: POSIX :: Linux
[files]
data_files =
/usr/share/ansible/roles/tripleo-ipsec/defaults = defaults/*
/usr/share/ansible/roles/tripleo-ipsec/files = files/*
/usr/share/ansible/roles/tripleo-ipsec/handlers = handlers/*
/usr/share/ansible/roles/tripleo-ipsec/meta = meta/*
/usr/share/ansible/roles/tripleo-ipsec/tasks = tasks/*
/usr/share/ansible/roles/tripleo-ipsec/templates = templates/*
/usr/share/ansible/roles/tripleo-ipsec/tests = tests/*
[pbr]
warnerrors = True
[wheel]
universal = 1

29
setup.py
View File

@ -1,29 +0,0 @@
# Copyright (c) 2013 Hewlett-Packard Development Company, L.P.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
# implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# THIS FILE IS MANAGED BY THE GLOBAL REQUIREMENTS REPO - DO NOT EDIT
import setuptools
# In python < 2.7.4, a lazy loading of package `pbr` will break
# setuptools if some other modules registered functions in `atexit`.
# solution from: http://bugs.python.org/issue15881#msg170215
try:
import multiprocessing # noqa
except ImportError:
pass
setuptools.setup(
setup_requires=['pbr>=2.0.0'],
pbr=True)

88
tasks/firewall.yml
View File

@ -1,88 +0,0 @@
---
- name: Open INPUT for UDP port 500 for the Internet Key Exchange (IKE) protocol
iptables:
action: insert
chain: INPUT
protocol: udp
jump: ACCEPT
source_port: 500
destination_port: 500
notify:
- Save iptables rules
- Restore iptables rules
- name: Open OUTPUT for UDP port 500 for the Internet Key Exchange (IKE) protocol
iptables:
action: insert
chain: OUTPUT
protocol: udp
jump: ACCEPT
source_port: 500
destination_port: 500
notify:
- Save iptables rules
- Restore iptables rules
- name: Open INPUT for UDP port 4500 for IKE NAT-Traversal
iptables:
action: insert
chain: INPUT
protocol: udp
jump: ACCEPT
source_port: 4500
destination_port: 4500
notify:
- Save iptables rules
- Restore iptables rules
- name: Open OUTPUT for UDP port 4500 for IKE NAT-Traversal
iptables:
action: insert
chain: OUTPUT
protocol: udp
jump: ACCEPT
source_port: 4500
destination_port: 4500
notify:
- Save iptables rules
- Restore iptables rules
- name: Open INPUT for Protocol 50 - Encapsulated Security Payload (ESP) IPsec packets
iptables:
action: insert
chain: INPUT
protocol: esp
jump: ACCEPT
notify:
- Save iptables rules
- Restore iptables rules
- name: Open OUTPUT for Protocol 50 - Encapsulated Security Payload (ESP) IPsec packets
iptables:
action: insert
chain: OUTPUT
protocol: esp
jump: ACCEPT
notify:
- Save iptables rules
- Restore iptables rules
- name: Open INPUT for Protocol 51 - Authentication Header (AH) traffic
iptables:
action: insert
chain: INPUT
protocol: ah
jump: ACCEPT
notify:
- Save iptables rules
- Restore iptables rules
- name: Open OUTPUT for Protocol 51 - Authentication Header (AH) traffic
iptables:
action: insert
chain: OUTPUT
protocol: ah
jump: ACCEPT
notify:
- Save iptables rules
- Restore iptables rules

101
tasks/hardcoded-network-discover.yml
View File

@ -1,101 +0,0 @@
---
#
# This gets the network related information of the nodes in the old hardcoded fashion.
# This is because we want it to still work with Newton; however, for Queens, we will
# have some variables provided that will help us do this in a better way.
- name: Get the current node's internal API IP address
shell: grep "{{ ansible_hostname }}.internalapi$" /etc/hosts | awk '{print $1}' # noqa 306
register: current_internalapi_ip_register
changed_when: false
# This outputs the hosts as lines consisting of <fqdn>,<IP>
- name: Get the controller internal API hostnames and IP addresses
shell: grep "{{ overcloud_controller_identifier }}.*internalapi$" /etc/hosts | awk '{print $3","$1}' # noqa 306
register: internalapi_controllers_register
changed_when: false
- name: Get the current node's storage IP address
shell: grep "{{ ansible_hostname }}.storage$" /etc/hosts | awk '{print $1}' # noqa 306
register: current_storage_ip_register
changed_when: false
# This outputs the hosts as lines consisting of <fqdn>,<IP>
- name: Get the controller storage hostnames and IP addresses
shell: grep "{{ overcloud_controller_identifier }}.*storage$" /etc/hosts | awk '{print $3","$1}' # noqa 306
register: storage_controllers_register
changed_when: false
- name: Get the current node's storagemgmt IP address
shell: grep "{{ ansible_hostname }}.storagemgmt$" /etc/hosts | awk '{print $1}' # noqa 306
register: current_storagemgmt_ip_register
changed_when: false
# This outputs the hosts as lines consisting of <fqdn>,<IP>
- name: Get the controller storagemgmt hostnames and IP addresses
shell: grep "{{ overcloud_controller_identifier }}.*storagemgmt$" /etc/hosts | awk '{print $3","$1}' # noqa 306
register: storagemgmt_controllers_register
changed_when: false
- name: Get the current node's ctlplane IP address
shell: grep "{{ ansible_hostname }}.ctlplane$" /etc/hosts | awk '{print $1}' # noqa 306
register: current_ctlplane_ip_register
changed_when: false
# We don't parse the control plane IP Addresses here since we don't expect communication
# between nodes with these. We only need the VIP
- name: Get the overcloud internal API VIP address
command: hiera -c /etc/puppet/hiera.yaml internal_api_virtual_ip
register: internalapi_vip_register
changed_when: false
- name: Get the overcloud redis VIP address
command: hiera -c /etc/puppet/hiera.yaml redis_vip
register: redis_vip_register
changed_when: false
- name: Get the overcloud storage VIP address
command: hiera -c /etc/puppet/hiera.yaml storage_virtual_ip
register: storage_vip_register
changed_when: false
- name: Get the overcloud storagemgmt VIP address
command: hiera -c /etc/puppet/hiera.yaml storage_mgmt_virtual_ip
register: storagemgmt_vip_register
changed_when: false
- name: Get the overcloud ctlplane VIP address
command: hiera -c /etc/puppet/hiera.yaml controller_virtual_ip
register: ctlplane_vip_register
changed_when: false
- name: Set the networks IPs facts
set_fact:
networks:
- name: internalapi
current_ip: "{{ current_internalapi_ip_register.stdout }}"
controllers: "{{ internalapi_controllers_register.stdout_lines }}"
vips:
- name: internalapi
ip: "{{ internalapi_vip_register.stdout }}"
- name: redis
ip: "{{ redis_vip_register.stdout }}"
- name: storage
current_ip: "{{ current_storage_ip_register.stdout }}"
controllers: "{{ storage_controllers_register.stdout_lines }}"
vips:
- name: storage
ip: "{{ storage_vip_register.stdout }}"
- name: storagemgmt
current_ip: "{{ current_storagemgmt_ip_register.stdout }}"
controllers: "{{ storagemgmt_controllers_register.stdout_lines }}"
vips:
- name: storagemgmt
ip: "{{ storagemgmt_vip_register.stdout }}"
- name: ctlplane
current_ip: "{{ current_ctlplane_ip_register.stdout }}"
controllers: []
vips:
- name: ctlplane
ip: "{{ ctlplane_vip_register.stdout }}"

47
tasks/init-connections.yml
View File

@ -1,47 +0,0 @@
---
- name: Set network name fact
set_fact:
network: "{{ item }}"
- name: Set IP/VIP variable key facts
set_fact:
ip_var_key: "{{ item + '_ip' }}"
vip_var_key: "{{ item + '_vip' }}"
- name: Set current IP fact
set_fact:
current_ip: "{{ hostvars[inventory_hostname][ip_var_key] }}"
# This effectively skips the configuration if we're in a network that's
# not actually enabled. We can notice that if the IP has fallen back to
# the control plane's IP.
- when: current_ip != ctlplane_ip or network == 'ctlplane'
block:
- name: Set net CIDR fact
set_fact:
current_subnet: "{{ ip_with_prefix_register.stdout | ipaddr('subnet') }}"
# Gets the IPs for the other nodes in the network. It skips the current IP and
# also skips the nodes that are not in the subnet (which fall back to the
# ctlplane network by default).
- name: Set other IPs fact
set_fact:
other_ips: "{{ hostvars|json_query(other_ips_query)|difference([current_ip])|ipaddr(current_subnet) }}"
vars:
other_ips_query: '*.{{ ip_var_key }}'
- name: Set VIP fact
set_fact:
current_vip:
name: "{{ network }}"
ip: "{{ hostvars[inventory_hostname][vip_var_key]|default('') }}"
- name: Ping all hosts in this network
command: "ping -c 5 {{ item }}"
ignore_errors: true
with_items: "{{ other_ips }}"
- name: Ping {{ current_vip.name }} VIP
command: "ping -c 5 {{ current_vip.ip }}"
when: current_vip.ip and ipsec_configure_vips|bool
ignore_errors: true

162
tasks/ipsec-conf.yml
View File

@ -1,162 +0,0 @@
---
# NOTE: This is only here because we currently don't have pluggable auth.
- name: Check for PSK variable
fail:
msg: Please provide the PSK key via the 'ipsec_psk' variable
when: ipsec_psk is not defined
- name: Set network name fact
set_fact:
network: "{{ item }}"
- name: Set IP/VIP variable key facts
set_fact:
ip_var_key: "{{ item + '_ip' }}"
vip_var_key: "{{ item + '_vip' }}"
- name: Set current IP fact
set_fact:
current_ip: "{{ hostvars[inventory_hostname][ip_var_key] }}"
# This effectively skips the configuration if we're in a network that's
# not actually enabled. We can notice that if the IP has fallen back to
# the control plane's IP.
- when: current_ip != ctlplane_ip or network == 'ctlplane'
block:
- name: Set IP with prefix register
shell: "ip addr show | grep {{ current_ip }} | awk '{print $2}'"
register:
ip_with_prefix_register
- name: Set net CIDR fact
set_fact:
current_subnet: "{{ ip_with_prefix_register.stdout | ipaddr('subnet') }}"
# Gets the IPs for the other nodes in the network. It skips the current IP and
# also skips the nodes that are not in the subnet (which fall back to the
# ctlplane network by default).
- name: Set other IPs fact
set_fact:
other_ips: "{{ hostvars|json_query(other_ips_query)|difference([current_ip])|ipaddr(current_subnet) }}"
vars:
other_ips_query: '*.{{ ip_var_key }}'
- name: Set VIP fact
set_fact:
current_vip:
name: "{{ network }}"
ip: "{{ hostvars[inventory_hostname][vip_var_key]|default('') }}"
- name: Remove {{ network }} from virtual-private setting in ipsec setup configuration
replace:
path: /etc/ipsec.conf
regexp: '(^\s+.*)%v4:{{ current_subnet|regex_replace("\.", "\.") }},(.*)$'
replace: '\1\2'
backup: yes
notify:
- Listen for IPSEC connections
- name: Write ipsec tunnel policy for the {{ network }} network
template:
src: policy.j2
dest: /etc/ipsec.d/policies/overcloud-{{ policy }}-{{ network }}-ip
mode: '0640'
when:
- other_ips != []
- type == 'opportunistic'
notify:
- Listen for IPSEC connections
- name: Write ipsec tunnel secrets for the {{ network }} network
template:
src: ipsec-{{ type }}-tunnels.secrets.j2
dest: /etc/ipsec.d/overcloud-{{ network }}-{{ type }}-tunnels.secrets
mode: '0600'
when:
- other_ips != []
- type != 'opportunistic'
notify:
- Listen for IPSEC connections
- name: Write ipsec tunnel configuration for the {{ network }} network
template:
src: ipsec-{{ type }}-{{ policy }}.conf.j2
dest: /etc/ipsec.d/overcloud-{{ network }}-{{ type }}-{{ policy }}-tunnels.conf
mode: '0640'
when: other_ips != []
- name: Write VIP ipsec secrets file for the {{ network }} network
template:
src: ipsec-vip-tunnels.secrets.j2
dest: /etc/ipsec.d/overcloud-{{ current_vip.name }}-vip-tunnels.secrets
mode: '0600'
when: current_vip.ip and type != 'opportunistic' and ipsec_configure_vips|bool
notify:
- Listen for IPSEC connections
- name: Write VIP ipsec tunnel configuration for the {{ network }} network
template:
src: ipsec-vip-tunnels.conf.j2
dest: /etc/ipsec.d/overcloud-{{ current_vip.name }}-vip-tunnels.conf
mode: '0640'
when: current_vip.ip and type != 'opportunistic' and ipsec_configure_vips|bool
notify:
- Listen for IPSEC connections
- include_tasks: resource-agent.yml
when:
- pacemaker_running|bool
- type != 'opportunistic'
- current_vip.ip
- inventory_hostname == groups['pacemaker'][0]
- ipsec_setup_resource_agents|bool
- ipsec_configure_vips|bool
- name: Filter redis VIP through current subnet
set_fact:
redis_net_filter: "{{ redis_vip|ipaddr(current_subnet) }}"
- name: Set fact to check if redis is part of this subnet
set_fact:
redis_in_subnet: "{{ redis_vip == redis_net_filter }}"
- name: Set Redis VIP fact
set_fact:
current_vip:
name: redis
ip: "{{ redis_vip }}"
when:
- redis_in_subnet|bool
- name: Write Redis VIP ipsec secrets file for the {{ network }} network
template:
src: ipsec-vip-tunnels.secrets.j2
dest: /etc/ipsec.d/overcloud-redis-vip-tunnels.secrets
mode: '0600'
when:
- redis_in_subnet|bool
- type != 'opportunistic'
- ipsec_configure_vips|bool
notify:
- Listen for IPSEC connections
- name: Write Redis VIP ipsec tunnel configuration for the {{ network }} network
template:
src: ipsec-vip-tunnels.conf.j2
dest: /etc/ipsec.d/overcloud-redis-vip-tunnels.conf
mode: '0640'
when:
- redis_in_subnet|bool
- type != 'opportunistic'
- ipsec_configure_vips|bool
notify:
- Listen for IPSEC connections
- include_tasks: resource-agent.yml
when:
- pacemaker_running|bool
- type != 'opportunistic'
- redis_in_subnet|bool
- inventory_hostname == groups['pacemaker'][0]
- ipsec_setup_resource_agents|bool
- ipsec_configure_vips|bool

63
tasks/ipsec.yml
View File

@ -1,63 +0,0 @@
---
# This tasks rely on TripleO's dynamic inventory being used.
- name: Set private-or-clear networks fact
set_fact:
private_or_clear_networks: ["ctlplane"]
- name: Set private networks fact
set_fact:
private_networks: "{{ enabled_networks|difference(private_or_clear_networks)|difference(ipsec_skip_networks) }}"
- name: Are we using Opportunistic IPSEC tunnels?
set_fact:
ipsec_type: opportunistic
when: use_opportunistic_ipsec|bool
- name: Are we using node-to-node IPSEC tunnels?
set_fact:
ipsec_type: node-to-node
when: not use_opportunistic_ipsec|bool
- name: Add uniqueids = no to ipsec setup configuration
lineinfile:
dest: /etc/ipsec.conf
regexp: '^\s+uniqueids'
insertafter: '^config setup'
line: "\tuniqueids=no"
when: not use_opportunistic_ipsec|bool
# Permissions gotten from http://www.linux-ha.org/doc/dev-guides/_installing_and_packaging_resource_agents.html
- name: Install TripleO IPSEC resource agent
copy:
src: ipsec-resource-agent.sh
dest: /usr/lib/ocf/resource.d/heartbeat/ipsec
mode: '0755'
force: no
register: resource_agent
when: pacemaker_running|bool
- include_tasks: ipsec-conf.yml
with_items: "{{ private_networks }}"
vars:
policy: private
type: "{{ ipsec_type }}"
# Unfortunately the ctlplane currently has issues when non-opportunistic
# tunnels are used. It will reject any connection and hold packets for
# some reason.
- include_tasks: ipsec-conf.yml
with_items: "{{ private_or_clear_networks }}"
vars:
policy: private-or-clear
type: "{{ ipsec_type }}"
when: use_opportunistic_ipsec|bool
# We force the restart of IPSEC here since adding it as a handler was
# getting run between the loop above, which is not desirable.
- name: Force restart IPSEC
shell: ipsec restart # noqa 301 305
- meta: flush_handlers
- include_tasks: init-connections.yml
with_items: "{{ private_networks }}"

51
tasks/legacy-ipsec-conf.yml
View File

@ -1,51 +0,0 @@
---
- name: Set network based facts for this node and network
set_fact:
network: "{{ item.name }}"
current_ip: "{{ item.current_ip }}"
controllers: "{{ item.controllers }}"
vips: "{{ item.vips }}"
- name: Add legacy {{ network }} tunnel configuration if not in skip list
when: network not in ipsec_skip_networks
block:
- name: Write node-to-node ipsec secrets file for the {{ network }} network
template:
src: legacy-ipsec-node-to-node-tunnels.secrets.j2
dest: /etc/ipsec.d/overcloud-{{ network }}-node-to-node-tunnels.secrets
mode: '0600'
when: controllers != []
notify:
- Restart ipsec
- name: Write node-to-node ipsec tunnel configuration for the {{ network }} network
template:
src: legacy-ipsec-node-to-node-tunnels.conf.j2
dest: /etc/ipsec.d/overcloud-{{ network }}-node-to-node-tunnels.conf
mode: '0640'
when: controllers != []
notify:
- Restart ipsec
- name: Write VIP ipsec secrets file for the {{ network }} network
template:
src: ipsec-vip-tunnels.secrets.j2
dest: /etc/ipsec.d/overcloud-{{ current_vip.name }}-vip-tunnels.secrets
mode: '0600'
with_items: "{{ vips }}"
loop_control:
loop_var: current_vip
notify:
- Restart ipsec
- name: Write VIP ipsec tunnel configuration for the {{ network }} network
template:
src: ipsec-vip-tunnels.conf.j2
dest: /etc/ipsec.d/overcloud-{{ current_vip.name }}-vip-tunnels.conf
mode: '0640'
with_items: "{{ vips }}"
loop_control:
loop_var: current_vip
notify:
- Restart ipsec

65
tasks/legacy.yml
View File

@ -1,65 +0,0 @@
---
# This contains the "legacy" code for setting up IPSEC tunnels before
# IPSEC 3.20
- name: Check for PSK variable
fail:
msg: Please provide the PSK key via the 'ipsec_psk' variable
when: ipsec_psk is not defined
# This gets the network information, which should come in a structure
# with the following format:
#
# networks:
# - name: <Network name>
# current_ip: <The IP of this node for this network>
# controllers: <The IPs for this network for the rest of the controllers>
# vips:
# - name: <Name of the VIP for this network>
# ip: <Actual VIP>
# - name: <Another name of the VIP for this network>
# ip: <Another actual VIP>
- import_tasks: hardcoded-network-discover.yml
# This returns the hostname (short) of the node hosting the VIP
- name: Determine which node is hosting the VIP
shell: pcs status | grep ip- | sed 's/ip-//' | awk '{print $1"\t"$4}' | grep "{{ networks[0]['vips'][0]['ip'] }}" | awk '{print $2}' # noqa 306
register: node_hosting_the_vip
when: pacemaker_running|bool
- name: Add uniqueids = no to ipsec setup configuration
lineinfile:
dest: /etc/ipsec.conf
regexp: '^\s+uniqueids'
insertafter: '^config setup'
line: "\tuniqueids=no"
notify:
- Restart ipsec
- include_tasks: legacy-ipsec-conf.yml
with_items: "{{ networks }}"
# We force the restart of IPSEC here since adding it as a handler was
# getting run between the loop above, which is not desirable.
- name: Force restart IPSEC
shell: ipsec restart # noqa 301 305
# Permissions gotten from http://www.linux-ha.org/doc/dev-guides/_installing_and_packaging_resource_agents.html
- name: Install TripleO IPSEC resource agent
copy:
src: ipsec-resource-agent.sh
dest: /usr/lib/ocf/resource.d/heartbeat/ipsec
mode: '0755'
force: yes
register: resource_agent
when: pacemaker_running|bool
# This queries the VIPs for all networks and flattens them into a list
# that contains a dict with the "name" and "ip" for each VIP entry.
- include_tasks: resource-agent.yml
loop_control:
loop_var: current_vip
with_items: "{{ networks|default([])|json_query('[*].vips[]')|list }}"
when:
- pacemaker_running|bool
- node_hosting_the_vip.stdout == ansible_hostname

23
tasks/main.yml
View File

@ -1,23 +0,0 @@
---
- import_tasks: pacemaker_facts.yml
- when: ipsec_uninstall_tunnels|bool or ipsec_upgrade_tunnels|bool
block:
- import_tasks: uninstall.yml
- when: not ipsec_uninstall_tunnels|bool or ipsec_upgrade_tunnels|bool
block:
- import_tasks: setup.yml
- import_tasks: firewall.yml
when: not ipsec_skip_firewall_rules|bool
- meta: flush_handlers
# This doesn't use the dynamic inventory
- import_tasks: legacy.yml
when: enabled_networks is not defined or ipsec_force_install_legacy|bool
# This uses the dynamic inventory
- import_tasks: ipsec.yml
when: enabled_networks is defined and not ipsec_force_install_legacy|bool

11
tasks/pacemaker_facts.yml
View File

@ -1,11 +0,0 @@
---
- name: Get pacemaker status
systemd:
name: pacemaker
register: pacemaker_status
- name: Determine if pacemaker is running
set_fact:
pacemaker_running: "{{ pacemaker_status.status.ActiveState == 'active' }}"

53
tasks/resource-agent.yml
View File

@ -1,53 +0,0 @@
---
# This file means to be a generic way to add resource agents for VIPs
# The following are assumed to be passed:
#
# * current_vip.name: Name of the network
# * current_vip.ip: the VIP
- name: Set specific resource agent facts
set_fact:
resource_agent_name: tripleo-ipsec-{{ current_vip.name }}
specific_tunnel: overcloud-{{ current_vip.name }}-vip-tunnel
fallback_tunnel: overcloud-{{ current_vip.name }}-node-to-vip-tunnel
specific_vip: "{{ current_vip.ip }}"
- name: Add {{ current_vip.name }} resource agent if not in skip list
when: current_vip.name not in ipsec_skip_networks
block:
- name: Was the {{ resource_agent_name }} Resource Agent added already?
command: pcs resource show {{ resource_agent_name }}
ignore_errors: yes
register: found_resource_agent
changed_when: found_resource_agent is failed
- name: Delete {{ resource_agent_name }} Resource Agent
command: pcs resource delete {{ resource_agent_name }}
when:
- resource_agent.changed
- found_resource_agent is succeeded
- name: Add {{ resource_agent_name }} pacemaker resource agent
command: pcs resource create {{ resource_agent_name }} ocf:heartbeat:ipsec tunnel={{ specific_tunnel }} vip={{ specific_vip }}
fallbacktunnel={{ fallback_tunnel }} --disabled
when:
- resource_agent.changed or found_resource_agent is failed
- name: Add collocation rule with VIP ( {{ resource_agent_name }} )
command: pcs constraint colocation add {{ resource_agent_name }} with ip-{{ specific_vip }}
when:
- resource_agent.changed or found_resource_agent is failed
- name: Add ordering rule with VIP ( {{ resource_agent_name }} ) for start operation
command: pcs constraint order start ip-{{ specific_vip }} then start {{ resource_agent_name }} symmetrical=false
when:
- resource_agent.changed or found_resource_agent is failed
- name: Add ordering rule with VIP ( {{ resource_agent_name }} ) for stop operation
command: pcs constraint order stop ip-{{ specific_vip }} then stop {{ resource_agent_name }} symmetrical=false
when:
- resource_agent.changed or found_resource_agent is failed
- name: Enable {{ resource_agent_name }} resource agent
command: pcs resource enable {{ resource_agent_name }}
when:
- resource_agent.changed or found_resource_agent is failed

14
tasks/setup.yml
View File

@ -1,14 +0,0 @@
---
- name: Install libreswan package
yum: name=libreswan state=present
- name: Initialize ipsec nss database
command: ipsec initnss
args:
creates: /etc/ipsec.d/*db
- name: Start and enable ipsec service
service:
name: ipsec
enabled: yes
state: started

42
tasks/uninstall.yml
View File

@ -1,42 +0,0 @@
---
- name: Get first node running the IPSec resource agents
shell: "pcs status | grep tripleo-ipsec | head -1 | awk '{print $4}'"
register: node_running_ipsec_agent_register
when: pacemaker_running|bool
changed_when: false
ignore_errors: true
- name: Delete IPSec pacemaker resource agents
shell: "pcs status | grep tripleo-ipsec | awk '{print $1}' | xargs -n1 pcs resource delete" # noqa 306
when:
- pacemaker_running|bool
- node_running_ipsec_agent_register.rc == 0
- node_running_ipsec_agent_register.stdout == ansible_hostname
- name: Find tunnel configurations to delete
find:
paths: /etc/ipsec.d/
patterns: overcloud-*
register: configs_to_delete
- name: Remove tunnel configurations
file:
path: "{{ item.path }}"
state: absent
with_items: "{{ configs_to_delete.files }}"
notify:
- Restart ipsec
- name: Find policy configurations to delete
find:
paths: /etc/ipsec.d/policies/
patterns: overcloud-*
register: policies_to_delete
- name: Remove tunnel configurations
file:
path: "{{ item.path }}"
state: absent
with_items: "{{ policies_to_delete.files }}"
notify:
- Restart ipsec

20
templates/ipsec-node-to-node-private-or-clear.conf.j2
View File

@ -1,20 +0,0 @@
# Generated by Ansible.
# This contains the node-to-node IPSEC configuration from this node's
# in the {{ network }} to every other node. This also uses a private-or-clear
# policy, which will drop packages while the negotiation is taking place,
# but will let packets through if it fails. Thus preferring IPSEC, but
# allowing clear connections if needed.
{% for other_ip in other_ips %}
conn overcloud-private-node-to-node-{{ network }}-ip-{{ loop.index0 }}
type=tunnel
authby=secret
leftid={{ current_ip }}
left={{ current_ip }}
rightid={{ other_ip }}
right={{ other_ip }}
failureshunt=passthrough
auto=start
retransmit-timeout=2s
phase2alg={{ ipsec_algorithm }}
{% endfor %}

18
templates/ipsec-node-to-node-private.conf.j2
View File

@ -1,18 +0,0 @@
# Generated by Ansible.
# This contains the node-to-node IPSEC configuration from this node's
# in the {{ network }} to every other node. This also uses a private
# policy, which will hold packages and drop them if negotiation fails.
{% for other_ip in other_ips %}
conn overcloud-private-node-to-node-{{ network }}-ip-{{ loop.index0 }}
type=tunnel
authby=secret
leftid={{ current_ip }}
left={{ current_ip }}
rightid={{ other_ip }}
right={{ other_ip }}
failureshunt=drop
auto=start
retransmit-timeout=2s
phase2alg={{ ipsec_algorithm }}
{% endfor %}

3
templates/ipsec-node-to-node-tunnels.secrets.j2
View File

@ -1,3 +0,0 @@
{% for other_ip in other_ips %}
{{ current_ip }} {{ other_ip }} : PSK "{{ ipsec_psk }}"
{% endfor %}

24
templates/ipsec-opportunistic-private-or-clear.conf.j2
View File

@ -1,24 +0,0 @@
# Generated by Ansible.
# This contains the Opportunistic IPSEC configuration from this node's
# in the {{ network }} to every other node. This also uses a private-or-clear
# policy, which will drop packages while the negotiation is taking place,
# but will let packets through if it fails. Thus preferring IPSEC, but
# allowing clear connections if needed.
conn overcloud-private-or-clear-{{ network }}-ip
type=tunnel
authby=null
leftid=%null
rightid=%null
left={{ current_ip }}
right=%opportunisticgroup
rightmodecfgclient=yes
negotiationshunt=drop
failureshunt=passthrough
ikev2=insist
auto=start
keyingtries=1
retransmit-timeout=2s
# To support being behind NAT
leftmodecfgclient=yes
leftcat=yes
narrowing=yes

22
templates/ipsec-opportunistic-private.conf.j2
View File

@ -1,22 +0,0 @@
# Generated by Ansible.
# This contains the Opportunistic IPSEC configuration from this node's
# in the {{ network }} to every other node. This also uses a private
# policy, which will hold packages and drop them if negotiation fails.
conn overcloud-private-{{ network }}-ip
type=tunnel
authby=null
leftid=%null
rightid=%null
left={{ current_ip }}
right=%opportunisticgroup
rightmodecfgclient=yes
negotiationshunt=hold
failureshunt=drop
ikev2=insist
auto=start
keyingtries=1
retransmit-timeout=2s
# To support being behind NAT
leftmodecfgclient=yes
leftcat=yes
narrowing=yes

30
templates/ipsec-vip-tunnels.conf.j2
View File

@ -1,30 +0,0 @@
# Generated by ansible.
{% if pacemaker_running|bool %}
conn overcloud-{{ current_vip.name }}-vip-tunnel
left={{ current_vip.ip }}
leftid=@{{ current_vip.name }}vip
right=%any
rightid=@overcloud{{ current_vip.name }}cluster
authby=secret
auto=add
dpdaction=hold
dpddelay=5
dpdtimeout=15
phase2alg={{ ipsec_algorithm }}
failureshunt=drop
{% endif %}
conn overcloud-{{ current_vip.name }}-node-to-vip-tunnel
left={{ current_ip }}
leftid=@overcloud{{ current_vip.name }}cluster
right={{ current_vip.ip }}
rightid=@{{ current_vip.name }}vip
authby=secret
auto=start
dpdaction=restart
dpddelay=5
dpdtimeout=15
phase2alg={{ ipsec_algorithm }}
failureshunt=drop

4
templates/ipsec-vip-tunnels.secrets.j2
View File

@ -1,4 +0,0 @@
{% if pacemaker_running|bool %}
@{{ current_vip.name }}vip @overcloud{{ current_vip.name }}cluster : PSK "{{ ipsec_psk }}"
{% endif %}
@overcloud{{ current_vip.name }}cluster @{{ current_vip.name }}vip : PSK "{{ ipsec_psk }}"

52
templates/legacy-ipsec-node-to-node-tunnels.conf.j2
View File

@ -1,52 +0,0 @@
# Generated by ansible.
{% if pacemaker_running %}
{% for controller_unsplit in controllers %}
{% set controller = controller_unsplit.split(',') %}
{% if controller[0] != (ansible_hostname + '.' + network) %}
conn overcloud-{{ network }}-controller-to-controller-tunnel-{{ loop.index0 }}
left={{ current_ip }}
leftid=@{{ ansible_hostname }}.{{ network }}
right={{ controller[1] }}
rightid=@{{ controller[0] }}
authby=secret
auto=start
dpdaction=hold
dpddelay=5
dpdtimeout=15
phase2alg={{ ipsec_algorithm }}
failureshunt=drop
{% endif %}
{% endfor %}
conn overcloud-{{ network }}-controller-to-compute-tunnel
left={{ current_ip }}
leftid=@{{ ansible_hostname }}.{{ network }}
right=%any
rightid=@computecluster
authby=secret
auto=add
dpdaction=hold
dpddelay=5
dpdtimeout=15
phase2alg={{ ipsec_algorithm }}
failureshunt=drop
{% else %}
{% for controller_unsplit in controllers %}
{% set controller = controller_unsplit.split(',') %}
conn overcloud-{{ network }}-controller-to-compute-tunnel-{{ loop.index0 }}
left={{ current_ip }}
leftid=@computecluster
right={{ controller[1] }}
rightid=@{{ controller[0] }}
authby=secret
auto=start
dpdaction=hold
dpddelay=5
dpdtimeout=15
phase2alg={{ ipsec_algorithm }}
failureshunt=drop
{% endfor %}
{% endif %}

14
templates/legacy-ipsec-node-to-node-tunnels.secrets.j2
View File

@ -1,14 +0,0 @@
{% if pacemaker_running %}
{% for controller_unsplit in controllers %}
{% set controller = controller_unsplit.split(',') %}
{% if controller[0] != (ansible_hostname + '.' + network) %}
@{{ ansible_hostname }}.{{ network }} @{{ controller[0] }} : PSK "{{ ipsec_psk }}"
{% endif %}
{% endfor %}
@{{ ansible_hostname }}.{{ network }} @computecluster : PSK "{{ ipsec_psk }}"
{% else %}
{% for controller_unsplit in controllers %}
{% set controller = controller_unsplit.split(',') %}
@computecluster @{{ controller[0] }} : PSK "{{ ipsec_psk }}"
{% endfor %}
{% endif %}

3
templates/policy.j2
View File

@ -1,3 +0,0 @@
# Generated by Ansible
# This contains the policy file for the {{ network }} tunnel
{{ current_subnet }}

3
test-requirements.txt
View File

@ -1,3 +0,0 @@
pbr>=1.6
ansible
ansible-lint

4
tests/deploy-ipsec-tripleo.yml
View File

@ -1,4 +0,0 @@
- hosts: overcloud
become: true
roles:
- tripleo-ipsec

1
tests/inventory
View File

@ -1 +0,0 @@
localhost

5
tests/test.yml
View File

@ -1,5 +0,0 @@
---
- hosts: localhost
remote_user: root
tasks:
- include_tasks: ../tasks/main.yml

77
tox.ini
View File

@ -1,77 +0,0 @@
[tox]
minversion = 2.0
skipsdist = True
envlist = linters
[testenv]
usedevelop = True
install_command =
pip install -c{env:TOX_CONSTRAINTS_FILE:https://opendev.org/openstack/requirements/raw/branch/master/upper-constraints.txt} {opts} {packages}
deps =
-r{toxinidir}/test-requirements.txt
commands =
/usr/bin/find . -type f -name "*.pyc" -delete
passenv =
HOME
http_proxy
HTTP_PROXY
https_proxy
HTTPS_PROXY
ANSIBLE_FORCE_COLOR
no_proxy
NO_PROXY
whitelist_externals =
bash
rm
sudo
setenv =
VIRTUAL_ENV={envdir}
[testenv:linters]
setenv =
{[testenv:ansible]setenv}
commands =
{[testenv:ansible-lint]commands}
{[testenv:ansible-syntax]commands}
[testenv:ansible]
#deps =
# {[testenv]deps}
setenv =
{[testenv]setenv}
ANSIBLE_HOST_KEY_CHECKING = False
ANSIBLE_SSH_CONTROL_PATH = /tmp/%%h-%%r
ANSIBLE_ACTION_PLUGINS = {homedir}/.ansible/roles/plugins/action
ANSIBLE_CALLBACK_PLUGINS = {homedir}/.ansible/roles/plugins/callback
ANSIBLE_FILTER_PLUGINS = {homedir}/.ansible/roles/plugins/filter
ANSIBLE_LOOKUP_PLUGINS = {homedir}/.ansible/roles/plugins/lookup
ANSIBLE_LIBRARY = {homedir}/.ansible/roles/plugins/library
ANSIBLE_ROLES_PATH = {homedir}/.ansible/roles:{toxinidir}/playbooks/roles
commands =
rm -rf {homedir}/.ansible/roles
[testenv:ansible-lint]
#deps =
# {[testenv:ansible]deps}
setenv =
{[testenv:ansible]setenv}
commands =
ansible-lint -x ANSIBLE0016,106,no-tabs {toxinidir}
[testenv:ansible-syntax]
#deps =
# {[testenv:ansible]deps}
setenv =
{[testenv:ansible]setenv}
commands =
{[testenv:ansible]commands}
ansible-playbook -i {toxinidir}/tests/inventory \
--syntax-check \
--list-tasks \
-e "rolename={toxinidir}" \
{toxinidir}/tests/test.yml
[testenv:venv]
basepython = python3
commands = {posargs}

7
zuul.d/layout.yaml
View File

@ -1,7 +0,0 @@
- project:
check:
jobs:
- openstack-tox-linters
gate:
jobs:
- openstack-tox-linters