Keep in mind I am only trying to test what was done, not provision machines for production. And then try to coax some more work on it, I suspect it doesn't pair up the grabber box to it's voctocore.
I am assuming this will have some value to the dc-video team, hopefully the cost of my fumbling will be worth it. So the actual setup is currently whatever was you (or someone) had in mind. I did just learn how the playbook gets run at the end of a single machine's setup, and only sets up that one local machine. thus the ansible_connection=local (which I thought was in there for testing so that one box would be setup to do everything.) Is it a goal that once all the boxes are provisioned that they can be updated? Like "change fps from 29.9 to 60" If so, then the ansible_connection=local won't apply, right? On Wed, Dec 14, 2016 at 1:35 PM, Louis-Philippe Véronneau < [email protected]> wrote: > AFAIK, the "setup_ansible.sh" script works fine (we tested it), it's the > ansible calls that it runs that causes problems :D > > As for the dhcp problem, your machine needs to be called "encodercube1" > for the right ansible roles to be ran. This is specified in the > "inventory/hosts" file. > > This file should be modified to represent your actual setup and is there > only as an example. The important part of the ansible code we wrote is > in the "roles" directory. You want to craft your "hosts" file to put > your machines in the right groups (you can have a look at them in site.yml) > > -- > pollo > > On 14/12/16 03:23 AM, Carl Karsten wrote: > > I think I have something going using juju and > > https://github.com/marcoceppi/charm-ubuntu/tree/carlfk > > > > I'll post instructions or something soon. > > > > basically, setup containers, stuff hostnames/IPs in /etc/hosts. > > > > ansible-playbook -u ubuntu -i inventory/hosts site.yml -b > > > > > > I think I found the first bug: > > TASK [dhcp-server : configure the dhcp server] > > ********************************* > > fatal: [encodercube1]: FAILED! => {"changed": true, "failed": true, > "msg": > > "Destination directory /etc/dnsmasq/dnsmasq.d does not exist"} > > > > I am guessing this is the problem: > > > > [dhcp-server] > > encodercube1 > > > > https://anonscm.debian.org/git/debconf-video/ansible.git/ > tree/inventory/hosts#n11 > > > > > > > > > > On Tue, Dec 13, 2016 at 3:07 PM, Carl Karsten <[email protected]> > > wrote: > >> > >> At the last dc-video sprint this was put together: > >> > >> > > https://anonscm.debian.org/git/debconf-video/ansible.git/ > tree/setup_ansible.sh#n20 > >> > >> but never tested, and something about "doesn't have the dynamic bits in > > place" > >> > >> I would like to test it, but don't really want to setup a pile of > > physical machines. > >> > >> my laptop only has 8gig, so I'm not sure it will handle enough VMs. (I > > think on the order of 8-12 targets for 2 rooms, streaming, file server, > > whatever.) > >> > >> I hear I might be able to use containers. I have looked into lxc/lxd and > > docker/docker-compose ... it all looks promising, but I can't figure out > > exactly what to really do. > >> > >> If someone can give me a script or whatever that will set up an > > environment to test the playbook I'll test and log issues and all that. > >> > >> I don't expect to hook up any video hardware (hdmi2usb, cameras, bm > > cards) or even run vocto. I just want to run ansible-playbook (probably > > on my laptop) and look at the results (logs and config files) > >> > >> > >> -- > >> Carl K > >> > > > > > > > > -- > > Carl K > > > > > > > > _______________________________________________ > > Debconf-video mailing list > > [email protected] > > http://lists.debconf.org/mailman/listinfo/debconf-video > > > > > _______________________________________________ > Debconf-video mailing list > [email protected] > http://lists.debconf.org/mailman/listinfo/debconf-video > >
_______________________________________________ Debconf-video mailing list [email protected] http://lists.debconf.org/mailman/listinfo/debconf-video
