| Summary: | Load Balancer | ||
|---|---|---|---|
| Product: | Red Hat Update Infrastructure for Cloud Providers | Reporter: | Jay Dobies <jason.dobies> |
| Component: | Documentation | Assignee: | Lana Brindley <lbrindle> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | wes hayutin <whayutin> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.0 | CC: | jskeoch, kbidarka, mhideo, sghai, tsanders |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-07-29 04:49:59 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Jay Dobies
2011-06-07 13:52:57 UTC
= CDS Repository Management =
Remember how there was that whole screen devoted to selecting which repositories are deployed to which CDS instances? Yeah... that's gone now.
We assume (actually, "enforce" is a better word here) all repositories are deployed to all CDS instances. This isn't technically a regression since this was all that was supported in 1.2.
It has to do with all of the load balancing and fail over awesomeness described above. We can't balance across a bunch of CDS instances without knowing that they all have the same repositories.
That said, it will be coming back in 2.1 (or beyond). Conceptually it will change such that you're not assigning repos to a CDS, but rather to a "CDS cluster" (which is just a group of CDS with similar attributes). That's going to involve additions to be able to manage those clusters, but I'm getting ahead of myself. I only mention it in the context that the work done about CDS-repo associations isn't wasted and will be coming back in some form.
So in terms of docs changes:
- Remove the section on this entirely (6.1. Manage Repositories Hosted on a CDS Instance)
- The CDS menu now doesn't have the option for it. Below is a screenshot of what it looks like now:
------------------------------------------------------------------------------
-= Red Hat Update Infrastructure Management Tool =-
-= Content Delivery Server (CDS) Management =-
l list all CDS instances registered to the RHUI
a register (add) a new CDS instance
d unregister (delete) a CDS instance from the RHUI
Connected: atlantis
------------------------------------------------------------------------------
= Client Configuration RPM = As mentioned previously, the client config RPM creation has changed to not prompt for a load balancer hostname, but instead require the user to select one of the CDS instances to act as the primary. The rest of the CDS instances will be used as backup. This is meant to be a balance between them having zero control of which is acting as the load balancer and having to do a complicated UI where they order the list completely. Below is a screen shot of what it looks like now. Ignore the values I used for all of the questions up to the CDS point; it's just dummy data that will probably confuse users if that's included in the example: ------------------------------------------------------------------------------ rhui (client) => c Local directory in which the client configuration files generated by this tool should be stored (if this directory does not exist, it will be created): /tmp/example Name of the RPM: example-client Version of the configuration RPM [2.0]: Full path to the entitlement certificate authorizing the client to access specific channels: /home/jdob/vault/code/data/rhui-installer/rhui-cds-1.crt Full path to the private key for the above entitlement certificate: /home/jdob/vault/code/data/rhui-installer/server.key Full path to the CA certificate used to sign the CDS SSL certificate: /home/jdob/vault/code/data/rhui-installer/ssl-ca.crt Select the CDS instance that should be the primary load balancer for the client. All other CDS instances will be listed as back up load balancers in the client's mirror list: 1 - cds-1.example.com 2 - cds-2.example.com Enter value (1-2) or 'b' to abort: 2 Load Balancer Order: cds-2.example.com cds-1.example.com Successfully created client configuration RPM. RPMs can be found at /tmp/example ------------------------------------------------------------------------------ (In reply to comment #1) > = CDS Repository Management = > > Remember how there was that whole screen devoted to selecting which > repositories are deployed to which CDS instances? Yeah... that's gone now. > > We assume (actually, "enforce" is a better word here) all repositories are > deployed to all CDS instances. This isn't technically a regression since this > was all that was supported in 1.2. > > It has to do with all of the load balancing and fail over awesomeness described > above. We can't balance across a bunch of CDS instances without knowing that > they all have the same repositories. > > That said, it will be coming back in 2.1 (or beyond). Conceptually it will > change such that you're not assigning repos to a CDS, but rather to a "CDS > cluster" (which is just a group of CDS with similar attributes). That's going > to involve additions to be able to manage those clusters, but I'm getting ahead > of myself. I only mention it in the context that the work done about CDS-repo > associations isn't wasted and will be coming back in some form. > > So in terms of docs changes: > > - Remove the section on this entirely (6.1. Manage Repositories Hosted on a CDS > Instance) > Done. > - The CDS menu now doesn't have the option for it. Below is a screenshot of > what it looks like now: > > ------------------------------------------------------------------------------ > -= Red Hat Update Infrastructure Management Tool =- > > > -= Content Delivery Server (CDS) Management =- > > l list all CDS instances registered to the RHUI > a register (add) a new CDS instance > d unregister (delete) a CDS instance from the RHUI > > Connected: atlantis > ------------------------------------------------------------------------------ Updated. LKB (In reply to comment #2) > = Client Configuration RPM = > > As mentioned previously, the client config RPM creation has changed to not > prompt for a load balancer hostname, but instead require the user to select one > of the CDS instances to act as the primary. The rest of the CDS instances will > be used as backup. > > This is meant to be a balance between them having zero control of which is > acting as the load balancer and having to do a complicated UI where they order > the list completely. > > Below is a screen shot of what it looks like now. Ignore the values I used for > all of the questions up to the CDS point; it's just dummy data that will > probably confuse users if that's included in the example: > > > ------------------------------------------------------------------------------ > rhui (client) => c > > Local directory in which the client configuration files generated by this tool > should be stored (if this directory does not exist, it will be created): > /tmp/example > > Name of the RPM: > example-client > > Version of the configuration RPM [2.0]: > > > Full path to the entitlement certificate authorizing the client to access > specific channels: > /home/jdob/vault/code/data/rhui-installer/rhui-cds-1.crt > > Full path to the private key for the above entitlement certificate: > /home/jdob/vault/code/data/rhui-installer/server.key > > Full path to the CA certificate used to sign the CDS SSL certificate: > /home/jdob/vault/code/data/rhui-installer/ssl-ca.crt > > Select the CDS instance that should be the primary load balancer for the > client. All other CDS instances will be listed as back up load balancers > in the client's mirror list: > > 1 - cds-1.example.com > 2 - cds-2.example.com > Enter value (1-2) or 'b' to abort: 2 > > Load Balancer Order: > cds-2.example.com > cds-1.example.com > > Successfully created client configuration RPM. > RPMs can be found at /tmp/example > > ------------------------------------------------------------------------------ <step> <para> All CDS instances are able to function as load balancers. You will be required to nominate one CDS as a primary load balancer, however if that CDS becomes unavailable, or is unable to function as a load balancer, load balancing tasks will fall to the other available CDS instances. Select a CDS instance to be the primary load balancer for the client: </para> <screen> Select the CDS instance that should be the primary load balancer for the client. All other CDS instances will be listed as back up load balancers in the client's mirror list: 1 - cds-1.example.com 2 - cds-2.example.com Enter value (1-2) or 'b' to abort: 2 </screen> <para> A list of the CDS instances to be used for load balancing will be displayed, in priority order: </para> <screen> Load Balancer Order: cds-2.example.com cds-1.example.command </screen> </step> Revision 1-14. LKB This book is now available at http://docs.redhat.com/docs/en-US/Red_Hat_Update_Infrastructure/2.0/html/Installation_Guide/index.html Please raise a new bug for any further changes. LKB |