It turns out if I include all the fields defined in the OXM in the PUT payload, then I would get back the all the fields. If I omit some, then only a subset would be returned.
________________________________ From: Prashant Kumar Sent: Tuesday, June 06, 2017 9:43 AM To: Eric Au; [email protected] Subject: RE: [ONAP-AAI] AAI data not fully display in GET Hi Eric, Try getting for specific host. cloud-infrastructure/pservers/pserver/{hostname} Thanks, Prashant From: [email protected] [mailto:[email protected]] On Behalf Of Eric Au Sent: Tuesday, June 6, 2017 5:24 PM To: [email protected] Subject: [onap-discuss] [ONAP-AAI] AAI data not fully display in GET Hi all, As I understand, AAI is model driven using the OXM file found in opt/app/aai/bundleconfig/etc/oxm. From the OXM, I came to understand that the pserver model payload should resemble the following: { "hostname": "{mandatory}", "ptnii-equip-name": "{optional field}", "number-of-cpus": "{optional field}", "disk-in-gigabytes": "{optional field}", "ram-in-megabytes": "{optional field}", "equip-type": "{optional field}", "equipment-vendor": "{optional field}", "equipment-model": "{optional field}", "fqdn": "{optional field}", "ipv4-oam-address": "{optional field}", "serial-number": "{optional field}", "pserver-id": "{optional field}", "internet-topology": "{optional field}", "pserver-name2" : "{optional field}", "purpose": "{optional field}" } I am able to PUT the data into AAI with a 201 Created response code. However, when I perform a GET on the pservers (cloud-infrastructure/pservers) , I end up with only a subset of the information I input. <pservers xmlns="http://org.openecomp.aai.inventory/v8";> <pserver> <hostname>test</hostname> <in-maint>false</in-maint> <resource-version>1496723052</resource-version> <pserver-name2>Pserver Test</pserver-name2> </pserver> </pservers> How do I get the full data set back from AAI? Thanks Eric This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
