Open zemanel opened 6 years ago
Hi, yes it will.
@jocatalin which OS would be closer to a production system ?
I did some preliminary work on this and utilized an offical Centos 7 vagrant box. Apart from some minor issues (as some script path issues on playbook) a major blocker was the lack of bonding network interface on that default vagrant box (and ansible_bonding_0
is hardcoded on the playbooks)
@zemanel We typically run DC/OS on CentOS.
Yes, the network interface is currently hardcoded but can perhaps be made configurable via a variable.
CentOS seems like a valid option.
Sent from Yahoo Mail on Android
On Mon, Feb 19, 2018 at 10:58, José Moreiranotifications@github.com wrote:
@jocatalin which OS would be closer to a production system ?
I did some preliminary work on this and utilized an offical Centos 7 vagrant box. Apart from some minor issues (as some script path issues on playbook) a major blocker was the lack of bonding network interface on that default vagrant box (and ansible_bonding_0 is hardcoded on the playbooks)
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
I have a branch on my fork (https://github.com/zemanel/dcos-ansible-packet/tree/vagrant-test-env) where i have been working on this:
vagrant-reload
plugin)dcos_download_path
Ansible var for allowing install dirs other than /root
net_interface
`net_interface_label` (could use better naming here) for the network interfaces of the nodes (i have eth1 on vagrant)The playbook provisioning ran ok on my last test (doing more tests but home wifi speed not the best) but also need to validate the DC/OS installation (web interface at http://
@jocatalin @frankscholten care to take a look at the changes i did there to see if we're going in the right direction ?
Would it be useful to have a local test environment for the playbook on Vagrant ?