I’d just like things like image-list to work under the new client :-)
https://bugs.launchpad.net/python-glanceclient/+bug/1492887
> On 10 Sep 2015, at 8:41 am, Nikhil Komawar wrote:
>
> Hi all,
>
> We recently release python-glanceclient 1.0.0 and it has the default
> shell version as v2. Thi
I'd be glad to see the backwards compatibility parts go in. I got bitten
by this earlier this week and ended up switching my scripts over to using
the python-openstackclient library to work around it.
On Wed, Sep 9, 2015 at 6:41 PM, Nikhil Komawar
wrote:
> Hi all,
>
> We recently release python
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Everyone!
I'd like to announce a pre-release[1] of 2.0.0.dev of the
kitchen-openstack[2] driver gem. I've been able to test this with
Windows 2012R2 and all the flavors of Linux I have on my OpenStack
Cloud, but would love some more feedback.[3
Hi all,
We recently release python-glanceclient 1.0.0 and it has the default
shell version as v2. This may result into some scripts not detecting the
change by default and discomfort to an extent.
So, I am reaching out to this list with the hope of getting some
feedback on the requirements, pros
On 09/09/2015 10:36 AM, David Medberry wrote:
Your users should also have reasonable quotas set. If they can boot thousands of
instances, you may have a quota issue to address. (No problem with the blueprint
or need to set an overall limit though--just that you should be able to address
this with
We recently just upgraded to Juno from Icehouse.
We used the upgrade_levels feature to get Nova off the ground, but ran into
major issues around conductor being too slow to respond to messages and
would cause a lot of our instances to not create. This would only happen
at a particular high amount
Ops - I'm looking for an example of the RPC compatibility issue that was
discussed in Palo Alto. Can someone help me out?
Thanks
Carol
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailma
Your users should also have reasonable quotas set. If they can boot
thousands of instances, you may have a quota issue to address. (No problem
with the blueprint or need to set an overall limit though--just that you
should be able to address this without waiting for that to land.)
On Mon, Sep 7, 2
I too have not attended any meetings previously, but would like to start
getting involved here. The 1pm time would be the least convenient for me,
but not impossible for me to make work.
On Wed, Sep 9, 2015 at 9:18 AM, Curtis wrote:
> On Tue, Sep 8, 2015 at 5:42 AM, Joseph Bajin
> wrote:
> > H
On Tue, Sep 8, 2015 at 5:42 AM, Joseph Bajin wrote:
> Hi Everyone,
>
> One of the items taken from the Operators Meet-up was that the time (10am
> EST) was too early for the west coast people. I've been looking at the
> meeting calendar and have a few suggested times that I'd like to see if they
On Wed, Sep 9, 2015 at 2:56 AM, Jean-Daniel Bonnetot
wrote:
> I’m very surprised to be the only one with this need 8)
Hi,
I think it makes a lot of sense and would be useful to me for sure, so
thanks for taking the time to write the blueprint. :)
Thanks,
Curtis.
>
> So I write a blueprint.
> h
I’m very surprised to be the only one with this need 8)
So I write a blueprint.
https://blueprints.launchpad.net/nova/+spec/limit-spawn-rate-for-users
https://review.openstack.org/#/c/221375/
—
Jean-Daniel
@pilgrimstack
> Le 7 sept. 2015 à 16:48, Jean-Daniel Bonnetot
> a écrit :
>
> Hi,
>
12 matches
Mail list logo
