PK @NuCê÷¶ÿŸ Ÿ topologist-latest/searchindex.jsSearch.setIndex({objects:{},terms:{becaus:2,tcp:2,follow:[1,2],paramet:1,current:1,layout:[1,2],graph:[1,2],configur:[1,2],yaml:[1,2],might:[1,2],match:1,real:1,"case":2,them:1,sourc:0,everi:1,thei:[1,2],expret:[1,2],nanomsg:0,topollog:1,like:1,name:1,config:2,list:2,resolv:1,"public":1,where:[1,2],page:[],set:2,some:[1,2],intern:1,connect:[1,2],server:2,extract:1,port:2,index:[],what:1,network:2,section:[0,1,2],content:0,rel:1,between:1,topolog:[1,2],refer:[0,1,2],deriv:1,insid:1,never:1,topologist:[0,1,2],given:2,here:2,parenthesi:1,host:2,address:[1,2],put:1,path:1,reusabl:1,search:[],actual:2,globmap:1,thing:1,tutori:[0,2],com:0,assign:2,origin:1,own:1,regardless:1,modul:[],bound:2,mai:1,differ:2,from:1,describ:1,wai:1,quir:[1,2],two:[1,2],interfac:2,includ:1,type:2,more:[1,2],form:1,both:[1,2],specifi:1,part:1,pars:[1,2],particular:1,info:[1,2],wide:2,kind:1,consist:2,servic:2,work:1,structur:1,exampl:[0,2],trick:[0,1],defin:1,can:1,listen:2,expect:1,want:2,indic:[],repres:[1,2],tag:1,file:[1,2],tabl:[],bracket:2,addr:2,end:1,welcom:0,reqrep:2,tip:[0,1],note:1,other:[1,2],role:[1,2],you:[1,2],document:[0,1,2],simpl:[0,2],updat:2,node:1,map:1,http:0,normal:1,extern:1,multipl:2,squar:2,github:0,directori:1,request:2,client:[1,2],thi:2,hirarchi:1},objtypes:{},titles:["Welcome to topologist’s documentation!","Topologist Reference","Topologist Tutorial"],objnames:{},filenames:["index","reference","tutorial"]})PK @NuC™éЖZ Z topologist-latest/search.html
Topologist configuration is a YAML file, that is parsed using quire. So you might refer to the documentation of both for more expret info.
The layouts section describes the layouts in form of mapping. Layouts are reusable parts of the topology. Layouts represented in graph-like structure.
The topologies section is a directory of the real topologies that might be resolved by end client. There are currently two kinds of topologies:
You can put every layout and every topology into it’s own file and include them in the following way:
layouts: !GlobMap "./layouts/(*).yaml"
topologies: !GlobMap "./topologies/(*).yaml"
Note the following things:
Topologist configuration is a YAML file, that is parsed using quire. So you might refer to the documentation of both for more expret info.
Here is a simple configuration file for one service:
server:
config-addr: [tcp://10.0.0.1:10001]
updates-addr: [tcp://10.0.0.2:10002]
layouts:
simple:
server <- client:
port: 10010
topologies:
simple: !Topology
type: reqrep
layout: simple
assign:
server:
- host: 10.0.0.3
In consists of the following sections.
server:
config-addr: [tcp://10.0.0.1:10001]
updates-addr: [tcp://10.0.0.2:10002]
It consists of addresses where to listen to for requests and some other server-wide settings. The addresses in example are in square brackets because they are actually YAML lists, for the case you want multiple addresses to listen to (such as on different network interfaces).
This section represents graph of the connections with connection settings. Given the example:
layouts:
simple:
server <- client:
port: 10010
There are two roles client and server. Where server is bound on the port 10010 and client connects to it.