ceph-ansible/roles/ceph-rgw/tasks/start_docker_rgw.yml

---
- name: include_task systemd.yml
  include_tasks: systemd.yml

- name: systemd start rgw container
  systemd:
    name: ceph-radosgw@rgw.{{ ansible_facts['hostname'] }}.{{ item.instance_name }}
    state: started
    enabled: yes
    masked: no
    daemon_reload: yes
  with_items: "{{ rgw_instances }}"
Re-arrange docker invocation and fix bootstrap rgw Signed-off-by: Sébastien Han <seb@redhat.com> 2015-07-28 23:35:47 +08:00			`---`
container: isolate systemd tasks This commit isolates the systemd unit files generation for containers into separate yml files in order to be able importing each corresponding roles without playing all tasks. This is needed so we can run ceph-ansible to render systemd unit files so they call podman instead of docker. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com> 2019-07-24 16:10:18 +08:00			`- name: include_task systemd.yml`
			`include_tasks: systemd.yml`
docker: enable rgw container on Atomic host environment 2016-06-01 03:59:05 +08:00
			`- name: systemd start rgw container`
rgw: refact start_docker_rgw.yml remove usage of `shell` module in favor of `systemd` module. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com> 2017-09-17 05:36:29 +08:00			`systemd:`
Use ansible_facts It has come to our attention that using ansible_* vars that are populated with INJECT_FACTS_AS_VARS=True is not very performant. In order to be able to support setting that to off, we need to update the references to use ansible_facts[<thing>] instead of ansible_<thing>. Related: ansible#73654 Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1935406 Signed-off-by: Alex Schultz <aschultz@redhat.com> 2021-03-03 22:43:50 +08:00			`name: ceph-radosgw@rgw.{{ ansible_facts['hostname'] }}.{{ item.instance_name }}`
docker: enable rgw container on Atomic host environment 2016-06-01 03:59:05 +08:00			`state: started`
			`enabled: yes`
update: mask systemd service units during upgrade This prevents the packaging from restarting services before we do need to restart them in the rolling update sequence. We want to handle services restart at rolling_update playbook. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com> 2019-03-20 18:35:36 +08:00			`masked: no`
rgw: add support for multiple rgw instances on a single host With this, we could have multiple rgw instances on a single host with a single run, don't have to use rgw-standalone.yml which does not seems able to bind ports separately. If you want to have multiple rgw instances, just change 'radosgw_instances' to the number you want, which defaults to 1. Not compatible with Multi-Site yet. Signed-off-by: guihecheng <guihecheng@cmiot.chinamobile.com> 2018-11-09 08:56:57 +08:00			`daemon_reload: yes`
			`with_items: "{{ rgw_instances }}"`