map-services will be removed on dib v2 branch, but
tripleo still relies heavily on it. To prevent breakage,
copy the script to the internal element using it.
In the future, all elements will need to be migrated
to new svc-map, but it is a massive change.
Change-Id: I9f450de66044123ab07fa498b68f744d1029089a
Currently on ubuntu we are sending all app logs to syslog which munges
them all together into /var/log/syslog. This makes debugging a somewhat
painful experience.
Change-Id: I89f9ddc168f08b90cece7cf5af2e032b2c4f5371
It have to be separate elements because installation differs depending
whether mysql or mariadb is used.
Change-Id: I9299b8e21a5ea2ff13ab9f11d851703a67c6b130
We install pip with get-pip.py and use this to install virtualenv. This
is done as part of the new pip-and-virtualenv element. All elements that
need pip or virtualenv should use this element to install them.
Our motivation is that we need to talk to a pypi mirror generated with
a recent http://github.com/openstack-infra/pypi-mirror This mirror
caches some 'wheels' that the previous version of pip & virtualenv
can't install.
virtualenv contains its own version of pip that is used for all
virtualenv environments.
Change-Id: I282fd8fffc8d5707a078f78f2b4571138d7266f3
If 1.11 is used with --system-site-packages pip won't be installed in
the virtualenv, leading to an activated virtualenv not using pip and
thus not installing anything into the virtualenv.
Change-Id: Ic9907438b17ca9a32fbeccc4ca806b8b43f41cd1
Partial-Bug: #1266513
Split out the code which enables services to start on boot into
a new os-svc-enable script. This script is currently called by
os-svc-deamon so that services automatically start on first boot
(as is the case with os-svc-install)
The motivation here is to decouple service installation and enabling
so that we can eventually avoid starting services on first boot
until after they are configured. Auto starting services on boot like
we currently do is causing lots of log ERROR messages, etc.
Change-Id: I66d4660c169f5918e924eab1876134891c3a24a1
Upstart doesn't have its own service enable/disable mechanism. We are in
need of a facility to enable/disable services without writing to /etc at
runtime to enable a readonly root for image based updates. This command
will be used by later changes to have a generic service enable/disable
mechanism for all init systems.
Change-Id: I931281988aa746f93de190794f68f4c9e628db19
Running just 'pip install -U distribute' can leave setuptools in a
half migrated state on Fedora/RHEL/CentOS. Following it up with 'pip
install -U setuptools' corrects the problem and leaves you with
distribute 0.7.3 and the latest setuptools.
Change-Id: I3652e84fcfdc39065b6b86fc85b6b6602601d7e9
os-svc-install is meant for any image, not just those installing a new
cloud, but it was only working so far because we've only been building
boot-stack images routinely.
Fix bug 1198701.
Change-Id: I4fd170333bb36b5bf9b0c33e224c43db2d4235f5
This allows openstack services to be git/pip installed
without installing any startup scripts.
This is useful for keystone-db or nova-db elements, for
example, where the service must be installed to perform
database migration, but no service start scripts need
be installed.
Additionally, add a tool to create openstack sql databases.
Use openstack pypi mirror:
Use the openstack pypi mirror for openstack service
installation. It's much faster than pypi.org.
Also, pip install $svc_repo/tools/pip-requires first,
if it exists, which is required to pick up oslo.config.
Change-Id: I72751d4da59f8597d20aea2f27a9dfabe2f63a8f
Move common openstack service installation operations
into a new script `os-svc-install`, which simplifies
the elements for openstack services.
Change-Id: Ied8ac3278e7fe8af76e24748ec4e598a84afa03c
Ghanshyam Mann