Project

General

Profile

Actions

Task #5608

closed

Improve OrientDB ansible script

Added by Luca Frosini over 8 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
_InfraScience Systems Engineer
Category:
Application
Target version:
Start date:
Nov 02, 2016
Due date:
% Done:

100%

Estimated time:
Infrastructure:
Development

Description

Orient DB ansible script should be enhanced with the following features:

Actions #1

Updated by Luca Frosini over 8 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 10

I already made part of the work to implement automatic backup. See commit bfaf045d437b40d143552820f93fcea7b6dcb1ff

Actions #2

Updated by Andrea Dell'Amico over 8 years ago

  • % Done changed from 10 to 60

Luca Frosini wrote:

Orient DB ansible script should be enhanced with the following features:

  • possibility to upgrade hook only (need an orientdb restart)

Done. You can call the playbook with the additional '--tags=orientdb_hooks'

  • upgrade selectively different instances

I don't know what do you mean with selectively. If you mean serially, I just changed the playbook to act on one instance at a time.

  • monitor instances with munin-ganglia

They are on ganglia already. See http://monitoring.research-infrastructures.eu/ganglia/?c=D4Science%20Development%20servers&m=load_one&r=hour&s=by%20name&hc=4&mc=2 (we are going towards one cluster for all the dev servers. You can filter by the hostname to get the data of the orientdb servers only).

Actions #3

Updated by Luca Frosini over 8 years ago

  • % Done changed from 60 to 10

I also parametrized the atuomatic backup configuration file. See rev 7fafb2c2e3041c8c5803bf3b9da42864c1e16470

Actions #4

Updated by Luca Frosini over 8 years ago

  • % Done changed from 10 to 70

Andrea Dell'Amico wrote:

Luca Frosini wrote:

Orient DB ansible script should be enhanced with the following features:

  • possibility to upgrade hook only (need an orientdb restart)

Done. You can call the playbook with the additional '--tags=orientdb_hooks'

Can I launch it with the following command?
./run.sh orientdb.yml -i inventory/hosts.dev --tags=orientdb_hooks

  • upgrade selectively different instances

Can I launch it with the following command if I want to decide where
./run.sh orientdb.yml -i inventory/hosts.dev -l orientdb01-d-d4s

I don't know what do you mean with selectively. If you mean serially, I just changed the playbook to act on one instance at a time.

  • monitor instances with munin-ganglia

They are on ganglia already. See http://monitoring.research-infrastructures.eu/ganglia/?c=D4Science%20Development%20servers&m=load_one&r=hour&s=by%20name&hc=4&mc=2 (we are going towards one cluster for all the dev servers. You can filter by the hostname to get the data of the orientdb servers only).

Thanks you

Actions #5

Updated by Andrea Dell'Amico over 8 years ago

Luca Frosini wrote:

Can I launch it with the following command?
./run.sh orientdb.yml -i inventory/hosts.dev --tags=orientdb_hooks

Yes, correct.

Can I launch it with the following command if I want to decide where
./run.sh orientdb.yml -i inventory/hosts.dev -l orientdb01-d-d4s

You can always limit to a specific host (or to a specific group). It does not depend by the playbook configuration.

Actions #6

Updated by Luca Frosini over 8 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 70 to 100

Andrea Dell'Amico wrote:

Luca Frosini wrote:

Can I launch it with the following command?
./run.sh orientdb.yml -i inventory/hosts.dev --tags=orientdb_hooks

Yes, correct.

Can I launch it with the following command if I want to decide where
./run.sh orientdb.yml -i inventory/hosts.dev -l orientdb01-d-d4s

You can always limit to a specific host (or to a specific group). It does not depend by the playbook configuration.

The right command is this:
./run.sh orientdb.yml -i inventory/hosts.dev -l orientdb01-d-d4s.d4science.org

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 8.91 MB)