In an effort to support JSON Path variable
queries, we need to:
* Pin to MySQL 5.7
* Use JSON column type
* Use a newer SQLAlchemy library.
Change-Id: I98ae021c9cd9755f51e67e56135db164e8ae1f50
Partial-Bug: 1671116
Depends-On: I36b7ae9cf68aeef0e5dbcb1f17db52b81efd6ffe
So far we have been using external mysql command
to insert project/user to bootstrap the process.
This caused much frustration since operators needed
to insert records in the db. This patch adds commands
to dbsync to allow creating project/users. This method
also takes care of association_id.
To initiate a bootstrap:
craton-dbsync --config-file=craton.conf bootstrap
which will create a project with a root user.
Users using Dockerfile can look at docker logs
after creating the container to find this info.
Closes Bug: 1670561
Change-Id: I9372961ca6623d530d7844b9f38aade544d961e8
This change moves craton to a port that is not in use according to
/etc/services and is not being consumed by any other OpenStack service
as defined here: [
https://docs.openstack.org/newton/config-reference/firewalls-default-ports.html
]. This should allow other deployers to leverage craton in an way that
does not conflict with other OpenStack services already running in
production.
Change-Id: I2d0432b4c608cf11538d7b8f267eaf7be763204c
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
Currently its bound to 127.0.0.1 for testing
purposes we need access to mysql inside the
container such that we can modify the tables
directly using mysql client. This patch adds
a line in dockerfile to bind mysql to 0.0.0.0
Change-Id: I5f3ea69e70b193d36f9782d0426e79cf80843110
Adds --pull flag to build process such that
cache is always used if there is not new image
available. If a new image exists that gets pulled.
This ensures we always run latest image on 16.04
Change-Id: I5cc6e6d9f9782ed99d01e088a88ce1f960d502cd
Closes-Bug: #1644294
Although the original Dockerfile was quite simple and straightforward,
it wasn't necessarily fast for doing repeated builds (local testing).
By putting things first which rarely change (pip install of base
requirements, for example), we can take advantage of docker caching to
skip redundant build steps.
Change-Id: I2fd961d8ad5c35280ccb23b00767acb6b5269993
When looking at integrating craton with Keystone, it became apparent
that we could not store project_id's from Keystone in Craton's Database.
All of our project_id columns are Integers and Keystone uses UUIDs by
default. As a result, we've switched Craton to use UUIDs for Project IDs
and tweaked the docker tooling and install documentation.
Change-Id: I4b84f6ac23ffd128e0060fd929c6f0c60ee16d52
Closes-bug: 1634191
-t will allow using psudotty such that we get
line buffereing and logs show up on console right away.
As suggested in docker issue: 18327
Change-Id: Ife163ab29421d568bc246027d579c78b570554c9
- Since its not just inventory, and the service
now includes everything craton the file names
should reflect the same.
Fixes Bug: 1630784
Change-Id: I0fb77942a92bbf2aacbf2c4a7d0c3104ed8bebfe
In order to try or test the api it is very
useful to have some dataset ready in the inventory.
This patch adds a script to generate the fake data.
Also, adds a comment on the Dockerfile to inform users
to use it with the image.
Change-Id: I3401b2b1ff4784a2505cd9d14c56e3d53ca8d5a0
Andreas Jaeger