Re: [OpenStack-Infra] The future of our server naming patterns

2016-05-27 Thread Jeremy Stanley
On 2016-05-24 13:50:42 + (+), Jeremy Stanley wrote: [...] > we have a bunch of hostname==service/vhost assumptions baked into > our configuration management right now. While I'm not opposed to > the plan in principle, executing it implies a pretty significant > cleanup effort to stop using

Re: [OpenStack-Infra] The future of our server naming patterns

2016-05-25 Thread James E. Blair
Spencer Krum writes: >> Though I've since been thinking (and a quick codesearch[*] confirms >> it) that we have a bunch of hostname==service/vhost assumptions >> baked into our configuration management right now. While I'm not >> opposed to the plan in principle, executing it implies a pretty >>

Re: [OpenStack-Infra] The future of our server naming patterns

2016-05-24 Thread Jeremy Stanley
On 2016-05-24 10:21:43 -0700 (-0700), Spencer Krum wrote: > At the summit Clark pointed out that many of our vhost templates could > be simplified to listen on *. I think this works for http, not sure > about https. [...] Yeah, I had to do it recently for the storyboard servers, since it appears t

Re: [OpenStack-Infra] The future of our server naming patterns

2016-05-24 Thread Spencer Krum
> Though I've since been thinking (and a quick codesearch[*] confirms > it) that we have a bunch of hostname==service/vhost assumptions > baked into our configuration management right now. While I'm not > opposed to the plan in principle, executing it implies a pretty > significant cleanup effort

Re: [OpenStack-Infra] The future of our server naming patterns

2016-05-24 Thread Jeremy Stanley
On 2016-05-23 20:38:55 + (+), Jeremy Stanley wrote: > As discussed during the "Launch Node, Ansible and Puppet" summit > session in Austin[1], we're making things unnecessarily hard on > ourselves by insisting on having multiple servers in our inventory > with the same name. In order to mak

Re: [OpenStack-Infra] The future of our server naming patterns

2016-05-23 Thread Ricardo Carrillo Cruz
2016-05-23 22:38 GMT+02:00 Jeremy Stanley : > As discussed during the "Launch Node, Ansible and Puppet" summit > session in Austin[1], we're making things unnecessarily hard on > ourselves by insisting on having multiple servers in our inventory > with the same name. In order to make server additi

Re: [OpenStack-Infra] The future of our server naming patterns

2016-05-23 Thread James E. Blair
Jeremy Stanley writes: > We do already have some servers with numbered suffixes but I don't > think this plan changes how we deal with them. When creating a new > server for a pool like that, just use the lowest available unused > number. Here's a relevant historical example: ... Yes, I think i

[OpenStack-Infra] The future of our server naming patterns

2016-05-23 Thread Jeremy Stanley
As discussed during the "Launch Node, Ansible and Puppet" summit session in Austin[1], we're making things unnecessarily hard on ourselves by insisting on having multiple servers in our inventory with the same name. In order to make server addition and replacement automation simpler, lets start usi