Hi Marek,
I've been using the following community AMI with no problem on both m1.tiny and
m1.large:
AMI: Fedora-16-ec2-2001-x86_64-sda (ami-0316d86a)
Being a 64bit image, it is not supported on m1.small.
Cheers,
Eoghan
- Original Message -
> From: "Marek Goldmann"
> To:
> I'm following;
>
> Red Hat Essex Preview
> Lab Guide
> Red Hat Summit - 2012 Edition
> http://fedorapeople.org/~russellb/openstack-lab-rhsummit-2012/
>
> to set up OpenStack, Essex, on Fedora 17
>
> I'm stuck here:
> Now that an admin user has been created, that account can be used to
> adm
> We would like to start testing OS Ceilometer, and I wonder if there
> are already plans to provide RPMs for this component.
Hi Jan,
The first ceilometer release is imminent (i.e. in the next couple days,
timed to coincide with the openstack design summit).
Once the release is out the door, w
> Has this code been security audited at all? It seems to me that the
> billing portion of OpenStack will likely be a high priority target
> for attackers (and naughty users/etc.).
The security story for Ceilometer definitely needs to be hardened ...
- the usage-related notifications emitted by
> > Has this code been security audited at all? It seems to me that the
> > billing portion of OpenStack will likely be a high priority target
> > for attackers (and naughty users/etc.).
>
> The security story for Ceilometer definitely needs to be hardened ...
>
> - the usage-related notificati
- Original Message -
> Hi Eoghan,
>
> >> We would like to start testing OS Ceilometer, and I wonder if
> >> there
> >> are already plans to provide RPMs for this component.
> >
> > Hi Jan,
> >
> > The first ceilometer release is imminent (i.e. in the next couple
> > days,
> > timed to co
Hi Jan,
This is effort has not started as yet, as there's a fair amount
of churn and instability on-going in ceilometer as we tie down
a better interaction model with nova (avoiding direct DB access
and calls to internal APIs).
Having just been incubated, ceilometer will shortly be joining
the o
Try:
echo "select updated_at from services where host like 'server-3%';" | mysql
-u root -pPASSWORD nova
to check the time the services table was updated at.
If the problem is clock skew, you could make nova-manage service list
more forgiving by overriding the service_down_time config option
