<     May 2017     >
Su Mo Tu We Th Fr Sa  
    1  2  3  4  5  6  
 7  8  9 10 11 12 13  
14 15 16 17 18 19 20  
21 22 23 24 25 _2_6 27  
28 29 30 31
00:09 iNs joined
00:29 Babar joined
01:11 livingstn joined
01:15 jane_booty_doe joined
01:24 cqi joined
01:30 techquila joined
01:57 zerocool_ joined
01:57 d^sh joined
02:49 saikat joined
03:32 Wanderer- joined
03:33 Wanderer- joined
03:41 cqi joined
04:03 budhram joined
04:43 dcastellani joined
05:38 atomekk joined
05:57 dag_ joined
05:58 <dag_> my host machine is windows.I have vagrant there.now i want to use ansible as a provisioner.how can i use this
05:59 <ada> https://www.vagrantup.com/docs/provisioning/ansible.html
06:16 vj3k joined
06:30 cqi joined
06:37 ogny joined
06:54 kwladyka joined
07:05 <dag_> what does vagrant-hostsupdater plugin does
07:09 TomyWork joined
07:27 <dag_> what does this plugin do vagrant-hostsupdater??
07:34 <double-p> i only know vagrant-hostmanager (and just ditched it :) )
08:05 antgel joined
08:20 _ADN_ joined
08:35 hoek joined
08:36 <strk> does it make any good to re-use boxes in multiple VM (like Docker) or not ?
08:39 _ADN_ joined
08:40 Pinky_McFly joined
08:41 budhram joined
08:44 balkamos joined
08:47 cstratak joined
08:58 serque joined
09:05 budhram joined
09:48 njbair joined
09:53 napramirez joined
09:53 electrofelix joined
10:15 balkamos joined
10:25 mariusv joined
10:25 mariusv joined
10:26 lunarlamp joined
10:27 balkamos joined
10:33 nicolasbock joined
10:48 k0nsl joined
10:48 k0nsl joined
11:00 Stacie_A joined
11:07 budhram joined
11:12 Stacie_A joined
11:17 kwladyka joined
11:20 serque joined
11:31 cstratak joined
11:35 budhram joined
11:45 budhram1 joined
11:47 zerocool_ joined
12:00 PHPanos joined
12:03 elliotb joined
12:04 memoryleak joined
12:15 <elliotb> I'm using the latest ubuntu/trusty64 box and provisioning with Puppet Apply. I'm a bit new to puppet and noticed the box has 3.4 installed. Any ideas if puppet baked into the box, or is vagrant installing it for me? There is no description on the boxes Atlas page.
12:15 <elliotb> If anyone has any information, it would be really appreciated!
12:18 cstratak joined
12:24 moozer joined
12:28 cstratak joined
12:29 bmurt joined
12:32 Tucky joined
12:32 PaulCapestany joined
12:38 <Tucky> Hi, I have a vagrant file with multiple vm definitions. Can I set specific memory size for each of them (I use virtualbox)?
12:40 <Tucky> I found https://www.vagrantup.com/docs/virtualbox/configuration.html but "config.vm.provider" seems to be a global setting to all VMs?
12:48 <Tucky> Ok, I think I should use "node.vm.provider" instead.
12:52 rkoller joined
12:54 zerocoo__ joined
13:01 techquila joined
13:08 saikat joined
13:15 zerocool_ joined
13:16 kwladyka joined
13:24 jayunit100 joined
13:27 charginghawk joined
13:28 digi691 joined
13:30 runway joined
13:32 digi691 joined
13:35 dhoppe joined
13:38 shiriru joined
13:41 digi691 joined
13:43 digi691 joined
13:45 tapoxi joined
13:48 budhram1 joined
13:49 kwladyka joined
14:04 <strk> is there a quick command to find IP of a machine, and exposed ports ?
14:04 <strk> something like `docker inspect` for docker...
14:07 serque joined
14:23 saikat joined
14:23 Natrick joined
14:25 computeracer joined
14:26 <setuid> strk: you mean using vboxmanage? Yes.
14:27 <setuid> vboxmanage list bridgedifs
14:29 Natrick joined
14:30 <setuid> You could also parse it out of showvminfo
14:32 <strk> vboxmanage showvminfo themachine | grep <the-known-ip-address> # gives no hits
14:32 <strk> found <themachine> via vboxmanage list runningvms
14:32 kwladyka joined
14:33 <strk> and took the first word
14:34 tabakhase__ joined
14:35 tabakhase__ joined
14:36 <setuid> VBoxManage guestproperty enumerate <uuid>
14:37 <setuid> This works for me: VBoxManage guestproperty enumerate <uuid> | grep 'Net/0'
14:40 fredrikh1 left
14:41 <strk> uhm, not really mnemonic :P
14:43 <strk> other question: is it normal that if provisioning fails, next `vagrant up` doesn't show any error ?
14:44 <strk> I mean, the machine is left in non-fully provisioned state
14:45 wlightning-fuel joined
14:46 dumbitguy2 joined
14:47 aspiers_ joined
14:48 vj3k_ joined
14:51 notebox joined
14:52 Kug3lis joined
14:54 PHPanos joined
14:55 jeffreylevesque joined
14:59 pgdagenais joined
15:08 ksclarke joined
15:27 <setuid> strk: Did adding debug and verbosity show any errors? Did you try with --no-provision and see if some process left it in an inconsistent state? Some race condition?
15:29 budhram joined
15:32 <strk> setuid: the provisioning is just not run on second "vagrant up" call
15:37 <setuid> Right, but you don't yet know why it's breaking, you have to instrument the process to figure out where it's dying
15:43 jayunit100 joined
15:47 saikat joined
15:52 untoreh joined
15:57 <strk> I know why it's breaking: I gave wrong vault password
16:00 memoryleak joined
16:01 Stacie_A joined
16:06 <setuid> ;)
16:07 <strk> but what I'm asking is: it is normal for "vagrant up" to still succeed after the first failure ?
16:07 <strk> because it sounds wrong to me
16:08 <strk> the Vault passowrd is always wrong, but on the first run "provisioning" is run and fails, while on the secodn run "provisioning" is not run at all (or this is my impression) so things just succeed
16:08 <strk> resulting in a silent failure
16:15 <double-p> if you run a vagrantfile including provisioners without --provision, it actually warns about this at startup
16:16 cstratak joined
16:17 <setuid> I've got an interesting issue I'm trying to work out: I'm bootstrapping 4 VMs in a row, all of them 90% identical, except the final cookbooks that install some openstack-specific kit on each one. Is there an easier way to bring these up, maybe as clones of each other, so I can then just add the last-mile packages as deltas?
16:18 <setuid> IOW, each of the 4 nodes does its own 'apt-get update && apt-get upgrade' within it, but they all start from the same trusty64 box
16:18 <setuid> It seems wasteful and redundant
16:25 GenteelBen joined
16:37 pgdagenais joined
16:42 ogny joined
17:03 nicolasbock joined
17:08 <setuid> Any thoughts? Ideas?
17:09 <setuid> I was thinking something with rsync-auto might help
17:09 strk left
17:11 njbair joined
17:12 atomekk joined
17:28 kwladyka joined
17:39 enpicket joined
17:46 pgdagenais joined
17:51 Edgan joined
18:01 antgel joined
18:04 livingstn joined
18:05 nicolasbock joined
18:25 kwladyka joined
18:27 nicolasbock joined
18:29 notebox joined
18:30 ahrs joined
18:35 shiriru joined
18:35 serque joined
18:49 Seablade_pixel joined
18:54 kwladyka joined
19:12 moozer joined
19:44 saikat joined
19:45 PHPanos joined
19:45 saikat_ joined
19:57 nalum joined
20:12 nalum joined
20:13 Wicaeed joined
20:14 Specialist joined
20:26 finchd joined
20:26 moozer joined
20:42 _ADN_ joined
20:50 techquila joined
20:52 soLucien joined
21:03 kwladyka joined
21:14 anupn left
21:15 techquila joined
21:21 enpicket joined
21:27 linux_dr joined
21:27 jayunit100 joined
21:27 <linux_dr> Hi… How’s it going?
21:28 <linux_dr> I’m looking at the —machine-readable interface and slightly confused
21:30 <linux_dr> I’m running vagrant global-status —machine-readable, and finding no recognizable type name in the output
21:36 vj3k joined
21:41 <linux_dr> anyone awake in here?
21:44 vj3k_ joined
21:45 ksclarke joined
21:50 <setuid> YEP
21:50 <setuid> er, Yep
21:55 shaytan joined
21:58 Babar joined
22:06 <linux_dr> Hi… I’m looking at —machine-readable output and seem to have found some undocumented tyops
22:06 <linux_dr> types
22:13 spox joined
22:20 caper joined
22:27 TheFuzzball joined
22:29 dheerajchand joined
22:30 cstratak joined
22:42 shaytan joined
22:46 spiette_ joined
22:52 TheFuzzball joined
23:10 spox joined
23:10 spox joined
23:16 shaytan joined
23:18 TheFuzzball joined