juju expose could allow exposing to a specific CIDR/IP

Bug #1401358 reported by Michael Nelson
This bug report is a duplicate of:  Bug #1287658: Fine grain secgroup rules. Edit Remove
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
juju-core
Triaged
Medium
Unassigned

Bug Description

This is pretty specific to a certain situation, but in case there are other situations where it would also be useful: I need to expose a service just to a specific IP/CIDR. Currently I can do:

juju expose postgresql-service

which will update the secgroup to allow anything to access it and then manually update the secgroup. What I'd like to do is:

juju expose postgresql-service --limit-to 1.2.3.4/24

or similar.

(The situation I have is a deployment where the database exists on metal, but when testing the deployment, I'm creating a postgresql service in a separate environment and exposing it to the application service only by manually updating the secgroup.)

Tags: expose feature
Curtis Hovey (sinzui)
tags: added: expose feature
Changed in juju-core:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Dimiter Naydenov (dimitern) wrote :

How about adding to the charm: open-port 0-65535/tcp
?

As we implement the ability to deploy services into juju network spaces, this and similar UX issues should improve a lot.

Revision history for this message
Anastasia (anastasia-macmood) wrote :

This will be resolved by a solution to bug #1287658. Marking it as duplicate.

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.