On 02/02/2016 8:45 AM, Jordan Pittier wrote:
On Tue, Feb 2, 2016 at 2:09 PM, gordon chung
mailto:g...@live.ca>> wrote:
yeah... the revert broke us across all telemetry projects since we fixed
plugins to adapt to v3. i'm very much for adapting to v3 since it's lingered
around for years. i think
On Tue, Feb 2, 2016 at 2:09 PM, gordon chung wrote:
> yeah... the revert broke us across all telemetry projects since we fixed
> plugins to adapt to v3. i'm very much for adapting to v3 since it's
> lingered around for years. i think given the time lapsed, if it breaks
> them, tough.
>
This is
yeah... the revert broke us across all telemetry projects since we fixed
plugins to adapt to v3. i'm very much for adapting to v3 since it's lingered
around for years. i think given the time lapsed, if it breaks them, tough. the
only issue i had with original patch was it merged on a Friday with
Hi Sean,
I've been working on v3 only related stuff in a while and I volunteer on
this too.
Henrique
Em ter, 2 de fev de 2016 às 05:41, Julien Danjou
escreveu:
> On Mon, Feb 01 2016, Sean Dague wrote:
>
> > The revert is here - https://review.openstack.org/#/c/274703/ - and will
> > move it's
On Mon, Feb 01 2016, Sean Dague wrote:
> The revert is here - https://review.openstack.org/#/c/274703/ - and will
> move it's way through the gate once the tests complete.
So… yeah, but FTR this revert broke again at least Gnocchi's gate. The
telemetry projects had already adapted to the v3 switc
Thanks for bringing this up Sean.
I went ahead and documented all the way the projects/gates/clients broke in
an etherpad: https://etherpad.openstack.org/p/v3-only-devstack
These are all the projects that I know that were affected, if someone knows
others, please add your findings.
Sean, you can