Hi Daniel
Thank you for your detailed replies.
You are exactly the frist one to point out this security issuse 3 years ago.
>> $HOME/.config/libvirt/auth.conf
I tried it , but still got the same error.
I also find another disadvantage of SASL :
The username+password will be shown using this
I agree with you extend might be one way to solve the problem.
By the way, How about another way that we could import volume
size with float value? such as: 2.5G, 3.4G?
Did community consider about it in the begin?
2017-04-07 20:16 GMT+08:00 Duncan Thomas :
> Cinder
Hey,
Just checking that you didn't mean the following week (17th) as it's Easter
Monday. That's a public holiday in Australia (although the meeting falls on
the Tuesday here), do we know if we'll have quorum next week?
Cheers,
Josh
On Sat, Apr 8, 2017 at 6:10 AM, James E. Blair
On Sat, Apr 8, 2017 at 1:57 AM, Bharat Kumar Kobagana wrote:
> Is it possible use same Python client version to communicate with all
> releases?
Yes, with one recent exception. If you use the current clients you
will be backward-compatible for all non-end-of-life releases,
I found a fun little legacy nugget of compute API non-interoperability
joy tonight.
The "allow_instance_snapshots" config option disables the createImage
server action API. Completely config driven and therefore not discoverable.
What intrigues me is that this isn't applied to the
I'll be in Ann Arbor for the Leadership Training [1], so I'll be away
from keyboard from Monday afternoon to Thursday night.
I might appear from time to time but don't expect me responsive and
helpful during these days.
Some notes though:
1. I'll handle the TripleO Pike-1 release on my free
TC Nomination is now over. The official candidate list is available on
the election website[0].
Starting with this election, there is a new "campaigning" period where
candidates and electorate may debate their statements.
The election will start this Friday.
Thank you,
Tristan
[0]:
On Sun, Apr 9, 2017 at 6:36 PM, Stephen Hindle wrote:
> On Fri, Apr 7, 2017 at 3:00 PM, Doug Hellmann wrote:
>>
>> Although I was a proponent of having the reload feature address
>> that issue, I'm not sure the complexity of the current implementation
>>
On Fri, Apr 7, 2017 at 3:00 PM, Doug Hellmann wrote:
>
> Although I was a proponent of having the reload feature address
> that issue, I'm not sure the complexity of the current implementation
> is something we want to hang on to. In the new spec, I propose an
> alternative
Hello all,
I have a workstation machine which communicates with various OpenStack
releases (Newton, Mitaka, Liberty and Kilo) through
Python clients (python-keystoneclient, python-novaclient,
python-glanceclient, python-cinderclient).
Is it possible use same Python client version to
We've talked about this since Ocata, maybe earlier, but I finally took
the time to write the spec to deprecate the os-virtual-interfaces API.
Here is the spec:
https://review.openstack.org/455023
Hopefully it makes sense. The proposed change is pretty straight-forward
and will help us get
Hello everyone,
I would like to put my name in for the TC election.
For those of you that don't know me, my name is Sean McGinnis and I have been
the Cinder PTL since the Mitaka release. I have been an operator, consumer,
and developer of infrastructure related services since the late 90's.
I
Hi,
a few of us will be off next week, so I'm proposing to cancel the meeting
on Thursday.
Let me know if you have any concern.
andrea
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
Hey everyone,
Just a friendly reminder that OSOps meetings for April will happen on
Monday April 10th and April 24th at 1400UTC in #openstack-meeting-5
Please feel free to add to the agenda and invite 100 people :)
https://etherpad.openstack.org/p/osops-meeting
You can catch up on previous
Hey everyone,
Just a friendly reminder that OSOps meetings for April will happen on
Monday April 10th and April 24th at 1400UTC in #openstack-meeting-5
Please feel free to add to the agenda and invite 100 people :)
https://etherpad.openstack.org/p/osops-meeting
You can catch up on previous
Hey everyone,
Just a friendly reminder that OSOps meetings for April will happen on
Monday April 10th and April 24th at 1400UTC in #openstack-meeting-5
Please feel free to add to the agenda and invite 100 people :)
https://etherpad.openstack.org/p/osops-meeting
You can catch up on previous
On Fri, Apr 07, 2017 at 12:15:49PM -0400, Paul Belanger wrote:
> Greetings,
>
> In an effort to help projects depending on docker infrastructure, we've setup
> a
> reverse proxy cache for http://registry-1.docker.io. Please see the
> instructions in 453811[1] on how to configure dockerd to use
Hi All,
I would like to throw my hat in the ring to be part of the OpenStack Technical
Committee.
I'm working for the OpenStack Foundation as Ecosystem Technical Lead where my
responsibility is to help our members to succeed with OpenStack both as
software and community. My main focus areas
Hi, all.
Due to the local holidays, the following two weekly meetings are cancelled:
* 10th Apr. 2017 (Tomorrow)
* 17th Apr. 2017 (Next week)
Next meeting will take place on the 24th April, 2017.
Sorry for the short notice.
Thank you,
Omer Anson.
On Fri, Mar 31, 2017, at 02:34 PM, James E. Blair wrote:
> Hi,
>
> This is a test message to verify mailing list functionality after the
> upgrade.
>
> -Jim
And this is a followup test after the server had a sad.
Clark
___
OpenStack-Infra mailing
20 matches
Mail list logo