Some versions of bash do not initialise a variable with declare -a
therefore with set -u bash can terminate the script.
Be more verbose in declaring the array if it is not set
Change-Id: I6ec2b6e986aeffe539a2ab93432fa7af9e5a4f5d
Stack.log is created by stack.sh, which is started by run.sh. Using
the pid from run.sh doesn't mean that stack.log has been created yet
so wait for the log to be created before tailing
Change-Id: I86e563478949cb7bbe0d1afd80b790ba70328e3a
We know what the GUEST_PASSWORD will be, so set it during DomU
installation; therefore if the installation fails for any reason
we have a correct GUEST_PASSWORD set rather than the obscure and
undocumented 'r00tme'
Change-Id: I684646a74f2cede43667a40556e247955e042ae4
While installing devstack in XenServer's DomU we can easily
track the output so end-users have much more visibility of
both what is going on and what (if anything!) went wrong.
Change-Id: I7d12a13cea9dffda6c1388ce711b6adf76cae72c
Github recently removed some sslv3 ciphers - wget seems to only
enable a subset of the ciphers available so fails now, but curl
continues to succeed.
Use --no-sessionid to work around
https://bugzilla.redhat.com/show_bug.cgi?id=1098711
Change-Id: Ia110bd2d0a222e438189c10a9c1a236bd7ea3d0e
Generally a ubuntu template is supplied - but in the case
where it is not, we need to source functions before sourcing
stackrc (Through xenrc)
Change-Id: I8325cf1c6f83946b7798e6d1bb8278e86831d3c4
Cirros 0.3.2 is fixing the host name setting issue, which
is required for turning on the tempest instance validation tests.
Change-Id: I1b87740ab02c4eb0a8df653a35e1f85d40abda51
Related-Bug: #1132686
Devstack doesn't need vim or locate, if someone wants to use them, they
can just install them afterwards.
Change-Id: I00f27c20c86d89465e4aefc67ed645a309c09a03
Check that function calls look like ^function foo {$ in bash8, and fix
all existing failures of that check. Add a note to HACKING.rst
Change-Id: Ic19eecb39e0b20273d1bcd551a42fe400d54e938
This commit removes some comment-outed codes. If we want to use them, we
can get them from the git repository.
Change-Id: Ie438c43d332d0631750f0ad458653fc40e23faad
As we are moving forward to test XenAPI in the gate, it is necessary to
move dom0 related modifications to be performed from domU. For this
purpose, a new user is created, and that user should be used to talk to
dom0 from domU. This change creates that user, makes it possible for
dom0 to log in to domU with that account, and configure that account to
be able to talk down to dom0.
Also move several steps to the nova xenserver plugin:
- dom0 plugin installation
- create kernels and images directory
- install console rotate script
- configure a cron to execute console rotate script
Configuration changes:
A new configuration option, DOMZERO_USER has been created, that
specifies a user account that is configured to be able to do
passwordless ssh to dom0.
Change-Id: If9de0b297a67b7cdb5de78d8dd0e8b2ca578b601
Like 'for/do' check that the while/until operator are on
the same line with the do.
Fixes some pep8 error along the way.
Change-Id: I440afe60691263365bf35310bf4212d94f30c339
we mostly have a consistent style on if/then & for/do in devstack,
except when we don't. This attempts to build a set of rules to
enforce this.
Because there are times when lines are legitimately long, and there
is a continuation, this starts off ignoring if and for loops with
continuations. But for short versions, we should enforce this.
Changes to make devstack pass are included. The fact that the
cleanup patch was so small is pretty solid reason that this is
actually the style we've all agreed to.
Part of a git stash from hong kong that I finally cleaned up.
Change-Id: I6376d7afd59cc5ebba9ed69e5ee784a3d5934a10
* Ensure that Xen setup scripts will continue to function when unset
variables are used in stackrc
* Ensure that the generic functions are sourced in all places that xenrc
(which sources stackrc) is sourced.
Change-Id: I54eba20733c2e149621b74a1387f0bef14fca12e
At the moment, xenserver installation depends on github snapshots.
Unfortunately, git.openstack.org does not have that capability. This
fix includes:
- Exit with error code, if a download fails
- create proper urls, even if they are using the git protocol
- set git base to github - so we are able to do snapshots
Fixes bug: 1259905
Change-Id: I8d0cf8bf8abb16ee0a4b138a6719409c75e7a146
Ubuntu saucy is using ext4, which means it hits a barrier
bug with certain versions of Xen, leading to a read only
filesystem.
This is bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/824089
Change-Id: I9a72b203d473dc555324d44ad7c240c80dccda15
Devstack has been increasing in complexity, and if we use too
much of our memory it can lead to fragmentation which in turn
causes a DomU error and a failure of random tests.
Change-Id: Ide9cc84625caed4e35a64a47ee1e92a6cd567651
Driven by a race condition in LVM being hit in the tempest
tests. This is a locking race between a file lock and a
semaphore which is fixed in 2.02.96-5.
Change-Id: I8a8c215c90a0602288292ffd06b7694d2db6219e
The git repositories on github for openstack are mirrors of the primary
repositories, which are hosted on git.openstack.org, so switch as much
as I can to using the primary, rather than the github mirror.
Change-Id: Idcfda49a691582055256b830c61e098f4a271339
install_os_domU.sh failed, if the FLAT_NETWORK_BRIDGE is found in
localrc. As nova looks up the network by either name-label or bridge
name, it makes sense to enable the user to specify this parameter. As an
example, if the user wants to use name-labels to specify networks, and
those name-labels could be used in domU to create bridges:
VM_BRIDGE_OR_NET_NAME="osvmnet"
FLAT_NETWORK_BRIDGE="osvmnet"
In this case, the domU will know only about a name label, so it could be
decoupled from which xapi bridges used.
This change also adds some fixes (missing double quotes).
Change-Id: I045e367ef441be20c4e8cb8af3c1149392db796b
If the JeOS template contained an exotic network configuration, the VM
prep step might fail. This patch resets the networking of the VM before
starting it.
Fixes bug 1245607
Change-Id: I921f1fdd0709d7a7760c4bb165e32f3898098bff
Give as much VCPUs to the DevStack machine as possible. First asking
xenapi about its CPU count, and as a fallback, count the CPUs in dom0.
This should result in faster test runs.
Change-Id: I1ffb99ecd435f1d7eb5754fe9cd99f0e8ceae6dc
xenbr0 is correct for most installations, but not all. Notable xenserver-core
may use a differently named device. Since we can auto detect this, remove the
config and do so.
Change-Id: I989f6ddd5ffb526ab350f263ef6fc402c596304a
Set the DHCP timeout to 120 seconds during virtual machine installation.
Some users failed to run devstack, due to a low DHCP timeout setting.
The default value is 60 seconds. This change sets the value to 120 secs,
that should give enough time for most people.
Change-Id: I15fde45ed0d005c1a8621134eee6c3c338b5be5d
The devstack setup service can update /etc/issue, displaying the status
of the installation and the VM's management IP. With this change, after
the devstack service finsihed, the login prompt will look like this:
OpenStack VM - Installed by DevStack
Management IP: 10.219.3.108
Devstack run: SUCCEEDED
DevStackOSDomU login:
This helps people to log in to their system.
Change-Id: Idd6bbd5faf9ced5618cd3e95191bfc3b89473fa2
In XenServer, devstack runs inside a virtual machine. This makes it hard
for the user to interact with stack.sh should a parameter be missing.
This change will create an upstart job (devstack) that runs
stack.sh with console enabled so user can interact with it by running
vncviewer or using XenCenter.
Logging the output is also disabled, stamp files are used instead to
detect the script run status in case install_os_domU.sh is used.
As run.sh.log is removed, standard devstack logging should be used.
The change also removes the environment settings from run.sh, as they
are not needed, they should be specified in localrc. This way user
cannot get different experiences by using unstack.sh/stack.sh or run.sh
Also a proper unstack.sh is called instead of killing screen in run.sh
Change-Id: I7eb12bd74746cc7a1db3aa9fd68ece645a50001d