But a usefull name is a good way to identify the target server) (ooh and don’t rename your target server to the source server just yet, double take will complain and will not continue. So same os ,service pack,IP and disk layout and your good to go. Make sure your target servers are as identical as possible to your source servers. You can also add it in the hosts file like so Īnsible_winrm_server_cert_validation = ignore # it is suggested that these be encrypted with ansible-vault:# ansible-vault encrypt sourceservers.yml # The following is necessary for Python 2.7.9+ when using default WinRM self-signed certificates:Īnsible_winrm_server_cert_validation: ignore # ansible-vault encrypt sourceservers.yml # it is suggested that these be encrypted with ansible-vault: Store these under the /etc/ansible/group_vars. So in this case a sourceservers.yml and targetservers.yml It contains some examples in how to use an Ansible Inventory file.īut for the these migration you can do something like thisįor each group you create here you can/must create a credential file with the same name. Under your /etc/ansible directory there is a hosts file. You can then check your Kerberos ticket with the command klist Kinit nothing is returned -> don’t panic!!! Then it worked ! When that is done you can test the connection is working by running the below command Please read the kerberos documentation carefully, as your really need this to be correct and working.Įdit the /etc/nf file and change it to reflect your domainĭefault_ccache_name = KEYRING:persistent:% You will also need the python part to this. Yum -y install python-devel krb5-devel krb5-libs krb5-workstation If your windows systems are in a domain (most of them normally are) install the Kerberos dependencies.Or change to your way of working (you can then push this key out to linux server, which are not in scope of this blog) Then run the below commandsĪccept defaults for the keygen. We mostly use at least Ansible version 2, therefore we need to enable the the epel-testing repository to install Ansible. Edit the file under /etc//epel-testing.repo to enable it.We have been using Ansible for quite some time now and we find that installing it on Centos or Ubuntu is the best way to go. We used this mostly in Azure to Aws migrations. Maybe for connectivity to work you will need to attach some public ip’s to your source and target servers. Netbios-name-servers = netbiosserveriphere Public ip’s Make sure that you create a dhcp option set if the servers you are migrating are on dhcp.ĭHCP options set ID: dopt-xxxxxx | NameHere (And also create the target servers in the correct subnets) DHCP option set Make sure that the vpc cidr block and subnets match your current setup exactly. Lets first configure the Aws environment, create the needed vpc, subnets,vpn’s, seurity groups, roles,etc… VPC (more if your not already using Ansible now) AWS Instead of spending hours of work on installing and configuring, exporting, importing, etc… we can now really get things going by using Double Take Move and Ansible.įor this article you need some basic knowledge of Ansible.ĭouble take move is really well made and very user friendly!Īnd the license cost to use this product is forgotten easily when you don’t have to spend hours in exporting-importing – troubleshooting these kind of moves.Īh yes, there is always some prep work to do. When you’re a cloud reseller/architect you often get contacted by customers who want to migrate their infra to Aws.Īlthough I’m not really for the lift and shift way of working, sometimes there is no way around it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |