答复: [opnfv-tech-discuss] [compass] Fraser installation guide

Hi Louie The installation guide hasn’t changed since Euphrates. Basically the only difference is to export OPENSTACK_VERSION to pike for fraser 6.2. Regards Harry 发件人: opnfv-tech-discuss@lists.opnfv.org [mailto:opnfv-tech-discuss@lists.opnfv.org] 代表 louie long 发送时间: 2018年7月2日 14:23 收件人:

[opnfv-tech-discuss] 答复: [compass4nfv][auto] Compass4nfv on LaaS x86 server

Hi Gerard I have logged into hpe32 and identified the issue: you are using compass4nfv master branch but opnfv-6.2.tar.gz is the package for fraser. You can try to use this package http://artifacts.opnfv.org/compass4nfv/opnfv-2018-07-27_08-43-10.tar.gz or switch to use fraser branch. Regards

答复: [opnfv-tech-discuss] [compass4nfv][auto] Compass4nfv on LaaS x86 server

Hi Gerard Sorry that I may brought some confusion here: VIRT_NUMBER is set to 5 by default and should be set to 2 explicitly when using noha scenario. I will log in hpe32 to finish the deploy and update your steps on auto wiki. Regards Harry 发件人: gerard.d...@wipro.com

答复: [opnfv-tech-discuss] [compass4nfv][auto] Compass4nfv on LaaS x86 server

Hi Gerard This Error comes from the missing of variable VIRT_NUMBER. Because in the script, you are using noha scenario (os-nosdn-nofeature-noha.yml) which contains only one controller and one compute. Compass will expect five

答复: [opnfv-tech-discuss] [compass4nfv][auto] Compass4nfv on LaaS x86 server

Hi Gerard On hpe32, actually OpenStack deploy is successful and there may be a bug in noha scenario which causes the repeated failure. I have identified the problem and tried to fix it directly on hpe32. Can you keep the environment untouched? If this fix is confirmed to be effective, I will

答复: [opnfv-tech-discuss] [compass4nfv][auto] Compass4nfv on LaaS x86 server

Hi Gerard, Martin Issue is fixed and I have successfully deployed noha scenario on hpe32. You can pull the new master branch of compass4nfv and try again. And it's also a good feedback from you which can help to improve the usage of compass. Indeed it seems quite redundant to export VIRT_NUMBER

答复: [opnfv-tech-discuss] [compass4nfv][auto] Compass4nfv on LaaS x86 server

Gerard Thanks for trying compass and bringing up those questions. Please also notice with patch https://gerrit.opnfv.org/gerrit/#/c/60589/ merged, variable VIRT_NUMBER is no longer needed. Best Regards Harry 发件人: opnfv-tech-discuss@lists.opnfv.org [mailto:opnfv-tech-discuss@lists.opnfv.org]

答复: [OPNFV Helpdesk #62413] [opnfv-tech-discuss] docker image build fails on lf-build3

Hi Trevor Thanks for the quick response ! All images have been built successfully now. Thanks Harry -邮件原件- 发件人: Trevor Bramwell via RT [mailto:opnfv-helpd...@rt.linuxfoundation.org] 发送时间: 2018年10月18日 11:57 收件人: huangxiangyu 抄送: agard...@linuxfoundation.org;

答复: [OPNFV Helpdesk #62413] [opnfv-tech-discuss] docker image build fails on lf-build3

Hi Trevor Sorry to bother you again but lf-build3 has blocked our build process again. I'm wondering if this permission issue for lf-build3 can be solved permanently so we won't have to bother you anymore? Thanks Harry -邮件原件- 发件人: Trevor Bramwell via RT

[opnfv-tech-discuss] docker image build fails on lf-build3

Hi Trevor As Gambia branch is created, compass4nfv Gambia is supposed to use docker images built from compass-containers Gambia branch. But somehow building process always failed on lf-buld3. In https://build.opnfv.org/ci/view/compass4nfv/job/compass-docker-gambia/ you can find the build

Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status

Hi Richard I have removed the pip.conf for host1. Though pip will still check the local repo first but it can install packages from internet now. There seems no stack at this point and I believed OpenStack components are working functionally. As for nbi_docker, I haven’t met this problem

Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status

Hi Martin On host1 you can run the following commands to recreate the ONAP stack: cd /root/onap/integration/test/ete source ./labs/huawei-shanghai/onap-openrc ./scripts/deploy-onap.sh huawei-shanghai These steps will get all onap VMs spinning but all scripts be called inside are pulled from

[opnfv-tech-discuss] [compass4nfv] Gambia Status

Hi David A baremetal deployment of os-nosdn-nofeature-ha scenario has passed functest health check: https://build.opnfv.org/ci/view/compass4nfv/job/functest-compass-baremetal-daily-gambia/19/console Compass CI job consists of deploy, functest, yardstick, bottleneck, dovetail, it will take

[opnfv-tech-discuss] Permission issue in compass build master

Hi Trevor There is a permission problem in compass build job for master: https://build.opnfv.org/ci/view/compass4nfv/job/compass-build-daily-master/lastFailedBuild/console Can you help to remove the file which is causing trouble? Thanks Harry -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all

[opnfv-tech-discuss] Compass4nfv project intent to Participate in the OPNFV Hunter Release

Hi TSC The purpose of this mail is to notify the OPNFV TSC that Compass4nfv project intends to participate in the OPNFV Hunter release. We intend to follow the traditional track. Best Regards Harry 发件人: opnfv-tech-discuss@lists.opnfv.org [mailto:opnfv-tech-discuss@lists.opnfv.org] 代表 David

Re: [opnfv-tech-discuss] #compass Help installing Compass

Hi Parker We are not maintaining Fraser anymore, please use Gambia instead. LXC name and hostname are two different things. For example, in Gambia cinder LXC named hostx_cinder_api_container- but inside LXC the hostname is hostx-cinder-api-container-. Regards Harry 发件人: