Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[AMBARI-22878] Update Service Group API to take list of mpack name associated with the service group #226

Closed
wants to merge 127 commits into from

Conversation

scottduan
Copy link

What changes were proposed in this pull request?

When we post the REST api to create servicegroups, each sericegroup must include one and only one mpack name.

How was this patch tested?

(1) I have written an unit test to verify it
(2) Deployed 3 node cluster and manually tested with REST API. This patch will break cluster deployment from webUI, so webUI needs another patch to support this change.

jayush and others added 30 commits May 12, 2017 12:31
…/ambari into branch-feature-AMBARI-14714"

This reverts commit 7aeef41, reversing
changes made to 38cc334.
…int for an API version (jluniya)"

This reverts commit ea3dc9a.
…on after a failed registry request (mradhakrishnan)
…iceGroups and use Servicegroup while doing Creation, Update and retrieval of HostComponents and ServiceComponents.
d0zen1 and others added 28 commits December 8, 2017 14:41
…lusterImpl and serviceConfigTypes initialization (dsen)
…lusterImpl and serviceConfigTypes initialization. Addendum patch (dsen)
… + DDL cleanup (#109) (benyoka)

* AMBARI-22776 Blueprint 3.0 Database schemas and JPA objects, DDL fixes (benyoka)

* AMBARI-22776 Revert accidental commit (benyoka)

* AMBARI-22776 Revert accidental change #2 (benyoka)

* AMBARI-22776 Fix review findings (benyoka)

* AMBARI-22776 Fix review findings #2 (benyoka)

* AMBARI-22776 remove blueprint -> stack reference, docs (benyoka)

* AMBARI-22776 fix build issues (benyoka)

* AMBARI-22776 Add MpackInstanceEntity -> MpackEntity reference (benyoka)
…155)

* AMBARI-22817. Update backend code to handle new versioning schema.(vbrodetskyi)

* AMBARI-22817. Update backend code to handle new versioning schema.(vbrodetskyi)

* AMBARI-22817. Update backend code to handle new versioning schema.(vbrodetskyi)

* AMBARI-22817. Update backend code to handle new versioning schema.(vbrodetskyi)

* AMBARI-22817. Update backend code to handle new versioning schema.(vbrodetskyi)

* AMBARI-22817. Update backend code to handle new versioning schema.(vbrodetskyi)
* AMBARI-22815 Change requiredServices in metainfo.xml (dsen)

* AMBARI 22815   Change requiredServices in metainfo xml   (renamed  scope  to  dependencyType) (dsen)
…enyoka) (#189)

* AMBARI-22776 Fix DDL issues resulting from incomplete table rename (benyoka)

* AMBARI-22776 More DDL fixes and renamings in the code (benyoka)
* AMBARI-22845 Update service metainfo schema (dsen)

* AMBARI-22845 Update service metainfo schema - changes according to review (dsen)
…tes (#213)

* AMBARI-22776 Blueprint 3.0 Database schemas and JPA objects, DDL fixes (benyoka)

* AMBARI-22776 Revert accidental commit (benyoka)

* AMBARI-22776 Revert accidental change #2 (benyoka)

* AMBARI-22776 Fix review findings (benyoka)

* AMBARI-22776 Fix review findings #2 (benyoka)

* AMBARI-22791-Update blueprint object and convert from entity (benyoka)

* AMBARI-22791-BlueprintFactory and tests (benyoka)

* AMBARI-22791 Can store and retrieve multi-instance blueprint

* AMBARI-22791 Build and unit test fixes (benyoka)

* AMBARI-22791 merge branch-feature-AMBARI-14714 and fixes (benyoka)

* AMBARI-22791 fix unit test failure (benyoka)

* AMBARI-22791 fix import error (benyoka)

* AMBARI-22791 Multi-everythin cluster template support (benyoka)

* AMBARI-22791 fix review findings (benyoka)
@scottduan scottduan closed this Jan 30, 2018
@asfgit
Copy link

asfgit commented Jan 30, 2018

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/339/
Test FAILed.
Test FAILured.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
9 participants