Bug 697213 - RHUI Manager: CDS Repository Screen
Summary: RHUI Manager: CDS Repository Screen
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Update Infrastructure for Cloud Providers
Classification: Red Hat
Component: Documentation
Version: 2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Lana Brindley
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks: 695556
TreeView+ depends on / blocked
 
Reported: 2011-04-16 21:26 UTC by Jay Dobies
Modified: 2016-02-18 05:33 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-29 04:43:45 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jay Dobies 2011-04-16 21:26:42 UTC
Unlike the other screens, this is accessed from the CDS Screen, not the Home screen. When choosing to go to this screen, the user is prompted to select one CDS (as compared to many other portions of the UI that allow multi-select).

   r   manage repositories hosted on a CDS instance

Select the CDS instance to manage repositories: 
  1  - US East Region CDS
Enter value from (1-1) or 'b' to abort: 1



Menu:


------------------------------------------------------------------------------
             -= Red Hat Update Infrastructure Management Tool =-


-= CDS Repositories Management - US East Region CDS =-

   l   list repositories deployed on this CDS
   a   deploy (add) a repository to this CDS
   d   undeploy (delete) a repository from this CDS

                                                           Connected: guardian
------------------------------------------------------------------------------
rhui (US East Region CDS) => 



Also unlike other screens, the value in the ( ) in the prompt doesn't specify the screen name but rather the CDS being manipulated.

Comment 1 Jay Dobies 2011-04-16 21:32:21 UTC
Associate Repositories

   a   deploy (add) a repository to this CDS

Configured which repositories will be hosted by the currently selected CDS. The contents of the newly added repositories are not immediately sent to the CDS. The will be sent the next time the repo is synchronized, either from the recurring scheduled sync or by manually triggering one.

Repos can be deployed in two granularities:

- All in RHUI - Pretty self explanatory, all repositories in the RHUI will be hosted by the CDS instance.

- By Repository - Allows the user to select one or more repositories to be deployed, allowing finer control over which CDS instance hosts which repositories. Only currently undeployed repositories are displayed. If all of the repositories are already associated to the CDS, the user is informed of this fact and nothing else occurs.


Sample:

------------------------------------------------------------------------------
rhui (US East Region CDS) => a

Deploy Repositories:
  1  - All in RHUI
  2  - By Repository
Enter value from (1-2) or 'b' to abort: 2

Select the repositories to be deployed to the CDS (only undeployed products are displayed):

  Custom Repositories
    -  1 : Custom Repository 1

  Red Hat Repositories
    -  2 : Red Hat Update Infrastructure 1.2 (RPMs) (5Server-i386)
    -  3 : Red Hat Update Infrastructure 1.2 (RPMs) (5Server-x86_64)

Enter value from (1-3) to toggle selection, 'c' to confirm selections, or '?' for more commands: 1-3

Select the repositories to be deployed to the CDS (only undeployed products are displayed):

  Custom Repositories
    x  1 : Custom Repository 1

  Red Hat Repositories
    x  2 : Red Hat Update Infrastructure 1.2 (RPMs) (5Server-i386)
    x  3 : Red Hat Update Infrastructure 1.2 (RPMs) (5Server-x86_64)

Enter value from (1-3) to toggle selection, 'c' to confirm selections, or '?' for more commands: c


Custom Repositories
  Custom Repository 1

Red Hat Repositories
  Red Hat Update Infrastructure 1.2 (RPMs) (5Server-i386)
  Red Hat Update Infrastructure 1.2 (RPMs) (5Server-x86_64)

Proceed? (y/n) 



Already associated all repos:

------------------------------------------------------------------------------
rhui (US East Region CDS) => a

All repositories are deployed to CDS US East Region CDS

------------------------------------------------------------------------------
rhui (US East Region CDS) =>

Comment 2 Jay Dobies 2011-04-16 21:33:20 UTC
I missed the tail end of my first sample in associate. After selecting 'y' for proceed:

Proceed? (y/n) y


Associating repository Custom Repository 1...
Associating repository Red Hat Update Infrastructure 1.2 (RPMs) (5Server-i386)...
Associating repository Red Hat Update Infrastructure 1.2 (RPMs) (5Server-x86_64)...

Content will not be downloaded to the CDS until the next sync is run.

------------------------------------------------------------------------------
rhui (US East Region CDS) => a

Comment 3 Jay Dobies 2011-04-16 21:34:29 UTC
Unassociate a Repo

   d   undeploy (delete) a repository from this CDS

Very similar to associate in the sense that the changes are not made on the CDS itself until a sync is run.

The user selects one or more repos from the currently associated repos and confirms the delete.


Sample:


rhui (US East Region CDS) => d

Select one or more repositories to undeploy from the CDS:

  Custom Repositories
    -  1 : Custom Repository 1

  Red Hat Repositories
    -  2 : Red Hat Update Infrastructure 1.2 (RPMs) (5Server-i386)
    -  3 : Red Hat Update Infrastructure 1.2 (RPMs) (5Server-x86_64)

Enter value from (1-3) to toggle selection, 'c' to confirm selections, or '?' for more commands: 2-3

Select one or more repositories to undeploy from the CDS:

  Custom Repositories
    -  1 : Custom Repository 1

  Red Hat Repositories
    x  2 : Red Hat Update Infrastructure 1.2 (RPMs) (5Server-i386)
    x  3 : Red Hat Update Infrastructure 1.2 (RPMs) (5Server-x86_64)

Enter value from (1-3) to toggle selection, 'c' to confirm selections, or '?' for more commands: c


The following repositories will be undeployed from the CDS:

Red Hat Repositories
  Red Hat Update Infrastructure 1.2 (RPMs) (5Server-i386)
  Red Hat Update Infrastructure 1.2 (RPMs) (5Server-x86_64)

Proceed? (y/n) y

Unassociating repository Red Hat Update Infrastructure 1.2 (RPMs) (5Server-i386)...
Unassociating repository Red Hat Update Infrastructure 1.2 (RPMs) (5Server-x86_64)...

Content will not be deleted from the CDS until the next sync is run.

------------------------------------------------------------------------------
rhui (US East Region CDS) =>

Comment 4 Jay Dobies 2011-04-16 21:35:58 UTC
List Repositories

   l   list repositories deployed on this CDS

Displays all associated repos.



Sample:

------------------------------------------------------------------------------
rhui (US East Region CDS) => /

rhui (US East Region CDS) => l

-= CDS Repositories =-

  Red Hat Update Infrastructure 1.2 (RPMs) (5Server-i386)
  Red Hat Update Infrastructure 1.2 (RPMs) (5Server-x86_64)
  Custom Repository 1

------------------------------------------------------------------------------
rhui (US East Region CDS) => 




No repos associated:

------------------------------------------------------------------------------
rhui (US East Region CDS) => l

-= CDS Repositories =-

No repositories have been associated with CDS US East Region CDS

------------------------------------------------------------------------------
rhui (US East Region CDS) =>

Comment 5 Jay Dobies 2011-04-16 21:37:11 UTC
Just to be clear on terminology, I tend to use the following interchangably:

Associate = Add = Deploy - Maps a repo to a CDS.
Unassociate = Remove = Undeploy - Removes the mapping of a repo and CDS.

Sorry for jumping around on terms in this BZ.

Comment 6 Lana Brindley 2011-04-17 23:10:06 UTC
Operation/CDS

LKB

Comment 7 Lana Brindley 2011-05-04 00:51:13 UTC
Revision 1-4

LKB

Comment 8 Kedar Bidarkar 2011-05-24 11:47:34 UTC
Managing repositories hosted on CDS Instances is now covered in detail in the docs.

Comment 9 Lana Brindley 2011-07-29 04:43:45 UTC
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


Note You need to log in before you can comment on or make changes to this bug.