| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
This should almost match the changes done for keystone.conf in the
commit 8d76e18a6debb4b421c5d443bc673f88abc7a8e6, but for Kilo 2015.1.0
|
| |
|
|
|
|
|
|
| |
Every component has its own idempotent script to intitiate the
databases, and they are maintained, whereas the Ansible modules
have started failing with Kilo.
|
|
|
|
|
|
|
|
| |
New component needed:
- tempest-lib 0.5.0
The following upgrade was needed:
- testscenarios to 0.4
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
New componentes needed:
- pint 0.6 as a horizon dependency
- xstatic-angular-lrdragndrop 1.0.2.3
- xstatic-magic-search 0.2.0.1
- xstatic-termjs 0.0.4.2
The following upgrades were needed:
- django-openstack-auth to 1.2.0
- python-heatclient to 0.4.0
- python-saharaclient to 0.8.0
- xstatic-bootstrap-datepicker to 1.3.1
- xstatic-bootstrap-scss to 3.1.1.1
- xstatic-d3 to 3.1.6.2
- xstatic-hogan to 2.0.0.2
|
|
|
|
|
|
|
|
| |
New component needed:
- gf-complete 2
- jerasure 2
- liberasurecode 1.0.7
- pyeclib 1.0.7
|
|
|
|
|
|
|
|
| |
Other changes:
- Rename pysinglefile to pysendfile
- Add ironic runtime dependencies as build dependencies to track some
information about them, and to be consistent with other OpenStack
components.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
New components needed
- redis-py 2.10.3
- kafka-python 0.9.3
- werkzeug 0.10.4
The following upgrades were needed:
- python-ceilometerclient to 1.0.14
- tooz to 0.13.2
- pymemcache to v1.2.9
- zake to 0.2.1
|
|
|
|
|
| |
The following upgrade was needed:
- python-barbicanclient to 3.0.3
|
|
|
|
|
|
|
|
| |
New components needed:
- pysaml2 2.4.0
Other changes:
- Remove duplicated oauthlib keeping the most recent
|
|
|
|
|
| |
The following upgrade was needed:
- python-novaclient to 2.23.0
|
|
|
|
|
|
|
|
|
|
| |
The following upgrades were needed:
- python-neutronclient to 2.4.0
- cmd2 to 0.6.7
- cliff to 1.10.1
- python-glanceclient to 0.17.1
- websockify to 0.6.1
- oslo-rootwrap to 1.6.0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
New components needed:
- ordereddict 1.1
- oslo-concurrency 1.8.0
- oslo-context 0.2.0
- posix-ipc
- oslo-log 1.0.0
- oslo-middleware 1.2.0
- aioeventlet 0.4
- trollius 1.0.4
- urllib3 1.10.4
- semantic-version 2.4.1
The following upgrades were needed:
- eventlet to v0.17.3
- sqlalchemy-migrate to 0.9.6
- httplib2 to v0.9.1
- kombu to v3.0.26
- oslo-config to 1.9.3
- oslo-utils to 1.4.0
- taskflow to 0.7.1
- keystonemiddleware to 1.5.1
- pycadf to 0.9.0
- oslo-vmware to 0.11.0
- suds to 0.4
- oslo-serialization to 1.4.0
- python-keystoneclient to 1.3.1
- oslo-i18n to 1.5.0
- oslo-db to 1.7.1
- alembic to 0.7.6
- testscenarios to 0.4
- oslo-messaging to 1.8.2
- oslo-policy 0.3.2
- glance_store to 0.4.0
Other changes:
- Use a stable version of prettytables 0.7.2 so that we know the version
number of if.
- Move netifaces to openstack-common, because it's needed for the new
version of oslo-utils.
|
|
|
|
| |
Change-Id: I3f5dcbc3484ad188366b5d9c151dbbf994efaf93
|
|
|
|
| |
Change-Id: I4f618fe3ba1c7ffe8be2226564f7c95d150d22fd
|
|
|
|
| |
Change-Id: I0fe801dda64a9a20a27e3d67aa36cb12560a1f3a
|
|
|
|
|
| |
... to avoid build failure when building gobject-introspection
Change-Id: I9efdbe7063595fe147e00b4e5335ba6a32afa582
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove the symlink that enables the default network to autostart.
It's helpful to have a default network, but starting it
automatically may create some confusion to the network if you
didn't want it running, and didn't know it was there.
I found that this network was running after configuring a OpenStack
sub-network using the same range of IP addresses and suffering
connectivity issues.
Change-Id: I0d0c399236ba06547e20c6433f115633a97b01b9
|
|
|
|
| |
Change-Id: I6ace782d08aaa476e9da07d295724734e41b9837
|
|
|
|
| |
Change-Id: If22da124a46444fbcde69b12ff50ca3d44300173
|
|
|
|
| |
Change-Id: Idd1a0c155f2872c2b4aba64fa388e505e04fe7ab
|
|\
| |
| |
| | |
Reviewed-by: Richard Maw <richard.maw@codethink.co.uk>
|
| |
| |
| |
| | |
Change-Id: I309c183ce8b9ff9d0f5ac4807244547f2cc4ddf5
|
| |
| |
| |
| | |
Change-Id: I9a523f5bbe744225b1f5fe30f29d197596337290
|
| |
| |
| |
| | |
Change-Id: I12e7c03b30da78da1eb220d2826ce0003d6efe2e
|
| |\
|/ /
| |
| |
| | |
This merge commit merges the deployment extensions and all relevant
history from morphlib into definitions.
|
| |
| |
| |
| |
| |
| |
| | |
Switching to the keystoneclient python api
gives us a more reliable means of detecting auth failure.
Change-Id: I5f734bbfe5568c855f524a3448357f7cf46ab254
|
| |
| |
| |
| |
| |
| | |
The * should not be in quotes.
Change-Id: Ieebdc7532ba1bff5ba9742f72440ed00b0c0de2a
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Commit 807e6a90876c5469d242 changed the behaviour of sysroot.write to
avoid deleting the contents of the sysroot. This was done so if you
accidentally set 'sysroot=/' it wouldn't delete your whole system.
It turns out that SDK deployments like
clusters/sdk-example-cluster.morph depended on the contents of the
directory being deleted. The system
armv7lhf-cross-toolchain-system-x86_64.morph has a bunch of files
installed by the cross-toolchain in
/usr/armv7lhf-baserock-linux-gnueabi/sys-root. Previously sysroot.write
would delete these, but since commit 807e6a90876c5469d242 it would
fail with several errors like:
mv: can't rename '/src/tmp/deployments/usr/armv7l.../sys-root/sbin'
If we use 'cp -a' instead of 'mv' then it is slower to deploy, but there
are no errors.
I am still unsure why files from the cross-toolchain system are
installed and then deleted. Although this patch fixes the immediate
issue, I don't know if it's the right thing to do. It seems better to
not install those files in the first place, if we do not need them.
This commit also removes the check for the sysroot target location being
empty. This doesn't work, because it runs /before/ the system being
deployed is unpacked.
Change-Id: I10671c2f3b2060cfb36f880675b83351c6cdd807
|
| |
| |
| |
| |
| |
| | |
os.symlink will fail if the origin file/link already exist
Change-Id: I8175c8dce699e55c3e39e35dfd45c0c19b8bd96d
|
| |
| |
| |
| | |
Change-Id: I4e7888cbff2e4708154538f8f0a48aeaa1a8a811
|
| |
| |
| |
| |
| |
| | |
This fixes morph check.
Change-Id: I5f9c8f5e73c1976b623f9a75f97b5e9aa1887c44
|
| |
| |
| |
| |
| |
| |
| | |
This is meant to add essential system files like
/etc/profile, /etc/os-release ...
Change-Id: I3d67b3a452b32205c5d3c7303d128bda80ce75de
|
| |
| |
| |
| | |
Change-Id: Ibf7cf1f81998678f9354d77f52e54344294e89f7
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The nfsboot.write deployment extension has been deprecated for a while
because it's not generally useful. It's only used for deploying
distbuild nodes to a Trove, as far as I know.
We still need to support setting up a bunch of machines that boot over
NFS from a Trove. But we can do this in a special-purpose .write
extension.
The new distbuild-trove-nfsboot.write is much more efficient than
the more generic nfsboot.write: instead of treating each system
individually (thus copying an almost identical ~2GB rootfs to the Trove
once per node) it copies the system image to the Trove once, and /then/
sets up a rootfs per node.
Upgrades are now supported, although the code assumes distbuild nodes
are stateless (as they should be) so nothing special is done for
upgrades, other than checking that there is already a version of the
given system in existance. The new extension does not create an
orig/ and run/ version of each system, because there is no need when the
deployed system is stateless.
There could be further gains in efficiency, but I don't have time to do
them right now. This write extension is full of compromises, its goal is
to better support the existing users who have a Trove and a distbuild
network deployed via NFS. It is specifically not intended to be useful
for other purposes.
Change-Id: I9a50c58b714ed272212d1d6c55b289aaa96051b1
|
| |
| |
| |
| | |
Change-Id: I0f4490d76caca802536b21085ea0d770fb8c0798
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This adds an optional 'template' option to the install-files manifest format.
A file declared as a template will be rendered using jinja2
with variables substituted in from the environment.
Change-Id: I2ed6fe58f5fff315b42b7e4ec478ada851e0a70d
|
| |
| |
| |
| |
| |
| |
| | |
This allows us to catch a case where virt-install hasn't been installed
on the host we're deploying to much earlier in the deployment process.
Change-Id: I413ad804a7e8bef4fc2d1231411e01d30d0cb9e8
|
| |
| |
| |
| |
| |
| | |
Also ensure NIC_CONFIG begins with 'network=', 'bridge=' or is 'user'
Change-Id: I3bcbd25eb2c9a05b7fa276697f97a1080cb0316e
|
| |
| |
| |
| | |
Change-Id: I1521c0bdec4d7a6812f8988a2349e66b08161de8
|
| |
| |
| |
| | |
Change-Id: I44693d15aa5e92d5f09720065788adff34f8685c
|
| |
| |
| |
| | |
Change-Id: If011a5518fd30914c89b00099b9d05cff5cd3959
|
| |
| |
| |
| | |
Change-Id: Ic715815bbad3ef1ee9ab457b62a194eaef45744c
|
| |
| |
| |
| |
| |
| | |
This adds a new config extension to allow deployments to write to /etc/hosts
by adding HOSTS_x: </etc/hosts line> to a cluster morph in a similar manner
to the fstab.configure extension.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Some lines were more than 79 characters long. This was causing
./check --full to fail on master of morph. This commit fixes the
lines in question.
Change-Id: I80969d2d89d3922e021b716c250796188d7a7f4c
|
| |\
| | |
| | |
| | |
| | | |
Reviewed-By: Richard Maw <richard.maw@codethink.co.uk>
Reviewed-By: Sam Thursfield <sam.thursfield@codethink.co.uk>
|
| | |
| | |
| | |
| | |
| | | |
Rename instead removal in case the user is already using a
10-dhcp.network file
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Use DHCP by defaul in the default interfaces:
- for /etc/networ/interfaces: "lo:loopback;eth0:dhcp,hostname=$(hostname)"
- for networkd: "e*:dhcp"
|