On Sat, Jun 25, 2011 at 11:47 AM, Jay Pipes <[email protected]> wrote: > On Fri, Jun 24, 2011 at 10:10 AM, Todd Willey <[email protected]> wrote: >> I'd prefer to keep it convenient to develop and demo on a single >> machine. I don't think there is any added inconvenience during >> deployment if the ports are not the standard http ports. > > Can you explain why having the *default* port be 80/8080 for HTTP > services would hinder that? Unless I'm mistaken, spinning up servers > on different ports is as simple as specifying a set of test config > files that have ports set for an all-on-one-machine setup? > > Just curious... > > -jay >
I'm just trying to avoid having to either remember a command line flag for every service I launch, or remember to not check in config files that specify port numbers that I've changed in source directories. If we go to a 80/8080 setup I'll just end up writing scripts that wrap all the services, but I imagine that if I'm doing that to make things easier, people who want to evaluate OpenStack on a single box are going to find things unnecessarily complicated. _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
