Details
-
Type: extRequest
-
Status: Closed
-
Priority: Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
Labels:None
-
HD-Chapter:Cloud
-
HD-Enabler:Cloud Portal
Description
When Blueprint is created with Products (and Plain, IP or IPALL attributes), Cloud Portal is not managing them to send that info to Pegasus, when Tier is created.
POST Request from Cloud Portal to Pegasus
<tierDto> <name>tier3</name> <flavour>2</flavour> <floatingip>false</floatingip> <image>312ab1e9-5627-4f8d-b347-c0d52c59e459</image> <icono/> <keypair>default</keypair> <region>Trento</region> <minimumNumberInstances>0</minimumNumberInstances> <maximumNumberInstances>4</maximumNumberInstances> <initialNumberInstances>1</initialNumberInstances> <productReleaseDtos> <productName>WebRTC_SE</productName> <version>1.0.0</version> </productReleaseDtos> <networkDto> <networkName>test02</networkName> <networkId>c2d4aaa9-949e-4daa-a302-8b9f6354238c</networkId> </networkDto> </tierDto>
Product attributes should be sent like this:
- If the type of attribute is Plain:
<productReleaseDtos> <productName>WebRTC_SE</productName> <version>1.0.0</version> <attributes> <key>data_endpoint</key> <value>10.0.10.1</value> </attributes> </productReleaseDtos>
- If the type of attribute is IP:
<productReleaseDtos> <productName>WebRTC_SE</productName> <version>1.0.0</version> <attributes> <key>data_endpoint</key> <value>IP(tier1)</value> </attributes> </productReleaseDtos>
- If the type of attribute is IPALL:
<productReleaseDtos> <productName>WebRTC_SE</productName> <version>1.0.0</version> <attributes> <key>data_endpoint</key> <value>IPALL(tier1)</value> </attributes> </productReleaseDtos>
Activity
- All
- Comments
- History
- Activity
- Transitions
When creating a new Tier, data (value) about IP and IPALL attributes are sent wrong to Pegasus PaaSManager (missing IP (..) or IPALL(..)).
Request from Cloud Portal to PaaSManager when creating Tier
ProductAndRelease data received from SDC