« Deploy/SpaceWalk/Upload » : différence entre les versions

De TartareFR
Aller à la navigation Aller à la recherche
Aucun résumé des modifications
Ligne 114 : Ligne 114 :
{{Spacewalk/repo|name=centos5-updates-i386|url=http://mirror.centos.org/centos/5/updates/i386/}}
{{Spacewalk/repo|name=centos5-updates-i386|url=http://mirror.centos.org/centos/5/updates/i386/}}
{{Spacewalk/repo|name=centos5-rpmforge-i386|url=http://apt.sw.be/redhat/el5/en/i386/rpmforge/}}
{{Spacewalk/repo|name=centos5-rpmforge-i386|url=http://apt.sw.be/redhat/el5/en/i386/rpmforge/}}
{{Spacewalk/repo|name=centos5-epel-i386|url=http://mirrors.fedoraproject.org/mirrorlist?repo=epel-5&arch=i386
{{Spacewalk/repo|name=centos5-epel-i386|url=http://mirrors.fedoraproject.org/mirrorlist?repo=epel-5&arch=i386}}
{{Spacewalk/repo|name=centos5-b2pweb-i386|url=http://koji.b2pweb.com/repos/centos/5/os/RPMS/i386}}
{{Spacewalk/repo|name=centos5-b2pweb-i386|url=http://koji.b2pweb.com/repos/centos/5/os/RPMS/i386}}


Ligne 121 : Ligne 121 :
{{Spacewalk/repo|name=centos5-updates-x86_64|url=http://mirror.centos.org/centos/5/updates/x86_64/}}
{{Spacewalk/repo|name=centos5-updates-x86_64|url=http://mirror.centos.org/centos/5/updates/x86_64/}}
{{Spacewalk/repo|name=centos5-rpmforge-x86_64|url=http://apt.sw.be/redhat/el5/en/x86_64/rpmforge/}}
{{Spacewalk/repo|name=centos5-rpmforge-x86_64|url=http://apt.sw.be/redhat/el5/en/x86_64/rpmforge/}}
{{Spacewalk/repo|name=centos5-epel-x86_64|url=http://mirrors.fedoraproject.org/mirrorlist?repo=epel-5&arch=x86_64
{{Spacewalk/repo|name=centos5-epel-x86_64|url=http://mirrors.fedoraproject.org/mirrorlist?repo=epel-5&arch=x86_64}}
{{Spacewalk/repo|name=centos5-b2pweb-x86_64|url=http://koji.b2pweb.com/repos/centos/5/os/RPMS/x86_64}}
{{Spacewalk/repo|name=centos5-b2pweb-x86_64|url=http://koji.b2pweb.com/repos/centos/5/os/RPMS/x86_64}}


Ligne 127 : Ligne 127 :
{{Spacewalk/repo|name=centos6-base-i386|url=http://mirror.centos.org/centos/6/os/i386/}}
{{Spacewalk/repo|name=centos6-base-i386|url=http://mirror.centos.org/centos/6/os/i386/}}
{{Spacewalk/repo|name=centos6-updates-i386|url=http://mirror.centos.org/centos/6/updates/i386/}}
{{Spacewalk/repo|name=centos6-updates-i386|url=http://mirror.centos.org/centos/6/updates/i386/}}
{{Spacewalk/repo|name=centos6-epel-i386|url=http://mirrors.fedoraproject.org/mirrorlist?repo=epel-6&arch=i386
{{Spacewalk/repo|name=centos6-epel-i386|url=http://mirrors.fedoraproject.org/mirrorlist?repo=epel-6&arch=i386}}
{{Spacewalk/repo|name=centos6-b2pweb-i386|url=http://koji.b2pweb.com/repos/centos/6/os/RPMS/i386}}
{{Spacewalk/repo|name=centos6-b2pweb-i386|url=http://koji.b2pweb.com/repos/centos/6/os/RPMS/i386}}


Ligne 133 : Ligne 133 :
{{Spacewalk/repo|name=centos6-base-x86_64|url=http://mirror.centos.org/centos/6/os/x86_64/}}
{{Spacewalk/repo|name=centos6-base-x86_64|url=http://mirror.centos.org/centos/6/os/x86_64/}}
{{Spacewalk/repo|name=centos6-updates-x86_64|url=http://mirror.centos.org/centos/6/updates/x86_64/}}
{{Spacewalk/repo|name=centos6-updates-x86_64|url=http://mirror.centos.org/centos/6/updates/x86_64/}}
{{Spacewalk/repo|name=centos6-epel-x86_64|url=http://mirrors.fedoraproject.org/mirrorlist?repo=epel-6&arch=x86_64
{{Spacewalk/repo|name=centos6-epel-x86_64|url=http://mirrors.fedoraproject.org/mirrorlist?repo=epel-6&arch=x86_64}}
{{Spacewalk/repo|name=centos6-b2pweb-x86_64|url=http://koji.b2pweb.com/repos/centos/6/os/RPMS/x86_64}}
{{Spacewalk/repo|name=centos6-b2pweb-x86_64|url=http://koji.b2pweb.com/repos/centos/6/os/RPMS/x86_64}}



Version du 16 août 2013 à 14:05

LogoSpacewalk.svg

Importer des paquets dans Spacewalk

Introduction

Pour utiliser Spacewalk, il faut d'abord lui importer des paquets RPM. Il y a deux façons de faire:

  1. spacewalk-repo-sync: pour importer/synchroniser tout un dépôt
  2. rhnpush: pour ajouter directement des paquets

Mais avant tout, Spacewalk a besoin d'avoir des définitions de channels

Créer des Channels

Création via Interface Web

La façon la plus simple est de le faire à partir de l'interface web. On s'identifie et depuis le menu

"Channels"->"Manage Software Channels"-> "Create"

SpaceWalkChannelAdd.png

On va créer les channels de base, ainsi que les channels enfants (dépôts additionnels) pour:

  • CentOS 5 32 bits
  • CentOS 5 64 bits
  • CentOS 6 32 bits
  • CentOS 6 64 bits

SpacewalkAllChannels.png

Channels pour CentOS 5 32 bits

IconChannel16.pngCanal

Basic Channel Details

  • Channel Name: CentOS 5 Base - i386
  • Channel Label: centos5-base-i386
  • Parent Channel: (none)
  • Yum Repository Checksum Type: sha1
  • Architecture: IA-32
  • Summary: CentOS 5 Base for i386 architecture

Security: GPG


IconChannel16.pngCanal

Basic Channel Details

  • Channel Name: CentOS 5 Updates - i386
  • Channel Label: centos5-updates-i386
  • Parent Channel: CentOS 5 Base - i386
  • Yum Repository Checksum Type: sha1
  • Architecture: IA-32
  • Summary: CentOS 5 Updates for i386 architecture

Security: GPG


IconChannel16.pngCanal

Basic Channel Details

  • Channel Name: CentOS 5 Rpmforge - i386
  • Channel Label: centos5-rpmforge-i386
  • Parent Channel: CentOS 5 Base - i386
  • Yum Repository Checksum Type: sha1
  • Architecture: IA-32
  • Summary: CentOS 5 Rpmforge for i386 architecture

Security: GPG


IconChannel16.pngCanal

Basic Channel Details

  • Channel Name: CentOS 5 EPEL - i386
  • Channel Label: centos5-epel-i386
  • Parent Channel: CentOS 5 Base - i386
  • Yum Repository Checksum Type: sha1
  • Architecture: IA-32
  • Summary: CentOS 5 EPEL for i386 architecture

Security: GPG


IconChannel16.pngCanal

Basic Channel Details

  • Channel Name: CentOS 5 B2PWeb - i386
  • Channel Label: centos5-b2pweb-i386
  • Parent Channel: CentOS 5 Base - i386
  • Yum Repository Checksum Type: sha1
  • Architecture: IA-32
  • Summary: CentOS 5 B2PWeb for i386 architecture

Security: GPG (none)

Channels pour CentOS 5 64 bits

IconChannel16.pngCanal

Basic Channel Details

  • Channel Name: CentOS 5 Base - x86_64
  • Channel Label: centos5-base-x86_64
  • Parent Channel: (none)
  • Yum Repository Checksum Type: sha1
  • Architecture: x86_64
  • Summary: CentOS 5 Base for x86_64 architecture

Security: GPG


IconChannel16.pngCanal

Basic Channel Details

  • Channel Name: CentOS 5 Updates - x86_64
  • Channel Label: centos5-updates-x86_64
  • Parent Channel: CentOS 5 Base - x86_64
  • Yum Repository Checksum Type: sha1
  • Architecture: x86_64
  • Summary: CentOS 5 Updates for x86_64 architecture

Security: GPG


IconChannel16.pngCanal

Basic Channel Details

  • Channel Name: CentOS 5 Rpmforge - x86_64
  • Channel Label: centos5-rpmforge-x86_64
  • Parent Channel: CentOS 5 Base - x86_64
  • Yum Repository Checksum Type: sha1
  • Architecture: x86_64
  • Summary: CentOS 5 Rpmforge for x86_64 architecture

Security: GPG


IconChannel16.pngCanal

Basic Channel Details

  • Channel Name: CentOS 5 EPEL - x86_64
  • Channel Label: centos5-epel-x86_64
  • Parent Channel: CentOS 5 Base - x86_64
  • Yum Repository Checksum Type: sha1
  • Architecture: x86_64
  • Summary: CentOS 5 EPEL for x86_64 architecture

Security: GPG


IconChannel16.pngCanal

Basic Channel Details

  • Channel Name: CentOS 5 B2PWeb - x86_64
  • Channel Label: centos5-b2pweb-x86_64
  • Parent Channel: CentOS 5 Base - x86_64
  • Yum Repository Checksum Type: sha1
  • Architecture: x86_64
  • Summary: CentOS 5 B2PWeb for x86_64 architecture

Security: GPG (none)

Channels pour CentOS 6 32 bits

IconChannel16.pngCanal

Basic Channel Details

  • Channel Name: CentOS 6 Base - i386
  • Channel Label: centos6-base-i386
  • Parent Channel: None
  • Yum Repository Checksum Type: sha1
  • Architecture: IA-32
  • Summary: CentOS 6 Base for i386 architecture

Security: GPG


IconChannel16.pngCanal

Basic Channel Details

  • Channel Name: CentOS 6 Updates - i386
  • Channel Label: centos6-updates-i386
  • Parent Channel: CentOS 6 Base - i386
  • Yum Repository Checksum Type: sha1
  • Architecture: IA-32
  • Summary: CentOS 6 Updates for i386 architecture

Security: GPG


IconChannel16.pngCanal

Basic Channel Details

  • Channel Name: CentOS 6 EPEL - i386
  • Channel Label: centos6-epel-i386
  • Parent Channel: CentOS 6 Base - i386
  • Yum Repository Checksum Type: sha1
  • Architecture: IA-32
  • Summary: CentOS 6 EPEL for i386 architecture

Security: GPG


IconChannel16.pngCanal

Basic Channel Details

  • Channel Name: CentOS 6 B2PWeb - i386
  • Channel Label: centos6-b2pweb-i386
  • Parent Channel: CentOS 6 Base - i386
  • Yum Repository Checksum Type: sha1
  • Architecture: IA-32
  • Summary: CentOS 6 B2PWeb for i386 architecture

Security: GPG (none)

Channels pour CentOS 6 64 bits

IconChannel16.pngCanal

Basic Channel Details

  • Channel Name: CentOS 6 Base - x86_64
  • Channel Label: centos6-base-x86_64
  • Parent Channel: None
  • Yum Repository Checksum Type: sha1
  • Architecture: x86_64
  • Summary: CentOS 6 Base for x86_64 architecture

Security: GPG


IconChannel16.pngCanal

Basic Channel Details

  • Channel Name: CentOS 6 Updates - x86_64
  • Channel Label: centos6-updates-x86_64
  • Parent Channel: CentOS 6 Base - x86_64
  • Yum Repository Checksum Type: sha1
  • Architecture: x86_64
  • Summary: CentOS 6 Updates for x86_64 architecture

Security: GPG


IconChannel16.pngCanal

Basic Channel Details

  • Channel Name: CentOS 6 EPEL - x86_64
  • Channel Label: centos6-epel-x86_64
  • Parent Channel: CentOS 6 Base - x86_64
  • Yum Repository Checksum Type: sha1
  • Architecture: x86_64
  • Summary: CentOS 6 EPEL for x86_64 architecture

Security: GPG


IconChannel16.pngCanal

Basic Channel Details

  • Channel Name: CentOS 6 B2PWeb - x86_64
  • Channel Label: centos6-b2pweb-x86_64
  • Parent Channel: CentOS 6 Base - x86_64
  • Yum Repository Checksum Type: sha1
  • Architecture: x86_64
  • Summary: CentOS 6 B2PWeb for x86_64 architecture

Security: GPG (none)

Création via <app>spacewalk-common-channels</app>

Alternativement, on peut utiliser en ligne de commande, le script <app>spacewalk-common-channels</app> du paquet <package>spacewalk-utils</package>pour créer les channels préconfigurés. Il peut aussi créer les clés d'activation et les définitions des dépôts externes.

Par exemple pour créer les channels i386 et x86_64 pour CentOS 5, les clés d'activations et les sous-channels clients:

/usr/bin/spacewalk-common-channels -v -u admin -p pass -a i386,x86_64 -k unlimited 'centos5*' 'spacewalk-nightly-client*'

Usage:

# spacewalk-common-channels -h
Usage: spacewalk-common-channels [options] <channel1 glob> [<channel2 glob> ... ]

Options:
  -c CONFIG, --config=CONFIG
                        configuration file
  -u USER, --user=USER  username
  -p PASSWORD, --password=PASSWORD
                        password
  -s SERVER, --server=SERVER
                        your spacewalk server
  -k KEY_LIMIT, --keys=KEY_LIMIT
                        activation key usage limit - 'unlimited' or number
                        (default: options is not set and activation keys are
                        not created at all)
  -n, --dry-run         perform a trial run with no changes made
  -a ARCHS, --archs=ARCHS
                        list of architectures
  -v, --verbose         verbose
  -l, --list            print list of available channels
  -h, --help            show this help message and exit


Examples:

Create Fedora 12 channel, its child channels and activation key limited to 10 servers:
    /usr/bin/spacewalk-common-channels -u admin -p pass -k 10 'fedora12*'

Create Centos 5 with child channels only on x86_64:
    /usr/bin/spacewalk-common-channels -u admin -p pass -a x86_64 'centos5*'

Create only Centos 4 base channels for intel archs:
    /usr/bin/spacewalk-common-channels -u admin -p pass -a i386,x86_64 'centos4'

Create Spacewalk client child channel for every (suitable) defined base channel:
    /usr/bin/spacewalk-common-channels -u admin -p pass 'spacewalk-client*'

Create everything as well as unlimited activation key for every channel:
    /usr/bin/spacewalk-common-channels -u admin -p pass -k unlimited '*'

Repo-sync

Déclaration des dépôts

On va maintenant déclarer nos dépôts (repositories)

Goto Channels -> Manage Software Channels -> Manage Repositories -> create new repository

SpaceWalkRepoAdd.png

Repository pour CentOS 5 32 bits

IconRepo16.pngDépôt


IconRepo16.pngDépôt


IconRepo16.pngDépôt


IconRepo16.pngDépôt


IconRepo16.pngDépôt

Repository pour CentOS 5 64 bits

IconRepo16.pngDépôt


IconRepo16.pngDépôt


IconRepo16.pngDépôt


IconRepo16.pngDépôt


IconRepo16.pngDépôt

Repository pour CentOS 6 32 bits

IconRepo16.pngDépôt


IconRepo16.pngDépôt


IconRepo16.pngDépôt


IconRepo16.pngDépôt

Repository pour CentOS 6 64 bits

IconRepo16.pngDépôt


IconRepo16.pngDépôt


IconRepo16.pngDépôt


IconRepo16.pngDépôt

Mise en place de la liaison channel/dépôt

Après avoir créer les dépôts, nous devons les lier à un channel.

Goto: Channels -> Manage Software Channels -> Choose the channel to be linked -> Repositories -> Select the repositories to be linked to the channel -> Update Repositories.

SpaceWalkRepoSync.png

Note.png
Channels créés avec <app>spacewalk-common-channels</app>
Si le script <app>spacewalk-common-channels</app> a été utilisé, les dépôts sont déjà lier au channel correspondant.

Maintenant on peut synchroniser les dépôts via l'interface web ou en ligne de commande.

spacewalk-repo-sync --channel CHANNEL_LABEL 

N'importe quelle adresse de dépôt supporté par <app>yum</app> peut être utilisé (http://, file://, etc...). En ligne de commande, il faut être le super-utilisateur root pour synchroniser.

Voir la page <app>man</app> pour plus d'information

man 8 spacewalk-repo-sync


Idea.png
Erreur "yum.Errors.NoMoreMirrorsRepoError"
Si l'erreur "yum.Errors.NoMoreMirrorsRepoError" apparait durant une synchronisation, il faut installer le paquet <package>python-hashlib</package>.

Les logs se trouvent dans <path>/var/log/rhn/reposync/</path>

rhnpush

If the packages you are wanting to push to the Spacewalk server are not in a yum repository, you can push them directly using the rhnpush tool.

For example, to upload a directory of packages called 'dir_of_packges' to the channel 'my-custom-channel':

rhnpush -v --channel=my-custom-channel --server=http://localhost/APP --dir=dir_of_packages

Note: Make sure <path>/var/satellite</path> exists on the Spacewalk server and has owner:group apache before pushing. The -v option causes progress information to be printed, e.g.:

# rhnpush -v --channel=rhel-x86_64-server-5 --server=http://localhost/APP --dir=update
Connecting to http://localhost/APP
Package /root/update/xorg-x11-drv-vga-4.1.0-2.1.x86_64.rpm Not Found on RHN Server -- Uploading
Uploading package /root/update/xorg-x11-drv-vga-4.1.0-2.1.x86_64.rpm
Using POST request
Package /root/update/gnome-python2-gconf-2.16.0-1.fc6.x86_64.rpm Not Found on RHN Server -- Uploading
Uploading package /root/update/gnome-python2-gconf-2.16.0-1.fc6.x86_64.rpm
Using POST request

Note: I found that the above failed on Fedora 9 Everything. My work around was

find . -name "*rpm" | xargs rhnpush --channel=fedora-9-i386 --server=http://localhost/APP -v --tolerant -u spacewalk -p spacewalk

Note: The directory you pass as --dir=suchandsuch HAS TO contain the RPMs. rhnpush won't descend into directories to find RPMs.

     Also, I had to put the -v at the end of the group of parameters.
       --onekopaka

Note: If you are running rhnpush from a box that is NOT your spacewalk server, use the correct hostname in the --server param

Channel-to-update

If you are using CenOS or RHEL content, and wish to create channels according to an update level. You may be interested in this script here.

Regularly syncing yum repositories

This script will get the yum repo information out of the database and trigger spacewalk-repo-sync for every channel that has a yum repository. You can run it from cron to sync your repositories on a regular basis.