Package: oar-cli
OAR Command line interfaceInstallationRequirements:python >= 2.7python-mysqldb/python-psycopg2 (for oar database archive)You can install, upgrade, uninstall oar-cli with these commands:$ pip install [--user] oar-cli
$ pip install [--user] --upgrade oar-cli
$ pip uninstall oar-cliOr from git (last development version):$ pip install git+https://github.com/oar-team/python-oar-cli.gitOr if you already pulled the sources:$ pip install path/to/sourcesOr if you don’t have pip:$ easy_install oar-cliOAR Database archiveThis script allow you to copy your OAR database to another database for
archiving purposes.In order to do this, the tool offers two commands that can be launched
regularly to simplify both databases maintenance.SyncThis command is used to copy data to archive on the archive database. It is
only useful when handling asmall amount of data.If your database is too big, we advise you to first create manually your
archive database with a dump. If your archive database does not exist yet, and
if it will be located on the same machine than your current OAR database, the
‘sync’ command will clone the OAR database to the archive (extremely efficient
for postgresql).UsageUsage: oar-database-archive sync [OPTIONS]

  Send all resources and finished jobs to archive database.

Options:
  --chunk INTEGER        Chunk size  [default: 10000]
  --ignore-jobs TEXT     Ignore job state  [default: ^Terminated, ^Error]
  --current-db-url TEXT  The url for your current OAR database.
  --archive-db-url TEXT  The url for your archive OAR database.
  -h, --help             Show this message and exit.Jobs unfinished (i.e. current jobs) are not copied by default. The symbol ‘^’
means negation.For more information about the URL format, please refer to the SQLAlchemy
documentation:http://docs.sqlalchemy.org/en/latest/core/engines.html#database-urlsExamples$ oar-database-archive sync --archive-db-url postgresql://oar:oar@server:5432/oar_archiveThis command will dump your current OAR database (configured in oar.conf) in
the given database. The second run will only copy the missing rows.From postgresql to mysql:$ oar-database-archive sync --current-db-url postgresql://user:password@server1:5432/oar \
                        --archive-db-url mysql://user:password@server2:3306/oar_archiveFrom mysql to sqlite:$ oar-database-archive sync --current-db-url mysql://user:password@server1:3306/oar \
                        --archive-db-url sqlite:////tmp/archive.dbPurgeThe purge command is used to delete jobs and resources (previously archived)
from the current OAR database.UsageUsage: oar-database-archive purge [OPTIONS]

  Purge old resources and old jobs from your current database.

Options:
  --ignore-jobs TEXT       Ignore job state  [default: ^Terminated, ^Error]
  --max-job-id INTEGER     Purge only jobs lower than this id
  --ignore-resources TEXT  Ignore resource state  [default: ^Dead]
  --current-db-url TEXT    The url for your current OAR database.
  -h, --help               Show this message and exit.These options are almost similar. By default, all finished jobs are purged. You
can use--max-job-idto ignore all jobs with an ID greater than the ID used
as parameter..All resources in ‘Dead’ state are also purged. If we do not want to purge
resources, the filter--ignore-resourcesallneeds to be used.Example$ oar-database-archive purge \
    --ignore-resources ^Dead \
    --ignore-jobs ^Terminated  --ignore-jobs ^Error \
    --max-job-id 100000 \
    --current-db-url postgresql://scott:tiger@localhost/oar_prod_databaseThis commande is used to delete all resourced marked as ‘Dead’ and all finished
jobs (and associated events) with a ID smaller than 100000.OAR CLI changelogVersion 0.3.5Released on July 08th 2015Emptied admission_rules table before migrationUsed postgresql binary COPY by defaultSplit big queries with BETWEEN clause to improved performance and avoided mysql crashesVersion 0.3.4Released on July 07th 2015Removed OFFSET sql clause from big queries to avoided mysql crashesVersion 0.3.3Released on June 24th 2015Added--confoption to used custom oar configuration fileUsed postgresql COPY with csv format by defaultFixed modify nullable operation during schema upgradeVersion 0.3.2Released on June 23rd 2015Minor bug fixesVersion 0.3.1Released on June 23rd 2015Fixed project description in PypiVersion 0.3.0Released on June 23rd 2015Renamed the project to OAR CLI !Addedoar-database-migratescript.Added--schema-onlyand--data-onlyfeatures tooar-database-migratescriptSupported postgresql bulk insert using COPY clause to improved performance.Handled database connection errors.Managed the schema upgrade with alembicFixed max_job_to_sync query if we want to copy all jobsVersion 0.2.0Released on June 05th 2015Database ArchiveMade deterministic order_by to sync queries in order to avoid IntegrityError during copy (Fixed #1)Handled IntegrityError during bulk INSERT (Fixed #1)Used Postgresql DELETE with the USING clause to improve performance (Fixed #2)Made the delete orphan queries faster with LEFT JOIN in Mysql (Fixed #2)Removed count query when performing a bulk delete query (Fixed #2)Configured debug logging to displayed SQL queriesAdded option to disable pagination during sync operationDisplayed default values in the CLIVersion 0.1.2Released on May 05th 2015[database-archive] : Added ability to ignore all resources during purgeVersion 0.1.1Released on May 04th 2015Fixed pypi packageVersion 0.1.0First public preview release.