master
stable/train
victoria-eol
victoria-em
ussuri-eol
ussuri-em
13.1.0
stein-eol
queens-eol
11.0.4
train-em
12.0.2
10.6.0
12.0.1
11.0.3
13.0.1
rocky-eol
11.0.2
13.0.0
12.0.0
stein-em
11.0.1
rocky-em
10.5.1
10.3.1
11.0.0
queens-em
10.5.0
pike-eol
ocata-eol
10.4.0
pike-em
7.2.3
10.3.0
ocata-em
8.3.1
9.2.1
10.2.0
10.1.0
10.0.0
9.2.0
newton-eol
9.1.0
9.0.0
8.3.0
7.2.2
6.1.3
8.2.0
8.1.0
7.2.1
5.2.1
6.1.2
8.0.0
7.2.0
6.1.1
7.1.0
7.0.0
6.1.0
5.2.0
7.0.0.0b1
6.0.0
6.0.0.0rc1
5.1.0
6.0.0.0b2
6.0.0.0b1
5.0.0
5.0.0.0rc2
5.0.0.0b3
5.0.0.0b1
0.1.37
0.1.36
0.1.35
0.1.34
0.1.33
0.1.32
0.1.31
0.1.30
0.1.29
0.1.28
0.1.27
0.1.26
0.1.25
0.1.24
0.1.23
0.1.22
0.1.21
0.1.20
0.1.19
0.1.18
0.1.17
0.1.16
0.1.15
0.1.14
0.1.13
0.1.12
0.1.11
0.1.10
0.1.9
0.1.8
0.1.7
0.1.6
0.1.5
0.1.4
0.1.3
0.1.2
0.1.1
0.1.0
0.0.1
${ noResults }
2 Commits (master)
Author | SHA1 | Message | Date |
---|---|---|---|
![]() |
cb171db770 |
Use universal_newlines with subprocess.check_output
Python 3 will complain when trying to split a byte-string using a string so this change enables universal_newlines to make the split work in both python 2 and 3. Also add a py3 tox environment. Change-Id: I9af74b6c6cc9cfd0c973c85be04791aa6dc0acd4 |
6 years ago |
![]() |
76975f04e5 |
ec2 collector attempt config-drive before metadata server
This change will first attempt to get ec2 metadata from a v2 config drive before falling back to the nova metadata server if no config drive is detected. Config drive is enabled in overcloud nodes, so using this for os-collect-config will allow the undercloud nova metadata server to be disabled. V2 of the config-drive was released in OpenStack Folsom, so a decision was made to not support V1 discovery at all. This makes the block device candidate selection much simpler than the cloud-init one[1]. [1] https://git.launchpad.net/cloud-init/tree/cloudinit/sources/DataSourceConfigDrive.py#n219 Change-Id: I2aec0544fe40c2e901aee38c79bb838a627d20da Closes-Bug: #1619074 |
7 years ago |