It is being removed from OSC in https://review.opendev.org/#/c/677795/.
Apparently, setting OS_AUTH_TYPE=none works now.
Change-Id: Ib910a50c8ad01abc0a6058c400a7eb875d3b6b77
Removed setting was used and the second step was unclear.
I updated the procedure to match current state.
Change-Id: I10ce74a1c1a7355837b283c372737c9b06ae2e85
Signed-off-by: Radosław Piliszek <radoslaw.piliszek@gmail.com>
Following recent changes to global requirements [1], we need
to update sphinx requirements locally.
[1] If558f184c959e4b63b56dec3ca1571d1034cfe5c
Change-Id: I9088c6a63f9cf51dd17f576c6b675278646836b6
The most important bits are updating shade references to remove
the openstack-infra. The other git urls will work through the
redirect, but cleaning them up is just nicer.
This removes two comments that reference files that no longer
exist due to config generation.
Also, fix some random use of github for cloning openstack repos,
since the github mirror is best-effort only.
Change-Id: I55a1d9db940cf5fa2c35421db7add015ae334563
Needed-By: https://review.opendev.org/654056
It seems that Jessie is no longer supported, and its backports repo
is no longer available, hence all DIB jobs fail.
Depends-On: https://review.openstack.org/#/c/653453/
Change-Id: I7973c8da057a678e6285ecc9418a4862bc1d3feb
The ironic CLI is deprecated, and use of OS_AUTH_TOKEN causes problems
when set during deploy-dynamic.yaml, so we should move to recommending
use of the openstack CLI instead.
Change-Id: I7aa969385962008505db3115fc7e86b2729f26ee
Story: 2005034
Task: 29523
Due to the fact that the openstack CLI can not be found on
the minimal OS (Ubuntu Xenial + OpenSSH server ~ 363 packages)
and that some tasks related to Keystone use this utility
it should be installed like the other Ironic CLIs
Change-Id: I3c2056cd1fe8551ca7dcb7f122e8982d5f9301a5
Closes-Bug: #1747349
This change will help fix pep8 issues of all *.rst files
in the project and checking for new files.
Change-Id: Ib06aeb7fa76bd387d76c23bc3f8ecca89332d989
Co-authored-By: Hoang Trung Hieu <hieuht@vn.fujitsu.com>
1) Update doc links according to OpenStack document migration
2) Use https instead of http for docs links
Change-Id: I66ec684f89a842f73f5854ad70c35c8a3d8334dc
http_proxy and https_proxy are passed as enviroment variable, while
no_proxy is not taken into account during bifrost installation.
This patch add no_proxy environment variable to Ansible.
Change-Id: I5eaaf86ff08ca7189aa63b0a709be48e189b5f7c
Closes-Bug: #1708322
It is included into doc/source/index, so its heading levels have to be
compatible with ones there. The same goes for MISSION.
Also fixes incorrect link syntax.
Change-Id: I71f575b72abad0c5992be841ac3ee5ea1094537d
As part of the docs migration work[0] for Pike we need to switch to use
the openstackdocstheme.
[0]https://review.openstack.org/#/c/472275/
Change-Id: Ifcfdaf8247ed52e57ed8ccb31338eb492df10e0e
Some of the documentation linking is broken, and will need
to be fixed as the documentation is revamped for the doc
migration.
Change-Id: I23a5f8a7c0cc7b0ce19052a2383e20b96e195996
In order to make it more flexible, and to consume the upper
constraints file from the right branch, allow to consume an
exported var, and default to the current path.
Change-Id: I57ef2944f4c2b643d240f30cac46ad91662ff538
As an operator, I may wish to provide DHCP boot options for hosts not
managed by bifrost using the bifrost dnsmasq server.
If a dhcp-boot configuration option is provided to dnsmasq via a file in
/etc/dnsmasq.d/, and the server is not booted via iPXE, it will be
overridden by the undionly.kpxe option added by bifrost in
/etc/dnsmasq.conf.
This occurs because the negated tag match !ipxe used in the
/undionly.kpxe dhcp-boot entry will match all hosts not using iPXE. The
dhcp-boot entries are processed in order and the last matching entry
wins. Since the config-dir option appears before the dhcp-boot options,
user-provided options are processed first and are therefore overridden.
The solution here is fairly simple - use a positive match for the ipxe
tag:
dhcp-boot=tag:ipxe,http://host:port/boot.ipxe
dhcp-boot=/undionly.kpxe
An entry with a tag will always win over the entry without a tag
specified, so it is now possible to add a rule to override
undionly.kpxe.
Change-Id: Ic0637e14504def73fbc0333eee9dc2456c57c32e
Closes-Bug: #1675367
To move bifrost testing to *_ipmitool drivers + virtualbmc, we need
the baremetal data file to support ipmi port setting, as in the case of
virtualbmc, all test VM nodes use the same local IPMI address with
different port per-node.
Unfortunately, the CSV baremetal inventory format that is used in our
testing procedures does not support setting IPMI ports.
As the CSV format is considered a legacy format, let's move testing to use
JSON-formatted baremetal data instead of fixing the legacy format parser.
Changes are mostly to 'bifrost-create-vm-nodes' role and it's callers.
Some level of backward compatibility is provided:
- baremetal_csv_file var is still accepted, and its value is used as
path to write data, although the data will nevertheless be in JSON format.
An extra helper script is added to reduce the number of nodes in
inventory when testing DHCP.
Also the script in 'bifrost-test-dhcp' role is changed to support
loading data from JSON.
This change officially deprecates using CSV formatted baremetal inventory
files.
Handling CSV baremetal inventory files will be removed in the Queens
release.
Change-Id: If2dcf43857195611ef342fe602330878378b021b
Partial-Bug: #1659876
Reordering documenation for a cleaner presentation
of details, and centralization of howto information.
Change-Id: I758161b46cb19b8871e59cd2b3fcddbfc009b785
This change introduces fixes, which allows install Ironic on remote
server. This may not complete list of changes required for all
operations.
Also added group 'target' to inventory file, which is same as localhost
by default, and host in this group can be replaced by remote host.
Change-Id: I59c942d2556c5e1b7eee661fb8cf13c4ae02b2d1
* Adding keystone support reference to documentation.
* Adding Xenial to the list of supported Ubuntu distributions.
Change-Id: Id093d2e474c6e9501599431342d208886d04444c
Using keystone is a bit of an advance topic, but documentation
is required to allow users to hopefully grasp the essentials of
what is required.
Change-Id: I25fd57f9acf07420384f021d17a43cf73412a965
The intermediate chain loader URL, for our TFTP configuration
requires a leading / to match the file in order to serve up the
user's request.
Added leading "/" to the configuration examples.
Change-Id: I8bec59400f013b2912f836b3619bea2e078f564c
Closes-Bug: #1524505
In some cases it is simpler to just configure the images being deployed
to use DHCP, rather than teach them how to put the IP address in the
configdrive in the right place. This will setup dnsmasq to send the
static address for the box. It will use that address for the deploy as
well.
Co-Authored-By: Clint Byrum <clint@fewbar.com>
Co-Authored-By: Gregory Haynes <greg@greghaynes.net>
Co-Authored-By: Julia Kreger <juliaashleykreger@gmail.com>
Change-Id: I524958be5e787d42c91278baf2c4a14beb965e7c
Assorted cleanups for this readme, including:
- Move file to .rst extension
- Fix bulleted lists
- Mark up literals
- Fix typos
Change-Id: I66f8454c671b3d8d8f126304875285e2599f7dde
Do some cleanups on our troubleshooting doc, including:
- Add the doc to the tree of stuff that gets rendered
- Correctly mark up literals
- Consistent capitalization for Ironic/Bifrost
- Make list autonumerate for ease of maintenance
Change-Id: I29dc39bf5b88588d19626af566d2e7d29fdacf48
Some of our documentation wasn't in the index. Add it. Also
clean up one bulleted list which was causing some errors.
Change-Id: I5459d8914ddef905e7783a711477bad116d585a8
The deploy_kernel* and deploy_ramdisk* variables were confusingly
named because they looked similar to deploy_image. I've renamed
them to ipa_kernel* and ipa_ramdisk* to reflect that they are the
CoreOS kernel and ramdisk from IPA and have updated the
documentation. I also cleaned up a minor issue where we defined
a path for the local copies of the kernel and ramdisk but didn't
use it in the install playbook.
I've also removed deploy_image_upstream_url from the offline
installation documentation as we no longer use it.
Partial-Bug: 1478726
Change-Id: Ia8c865521974e6bdd9e8e6a3ffa4c5f6b1f2f6ad
For an offline install, env-setup.sh needs to be able to clone
from locations other than GitHub. Additionally, since
the ansible repo will have to have its .gitmodules file patched
to point submodules to some other location as well, its convenient
to allow for alternate branches.
As a side-effect, this moves the documentation of what branch
we're using to the top of the script for easy reference and removes
the duplicated branch name.
Change-Id: I7432531915c03638aaf52f836cda607d424351ba
To facilitate offline installs, any explicit URLs should be
moved to a location where they can be easily overridden with
a local equivalent.
That way, a default install will use the canonical location, but
a user can easily override this behavior in inventory.
(Such gymnastics are not necessary for apt/yum/pip, because those
can be configured to point to local/alternate repositories independently).
** WIP - Needs *better* documentation **
Change-Id: I9dada2fe769e30abc06dac092b9f47b99969a954
Closes-Bug: #1464787
Use cookiecutter (https://git.openstack.org/openstack-dev/cookiecutter)
to generate config for tox so we can generate docs, run pep8, etc.
Also move CONTRIBUTING.rst to the root of the repository in keeping
with what seems to be the standard location. This move allows us to
easily generate the docs. Also include a tiny fix to allow pep8 to
run cleanly.
Change-Id: Ifbfc6d85c7b02bf4ab989974b491a3a1ae6f0900
