[IGNITE-5145] Support multiple service deployment in API

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0
• Fix Version/s: 2.3
• Assignee: Denis Mekhanikov
• Reporter: Dmitry Karachentsev
• Created: 03/May/17 07:49
• Updated: 07/Sep/17 20:16
• Resolved: 07/Sep/17 17:49

Description

IgniteServices should support possibility of deploying batch of services at once to speed up deployment.

It implies the following API changes:

• introduce ServiceDeploymentException, indicating that some problems were encountered during deployment process and containing a list of failed services;
• add deployAll(Collection<ServiceConfiguration>, boolean) and deployAllAsync(Collection<ServiceConfiguration>, boolean) methods to IgniteServices interface. Boolean flag shows whether we should follow "all-or-none" failing policy, or allow partial deployments.
  Also all async methods in IgniteServices should not throw any exceptions, but return a future, whose get method should throw an exception if any errors occur during deployment.

Issue Links

• links to: GitHub Pull Request #2450
• links to: GitHub Pull Request #2594