summaryrefslogtreecommitdiff
path: root/test-requirements.txt
Commit message (Collapse)AuthorAgeFilesLines
* Remove the PowerVM driverStephen Finucane2022-08-021-1/+0
| | | | | | | | | | | | | | The PowerVM driver was deprecated in November 2021 as part of change Icdef0a03c3c6f56b08ec9685c6958d6917bc88cb. As noted there, all indications suggest that this driver is no longer maintained and may be abandonware. It's been some time and there's still no activity here so it's time to abandon this for real. This isn't as tied into the codebase as the old XenAPI driver was, so removal is mostly a case of deleting large swathes of code. Lovely. Change-Id: Ibf4f36136f2c65adad64f75d665c00cf2de4b400 Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
* Move optional build dependencies to 'extras'Stephen Finucane2022-01-281-3/+0
| | | | | | | | | | | | | | | | ...and start skipping the relevant tests in 'nova.tests.unit.virt' if these dependencies are not present. Thanks to hacking rules N311 and N312, which prevent virt drivers using code from other virt drivers, simply skipping the unit tests for a virt driver module is enough to ensure we never load those modules. This means users that want to use the powervm driver can install the required dependencies using e.g. 'pip install .[powervm]', and packagers can choose to skip packaging a dependency safe in the knowledge that the relevant tests will be skipped. Change-Id: I3787f9afd78cd0a7c7feb4dfe1bcb21437b5a128 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* requirements: Bump minimum testtools to 2.5.0Stephen Finucane2022-01-281-1/+1
| | | | | | | | | | This release removed the use of unittest2 in favour of the stdlib unittest module. unittest2 hasn't been maintained in years and has some quirky behavior differences to stdlib unittest. By bumping to 2.5.0, we avoid anyone having to use this. Change-Id: Ic3b257c799fe1669933c13f9571208740cd1cd1a Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* Move ReaderWriterLock to the test treeBalazs Gibizer2022-01-171-0/+1
| | | | | | | | | | | | | | | | The commit I168fffac8002f274a905cfd53ac4f6c9abe18803 added a wrapper around fasteners.ReaderWriterLock to fix up an issue with eventlet. But the wrapper was added to nova.utils module that is use not only by the nova tests but also the nova production code. This made the fixture library a dependency of the nova production code. While the current ReaderWriterLock usage only limited to the nova test sub tree. The I712f88fc1b6053fe6d1f13e708f3bd8874452a8f commit fix the issue of not having fixtures in the nova requirements.txt. However I think a better fix is to move the wrapper to the test subtree instead. This patch does that and restores the state of the requirements.txt Change-Id: I6903ce53b9b91325f7268cf2ebd02e4488579560 Related-Bug: #1958075
* Add fixtures to requirementsTakashi Kajinami2022-01-161-1/+0
| | | | | | | | | | | | The commit 887c445a7a6a17b92a37b6ed1dcdcc7dd009f65d made the nova.utils module dependent on the fixtures library but the change missed updating requirements and the fixtures library is not installed automatically. This change migrates the fixtures library from test-requirements.txt to requirements.txt so that the library is installed without test codes. Closes-Bug: #1958075 Change-Id: I712f88fc1b6053fe6d1f13e708f3bd8874452a8f
* requirements: Add types-paramikoStephen Finucane2021-06-091-0/+1
| | | | | | | | | | | | | This is required to resolve the following warning: error: Library stubs not installed for "paramiko" (or incompatible with Python 3.9) note: Hint: "python3 -m pip install types-paramiko" note: (or run "mypy --install-types" to install all missing stub packages) note: See https://mypy.readthedocs.io/en/stable/running_mypy.html#missing-imports Change-Id: I035d6dc752eaa83105cc12797765b304d843e1f7 Signed-off-by: Stephen Finucane <stephenfin@redhat.com> Depends-On: https://review.opendev.org/c/openstack/requirements/+/795532/
* vmware: Use oslo.vmware's get_moref_value()Johannes Kulik2021-04-191-1/+1
| | | | | | | | | | | | | | | | | | With switching the SOAP library backing oslo.vmware [1], the internal representation of ManagedObjectReference's attributes changes. To be able to make the switch without interruption, we introduced helper functions in oslo.vmware. This commit uses one of those - get_moref_value() - to make the access to the "value" attribute compatible with both backing libraries. Bump oslo.vmware lower-constraint to a version containing the helper function. We bump one version higher, because we already merged a patch (I3c769d3499f906b33725171a57313c8ae35b6a1d) that uses the cookiejar access contained in that version. [1] https://specs.openstack.org/openstack/oslo-specs/specs/victoria/oslo-vmware-soap-library-switch.html Change-Id: I48841a777aaa2e515c141857099c16483ab619e0
* use psycopg2 binary instead of source packageSean Mooney2021-01-141-1/+1
| | | | | | | | this change replaces psycopg2 with psycopg2-binary to avoid requiring the build depencyies for the postgres client. instead the tests now use the prebuilt binary wheel. Change-Id: Id6d920508b9ee9597a51616e66c47d4cb7f48ca0
* [goal] Prepare for job migration to Ubuntu Focal (20.04)Ghanshyam Mann2020-08-181-2/+2
| | | | | | | | | | | | | | | | | As per victoria cycle testing runtime and community goal[1] we need to migrate upstream CI/CD to Ubuntu Focal(20.04). Bump the lower constraints for required deps which added python3.8 support in their later version. Story: #2007865 Task: #40200 Closes-Bug: #1886298 [1] https://governance.openstack.org/tc/goals/selected/victoria/migrate-ci-cd-jobs-to-ubuntu-focal.html Change-Id: I6d79fc80b85d398fe0168677318c9c34285189ae
* Fix lower-constraints conflictsSean McGinnis2020-08-031-2/+2
| | | | | | | | | | Several version specified in our lower-constraints files had conflicting dependencies. This updates a few packages to avoid those conflicts. It also removes the linters that are tracked in the global requirements blocklist since we do not need to enforce lower-constraints for linters. Change-Id: Iae93f0631d77794f093fd330e849d2fd805b238f Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
* Provider Config File: YAML file loading and schema validationDustin Cowles2020-07-301-1/+1
| | | | | | | | | | | | | | | This series implements the referenced blueprint to allow for specifying custom resource provider traits and inventories via yaml config files. This first commit includes schema version 1.0 and functions to load and validate against that schema. Since this patch, package ddt>=1.2.1 is required to run tests. Co-Author: Tony Su <tao.su@intel.com> Author: Dustin Cowles <dustin.cowles@intel.com> Blueprint: provider-config-file Change-Id: I58099726f799c427e9174a0dcce9889344d51e7c
* Bump hacking min version to 3.1.0zhangbailin2020-05-191-1/+1
| | | | | | | | This has introduced a new version of pycodestyle, which has improved its parser to catch new corner cases and introduced some new tests. Closes-Bug: #1878317 Change-Id: I853cf4dbd7ad6b7903a7f444f5c1da3f0fb21f77
* tox: Integrate mypyStephen Finucane2020-05-151-0/+1
| | | | | | | | | | | | | | | | | | mypy is an experimental optional static type checker for Python that aims to combine the benefits of dynamic (or "duck") typing and static typing. While still in development, most features are supported and it's already being used by real world projects like Sphinx. Let's start small by integrating it into some of the interfaces that nova exposes. We can further build upon this if it works out. This change sets up the boilerplate necessary to use mypy in nova. Type annotations are not included for any module - these will be added separately. We're calling mypy by way of a script, as this allows us to store a list of files that we have converted while we're in the process of adding type annotations where necessary. Change-Id: I75ab46a6768c4ca2050fdde2b7f8eeb90724c8c6 Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
* Bump hacking min version to 3.0.1Ghanshyam Mann2020-05-151-1/+1
| | | | | | | | | | | | hacking 3.0.1 fix the pinning of flake8 to avoid bringing in a new version with new checks. bumping the min version for hacking so that any older hacking versions which auto adopt the new checks are not used. Depends-On: https://review.opendev.org/#/c/728335/ Change-Id: Ie00c10332bd7110169dbb150d601c157b6694d05
* requirements: Limit hacking to one minor versionStephen Finucane2020-01-201-1/+1
| | | | | | | | | It is possible, though unlikely, that hacking might introduce new rules in a minor version that would break the gate for nova. See this off before it can ever be an issue by doing $subject. Change-Id: I063488a2ad4924ffe2a48cbfc0c3c750221d37b7 Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
* Switch to hacking 2.xStephen Finucane2020-01-171-2/+1
| | | | | | | | | This bumps the version of flake8 and pycodestyle to something much newer, which resolves a long-standing warning about nested sets and allows us to use new fangled features like f-strings if we so choose. Change-Id: I0bb9077f1cea2243b7945e87cfa140f9cf89d558 Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
* nova-net: Kill itStephen Finucane2020-01-141-1/+0
| | | | | | | | | | | Finish the job by removing all the now-unused modules. This also allows us to - wait for it - kill mox at long last. It's a great day in the parish. Partial-Implements: blueprint remove-nova-network-ussuri Partial-Implements: blueprint mox-removal-ussuri Change-Id: Ia33ec2604b2fc2d3b6830b596cac669cc3ad6c96
* Revert "(Temporarily) readd bare support for py27"Stephen Finucane2019-12-131-1/+0
| | | | | | | | | | | | This reverts commit 33a2a5f2e408ee11e61b38b4dbdfe340939ecceb. We're now at M1 and the DevStack default has been changed. We no longer need to pretend to support Python 2.7. This is slightly modified to drop an additional Python 2.7-only dependency from lower-constraints.txt. [1] I52b03caee0ba700da3a15035201ea6cd91baa06b Change-Id: I1068850072e639ee268d68ca82249f569a40310e Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
* (Temporarily) readd bare support for py27Luigi Toscano2019-11-191-0/+1
| | | | | | | | | | | | | | Revert part of the changes from Ie1a0cbd82a617dbcc15729647218ac3e9cd0e5a9 This way it is possible again for nova to be installed using python 2, thus allowing other devstack-based jobs to work until everything switches to python 3 according the plans. While py2 support may break anytime, its days are limited anyway. Change-Id: I99ff84e6c1c033c28d499b0b8ac17ac5b0565f61
* Stop testing Python 2Stephen Finucane2019-11-181-1/+0
| | | | | | | | | | | | | | | | | | It's Ussuri. We can *finally* stop testing Python 2 [1]. Time to party. We don't attempt any cleanup but simply stop testing with Python 2, indicate that we only support Python 3 via 'setup.cfg' and remove any Python 2 only dependencies. Our 'tox.ini' is modified such that 'functional' now runs with 'python3', whatever that may point to, though the gate will only use a versioned variant (currently 'functional-py36'). This should free up a significant amount of resources from the gate and let us start using Python 3 idioms in our code. Win-win. [1] https://governance.openstack.org/tc/resolutions/20180529-python2-deprecation-timeline.html#python2-deprecation-timeline Change-Id: Ie1a0cbd82a617dbcc15729647218ac3e9cd0e5a9 Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
* Remove an unused file and a related descriptionTakashi NATSUME2019-09-131-3/+1
| | | | | | | | | | | | | | | | | The following file should have been removed in I4181f39dea7eb10b84e6f5057938767b3e422aff. * etc/nova/placement-policy-generator.conf A description of generating the placement policy.yaml file should also have been removed in the commit. Therefore remove them. And the 'wsgi-intercept' package is used for OSAPIFixture and not for placement functional tests currently. So a comment is removed in test-requirements.txt. Change-Id: Ie8d0d7085ccd82a47ea27b98be75c1bc9ba6195b
* Tests: autospecs all the mock.patch usagesTakashi NATSUME2019-08-191-1/+1
| | | | | | | | | | | | | | By default, mock.patch's autospec argument is None, meaning that there's no signature checking for the patched methods and functions. oslotest.mock_fixture.patch_mock_module fixes a few issues within mock.patch functions, as well as setting autospec=True by default, unless otherwise specified or new_callable, create, spec arguments are passed in. Co-Authored-By: Claudiu Belu <cbelu@cloudbasesolutions.com> Change-Id: I4484e63c97bd1cdde3d88855eabe7545784f365e Closes-Bug: #1735588
* Merge "Exclude broken ironicclient versions 2.7.1"Zuul2019-06-031-1/+1
|\
| * Exclude broken ironicclient versions 2.7.1翟小君2019-06-021-1/+1
| | | | | | | | | | | | Depends-On:https://review.opendev.org/#/c/659612/ Change-Id: Ia887be9e61ab68ab5cf1586082f2791118fc9c93
* | Move selective patching of open() to nova.test for reuseAdam Spiers2019-05-251-1/+1
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Several existing tests patch open() to fake the contents of a file outside the test virtualenv, whilst avoiding interfering with reading and writing of other files inside the test virtualenv. Currently they do it by duplicating logic. Furthermore, in the near future, more tests (specifically, some SEV tests) will want to do the same selective patching, and similarly will need to avoid impacting reads of other files within the test virtualenv, e.g. placement-policy.yaml. So create new patch_open() context manager / decorator in nova.test for selectively patching open based on the path parameter, and reuse this for existing tests. Also add unit tests for all these cases. mock >= 3.0.0 is required because configparser.RawConfigParser._read() uses enumerate() to iterate over the lines of the (mocked) /etc/nova/release config file, and this uses __iter__() under the hood which was not supported via mock_open until a bug was fixed and backported to the external mock library for 3.0.0: https://bugs.python.org/issue21258 https://bugs.python.org/issue32933 https://github.com/testing-cabal/mock/commit/73f6eed0d6867299fa2543b88a07cd8f12198361 Change-Id: I19f49c923d2c41eab0c7b4cab28c50498dc07046
* Move patch_exists() to nova.test.TestCase for reuseAdam Spiers2019-05-241-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | Several existing tests patch os.path.exists() to return a given value, whilst avoiding interfering with other checks for path existence inside the test virtualenv. Currently they do it by duplicating logic. Furthermore, in the near future, more tests (specifically, some SEV functional tests) will want to do the same selective patching, and similarly will need to avoid impacting existence checks on other files within the test virtualenv, e.g. placement-policy.yaml. TestGuestConfigSysinfoSerialOS already had a nice patch_exists() context manager for selectively patching os.path.exists based on the path parameter, so move this to nova.test.TestCase so that it can be reused to reduce duplication, and add appropriate unit test cases. In order to make patch_exists() generic, the path has to be introduced as an extra parameter alongside the desired return value. Additionally make it usable as a decorator, not just a context manager. This is achievable natively in Python 3 with contextlib, and in Python 2 via contextlib2. Change-Id: Ibe7cb29620f06d31059f2a5f94ca180b8671046e
* Bump to hacking 1.1.0Stephen Finucane2019-04-121-1/+2
| | | | | | | | | | | | This brings in a couple of new checks which must be addressed, many of which involve a rather large amount of changes, so these are ignored for now. A series of follow-up changes will resolved these. 'pycodestyle' is added as a dependency rather than it being pulled in transitively. This is necessary since we're using it in tests. Change-Id: I35c654bd39f343417e0a1124263ff31dcd0b05c9 Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
* Correct lower-constraints.txt and the related tox jobChris Dent2019-04-011-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In the review of a similar change in placement [1], it was realized that the nova lower-constraints tox job probably had the same problems. Testing revealed this to be the case. This change fixes the job and updates the related requirements problems accordingly. The are two main factors at play here: * The default install_command in tox.ini uses the upper_contraints.txt file. When there is more than one constraints.txt they are merged and the higher constraints win. Using upper and lower at the same time violates the point of lower (which is to indicate the bare minimum we are capable of using). * When usedevelop is true in tox, the command that is run to install the current projects code is something like 'python setup.py develop', which installs a project's requirements _after_ the install_command has run, clobbering the constrained installs. When using pbr, 'python setup.py install' (used when usedevelop is False) does not do this. Fixing those then makes it possible to use the test to fix the lower-constraints.txt and *requirements.txt files, changes include: * Defining 'usedevelop = False' in the 'lower-constraints' target and removing the otherwise superfluous 'skipsdist' global setting to ensure requirements aren't clobbered. * Removing packages which show up in lower-constraints.txt but not in the created virtualenv. Note that the job only runs unit tests, so this may be incomplete. In the placement version of this both unit and functional are run. We may want to consider that here. * Updating cryptography. This version is needed with more recent pyopenssl. * Updated keystonemiddleware. This is needed for some tests which confirm passing configuration to the middleware. * Update psycopg2 to a version that can talk with postgresql 10. * Add PyJWT, used by zVMCloudConnector * Update zVMCloudConnector to a version that works with Python 3.5 and beyond. * Update olso.messaging to versions that work with the tests, under Python 3. * Adding missing transitive packages. * Adjusting alpha-ordering to map to how pip freeze does it. * setuptools is removed from requirements.txt because the created virtualenv doesn't contain it NOTE: The lower-constraints.txt file makes no commitment to expressing minimum requirements for anything other than the current basepython. So the fact that a different set of lower-constraints would be present if we were using python2 is not relevant. See discussion at [1]. However, since requirements.txt _is_ used for python2, the requirements-check gate job requires that enum34 be present in lower-constraints.txt because it is in requirements.txt. NOTE: A test is removed because it cannot work in the lower-constraints context: 'test_policy_generator_from_command_line' forks a call to 'oslopolicy-policy-generator --namespace nova' which fails because stevedore fails to pick up nova-based entry points when in a different process. This is because of the change to usedevelop. After discussion with the original author of the test removal was considered an acceptable choice. [1] http://eavesdrop.openstack.org/irclogs/%23openstack-dev/%23openstack-dev.2019-03-05.log.html#t2019-03-05T13:28:23 Closes-Bug: #1822575 Change-Id: Ic6466b0440a4fe012731a63715cf5d793b6ae4dd
* Require python-ironicclient>=2.7.0Matt Riedemann2019-03-121-1/+1
| | | | | | | | | | | | This is related to change I5f78d21c39ed2fd58d2a0f3649116e39883d5a2c which depends on python-ironicclient change I610836e5038774621690aca88b2aee25670f0262 which was released in 2.7.0. The former did not have a direct dependency or version bump since it is being backported to stable branches where we don't bump minimum required versions of dependencies. Change-Id: I5edf350b29ef3bd1f103cdd4b0b997cb5ca32117 Related-Bug: #1818295
* Fix ironic client ironic_url deprecation warningDaniel Abad2018-10-241-1/+1
| | | | | | | | | | | | | | | | | | | | In preparation for stein, use 'endpoint' instead of 'ironic_url' when calling get_client in order to remove the following warning: WARNING ironicclient.client The argument "ironic_url" passed to get_client is deprecated and will be removed in Stein release, please use "endpoint" instead. For reference: In the python-ironicclient code, in the ironicclient/client.py#L24 TODO(vdrok): remove in Stein [...] ('ironic_url',): 'endpoint', Introduced in commit: https://github.com/openstack/python-ironicclient/commit/58c39b7a80583dd54165cf292ae5dc621e9da361 Change-Id: I1b3ce1955622c40b780c0b15ec7e09be3e8ace72
* Cleanup ugly stub in TestLocalDeleteAllocationsMatt Riedemann2018-05-161-1/+1
| | | | | | | | | | | | | | With a fix in wsgi-intercept 1.7.0 we can properly use the PlacementFixture as a context manager to simulate when placement is configured for a given operation. This allows us to remove the ugly stub that one of the tests in here had to rely on. While in here, the CastAsCall fixture is removed since we shouldn't rely on that in these tests where we're trying to simulate the user experience. Change-Id: I2074b45126b839ea6307a8740364393e9dddd50b
* Updated from global requirementsOpenStack Proposal Bot2018-03-231-2/+2
| | | | Change-Id: I004b8ea8fd3a8de76c04f70af5ed5e516aa2bfbc
* Follow the new PTI for document buildStephen Finucane2018-03-161-11/+0
| | | | | | | | | | | The Project Testing Interface [1] asks that we list requirements in 'doc/requirements.txt' and build docs by calling 'sphinx-build' directly instead of via the 'build_sphinx' setuptool/distutils wrapper. Start doing this. [1] https://governance.openstack.org/tc/reference/project-testing-interface.html Change-Id: If9342c8ea757b1735f2488db751008984fb33baf
* Updated from global requirementsOpenStack Proposal Bot2018-03-161-2/+2
| | | | Change-Id: I518860c51e6b19def5efc3f624dceb9350cb9494
* Updated from global requirementsOpenStack Proposal Bot2018-03-131-1/+1
| | | | Change-Id: Iff8f99d4ff97f03ccdeb29405f3cbb853068161d
* Updated from global requirementsOpenStack Proposal Bot2018-03-101-1/+1
| | | | Change-Id: Ibe70f1f60180a7c8da9887e4466dd1e1d25b157f
* Updated from global requirementsOpenStack Proposal Bot2018-01-291-2/+2
| | | | Change-Id: I371ee0cb4156ec4e0a20f55852b0756502d0dd90
* Merge "Updated from global requirements"Zuul2018-01-271-1/+1
|\
| * Updated from global requirementsOpenStack Proposal Bot2018-01-241-1/+1
| | | | | | | | Change-Id: I1fae25690551ff75a9838e760851a990e216be72
* | Merge "add whereto for testing redirect rules"Zuul2018-01-251-0/+3
|\ \ | |/ |/|
| * add whereto for testing redirect rulesDoug Hellmann2017-10-301-0/+3
| | | | | | | | | | | | | | | | | | | | | | Use whereto to test that the redirect rules do what we expect. The test coverage is a bit minimal for now, but should be useful as an example of how it can be extended. The test files in the openstack-manuals repo provide some other examples. Depends-On: I36003d3525dcc9fef8e5f008ecabb2b2ac78088e Change-Id: Ia14bfa6c89fd04844842d727d11ff8874ec7fc2a Signed-off-by: Doug Hellmann <doug@doughellmann.com>
* | Updated from global requirementsOpenStack Proposal Bot2018-01-181-1/+1
| | | | | | | | Change-Id: I1c1dc245f98cb5c3b57733ddc338394dfb3bc0b6
* | Updated from global requirementsOpenStack Proposal Bot2018-01-161-1/+1
| | | | | | | | Change-Id: Icada15d601dc5399eeb927bb7cba9bea828883da
* | Finish stestr migrationMatthew Treinish2017-11-241-2/+1
| | | | | | | | | | | | | | | | | | | | | | Nova switched to using stestr for all it's in tree testing except for the coverage job. This commit updates that job so it also uses stestr and cleans up the last bits of testr setup left in tree. As part of this change this moves all the one off per job configuration into the tox job definitions instead of hiding it in either the .stestr.conf or in a wrapper script. Change-Id: I36e0e791d485b44641a1ed8770eca8e95aca19be
* | Updated from global requirementsOpenStack Proposal Bot2017-11-161-1/+1
|/ | | | Change-Id: I2ddeb4baef5e535923a8e16ef763782595df614d
* Merge "cleanup test-requirements"Jenkins2017-09-261-1/+0
|\
| * cleanup test-requirementscaoyuan2017-09-251-1/+0
| | | | | | | | | | | | | | | | | | python-subunit is not used directly anywhere and it is dependency of both testrepository and os-testr (probably was used by some tox wrapper script before) Change-Id: Ic2139ceb5a200c3b32bcc87e81fc30f208645771
* | Live Migration sequence diagramEric Fried2017-09-251-0/+1
| | | | | | | | | | | | | | | | | | | | Based on mriedem's hand-drawn version [1] (but not as pretty). [1] https://photos.google.com/share/AF1QipNpWVQKU8GK4_9wxVbiRJUqJnMzqPcBh6DvjVyBPIjjmi6ZU8r9TleQNo6pV1t9SA?key=NUl3OUFGYkRFTE8tMHhSX0lfc0Y1eEdoeHo4SUhn Co-Authored-By: Matt Riedemann <mriedem.os@gmail.com> Change-Id: I63046079cd3135b4b19c0c6745075f090d04e396
* | Updated from global requirementsOpenStack Proposal Bot2017-09-161-1/+1
| | | | | | | | Change-Id: I10ea32764a04cfe0dd8445708f04bcd184c0d308
* | Updated from global requirementsOpenStack Proposal Bot2017-09-131-6/+6
| | | | | | | | Change-Id: I043babceb3b1be03550c8e90c9abb9450d5f5cde
View Lorry Controller Status