We are using the env file environments/neutron-ml2-cisco-nexus-ucsm.yaml for cisco_ucsm mechanism driver and composable role for our needs in NFV. environments/neutron-ml2-cisco-nexus-ucsm.yaml calls puppet/extraconfig/all_nodes/neutron-ml2-cisco-nexus-ucsm.yaml which is not "composable role ready" We are in a case for NFV where we need different type of compute role. For the 'Compute like' role we configure, the parameter ucsm_host_list is not generated. This is a problem when we want to spawn a VM with an SR-IOV interface on a compute. Thanks,
I would like TripleO experts to chime in on this issue. Obviously, the final solution would be for config for Cisco mech drivers to be compossible role compatible. Since, this issue has to be fixed in OSP10, a different solution needs to be found in the meantime. I am currently looking at: tripleo-heat-templates/puppet/extraconfig/all_nodes/neutron-ml2-cisco-nexus-ucsm.yaml I think the reason, compute hosts with different compute roles are being ignored is because of this: CollectMacDeploymentsCompute: type: OS::Heat::SoftwareDeployments properties: name: CollectMacDeploymentsCompute servers: {get_param: [servers, Compute]} <----- config: {get_resource: CollectMacConfig} actions: ['CREATE'] # Only do this on CREATE Looking for suggestions from the Triple experts. Can the "Compute" string be a regular expression? Or, should be create a block like this for every compute role (brute force, I know)?
Opened a new triple bug: https://bugs.launchpad.net/tripleo/+bug/1704853 describing the issue as I see it.
Fix has been back ported to stable/newton via:https://review.openstack.org/#/c/487164/. This needs to make its way into OSP10.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2825
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days