Also, it's clear that something has changed re the dependency upon jinja2, 
python-3-ipmi, etc ... per the error I got below when trying to install the 
RPMs:
--> Processing Dependency: python3-ipmi for package: 
opnfv-apex-common-4.0-20170121.noarch
--> Processing Dependency: python3-jinja2 for package: 
opnfv-apex-common-4.0-20170121.noarch
--> Finished Dependency Resolution
Error: Package: opnfv-apex-common-4.0-20170121.noarch 
(/opnfv-apex-common-4.0-20170121.noarch)
           Requires: python3-jinja2
Error: Package: opnfv-apex-common-4.0-20170121.noarch 
(/opnfv-apex-common-4.0-20170121.noarch)
           Requires: python3-ipmi
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles -nodigest

[bryan@opnfv apex]$ sudo yum install -y python-jinja2-2.8-5.el7.centos.src.rpm 
python-markupsafe-0.23-9.el7.centos.src.rpm python3-ipmi-0.3.0-1.noarch.rpm
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
 * base: mirror.hostduplex.com
 * epel: mirrors.kernel.org
 * extras: mirror.scalabledns.com
 * updates: mirrors.kernel.org
No package python-jinja2-2.8-5.el7.centos.src.rpm available.
No package python-markupsafe-0.23-9.el7.centos.src.rpm available.
No package python3-ipmi-0.3.0-1.noarch.rpm available.
Error: Nothing to do
[bryan@opnfv apex]$

Thanks,
Bryan Sullivan | AT&T

From: SULLIVAN, BRYAN L
Sent: Saturday, January 21, 2017 4:36 PM
To: [email protected]
Subject: RE: [Apex] Danube install help

One other thing I forgot in the list added below.

Thanks,
Bryan Sullivan | AT&T

From: SULLIVAN, BRYAN L
Sent: Saturday, January 21, 2017 4:33 PM
To: 
[email protected]<mailto:[email protected]>
Subject: [Apex] Danube install help

Hi Apex team,

I want to get going on installing Apex in a virtual or non-HA/3-node (jumphost, 
control, compute) environment, for Copper, Models, VES. I need to know how the 
install process has changed for Danube, e.g. pre-reqs and command line options.

Here is the process I used for Colorado virtual install. Is all this still 
correct?


*         sudo yum install -y epel-release

*         sudo yum install -y python34

*         sudo yum install -y https://www.rdoproject.org/repos/rdo-release.rpm

*         sudo yum install -y python-jinja2-2.8-5.el7.centos.src.rpm 
python-markupsafe-0.23-9.el7.centos.src.rpm python3-ipmi-0.3.0-1.noarch.rpm

*         Download latest Apex RPMs, e.g. (How do we know which build is stable 
enough to test with? Digging through Jenkins is not a great solution...)

o   wget  http://artifacts.opnfv.org/apex/opnfv-apex-4.0-20170121.noarch.rpm

o   wget  
http://artifacts.opnfv.org/apex/opnfv-apex-common-4.0-20170121.noarch.rpm

o   wget  
http://artifacts.opnfv.org/apex/opnfv-apex-undercloud-4.0-20170121.noarch.rpm

*         sudo yum install -y opnfv-*.rpm

*         sudo opnfv-deploy -v -d /etc/opnfv-apex/os-nosdn-nofeature-noha.yaml 
-n /etc/opnfv-apex/network_settings.yaml

*         sudo opnfv-util undercloud

And for the non-HA bare metal install with flat networking and PXE_WOL, what 
are the options I need to include for the deploy?

If you've documented all this for Danube, a link to the docs/wiki would help.

Thanks,
Bryan Sullivan | AT&T

_______________________________________________
opnfv-tech-discuss mailing list
[email protected]
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Reply via email to