OpenStack Ceilometer example: a bit of improvements

This commit is contained in:
Eugene Kalinin
2016-10-17 19:18:40 +03:00
committed by Travis Reeder
parent 1c71f1864d
commit 4edc2feeea
2 changed files with 4 additions and 4 deletions

View File

@@ -68,7 +68,7 @@ $ nova list --all-tenants
+--------------------------------------+-------------+----------------------------------+--------+------------+-------------+------------------+
```
## Use the OpenStack Ceilometer CLI to create an alarm threshold"
## Use the OpenStack Ceilometer CLI to create an alarm threshold
```bash
$ ceilometer alarm-threshold-create \
@@ -103,7 +103,9 @@ $ dd if=/dev/zero of=/dev/null
## Checking IronFunctions log
In 5-10 minutes we should see in the IronFunctions's log:
In 5-10 minutes the Ceilometer alarm will trigger an HTTP callback to the
IronFunctions route we created earlier, and this can be seen from the
IronFunctions API server log:
```
INFO[1633] name=run.myapp.requests type=count value=1

View File

@@ -14,8 +14,6 @@ Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
end
config.vm.box = "ubuntu/trusty64"
# https://bugs.launchpad.net/cloud-images/+bug/1573058
#config.vm.box = "bento/ubuntu-16.04"
# eth0: NAT network - is created by default by Vagrant
# eth1: host-only network - to access the VM using its IP address