I am looking for help in properly configuring a TripleO environment on a
machine with two network cards talking to two baremetal nodes in the
overcloud also with two network cards. One network will be for
provisioning and one will be for internet connection. I have documented
my current confi
Joe Talerico wrote on 10/09/2017 11:26:14 AM:
> If you ssh to your compute node can you ping 172.16.0.14?
Just a quick note to let everyone know that I am no longer seeing this
problem.
I had to wait a while for lab services to update the firmware and then I
was
seeing IP conflicts with rogue
I am seeing "Can't connect to MySQL server on '9.114.118.250' ([Errno 113]
EHOSTUNREACH)" when installing tripleo
Debugging it further, it seems that corosync will not start and returns an
error code of 8. This seems like not an error according to:
http://www.linux-ha.org/doc/dev-guides/_liter
> I just need an understanding on the impact and the timeline. Replying
> here is sufficient.
>
> I assume since some of this work was sort of done earlier outside of
> tripleo and does not affect the default installation path that most
> folks will consume, it shouldn't be impacting to general te
Alex Schultz wrote on 12/13/2017 04:29:49 PM:
> On Wed, Dec 13, 2017 at 3:22 PM, Mark Hamzy wrote:
> > What I have done at a high level is to rename the images into
architecture
> > specific
> > images. For example,
> >
> > (undercloud) [stack@
Alex Schultz wrote on 12/14/2017 09:24:54 AM:
> On Wed, Dec 13, 2017 at 6:36 PM, Mark Hamzy wrote:
> ... As I said previously, please post the
> patches ASAP so we can get eyes on these changes. Since this does
> have an impact on the existing functionality this should have b
When the system boots up, the IP addresses seem correct:
Jun 6 12:43:07 overcloud-controller-0 cloud-init: ci-info: | eno5: |
True | . | . | . | 6c:ae:8b:25:34:ed |
Jun 6 12:43:07 overcloud-controller-0 cloud-init: ci-info: | eno4: |
True | 9.114.118.241 |
I am trying to delete the Storage, StorageMgmt, Tenant, and Management
networks and trying to deploy using TripleO.
The following patch
https://hamzy.fedorapeople.org/0001-RedisVipPort-error-internal_api.patch
applied on top of /usr/share/openstack-tripleo-heat-templates from
openstack-tripleo
What is the proper way to use NetConfigDataLookup? I tried the following:
(undercloud) [stack@oscloud5 ~]$ cat << '__EOF__' >
~/templates/mapping-info.yaml
parameter_defaults:
NetConfigDataLookup:
control1:
nic1: '5c:f3:fc:36:dd:68'
nic2: '5c:f3:fc:36:dd:6c'
nic3:
