Project Name:
- Proposed name for the project:
Active and Available Inventory
- Proposed name for the repository:
aai
Project description:
Active and Available Inventory (AAI) is the ONAP subsystem that provides real-time views of Resources and Services and their relationships. AAI not only forms a registry of active, available, and assigned assets, it also maintains up-to-date views of the multidimensional relationships among these assets, including their relevance to different components of ONAP.
This project targets a logically centralized reference point for service and resource details serving other ONAP components and non-ONAP systems to enable fulfillment, closed loop, reporting, and other operational use cases. A&AI is critical to ONAP as the existing sources of truth do not provide a cross domain view and are not designed to serve this information to multiple clients.
Scope:
Inventory for services and resources (core capability to be delivered in R1)
Problem being addressed: Service and Resource information is critical to operational processes throughout the life cycle. When information is needed it should be made available quickly, accurately, reliably without overly impacting components in the ecosystem. Information must be made immediately available for newly defined service and resources.
Delivering a single point of reference for service and resource details
a central registry to create a global view of inventory and network topology
Receives updates from various Clients, to persist & maintain a global view.
As transactions occur, AAI persists asset attributes and relationships into the view based on configurable metadata definitions.
Provides a set of APIs to enable queries from various clients regarding inventory and topology. Queries can be supported for a specific asset or a collection of assets.
metadata-driven, new resources and services can be added quickly with Service Design and Creation (SDC) catalog definitions, using the AAI model loader.
- A&AI will capture, maintain, and expose the data required to support the 3 ONAP R1 use-cases
- Deliverables:
Service/Capability | Description |
---|---|
Model Loader | Pulls in models from SDC topic queue and loads them to AAI inventory. |
Resources | CRUD REST API endpoints for AAI inventory resources |
Traversal | REST APIs for graph traversals. Some APIs use the Gremlin Server. |
UI | used by operations for visualizing and searching. Available through ONAP Portal. |
Data Router: | Makes decisions about workloads to be dispatched to database abstraction services (including the search service). Includes logic to recognize and direct requests based on request archetypes. |
Search: | Enable complex searches for sub graphs and functions that need to perform well across deeply nested structures using Elastic Search. Used by UI. |
Champ | Abstraction from underlying graph storage systems that A&AI would interface with. |
Gizmo | CRUD REST API endpoints for resources and relationships, delivering atomic interactions for improved scalability |
Move to Active Open Source Graph Database (R1 candidate)
- Problem being addressed:
- OpenECOMP AAI is today delivered on TitanDB in ONAP
- TitanDB has no active Open Source community. No community updates for over 1 year.
- ONAP AAI needs to move away from alignment to Titan There is risk in aligning AAI to TitanDB due to lack of support, maintenance and ongoing development.
- Main scope for this feature is technical evaluation, selection, implementation of open source graph database options.
- Janus good candidate (http://janusgraph.org/)
- Janus supports Tinkerpop Abstraction implemented today in AAI.
- Janus is an evolution of TitanDB (fork)
- For support of Active-Active, Cassandra back-end is needed (rather than HBASE)
- Problem being addressed:
Extend Model-driven AAI Use cases (R1 candidate)
- Problem being addressed:
- AAI needs to dynamically operationalize new and updated models at run-time, with minimal downtime and no coding, so that ONAP is always on, and that latest service and resource models can be delivered by ONAP quickly, and without release boundary.
- To do this, AAI must update its internal model, external API and behavior at run-time to respond to change to service and resource models, including schema changes.
- OpenECOMP AAI today delivers a model loader capability that ingests native A&A models and generates the API.
- This capability needs to be extended to support:
- Retrieve the common model artifact(s) (TOSCA assumed) for schema and for model
- Translate the common model artifact(s) to AAI native artifact(s)
- Ingest and operationalize the new models - making appropriate changes to data stores, APIs, configurations
- Operationalization should include an internal 2 phase commit to ensure that relevant AAI services are successfully updated
- Operationalization should include an external 2 phase commit across all relevant ONAP components to ensure they are successfully updated.
- Decomposing AAI model/schema artefacts - today's OXM is a monolith, a more granular approach will better enable extensibility and support logical subdivision of modls
- First priority is the aspects of this behavior required for the 3 ONAP R1 use-cases
- Track Change through Time (R2+ candidate)
- Problem being addressed:
- Some assurance use-cases require investigation of the historical state of a service or resource (i.e. there was severe service degradation last Tuesday, what did the network/service look like then)
- A&AI today delivers insight only into current service and resource.
- Tracking the changes to Service and Resource inventory across time
- Support for point in time service/resource detail, e.g. for assurance
- Updated API to support query of time series data
- Problem being addressed:
AAI Reconciliation from Network/Cloud. (dependencies on Multi VIM project- assume R2 earliest)
- Problem being addressed:
- Information supplied by AAI needs to be accurate to minimize fallout in operational processes.
- Maintaining an accurate view of the service/resource is made more challenging by Increased autonomy within the network
- AAI needs mechanisms to ensure tight alignment with network, without significant additional load to the controllers. etc.
- Need to refresh from VIM
- data integrity checks and reconciliation
- event based updates from VIM/SO/Controller
- Different VIMs have different levels of detail.
- SO has this UC also.
- Variety of different options here (VIM/SO/Controller) - all valid.
Related work
Scalable, HA AAI (assumed covered by ONAP level project - Project does not yet exist for this)
- Back end needs to be HA. Need to confirm, explore.
- Testing vs performance, throughput
- Scaling AAI
Distributed AAI (assumed covered by ONAP level project - Project does not yet exist for this)
- How does AAI serve local orchestrator, local DCAE across large geographical regions
- Resource data, interim data cant be centralized - too costly.
Architecture Alignment:
- How does this project fit into the rest of the ONAP Architecture?
- AAI is one of the key functional blocks in the ONAP Architecture
- What other ONAP projects does this project depend on?
- SDC / Modelling
- Multi VIM / SO / SDN-C
- CommServ1 /MSB
- Integration
- OpenLab
- How does this align with external standards/specifications?
- APIs/Interfaces - TinkerPop, Gremlin
- Information/data models - ONAP TOSCA model
- Are there dependencies with other open source projects?
- APIs/Interfaces
- TitanDB
- Hbase
- AJSC
- EELF
- DMAAP
- Integration Testing
Resources:
- Primary Contact Person - Manisha Aggarwal (ma9181@att.com), Colin Burns (Colin Burns@amdocs.com)
Table of Committers:
Name | Gerrit ID | Company | Time Zone | |
---|---|---|---|---|
Manisha Aggarwal | AT&T | ma9181@att.com | Middletown, NJ, USA, UTC -4 | |
Jimmy Forsyth | AT&T | jf2512@att.com | Michigan, USA, UTC -4 | |
Steven Blimkie | sblimkie | Amdocs | Steven.Blimkie@amdocs.com | Ottawa, Canada, UTC -4 |
Tian Lee | TianL | Amdocs | tian.lee@amdocs.com | Bath, UK, UTC +1 |
Heliu Zhong | BOCO | zhongheliu@boco.com.cn | Beijing, China. UTC +8 | |
Yuanwei Yang | BOCO | yangyuanwei@boco.com.cn | Beijing, China. UTC +8 |
Table of Contributors:
(Names and affiliations of any other contributors)
Name | Gerrit ID | Company | Time Zone | |
---|---|---|---|---|
Jimmy Forsyth | AT&T | jf2512@att.com | Michigan, USA, UTC -4 | |
Ming Li | ZTE | Beijing, China. UTC +8 | ||
Fanhu Fu | ZTE | fu.fanhu1@zte.com.cn | Beijing, China. UTC +8 | |
CT Paterson | Amdocs | Creighton.Paterson@amdocs.com | Ottawa, Canada, UTC -4 | |
Colin Burns | Amdocs | colin.burns@amdocs.com | Bath, UK, UTC +1 | |
Andrew Baxter | Amdocs | andrew.baxter@amdocs.com@amdocs.com | Bath, UK, UTC +1 | |
Murali | Huawei | murali.p@huawei.com | Bangalore, India UTC +5:30 | |
Jason Plurad | IBM | pluradj@us.ibm.com | Durham, NC, USA UTC -4Tuesday, May 30, 1500 UTC | |
Steve Blimkie | sblimkie | Amdocs | Steven.Blimkie@amdocs.com | Ottawa, Canada, UTC -4 |
Tian Lee | TianL | Amdocs | tian.lee@amdocs.com | Bath, UK, UTC +1 |
Michael Arrastia | Amdocs | marrasti@amdocs.com | Bath, UK, UTC +1 | |
Gino Fraboni | Amdocs | gino.fraboni@amdocs.com | Ottawa, Canada, UTC -4 | |
Arul Nambi | Amdocs | arul.nambi@amdocs.com | Ottawa, Canada, UTC -4 | |
Harish Kajur | AT&T | vk250x@att.com | Middletown, NJ, USA, UTC -4 | |
Robby Maharajh | AT&T | rx2202@att.com | Middletown, NJ, USA, UTC -4 | |
Andrew Muller | AT&T | am8383@att.com | Middletown, NJ, USA, UTC -4 | |
William Lamont | AT&T | wl2432@att.com | Middletown, NJ, USA, UTC -4 | |
Giulio Graziani | Amdocs | giulio.graziani@amdocs.com | Ottawa, Canada, UTC -4 | |
Dileep Ranganathan | dileep.ranganathan | Intel | dileep.ranganathan@intel.com | Santa Clara, CA, USA, UTC -7 |
- Project Roles (include RACI chart, if applicable)
Other Information:
- link to seed code (if applicable)
- Vendor Neutral
- if the proposal is coming from an existing proprietary codebase, have you ensured that all proprietary trademarks, logos, product names, etc., have been removed?
The current seed code has been already scanned and cleanup to remove all proprietary trademarks, logos, etc. except openecomp to be replaced by onap
Subsequent modification to the existing seed code should continue to follow the same scanning and clean up principles.
- if the proposal is coming from an existing proprietary codebase, have you ensured that all proprietary trademarks, logos, product names, etc., have been removed?
- Meets Board policy (including IPR)
Use the above information to create a key project facts section on your project page
Key Project Facts
Primary Contact: Manisha Aggarwal (AT&T), Colin Burns (Amdocs)
Project Lead: Manisha Aggarwal (AT&T), Steve Blimkie (Amdocs)
Project Name:
- JIRA project name: Active and Available Inventory
- JIRA project prefix: AAI-
Repo name: Lifecycle State: Primary Contact: Project Lead: mailing list tag [Should match Jira Project Prefix]
Committers:
ma9181@att.com AT&T
jf2512@att.com AT&T
Steven.Blimkie@amdocs.com Amdocs
Link to TSC approval:
Link to approval of additional submitters:
19 Comments
Catherine Lefevre
I am adding a comment regarding the Vendor Neutral section.
Suggested tools or anything else equivalent: FOSSology, Blackduck suite, Sonar, CheckMarx.
I have updated the JIRA project name/prefix to align with jira.onap.org
Chengli Wang
Suggest to consider providing portal or tools to display services/resources and relationship between them according to the instances inside A&AI.
Colin Burns
Search and Inspect UI for A&AI is in development as part of ECOMP, and should be available in ONAP first release.
To better understand your requirements, can you describe your use-cases for this functionality?
Chengli Wang
After provisioning the network service, there will be logic resources(NS/VNF...) and real resources(VM/VL/CP...) instances, all these should be recorded in A&AI. Of course we can explore them as items in tables. I think it would be better to have graphical representation. for example, NS instance is consist of mult VNF instances, VNF instance is consist of mult VNFC instances, VNFC instance deployed on VDU instances, VDU instance map to VM, VM located on compute node.
jin xin
One question:
How to comprehend the word group "the distributed master data sources" in the scope section. Does it mean that AAI support distributed deployment?
Thanks
Tian Lee
In order to understand the aforementioned phrase you must first understand that A&AI is not the master of its data. It stores only a minimal set of identifying information about the objects it contains, and their relationships to other objects. These act as "pointers" to data held in external data sources that A&AI will interrogate at query time to enrich the data held in the A&AI database.
As a simple example, if a new virtual firewall is spun up in OpenStack, A&AI may simply store its name and VMID in its database. The OpenStack instance then becomes the master data source (a.k.a. Source of Truth) for the vFW. When a client queries for the status of the vFW through A&AI, it will contact OpenStack to pull in the current live status and display that to the user.
In a world of fast-changing virtual devices, this approach helps to alleviate issues around stale data and data synchronization inherent in traditional inventory management systems.
Catherine Lefevre
I also would like to consider the following JIRA stories as part of the AAI proposal
AAI-3 - Getting issue details... STATUS
AAI-5 - Getting issue details... STATUS if the following epic is approved COMMON-10 - Getting issue details... STATUS
AAI-7 - Getting issue details... STATUS
Tao Shen
Is AAI subsystem going to provide application UI for users to show the following informations?
Tao Shen
About services, does AAI support for exporting network resource model in XML format?
Tian Lee
Yes, A&AI provides a REST endpoint for querying resource models. The REST GET request will return a payload containing all service and resource models loaded in A&AI, in XML format.
Catherine Lefevre
Shall we also track the dependency on External System Register (5/14/17) - ESR as raised by Li Zi?
Brian Hedstrom
What level, if any, of Information and Data modeling will this project be responsible for, versus other projects? Is this project responsible for defining and creating Information and Data models for Services, Resources and their relationships? Or is this project providing a framework only for other projects? If this project is modeling resources, for example, would this project need to support YANG data models? For API definitions, are these APIs abstracting service and resource models to other components? For example, if another ONAP component needs to query or change a specific resource's property.
Tian Lee
Brian Hedstrom
The design and creation of service models is the responsibility of the SDC (Service Design and Create) project. A&AI's role is to provide an inventory of service and resource instances that reflect the current state of the real network, and to consolidate and facilitate the retrieval of real-time data for these instances from external sources (a.k.a. Sources of Truth).
The service model versions produced by SDC (currently in TOSCA specification) will be ingested by AAI and used to determine the format and content of the REST CRUD API payload (e.g. to return new object types, new relationships between object types or new attributes on existing object types).
It is expected that other ONAP components share a common understanding of the SDC models and therefore no abstraction layer over the A&AI CRUD interface is necessary.
Murali Mohan Murthy Potham
Tian Lee
I have few thoughts about AAI requirements.Kindly let me know your views.
1. Whether i can replace the Titan DB with any other graph database like Neo4J.
Does the code conform to the layered structure design? If not, we need to plan for this.
2. If a third party software or product want to use the AAI has its inventory store?
How easy or difficult it is ? Is there any documentation available for modeling the data for storage?
If we can make above possible, AAI will have greater participation from other companies
and it can become a true open-source.
Tian Lee
Steven Blimkie
I can expand a bit on the 1st point...
I'm in complete agreement wrt the advantages of being able to swap in different graph technologies. In the current release, A&AI is fairly tightly coupled with Titan. However, a "graph abstraction" library (Champ) is on the roadmap. Once the A&AI has been transitioned to use this library in it's interactions with the graph, we should be able to swap in various back-end technologies. I imagine that in the first release, the library will support only a Titan implementation (and possibly a DSE Graph implementation). But the library will be extensible such that the opensource community will be able to contribute implementation modules for other back-end technologies.
We followed a similar pattern with the existing search service, which provides an abstraction layer to a search database. Currently only an ElasticSearch imlementation is provided, but it can be extended for other technologies (Solr, Lucene, etc).
Matthew Harffy
Is this list of deliverables the definitive list for the Amsterdam release? Thanks.
samir kumar
Dear Good Folks ,
Not sure where to start hence using this forum - I am trying to install AAI on a single VM.
Everything things goes as per the plan except for the below and then it eventually stops --
Tue Nov 13 07:50:20 UTC 2018 Starting /opt/app/aai-graphadmin/bin/createDBSchema.sh
---- NOTE --- about to open graph (takes a little while)--------;
-- Loading new schema elements into JanusGraph --
-- graph commit
-- graph shutdown
Tue Nov 13 07:50:54 UTC 2018 Done /opt/app/aai-graphadmin/bin/createDBSchema.sh
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Waiting for 'testconfig_aai-graphadmin.api.simpledemo.onap.org_1' deployment to finish ...
Keong Lim
hi samir kumar,
The wiki is probably not the best place to have this discussion. Perhaps forward to the onap-discuss email list with tag #aai or join the AAI weekly meeting to get people involved. Looks like you'd need to dig into the log files to see why some service did not start properly.
Keong