[HELP-2400] FIWARE.Request.Tech.Cloud.CloudPortal.productattributesBlueprints - JIRA

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

Ascending order - Click to sort in descending order

Javier Fernández (Inactive) created issue - 24/Mar/15 11:47 AM

Javier Fernández (Inactive) made changes - 24/Mar/15 12:37 PM

Field	Original Value	New Value
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 {code:xml} <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> {code} ---- Product attributes should be sent like this: * If the type of attribute is Plain: {code:xml} <productReleaseDtos> <productName>WebRTC_SE</productName> <version>1.0.0</version> <attributes> <key>data_endpoint</key> <value>10.0.10.1</value> </attributes> </productReleaseDtos> {code} * If the type of attribute is IP: {code:xml} <productReleaseDtos> <productName>WebRTC_SE</productName> <version>1.0.0</version> <attributes> <key>data_endpoint</key> <value>IP(tier1)</value> </attributes> </productReleaseDtos> {code} * If the type of attribute is IPALL: {code:xml} <productReleaseDtos> <productName>WebRTC_SE</productName> <version>1.0.0</version> <attributes> <key>data_endpoint</key> <value>IPALL(tier1,tier2)</value> </attributes> </productReleaseDtos> {code}	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 {code:xml} <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> {code} ---- Product attributes should be sent like this: * If the type of attribute is Plain: {code:xml} <productReleaseDtos> <productName>WebRTC_SE</productName> <version>1.0.0</version> <attributes> <key>data_endpoint</key> <value>10.0.10.1</value> </attributes> </productReleaseDtos> {code} * If the type of attribute is IP: {code:xml} <productReleaseDtos> <productName>WebRTC_SE</productName> <version>1.0.0</version> <attributes> <key>data_endpoint</key> <value>IP(tier1)</value> </attributes> </productReleaseDtos> {code} * If the type of attribute is IPALL: {code:xml} <productReleaseDtos> <productName>WebRTC_SE</productName> <version>1.0.0</version> <attributes> <key>data_endpoint</key> <value>IPALL(tier1)</value> </attributes> </productReleaseDtos> {code}

Manuel Escriche made changes - 06/Apr/15 5:06 PM

Component/s

FIWARE-TECH-HELP [ 10278 ]

Alvaro Alonso made changes - 08/Apr/15 3:48 PM

Status

Open [ 1 ]

Answered [ 10104 ]

Alvaro Alonso made changes - 08/Apr/15 3:48 PM

Resolution		Done [ 10000 ]
Status	Answered [ 10104 ]	Done [ 10000 ]

Hide

Permalink

Javier Fernández (Inactive) added a comment - 28/Apr/15 12:08 PM

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

...
<productReleaseDtos>
  <productName>testingpuppet</productName>
  <version>1.2.3</version>
  <attributes>
    <key>custom_att_01</key>
    <value>tierplain</value>
  </attributes>
  <attributes>
    <key>custom_att_02</key>
    <value>tierplain</value>
  </attributes>
  <attributes>
    <key>custom_att_03</key>
    <value>plain_new_value</value>
  </attributes>
</productReleaseDtos>
...

ProductAndRelease data received from SDC

.... ></product><version>1.0</version></productAndReleaseDto><productAndReleaseDto><product><name>testingpuppet
</name><description>For testing purpose</description><attributes><key>custom_att_01</key><value>IPALL_default_value
</value><type>IPALL</type></attributes><attributes><key>custom_att_02</key><value>IP_default_value</value
><type>IP</type></attributes><attributes><key>custom_att_03</key><value>Plain_dafault_value</value><type
>Plain</type></attributes><metadatas><key>cookb ....

Show

Javier Fernández (Inactive) added a comment - 28/Apr/15 12:08 PM 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 ... <productReleaseDtos> <productName> testingpuppet </productName> <version> 1.2.3 </version> <attributes> <key> custom_att_01 </key> <value> tierplain </value> </attributes> <attributes> <key> custom_att_02 </key> <value> tierplain </value> </attributes> <attributes> <key> custom_att_03 </key> <value> plain_new_value </value> </attributes> </productReleaseDtos> ... ProductAndRelease data received from SDC .... > </product> <version> 1.0 </version> </productAndReleaseDto> <productAndReleaseDto> <product> <name> testingpuppet </name> <description> For testing purpose </description> <attributes> <key> custom_att_01 </key> <value> IPALL_default_value </value> <type> IPALL </type> </attributes> <attributes> <key> custom_att_02 </key> <value> IP_default_value</value > <type> IP </type> </attributes> <attributes> <key> custom_att_03 </key> <value> Plain_dafault_value </value> <type >Plain </type> </attributes> <metadatas> <key> cookb ....

Backlog Manager made changes - 24/Jul/15 10:55 AM

Summary

[BUG] [CLOUD PORTAL] The Cloud Portal is not managing the product attributes in Blueprints

FIWARE.Request.Lab.The Cloud Portal is not managing the product attributes in Blueprints

Alvaro Alonso made changes - 31/Jul/15 9:16 AM

Summary

FIWARE.Request.Lab.The Cloud Portal is not managing the product attributes in Blueprints

FIWARE.Request.Lab.Cloud.CloudPortal.productattributesBlueprints

Manuel Escriche made changes - 16/Dec/15 12:37 PM

Summary

FIWARE.Request.Lab.Cloud.CloudPortal.productattributesBlueprints

FIWARE.Request.Tech.Cloud.CloudPortal.productattributesBlueprints

Manuel Escriche made changes - 12/Jan/16 9:08 AM

Workflow	FW eRequest Workflow [ 25893 ]	FW extRequest Workflow-II [ 40707 ]
Status	Done [ 10000 ]	Closed [ 6 ]
Issue Type	eRequest [ 10101 ]	extRequest [ 10104 ]

Manuel Escriche made changes - 11/Apr/16 5:18 PM

HD-Enabler		Cloud Portal [ 10860 ]
HD-Chapter		Cloud [ 10837 ]

Fernando Lopez made changes - 27/May/21 10:53 AM

Fix Version/s

2021 [ 12600 ]

Transition

Time In Source Status

Execution Times

Last Executer

Last Execution Date

Open

Answered

15d 3h

Alvaro Alonso

08/Apr/15 3:48 PM

Answered

Done

Alvaro Alonso

08/Apr/15 3:48 PM

Done

Closed

278d 18h 19m

Manuel Escriche

12/Jan/16 9:08 AM

People

Assignee:

Alvaro Alonso

Reporter:

Javier Fernández (Inactive)

Votes:

0 Vote for this issue

Watchers:

1 Start watching this issue

Dates

Created:

24/Mar/15 11:47 AM

Updated:

27/May/21 10:53 AM

Resolved:

08/Apr/15 3:48 PM

Agile

View on Board