Age | Commit message (Collapse) | Author | Files | Lines |
|
1. improved vm_init script
2. enabled vm_init script at the end of install script
3. noting that now supporting more deployment profiles
Issue-ID: DCAEGEN2-434
Change-Id: I2bcbe1c79571dad5f6d8998f02eaf702efa5625e
Signed-off-by: Lusheng Ji <lji@research.att.com>
|
|
Issue-ID: DCAEGEN2-434
Change-Id: Iab71fe366d2e518db0fdf3ab98bbe45e4492751a
Signed-off-by: Lusheng Ji <lji@research.att.com>
|
|
Issue-ID: DCAEGEN2-206
Change-Id: I7e60806369eef5a816f6c5c686f1061debc833ee
Signed-off-by: Lusheng Ji <lji@research.att.com>
|
|
Added code using a "dcae_deployment_profile" parameter to control
what kind of deployment for DCAE. R1 is for ONAP Amsterdam deployment
(bootstrap installs Cloudify Manager then uses CM to deploy additional
VMs). R2MVP is a new MVP deployment, with only service components such
as VES collector and supporting components. All components are
deployed with their default configurations. R2MVP does not support
dynamic depoyment of additional assets and configuration via CLAMP.
Issue-ID: DCAEGEN2-206
Change-Id: Ide51c780a45c23f33123d52f9df225b8715833d3
Signed-off-by: Lusheng Ji <lji@research.att.com>
|
|
Issue-ID: DCAEGEN2-376
Change-Id: If07ae2ec696449dfd1c82896aaef6132dd5c82ac
Signed-off-by: Lusheng Ji <lji@research.att.com>
|
|
Issue-ID: DCAEGEN2-200
Change-Id: Ie686c2443f1110c680f3821fc9e51d68ea952156
Signed-off-by: Lusheng Ji <lji@research.att.com>
|
|
Added DNS zone creation code for OpenStack installations with Designate
support. Previously for this type of OpenStack instaalations we
assumed that there was no need to create new zone. But such assumption
is not consistent with the DACE blueprints. Therefore the blueprints
working for proxied Designate OpenStack installation will break not work
for direct Designate OpenStack installations. This new change makes the
vm_init behaves consistently for both direct Designate and proxied Designate
so that the same blueprint can be use in both environments.
Issue-ID: DCAEGEN2-200
Change-Id: I1f82f60facad77849c67f0feb1fa07f02af1079e
Signed-off-by: Lusheng Ji <lji@research.att.com>
|
|
Issue-Id: DCAEGEN2-187
Change-Id: I77a5b4d005d9e4b19fe46940e5b121666f682f23
Signed-off-by: Lusheng Ji <lji@research.att.com>
|
|
Issue-Id: DCAEGEN2-187
Change-Id: I44511ceba24065482b83c0774993bb3ca9164c8a
Signed-off-by: Lusheng Ji <lji@research.att.com>
|
|
This submission address the "fusion" between DNS service zones
between DCAE and rest of ONAP R1. In ONAP R1 each ONAP deployment
runs its own private DNS server; DCAE use Designate DNS as a Service.
The VMs on both sides need to be able to communicate with each other
by hostnames. This submission modifies the ONAP private DNS server
so it uses the DNS server behind the Designate as the forwarder. For
ONAP->DCAE communication, host names will be resolved by Designate DNS
server; for DCAE->ONAP communication, since DCAE VMs also use the ONAP
private DNS server as first name server, it is not a problem.
Issue-Id: DCAEGEN2-187
Change-Id: Ia54cd41f33b446d406a69868598ae1a8c0cdea8d
Signed-off-by: Lusheng Ji <lji@research.att.com>
|
|
MultiCould expects tenant name and network name instead of IDs.
Integration Heat passes in only IDs. Added additional parameters
for names.
Fix a file path issue when setting up nginx.
Issue-Id: DCAEGEN2-128
Change-Id: Iac6025c4ab1f38682c8f75d13c6ea6b31d43106a
Signed-off-by: Lusheng Ji <lji@research.att.com>
|
|
This submission contains implementation for supporting MultiCloud
proxy-ed Designate solution. The changes, mostly in dcae2_vm_init.sh,
are for registering Designate proxy by MultiCloud with A&AI; register
new DNS zone with the MultiCloud proxyed Designate service; configure
DCAE to use the new DNS zone, etc.
The submission for corresponding Heat template changes will be made separtely.
Issue-Id: DCAEGEN2-128
Change-Id: Ief8e91152c7d2f117aec3f21df54c1ed74ceef0f
Signed-off-by: Lusheng Ji <lji@research.att.com>
|
|
Changes are for:
1. Proxying healthcheck API call to Consul's health API using a Nginx
container proxy. Also some code cleanup.
2. Add support for posting floating addresses to Designate DNS
3. Add addition parameters in heat for supporting spinning up DCAE in
a separate OS/tenant (due to lack of Designate support in main Integration
OS/tenant)
Issue-Id: DCAEGEN2-127
Change-Id: Iac66eddbdd1dfadfc92bf2a1e372c6ad55bd0ab1
Signed-off-by: Lusheng Ji <lji@research.att.com>
|
|
Issue-Id: DCAEGEN2-127
Change-Id: I4e8221972144495d9f121e4f5cfc775d141b15cb
Signed-off-by: Lusheng Ji <lji@research.att.com>
|
|
- Add DCAE GEN2 VM to all Heat templates
- Add DCAE-related parameters
- Create new install/init scripts for DCAE
Change-Id: I299ad3b2c212a05d12a109fda21ce48980ddd448
Issue-ID: INT-213
Signed-off-by: Marco Platania <platania@research.att.com>
|