Update component:
- cn-agent@2.13.0
Update component:
- cn-agent@2.12.1
TRITON-1165 mockcloud should use sdc-scripts Update components:
- cn-agent@2.11.0
- deps/sdc-scripts (new dep)
TRITON-922 sdc-mockcloud admin IP functions need to be factored out (#4) Update component:
- triton-netconfig@1.1.0
Update component:
- cn-agent@2.9.0
TRITON-1224 add "agents_uninstall" task to cn-agents "dummy" backend for mockcloud Update component:
- cn-agent@2.8.2
Update components:
- cn-agent@2.8.0
- net-agent@2.2.2
- vm-agent@1.8.2
Update component:
- cn-agent@2.7.0
Update component:
- cn-agent@2.6.2
Update component:
- cn-agent@2.6.1
Update components:
- cn-agent@2.3.2
- net-agent@2.2.0
- vm-agent@1.8.0
TRITON-863 Add support for dummy cmon-agent.
Add support for GET /servers/*/vms/<vm_uuid>
in dummy vminfod.
Add simple script tools/add_externals.sh for adding external interfaces to mock CNs.
Now listens on 127.0.0.1 only.
Adds a dummy vminfod for more consistent view of the system for agents.
Add restify dependency.
Add vm-agent.
Update cn-agent to latest/master.
Add net-agent.
Update cn-agent to b160d04 for delegated dataset support.
First instance should be mockcloud0
not mockcloud1
. Also ignore deleted
instances when determining next name, and increase setup time to 600s from 30s
to allow more CNs to be created.
A re-write of mockcloud to support mocking multiple CNs with a single instance. The mem usage of one mocked CN per VM instances with v1.0.0 was insufficient for testing with many many CNs. Currently this supports just a mocked out cn-agent (using its "dummy" backend).
The first incarnation of mockcloud that, IIUC, would simulate a single CN per instance.