Skip to content
This repository has been archived by the owner on Aug 30, 2024. It is now read-only.

Calyptos: Support for static route deployment (instead of bgp) #78

Open
dmccue opened this issue Sep 16, 2015 · 2 comments
Open

Calyptos: Support for static route deployment (instead of bgp) #78

dmccue opened this issue Sep 16, 2015 · 2 comments

Comments

@dmccue
Copy link

dmccue commented Sep 16, 2015

Could have an attribute such as default_attributes.midokura.static_route: true

This would kick off multiple resources to allow access to instances over their public interfaces based on the default_attributes.eucalyptus.network.config-json.PublicIps string

@nephomaniac
Copy link

Hi @dmccue,
I began testing some different approaches to this last week.
I also discussed this briefly with @mbacchi last week. We are looking at larger changes in regards to how Calyptos handles system level items (such as network interfaces) in general. This may add to the potential size of the environment document, but should also allow that document to be more transparent and flexible. I think this refactor will cover this use case.
In the meantime...
We could also add a recipe to the Midokura-Cookbook that can be used directly via chef-client on the GW's to see if that addresses the problem/need? ie: "chef-client -z -o midokura::static-gateway" ?
Thanks!
-M

@dmccue
Copy link
Author

dmccue commented Nov 21, 2015

The midokura::static-gateway using chef-solo should work temporarily, let me know when to start testing

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants