Hi all, To address Yaogang's questions:
> Can you show me how to update the (active) swVersion of a specified PNF by > AAI APIs? As per the AAI API HTML: https://nexus.onap.org/service/local/repositories/releases/archive/org/onap/aai/aai-common/aai-schema/1.2.4/aai-schema-1.2.4.jar/!/aai_swagger_html/aai_swagger_v13.html#operation--network-pnfs-pnf--pnf-name--patch You can use "PATCH /network/pnfs/pnf/{pnf-name}" with a request body that includes: { "sw-version": "new version" } > What is the status of attribute swVersionList or availableSwVersions of PNF > in AAI? (Since I donot find the corresponding attribute in aai schema files) This schema does not exist yet, but that is covered by the question asked by Ben Cheung below. To address Ben's questions: > You mentioned on the A&AI call today that you did the structure for the > VCPE use case and that for the PNF Plug and Play use case, we might be able > to reuse or learn from what you did? > Thanks for any pointers you can give us insight into. >From experience with CCVPN use case, my suggestion would be as follows: 1. Add a new "softwares" component under "/network" namespace to represent "a repository of known software": <java-type name="Network"> <xml-root-element name="network" /> <java-attributes> ... <xml-element java-attribute="softwares" name="software" type="inventory.aai.onap.org.v14.Softwares" /> ... </java-attributes> </java-type> 2. Define the "softwares" and "software" elements, with the properties desired and a relationship-list: <java-type name="Softwares"> <xml-root-element name="softwares" /> <xml-properties> <xml-property name="description" value="Collection of softwares" /> </xml-properties> <java-attributes> <xml-element container-type="java.util.ArrayList" java-attribute="software" name="software" type="inventory.aai.onap.org.v14.Software" /> </java-attributes> </java-type> <java-type name="Software"> <xml-root-element name="software" /> <java-attributes> <xml-element java-attribute="id" name="id" required="true" type="java.lang.String" xml-key="true" /> <xml-element java-attribute="version" name="version" type="java.lang.String" /> <xml-element java-attribute="vendor" name="vendor" type="java.lang.String" /> ... <xml-element java-attribute="relationshipList" name="relationship-list" type="inventory.aai.onap.org.v14.RelationshipList" /> </java-attributes> ... </java-type> </java-types> 3. This will create a new API under "/network/softwares/software/{id}" with standard operations for GET/PUT/PATCH/DELETE. 4. Add EdgeRules between "software" and "pnf" to represent "software available to pnf": { "from": "software", "to": "pnf", "label": "org.onap.relationships.inventory.AvailableTo", "direction": "OUT", "multiplicity": "MANY2MANY", "contains-other-v": "NONE", "delete-other-v": "NONE", "prevent-delete": "NONE", "default": "true", "description":"For Ben and Yaogang" } 5. With this design, each "software" object can be "available to" many "pnfs" and each "pnf" can have many available "softwares". There is no restrictions on deleting "softwares" that are attached to "pnfs" in this way. 6. This EdgeRule will allow the "software" to be attached/detached from the "pnf" through the "relationship-list", i.e. the API would be "/network/softwares/software/{id}/relationship-list" 7. Note that there is no change to the "pnf" schema at all. The existing "sw-version" property is already functioning as "active software version" attribute. The process to use would be: a. Create pnf b. Create softwares c. Attach available "software" objects to "pnf" relationship-list d. UI retrieves "pnf" object e. UI displays "available software" retrieved from the pnf relationship-list f. User selects "software" object from the UI display g. Update pnf "sw-version" attribute with id of selected "software" object, representing the "active software" Keong From: Cheung, Ben (Nokia - US/Murray Hill) [mailto:ben.che...@nokia.com] Sent: Thursday, 16 August 2018 01:06 To: Keong Lim <keong....@huawei.com>; jf2...@att.com Cc: Hillis, Marge (Nokia - US) <marge.hil...@nokia.com>; MONTELEONE, CHRISTINA <cm3...@att.com> Subject: A&AI PNF PnP Impacts Keong, You mentioned on the A&AI call today that you did the structure for the VCPE use case and that for the PNF Plug and Play use case, we might be able to reuse or learn from what you did? Thanks for any pointers you can give us insight into. Jimmy, Just as a reminder - from our A&AI team call today, you mentioned you could check to see if there was already a jira task for the A&AI work for PNF PnP UC. Thanks. Best regards, -Ben Cheung, PhD, DMTS, ALTA ATF Architecture Systems Engineer Mobile Networks, Nokia Tel +1 (908) 679-6615 Email ben.che...@nokia.com<mailto:ben.che...@nokia.com> 600-700 Mountain Ave, Murray Hill, NJ 07974-0636 USA / #2C-378 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11892): https://lists.onap.org/g/onap-discuss/message/11892 Mute This Topic: https://lists.onap.org/mt/24554527/21656 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
