Description of problem:
Downstream packages are named "rhscon-*", and upstream packages are named "tendrl-*"

Version-Release number of selected component (if applicable):
rhscon-api-0.0.1-1.el7
rhscon-api-doc-0.0.1-1.el7
rhscon-api-httpd-0.0.1-1.el7
rhscon-ceph-integration-1.1-1.el7
rhscon-common-0.0.1-1.el7
rhscon-dashboard-1.1-1.el7
rhscon-gluster-integration-0.0.1-1.el7
rhscon-node-agent-0.0.1-1.el7


How reproducible:
always

Steps to Reproduce:
1. Look at the builds list at 
2. Compare this to the upstream build list at https://copr.fedorainfracloud.org/coprs/tendrl/tendrl/builds/

Actual results:
Upstream packages are named differently

Expected results:
Minimal or no naming differences

Additional info:
This naming difference is something that happened in the RH Storage Console 2 product, and I'd really love to see it go away during RH Storage Console 3.

Here are the areas where this naming difference is going to cause confusion:

1. Upstream docs will need to be rewritten for downstream.

2. Upstream test tools that install Tendrl will need to be altered to handle the downstream builds. This introduces code complexity and reduces the opportunity to share test tooling between upstream and downstream. This becomes even more difficult when talking about integrating testing between teams external to RH Storage Console, like the Openstack team or the Ceph team.

3. Any kind of installation tools for Tendrl will need to be different between upstream and downstream, introducing code and process complexity. This would affect the QEMU image kickstart configurations between upstream and downstream, any future container images, etc.

4. Any kind of automated tooling for builds (ie Jenkins) that makes our build process faster cannot be re-used as-is between upstream and downstream.


I am not sure why we would rename packages downstream. It will adversely affect other teams (especially docs and QE) for questionable gain, and ultimately hurt efforts for "upstream first" and "staying close to upstream".