A project used to hold out-of-tree ironic drivers
Go to file
Pavlo Shchelokovskyy 0cdc53948f [ansible] configure SSL validation
This patch adds a number of configration options and playbook variables
that govern SSL validation and authentication when accessing the image
store to download the image and configdrive from the deploy ramdisk.

Most of them are not yet used in the default set of playbooks provided
with the driver
(for example some of them require yet unreleased Ansible 2.4),
however they can be used by custom playbooks, for example to upload
and enable those custom CA bundle and cert files to the ramdisk at
deploy time.

This patch also sets DevStack to disable validation of image store SSL
certificate by ansible deploy interface (similar to how IPA is currently
confugured).

This patch also caps Anisble < 2.4, since our custom callback plugin
has troubles with the newest Ansible 2.4 version (to be fixed later).

Change-Id: Id40f1067361cc32e98973c70fc5cd3d4242308d0
Closes-Bug: #1717858
2017-09-25 10:48:24 +00:00
devstack [ansible] configure SSL validation 2017-09-25 10:48:24 +00:00
doc/source [ansible] configure SSL validation 2017-09-25 10:48:24 +00:00
imagebuild Re-use tinyipa image for ansbile-deploy 2017-02-13 16:39:34 +00:00
ironic_staging_drivers [ansible] configure SSL validation 2017-09-25 10:48:24 +00:00
releasenotes Add hardware types 2017-08-31 11:34:40 +00:00
tools Add hardware types 2017-08-31 11:34:40 +00:00
.coveragerc remove omit in coveragerc 2016-01-29 13:31:34 +08:00
.gitignore Update .gitignore 2017-07-19 17:59:03 +05:30
.gitreview Added .gitreview 2016-01-25 14:10:45 +00:00
.mailmap Skeleton initial commit 2016-01-26 12:48:24 +00:00
.testr.conf Skeleton initial commit 2016-01-26 12:48:24 +00:00
CONTRIBUTING.rst Skeleton initial commit 2016-01-26 12:48:24 +00:00
HACKING.rst Skeleton initial commit 2016-01-26 12:48:24 +00:00
LICENSE Skeleton initial commit 2016-01-26 12:48:24 +00:00
README.rst Corrected typos from "resposible" to "responsible" and from "tho" to "though""tho" to "though" 2017-06-08 08:01:47 -04:00
babel.cfg Skeleton initial commit 2016-01-26 12:48:24 +00:00
extra-requirements.txt Install "ironic" in the unittest environment 2016-01-28 15:16:30 +00:00
requirements.txt Updated from global requirements 2017-08-30 23:21:18 +00:00
setup.cfg Add hardware types 2017-08-31 11:34:40 +00:00
setup.py Updated from global requirements 2017-03-20 13:20:56 +00:00
test-requirements.txt Updated from global requirements 2017-08-30 23:21:18 +00:00
tox.ini Specify ironic_staging_drivers as name of the app 2017-03-20 18:40:32 +02:00

README.rst

Ironic Staging Drivers

The Ironic Staging Drivers is used to hold out-of-tree Ironic drivers which doesn't have means to provide a 3rd Party CI at this point in time which is required by Ironic.

The intention of this project is to provide a common place for useful drivers resolving the "hundreds of different download sites" problem.

What the Ironic Staging Drivers is not

  • The Ironic Staging Drivers is not a project under Ironic's governance, meaning that the Ironic core group is not responsible for the code in this project (even though, some individuals that work in this project also hold core status in the Ironic project).
  • This project is not a place to dump code and run away hoping that someone else will take care of it for you. Drivers included in this project should be maintained and have their bugs fixed quickly. Therefore, driver owners are going to be asked to "babysit" their driver.

How to contribute

We want to make sure that the Ironic Staging Drivers project is a welcoming and friendly place to contribute code. Therefore, we want to avoid bureaucratic processes as much as possible. If you want to propose a driver to be included in the repository: Just submit the code!

How do I submit the code?

  1. Before we can accept your patches, you'll have to agree to a contributor license agreement.

  2. Learn about how to use our Gerrit review system.

  3. Get the code:

    git clone git://git.openstack.org/openstack/ironic-staging-drivers
  4. Make your changes and write a nice commit message explaining the change in details.

  5. Submit the code!