Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Relate via #7813

Merged
merged 2 commits into from Aug 31, 2017
Merged

Relate via #7813

merged 2 commits into from Aug 31, 2017

Conversation

wallyworld
Copy link
Member

Description of change

We now support adding a remote relation and specifying the egress subnets from which outbound traffic will originate. This compliments the existing model wide config attribute "egress-subnets".

The first commit renames the model attribute "egress-cidrs" to "egress-subnets".
The second commit addes the --via support.

The UX is "juju add-relation foo bar --via cidr1,cidr2,..."

QA steps

juju bootstrap aws dbctrl
juju deploy mysql
juju offer mysql:db

From behind a firewall or cgnat:
juju bootstrap lxd mwctrl
juju deploy mediawiki
juju relate mediawiki:db dbctrl:defauly.mysql --via <what's-my-ip>/32

check aws firewall ports and check that media wiki is operational

@@ -218,6 +219,13 @@ func (s stateShim) AddRelation(eps ...state.Endpoint) (Relation, error) {
return stateRelationShim{r}, nil
}

type RelationNetworks state.RelationNetworks
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see any point to this, state.RelationNetworks is already an interface.

@wallyworld
Copy link
Member Author

$$merge$$

@jujubot
Copy link
Collaborator

jujubot commented Aug 31, 2017

Status: merge request accepted. Url: http://ci.jujucharms.com/job/github-merge-juju

@jujubot jujubot merged commit 4e1be75 into juju:develop Aug 31, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants