Jason Hennessey
Jason Hennessey
It turns out I was wrong -- we **can** mix sudo and non-sudo travis jobs! Here was the amazing response Travis support sent back to me: > It is possible...
Running multiple HaaS APIs (as opposed to the network action daemon) under separate webservers.
I thought we supported mysql? Doesn't SQLAlchemy get us support for several DBs?
Also, the instructions need to be updated to reflect that CentOS does not have a libvirt user by default.
... and there should be a reference to the haas.cfg base_imgs in the Headnode section
Sorry that I didn't see your previous comment. re: the original issue, it's more of a styling/separation of the headnode VMs from any other libvirt VMs the system might have....
I'd suggest that to maintain simplicity, we set a flag that causes the journal action thread(s) to suspend, verify this happened, then deploy that switch's config.
Treat the trunk as another port that supports "trunked" mode? Perhaps support a free text field that is a series of special commands?
@christophernhill, is this still a feature you'd like? If so, it'd be good to talk about how well the HaaS model maps onto IB partitions.
This should also include: - [ ] Testing the various `HTTPClient` methods (currently in cli.py). - [ ] For testing KeystoneHTTPClient, it might make sense to modify `tests/integration/keystone.py`. - [...