When a cloud image only has root user, deploy wordpress will fail
without the flag since wordpress by default does not allow root user
to deploy artifacts. Adding this flag will allow root and non root
users to be used to deploy wordpress
Change-Id: Icf0a62bdfc5db5d0e14752908477288516143eb9
This commit adds a spec folder within documentation. This would be
moved under its own project if it starts growing big enough.
Change-Id: I54b8402b35ff72577f1b949d9a081752cb08a13b
This should resolve two problems:
* Ansible cannot find `userdata.j2` due to incorrect path used
* Allow the template to be actually rendered as template instead of
being loaded as plain file without evaluation
There's another solution - simple move of `/roles/apply/templates/`
to `/roles/apply/files/templates/`. I have favored this one though
to make it possible to use Jinja2 expressions in the template file,
which I believe was the original creator's idea.
Change-Id: I268e4967597508e15d7de76051e097a43a0bfeac
1. mysql 5.6+ configuration
2. noting supporting ubuntu 16.xx
3. different platform code mixing
4. tags so that you can run selected tasks by role
5. uses openstack superuser theme and posts
6. haproxy used old configuration format
Closes-Bug #1654240
Closes-Bug #1649949
Change-Id: Ibbde92ed4fc18f85d004d54f00d3547c3df8fcc4
The lessions learnt document has been created on etherpad, this
patch took all the content from that document, edited, reformatted,
and also added more few items I learnt from my own experiences of
developing these workload scripts.
Change-Id: I3ab9cacd6369c3cbcfc912707a9e844ae7c4fc2d
