edvgui
commented
3 years ago In the current state of things, the input attributes would look like this:
desired_attributes = {
"identifier": "my-evc-001",
"connectionType": "POINT_TO_POINT",
"evcEndPoints": [
{
"identifier": "my-evc-ep-1",
"egressBandwidthProfilePerEndPoint": [
{
"cir": 1,
},
{
"cir": 2,
},
],
"evcEndPointMap": {
"type": "LIST",
"vlanIdList": [{"vlanId": 200}],
},
"carrierEthernetSubscriberUni": {
"href": "inmanta:456-852-789",
},
},
{
"identifier": "my-evc-ep-2",
"egressBandwidthProfilePerEndPoint": [
{
"cir": 1,
},
{
"cir": 2,
},
],
"evcEndPointMap": {
"type": "LIST",
"vlanIdList": [{"vlanId": 201}],
},
"carrierEthernetSubscriberUni": {
"href": "inmanta:123-852-456",
},
},
],
}for a service definition that looks like this:
entity CarrierEthernetService:
connection_type connectionType
end
entity CarrierEthernetEvc extends CarrierEthernetService, lsm::ServiceEntity:
evc_id identifier
end
index CarrierEthernetEvc(identifier)
CarrierEthernetEvc.evcEndPoints [2] -- CarrierEthernetEvcEndPoint
entity CarrierEthernetEvcEndPoint extends lsm::EmbeddedEntity:
evc_id identifier
end
index CarrierEthernetEvcEndPoint(identifier)
CarrierEthernetEvcEndPoint.egressBandwidthProfilePerEndPoint [0:] -- EgressBwpFlow
CarrierEthernetEvcEndPoint.evcEndPointMap [1] -- VlanIdListOrUntag
CarrierEthernetEvcEndPoint.carrierEthernetSubscriberUni [1] -- CarrierEthernetSubscriberUniRef
entity EgressBwpFlow extends lsm::EmbeddedEntity:
std::positive_int cir
end
entity VlanIdListOrUntag extends lsm::EmbeddedEntity:
vlan_id_list_type type
end
VlanIdListOrUntag.vlanIdList [0:] -- VlanId
entity VlanId extends lsm::EmbeddedEntity:
vlan_id_type vlanId
end
entity CarrierEthernetSubscriberUniRef extends lsm::EmbeddedEntity:
string href
endHere is an automatically generated openapi json file for this service:
butterybread
bartv
andraskvr
Currently the add instance form only support the toplevel attributes. More and more services use a nested structure. This goal of this ticket is to: