Hi Mark and Tianwei, Did you solve this issue? I am also trying to deploy virtual compass on a single node and I am getting same error message.
Thanks, Br, Mika Rautakumpu Nokia From: [email protected] [mailto:[email protected]] On Behalf Of wutianwei Sent: Friday, April 20, 2018 4:15 AM To: Beierl, Mark <[email protected]> Cc: [email protected] Subject: Re: [opnfv-tech-discuss] [compass] Virtual install on single node Hi Mark, 1. Make sure ports 67, 69, 80, 443 are free on your node. 2. Make sure the docker storage is not overlay(overlay2). 3. When deploying nosdn-nofeature-noha scenario 1). please set the VIRT_NUMBER=2 2). Please set the DHA=./deploy/conf/vm_environment/os-nosdn-nofeature-noha.yml You can also find us in the IRC channel “#opnfv-compass4nfv” Thanks, Tianwei Wu 发件人: Beierl, Mark [mailto:[email protected]] 发送时间: 2018年4月20日 2:29 收件人: wutianwei <[email protected]<mailto:[email protected]>> 抄送: [email protected]<mailto:[email protected]> 主题: Re: [opnfv-tech-discuss] [compass] Virtual install on single node Hello, and thank you for the information. I tried a single node installation (Ubuntu 16.04, 512G ram, 88 cores), with internet, as follows: export SCENARIO=os-nosdn-nofeature-noha.yml export VIRT_NUMBER=4 export VIRT_CPUS=16 export VIRT_MEM=65536 export VIRT_DISK=200G export DHA=./deploy/conf/vm_environment/os-nosdn-nofeature-ha.yml export NETWORK=./deploy/conf/vm_environment/unh-virtual1/network.yml ./build.sh (completed successfully) ./deploy.sh That failed with the following error: FAILED - RETRYING: cobbler import iso (1 retries left). failed: [localhost] (item={'key': u'CentOS-7', 'value': {u'cobbler_arch': u'x86_64', u'kickstart': u'default.ks', u'iso_name': u'CentOS-7-x86_64-Minimal-1708', u'breed': u'redhat', u'ppa_name': u'centos7-pike-ppa', u'version': u'centos', u'cobbler_name': u'CentOS-7-Minimal-1708', u'aliase': u'centos7'}}) => {"attempts": 10, "changed": true, "cmd": "name=\"CentOS-7-Minimal-1708\"\n docker exec compass-cobbler bash -c \"service cobblerd restart;\nsleep 3;\ncobbler import --name $name \\\n--path<file://n--path> /mnt/CentOS-7-x86_64-Minimal-1708 \\\n--arch<file://n--arch> x86_64 \\\n--kickstart<file://n--kickstart> /var/lib/cobbler/kickstarts/default.ks \\\n--breed<file://n--breed> redhat\"", "delta": "0:00:03.602367", "end": "2018-04-19 14:27:34.678629", "failed": true, "item": {"key": "CentOS-7", "value": {"aliase": "centos7", "breed": "redhat", "cobbler_arch": "x86_64", "cobbler_name": "CentOS-7-Minimal-1708", "iso_name": "CentOS-7-x86_64-Minimal-1708", "kickstart": "default.ks", "ppa_name": "centos7-pike-ppa", "version": "centos"}}, "rc": 155, "start": "2018-04-19 14:27:31.076262", "stderr": "Redirecting to /bin/systemctl restart cobblerd.service\nhttpd does not appear to be running and proxying cobbler, or SELinux is in the way. Original traceback:\nTraceback (most recent call last):\n File \"/usr/lib/python2.7/site-packages/cobbler/cli.py\", line 252, in check_setup\n s.ping()\n File \"/usr/lib64/python2.7/xmlrpclib.py\", line 1233, in __call__\n return self.__send(self.__name, args)\n File \"/usr/lib64/python2.7/xmlrpclib.py\", line 1587, in __request\n verbose=self.__verbose\n File \"/usr/lib64/python2.7/xmlrpclib.py\", line 1273, in request\n return self.single_request(host, handler, request_body, verbose)\n File \"/usr/lib64/python2.7/xmlrpclib.py\", line 1321, in single_request\n response.msg,\nProtocolError: <ProtocolError for 10.1.0.1:80/cobbler_api: 404 Not Found>", "stderr_lines": ["Redirecting to /bin/systemctl restart cobblerd.service", "httpd does not appear to be running and proxying cobbler, or SELinux is in the way. Original traceback:", "Traceback (most recent call last):", " File \"/usr/lib/python2.7/site-packages/cobbler/cli.py\", line 252, in check_setup", " s.ping()", " File \"/usr/lib64/python2.7/xmlrpclib.py\", line 1233, in __call__", " return self.__send(self.__name, args)", " File \"/usr/lib64/python2.7/xmlrpclib.py\", line 1587, in __request", " verbose=self.__verbose", " File \"/usr/lib64/python2.7/xmlrpclib.py\", line 1273, in request", " return self.single_request(host, handler, request_body, verbose)", " File \"/usr/lib64/python2.7/xmlrpclib.py\", line 1321, in single_request", " response.msg,", "ProtocolError: <ProtocolError for 10.1.0.1:80/cobbler_api: 404 Not Found>"], "stdout": "", "stdout_lines": []} FAILED - RETRYING: cobbler import iso (10 retries left). What am I missing? Regards, Mark Mark Beierl SW System Sr Principal Developer Dell EMC | Cloud & Communication Service Provider Solution mobile +1 613 314 8106<tel:1-613-314-8106> [email protected]<mailto:[email protected]> On Apr 17, 2018, at 23:50, wutianwei <[email protected]<mailto:[email protected]>> wrote: Hi Mark, If you have a single node, you could try the virtual deployment quick start, more information refer to the wiki page[1]. When virtual deployment, there are no requirement about multiple physical networks, but need access to Internet. btw, it is necessary to launch VMs, and each VM need 8vCPU and 16 GB memory as default. The ha scenarios need 5 VMs, and the noha scenarios need 2 VMs. So the single node need a powerful performance. [1] https://wiki.opnfv.org/display/compass4nfv/Containerized+Compass#ContainerizedCompass-QuickStart: Thanks, Tianwei Wu 发件人: [email protected]<mailto:[email protected]> [mailto:[email protected]] 代表 Beierl, Mark 发送时间: 2018年4月17日 22:17 收件人: [email protected]<mailto:[email protected]> 主题: [opnfv-tech-discuss] [compass] Virtual install on single node Hello, What are the requirements for deploying compass in a virtual environment. I am trying to use the LaaS pods, and I only have one IP address for management. Therefore, there is no provider network. Can I just create a non-routed interface on one of the unused NICs, or do I need to have multiple physical networks in place? Alternatively, should I create a VM with the networks in place and use that for all the deployments? Regards, Mark Mark Beierl SW System Sr Principal Developer Dell EMC | Cloud & Communication Service Provider Solution mobile +1 613 314 8106<tel:1-613-314-8106> [email protected]<mailto:[email protected]>
_______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
