Comment 3 for bug 1530515

Reviewed: https://review.openstack.org/279913
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=17e6e629f5660a364498b2bfd2f5aa6aede79859
Submitter: Jenkins
Branch: master

commit 17e6e629f5660a364498b2bfd2f5aa6aede79859
Author: xionglingfeng <email address hidden>
Date: Sat Feb 13 23:50:46 2016 -0330

    Allow cinder-volume to be configured to use NFS

    Allow cinder-volume, nova-compute and nova-libvirtd to be configured to
    use NFS. In order to mount and work with NFS shares, several containers
    needed the NFS packages installed during build time.

    One somewhat significant change is the addition of an explicit bind
    volume for nova-compute that has shared mounts enabled.

    According to docker-run(1), the shared mount propagation flag can only
    be specified for bind mounted Docker volumes and not named volumes.

    In an NFS setup, cinder-volume mounts the NFS shares so that it can
    create and manage the Cinder volumes. When a new instance is created
    with a Cinder volume or a Cinder volume is attached to an existing
    instance, nova-compute mounts the Cinder volume from the NFS share for
    nova-libvirtd. In order for nova-libvirtd to then see those Cinder
    volumes the shared mounts flag must be enabled for the Docker volume.

    Remove the rpcbind container as it is only necessary for operators who
    are using NFSv3 or lower. There is no known need for this currently
    however, this container can be added in the future should an operator
    require it.

    Co-authored-by: Ryan Hallisey <email address hidden>
    Co-authored-by: Andrew Widdersheim <email address hidden>
    Change-Id: Iad77c05bce8876bdcc69b7ec22edd50e3bf48b9f
    Closes-Bug: #1530515
    Partially implements: blueprint nfs-support-in-cinder