QoS Queue Profile. This profile is used to assign priorities to
queues, to determine servicing. Once it has been created, a queue
profile can be globally applied in combination with a separately-
created schedule profile, using the aruba-qos-global yang model. The
queue and schedule profiles must be valid for the platform to which
they are being applied, and the configured number of queues and the
queue ID values must match.

Platform-dependent queue profile restrictions may include requiring
profiles to start with queue zero and requiring all queues in the
profiles to be adjacent.

AOSCX: All local priorities must be mapped to a queue, with no
duplicates.
PVOS: Profiles can only be configured for 2, 4, or 8 queues. All cos
values must be mapped to a queue, with no duplicates.

Queue profiles cannot be modified while they are applied. If an
applied queue profile is modified, the configuration is rejected.
To apply the modified queue profile, follow the following sequence
of operations:

1. If sched-profile in aruba-qos-global is set to DEFAULT, set
   q-profile to DEFAULT. Otherwise, remove both q-profile and
   sched-profile. This will cause the factory-default profiles
   to be applied.
2. For PVOS devices, ensure that the traffic-template leaf in
   aruba-qos-global is not set to the same profile as the
   queue-profile being modified. If it is, delete the
   aruba-qos-global traffic-template by setting the traffic-template
   leaf to null.
3. Modify the queue profile.
4. If both q-profile and sched-profile were removed in step 1, apply
   them again together in the same transaction. If q-profile was set
   to DEFAULT in step 1, apply only the q-profile leaf in aruba-qos-global.
5. If the traffic-template leaf in aruba-qos-global was set to null
   as part of this process, apply it again after the queue profile
   has been modified.