On 06/01/15 03:20, Steve Gordon wrote:
- Original Message -
From: "Maish Saidel-Keesing"
To: openstack-dev@lists.openstack.org
On 05/29/15 18:25, Matthew Thode wrote:
On 05/29/2015 10:18 AM, Ihar Hrachyshka wrote:
What about release notes? How can we now communicate some changes that
Hi all folks from Cinder,
According to our agreement in the Vancouver summit, I submitted a
cinder-spec to do the volume migration improvement. The spec is here for
review: https://review.openstack.org/#/c/186327/. Please feel free to give
your comments.
@Mitsuhiro Tanino, I believe you can sub
I have this same problem with devstack master. I’m not sure what it is other
then it involves the requirements repo possibly not containing
oslo.versionedobjects on my system. Dims has a suggestion to do something
about it, but I didn’t get back to it. Try joining channel
#openstack-containe
Hi, all
I am following
http://git.openstack.org/cgit/openstack/magnum/tree/doc/source/dev/dev-quickstart.rst
to
install magnum with openstack kilo version.
At the end, there are error messages like
python update.py /opt/stack/magnum
...
Syncing /opt/stack/magnum/requirements.txt
2015-0
Hi Thomas,
The time reserved for the weekly IRC is 1600 UTC on Tuesdays
(http://eavesdrop.openstack.org/#Neutron_VPNaaS_Meeting). The IRC channel
might not be available on any other time (1500 UTC is taken by the libvirt team
meeting).
Thanks,
—Hanif.
On 5/29/15, 12:57 PM, "Vikram Choudha
+1 for Jay's suggestion.
xuhaiwei
-Original Message-
From: Davanum Srinivas [mailto:dava...@gmail.com]
Sent: Monday, June 01, 2015 8:26 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Magnum] Does Bay/Baymodel name should be a
required op
- Original Message -
> From: "Maish Saidel-Keesing"
> To: openstack-dev@lists.openstack.org
>
> On 05/29/15 18:25, Matthew Thode wrote:
> > On 05/29/2015 10:18 AM, Ihar Hrachyshka wrote:
> >> What about release notes? How can we now communicate some changes that
> >> require operator cons
On 05/31/2015 05:50 PM, Alan Pevec wrote:
> 2015-05-29 18:30 GMT+02:00 Jeremy Stanley :
>> On 2015-05-29 16:30:12 +0100 (+0100), Dave Walker wrote:
>>> This is generally my opinion as-well, I always hoped that *every*
>>> commit would be considered a release rather than an arbitrary
>>> tagged date
+1 from me as well
On Sun, May 31, 2015 at 6:08 PM, Steven Dake (stdake) wrote:
> Jay 513
>
> +1 on mandatory name requirement.
>
> From: Jay Lau
> Reply-To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: Sunday, May 31, 2015 at 2:38 PM
> To: OpenStack Development Mail
Hey folks,
Since this is our first odd week meeting and the time is different from our
original time, I’d like to remind folks interested in Kolla to attend our IRC
meeting in openstack-meeting-4 at 2200 UTC on Wednesday, June 3rd.
Agenda is here:
https://wiki.openstack.org/wiki/Meetings/Kolla#
2015-05-29 18:30 GMT+02:00 Jeremy Stanley :
> On 2015-05-29 16:30:12 +0100 (+0100), Dave Walker wrote:
>> This is generally my opinion as-well, I always hoped that *every*
>> commit would be considered a release rather than an arbitrary
>> tagged date.
> [...]
>
> If we switch away from lockstep ma
Jay 513
+1 on mandatory name requirement.
From: Jay Lau mailto:jay.lau@gmail.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Sunday, May 31, 2015 at 2:38 PM
To: OpenStack Development Mailing List
mailto:openstac
Just want to use ML to trigger more discussion here. There are now
bugs/patches tracing this, but seems more discussions are needed before we
come to a conclusion.
https://bugs.launchpad.net/magnum/+bug/1453732
https://review.openstack.org/#/c/181839/
https://review.openstack.org/#/c/181837/
https
Starting tomorrow, the akanda project will be meeting on #openstack-meeting
at 11:00 PDT. Agenda is in the usual place
https://wiki.openstack.org/wiki/Meetings/akanda
See you there
~ sean
__
OpenStack Development Mailing List
Hey Bryan,
The configuration is done through a provider - you can use it in your
composition layer, your site.pp or wherever else you want - a bit like this:
ceph_config {
'osd/osd_journal_size', value => '16384';
'osd/osd_max_backfills', value => '1';
# ...
'client/rbd_cache': va
+1!
2015-05-31 23:30 GMT+08:00 Hongbin Lu :
> +1!
>
>
>
> *From:* Steven Dake (stdake) [mailto:std...@cisco.com]
> *Sent:* May-31-15 1:56 AM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* [openstack-dev] [magnum] Proposing Kai Qiang Wu (Kennan) for
> Core for M
Hi All,
I would like to ask about the user-facing notifications part of the list. Do
you have a roadmap for this? Is this driven by the Zaqar team? What are the
next steps?
Thanks and Best Regards,
Ildikó
-Original Message-
From: Clint Byrum [mailto:cl...@fewbar.com]
Sent: May 27, 201
+1!
From: Steven Dake (stdake) [mailto:std...@cisco.com]
Sent: May-31-15 1:56 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [magnum] Proposing Kai Qiang Wu (Kennan) for Core for
Magnum
Hi core team,
Kennan (Kai Qiang Wu's nickname) has really done
As a public service announcement I thought I'd mention something that we
recently spent quite a few hours tracking down.
When neutron runs "ip netns exec" to run dnsmasq or neutron-ns-metadata-proxy,
this causes the creation of a new filesystem namespace (in addition to setting
the network nam
hi Rob
thx for your information, i have updated my horizon master, but it seems
the issue still exists, do you running this well after update the master?
2015-05-29 17:35 GMT+08:00 Rob Cresswell (rcresswe) :
> This was a known bug with the modals, which was fixed yesterday. Update
> horizon ma
On Thu, May 28, 2015 at 4:54 PM, Duncan Thomas
wrote:
> On 28 May 2015 at 13:03, Deepak Shetty wrote:
>
>> Isn't this similar to what cinder transfer-* cmds are for ? Ability to
>> transfer cinder volume across tenants
>> So Manila should be implementing the transfer-* cmds, after which
>> admin
I also learn that from Sean!
-Original Message-
From: Jay Pipes [mailto:jaypi...@gmail.com]
Sent: Saturday, May 30, 2015 2:58 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [nova][api] New micro-version needed for api bug
fix or not?
On 05/29/2015 05:04 AM, John G
Replied in line with prefix [alex]
-Original Message-
From: John Garbutt [mailto:j...@johngarbutt.com]
Sent: Friday, May 29, 2015 8:05 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova][api] New micro-version needed for api bug
fix or
+1 from me!
On Sun, May 31, 2015 at 1:56 AM, Steven Dake (stdake) wrote:
> Hi core team,
>
> Kennan (Kai Qiang Wu’s nickname) has really done a nice job in Magnum
> contributions. I would like to propose Kennan for the core reviewer team.
> I don’t think we necessarily need more core reviewers o
Hi,all. I have a question about keystone federation. Does one keystone have
multiple identity providers?
For examle, there are 3 keystone - A, B and C. Can I configure B and C as the
A‘s identity provider at the same time?
If it's OK, so what's the sequence if we send a request to keystone A?
Good for me - Tuesday at 1600UTC
-Original Message-
From: Doug Wiegley [mailto:doug...@parksidesoftware.com]
Sent: Thursday, May 28, 2015 10:37 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [designate] and [lbaas] - GSLB API and backend
+1 for Kennan.
Thanks & Regards
Madhuri Kumari
From: Steven Dake (stdake) [std...@cisco.com]
Sent: Sunday, May 31, 2015 11:26 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [magnum] Proposing Kai Qiang Wu (Kennan) for
27 matches
Mail list logo
