Skip to content

Conversation

@EmilienM
Copy link
Member

@EmilienM EmilienM commented Sep 29, 2021

Configuring QoS Policy ID on ports can be useful to apply Quality of
Services into the OpenStack Neutron ports, for example in NFV use-cases.

OSASINFRA-2447

@openshift-ci
Copy link

openshift-ci bot commented Sep 29, 2021

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please ask for approval from emilienm after the PR has been reviewed.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@EmilienM
Copy link
Member Author

Upstream is being implemented here: kubernetes-sigs#1008

@EmilienM EmilienM force-pushed the neutron_qos branch 4 times, most recently from da04ea4 to 2d3b01c Compare September 30, 2021 20:23
@EmilienM EmilienM changed the title getOrCreatePort: add support to configure port QoS WIP - getOrCreatePort: add support to configure port QoS Sep 30, 2021
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 30, 2021
Configuring QoS Policy ID on ports can be useful to apply Quality of
Services into the OpenStack Neutron ports, for example in NFV use-cases.

It refactors a bit how we construct the Port creation, so we can easily
use Neutron extensions (here QoS).

OSASINFRA-2447
@EmilienM EmilienM changed the title WIP - getOrCreatePort: add support to configure port QoS getOrCreatePort: add support to configure port QoS Sep 30, 2021
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 30, 2021
@EmilienM
Copy link
Member Author

EmilienM commented Oct 1, 2021

@EmilienM
Copy link
Member Author

EmilienM commented Oct 4, 2021

/retest

1 similar comment
@EmilienM
Copy link
Member Author

EmilienM commented Oct 5, 2021

/retest

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 4, 2022
@openshift-bot
Copy link

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 3, 2022
@mandre
Copy link
Member

mandre commented Feb 4, 2022

/test e2e-openstack-operator

@openshift-ci
Copy link

openshift-ci bot commented Feb 4, 2022

@EmilienM: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-openstack-proxy 15aa201 link false /test e2e-openstack-proxy
ci/prow/e2e-openstack-operator 15aa201 link false /test e2e-openstack-operator

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@openshift-bot
Copy link

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci bot closed this Mar 6, 2022
@openshift-ci
Copy link

openshift-ci bot commented Mar 6, 2022

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants