On Thu, Feb 5, 2015 at 9:01 PM, Steve Gordon sgor...@redhat.com wrote:
- Original Message -
From: Przemyslaw Czesnowicz przemyslaw.czesnow...@intel.com
To: OpenStack Development Mailing List (not for usage questions)
1) If the device is
Hi wanyen and Nova team,
I support wanyen for this FFE. The code changes are very small and harmless
to Nova. They just provide a way to ironic to comsume inputs given at
On Sat, Feb 7, 2015 at 12:33 AM, Hsu, Wan-Yen firstname.lastname@example.org wrote:
I would like to
We are proposing this spec: https://review.openstack.org/#/c/148730/ . In
there we detail how will work recursive deletion and disabling for projects
(and domains). This change was dependent on the Reseller spec that was
approved before the deadline and adds some good improvements for the
On 06/02/15 23:07, Qiming Teng wrote:
Just checked your template. It seems your SoftwareDeployment resource
is not referencing the SoftwareConfig resource properly. A
SoftwareDeployment 'binds' a SoftwareConfig to a Server. Without that
'binding', the template won't work as expected.
2015-02-09 9:26 GMT+09:00 Christopher Yeoh cbky...@gmail.com:
I wasn't at the mid-cycle meetup for Kilo but even for Juno I'll admit I
was a bit lost. It's not my fault, I'm more good looks than brains. :)
When I look at approved specs for Kilo, three pop out:
Couple of questions..
1) Roll back support : I came across few blueprints that talk about the
roll-back support but not sure if they are delivered yet, I wanted to check
if something is there out of the box that I should be aware of. Ofcourse,
roll-back being very specific, I'd
We want to run python-manilaclient along with clients for other OpenStack
services coming from OpenStack Juno release.
But, since https://github.com/openstack/python-manilaclient has only the
master branch and no branch for Juno, if I try to deploy it on the same
node, it breaks others
Sorry for the burden.
It took more effort than I expected.
Finally, I think I understand what you guys have told me again and again.
Thanks very much for putting up with me and my questions.
From: Ben Swartzlander [mailto:b...@swartzlander.org]
Sent: Thursday, February 05, 2015
On Sat, Feb 7, 2015 at 8:35 AM, Matt Riedemann mrie...@linux.vnet.ibm.com
I'm not going to hide it, I don't know what's going on with the v2.1 API
status, i.e. what is the criteria to that thing dropping it's
So I caught up with Matt on IRC, repeating some