see FABRIC-291 for the low level implementation details - FMC-372 for how FMC is going to implement a REST endpoint to do the work using Fabric. So all HQ Server needs to do is a simple JSON POST to FMC at a URL based on the scaleUp/Down operation - with the profile parameter. Then we'll be able to do things like setting up an alert that if a queue gets too big, spin up a new consumer container automatically. Should be a fairly simple Action for HQ really - so long as its easy to discover the HQ server