Hi Jay,
(Switching Subject to third party testing)
On 4 March 2014 15:13, Jay Pipes wrote:
> Let me know how we can help you!
>
Thanks for the invitation! I will take you up on it :-).
My goal is to make sure the Tail-f NCS mechanism driver is fully supported
in Icehouse.
Question: How shoul
On Tue, 2014-03-04 at 16:31 +0100, Luke Gorrie wrote:
> Option 1: Should I debug the CI implementation we developed and tested
> back in December, which was not based on Tempest but rather on our
> private integration test method that we used in the Havana cycle? The
> debugging that is needed is m
On 4 March 2014 17:07, Jay Pipes wrote:
> I would advise dropping the custom CI setup and going with a method that
> specifically uses the upstream openstack-dev/devstack and
> openstack-infra/devstack-gate projects.
>
This sounds great to me. Thank you for all the work you are doing on
simplify
Howdy!
I have some tech questions I'd love some pointers on from people who've
succeeded in setting up CI for Neutron based on the upstream devstack-gate.
Here are the parts where I'm blocked now:
1. I need to enable an ML2 mech driver. How can I do this? I have been
trying to create a localrc w
oh and in my haste I forgot to say: thank you extremely much to everybody
who's been giving me pointers on IRC and especially to Jay for the blog
walkthrough!
On 13 March 2014 15:30, Luke Gorrie wrote:
> Howdy!
>
> I have some tech questions I'd love some pointers on from people who've
> succee
Howdy!
Here's some follow-up on setting up devstack-vm-gate as a 3rd party.
On 13 March 2014 15:30, Luke Gorrie wrote:
> 1. I need to enable an ML2 mech driver. How can I do this? I have been
> trying to create a localrc with a "Q_ML2_PLUGIN_MECHANISM_DRIVERS=..."
> line, but it appears that th
