from:"harry huang"

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

2018-07-02 Thread harry huang

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 
主题: [opnfv-tech-discuss] [compass] Fraser installation guide


 Hi，

 The fraser 6.2 version recently have been released , I am intend to upgrade my 
opnfv version，
but in the compass installation guide page I can‘t find the latest installation 
guide,
the compass release note and installation guide are Euphrate[1][2][3].

Where can I find the latest installation guide page of compass?

 BRs，

 Louie


[1] https://www.opnfv.org/software/downloads
[2] 
https://docs.opnfv.org/en/stable-fraser/submodules/compass4nfv/docs/release/installation/introduction.html
[3] 
https://docs.opnfv.org/en/stable-fraser/submodules/compass4nfv/docs/release/release-notes/release-notes.html




--
Louie Long
 E-mail: yl...@biigroup.cn
 Mobile: +86 13261979365
Fax: 86-10-5867-8466
Postcode：10
Add: 2nd Floor, Building 5, No.58 Jinghai Road, BDA, Beijing, China
Website: www.biigroup.com  
www.cfiec.net


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#21500): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/21500
Mute This Topic: https://lists.opnfv.org/mt/23000206/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

2018-07-27 Thread harry huang

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
Harry

发件人: opnfv-tech-discuss@lists.opnfv.org 
[mailto:opnfv-tech-discuss@lists.opnfv.org] 代表 Gerard Damm
发送时间: 2018年7月26日 6:31
收件人: opnfv-tech-discuss@lists.opnfv.org
主题: [opnfv-tech-discuss] [compass4nfv][auto] Compass4nfv on LaaS x86 server

Hi,

I'm trying to use Compass4nfv installer (basic virtual deployment) on a x86 UNH 
Pharos LaaS server.
This would be used later as one of the infrastructure options for the Auto 
project (e.g., to provide
Openstack instances for VNFs and for ONAP).

I've been getting different errors on different attempts, such as:

error in client.py, line 977, in get_ansible_print
error in client.py, line 1015, in _get_installing_progress


Example for the first error:
Traceback (most recent call last):
  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1136, in 
main()
  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1131, in main
deploy()
  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1085, in deploy
ansible_print = client.get_ansible_print()
  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 977, in 
get_ansible_print
raise RuntimeError("OS installation timeout")
RuntimeError: OS installation timeout
+ RET=1
+ sleep 25
+ [[ 1 -eq 0 ]]
+ /bin/false
+ exit 1


Example for the second error:
Traceback (most recent call last):
  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1136, in 
main()
  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1131, in main
deploy()
  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1086, in deploy
client.get_installing_progress(cluster_id, ansible_print)
  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1029, in 
get_installing_progress
_get_installing_progress()
  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1015, in 
_get_installing_progress
(cluster_id, status, cluster_state)
RuntimeError: ('get cluster %s state status %s: %s, error', (1, 200, 
{u'status': {u'completed_hosts': 0, u'total_hosts': 5, u'installing_hosts': 0, 
u'failed_hosts': 5}, u'severity': u'ERROR', u'created_at': u'2018-07-25 
20:09:15', u'message': u'total 5, installing 0, completed: 0, error 5', 
u'updated_at': u'2018-07-25 20:29:33', u'state': u'ERROR', u'ready': False, 
u'percentage': 0.0, u'id': 1}))
+ RET=1
+ sleep 25
+ [[ 1 -eq 0 ]]
+ /bin/false
+ exit 1


I've been using commands such as those listed in this simple test script to 
automate the Compass4nfv installation (virtual deployment):
https://wiki.opnfv.org/display/AUTO/Script%3A+Compass4nfv


Any idea what the issue(s) could be (missing command, version/release problem, 
environment variables, etc.) ?
For example, should TAR_URL be set even if build.sh is run before deploy.sh ?

Also, is there a compass4nfv script to delete/uninstall/teardown everything 
installed/deployed by compass4nfv ?
It would be handy, when running a pipeline covering various infrastructure 
options on the same server or cluster of servers.


A few links:
Compass4nfv installation instructions:
https://docs.opnfv.org/en/latest/submodules/compass4nfv/docs/release/installation/index.html

Auto home wiki page:
https://wiki.opnfv.org/pages/viewpage.action?pageId=12389095


Thanks in advance,
Gerard
The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. WARNING: Computer viruses can be transmitted via email. The 
recipient should check this email and any attachments for the presence of 
viruses. The company accepts no liability for any damage caused by any virus 
transmitted by this email. www.wipro.com


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#21639): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/21639
Mute This Topic: https://lists.opnfv.org/mt/23838038/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

2018-07-31 Thread harry huang

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 virtual machines for virtual deploy and user need to 
export VIRT_NUMBER to specify the number if it’s not 5.

BTW, which doc do you follow when testing the compass installer? I will add 
this operation if there isn’t.

Regards
Harry

发件人: opnfv-tech-discuss@lists.opnfv.org 
[mailto:opnfv-tech-discuss@lists.opnfv.org] 代表 Gerard Damm
发送时间: 2018年7月31日 7:20
收件人: opnfv-tech-discuss@lists.opnfv.org
抄送: huangxiangyu 
主题: Re: [opnfv-tech-discuss] [compass4nfv][auto] Compass4nfv on LaaS x86 server

Hi,

Thanks for that, but wouldn't that apply only to the option of downloading a 
tar ball ? If a user launches build.sh, shouldn't that build the correct 
package from the current branch (usually master, but any branch really) ? In 
that second case, I guess there shouldn't be a release/branch issue.

And I understood that it is preferable to use build.sh (among other things, to 
avoid such release/branch mismatch issues), so the preferred sequence would be: 
git clone compass4nfv repo, launch build.sh, edit and launch deploy.sh.

Anyway, I retried 2 examples (with fresh git clone each time):
1) stay in master branch, use build.sh
2) checkout to stable/fraser branch, download package 6.2

They both failed:

1) Still got that get_ansible_print error:
Traceback (most recent call last):
  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1136, in 
main()
  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1131, in main
deploy()
  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1085, in deploy
ansible_print = client.get_ansible_print()
  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 977, in 
get_ansible_print
raise RuntimeError("OS installation timeout")
RuntimeError: OS installation timeout
+ RET=1
+ sleep 25
+ [[ 1 -eq 0 ]]
+ /bin/false
+ exit 1


2) sequence of key commands:

wget http://artifacts.opnfv.org/compass4nfv/fraser/opnfv-6.2.tar.gz
git clone https://gerrit.opnfv.org/gerrit/compass4nfv
cd compass4nfv/
git checkout stable/fraser
(or should it be to tag opnfv-6.2.0 ? "git checkout opnfv-6.2.0" ?)

root@linux-r4ap:/opt/opnfv-compass/compass4nfv# git branch
  master
* stable/fraser

edited deploy.sh as follows : (note: I picked "noha", not "ha")
export OS_VERSION=xenial
export TAR_URL=file:///opt/opnfv-compass/opnfv-6.2.tar.gz
export 
DHA=/opt/opnfv-compass/compass4nfv/deploy/conf/vm_environment/os-nosdn-nofeature-noha.yml
export 
NETWORK=/opt/opnfv-compass/compass4nfv/deploy/conf/vm_environment/network.yml

./deploy.sh

And still that get_ansible_print error (lines are different, I guess because 
it's a client.py file from a different branch):
Traceback (most recent call last):
  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1127, in 
main()
  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1122, in main
deploy()
  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1076, in deploy
ansible_print = client.get_ansible_print()
  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 968, in 
get_ansible_print
raise RuntimeError("OS installation timeout")
RuntimeError: OS installation timeout
+ RET=1
+ sleep 25
+ [[ 1 -eq 0 ]]
+ /bin/false
+ exit 1


Has anyone else tried the procedure on a LaaS server ?

My current (updated today) notes are at :
https://wiki.opnfv.org/display/AUTO/Script%3A+Compass4nfv

Best regards,
Gerard



From: huangxiangyu [mailto:huangxiang...@huawei.com]
Sent: Friday, July 27, 2018 10:35 PM
To: Gerard Damm (Product Engineering Service) 
mailto:gerard.d...@wipro.com>>; 
opnfv-tech-discuss@lists.opnfv.org
Subject: ** Newsletter/Marketing email** 答复: [compass4nfv][auto] Compass4nfv on 
LaaS x86 server


** This mail has been sent from an external source **
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

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

2018-08-01 Thread harry huang

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 [mailto:gerard.d...@wipro.com]
发送时间: 2018年8月1日 8:07
收件人: opnfv-tech-discuss@lists.opnfv.org
抄送: huangxiangyu 
主题: RE: [opnfv-tech-discuss] [compass4nfv][auto] Compass4nfv on LaaS x86 server

Thanks for pointing out that other possible issue.

The instructions I use as a reference:
https://docs.opnfv.org/en/latest/submodules/compass4nfv/docs/release/installation/index.html

My spelled out version/script for these instructions (case of virtual 
deployment on Ubuntu):
https://wiki.opnfv.org/display/AUTO/Script%3A+Compass4nfv


I did 3 more attempts on hpe32, and unfortunately they also failed:

1) tarball 6.2, stable/fraser branch, noha scenario, set VIRT_NUMBER to 5, 
deploy.sh
2) quickstart.sh (i.e. in master branch, build.sh, ha scenario, deploy.sh)
3) master branch, build.sh, noha scenario, set VIRT_NUMBER to 5, deploy.sh

I got twice with the get_ansible_print error, and once a 
get_installing_progress error.
(details below)

At this point, probably the most efficient next step would be for you to try 
yourself on a LaaS server,
write down exactly the sequence of commands you used, so as to find out the 
missing commands.
Then I'll updates my notes, and the compass4nfv docs may also be updated.

Best regards,
Gerard




1) tarball 6.2, stable/fraser branch, noha scenario, set VIRT_NUMBER to 5, 
deploy.sh

downloaded 6.2 tarball, checked out to stable/fraser, added these lines in 
deploy.sh (and with noha scenario):
export VIRT_NUMBER=5
export VIRT_CPUS=4
export VIRT_MEM=16384
export VIRT_DISK=200G

error:

Traceback (most recent call last):
  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1127, in 
main()
  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1122, in main
deploy()
  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1076, in deploy
ansible_print = client.get_ansible_print()
  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 968, in 
get_ansible_print
raise RuntimeError("OS installation timeout")
RuntimeError: OS installation timeout
+ RET=1
+ sleep 25
+ [[ 1 -eq 0 ]]
+ /bin/false
+ exit 1



2) quickstart.sh (i.e. in master branch, build.sh, ha scenario, deploy.sh)

error:

2018-07-31 21:57:59,756 p=130 u=root |  hostname: host2
2018-07-31 21:57:59,782 p=130 u=root |  
host=compass-deck,url=/api/clusterhosts/2/state,body={"state": 
"ERROR"},headers={'Content-type': 'application/json', 'Accept': '*/*', 
'X-Auth-Token': '$1$UohR2peC$xirMX8ctPjiZv5d1amTDf/'}
2018-07-31 21:57:59,817 p=130 u=root |  notify host status success!!! 
status=200, body={
"severity": "INFO",
"created_at": "2018-07-31 21:37:19",
"updated_at": "2018-07-31 21:57:59",
"id": 2,
"state": "ERROR",
"ready": false,
"percentage": 0.0,
"message": ""
}

2018-07-31 21:57:59,818 p=130 u=root |  hostname: host1
2018-07-31 21:57:59,845 p=130 u=root |  
host=compass-deck,url=/api/clusterhosts/1/state,body={"state": 
"ERROR"},headers={'Content-type': 'application/json', 'Accept': '*/*', 
'X-Auth-Token': '$1$F7YoEKlk$1/6TRpRf7crU2U6t8S0lE1'}
2018-07-31 21:57:59,892 p=130 u=root |  notify host status success!!! 
status=200, body={
"severity": "INFO",
"created_at": "2018-07-31 21:37:19",
"updated_at": "2018-07-31 21:57:59",
"id": 1,
"state": "ERROR",
"ready": false,
"percentage": 0.0,
"message": ""
}

Traceback (most recent call last):
  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1136, in 
main()
  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1131, in main
deploy()
  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1086, in deploy
client.get_installing_progress(cluster_id, ansible_print)
  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1029, in 
get_installing_progress
_get_installing_progress()
  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1015, in 
_get_installing_progress
(cluster_id, status, cluster_state)
RuntimeError: ('get cluster %s state status %s: %s, error', (1, 200, 
{u'status': {u'completed_hosts': 0, u'total_hosts': 5, u'installing_hosts': 0, 
u'failed_hosts': 5}, u'severity': u'ERROR', u'created_at': u'2018-07-31 
21:37:19', u'message': u'total 5, installing 0, completed: 0, error 5', 
u'updated_at': u'2018-07-31 21:57:59', u'state': u'ERROR', u'ready': False, 
u'percentage': 0.0, u'id': 1}))
+ RET=1
+ sleep 25
+ [[ 1 -eq 0 ]]
+ /bin/false
+ exit 1




3) master branch, build.sh, noha scenario, set VIRT_NUMBER to 5, deploy.sh

error:

Traceback (most recent call last):
  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1136, in 
main()
  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1131, in main
deplo

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

2018-08-02 Thread harry huang

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 commit a patch to compass 
master.

Regards
Harry

发件人: opnfv-tech-discuss@lists.opnfv.org 
[mailto:opnfv-tech-discuss@lists.opnfv.org] 代表 Gerard Damm
发送时间: 2018年8月2日 5:21
收件人: opnfv-tech-discuss@lists.opnfv.org
抄送: huangxiangyu ; Klozik Martin 

主题: Re: [opnfv-tech-discuss] [compass4nfv][auto] Compass4nfv on LaaS x86 server

Hi,

Thanks Martin and Harry for your feedback !

On hpe15, the log file doesn't end with the string "compass deploy success", so 
the process may not have completed correctly.
When you reach the point of "reboot_hosts do nothing", it takes quite a while 
(30-60 minutes ?) to get to the conclusion.
Is it possible you stopped the process before it finished ?

Also, I didn't see the setting of "VIRT_NUMBER" in the "deploy.sh" file in 
"/home/opnfv/compass4nfv", but then again it's possible you changed it 
afterwards.

One directory up ("/home/opnfv"), the file "deply.sh.log" ends in 
"launch_compass failed".

Out of curiosity, I tried option 1 on hpe15 (see script in ~/auto) (so: master 
branch, build+deploy, NOHA scenario, VIRT_NUMBER=2).
This one failed with the "get_installing_progress" error.
You can check the logs in /opt/opnfv-compass/compass4nfv, and in ~/auto).

Best regards,
Gerard




From: Klozik Martin [mailto:martin.klo...@tieto.com]
Sent: Wednesday, August 1, 2018 4:50 AM
To: Gerard Damm (Product Engineering Service) 
mailto:gerard.d...@wipro.com>>; 
opnfv-tech-discuss@lists.opnfv.org
Cc: huangxiangyu mailto:huangxiang...@huawei.com>>
Subject: Re: [opnfv-tech-discuss] [compass4nfv][auto] Compass4nfv on LaaS x86 
server


** This mail has been sent from an external source. Treat hyperlinks and 
attachments in this email with caution**

Hi Gerard,



I tried to follow your installation procedure (i.e. point 1 below) at HPE15 
with the only difference, i.e. VIRT_NUMBER=1. I've not observed the same error 
as you, but some (probably not fatal) assertion error (search log for 
client.py). Anyhow the installation process seemed to finish somehow. I plan to 
have a more detailed look at the machine tomorrow. Feel free to have a look 
yourself, I'll forward you appropriate credentials. The installation log 
(output of deploy.sh) is available at /home/opnfv/compass4nfv/deploy.log



Have a nice day,

Martin


Od: 
opnfv-tech-discuss@lists.opnfv.org 
mailto:opnfv-tech-discuss@lists.opnfv.org>> 
za uživatele Gerard Damm mailto:gerard.d...@wipro.com>>
Odesláno: středa 1. srpna 2018 2:06:43
Komu: 
opnfv-tech-discuss@lists.opnfv.org
Kopie: huangxiangyu
Předmět: Re: [opnfv-tech-discuss] [compass4nfv][auto] Compass4nfv on LaaS x86 
server


Thanks for pointing out that other possible issue.



The instructions I use as a reference:

https://docs.opnfv.org/en/latest/submodules/compass4nfv/docs/release/installation/index.html



My spelled out version/script for these instructions (case of virtual 
deployment on Ubuntu):

https://wiki.opnfv.org/display/AUTO/Script%3A+Compass4nfv





I did 3 more attempts on hpe32, and unfortunately they also failed:



1) tarball 6.2, stable/fraser branch, noha scenario, set VIRT_NUMBER to 5, 
deploy.sh

2) quickstart.sh (i.e. in master branch, build.sh, ha scenario, deploy.sh)

3) master branch, build.sh, noha scenario, set VIRT_NUMBER to 5, deploy.sh



I got twice with the get_ansible_print error, and once a 
get_installing_progress error.

(details below)



At this point, probably the most efficient next step would be for you to try 
yourself on a LaaS server,

write down exactly the sequence of commands you used, so as to find out the 
missing commands.

Then I'll updates my notes, and the compass4nfv docs may also be updated.



Best regards,

Gerard









1) tarball 6.2, stable/fraser branch, noha scenario, set VIRT_NUMBER to 5, 
deploy.sh



downloaded 6.2 tarball, checked out to stable/fraser, added these lines in 
deploy.sh (and with noha scenario):

export VIRT_NUMBER=5

export VIRT_CPUS=4

export VIRT_MEM=16384

export VIRT_DISK=200G



error:



Traceback (most recent call last):

  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1127, in 

main()

  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1122, in main

deploy()

  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1076, in deploy

ansible_print = client.get_ansible_print()

  File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 968, in 
get_ansible_print

raise RuntimeError("OS installation timeout")

RuntimeError: OS installation timeout

+ RET=1

+ sleep 25

+ [[ 1 -eq 0

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

2018-08-05 Thread harry huang

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 instead of getting it 
from the scenario.
I will working on getting rid of VIRT_NUMBER today and let you know when it's 
done.

Regards
Harry

-邮件原件-
发件人: opnfv-tech-discuss@lists.opnfv.org 
[mailto:opnfv-tech-discuss@lists.opnfv.org] 代表 Gerard Damm
发送时间: 2018年8月3日 2:58
收件人: opnfv-tech-discuss@lists.opnfv.org
抄送: huangxiangyu ; Klozik Martin 

主题: Re: [opnfv-tech-discuss] [compass4nfv][auto] Compass4nfv on LaaS x86 server

Hi,

Yes, like on the Apex thread, there's got to be some implicit setup (such as 
tool installations and updates, and indeed maybe reboot) to be done, and these 
initial config problems appear only when running a procedure for the first time 
on a brand new server where nothing else has ever run before.

The same procedure may run fine on an "old" server, but can fail on a new one.
These exact required initial steps will have to be identified/documented and 
included in scripts.

I guess including the booking of a new server daily in CI will help validate 
the initial configuration steps.

Moreover, the procedure could be hardened by trying it in multiple cases: new 
server, twice on new server (after a delete or not), and the same on an "old" 
server.

And then it depends also on scenarios (e.g., success for HA, failure for NOHA, 
depending on environment variables like VIRT_NUMBER).

About opnfv-clean: that was in the Apex thread, not the Compass4nfv thread. So 
the tool came from installing the Apex packages and RPMs:
https://wiki.opnfv.org/pages/viewpage.action?pageId=26837081
or:
https://wiki.opnfv.org/display/storperf/LaaS+Setup+For+Development#LaaSSetupForDevelopment-InstallOPNFVApex

About picking an option: yes, agreed. Harry had recommended the first option 
(build the ISO file rather than download it). Let's wait for the analysis by 
Harry going on hpe32 for NOHA, then confirm.

As always, thanks all for your feedback !

BR,
Gerard


> -Original Message-
> From: Klozik Martin [mailto:martin.klo...@tieto.com]
> Sent: Thursday, August 2, 2018 3:16 AM
> To: Gerard Damm (Product Engineering Service) ; 
> opnfv-tech-discuss@lists.opnfv.org
> Cc: huangxiangyu 
> Subject: Re: [opnfv-tech-discuss] [compass4nfv][auto] Compass4nfv on 
> LaaS
> x86 server
>
> ** This mail has been sent from an external source. Treat hyperlinks 
> and attachments in this email with caution**
>
> Hi Gerard,
>
> I did a few checks today with following outcome:
>
> * (HPE15) installation with VIRT_NUMBER=1 does not pass "reboot_hosts"
> stage, it simply terminates after this messages is shown; that's why I 
> was not able to see anything else yesterday
> * (HPE15) installation with VIRT_NUMBER=2 went correctly (i.e. I see 
> the "Installation Complete!" banner :-))
> * I tried to retest it (with VIRT_NUMBER=2) at "clean" server HPE16 
> and I hit the same issue as you did (i.e. RuntimeError: OS 
> installation timeout)
>
> I'm wondering if it can be related to the OS state. May be we should 
> firstly try to do an apt update & upgrade (may be even followed by the 
> sever reboot), before execution of compass installation. I'll give it a try 
> at another server.
>
> One additional question. How did you "installed" opnfv-clean binary at 
> your server? I've used alien to create a deb package from
> http://artifacts.opnfv.org/apex/master/opnfv-apex-common-2.1-
> 20160306.noarch.rpm. After its installation at HPE15, I was able to 
> execute opnfv-clean, but I doubt that it works. So I'm wondering if it 
> is enough to install this package or other two rpms/debs are also 
> required (in that case I would expect that such dependency would be 
> enforced by package spec file...).
>
> BTW, I did a small updates to your compass install script. May be it's 
> time to comment out one of the options, so it is directly usable for 
> OPNFV deployment at LaaS server. What do you think?
>
> Cheers,
> Martin
>
The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. WARNING: Computer viruses can be transmitted via email. The 
recipient should check this email and any attachments for the presence of 
viruses. The company accepts no liability for any damage caused by any virus 
transmitted by this email. www.wipro.com




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#21708): 
https://lists.opnfv.org/g/opnfv-tech-disc

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

2018-08-30 Thread harry huang

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] 代表 Gerard Damm
发送时间: 2018年8月31日 4:28
收件人: opnfv-tech-discuss@lists.opnfv.org
主题: Re: [opnfv-tech-discuss] [compass4nfv][auto] Compass4nfv on LaaS x86 server

Hi,
Just a note on that thread: the latest release of Compass4nfv allowed to solve 
the problem.
Best regards,
Gerard


The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. WARNING: Computer viruses can be transmitted via email. The 
recipient should check this email and any attachments for the presence of 
viruses. The company accepts no liability for any damage caused by any virus 
transmitted by this email. www.wipro.com


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#21900): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/21900
Mute This Topic: https://lists.opnfv.org/mt/25137172/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

2018-10-17 Thread harry huang

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 process of lf-build3 failed because of a permission 
denied issue.
Console output: 
https://build.opnfv.org/ci/job/compass-tasks-k8s-build-amd64-gambia/2/console

There are 7 images need to be built so it's hard to bypass lf-build3 to build 
all images.
I didn't know the exact reason why this failure happened, can you help to check 
this issue?

Thanks
Harry
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22179): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22179
Mute This Topic: https://lists.opnfv.org/mt/27399525/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

2018-10-18 Thread harry huang

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; dmcbr...@linuxfoundation.org; 
opnfv-tech-discuss@lists.opnfv.org
主题: [OPNFV Helpdesk #62413] [opnfv-tech-discuss] docker image build fails on 
lf-build3

Hi Harry,

I've taken lf-build3 out of rotation for now, as we only brought it online to 
help with the build queue the other day.

This should make your builds get scheduled on ericsson-build4 or lf-build2 
where they've been successful in the past.

Regards,
Trevor Bramwell

On Wed Oct 17 20:32:13 2018, huangxiang...@huawei.com wrote:
> 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 process of lf-build3 failed because of a 
> permission denied issue.
> Console output: https://build.opnfv.org/ci/job/compass-tasks-k8s-
> build-amd64-gambia/2/console
> 
> There are 7 images need to be built so it's hard to bypass lf-build3 
> to build all images.
> I didn't know the exact reason why this failure happened, can you help 
> to check this issue?
> 
> Thanks
> Harry



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22184): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22184
Mute This Topic: https://lists.opnfv.org/mt/27411821/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

2018-10-22 Thread harry huang

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 [mailto:opnfv-helpd...@rt.linuxfoundation.org] 
发送时间: 2018年10月18日 11:57
收件人: huangxiangyu 
抄送: agard...@linuxfoundation.org; dmcbr...@linuxfoundation.org; 
opnfv-tech-discuss@lists.opnfv.org
主题: [OPNFV Helpdesk #62413] [opnfv-tech-discuss] docker image build fails on 
lf-build3

Hi Harry,

I've taken lf-build3 out of rotation for now, as we only brought it online to 
help with the build queue the other day.

This should make your builds get scheduled on ericsson-build4 or lf-build2 
where they've been successful in the past.

Regards,
Trevor Bramwell

On Wed Oct 17 20:32:13 2018, huangxiang...@huawei.com wrote:
> 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 process of lf-build3 failed because of a 
> permission denied issue.
> Console output: https://build.opnfv.org/ci/job/compass-tasks-k8s-
> build-amd64-gambia/2/console
> 
> There are 7 images need to be built so it's hard to bypass lf-build3 
> to build all images.
> I didn't know the exact reason why this failure happened, can you help 
> to check this issue?
> 
> Thanks
> Harry



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22189): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22189
Mute This Topic: https://lists.opnfv.org/mt/27482989/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

2018-10-23 Thread harry huang

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 internet where some problems lie.
Be aware that there are some docker tag mismatches exist, you will need to 
manually check the install.log inside VMs to fix them and then call 
xx_vm_init.sh.

Regards
Harry

发件人: opnfv-tech-discuss@lists.opnfv.org 
[mailto:opnfv-tech-discuss@lists.opnfv.org] 代表 Klozik Martin
发送时间: 2018年10月23日 14:16
收件人: huangxiangyu ; opnfv-tech-discuss@lists.opnfv.org
主题: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status

Hi Harry,

after the power down of huawei-pod12 we are facing an issue with the ONAP 
installation. The Onap VMs are seen as running by OpenStack, but all of them 
have failed to boot the kernel and are hanging in the initramfs.

Paul did some investigation and he has found out, that it is possible to boot 
vm manually, it means, that kernel will boot properly. He did some quick checks 
and it is not clear to us, why VMs can't be boot properly by the OpenStack.

Have you seen similar issue in the past, e.g. at any other huawei server after 
the recent power down? We have a suspicion, that some OS configuration 
performed during installation was not hardened in the configuration files and 
thus it was lost after the pod was powered down.

We will be grateful for any hints, so we can bring the ONAP installation up and 
running again.

I'm also wondering if you have any notes about the OS and ONAP installation. We 
can access the bash history, but it is not clear if all performed activities 
are really necessary. It would be great if you will document the steps required 
to have OS deployed. I suppose, that for documentation of ONAP installation, we 
have to ask Gary, am I right?

Thank you,
Martin
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22209): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22209
Mute This Topic: https://lists.opnfv.org/mt/27566007/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

2018-11-04 Thread harry huang

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 before, maybe you need to find 
answer from ONAP community

Regards
Harry

发件人: Elias Richard [mailto:richard.el...@tieto.com]
发送时间: 2018年10月30日 21:36
收件人: Klozik Martin ; huangxiangyu 
; opnfv-tech-discuss@lists.opnfv.org
主题: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status


Hi Harry,

I connected to the host and run the commands, but there were problems with the 
python packages.



There was a proxy server set for the pip installation which cannot download the 
packages. Was there a reason a proxy was necessary for pip? If the packages are 
already installed the check could probably be skipped.



There are also some parts of Openstack that seem to be stuck after the reboot( 
for example a stack with status:DELETE_FAILED). The teardown script tries to 
remove this, but as it is stuck there could be problems with the deployment.



The creation script itself returns this error:

"ERROR: The Parameter (nbi_docker) was not provided."

I was not able to find this parameter in any of the templates in 
~/onap/integration/test/ete/labs/ so I am not sure what is missing.



I started analyzing the problem but I did not want to change anything before 
asking you for help.

Could you please take a look at it and share any insights you have?

Thank you very much,

Richard


From: Klozik Martin
Sent: 29 October 2018 14:36:37
To: huangxiangyu; 
opnfv-tech-discuss@lists.opnfv.org
Cc: Elias Richard
Subject: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status


adding Richard to the loop...


--Martin

Od: 
opnfv-tech-discuss@lists.opnfv.org 
mailto:opnfv-tech-discuss@lists.opnfv.org>> 
za uživatele Klozik Martin 
mailto:martin.klo...@tieto.com>>
Odesláno: středa 24. října 2018 8:00
Komu: huangxiangyu; 
opnfv-tech-discuss@lists.opnfv.org
Předmět: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status


Hi Harry,



thank you for the hints, we will go ahead with ONAP re-deployment as suggested.



Best Regards,

Martin


Od: huangxiangyu mailto:huangxiang...@huawei.com>>
Odesláno: středa 24. října 2018 5:01:37
Komu: Klozik Martin; 
opnfv-tech-discuss@lists.opnfv.org
Předmět: RE: [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 internet where some problems lie.

Be aware that there are some docker tag mismatches exist, you will need to 
manually check the install.log inside VMs to fix them and then call 
xx_vm_init.sh.



Regards

Harry



发件人: 
opnfv-tech-discuss@lists.opnfv.org 
[mailto:opnfv-tech-discuss@lists.opnfv.org] 代表 Klozik Martin
发送时间: 2018年10月23日 14:16
收件人: huangxiangyu mailto:huangxiang...@huawei.com>>; 
opnfv-tech-discuss@lists.opnfv.org
主题: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status



Hi Harry,

after the power down of huawei-pod12 we are facing an issue with the ONAP 
installation. The Onap VMs are seen as running by OpenStack, but all of them 
have failed to boot the kernel and are hanging in the initramfs.



Paul did some investigation and he has found out, that it is possible to boot 
vm manually, it means, that kernel will boot properly. He did some quick checks 
and it is not clear to us, why VMs can't be boot properly by the OpenStack.



Have you seen similar issue in the past, e.g. at any other huawei server after 
the recent power down? We have a suspicion, that some OS configuration 
performed during installation was not hardened in the configuration files and 
thus it was lost after the pod was powered down.



We will be grateful for any hints, so we can bring the ONAP installation up and 
running again.

I'm also wondering if you have any notes about the OS and ONAP installation. We 
can access the bash history, but it is not clear if all performed activities 
are really necessary. It would be great if you will document the steps required 
to have OS deployed. I suppose, that for documentation of ONAP installation, we 
have to ask Gary, am I right?



Thank you,

Martin
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22280): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22280
Mute This Topic: h

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

2018-11-07 Thread harry huang

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 almost half a day to finish a daily job.
At this point, I think we can release os-nosdn-nofeature-ha scenario for 
baremetal deploy in 7.0.0 release and release other baremetal scenarios in 
7.0.1 when they are verified by health check.

I will keep triggering os-nosdn-nofeature-ha scenario to confirm issue's been 
really fixed.

Regards
Harry

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22312): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22312
Mute This Topic: https://lists.opnfv.org/mt/28034231/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

2018-11-08 Thread harry huang

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 messages sent to this group.

View/Reply Online (#22313): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22313
Mute This Topic: https://lists.opnfv.org/mt/28035325/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

2018-11-11 Thread harry huang

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 McBride
发送时间: 2018年11月10日 6:04
收件人: TECH-DISCUSS OPNFV 
抄送: Bin Hu ; TSC OPNFV 
主题: Re: [opnfv-tech-discuss] Intent to Participate in the OPNFV Hunter Release 
#release #hunter

Team,

Just a reminder that we've reached the halfway point in the 
intent-to-participate window for the Hunter release.  The window will close in 
two weeks on Nov 23 (MS1). While I've heard from many of you, there are still 
several projects that have not responded.  If you're one of those, please send 
your intent email ASAP.

In addition, please remember that the end of the intent-to-participate window 
also marks MS1, at which time your project release plan is required.  Recall 
that projects may create a release plan that is suitable for their needs.  
However, if you are a new project, and you have no idea what to do for a 
release plan, you may use this 
template, 
although it is not required.

Finally, we have now passed the point at which a project proposal could be 
submitted and be approved in time to join the release, without a milestone 
exception.

Let me know if you have any questions.

David

On Mon, Oct 29, 2018 at 6:46 AM David McBride 
mailto:dmcbr...@linuxfoundation.org>> wrote:
Team,

Today marks the opening of the intent-to-participate window for the Hunter 
release (i.e. MS0).  Please find the procedure 
here.  
The window closes as of MS1, tentatively planned for Nov 23.

Please let me know which release track you intend to participate in by 
including one of the following statements in your intent to participate 
notification:
1. We intend to follow the traditional track.
2. We intend to follow the continuous delivery track
3. We intend to follow both the traditional track and the continuous 
delivery track
Also, please remember that if you are planning a new project for the Hunter 
release, you have until Nov 9 to submit your proposal to the TSC and still have 
time to be approved and to join the release before the intent-to-participate 
window closes.

Let me know if you have questions.  Thanks.

David

--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride


--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22340): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22340
Mute This Topic: https://lists.opnfv.org/mt/28086978/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

2018-12-17 Thread harry huang

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

发件人: opnfv-tech-discuss@lists.opnfv.org 
[mailto:opnfv-tech-discuss@lists.opnfv.org] 代表 Parker Berberian
发送时间: 2018年12月15日 2:55
收件人: opnfv-tech-dis. 
主题: [opnfv-tech-discuss] #compass Help installing Compass

Hello,

I am trying to install Compass Fraser release. I am running into an issue late 
in the deployment process where the cinder api container on one of my 
controllers throws an exception. The problem seems to be that the LXC 
containers are given hostnames with underscores, which are rejected as invalid.

According to the Openstack Oslo documentation 
(here), 
Parsing for HostAddress "Performs strict checks for both IP addresses and valid 
hostnames, matching the opt values to the respective types as per RFC1912"

The mentioned RFC (here) states: " 
Allowable characters in a label for a host name are only ASCII letters, digits, 
and the `-' character."



The exception I am getting is:  "oslo_config.cfg.DefaultValueError: Error 
processing default value host3_cinder_api_container-7534a57f for Opt type of 
HostAddress."

The exception being raised on line 975 of oslo_config/cfg.py says 
"host3_cinder_api_container-7534a57f is not a valid hostname"

Is there anything I can do here? Any help would be appreciated.

Parker





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22576): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22576
Mute This Topic: https://lists.opnfv.org/mt/28755686/21656
Mute #compass: https://lists.opnfv.org/mk?hashtag=compass&subid=2783016
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

16 matches

Site Navigation

Mail list logo

Footer information