Skip to content

This project convert from BARMAN command to RESTful api. Barman API support full future and all versions of BARMAN.

License

Notifications You must be signed in to change notification settings

emin100/barmanapi

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

13 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

PostgreSQL Barman RESTful Api

Build Status

This project convert from BARMAN command to RESTful api. Barman API support full future and all versions of BARMAN.

##Before you start Barman API needs a directory to store data.

  • Barman API Server
    api@barmanapi$ sudo mkdir /var/lib/barmanapi
    api@barmanapi$ sudo chown user:user /var/lib/barmanapi
    api@barmanapi$ sudo chown user:user /etc/barmanapi.conf
  • Barman Server
barman@backup$ sudo chown barman:barman /etc/barman.conf

####Use with the BARMAN server and Barman API Server in the same machine You don't need anything. ####Use with the BARMAN server and Barman API Server in the diffrent machine Barman API using SSH connection to BARMAN server. You must provide ssh connection BARAMAN Server and Barman API server with trust connection. ######If you don't have a ssh keygen

api@barmanapi$ ssh-keygen

######Trust connection to BARMAN server

api@barmanapi$ ssh-copy-id barman@backup

System requirements

  • Linux/Unix
  • Python > 2.6
  • Python modules:
    • Flask
    • Flask-HTTPAuth
    • Flask-Script
    • pyjwt
  • ssh

INSTALL

####From pip

api@barmanapi$ sudo pip install barmanapi

####From source

api@barmanapi$ git checkout https://github.com/emin100/barmanapi.git
api@barmanapi$ cd barmanapi
api@barmanapi$ sudo python setup.py install

Default User

Basic Auth default user

Username:memin Password:1258

####Start Server

api@barmanapi$ barmanapi runserver

Note: First usage, must call http://host:port/barman/reload?token=XX

Basic configuration

####Directory List ######/var/lib/barmanapi/ Store BARMAN API data files.

  • archive: All active folder compress by month
  • active : Async commands and results store in directory
  • config : Barman commands and config parameter templates store in directory
  • garbage: Temp directory
  • logs : All logs store in directory

######/usr/share/barmanapi/ Store some config files

  • client.conf : Store user information. You can change this file location in barmanapi.conf file.
  • man.conf : Store man parse options. Do not change this file location and content.
  • template/config_change_template : Store code template. Do not change this file location and content.

####BARMAN API Config (/etc/barmanapi.conf)

#Don't delete any option from this file. All option is using. If you don't need anyone, blank value this option
#User store location and pasword hash secret.
[user]
config_file=/usr/share/barmanapi/client.conf
#if change your secret all password is unusable. You must change all of password hash in user config_file
secret=89660c74da48ddd4efbe4d3c8f8150de
  
[application]
store_directory=/var/lib/barmanapi/
host=0.0.0.0
port=1935
#In production, must be False debug parameter.
debug=True
  
#Barman Server Settings
[barman]
config_file=/etc/barman.conf
command=/usr/bin/barman
remote=true
#If remote is false, you can blank remote_ssh option.
remote_ssh=ssh barman@backup
async_command=['backup','cron','recover']
  
[auth_token]
secret=Deneme
algorithm=HS256
#Token life time(second). At the end of this time token is unusable.
token_life=6000
  
[log]
#Stored last x log file
backup_count=5
#Log file truncate size(Bytes)
max_bytes=20000

####Client config file

[memin]
password = 26588e932c7ccfa1df309280702fe1b5
access = []
deny = []

Client file is basic conf file. You can store password, access api urls and deny api urls.

  • Section is a username(Like memin)
  • Password hash with your secret (described in your barman api config file).
  • access is an array.
    • Blank array, user can call all APIS.
    • Example access['barman','auth/user/list']. This example user access all /barman module api calls and only auth/user/list api call.
  • deny is an array.
    • Deny some api calls. Example deny['barman','auth/user/list']. User access out of this apis(All /barman module api calls and only auth/user/list api call).

REST API

Authentication & Authorization

Rest: /auth
Auth Model: Basic
######/auth/token Auth: Yes
Parameters: No
Return: token

Get a token for other rest api calls

######/auth/user Auth: Yes
Parameters: No
Return: json list

Current user access and deny parameters

######/auth/user/list Auth: Yes
Parameters: No
Return: json list

Get rest user list ######/auth/user/change Auth:Yes
Parameters:

  • username: Required
  • password
  • access
  • deny

Return: updated user properties

Change user properties

######/auth/user/add Auth:Yes
Parameters:

  • username: Required
  • password: Required
  • access
  • deny

Return: added user properties

Add user

####CONFIG Rest: /config
Auth Model: Token Based
Description: You can change barman or barmanapi config file in rest api. If you want to use this future, you give write access to config files.

  • For Barman API
api@barmanapi$ sudo chown api:api /etc/barmanapi.conf
  • For Barman
barman@backup$ sudo chown barman:barman /etc/barman.conf

######/config/barman Auth:Yes
Parameters:

  • token: Required

Return: Barman configuration list.

######/config/barman/help Auth:Yes
Parameters:

  • token: Required

Return: Barman configuration paramater list and descriptions.

######/config/barman/reload Auth:Yes
Parameters:

  • token: Required

Return: Get Barman configuration parameters list and make configuration template

######/config/barman/change Auth:Yes
Parameters:

  • token: Required

Return: Change Barman configuration
Example:

Note: Must be restart barman

######/config/barmanapi Auth:Yes
Parameters:

  • token: Required

Return: Barman API configuration list

######/config/barmanapi/change Auth:Yes
Parameters:

  • token: Required

Return: Change Barman API configuration
Example:

Note: Must be restart barmanapi

####HISTORY Rest: /history
Auth Model: Token Based
######/history/list Auth:Yes
Parameters:

  • token: Required
  • past: Optional - YYYYmm (Example : 201602). Get past archive history.

Return: async command result list

In month executed async commands list. If you want to past history, you must be send past parameters.
Example:

######/history/result Auth:Yes
Parameters:

  • token: Required
  • ticket: Required

Return: Sync command result

Ticket related async command result.

####BARMAN API Rest: /barman
Auth Model: Token Based
Description: Execute barman commands. If you want to see parameter list, you use /barman/command/help url or full api list /barman/help url.

Example:

About

This project convert from BARMAN command to RESTful api. Barman API support full future and all versions of BARMAN.

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages