Repository navigation
Read Ript rules from JSON #5
Description
The Ript DSL is pretty much just a nested set of method invocations:
partition "bar" do
label "www.bar.com", :address => "172.23.0.95"
label "barprod-web-01", :address => "192.168.19.2"
label "barprod-web-02", :address => "192.168.19.4"
rewrite "bar.com public website" do
ports 80
dnat "www.bar.com" => "barprod-web-01"
end
rewrite "bar.com public website" do
ports 22
dnat "www.bar.com" => "barprod-web-02"
end
endWe could in theory represent this as JSON:
{
"partition": {
"name": "bar",
"labels": {
"www.bar.com.au": {
"address": "172.23.0.95"
},
"barprod-web-01": {
"address": "192.168.19.2"
},
"barprod-web-02": {
"address": "192.168.19.4"
}
},
"rules": [
{
"rewrite": {
"ports": 80,
"dnat": {
"www.bar.com": "barprod-web-01"
}
}
},
{
"rewrite": {
"ports": 22,
"dnat": {
"www.bar.com": "barprod-web-02"
}
}
}
]
}
}This would allow other systems to generate JSON that Ript could consume, and allow for dynamic rule generation through configuration management or customer portals.
Activity
jdub commentedon Jan 31, 2013
On 31/01/2013, at 11:09, Lindsay Holmwood notifications@github.com wrote:
Yyyyyyyyeeeeessssss!
auxesis commentedon Jan 31, 2013
One other thing to consider - we could turn the existing DSL rules into JSON by implementing a
.to_jsonmethod on each partition instance.This would provide people a migration path from DSL rules to JSON rules.
auxesis commentedon Jan 31, 2013
@ycros also suggested implementing a method to include a block of JSON within the DSL, along the lines of:
auxesis commentedon Jan 31, 2013
@johnf and I were talking about this. It might make sense to:
This is good because:
Image the following orchestration use case:
This is much simpler than instructing each agent to
git pullthe rules and runript rules applyandys commentedon Feb 18, 2015
👍