On Sat, Jun 29, 2013 at 7:49 AM, Anne Gentle
annegen...@justwriteclick.comwrote:
What does no plans to port mean for people already using Floating IPs
and Cloudpipe via API extensions? Sounds like it could mean a couple of
things -
- these are becoming core and won't be an extension any more
Greetings Stackers!
We have had a lot of progress with reviews. Thanks to Sean Dague, Russell
Bryant, Kevin L. Mitchell, Matt Dietz, Joe Gordan, and Michael Still for their
+2 on these merged changes:
https://review.openstack.org/#/c/34389/
https://review.openstack.org/#/c/33482/
Anne Gentle
Content Stacker
a...@openstack.org
On Jun 29, 2013, at 3:26 AM, Christopher Yeoh cbky...@gmail.com wrote:
On Sat, Jun 29, 2013 at 7:49 AM, Anne Gentle annegen...@justwriteclick.com
wrote:
What does no plans to port mean for people already using Floating IPs and
Cloudpipe
Hi Thomas,
We switched to using entrypoints for creating our binaries. Unfortunately,
this means you need to have the glance version installed in some sense in
your path when you want to run those tests. This felt like a no-no when we
made the change, but it worked fine without any changes to our
On 06/30/2013 12:16 AM, Mark Washenberger wrote:
Hi Thomas,
We switched to using entrypoints for creating our binaries.
Can you explain this a bit more?
Unfortunately, this means you need to have the glance version
installed in some sense in your path when you want to run those tests.
On 06/29/2013 02:14 PM, Thomas Goirand wrote:
On 06/30/2013 12:16 AM, Mark Washenberger wrote:
Hi Thomas,
We switched to using entrypoints for creating our binaries.
Can you explain this a bit more?
Unfortunately, this means you need to have the glance version
installed in some sense in
Munging together some replies:
On Sat, Jun 29, 2013 at 12:26 PM, Monty Taylor mord...@inaugust.com wrote:
On 06/29/2013 02:14 PM, Thomas Goirand wrote:
On 06/30/2013 12:16 AM, Mark Washenberger wrote:
Hi Thomas,
We switched to using entrypoints for creating our binaries.
Can you
I believe we should fix the unittests to not shell out to glance-manage
in that manner. One of the nice things about moving the code from bin/
to glance.cmd is that it's available inside of the source tree for
unittests! :) What we want to do is call the glance.cmd.manage:main()
function
On 06/29/2013 08:02 PM, John Bresnahan wrote:
I believe we should fix the unittests to not shell out to glance-manage
in that manner. One of the nice things about moving the code from bin/
to glance.cmd is that it's available inside of the source tree for
unittests! :) What we want to do is
