Re: [opnfv-tech-discuss] [armband] Resource for development or testing

2017-08-06 Thread Bob Monkman
+ Rak Paik, Morgan and Dave McBride (although since tech-discuss is copied they should get this) Mark B is correct here, the way that alpine does this is correct, putting the architecture designation in the name. This is the only way to avoid consuion and support equity in multi-architecture,

[opnfv-tech-discuss] Jump server common configuration for PXE/admin network - questions

2017-08-06 Thread Alexandru Avadanii
Hi, I am looking at integrating Fuel@OPNFV/MCP with our OPNFV baremetal PODs (both x86_64 and aarch64). Right now I am playing with MaaS and its network configuration. The old Fuel@OPNFV was relying on the jump server's "pxebr" bridge interface, which is supposed to reach all baremetal nodes,

Re: [opnfv-tech-discuss] [armband] Resource for development or testing

2017-08-06 Thread Alexandru Avadanii
Hi, Mark, If we want to go this route, we will have to get all projects having docker builds to agree to this change, and it will require renaming quite a lot of tags. I support the idea, but I wonder what the rest of the community thinks about it. BR, Alex From: Beierl, Mark