cerndb / dbod-api Goto Github PK

Update influxdb basedir path from /usr/local/influx to /usr/local/influxdb

Don't start the application if the config file has wrong options.

Check how to deploy required modules

• PEX executable?

After the refactoring there's a missing import to provide the error codes:

$:~ $ httpu https://dbod-api-test:5443/api/v1/host/aliases/db-50010                                                                                      
HTTP/1.1 500 Internal Server Error
Content-Length: 359
Content-Type: text/plain
Date: Fri, 05 Aug 2016 13:03:18 GMT
Server: TornadoServer/4.2

Traceback (most recent call last):
  File "/home/dbod/venv_qa/lib/python2.7/site-packages/tornado/web.py", line 1413, in _execute
    result = method(*self.path_args, **self.path_kwargs)
  File "build/bdist.linux-x86_64/egg/dbod/api/hostaliases.py", line 35, in get
    raise tornado.web.HTTPError(NOT_FOUND)
NameError: global name 'NOT_FOUND' is not defined

While the name is actually maybe clearer for the DB schema, if we expose the vgroup name the result can't not be used directly later on without mapping it to the right value

Attributes should be shown in a similar way as volumes when getting an instance.
Also a way to add, delete and modify them should exist.

In Oracle the DATE type includes the TIME, and it is not set in PostgreSQL when using the Foreign Data Wrapper.
Probably we should use a different type in the foreign table, as DATETIME.

Separate/refactor handlers and dbops modules to better organize methods when we start adding managing code for the Web Application endpoints and the Oracle database backend.

The old entity endpoint functionality has been moved to metadata/entity and maintaining the name while changing the functionality only creates confusion

This view needs to show the list of ip-aliases per host

• url
• port
• credentials

This would allow us to use the same structure sql file to create production and test databases, instead of having different files, which could introduce inconsistencies in one of them.

This issue domes from #19.

As title says, There is a permissions error happening when the log file reach rotation point.

May be explained here: https://stackoverflow.com/questions/17043814/why-am-i-getting-ioerror-errno-13-permission-denied

When running the application we could specify a parameter with the path of the config file. If not specified it would use the default one (in /etc/dbod/api.cfg).

Creation of a dataset to import in Posgres database to run the tests in Travis.

The username colunm is truncated to 1 char.

• This API endpoint needs to return a valid resources.xml file to use in the Rundeck

The "host" value in instances should be shown as an array in the metadata, as it could contain (in future) multiple values.

Fix check on this methods DB operations (causing exception by checking for response for server instead of number of affected rows)

We need to discuss with the Nile team to consolidate the backing db design

The stored procedure/view generating the aliases by convention is not substituting the underscores in the
db_name for dashes

Optional endpoints (Rundeck, FIM, ...) will be activated or not depending on the presence
of the right configuration file sections.

This change will allow us to have different columns and names for each type of instance.

The atomicity of the PostgREST calls brings up the problem of how to manage rollbacks for the external API level. As recommended by the PostgREST author, one option is to map complex actions
to DB stored procedures and call those through PostgREST.