ProHoster > Π‘Π»ΠΎΠ³ > Administrasi > Nginstal lan ngonfigurasi Nexus Sonatype nggunakake infrastruktur minangka pendekatan kode

Nginstal lan ngonfigurasi Nexus Sonatype nggunakake infrastruktur minangka pendekatan kode

Sonatype Nexus minangka platform terpadu ing ngendi pangembang bisa nggawe proxy, nyimpen lan ngatur dependensi Java (Maven), Docker, Python, Ruby, NPM, gambar Bower, paket RPM, gitlfs, Apt, Go, Nuget, lan nyebarake keamanan piranti lunak.

Napa sampeyan butuh Sonatype Nexus?

  • Kanggo nyimpen artefak pribadi;
  • Kanggo artefak cache sing diundhuh saka Internet;

Artefak sing didhukung ing paket Sonatype Nexus dhasar:

  • Jawa, Maven (jar)
  • docker
  • Python (pip)
  • Ruby (permata)
  • NPM
  • Bower
  • Yum (rpm)
  • gitlfs
  • Mentah
  • Apt (deb)
  • Go
  • Nuget

Artefak sing Didhukung Komunitas:

  • pengarang
  • Conan
  • CPAN
  • ELPA
  • Helm
  • P2
  • R

Nginstal Sonatype Nexus nggunakake https://github.com/ansible-ThoTeam/nexus3-oss

syarat

  • Waca babagan nggunakake ansible ing Internet.
  • Instal ansible pip install ansible ing workstation ngendi playbook mlaku.
  • Instal geerlingguy.java ing workstation ngendi playbook mlaku.
  • Instal geerlingguy.apache ing workstation ngendi playbook mlaku.
  • Peran iki wis diuji ing CentOS 7, Ubuntu Xenial (16.04) lan Bionic (18.04), Debian Jessie lan Stretch
  • jmespath Pustaka kudu diinstal ing workstation ngendi playbook mlaku. Kanggo nginstal: sudo pip install -r requirements.txt
  • Simpen file playbook (conto ing ngisor iki) menyang file nexus.yml
  • Jalanake instalasi nexus ansible-playbook -i host nexus.yml

Conto ansible-playbook kanggo nginstal nexus tanpa LDAP karo Maven (java), Docker, Python, Ruby, NPM, Bower, RPM lan repositori gitlfs.

---
- name: Nexus
  hosts: nexus
  become: yes

  vars:
    nexus_timezone: 'Asia/Omsk'
    nexus_admin_password: "admin123"
    nexus_public_hostname: 'apatsev-nexus-playbook'
    httpd_setup_enable: false
    nexus_privileges:
      - name: all-repos-read
        description: 'Read & Browse access to all repos'
        repository: '*'
        actions:
          - read
          - browse
      - name: company-project-deploy
        description: 'Deployments to company-project'
        repository: company-project
        actions:
          - add
          - edit
    nexus_roles:
      - id: Developpers # maps to the LDAP group
        name: developers
        description: All developers
        privileges:
          - nx-search-read
          - all-repos-read
          - company-project-deploy
        roles: []
    nexus_local_users:
      - username: jenkins # used as key to update
        first_name: Jenkins
        last_name: CI
        email: [email protected]
        password: "s3cr3t"
        roles:
          - Developpers # role ID here
    nexus_blobstores:
      - name: company-artifacts
        path: /var/nexus/blobs/company-artifacts
    nexus_scheduled_tasks:
      - name: compact-blobstore
        cron: '0 0 22 * * ?'
        typeId: blobstore.compact
        taskProperties:
          blobstoreName: 'company-artifacts'

    nexus_repos_maven_proxy:
      - name: central
        remote_url: 'https://repo1.maven.org/maven2/'
        layout_policy: permissive
      - name: jboss
        remote_url: 'https://repository.jboss.org/nexus/content/groups/public-jboss/'
      - name: vaadin-addons
        remote_url: 'https://maven.vaadin.com/vaadin-addons/'
      - name: jaspersoft
        remote_url: 'https://jaspersoft.artifactoryonline.com/jaspersoft/jaspersoft-repo/'
        version_policy: mixed
    nexus_repos_maven_hosted:
      - name: company-project
        version_policy: mixed
        write_policy: allow
        blob_store: company-artifacts
    nexus_repos_maven_group:
      - name: public
        member_repos:
          - central
          - jboss
          - vaadin-addons
          - jaspersoft

    # Yum. Change nexus_config_yum to true for create yum repository
    nexus_config_yum: true
    nexus_repos_yum_hosted:
      - name: private_yum_centos_7
        repodata_depth: 1
    nexus_repos_yum_proxy:
      - name: epel_centos_7_x86_64
        remote_url: http://download.fedoraproject.org/pub/epel/7/x86_64
        maximum_component_age: -1
        maximum_metadata_age: -1
        negative_cache_ttl: 60
      - name: centos-7-os-x86_64
        remote_url: http://mirror.centos.org/centos/7/os/x86_64/
        maximum_component_age: -1
        maximum_metadata_age: -1
        negative_cache_ttl: 60
    nexus_repos_yum_group:
      - name: yum_all
        member_repos:
          - private_yum_centos_7
          - epel_centos_7_x86_64

    # NPM. Change nexus_config_npm to true for create npm repository
    nexus_config_npm: true
    nexus_repos_npm_hosted: []
    nexus_repos_npm_group:
      - name: npm-public
        member_repos:
          - npm-registry
    nexus_repos_npm_proxy:
      - name: npm-registry
        remote_url: https://registry.npmjs.org/
        negative_cache_enabled: false

    # Docker. Change nexus_config_docker to true for create docker repository
    nexus_config_docker: true
    nexus_repos_docker_hosted:
      - name: docker-hosted
        http_port: "{{ nexus_docker_hosted_port }}"
        v1_enabled: True
    nexus_repos_docker_proxy:
      - name: docker-proxy
        http_port: "{{ nexus_docker_proxy_port }}"
        v1_enabled: True
        index_type: "HUB"
        remote_url: "https://registry-1.docker.io"
        use_nexus_certificates_to_access_index: false
        maximum_component_age: 1440
        maximum_metadata_age: 1440
        negative_cache_enabled: true
        negative_cache_ttl: 1440
    nexus_repos_docker_group:
      - name: docker-group
        http_port: "{{ nexus_docker_group_port }}"
        v1_enabled: True
        member_repos:
          - docker-hosted
          - docker-proxy

    # Bower. Change nexus_config_bower to true for create bower repository
    nexus_config_bower: true
    nexus_repos_bower_hosted:
      - name: bower-hosted
    nexus_repos_bower_proxy:
      - name: bower-proxy
        index_type: "proxy"
        remote_url: "https://registry.bower.io"
        use_nexus_certificates_to_access_index: false
        maximum_component_age: 1440
        maximum_metadata_age: 1440
        negative_cache_enabled: true
        negative_cache_ttl: 1440
    nexus_repos_bower_group:
      - name: bower-group
        member_repos:
          - bower-hosted
          - bower-proxy

    # Pypi. Change nexus_config_pypi to true for create pypi repository
    nexus_config_pypi: true
    nexus_repos_pypi_hosted:
      - name: pypi-hosted
    nexus_repos_pypi_proxy:
      - name: pypi-proxy
        index_type: "proxy"
        remote_url: "https://pypi.org/"
        use_nexus_certificates_to_access_index: false
        maximum_component_age: 1440
        maximum_metadata_age: 1440
        negative_cache_enabled: true
        negative_cache_ttl: 1440
    nexus_repos_pypi_group:
      - name: pypi-group
        member_repos:
          - pypi-hosted
          - pypi-proxy

    # rubygems. Change nexus_config_rubygems to true for create rubygems repository
    nexus_config_rubygems: true
    nexus_repos_rubygems_hosted:
      - name: rubygems-hosted
    nexus_repos_rubygems_proxy:
      - name: rubygems-proxy
        index_type: "proxy"
        remote_url: "https://rubygems.org"
        use_nexus_certificates_to_access_index: false
        maximum_component_age: 1440
        maximum_metadata_age: 1440
        negative_cache_enabled: true
        negative_cache_ttl: 1440
    nexus_repos_rubygems_group:
      - name: rubygems-group
        member_repos:
          - rubygems-hosted
          - rubygems-proxy

    # gitlfs. Change nexus_config_gitlfs to true for create gitlfs repository
    nexus_config_gitlfs: true
    nexus_repos_gitlfs_hosted:
      - name: gitlfs-hosted

  roles:
    - { role: geerlingguy.java }
    # Debian/Ubuntu only
    # - { role: geerlingguy.apache, apache_create_vhosts: no, apache_mods_enabled: ["proxy_http.load", "headers.load"], apache_remove_default_vhost: true, tags: ["geerlingguy.apache"] }
    # RedHat/CentOS only
    - { role: geerlingguy.apache, apache_create_vhosts: no, apache_remove_default_vhost: true, tags: ["geerlingguy.apache"] }
    - { role: ansible-thoteam.nexus3-oss, tags: ['ansible-thoteam.nexus3-oss'] }

Screenshot:

Nginstal lan ngonfigurasi Nexus Sonatype nggunakake infrastruktur minangka pendekatan kode

Nginstal lan ngonfigurasi Nexus Sonatype nggunakake infrastruktur minangka pendekatan kode

Peran variabel

Variabel Peran

Variabel kanthi nilai standar (ndeleng default/main.yml):

Variabel umum

    nexus_version: ''
    nexus_timezone: 'UTC'

Kanthi gawan, peran kasebut bakal nginstal versi Nexus paling anyar sing kasedhiya. Sampeyan bisa ndandani versi kanthi ngganti variabel nexus_version. Waca versi kasedhiya ing https://www.sonatype.com/download-oss-sonatype.

Yen sampeyan ngganti menyang versi anyar, peran bakal nyoba nganyari instalasi Nexus.

Yen sampeyan nggunakake versi Nexus lawas tinimbang sing paling anyar, sampeyan kudu mesthekake yen sampeyan ora nggunakake fitur sing ora kasedhiya ing rilis sing diinstal (contone, hosting repositori yum kasedhiya kanggo nexus luwih saka 3.8.0, git lfs repo. kanggo nexus luwih saka 3.3.0 etc.)

nexus timezone yaiku jeneng zona wektu Jawa, sing bisa migunani ing kombinasi karo ekspresi cron ing ngisor iki kanggo tugas nexus_scheduled.

Port Nexus lan path konteks

    nexus_default_port: 8081
    nexus_default_context_path: '/'

Port lan path konteks proses sambungan Jawa. nexus_default_context_path kudu ngemot garis miring maju nalika disetel, contone: nexus_default_context_path: '/nexus/'.

Pangguna lan Grup Nexus OS

    nexus_os_group: 'nexus'
    nexus_os_user: 'nexus'

Pangguna lan grup sing digunakake kanggo duwe file Nexus lan mbukak layanan bakal digawe dening peran yen ana sing ilang.

    nexus_os_user_home_dir: '/home/nexus'

Ngidini ngganti direktori ngarep standar kanggo pangguna nexus

Direktori conto Nexus

    nexus_installation_dir: '/opt'
    nexus_data_dir: '/var/nexus'
    nexus_tmp_dir: "{{ (ansible_os_family == 'RedHat') | ternary('/var/nexus-tmp', '/tmp/nexus') }}"

Katalog Nexus.

  • nexus_installation_dir ngemot file eksekusi sing diinstal
  • nexus_data_dir ngemot kabeh konfigurasi, repositori lan artefak sing diundhuh. Jalur blobstore khusus nexus_data_dir bisa selaras, ndeleng ngisor nexus_blobstores.
  • nexus_tmp_dir ngemot kabeh file sauntara. Path standar kanggo redhat wis dipindhah saka /tmp kanggo ngatasi masalah potensial karo prosedur reresik otomatis. Waca #168.

Konfigurasi Panggunaan Memori Nexus JVM

    nexus_min_heap_size: "1200M"
    nexus_max_heap_size: "{{ nexus_min_heap_size }}"
    nexus_max_direct_memory: "2G"

Iki minangka setelan gawan kanggo Nexus. Aja ngganti nilai kasebut Yen sampeyan durung maca bagean memori syarat sistem nexus lan ora ngerti apa sing ditindakake.

Minangka bebaya kapindho, iki minangka kutipan saka dokumen ing ndhuwur:

Ora dianjurake kanggo nambah memori tumpukan JVM ngluwihi nilai sing disaranake kanggo nambah kinerja. Iki bisa uga duwe efek ngelawan, nyebabake karya sing ora perlu kanggo sistem operasi.

Sandi administrator

    nexus_admin_password: 'changeme'

Sandi akun "admin" kanggo persiyapan. Iki mung bisa digunakake ing instalasi standar pisanan. Mangga deleng [Ganti sandi admin sawise instalasi pisanan](# change-admin-password-after-first-install) yen sampeyan pengin ngganti mengko nggunakake peran.

Disaranake supaya ora nyimpen tembung sandhi ing teks sing cetha ing playbook, nanging nggunakake [enkripsi ansible-vault] (https://docs.ansible.com/ansible/latest/user_guide/vault.html) (salah siji inline utawa ing file kapisah dimuat karo contone include_vars)

Akses anonim minangka standar

    nexus_anonymous_access: false

Akses anonim dipateni kanthi gawan. Waca liyane babagan akses anonim.

Jeneng host umum

    nexus_public_hostname: 'nexus.vm'
    nexus_public_scheme: https

Jeneng domain lan skema lengkap (https utawa http) ing ngendi conto Nexus bakal kasedhiya kanggo para klien.

akses API kanggo peran iki

    nexus_api_hostname: localhost
    nexus_api_scheme: http
    nexus_api_validate_certs: "{{ nexus_api_scheme == 'https' }}"
    nexus_api_context_path: "{{ nexus_default_context_path }}"
    nexus_api_port: "{{ nexus_default_port }}"

Variabel iki ngontrol carane peran nyambungake menyang Nexus API kanggo provisioning.
Kanggo pangguna sing luwih maju. Sampeyan mbokmenawa ora pengin ngganti setelan gawan iki

Nggawe proxy mbalikke

    httpd_setup_enable: false
    httpd_server_name: "{{ nexus_public_hostname }}"
    httpd_default_admin_email: "[email protected]"
    httpd_ssl_certificate_file: 'files/nexus.vm.crt'
    httpd_ssl_certificate_key_file: 'files/nexus.vm.key'
    # httpd_ssl_certificate_chain_file: "{{ httpd_ssl_certificate_file }}"
    httpd_copy_ssl_files: true

Instal SSL Reverse Proxy.
Kanggo nindakake iki, sampeyan kudu nginstal httpd. Cathetan: nalika kanggo httpd_setup_enable nyetel nilaitrue, kontak nexus 127.0.0.1:8081, mangkono ora bisa diakses langsung liwat port HTTP 8081 saka alamat IP eksternal.

Jeneng host standar sing digunakake yaiku nexus_public_hostname. Yen sampeyan butuh jeneng sing beda-beda kanggo sawetara alasan, sampeyan bisa nyetel httpd_server_name kanthi makna sing beda.

Π‘ httpd_copy_ssl_files: true (kanthi standar) sertifikat ing ndhuwur kudu ana ing direktori playbook lan bakal disalin menyang server lan dikonfigurasi ing apache.

Yen sampeyan pengin nggunakake sertifikat sing ana ing server, instal httpd_copy_ssl_files: false lan nyedhiyakake variabel ing ngisor iki:

    # These specifies to the vhost where to find on the remote server file
    # system the certificate files.
    httpd_ssl_cert_file_location: "/etc/pki/tls/certs/wildcard.vm.crt"
    httpd_ssl_cert_key_location: "/etc/pki/tls/private/wildcard.vm.key"
    # httpd_ssl_cert_chain_file_location: "{{ httpd_ssl_cert_file_location }}"

httpd_ssl_cert_chain_file_location opsional lan kudu ora disetel yen sampeyan ora pengin ngatur file chain

    httpd_default_admin_email: "[email protected]"

Setel alamat email admin standar

Konfigurasi LDAP

Sambungan LDAP lan wilayah keamanan dipateni kanthi gawan

    nexus_ldap_realm: false
    ldap_connections: []

sambungan LDAP, saben unsur katon kaya iki:

    nexus_ldap_realm: true
    ldap_connections:
      - ldap_name: 'My Company LDAP' # used as a key to update the ldap config
        ldap_protocol: 'ldaps' # ldap or ldaps
        ldap_hostname: 'ldap.mycompany.com'
        ldap_port: 636
        ldap_use_trust_store: false # Wether or not to use certs in the nexus trust store
        ldap_search_base: 'dc=mycompany,dc=net'
        ldap_auth: 'none' # or simple
        ldap_auth_username: 'username' # if auth = simple
        ldap_auth_password: 'password' # if auth = simple
        ldap_user_base_dn: 'ou=users'
        ldap_user_filter: '(cn=*)' # (optional)
        ldap_user_object_class: 'inetOrgPerson'
        ldap_user_id_attribute: 'uid'
        ldap_user_real_name_attribute: 'cn'
        ldap_user_email_attribute: 'mail'
        ldap_user_subtree: false
        ldap_map_groups_as_roles: false
        ldap_group_base_dn: 'ou=groups'
        ldap_group_object_class: 'posixGroup'
        ldap_group_id_attribute: 'cn'
        ldap_group_member_attribute: 'memberUid'
        ldap_group_member_format: '${username}'
        ldap_group_subtree: false

Conto konfigurasi LDAP kanggo otentikasi anonim (ikatan anonim), iki uga minangka konfigurasi "minimal":

    nexus_ldap_realm: true
    ldap_connection:
      - ldap_name: 'Simplest LDAP config'
        ldap_protocol: 'ldaps'
        ldap_hostname: 'annuaire.mycompany.com'
        ldap_search_base: 'dc=mycompany,dc=net'
        ldap_port: 636
        ldap_use_trust_store: false
        ldap_user_id_attribute: 'uid'
        ldap_user_real_name_attribute: 'cn'
        ldap_user_email_attribute: 'mail'
        ldap_user_object_class: 'inetOrgPerson'

Conto konfigurasi LDAP kanggo otentikasi prasaja (nggunakake akun DSA):

    nexus_ldap_realm: true
    ldap_connections:
      - ldap_name: 'LDAP config with DSA'
        ldap_protocol: 'ldaps'
        ldap_hostname: 'annuaire.mycompany.com'
        ldap_port: 636
        ldap_use_trust_store: false
        ldap_auth: 'simple'
        ldap_auth_username: 'cn=mynexus,ou=dsa,dc=mycompany,dc=net'
        ldap_auth_password: "{{ vault_ldap_dsa_password }}" # better keep passwords in an ansible vault
        ldap_search_base: 'dc=mycompany,dc=net'
        ldap_user_base_dn: 'ou=users'
        ldap_user_object_class: 'inetOrgPerson'
        ldap_user_id_attribute: 'uid'
        ldap_user_real_name_attribute: 'cn'
        ldap_user_email_attribute: 'mail'
        ldap_user_subtree: false

Conto konfigurasi LDAP kanggo otentikasi prasaja (nggunakake akun DSA) + grup sing dipetakan minangka peran:

    nexus_ldap_realm: true
    ldap_connections
      - ldap_name: 'LDAP config with DSA'
        ldap_protocol: 'ldaps'
        ldap_hostname: 'annuaire.mycompany.com'
        ldap_port: 636
        ldap_use_trust_store: false
        ldap_auth: 'simple'
        ldap_auth_username: 'cn=mynexus,ou=dsa,dc=mycompany,dc=net'
        ldap_auth_password: "{{ vault_ldap_dsa_password }}" # better keep passwords in an ansible vault
        ldap_search_base: 'dc=mycompany,dc=net'
        ldap_user_base_dn: 'ou=users'
        ldap_user_object_class: 'inetOrgPerson'
        ldap_user_id_attribute: 'uid'
        ldap_user_real_name_attribute: 'cn'
        ldap_user_email_attribute: 'mail'
        ldap_map_groups_as_roles: true
        ldap_group_base_dn: 'ou=groups'
        ldap_group_object_class: 'groupOfNames'
        ldap_group_id_attribute: 'cn'
        ldap_group_member_attribute: 'member'
        ldap_group_member_format: 'uid=${username},ou=users,dc=mycompany,dc=net'
        ldap_group_subtree: false

Conto konfigurasi LDAP kanggo otentikasi prasaja (nggunakake akun DSA) + grup kanthi dinamis dipetakan minangka peran:

    nexus_ldap_realm: true
    ldap_connections:
      - ldap_name: 'LDAP config with DSA'
        ldap_protocol: 'ldaps'
        ldap_hostname: 'annuaire.mycompany.com'
        ldap_port: 636
        ldap_use_trust_store: false
        ldap_auth: 'simple'
        ldap_auth_username: 'cn=mynexus,ou=dsa,dc=mycompany,dc=net'
        ldap_auth_password: "{{ vault_ldap_dsa_password }}" # better keep passwords in an ansible vault
        ldap_search_base: 'dc=mycompany,dc=net'
        ldap_user_base_dn: 'ou=users'
        ldap_user_object_class: 'inetOrgPerson'
        ldap_user_id_attribute: 'uid'
        ldap_user_real_name_attribute: 'cn'
        ldap_user_email_attribute: 'mail'
        ldap_map_groups_as_roles: true
        ldap_map_groups_as_roles_type: 'dynamic'
        ldap_user_memberof_attribute: 'memberOf'

Privilege

    nexus_privileges:
      - name: all-repos-read # used as key to update a privilege
        # type: <one of application, repository-admin, repository-content-selector, repository-view, script or wildcard>
        description: 'Read & Browse access to all repos'
        repository: '*'
        actions: # can be add, browse, create, delete, edit, read or  * (all)
          - read
          - browse
        # pattern: pattern
        # domain: domain
        # script_name: name

Dhaftar hak istimewa kanggo setelan. Deleng dokumentasi lan GUI kanggo mriksa variabel sing kudu disetel gumantung saka jinis hak istimewa.

Unsur kasebut digabungake karo nilai standar ing ngisor iki:

    _nexus_privilege_defaults:
      type: repository-view
      format: maven2
      actions:
        - read

Peran (ing Nexus tegese)

    nexus_roles:
      - id: Developpers # can map to a LDAP group id, also used as a key to update a role
        name: developers
        description: All developers
        privileges:
          - nx-search-read
          - all-repos-read
        roles: [] # references to other role names

Dhaftar peran kanggo setelan.

Pangguna

    nexus_local_users: []
      # - username: jenkins # used as key to update
      #   state: present # default value if ommited, use 'absent' to remove user
      #   first_name: Jenkins
      #   last_name: CI
      #   email: [email protected]
      #   password: "s3cr3t"
      #   roles:
      #     - developers # role ID

Dhaptar pangguna / akun lokal (non-LDAP) kanggo nggawe ing nexus.

Dhaptar pangguna/akun lokal (non-LDAP) sing arep digawe ing Nexus. 

      nexus_ldap_users: []
      # - username: j.doe
      #   state: present
      #   roles:
      #     - "nx-admin"

Ldap pemetaan pangguna / peran. negara absent bakal mbusak peran saka pangguna sing wis ana yen wis ana.
Pangguna Ldap ora dibusak. Nyoba nyetel peran kanggo pangguna sing ora ana bakal nyebabake kesalahan.

Pamilih konten

  nexus_content_selectors:
  - name: docker-login
    description: Selector for docker login privilege
    search_expression: format=="docker" and path=~"/v2/"

Kanggo informasi luwih lengkap babagan pamilih isi, waca Dokumentasi.

Kanggo nggunakake pamilih isi, nambah hak istimewa anyar karo type: repository-content-selector lan relevancontentSelector

- name: docker-login-privilege
  type: repository-content-selector
  contentSelector: docker-login
  description: 'Login to Docker registry'
  repository: '*'
  actions:
  - read
  - browse

Blobstores lan repositori

    nexus_delete_default_repos: false

Mbusak repositori saka nexus nginstal konfigurasi standar awal. Langkah iki mung dieksekusi nalika nginstal pisanan (nalika nexus_data_dir wis dideteksi kosong).

Mbusak repositori saka konfigurasi gawan standar kanggo Nexus. Langkah iki mung ditindakake nalika instalasi pisanan (nalika nexus_data_dir kosong).

    nexus_delete_default_blobstore: false

Mbusak blobstore gawan saka nexus nginstal konfigurasi gawan dhisikan. Iki bisa rampung mung yen nexus_delete_default_repos: true lan kabeh repositori sing dikonfigurasi (ndeleng ngisor) duwe eksplisit blob_store: custom. Langkah iki mung dieksekusi nalika nginstal pisanan (nalika nexus_data_dir wis dideteksi kosong).

Mbusak panyimpenan blob (artefak binar) dipateni kanthi gawan saka konfigurasi awal. Kanggo mbusak panyimpenan blob (artefak binar), mateni nexus_delete_default_repos: true. Langkah iki mung ditindakake nalika instalasi pisanan (nalika nexus_data_dir kosong).

    nexus_blobstores: []
    # example blobstore item :
    # - name: separate-storage
    #   type: file
    #   path: /mnt/custom/path
    # - name: s3-blobstore
    #   type: S3
    #   config:
    #     bucket: s3-blobstore
    #     accessKeyId: "{{ VAULT_ENCRYPTED_KEY_ID }}"
    #     secretAccessKey: "{{ VAULT_ENCRYPTED_ACCESS_KEY }}"

Blobstores kanggo nggawe. A path blobstore lan blobstore repositori ora bisa dianyari sawise nggawe dhisikan (update sembarang kene bakal digatèkaké ing re-provisionning).

Konfigurasi blobstore ing S3 kasedhiya minangka penak lan ora bagean saka tes otomatis kita mbukak ing travis. Wigati dimangerteni manawa nyimpen ing S3 mung dianjurake kanggo kedadeyan sing dipasang ing AWS.

cipta Blobstores. Jalur panyimpenan lan repositori panyimpenan ora bisa dianyari sawise nggawe wiwitan (nganyari apa wae ing kene bakal diabaikan nalika diinstal maneh).

Nyiyapake panyimpenan blob ing S3 kasedhiya minangka penak. Wigati dimangerteni manawa panyimpenan S3 mung dianjurake kanggo kedadeyan sing dipasang ing AWS.

    nexus_repos_maven_proxy:
      - name: central
        remote_url: 'https://repo1.maven.org/maven2/'
        layout_policy: permissive
        # maximum_component_age: -1
        # maximum_metadata_age: 1440
        # negative_cache_enabled: true
        # negative_cache_ttl: 1440
      - name: jboss
        remote_url: 'https://repository.jboss.org/nexus/content/groups/public-jboss/'
        # maximum_component_age: -1
        # maximum_metadata_age: 1440
        # negative_cache_enabled: true
        # negative_cache_ttl: 1440
    # example with a login/password :
    # - name: secret-remote-repo
    #   remote_url: 'https://company.com/repo/secure/private/go/away'
    #   remote_username: 'username'
    #   remote_password: 'secret'
    #   # maximum_component_age: -1
    #   # maximum_metadata_age: 1440
    #   # negative_cache_enabled: true
    #   # negative_cache_ttl: 1440

Ndhuwur iku conto konfigurasi server proxy Maven.

    nexus_repos_maven_hosted:
      - name: private-release
        version_policy: release
        write_policy: allow_once  # one of "allow", "allow_once" or "deny"

Maven repositori sing di-host konfigurasi. Konfigurasi cache negatif iku opsional lan bakal dadi standar kanggo nilai ing ndhuwur yen diilangi.

Konfigurasi repositori sing di-host Maven. Konfigurasi cache negatif (-1) opsional lan bakal dadi standar kanggo nilai ing ndhuwur yen ora ditemtokake.

    nexus_repos_maven_group:
      - name: public
        member_repos:
          - central
          - jboss

Konfigurasi kelompok Maven.

Kabeh telung jinis repositori digabungake karo nilai standar ing ngisor iki:

    _nexus_repos_maven_defaults:
      blob_store: default # Note : cannot be updated once the repo has been created
      strict_content_validation: true
      version_policy: release # release, snapshot or mixed
      layout_policy: strict # strict or permissive
      write_policy: allow_once # one of "allow", "allow_once" or "deny"
      maximum_component_age: -1  # Nexus gui default. For proxies only
      maximum_metadata_age: 1440  # Nexus gui default. For proxies only
      negative_cache_enabled: true # Nexus gui default. For proxies only
      negative_cache_ttl: 1440 # Nexus gui default. For proxies only

Docker, Pypi, Raw, Rubygems, Bower, NPM, Git-LFS lan jinis repositori yum:
ndeleng defaults/main.yml kanggo pilihan iki:

Docker, Pypi, Raw, Rubygems, Bower, NPM, Git-LFS lan repositori yum dipateni kanthi standar:
Deleng defaults/main.yml kanggo pilihan iki:

      nexus_config_pypi: false
      nexus_config_docker: false
      nexus_config_raw: false
      nexus_config_rubygems: false
      nexus_config_bower: false
      nexus_config_npm: false
      nexus_config_gitlfs: false
      nexus_config_yum: false

Wigati dimangerteni manawa sampeyan kudu ngaktifake ruang lingkup keamanan tartamtu yen sampeyan pengin nggunakake jinis repositori liyane saka maven. Iki palsu kanthi gawan

nexus_nuget_api_key_realm: false
nexus_npm_bearer_token_realm: false
nexus_docker_bearer_token_realm: false  # required for docker anonymous access

Realm Pangguna Remote uga bisa diaktifake nggunakake

nexus_rut_auth_realm: true

lan judhul bisa disesuaikan kanthi nemtokake

nexus_rut_auth_header: "CUSTOM_HEADER"

Tugas sing dijadwalake

    nexus_scheduled_tasks: []
    #  #  Example task to compact blobstore :
    #  - name: compact-docker-blobstore
    #    cron: '0 0 22 * * ?'
    #    typeId: blobstore.compact
    #    task_alert_email: [email protected]  # optional
    #    taskProperties:
    #      blobstoreName: {{ nexus_blob_names.docker.blob }} # all task attributes are stored as strings by nexus internally
    #  #  Example task to purge maven snapshots
    #  - name: Purge-maven-snapshots
    #    cron: '0 50 23 * * ?'
    #    typeId: repository.maven.remove-snapshots
    #    task_alert_email: [email protected]  # optional
    #    taskProperties:
    #      repositoryName: "*"  # * for all repos. Change to a repository name if you only want a specific one
    #      minimumRetained: "2"
    #      snapshotRetentionDays: "2"
    #      gracePeriodInDays: "2"
    #    booleanTaskProperties:
    #      removeIfReleased: true
    #  #  Example task to purge unused docker manifest and images
    #  - name: Purge unused docker manifests and images
    #    cron: '0 55 23 * * ?'
    #    typeId: "repository.docker.gc"
    #    task_alert_email: [email protected]  # optional
    #    taskProperties:
    #      repositoryName: "*"  # * for all repos. Change to a repository name if you only want a specific one
    #  #  Example task to purge incomplete docker uploads
    #  - name: Purge incomplete docker uploads
    #    cron: '0 0 0 * * ?'
    #    typeId: "repository.docker.upload-purge"
    #    task_alert_email: [email protected]  # optional
    #    taskProperties:
    #      age: "24"

Tugas sing dijadwalake kanggo setelan. typeId lan tugas tartamtutaskProperties/booleanTaskProperties sampeyan bisa ngira:

  • saka hierarki jinis Jawa org.sonatype.nexus.scheduling.TaskDescriptorSupport
  • mriksa formulir nggawe tugas HTML ing browser Panjenengan
  • saka ndeleng panjalukan AJAX ing browser nalika nyetel tugas kanthi manual.

Properti tugas kudu diumumake ing blok yaml sing bener gumantung saka jinise:

  • taskProperties kanggo kabeh sifat string (yaiku jeneng gudang, jeneng gudang, periode wektu ...).
  • booleanTaskProperties kanggo kabeh sifat logis (yaiku kothak centhang utamane ing GUI saka tugas nggawe nexus).

Gawe serep

      nexus_backup_configure: false
      nexus_backup_cron: '0 0 21 * * ?'  # See cron expressions definition in nexus create task gui
      nexus_backup_dir: '/var/nexus-backup'
      nexus_restore_log: '{{ nexus_backup_dir }}/nexus-restore.log'
      nexus_backup_rotate: false
      nexus_backup_rotate_first: false
      nexus_backup_keep_rotations: 4  # Keep 4 backup rotation by default (current + last 3)

Gawe serep ora bakal dikonfigurasi nganti sampeyan ngalih nexus_backup_configure Π² true.
Ing kasus iki, tugas skrip sing dijadwal bakal dikonfigurasi kanggo mbukak ing Nexus
ing interval kasebut ing nexus_backup_cron (standar 21:00 saben dina).
Deleng [cithakan groovy kanggo tugas iki] (templates/backup.groovy.j2) kanggo rincian.
Tugas sing dijadwal iki ora gumantung saka wong liya nexus_scheduled_taskssing sampeyan
ngumumake ing playbook sampeyan.

Yen sampeyan pengin muter / mbusak serep, instal nexus_backup_rotate: true lan ngatur jumlah serep sing pengin disimpen nggunakake nexus_backup_keep_rotations (standar 4).

Nalika nggunakake rotasi, yen sampeyan pengin ngirit ruang disk tambahan sajrone proses serep,
Sampeyan bisa nginstal nexus_backup_rotate_first: true. Iki bakal ngatur pra-rotasi / pambusakan sadurunge gawe serep. Kanthi gawan, rotasi dumadi sawise gawe serep. Elinga yen ing kasus iki serep lawas
bakal dibusak sadurunge gawe serep saiki.

Prosedur Recovery

Run playbook karo parameter -e nexus_restore_point=<YYYY-MM-dd-HH-mm-ss>
(contone, 2017-12-17-21 kanggo 00 Desember 00 ing 17:2017

Mbusak nexus

Pènget: Iki bakal mbusak data sing saiki. Priksa manawa nggawe serep luwih awal yen perlu

Gunakake variabel nexus_purgeyen sampeyan kudu miwiti maneh saka ngeruk lan instal maneh conto nexus karo kabeh data dibusak.

ansible-playbook -i your/inventory.ini your_nexus_playbook.yml -e nexus_purge=true

Ganti sandi administrator sawise instalasi pisanan

    nexus_default_admin_password: 'admin123'

Iki ora kudu diganti ing playbook sampeyan. Variabel iki diisi karo sandhi admin Nexus standar nalika pisanan diinstal lan mesthekake yen kita bisa ngganti tembung sandhi admin nexus_admin_password.

Yen sampeyan pengin ngganti sandhi administrator sawise instalasi pisanan, sampeyan bisa ngganti sandhi kanggo sandhi lawas saka baris printah. Sawise owah-owahan nexus_admin_password ing playbook sampeyan bisa mbukak:

ansible-playbook -i your/inventory.ini your_playbook.yml -e nexus_default_admin_password=oldPassword

Saluran Telegram ing Nexus Sonatype: https://t.me/ru_nexus_sonatype

Mung pangguna pangguna sing bisa melu survey. mlebunggih.

Repositori artefak apa sing sampeyan gunakake?

  • Sonatype Nexus gratis

  • Sonatype Nexus mbayar

  • Artifactory gratis

  • Artifactory mbayar

  • pelabuhan

  • pulp

9 pangguna milih. 3 pangguna abstain.

Source: www.habr.com

Add a comment