| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
| |
Yaml suggest to use .yaml when possible:
http://www.yaml.org/faq.html
This patch renames the file.
Change-Id: I3f8b1d337e0b1a8ab33832573b72624ae064021d
Signed-off-by: Zhao Lei <zhaolei@cn.fujitsu.com>
|
| |
|
|
|
|
|
|
|
|
| |
A couple of comments during my latest CORS review indicated that
there is a misunderstanding on why the Vagrantfile in ironic exists.
In those comments, the assumption appeared to be that vagrant is used
to provision ironic, not just the development resources necessary to
work on ironic. This patch adds documentation to clarify that.
Change-Id: I7d71adaba402a62343d1e0399ee53410b76c973f
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This makes two changes to the Vagrant defaults for the developer VM:
- Lowers VM memory from 2048 to 512, and pins the VM to 25% of one CPU
core. This is helpful for low-power development environments (like
laptops) and is sufficient for RabbitMQ and MySQL.
- Changes the default set of hardware drivers to be a minimal set
for developer environments that do not require the installation
of any hardware-specific utilities or libraries.
This list is: pxe_ssh, agent_ssh, fake
Change-Id: Icb5e0e42a07386b93250f8fa461424b69c7cdee9
|
|
|
This patch adds a vagrantfile and ansible playbook that captures
the instructions from the ironic developer quickstart. By using
'vagrant up', and configuring your local dev instance to use
192.168.99.11, you should be able to exercise your services locally.
Documentation has also been updated.
Change-Id: Ic4f42e59cbda968d301c797ef77ff98030c55c41
|
