Hello all,
I recently came across the need to add cinder's volume telemetry data
into a client's ceilometer environment.
I've found that there was a patch for charm-cinder that enables the
cron-tick for cinder-volume-usage-audit and implemented it in a
cherry-picked fashion into my current charm
On Fri, Apr 21, 2017 at 02:30:39PM -0700, James Beedy wrote:
It looks like any LXD I deploy to an instance on AWS is now inheriting the
constraints from the host, this is causing my LXD to fail across the board.
This is slightly difficult to reproduce, as you must have spaces and
subnets defined
On Mon, May 28, 2018 at 10:23:21PM -0700, James Beedy wrote:
I want to shed some light on a few blockers for me right now.
2) Maas needs better support for 3rd party drivers.
* Getting my Mellanox drivers hooked up at commissioning so maas
recognizes the 40Gb interfaces is taking me a few
