Uploaded image for project: 'Service Design and Creation'
  1. Service Design and Creation
  2. SDC-994

VirtualMachineInterface validation + flow tests

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Medium Medium
    • Beijing Release
    • None
    • None
    • None

      As ASDC User

      I want

      HEAT validations to support for VLAN Sub interface

       

      • A VLAN sub-interface must have below properties,
        • virtual_machine_interface_refs
        • virtual_machine_interface_properties_sub_interface_vlan_tag 
      • Both Properties exists it is a VLAN Sub-interface
      • Both Properties missing then it is parent port - no error/warning
      • if one of the property exists then throw warning
        • Warning Message:
          • Parent port property virtual_machine_interface_refs is missing in VLAN Resource
          • VLAN Tag property virtual_machine_interface_properties_sub_interface_vlan_tag is missing in VLAN Resource

       

      Done Criteria

      • A VLAN sub-interface must have only one parent port – error – we should validate that virtual_machine_interface_refs property include one value in the list, and that the parameter which is used is string and not map/list  (get_param)
        • Error Message: More than one parent port found, there should be only one parent port for a VLAN sub-interface [id].
      • A VLAN Sub-interface should be modeled only through a resource group - if not throw warning that the model may not be as expected
        • Warning Message: VLAN Resource will not be translated as the VLAN Sub-interface [id] is not modeled as resource group
      • A file with Sub-interface connected to port through get_param and has also Ports or Nova Server or VLAN - Error
        (OS::Nova::Server, OS::Neutron::Port and OS::ContrailV2::VirtualMachineInterface)
        • Error Message : There should not be any Compute Server Node, Port or additional VLAN in nested file which represent VLAN.
      • A VLAN sub-interface network must follow naming convention – warning – validation on parameter name of the sub-interface itself
        • Warning Message: Network role associated with VLAN Sub-interface [id] is not following the naming convention
        • As per the guide line OS::ContrailV2::VirtualMachineInterface type resources resouceid naming convention should be
          for external  - {vm-type}_{index}_{network-role}_vmi_{index}
          for internal - {vm-type}_{index}_int_{network-role}_vmi_{index}
          The {index} is optional 

            katy.rotman katy.rotman
            katy.rotman katy.rotman
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: