Bug 704633

Screenshots for adding Red Hat repositories:


=== Method Select ===

rhui (repo) => a

Loading latest entitled products from Red Hat...
... listings loaded
Determining undeployed products...
... product list calculated

Import Repositories:
  1  - All in Certificate
  2  - By Product
  3  - By Repository
Enter value (1-3) or 'b' to abort: 



=== All Repositories ===

Enter value (1-3) or 'b' to abort: 1

All repositories for all entitled products will be imported in
this process. This may result in multiple repositories being imported,
such as if a product is supported on multiple architectures.

The following products will be deployed:
  Red Hat Enterprise Linux Server 6 Releases (RPMs)
    Red Hat Enterprise Linux Server 6 Releases (RPMs) (6Server-x86_64)
    Red Hat Enterprise Linux Server 6 Releases (RPMs) (6Server-i386)
  Red Hat Enterprise Linux Server 6 Releases (SRPMS)
    Red Hat Enterprise Linux Server 6 Releases (SRPMS) (6Server-x86_64)
    Red Hat Enterprise Linux Server 6 Releases (SRPMS) (6Server-i386)
  Red Hat Enterprise Linux Server 6 Updates (RPMs)
    Red Hat Enterprise Linux Server 6 Updates (RPMs) (6Server-x86_64)
    Red Hat Enterprise Linux Server 6 Updates (RPMs) (6Server-i386)
  Red Hat Enterprise Linux Server 6 Updates (SRPMS)
    Red Hat Enterprise Linux Server 6 Updates (SRPMS) (6Server-i386)
    Red Hat Enterprise Linux Server 6 Updates (SRPMS) (6Server-x86_64)
Proceed? (y/n) 


=== By Repository ===

Enter value (1-3) or 'b' to abort: 3

Select the product repositories to be deployed to the RHUI (only undeployed
products are displayed):
  Red Hat Enterprise Linux Server 6 Optional Updates (SRPMS)
    -  1 : Red Hat Enterprise Linux Server 6 Optional Updates (SRPMS) (6Server-i386)
    -  2 : Red Hat Enterprise Linux Server 6 Optional Updates (SRPMS) (6Server-x86_64)

  Red Hat Enterprise Linux Server 6 Updates (RPMs)
    -  3 : Red Hat Enterprise Linux Server 6 Updates (RPMs) (6Server-x86_64)
    -  4 : Red Hat Enterprise Linux Server 6 Updates (RPMs) (6Server-i386)

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

[snip]

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

The following product repositories will be deployed:
  Red Hat Enterprise Linux Server 6 Optional Updates (SRPMS)
    Red Hat Enterprise Linux Server 6 Optional Updates (SRPMS) (6Server-i386)
Proceed? (y/n)

Procedure 5.5. List Packages in a Repository

Might want to put a link back to the shell page to tell them they can always get a full package listing, regardless of size, using the shell commands.

-----

(In reply to comment #0)
> "From the Repository Management screen, type l at the prompt to display
> information about a particular repository: "
> 
> Typo: "type i" not "type l"
> 

<para>
	From the Repository Management screen, type <userinput>i</userinput> at the prompt to list the repositories currently being managed by the RHUI:
</para>
			 
<screen>
------------------------------------------------------------------------------
rhui (repo) =&gt; i

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)
  Red Hat Update Infrastructure 1.2 (SRPMS) (5Server-i386)
  Red Hat Update Infrastructure 1.2 (SRPMS) (5Server-x86_64)


------------------------------------------------------------------------------
</screen>

> -----
> 
> "Select which repositories to view, by typing the number of the repository at
> the prompt: "
> 
> No comma.
> 

<para>
	A list of all repositories currently being managed by the RHUI will be displayed. Select which repositories to view by typing the number of the repository at the prompt:
</para>

> -----
> 
> "Enter value from (1-5) to toggle selection"
> 
> I took your advice and removed the "from" in this prompt. It's your call if you
> want to update your examples accordingly.
> 

Took them out, let me know if I missed any.

> -----
> 
> Info Example
> 
> Last Sync:          05-11-2011 16:01
> Next Sync:          05-13-2011 16:01
> 
> (in response to your note:
> Last Sync:          1302813062 This needs to be a date)
> 
> Also want to update the example since Next/Last sync do not appear for custom
> repos. Custom repos aren't syncced, only Red Hat ones.
> 

<screen>
Enter value (1-5) to toggle selection, 'c' to confirm selections, or '?'
for more commands: c

Name:               Custom Repository 1
Type:               Custom
Relative Path:      custom/i386
Entitlement Path:   /custom/$basearch
Package Count:      0

Name:               Red Hat Update Infrastructure 1.2 (RPMs) (5Server-i386)
Type:               Red Hat
Relative Path:      content/dist/rhel/rhui/server/5Server/i386/rhui/1.2/os
Package Count:      13
Last Sync:          05-11-2011 16:01
Next Sync:          05-13-2011 16:01

------------------------------------------------------------------------------
rhui (repo) =&gt;
</screen>

> ----
> 
> Add a Red Hat Repository
> 
> "Before adding a new Red Hat repository, you will need to contact Red Hat and
> have the specific repositories loaded for your entitled products. For example,
> if your content certificate grants access to the product Red Hat Enterprise
> Linux Server (RPMs), you will need to have both 32-bit and 64-bit repositories
> loaded by Red Hat so that RHUI Manager can perform the translation."
> 
> Not exactly. What happens is that RHUI Manager goes out to RHN and downloads
> the valid repositories for each product. They don't need to do anything in
> terms of contacting Red Hat themselves.

<para>
	Before adding a new &RH; repository, you will need to have the specific repositories loaded for your entitled products. For example, if your content certificate grants access to the product <filename>Red Hat Enterprise Linux Server (RPMs)</filename>, you will need to have both 32-bit and 64-bit repositories loaded. This occurs automatically when RHUI Manager contacts RHN.
</para>

Is that right?


Revision 1-9.

LKB

(In reply to comment #2)
> Procedure 5.5. List Packages in a Repository
> 
> Might want to put a link back to the shell page to tell them they can always
> get a full package listing, regardless of size, using the shell commands.
> 
> -----

Added note:

<note>
	<title>Note</title>
	<para>
		When listing repositories within RHUI Manager, only repositories that contain less than 100 packages will have their contents displayed. Results with more than 100 packages will display a package count only. To see a complete list, regardless of how many packages are contained within a repository, use the <command>rhui-manager packages list</command> command at the shell prompt instead. See <xref linkend="sect-Installation_Guide-RHUI_Manager-Using_RHUI_Manager_from_the_Shell_Prompt" /> for more information about managing RHUI from the shell prompt.
	</para>
</note>


Revision 1-9

LKB

*** Bug 705717 has been marked as a duplicate of this bug. ***

In section 5.1 List Repositories:

From the Repository Management screen, type l at the prompt to list the repositories currently
being managed by the RHUI:
------------------------------------------------------------------------------
rhui (repo) => l
Custom Repositories
Custom Repository 1
Red Hat Repositories
Red Hat Update Infrastructure
Red Hat Update Infrastructure
Red Hat Update Infrastructure
Red Hat Update Infrastructure
1.2
1.2
1.2
1.2
(RPMs) (5Server-i386)
(RPMs) (5Server-x86_64)
(SRPMS) (5Server-i386)
(SRPMS) (5Server-x86_64)


The sentence and the example needs to be corrected.
It has to be "type l" and not "type i".


For section 5.2 List repositories :

From the Repository Management screen, type i at the prompt to display information about a
particular repository:

In this section only the sentence needs to be corrected( here the example is perfect).
It has to be "type i" and not "type l".

I'm having nightmares about i's and l's now. Try Revision 1-11. Hopefully I've fixed it now.

LKB

agreed.. thats confusing :) looks fixed... kedar/sachin?

:). yes, its changed now in the latest one.

May be I did not notice this earlier but, this entire 1st point needs to be removed. There is no such pre-requisite.

Procedure 5.3. Add a Red Hat Repository

   1.
      Before adding a new Red Hat repository, you will need to have the specific repositories loaded for your entitled products. For example, if your content certificate grants access to the product Red Hat Enterprise Linux Server (RPMs), you will need to have both 32-bit and 64-bit repositories loaded. This occurs automatically when RHUI Manager contacts RHN.

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