monasca and murano both default to port 8082

[Matt Fischer]

Both monasca and murano are defaulting to port 8082. I'd prefer this not to be the case so will you guys please work out who got it first etc.

Once a port is picked for both projects I'd recommend updating the docs to stake your claim.

http://docs.openstack.org/kilo/config-reference/content/firewalls-default-ports.html

[David Medberry (med)]

I sense that Murano is going to win this one.

[David Medberry (med)]

Murano uses this port since at least June 2014.

[David Medberry (med)]

Okay, Feb 2014...

[Ekaterina Chernova (efedorova)]

Since Murano uses this port for a while (since 2013 to be sure), fix for this us will be in updating documentation, so any new project will know that is port is occupied

[Allan G (greental)]

Triaged - will change Monasca Events API to a different port

[Serg Melikyan (smelikyan)]

Thank you, Allan!

[Ekaterina Chernova (efedorova)]

https://review.openstack.org/#/c/234819/

[Cindy O'Neill (oneilcin)]

the monasca-events-api currently uses port 8082. I will change the port to default to 8072.
In the meantime, the monasca-events-api is only used for events which is under development - you can stop the monasca-events-api service and this will not affect metrics and alarms.

[Cindy O'Neill (oneilcin)]

The newest version of monasca-events-api in pypi (0.0.6) now uses a new port: 8072.
We also changed the functional tests that were in monasca-events-engine, and monasca-events-transform to use the new port.