gistfile1.txt

15:35 < goodwill> ok, this is a stupid question. but what is the prescribed way to handle development/production configuration in Java? Maven 
                  profiles?
15:35 < justintime> IE, they don't call a trunk a trunk, they call it an etherchannel or something.
15:35 < tomonocle> Those are two different things though
15:35 -!- vvuksan [[email protected]] has quit [Ping timeout: 240 seconds]
15:36 < jtopper> ISTR other vendors' idea of a trunk being what Cisco call an etherchannel
15:36 < jtopper> but the other vendor I'm thinking about might have been Netgear so basically fuck them
15:37 < tomonocle> 802.1q claimed the term 'trunk'
15:37 < tomonocle> So it's a little silly to conflate the two
15:37  * surfichris explores LAX wifi
15:37 < supine> this ^
15:37 < Volcane> yeah and trunking tend to refer to extending the backplane and management - turning many switches ito 1
15:37 < Volcane> thats not etherchannel
15:37 < Volcane> cisco does do trunking
15:37 -!- includex [[email protected]] has joined ##infra-talk
15:38 -!- paulmooring [[email protected]] has quit [Ping timeout: 245 seconds]
15:38 < supine> Volcane: I think you mean "stacking"?
15:38 < tomonocle> Yeah, I'd call that stacking
15:38 < Volcane> hah yeah - see its all confusing :P
15:38 < tomonocle> :)
15:39 < supine> trunk is a single "link" with multiple VLANs
15:39 < justintime> goodwill: I don't know if it's prescribed, but we're moving to a system where the devs include properties inside the war 
                    (they use maven profiles), but any of those properties can be overridden by system level properties files located in 
                    /etc/.  We have a jenkins job that builds an RPM of the app, and we managed the /etc/ properties files in puppet
15:39 < Volcane> yeah - etherchannel :P
15:39 < supine> etherchannel or portchannel is bonding/aggregating multiple physical links
15:39 < surfichris> etherchannel = LAG
15:39 < goodwill> justintime: interesting, thank you
15:40 < justintime> goodwill: the best part is that the devs can supply what they think are sane defaults, but we can override them without 
                    having to do a redeploy
15:40 < justintime> *what they think* being the key term :)
15:42 < goodwill> interestings
15:42 < goodwill> justintime: are the overrides for the app? or whole tomcat and are namespaced
15:42 < laurent\> with extremeos it's (load) sharing
15:43 < justintime> It's all app level for that stuff.  For cases where we have different settings for stage and prod, we let hiera sort all 
                    that out for us.