Exposing ports

Bug #1569142 reported by Mohammad Banikazemi
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Committed
Mohammad Banikazemi

Bug Description

Docker allows specifying the ports that are exposed for a given container. This is not supported as of now.

Changed in kuryr:
assignee: nobody → Mohammad Banikazemi (mb-s)
importance: Undecided → Medium
status: New → In Progress
Revision history for this message
Mohammad Banikazemi (mb-s) wrote :

We may need a config option that allows adding one default sec group for docker containers or one sec group per network.

Revision history for this message
Irena Berezovsky (irenab) wrote :

We added similar handling at the k8s integration, the default security group should be driven by kuryr https://github.com/midonet/kuryr/blob/k8s/kuryr/raven/raven.py#L127

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on kuryr (master)

Change abandoned by Mohammad Banikazemi (<email address hidden>) on branch: master
Review: https://review.openstack.org/307946
Reason: moved to https://review.openstack.org/#/c/337746/2

Revision history for this message
Dongcan Ye (hellochosen) wrote :
Changed in kuryr:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.