Red Hat Bugzilla – Bug 1476941
Designate documentation needs to specify the pool to attach to
Last modified: 2017-08-01 23:35:37 EDT
Description of problem:
I followed the steps here:
sudo yum install openstack-designate-api openstack-designate-central openstack-designate-sink openstack-designate-pool-manager openstack-designate-mdns openstack-designate-common python-designate python-designateclient openstack-designate-agent
Loaded plugins: product-id, search-disabled-repos, subscription-manager
No package openstack-designate-api available.
No package openstack-designate-central available.
No package openstack-designate-sink available.
No package openstack-designate-pool-manager available.
No package openstack-designate-mdns available.
No package openstack-designate-common available.
No package python-designate available.
No package openstack-designate-agent available.
Nothing to do
The node is registered with the employee sub on it.
Would be good to include what needs to be done before installing these packages.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.register the controller node
2.attach employee sub
3.Run step 1 here https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html/dns-as-a-service_guide/manual_dnsaas_installation
It would be good to include this in the documentation in the DNSaas prerequisites
- register your system
- attach the right pool
sudo subscription-manager repos --disable=*
sudo subscription-manager repos --enable=rhel-7-server-rpms --enable=rhel-7-server-extras-rpms --enable=rhel-7-server-rh-common-rpms
Perhaps say to reference the doc assumes the user has subscribed to the right channels as specified in  or ?
Thanks for the suggestion. I'll address this by linking to the existing steps for system registration: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html-single/director_installation_and_usage/#sect-Registering_your_System
Moving this work to the large DNSaaS bug, so that all the changes can be added in together as a single transaction.
*** This bug has been marked as a duplicate of bug 1423360 ***