Andrey

Hi @dshcherb , This repo is under gerrit/jira - so it would more helpful to escalate issues via PLM. In this case they can be fixed :)

in the instances.yaml you need to specify real IP-s of servers/services that will be used for your deployment. 10.87.64.23 is an IP of KVM host that should be accessible by...

As I know ansible doesn't setup networking with virsh. it just can run machines for you. different results in running virsh caused by different connection string to qemu.

commits are forbidden for this repo via pull requests. please use review.opencontrail.org

can you please share your instances.yaml? we haven't seen such issue previously. And please note - right place for bugs/issue is LP - https://bugs.launchpad.net/juniperopenstack/?orderby=-id&start=0

@sylvainOL the repo is managed by gerrit. commits are available only through review https://review.opencontrail.org/#/dashboard/self

Hi @chaiminghui you need to set 'TSN_EVPN_MODE: true' in vrouter role for exmaple: ``` instances: bms1: provider: bms ip: 192.168.1.51 roles: vrouter: TSN_EVPN_MODE: true ```

Hi @dvandok please file bugs there - https://bugs.launchpad.net/juniperopenstack/?orderby=-id&start=0 regarding this issue - i didn't find http_proxy in that doc.

I would recommend to file bugs in launchpad https://bugs.launchpad.net/juniperopenstack/?orderby=-id&start=0 ) This tracker is not supported actively. And it would be good to see your instances.yaml

@ygordienko Hi, can you please update status of your issue? I see that some code for swift was added here and in ansible deployer.