Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Red Hat / CloudForms should not be mentioned #1423

Open
2 tasks done
davidbaren opened this issue Apr 22, 2020 · 5 comments
Open
2 tasks done

Red Hat / CloudForms should not be mentioned #1423

davidbaren opened this issue Apr 22, 2020 · 5 comments

Comments

@davidbaren
Copy link
Contributor

davidbaren commented Apr 22, 2020

Red Hat is mentioned unnecessarily

@Fryguy
Copy link
Member

Fryguy commented Apr 22, 2020

@davidbaren Both of those are merged, but I'll leave this open if you find more. You can edit the first post to add more checklist items. If you think you are all done, feel free to close.

@Fryguy Fryguy added the bug label Apr 22, 2020
@Fryguy Fryguy self-assigned this Apr 22, 2020
@Fryguy Fryguy changed the title Red Hat should not be mentioned Red Hat / CloudForms should not be mentioned Jun 4, 2020
@Fryguy
Copy link
Member

Fryguy commented Jun 4, 2020

@stacyped here is the issue for replacing Red Hat and CloudForms terminology with placeholders.

@chessbyte
Copy link
Member

@Fryguy what is the placeholder? It would be good to have that described in this issue so that anybody in the community can tackle this.

@Fryguy
Copy link
Member

Fryguy commented Jun 4, 2020

The strings to look out for are:

  • Red Hat CloudForms => {{ site.data.product.product.title }}
  • CloudForms => {{ site.data.product.product.title_short }}
  • cloudforms => {{ site.data.product.product.title_short_l }}
  • cfme => {{ site.data.product.product.title_abbr }}
  • CFME => {{ site.data.product.product.title_abbr_uc }}

You may also find

  • Red Hat -> likely can just be removed except when listed as a part of a provider name as in Red Hat Virtualization or Red Hat OpenShift
  • CloudForms Management Engine -> I'm thinking just
    {{ site.data.product.product.title_short }}

@Fryguy
Copy link
Member

Fryguy commented Jul 7, 2020

Remanining references to cloudforms (aside from URLs):

appliance_hardening_guide/_topics/db_ssl.md:11:For more information, see the [Appliance Hardening Guide](#_chap_red_hat_cloudforms_security_guide_ssl_certs) on generating an SSL certificate.
appliance_hardening_guide/_topics/ssl_certs.md:76:If your environment consists of multiple appliances connecting to a single database appliance, you can use your certificate and key files to set up SSL for the database connection. For more information, see [Configuring the Database to use SSL](#_chap_red_hat_cloudforms_security_guide_setting_ssl_for_the_database_appliance).
creating_a_service_for_vm_provisioning/_topics/provisioning_a_vm_using_ssui.md:4:    <https://<your_cloudforms_appliance>/self_service>.
creating_a_service_for_vm_provisioning/index.md:4:# Creating a Service in CloudForms for Virtual Machine Provisioning
general_configuration/_topics/configuration.md:2228:![cloudforms general config roles 460469 1017
general_configuration/_topics/configuration.md:2229:jcs](../images/cloudforms_general_config_roles_460469_1017_jcs.png)
high_availability_guide/_topics/ha_roles.md:23:![cloudforms ha architecture 431939 0917 ece
high_availability_guide/_topics/ha_roles.md:24:02](../images/cloudforms_ha_architecture_431939_0917_ece-02.png)
high_availability_guide/_topics/ha_roles.md:33:See [Deploying CloudForms at
high_availability_guide/_topics/haproxy.md:55:![cloudforms ha architecture 431939 0917 ece
high_availability_guide/_topics/haproxy.md:56:01](../images/cloudforms_ha_architecture_431939_0917_ece-01.png)
installing_on_openshift_container_platform/_topics/installation.md:284:        template "cloudforms" created
installing_on_openshift_container_platform/_topics/installation.md:290:        cloudforms   CloudForms appliance with persistent storage   18 (1 blank)      12
installing_on_openshift_container_platform/_topics/installation.md:295:        $ oc process --parameters -n <your-project> cloudforms
installing_on_openshift_container_platform/_topics/installation.md:304:        $ oc new-app --template=cloudforms
installing_on_openshift_container_platform/_topics/installation.md:310:        $ oc new-app --template=cloudforms -p DATABASE_VOLUME_CAPACITY=2Gi,POSTGRESQL_MEM_LIMIT=4Gi,APPLICATION_DOMAIN=hostname
installing_on_openshift_container_platform/_topics/installation.md:349:        $ oc new-app --template=cloudforms-ext-db -p DATABASE_IP=<server_ip> -p DATABASE_USER=<user> -p DATABASE_PASSWORD=<password> -p DATABASE_NAME=<database_name>
installing_on_openshift_container_platform/_topics/installation.md:370:            cloudforms-0         1/1       Running   0          4m
installing_on_openshift_container_platform/_topics/installation.md:433:        $ oc set triggers dc --manual -l app=cloudforms
installing_on_openshift_container_platform/_topics/installation.md:437:        $ oc set triggers dc --from-config --auto -l app=cloudforms
installing_on_openshift_container_platform/_topics/installation.md:469:        cloudforms   cfme.apps.e2e.example.com  cloudforms:443-tcp   passthrough                app=cloudforms
installing_on_openshift_container_platform/_topics/post-installation.md:29:    $ oc scale statefulset cloudforms --replicas=2
installing_on_openshift_container_platform/_topics/post-installation.md:30:    statefulset "cloudforms" scaled
installing_on_openshift_container_platform/_topics/post-installation.md:33:    cloudforms-0           1/1       Running   0          34m
installing_on_openshift_container_platform/_topics/post-installation.md:34:    cloudforms-1           1/1       Running   0          5m
installing_on_openshift_container_platform/_topics/post-installation.md:38:The newly created replicas will join the existing {{ site.data.product.title_short }} region. Each new pod is numbered in the order it is deployed, starting with 0 and increasing sequentially. For example, replicas in a StatefulSet will be numbered *cloudforms-0* *cloudforms-1*, and so on.
installing_on_openshift_container_platform/_topics/post-installation.md:103:        $ oc scale statefulset cloudforms --replicas=0
installing_on_openshift_container_platform/_topics/post-installation.md:104:        $ oc scale statefulset cloudforms-backend --replicas=0
installing_on_openshift_container_platform/_topics/post-installation.md:108:        $ oc patch statefulset cloudforms -p '{"spec": {"template": {"spec": {"containers": [{"name": "cloudforms", "image": "registry.redhat.io/cloudforms46/cfme-openshift-app-ui:<new-version-tag>"}]}}}}'
installing_on_openshift_container_platform/_topics/post-installation.md:109:        $ oc patch statefulset cloudforms-backend -p '{"spec": {"template": {"spec": {"containers": [{"name": "cloudforms", "image": "registry.redhat.io/cloudforms46/cfme-openshift-app:<new-version-tag>"}]}}}}'
installing_on_openshift_container_platform/_topics/post-installation.md:113:        $ oc scale statefulset cloudforms --replicas=<old-value>
installing_on_openshift_container_platform/_topics/post-installation.md:114:        $ oc scale statefulset cloudforms-backend --replicas=<old-value>
installing_on_openshift_container_platform/_topics/post-installation.md:128:        $ oc export secret cloudforms-secrets > my_secrets.yml
installing_on_openshift_container_platform/_topics/post-installation.md:132:        $ oc scale statefulset cloudforms --replicas=0
installing_on_openshift_container_platform/_topics/post-installation.md:133:        $ oc scale statefulset cloudforms-backend --replicas=0
installing_on_openshift_container_platform/_topics/post-installation.md:145:            $ oc process -p APPLICATION_REPLICA_COUNT=0 -l app=cloudforms,template=cloudforms -f cfme-template.yaml | oc replace -f -
installing_on_openshift_container_platform/_topics/post-installation.md:149:            $ oc process -p APPLICATION_REPLICA_COUNT=0 -l app=cloudforms,template=cloudforms-ext-db -f cfme-template-ext-db.yaml | oc replace -f -
installing_on_openshift_container_platform/_topics/post-installation.md:161:        $ oc scale statefulset cloudforms --replicas=<old-value>
installing_on_openshift_container_platform/_topics/post-installation.md:162:        $ oc scale statefulset cloudforms-backend --replicas=<old-value>
installing_on_openshift_container_platform/_topics/troubleshooting.md:11:        cloudforms-1-deploy  0/1       Error     0          25m
installing_on_openshift_container_platform/_topics/troubleshooting.md:15:        $ oc deploy cloudforms --retry
installing_on_openshift_container_platform/_topics/troubleshooting.md:17:        Use 'oc logs -f dc/cloudforms' to track its progress.
installing_on_openshift_container_platform/_topics/troubleshooting.md:27:        15m     15m     1   {kubelet ocp-eval-node-2.e2e.example.com}   spec.containers{cloudforms} Warning     Unhealthy   Readiness probe failed: Get http://10.1.1.5:80/: dial tcp 10.1.1.5:80: getsockopt: connection refused
installing_on_red_hat_virtualization/_topics/installation.md:43:CloudForms appliance to your Red Hat Virtualization environment and
managing_authentication/_topics/external_ad.md:204:    `cloudforms` group.
managing_authentication/_topics/external_ad.md:214:Any user who is part of `cloudforms` AD group can now log in to
managing_authentication/_topics/external_ad.md:220:{{ site.data.product.title_short }} user interface with a user in the `cloudforms` AD
managing_authentication/_topics/external_ad.md:225:`cloudforms` AD group. When that user attempts to log in to
managing_authentication/index.md:4:# Managing Authentication for CloudForms
managing_infrastructure_and_inventory/_topics/container_entities.md:105:See [*Scanning Container Images in CloudForms with
scripting_actions/index.md:4:# Scripting Actions in CloudForms
service_provisioning_using_an_orchestration_template/index.md:4:# Service Provisioning in CloudForms Using an Orchestration Template

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants