This means it is fuel-setup-network no more and has been renamed to
more general fuel-setup. For the same reason MasterNode became
a top-level class that is expanded by particular commands with
required methods. Script requires now '-n' argument that specifies
environment name.
- 'network' works as old fuel-setup-network did.
- 'repos' expects MOS_REPOS and UBUNTU_LATEST environment variables
to be set in the same way fuel-qa does it
- because user might want to run both of them, running verify_network
has been split into its own command
The 'version' property of MasterNode requires requests library. All
other dependencies has been bumped to latest releases.
Change-Id: I9d0f5ba0a17b5821f8fb86b6a089c7d8adf802e1
Python 2.6 support would be dropped by
Infra team from mitaka,CI would no longer be testing it,
so projects should drop it too.
Change-Id: I20288880b29061920a54c6c1cc8618b67e70526a
OpenStack projects are no longer being tested under Python 2.6, so
remove the trove classifier implying that this project supports 2.6.
Change-Id: I5deb330ac5eb7aaff846eaf41aa2c036926aad5e
When a development environment is under a proxy, tox is failed even if
environment variables of the proxy are set.
This patch fixes this problem.
Closes-Bug: #1525115
Change-Id: Iff6d29445cbb88c041c58e87720300ef8ec38265
* fuelmenu-rsync is now available. It allows to rsync code from root of
fuel-menu repository to master node.
* Refactored RsyncCommand - moved it from docker module to command
module, so it can be used not only for docker-related rsyncing.
Change-Id: I3dcfa2d00a22368ce40e8457c3aacb72700bc54f
Closes-bug: #1522441
fuel-setup-network is a simple script that makes setting up networking
on master node deployed via fuel-devops easier.
It takes environment name as mandatory argument and allows to specify
environment id with -i (or --id).
Change-Id: I50fc4bb9f55baad8fc1e5606ec968ed207fb340a
Astute gem filename needs to match the name on master node in order for
astute container to run updated code.
Change-Id: I2ad3e4c7e879c3228db3e76a54b19996bc821455
Closes-Bug: #1514740
In a consensus reached in a proposal for code review process
change [1], and proposed team structure policy document [2],
adding MAINTAINERS files in repositories.
Please note, that this file is written in YAML format in order
to allow further automation around code review process.
[1] http://lists.openstack.org/pipermail/openstack-dev/2015-August/072406.html
[2] https://review.openstack.org/#/c/225376/
Change-Id: Ib89e8b36136ac64f01603efbc234a2e85a999edf
This change provides possibility to use vagrant-libvirt
plugin, whichby default uses KVM hypervisor. NFS is used
here for syncing /vagrant directory.
To run Vagrant with libvirt provider:
vagrant up --provider=libvirt
Change-Id: I90383717de1f04a90bdaa18d6eb1561fb77cc061
The Oslo libraries have moved all of their code out of the 'oslo'
namespace package into per-library packages. The namespace package was
retained during kilo for backwards compatibility, but will be removed by
the liberty-2 milestone. This change removes the use of the namespace
package, replacing it with the new package names.
The patches in the libraries will be put on hold until application
patches have landed, or L2, whichever comes first. At that point, new
versions of the libraries without namespace packages will be released as
a major version update.
Please merge this patch, or an equivalent, before L2 to avoid problems
with those library releases.
Blueprint: remove-namespace-packages
https://blueprints.launchpad.net/oslo-incubator/+spec/remove-namespace-packages
Change-Id: I85d65fac6119d66755fe490d90fe1c48124935f7
This is because we will be using SSH hops to rsync into slave nodes.
Fabric doesn't seem to support this out of the box.
Change-Id: Idf43d7b6c35324ade9be3467cee7c664833a38a8