The trystack environment file sources credentials from OS_* env
variables and as such we need to pass them properly in tox.
Change-Id: I8abc7c4d4109a178a6547a87aec2c2dbff56b988
Add three new app_env options:
wp_latest
wp_cli
wp_importer
these can be used to override the default install locations
for wordpress and various utilities used by the playbooks,
ensuring that the playbook can be configured for use in
environments where network egress to the internet is limited.
Change-Id: I9db0d8e562fdb74c9c68cb9881d6a2bbb7e4e77a
A few folks reported that installing scsitools was throwning an error
for them because the apt cache on the system hadn't been initialized.
This patch ensures that we update the apt cache before attempting to
install scsitools.
The patch also makes the workload run faster overall: previously,
we updated the apt cache each time we installed a package. In this
patch, we break out the cache update into a separate task that runs
before any software is installed, thus eliminating several
time-consuming calls to "apt-get update".
Finally, this patch also makes the workload slightly more portable:
it replaces apt calls with package calls. Adding a new guest OS
family should just require adding a new cache update block (if
necessary for that OS) with an appropriate when statement.
Change-Id: I30ffbf2da13f22475f920328d84e64460834bcdb
Currently, the lampstack workload assumes that either you're using the
nova metadata service or that config drive is enabled globally in
your nova.conf file: there's no option to enable it on a per-environment
basis. This patch adds the ability to specify whether config_drive
should be used or not in the app_env variables, with a default value
set to "no" (which means that the new variable isn't required and that
if a user doesn't set it, he or she will get the same behavior as before
this patch).
Change-Id: I717bf5a37f98da79141af70df90feb7fd7b3f8c7
Creates a new tox env called profile in order for profiling not to be
mandatory for each workload run.
Change-Id: I699551f1d50776499ad67440bc0a6b71bd8101ef
This commit enables profile_tasks callback plugin in order to measure
the timing on the lampstack interop challenge ansible workload.
Change-Id: Ia2e40fd65836b3ef80ff11c7ed54957c20dffc8c
Using the 2GB RAM flavor supersonic in order to speed up the
execution of the demo. With 2GB the playbook is completed in
about 8 minutes (1GB takes 12 minutes).
Change-Id: I10764bdb684df565328bfa3680e7ce1db28c975a
Some internal clouds need to use http proxies to reach the
internet so they can download the packages and wordpress
installation tools.
Change-Id: I008364b17334609b8a63d6832483bcbd344ddb61
Depending on the hypervisor and disk adapter used on the guest OS,
it may be necessary to rescan the SCSI bus before a Cinder volume
that has recently been attached is seen by the OS. This patch installs
the scsitools package and rescans the bus prior to partitioning new
space from the attached volume. It is harmless for
hypervisor/adapter/guestOS combinations that don't need it (other than
taking a tiny amount of disk space and a few seconds), and makes the
workload more portable for those that do.
Change-Id: Ibb33ec359343a7093cf3f6aa0d0a7e9086b9a55b
This commit allows the usage of shade inside a virtualenvironment for
the ansible workloads and also disables StrictHostKeyChecking for the
spawned vms, which were stopping the workload to ask for key
confirmation.
Change-Id: I1df24edc6264876d4aad012d93d50eade4afe4a8
This patch fixes the following issues:
1. When OS only support flat network, no tenant network is involved.
private_v4 should be used for remote access
2. Added availability zone in addition to region so that script can
also work for the cloud with multiple regions and zones.
3. Added validate_certs so that when self signed certificates used
by a cloud, the script can also work.
Change-Id: I13f789f72eae75a0274ecf38545cb026e14e7e81
Co-Authored-By: Rohit Agarwalla <roagarwa@cisco.com>
This patch set fixed the following problems
1. Using hardcoded device names such as eth0, /dev/vdb.
These names are configurable now
2. Requires tenant networks to be avaialbe.
No longer required now
3. Terraform multiple endpoints issue can not be overcame.
Recreated the docker swarm workload test using ansible
Change-Id: Ic4bcd07caa7f7a27f7cb520fb3302fb547f085f0
These scripts will do the following against an openstack cloud:
1. Provision 4 nodes
2. Create security group
3. Add security rules to allow ping, ssh, mysql and nfs access
4. Create a cinder volume
5. Attach the cinder volume to database node for wordpress database and
content
6. Setup NFS on database node, so that web servers can share the cinder
volume space, all wordpress content will be saved on cinder volume.
This is to ensure that the multiple web servres will represent same
content.
7. Setup mysql to use the space provided by cinder volume
8. Configure and initialize wordpress
9. Install and activte a wordpress theme specified by configuration file
10.Install wordpress importer plugin
11.Import sample word press content
12.Remove not needed floating IPs from servers which do not need them.
Change-Id: I828eb4952b4fcc8bd660538adfcff60f9932eda1
Sean McGinnis