On Mon, Aug 6, 2018 at 8:52 PM containerkid <prasanthgku...@gmail.com> wrote:
> Dear All.
> I am working on a project where we have a scenario in which we have to mount
> an NFS file system when each time system boots up ( we spin up using
> AWS/GITLAB CI/CD approach) so each time i get new instance with new Private
> ip, but my NFS( EFS in aws) will remain same and the mount point also.
> Environment is as below :
> infrastructure is build in AWS via terraform
> configuration management we are using Ansible.
> Situation is like this below :
> We have to deploy a software which is loaded in S3 bucket , when the gitlab
> runner build the AMI we mount the NFS file system using normal way of mouting
> using the ansible and download the binaries in the file system . Once its
> extracted file system will umount and AWS ami creation will start.
> In the deployment phase i have to mount the file system so that RDS can
> access will start provisioning the application environment , i think the best
> option is autofs instead of confd ( any suggessions are welcome) but if i use
> ansible for autofs how i can go for configuration ? i just need to mount the
> file system during the system boot itself thats it .
I think this line of discussion is best suited for the ansible-project
list as that's more focused on users of Ansible aiming to solve real
world problems and share solutions, but this list is meant for
discussion of developing Ansible itself.
> You received this message because you are subscribed to the Google Groups
> "Ansible Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-devel+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.