Setting ccollett as the peer reviewer. Charelle, this *might* also impact of the Overcloud Bare Metal guide, so it might be good to read over this content once it gets ON_QA status.

Hi Mike,

I've CC'd Charelle Collett, who is working on our overcloud bare metal guide. I think it might be better to put the overcloud-specific content there.

Charelle, is this something you'll be able to implement for the bare metal guide? I can provide advice on how to implement it if need be.

Hi Dan, Mike,

If it's adding an extra section to the bare metal guide, I can definitely do that.  Is the section be for migrating from pxe_ssh to VirtualBMC with the Bare Metal service in the overcloud?  I'll definitely be asking you for implementation advice, Dan.

Would it be for both OSP10 and 11?

Cheers,
Char.

Hi, 

Mike is right, the migration section should cover the step required in the overcloud that updates the parameter "IronicEnabledDrivers" for those users moving from pxe_ssh to vbmc+pxe_ipmitool in OSP 11. 

@Charelle, in response to your question, vbmc is not part of OSP 10.

@Dan, as this is only required in the context of using pxe_ssh and now vbmc, rather than part of the general workflow of installing Ironic in the Overcloud, and in particular, when replacing pxe_ssh by vbmc+pxe_ipmitool, I suggest to include it in the appendix Dan is working on. Without updating "IronicEnabledDrivers" the deployment will fail, which is what Mike uncovered when testing it, and that will only be relevant for users testing on virtual machines.

Dan, what do you think about replacing "enterprise" by "production" in "It is not recommended for Red Hat OpenStack Platform enterprise environments."? My reasoning is that for non-production environments, dev+test and staging for instance, is still enterprise if that makes sense?

(In reply to Ramon Acedo from comment #8)
> @Dan, as this is only required in the context of using pxe_ssh and now vbmc,
> rather than part of the general workflow of installing Ironic in the
> Overcloud, and in particular, when replacing pxe_ssh by vbmc+pxe_ipmitool, I
> suggest to include it in the appendix Dan is working on. Without updating
> "IronicEnabledDrivers" the deployment will fail, which is what Mike
> uncovered when testing it, and that will only be relevant for users testing
> on virtual machines.

This isn't a good idea. The appendix I'm working on is specific to the undercloud. Charelle has a similar appendix for drivers in the Bare Metal Guide and this is targeted specifically for the overcloud.

I *strongly* recommend against putting the overcloud-specific instructions in with the undercloud-specific instructions.

> 
> Dan, what do you think about replacing "enterprise" by "production" in "It
> is not recommended for Red Hat OpenStack Platform enterprise environments."?
> My reasoning is that for non-production environments, dev+test and staging
> for instance, is still enterprise if that makes sense?

Sure, I'm okay with the switch.

Understood Dan, that makes sense. In that case I understand the instructions for migrating for nodes in the Overcloud can be covered in the section Charelle is working on. Thanks.

Perhaps just make a link to it from each section (if not already)

That looks good to me, Dan.

I'll add the overcloud content as an update to the OSP11 guide once it is published.  Should I create/clone a new BZ for this?

Yep, clone would be the best way.

Sorry, accidentally mixed the Assignee and QA.

Closing this bug as the Undercloud content is already live.