Age | Commit message (Collapse) | Author | Files | Lines |
|
It is currently 20. It should be 200.
I'm also fixing HeatFiles.hbm.xml to match a recent
schema fix (SO-247).
Issue: SO-264
Change-Id: I2bd6fc480310abc80b1a189a83b1e3f73c90149b
Signed-off-by: Rob Daugherty <rd472p@att.com>
|
|
Updated the hibernate hbm.xml files to correct the following issues:
1) Timestamps had generated="insert" but hibernate was not auto-populating
the timestamp value thus the DB was generating an exception. Modified
the definition of this field to cause hibernate to provide the default
value of CURRENT_TIMESTAMP. This impacted most of the hbm.xml files.
2) While running junit tests, the following message appeared in the log
underneath most of the hbm.xml files:
Recognized obsolete hibernate namespace
http://hibernate.sourceforge.net/. Use namespace
http://www.hibernate.org/dtd/ instead. Refer to
Hibernate 3.6 Migration Guide!
Updated most of the hbm.xml files, changing the namespace per the
guide. Note: a couple of the files were already correctly configured.
Change-Id: Id96775b7bd7a42da0c00e208e33aed6fa96ab996
Issue-Id: SO-215
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
UT-Step6
IssueId: SO-172
Change-Id: I18ba0ebfd372b06e688e5a1b6d9e8b8d34cab227
Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
|
|
|
|
|
|
The foreign key we fixed in the VNF_RES_CUSTOM_TO_VF_MODULE_CUSTOM
table is blocking distribution of the model. The insert that's
failing is:
insert into VNF_RES_CUSTOM_TO_VF_MODULE_CUSTOM (
VNF_RESOURCE_CUST_MODEL_CUSTOMIZATION_UUID,
VF_MODULE_CUST_MODEL_CUSTOMIZATION_UUID)
values (?, ?);
The error is: "foreign key constraint fails"
Issue: SO-180
Change-Id: I8d98bde144eb666430632b6089d8d27d66527884
Signed-off-by: Rob Daugherty <rd472p@att.com>
|
|
UT-Step4
IssueId:SO-172
Change-Id: I33f1cb757f038085f649eaa836da90e32ef04814
Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
|
|
UT-Step5
IssueId:SO-172
Change-Id: I008b3587e68350dcc1c5a14069afbf8f0153a35b
Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
|
|
Corrected a foreign key definition in the
VNF_RES_CUSTOM_TO_VF_MODULE_CUSTOM table.
Issue: SO-180
Change-Id: I4dfb51ac615ca1dab19fbf3e0be728b2752e06bd
Signed-off-by: Rob Daugherty <rd472p@att.com>
|
|
UT-Step3
IssueId: SO-172
Change-Id: Iac580a8936104078e529db9fdab178e0686eae51
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
|
|
UT-Step2
IssueId: SO-172
Change-Id: I4aa763ad9cf723f969b9fd9a9ab7eca5b303ade0
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
|
|
|
|
UT-Step1
IssueId: SO-172
Change-Id: I82c9095d25da5fec5b79360e54a0326b8b86ffc0
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
|
|
IssueId: SO-172
Change-Id: I8429cb938e786c527fad00067dc733fc02997639
Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
|
|
IssueId: SO-172
Change-Id: I459ab18a5dccb3e773278db933f97b50f87d0e76
Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
|
|
IssueId: SO-164
Change-Id: I87915bcdab1457c766d53157305e8e2b68a7b4d8
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
|
|
Issue-Id:SO-118
Change-Id: I97cfd892ae5d13003b0b37509ac91be863dbd55e
Signed-off-by: rama-huawei <rama.subba.reddy.s@huawei.com>
|
|
Issue-Id:SO-118
Change-Id: I979370f8d3ffa0382856353aa189610d24dcd20c
Signed-off-by: rama-huawei <rama.subba.reddy.s@huawei.com>
|
|
https://sonar.onap.org/component_issues?id=org.openecomp.so%3Aso#resolved=false|severities=MAJOR|fileUuids=AV3Bnsck5bp_wwmIVB7V|rules=squid%3AS2293%2Csquid%3AS1161
Issue-Id:SO-118
Change-Id: Iea674f0d8f4f0b9cef346f8c5315b02767ae65f4
Signed-off-by: shashikanth.vh <shashikanth.vh@huawei.com>
|
|
A foreign key definition for the VNF_RESOURCE_CUSTOMIZATION table was
wrong. I fixed VnfResourceCustomization.hbm.xml
Change-Id: Ie52f0b495d100d28bcb053ba46cb8e680a4e95a2
Issue-id: SO-147
Signed-off-by: Rob Daugherty <rd472p@att.com>
|
|
Issue-Id : SO-117
Change-Id: Icdc64605b475e20af7e871135af327f7d0e38792
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
|
|
IssueId: SO-120
Change-Id: I429381791a209b421349baa9a4adaa32c6e27958
Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
|
|
This commit rebases changes from openecomp-mso/internal-staging-1710 up to and including this codecloud commit:
54483fc6606ddb1591a2e9da61bff8712325f924
Wed Sep 6 18:12:56 2017 -0400
Rebasing was done on a branch on top of this commit in so/master in ONAP:
93fbdfbe46104f8859d4754040f979cb7997c157
Thu Sep 7 16:42:59 2017 +0000
Change-Id: I4ad9abf40da32bf5bdca43e868b8fa2dbcd9dc59
Issue-id: SO-107
Signed-off-by: Arthur Martella <amartell@research.att.com>
|
|
define default recipe mapping for any 'source' at level of 'service' and 'network' resources."
|
|
The top level pom will contain:
<groupId>org.openecomp.so</groupId>
<artifactId>so</artifactId>
Child modules will contain:
<parent>
<groupId>org.openecomp.so</groupId>
<artifactId>so</artifactId>
<version>1.1.0-SNAPSHOT</version>
</parent>
<groupId>org.openecomp.so</groupId>
<artifactId>some-child-artifact</artifactId>
Note that the groupId for the direct child module will be
the same as the groupId for its parent.
Issue: SO-21
Change-Id: I1976819df459d92937c6a4780959c32599dc3e71
Signed-off-by: Rob Daugherty <rd472p@att.com>
|
|
There are Linux Foundation rules (enforced by nexus) that I still
don't really understand. I'm convinced this is absolutely true:
The groupId of every artifact in a project MUST begin with:
org.openecomp.<project>
--or--
org.onap.<project>
The top-level artifact is no exception. So for example, this is
NOT allowed:
<groupId>org.openecomp</groupId>
<artifactId>so</groupId>
Here's what I'm trying now. The top level pom will contain:
<groupId>org.openecomp.so</groupId>
<artifactId>so-parent</artifactId>
Child modules will contain:
<parent>
<groupId>org.openecomp.so</groupId>
<artifactId>so-parent</artifactId>
<version>1.1.0-SNAPSHOT</version>
</parent>
<groupId>org.openecomp.so</groupId>
<artifactId>some-child-artifact</artifactId>
Note that the groupId for the direct child module will be the
same as the groupId for its parent.
Issue: SO-21
Change-Id: I0d3cd2eb7a1883e23e3c0878ee7fa3dd4a7d55b2
Signed-off-by: Rob Daugherty <rd472p@att.com>
|
|
More problems encountered since mso repos were renamed.
We now have found that this declaration in the top-level so pom
causes the deploy to fail with a 403 Forbidden error:
<groupId>org.openecomp</groupId>
<artifactId>so</artifactId>
We are changing this to:
<groupId>org.openecomp.so</groupId>
<artifactId>framework</artifactId>
Issue: SO-21
Change-Id: I4e21d689c73c5071bde725127bb81482ce3d91f9
Signed-off-by: Rob Daugherty <rd472p@att.com>
|
|
default recipe mapping for any 'source' at level of 'service' and 'network' resources.
Change-Id: I42dafa343e2e65c6e892c21de5f3f1131890b24e
Signed-off-by: eyalholz <eyalh@amdocs.com>
|
|
Since the repositories were renamed from "mso" to "so" the
artifact group IDs in the poms must be updated to match.
Issue: SO-39
Change-Id: I617fe738a77d0f6c1d1cc0ac9474fb753f4e234c
Signed-off-by: Rob Daugherty <rd472p@att.com>
|
|
Second rebase containing additional features for MSO + total reworking
of the BPMN structure + Notification flow can now be added at the end of
some BPMN flows
Change-Id: I7e937c7a0ba1593ca85e164a093f79c7e38b6ce0
Signed-off-by: Determe, Sebastien (sd378r) <sd378r@intl.att.com>
|
|
Remove the unnecessary use of boxed types
in MavenLikeVersioning.
Change-Id: I8b96db9e753f80860b95b84473bb8d2b61e2328e
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
|
|
Update the maven depenency for sdc-distribution-client to cooperate with the sdc changes.
Change-Id: I2da936e5c40cb68c7181bb78307192dd5655b5dc
Signed-off-by: xg353y <xg353y@intl.att.com>
|
|
Change-Id: Id054e7a04ce88450c3cfe108c8259c4d287681c8
Signed-off-by: ChrisC <cc697w@intl.att.com>
|
|
The Catalog Db and Requests DB have been reworked to be extendable by
project using MSO opensource.
Useless hibernate cfg.xml file have been removed too.
Change-Id: I15579bde3913c9faf8eded6f92d6b5239cca512c
Signed-off-by: Determe, Sebastien (sd378r) <sd378r@intl.att.com>
|
|
Change-Id: Ia6a7574859480717402cc2f22534d9973a78fa6d
Signed-off-by: ChrisC <cc697w@intl.att.com>
|