Checking with dsneddon what would be the best course of action here.

So I think we need to test by adjusting the environment files during upgrade with the file which worked for OSP11 fresh deployment(https://bugzilla.redhat.com/show_bug.cgi?id=1416355#c10)

One question that I have: in OSP10 we didn't have to pass the ControlPlaneIP parameter but it looks like in OSP11 passing ControlFixedIPs is mandatory, otherwise the default is going to be used which could not match the existing ctlplane subnet. Can we get a clarification on what the ControlFixedIPs is used for? Does it needs to be configured on the external loadbalancer?

Hi,

After discussing with Marius, we think there are two issues here:

 - one is a documentation problem: We need to make the user aware of
   the breaking changes introduced in osp11 for ext-lb:
   - parameter name change;
   - new required modules;

This would be solved by a documentation bug.  Marius is currently
investigating what should go into this documentation.

 - the other one is what seems to be an useless requirement for
   ControlFixedIPs.  Marius is validating that as well and we will
   open a new bz based on his finding for tracking this one.

Bottom line: we're going to solve this one as documentation.

Adding HardProv for awareness and help to get this right.

Hi Lucas,

hum ... it's because the change has been made by a member of your team so I just made a simple association here.  But all in all, you're right it make more sense to put the networking squad in the loop.

Thanks,

(In reply to Sofer Athlan-Guyot from comment #5)
> Hi Lucas,
> 
> hum ... it's because the change has been made by a member of your team so I
> just made a simple association here.  But all in all, you're right it make
> more sense to put the networking squad in the loop.
> 
> Thanks,

It seems like the issue is a backwards incompat change to TripleO Heat Templates. Is there anything you expect from the Network team here?

Based on today's sync (and Sofer), this is going to be documentation effort.

Dan can you please sync with Sofer and Marius on the update of our documentation, please?

In addition to bug 1416355 which tracks the parameters change we need to document that the external loadbalancer configuration needs to be updated with the new services introduced in OSP11 for the nova placement api and Panko API.

HAProxy example configs:

listen nova_placement
  bind 10.0.0.120:8778 transparent
  bind 172.16.18.120:8778 transparent
  mode http
  http-request set-header X-Forwarded-Proto https if { ssl_fc }
  http-request set-header X-Forwarded-Proto http if !{ ssl_fc }
  server overcloud-serviceapi-0.internalapi.localdomain 10.0.0.124:8778 check fall 5 inter 2000 rise 2
  server overcloud-serviceapi-1.internalapi.localdomain 10.0.0.125:8778 check fall 5 inter 2000 rise 2
  server overcloud-serviceapi-2.internalapi.localdomain 10.0.0.126:8778 check fall 5 inter 2000 rise 2

listen panko
  bind 10.0.0.120:8779 transparent
  bind 172.16.18.120:8779 transparent
  http-request set-header X-Forwarded-Proto https if { ssl_fc }
  http-request set-header X-Forwarded-Proto http if !{ ssl_fc }
  server overcloud-serviceapi-0.internalapi.localdomain 10.0.0.124:8779 check fall 5 inter 2000 rise 2
  server overcloud-serviceapi-1.internalapi.localdomain 10.0.0.125:8779 check fall 5 inter 2000 rise 2
  server overcloud-serviceapi-2.internalapi.localdomain 10.0.0.126:8779 check fall 5 inter 2000 rise 2

Assigning to Dan to cover as part of work on upgrades.

Dan, feel free to close this one out if you have a central tracker you'd prefer to use.

Thanks, Marius.

@Sofer, did you have any feedback?

Hi Dan,

from comment #3, the first part (doc) is good.  The second point (ControlFixedIPs) has been answered as well.  So all is good on my side.

Thanks Dan.

Thanks, Sofer!