1. 12 Mar, 2021 2 commits
  2. 11 Mar, 2021 11 commits
  3. 10 Mar, 2021 1 commit
  4. 03 Mar, 2021 3 commits
  5. 18 Feb, 2021 2 commits
  6. 11 Feb, 2021 2 commits
  7. 10 Feb, 2021 3 commits
  8. 01 Feb, 2021 1 commit
    • Guillaume Abrioux's avatar
      rgw: quick fix in create_zone_user.yml · 920f0751
      Guillaume Abrioux authored
      typical error:
      2021-02-01 03:11:09,809 p=93834 u=cephuser n=ansible | TASK [ceph-rgw : check if the realm system user already exists] ***************************************************************************************************************************************************
      2021-02-01 03:11:09,809 p=93834 u=cephuser n=ansible | Monday 01 February 2021  03:11:09 -0500 (0:00:00.084)       0:14:38.607 *******
      2021-02-01 03:11:09,836 p=93834 u=cephuser n=ansible | fatal: [ceph-kvm-ms2-1611241931591-node7-rgw]: FAILED! =>
        msg: |-
          The task includes an option with an undefined variable. The error was: 'None' has no attribute 'realm'
      This task should be skipped when `zone_users` is undefined.
      Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1922998
      Signed-off-by: default avatarGuillaume Abrioux <gabrioux@redhat.com>
  9. 29 Jan, 2021 1 commit
  10. 28 Jan, 2021 3 commits
    • Guillaume Abrioux's avatar
      rgw: avoid useless call to ceph-rgw · aeee3471
      Guillaume Abrioux authored
      since `ceph-rgw` may be called from `ceph-handler` in some contexts we
      should avoid rerunning it unnecessarily.
      Signed-off-by: default avatarGuillaume Abrioux <gabrioux@redhat.com>
      (cherry picked from commit 86170816)
    • Guillaume Abrioux's avatar
      containers: use --cpus instead --cpu-quota · b903446f
      Guillaume Abrioux authored
      When using docker 1.13.1, the current condition:
      {% if (container_binary == 'docker' and ceph_docker_version.split('.')[0] is version_compare('13', '>=')) or container_binary == 'podman' -%}
      is wrong because it compares the first digit (1) whereas it should
      compare the second one.
      It means we always use `--cpu-quota` although documentation recommend
      using `--cpus` when docker version is 1.13.1 or higher.
      From the doc:
      > --cpu-quota=<value>	Impose a CPU CFS quota on the container. The number of
      > microseconds per --cpu-period that the container is limited to before
      > throttled. As such acting as the effective ceiling.
      > If you use Docker 1.13 or higher, use --cpus instead.
      Signed-off-by: default avatarGuillaume Abrioux <gabrioux@redhat.com>
      (cherry picked from commit 3e262e07)
    • Guillaume Abrioux's avatar
      rgw: multisite refact · 14267fe0
      Guillaume Abrioux authored
      Add the possibility to deploy rgw multisite configuration with a mix of
      secondary and primary zones on a same rgw node.
      Before that, on a same node, all instances were either primary
      zones *OR* secondary.
      Now you can define a rgw instance like following:
        - instance_name: 'rgw0'
          rgw_zonemaster: false
          rgw_zonesecondary: true
          rgw_zonegroupmaster: false
          rgw_realm: 'france'
          rgw_zonegroup: 'zonegroup-france'
          rgw_zone: paris-00
          radosgw_address: "{{ _radosgw_address }}"
          radosgw_frontend_port: 8080
          rgw_zone_user: jacques.chirac
          rgw_zone_user_display_name: "Jacques Chirac"
          system_access_key: P9Eb6S8XNyo4dtZZUUMy
          system_secret_key: qqHCUtfdNnpHq3PZRHW5un9l0bEBM812Uhow0XfB
      Basically it's now possible to define `rgw_zonemaster`,
      `rgw_zonesecondary` and `rgw_zonegroupmaster` at the intsance
      level instead of the whole node level.
      Also, this commit adds an option `deploy_secondary_zones` (default True)
      which can be set to `False` in order to explicitly ask the playbook to
      not deploy secondary zones in case where the corresponding endpoint are
      not deployed yet.
      Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1915478
      Signed-off-by: default avatarGuillaume Abrioux <gabrioux@redhat.com>
      (cherry picked from commit 71a5e666)
  11. 22 Jan, 2021 1 commit
    • Guillaume Abrioux's avatar
      fs2bs: skip migration when a mix of fs and bs is detected · a36eee18
      Guillaume Abrioux authored
      Since the default of `osd_objectstore` has changed as of 3.2, some
      deployments might have a mix of filestore and bluestore OSDs on a same
      node. In some specific cases, there's a possibility that a filestore OSD
      shares a journal/db device with a bluestore OSD. We shouldn't try to
      redeploy in this context because ceph-volume will complain. (either
      because in lvm batch you can't pass partition or about gpt header).
      The safest option is to skip the migration on the node when such a mix
      is detected or force all osds including those already using bluestore
      (option `force_filestore_to_bluestore=True` has to be passed as an extra var).
      If all OSDs are using filestore, then they will be migrated to
      Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1875777
      Signed-off-by: default avatarGuillaume Abrioux <gabrioux@redhat.com>
      (cherry picked from commit e66f12d1)
  12. 19 Jan, 2021 2 commits
  13. 06 Jan, 2021 3 commits
  14. 16 Dec, 2020 5 commits