On 2 April 2014 14:04, Juha Tynninen juha.tynni...@tieto.com
wrote:
Hi,
I'm sending custom Ceilometer metrics from inside VM instance with
REST
call
to
http://192.168.100.5:8777/v2/meters/vm_cpu_load .
This is successful
/mongo_client.py, line
911, in __check_response_to_last_error
raise OperationFailure(details[err], details[code])
OperationFailure: not okForStorage
Hmm. What am I doing wrong here?
Thanks,
-Juha
On 2 April 2014 14:04, Juha Tynninen juha.tynni...@tieto.com wrote:
Hi,
I'm sending custom
Hi,
I'm sending custom Ceilometer metrics from inside VM instance with REST
call to
http://192.168.100.5:8777/v2/meters/vm_cpu_load.
This is successful and I can see the entered metric data with Ceilometer:
# ceilometer sample-list -m vm_cpu_load
Hi,
I'm having some problems concerning auto scaling feature.
Any ideas?
First scaling up and down is working just fine. But then when tested later
on scaling down/up is no longer working properly.
Scaling down may occur even it shouldn't or scaling up doesn't occur even
it should. When in this
Dake sd...@redhat.com wrote:
Juha,
Copying Angus so he sees. He wrote a big majority of the ceilometer +
heat integration and might have a better idea of the details of the problem
you face.
On 02/24/2014 01:27 AM, Juha Tynninen wrote:
Hi,
I'm having some problems concerning auto
Hi,
I'm using the following unmodified image:
http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64-disk1.img
I set static ip address for the VM instance via Heat template and user-data:
Resources : {
DemoInstance : {
Type : OS::Nova::Server,
Properties : {
Hi,
I'm trying to define config_drive by using volume-id for OS::Nova::Server
in a Heat template.
http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Nova::Serversays
that:
config_drive : String
- value for config drive either boolean, or volume-id.
- Updates cause
Hi,
I'm using stable/havana version of Openstack.
I can boot instance from the pre-existing bootable Cinder volume with nova
command:
nova boot --flavor 2 --block_device_mapping vda=volume id:::0 name for
instance
...but how can this be done with a Heat template? Or can it be done?
}
}
...but the question remains is it possible somehow to define that the
instance is started (booted) from the volume. E.g. instead of ImageId
defined for AWS::EC2::Instance, define the reference to the volume
somehow.
On 9 December 2013 12:56, Juha Tynninen juha.tynni...@tieto.com wrote:
Hi,
I'm
Hi,
In havana the user must have admin privileges to be able to create heat
stacks having e.g. HARestarter resource. Otherwise an error will occur...
What's logic behind this / or is this a bug?
2013-09-19 17:56:11.380 TRACE heat.engine.resource File
Hi,
Previously in grizzly if I killed the VM process (in case of devstack the
relevant qemu-system process) nova
almost immediately noticed this and the status of VM was updated to SHUTOFF.
But now in havana it takes about 5 minutes the VM status to change to
SHUTOFF.
Anyone knows what causes
Many thanks again.
Seems to be I was missing the Tags definition for AutoScalingGroup in the
template:
Tags : [ { Key : metering.server_group, Value : Group_A } ]
Added that and now I can see evaluation occurring and some scaling actions
triggered (some exceptions can be seen in the logs, but
Hi,
I met the problem when tried to be using autoscaling groups in heat
templates with havana (see:
https://bugs.launchpad.net/heat/+bug/1223710)
Can anyone confirm whether the autoscaling should already work with havana?
Currently the evaluation of the ceilometer alarm/meter data seems to be
13 matches
Mail list logo
