+++ This bug was initially created as a clone of Bug #1939281 +++

Description of problem:

Felix from AWS reached out to us to request zStreams for resource-agents commit b727fe4e.
  - https://github.com/ClusterLabs/resource-agents/pull/1549/commits/b727fe4e

As far as I know, we're already getting this into RHEL 8.4 via a rebase on resource-agents 4.7.0. So this BZ is to request that we get it into 8.1.z and 8.2.z (for SAP support) as well as 8.3.z (in order not to skip one).

I'll open a separate BZ for RHEL 7 and leave that to engineering's discretion. On the one hand, it's technically a new feature. On the other hand, the feature is a way of making the RA compatible with a particular type of infrastructure rather than adding new functionality, and it sounds like there's some significant demand for this.


Conversation with Felix in the support case regarding justification:
~~~
AWS:
>> While I understand that this may be a new feature, this is also OK to ship still on RHEL 8.1 and 8.2. Is it possible to request it?
>> 
>> The main reasons behind my ask are:
>> 
>> 1) AWS customers only use these RAs with their SAP Applications, and currently only RHEL 8.1 and RHEL 8.2 are certified for SAP
>> 2) The only "RHEL 8.x for SAP" versions available for customers in AWS Marketplace are 8.1 and 8.2, and we aren't aware of Red Hat's plans to certify 8.3 and later, or even when it will happen. 
>> 
>> In summary, I'm afraid that waiting for RHEL 8.4 will take way too long and we need to improve this timeline to reduce the time to market of some of these features.

RH:
> Maybe. As far as I know, there's no Bugzilla for it, as there's been no demand expressed to us by Red Hat customers so far. But if the absence of this feature is likely to have a negative impact on users, then it may be possible to backport it.
> 
> I don't fully understand the technology involved in this patch, or how widely used it is and whom it's likely to impact. Can you tell us any more about this, so that we can relay the info to the dev team?

AWS:
2) https://github.com/ClusterLabs/resource-agents/pull/1549

This is the most important one and the one that I really really care to be back ported.  Shared VPC is something that customers are starting to use on their AWS deployments to create more sophisticated and easier to manage VPC (network) architectures and topologies, and this patch will allow our common customers to use shared VPC subnets from a different AWS account with their Red Hat HA cluster nodes.

Most of our customers migrating to AWS, or implementing HA cluster for SAP on AWS are still on RHEL 7.x and since there are no upgrade paths from RHEL 7.x to RHEL 8.x in AWS I would like try to keep it as current as possible and where possible still ship small improvements and feature requests like this one.

Customers are requesting this to us (AWS) as since they are mostly using the AWS provided Red Hat images we end up receiving the feedback directly, and this is likely the reason on why you haven't heard of it on your side. Unfortunately, due to strict security and confidentiality policies I'm not allowed to share customer names, but I can say that there is demand and interest of new and existing customers, and some of them have already deployed RHEL 7.x and are simply waiting for this feature to enable their HA cluster, and others decided to move on with the upstream agent version only to enable this feature (regardless of being aware of support policies).
~~~

-----

Version-Release number of selected component (if applicable):

N/A

-----

How reproducible/Steps to reproduce:

I haven't researched how to set up the infrastructure to test this. I'm relaying this request from AWS.

--- Additional comment from RHEL Program Management on 2021-03-15 22:23:16 UTC ---

840ITRStrip AtFullFreeze

Attention assignees: This BZ was automatically returned to the backlog by changing the Internal Target Release (ITR) to '---'. The change was made because the final release+ deadline was passed and no request for an exception, blocker, or zstream was made.  Please consult with your team to decide what action to take next with this BZ:

1. Important changes that cannot wait for the next minor release should request an exception or blocker (Reset ITR/ITM, set exception? or blocker?, save, then follow the instructions appended to the BZ).

2. Bug fixes that may be best managed post-release can start following the z-stream process (Set ZTR, ITR, and zstream? flag)

3. Changes that can wait for a future release can have their ITR/ITM set to the optimal release target.  Acks are preserved and release+ will again be added.

If you are unsure of what action to take it is safe to leave this BZ in the backlog for the time being.  You may wish to unset your acks in this case.

--- Additional comment from Reid Wahl on 2021-03-15 22:28:51 UTC ---

zStream justification, via Felix from AWS (copied from comment 0):
~~~
>> 1) AWS customers only use these RAs with their SAP Applications, and currently only RHEL 8.1 and RHEL 8.2 are certified for SAP
>> 2) The only "RHEL 8.x for SAP" versions available for customers in AWS Marketplace are 8.1 and 8.2, and we aren't aware of Red Hat's plans to certify 8.3 and later, or even when it will happen. 
>> 
>> In summary, I'm afraid that waiting for RHEL 8.4 will take way too long and we need to improve this timeline to reduce the time to market of some of these features.
...
Shared VPC is something that customers are starting to use on their AWS deployments to create more sophisticated and easier to manage VPC (network) architectures and topologies, and this patch will allow our common customers to use shared VPC subnets from a different AWS account with their Red Hat HA cluster nodes.

Most of our customers migrating to AWS, or implementing HA cluster for SAP on AWS are still on RHEL 7.x and since there are no upgrade paths from RHEL 7.x to RHEL 8.x in AWS I would like try to keep it as current as possible and where possible still ship small improvements and feature requests like this one.

Customers are requesting this to us (AWS) as since they are mostly using the AWS provided Red Hat images we end up receiving the feedback directly, and this is likely the reason on why you haven't heard of it on your side. Unfortunately, due to strict security and confidentiality policies I'm not allowed to share customer names, but I can say that there is demand and interest of new and existing customers, and some of them have already deployed RHEL 7.x and are simply waiting for this feature to enable their HA cluster, and others decided to move on with the upstream agent version only to enable this feature (regardless of being aware of support policies).
~~~

While this is technically a new feature, it's a way of making the RA compatible with a particular type of infrastructure rather than adding new functionality, and it sounds like there's some significant demand for this.

--- Additional comment from RHEL Program Management on 2021-03-24 15:13:08 UTC ---

The BZ has been approved for cloning.

The BZ can be now clone by everyone with the self-service cloning tool http://watson.int.open.paas.redhat.com/rules

For more information regarding RHEL ZStream and cloning please visit https://docs.google.com/document/d/1yL8iTHjxyQ7sI-fC4PcPjpOOyfF5ECGnK-B7r_QRZm4/edit#

--- Additional comment from RHEL Program Management Team on 2021-03-25 12:54:26 UTC ---

This bug has been copied as 8.4.0 stream bug#1943093 and now must be resolved in the current update release, blocker flag set.

This bug has been copied as 8.2.0 stream bug#1943095 and now must be resolved in the current update release, blocker flag set.

This bug has been copied as 8.1.0 stream bug#1943111 and now must be resolved in the current update release, blocker flag set.

--- Additional comment from Reid Wahl on 2021-03-26 22:56:26 UTC ---

There's no 8.3.z clone. I set ZTR 8.3.0 and ran the BZ cloning tool, and it didn't even attempt to make an 8.3.z clone. It skipped 8.3.z.

I'll make one manually but that seems problematic.