On Fri, May 1, 2015 at 2:50 PM, Adam Lawson alaw...@aqorn.com wrote:
I purposely didn't email the general mailing list since I didn't want to
cross-post, hard to have these discussions across verticals and choosing
one list = hearing one community - those subscribed to the developer
mailing
Thanks Adam!
That makes sense to me!Wanjing Xu
From: adam.harw...@rackspace.com
To: openstack-dev@lists.openstack.org
Date: Fri, 1 May 2015 16:33:09 +
Subject: Re: [openstack-dev] [Neutron][LBaaS] Why do we need to select subnet
when creating a pool?
The subnet_id on the pool
Hi all,
At around the time Barbican was applying for incubation there was a
discussion about supported WSGI frameworks. From memory the decision
at the time was that Pecan was to be the only supported framework and
that for incubation Barbican had to convert to Pecan (from Falcon).
Keystone is
+1
From: Alex Xu sou...@gmail.commailto:sou...@gmail.com
Reply-To: OpenStack List
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Friday, May 1, 2015 at 6:30 AM
To: OpenStack List
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject:
Paging David Lyle!
We're trying to nail down exactly what work needs to be done on the Karma
patch to get your approval and avoid further frustrating patch churn. Could
you take a moment to respond to Matt's question, and/or discuss here what
you're looking for? We tried pinging you on IRC, but
Excerpts from Adam Lawson's message of 2015-05-01 14:50:33 -0700:
I purposely didn't email the general mailing list since I didn't want to
cross-post, hard to have these discussions across verticals and choosing
one list = hearing one community - those subscribed to the developer
mailing list.
Hi,
TL;DR: Please review:
https://review.openstack.org/#/q/status:open++topic:bug-1444736,n,z
I would like to share some progress/feedback about integrating Beaker in
our modules.
First, everything is updated in the Google Doc [1]
My main blockers were related to packaging in UCA, I had
Hello everyone,
Some of you have reached out to me asking questions about when we will start
meeting discussion on the service chaining feature BPs in OpenStack.
I have set up agoto meeting for an audio meeting discussion so that we can
sync up thought and bring everyone on the same page in a
On 05/01/2015 05:35 PM, Emilien Macchi wrote:
Hi,
TL;DR: Please review:
https://review.openstack.org/#/q/status:open++topic:bug-1444736,n,z
I would like to share some progress/feedback about integrating Beaker in
our modules.
First, everything is updated in the Google Doc [1]
My main
Hello,
I am playing around with Neutron LBaaS API calls as per Neutron/LBaaS/API
2.0 docs. I have noticed below behavior against working devstack. I would
like to clarify on it:
1. I create a loadbalancer using RESTAPI with the attributes -
'vip_subnet_id' and 'admin_state_up' as 'False'. It is
On 01/05/15 11:44, John Garbutt wrote:
Hi,
In case you were unable to make yesterday's Nova meeting...
I was there, but still a bit shy and retiring... :-)
If you have a suggestion for a Nova design summit session, please
ensure you add it to before the next Nova meeting (7th May):
Anyone still interested in this work? :)
* there's a stable/kilo branch now (see
http://git.openstack.org/cgit/stackforge/nova-docker/).
* CI jobs are running fine against both nova trunk and nova's
stable/kilo branch.
* there's an updated nova-spec to get code back into nova tree (see
Good stuff. Thanks everyone for your hard work on getting Octavia to this point!
Cheers,
--Jorge
From: Brandon Logan
brandon.lo...@rackspace.commailto:brandon.lo...@rackspace.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
On Thu, Apr 30, 2015 at 5:17 PM, Eichberger, German
german.eichber...@hp.com wrote:
Hi,
I am proposing that Octavia is joining the Networking program as a project
under the Services area.
Octavia is the open scalable reference implementation for Neutron LBaaS V2
and has always seen itself
Our PO files contain information about location (filename and line
numbers) as well as untranslated strings. Dolph suggested to me recently
to import into projects only the *translated* strings and I did some
investigation and implementation after discussion with the translation
team [1] -
?+1 from me
From: Kyle Mestery mest...@mestery.com
Sent: Friday, May 1, 2015 8:53 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [octavia] Joining Neutron under the big tent
On Thu, Apr 30, 2015 at 5:17 PM,
Thanks for your reply, Kevin, and sorry for the delay in following up.
On 21/04/15 09:40, Kevin Benton wrote:
Is it compatible with overlapping IPs? i.e. Will it give two different
VMs the same IP address if the reservations are setup that way?
No, not as I've described it below, and as we've
Davanum Srinivas wrote:
One concrete suggestion based on my experience working with Kris
Lindgren on Heartbeat patch:
http://markmail.org/message/gifrt5f3mslco24j
I could have added a Co-Tested-By (or Co-Operator - get it? :) in
my commit message which would have signaled a concrete
On 1 May 2015 at 05:39, Sean Dague s...@dague.net wrote:
On 04/30/2015 12:53 PM, Matt Riedemann wrote:
snip
Yeah why would you not include admin tests? Like listing services and
hosts in nova?
It is extremely easy to say why not include *, it's valid function and
we're going to end up with
+1
Governance patch filed:
https://review.openstack.org/179417
Thanks,
doug
On May 1, 2015, at 9:58 AM, Jorge Miramontes jorge.miramon...@rackspace.com
wrote:
Good stuff. Thanks everyone for your hard work on getting Octavia to this
point!
Cheers,
--Jorge
From: Brandon
Excerpts from Adam Lawson's message of 2015-05-01 09:06:20 -0700:
So this is an interesting idea. Would we require operators co-author/review
all patches that land? if not (and that actually strikes me as making
uploading patches more difficult unnecessarily), My question is how
Operators can
Hi Cathy,
Thanks for the information.
Waiting for the invite.
Thanks
Swami
From: Cathy Zhang [mailto:cathy.h.zh...@huawei.com]
Sent: Thursday, April 30, 2015 6:17 PM
To: adolfo.duar...@hp.com; Vikram Choudhary; Isaku Yamahata; Yamahata, Isaku;
Vasudevan, Swaminathan (PNB Roseville); Anand,
Hello everyone,
Some of you have reached out to me asking questions about when we will start
meeting discussion on the service chaining feature BPs in OpenStack.
I have set up agoto meeting for an audio meeting discussion so that we can
sync up thought and bring everyone on the same page in a
So this is an interesting idea. Would we require operators co-author/review
all patches that land? if not (and that actually strikes me as making
uploading patches more difficult unnecessarily), My question is how
Operators can easily get involved with that process.
If Operators want to get
Excerpts from Robert Collins's message of 2015-05-01 10:59:49 +1200:
pbr 0.11 is finally released (now that Kilo is out :).
This brings in more support to ensure that our version numbers are
monotonically increasing.
Mostly this should be unintrusive (but please do read the docs -
+1
--Adam
https://keybase.io/rm_you
From: Doug Wiegley
doug...@parksidesoftware.commailto:doug...@parksidesoftware.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Friday, May 1, 2015 at
Same is true of network shares. If its already listed in fstab, it will just
work. But an admin's got to manually add it there. My point is automation is
not supported in cinder either?
Thanks,
Kevin
From: Ben Swartzlander [b...@swartzlander.org]
Sent: Friday,
The subnet_id on the pool specifies what networks to plug when everything is
first configured.Iif you add a member to the pool that is outside this subnet,
there may not be a route to it, since it is probably on a different network
that is not correctly plugged on the LB host. (I hope this is
On Friday, May 1, 2015, Russell Bryant rbry...@redhat.com wrote:
On 05/01/2015 02:22 PM, Tim Bell wrote:
The spec review process has made it much easier for operators to see
what is being proposed and give input.
Recognition is a different topic. It also comes into who would be the
On Wed, Apr 29, 2015 at 8:00 PM, Jay Pipes jaypi...@gmail.com wrote:
On 04/29/2015 03:41 PM, Ed Leafe wrote:
On Apr 29, 2015, at 2:30 PM, Matt Riedemann
mrie...@linux.vnet.ibm.com wrote:
I'd prefer to see the scheduler filter docs be maintained in the
nova devref where they are close to
On 05/01/2015 09:32 AM, Fox, Kevin M wrote:
Hmm The cinder volumes dont automount either. /dev/vdx shows up,
but you have to format/mount it yourself.
Maybe both teams could share a common solution? Im guessing it will
have to be an agent...
That not really true. If the volume is
The spec review process has made it much easier for operators to see what is
being proposed and give input.
Recognition is a different topic. It also comes into who would be the
operator/user electorate ? ATC is simple to define where the equivalent
operator/user definition is less clear.
Hi everyone!
I'm happy to announce that (due to overwhelming demand from the development
team) Keystone will be holding a MidCycle meetup for Liberty.
In an effort to get ahead of the curve and ensure everyone has time to put in
for travel arrangements, I am sending out the preliminary
On 05/01/2015 02:22 PM, Tim Bell wrote:
The spec review process has made it much easier for operators to see
what is being proposed and give input.
Recognition is a different topic. It also comes into who would be the
operator/user electorate ? ATC is simple to define where the equivalent
On 2 May 2015 at 04:17, Doug Hellmann d...@doughellmann.com wrote:
Excerpts from Robert Collins's message of 2015-05-01 10:59:49 +1200:
pbr 0.11 is finally released (now that Kilo is out :).
This brings in more support to ensure that our version numbers are
monotonically increasing.
Mostly
On 04/30/15 16:40, Jay Pipes wrote:
On 04/30/2015 09:26 AM, David Medberry wrote:
Hey guys,
Congrats to the new TC leaders.
http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_ef1379fee7b94688
Please reach out to me (and openstack-operat...@lists.openstack.org
On Apr 30, 2015, at 9:54 AM, Jay Pipes jaypi...@gmail.com wrote:
Hi Stackers,
OK, so Matthew Gilliard and Alex Xu have volunteered to be the Nova team's
liaisons to the API working group. Big thank you to Matthew and Alex for
volunteering for this important role.
I've created a wiki
All 3 API guidelines have merged. Thanks everyone!
Everett
On Apr 22, 2015, at 2:08 PM, Everett Toews everett.to...@rackspace.com wrote:
Hi All,
We have 3 API Guidelines that are ready for a final review.
1. Metadata guidelines document
https://review.openstack.org/#/c/141229/
2.
I purposely didn't email the general mailing list since I didn't want to
cross-post, hard to have these discussions across verticals and choosing
one list = hearing one community - those subscribed to the developer
mailing list.
So I'm not assuming anything, it seems some are suggesting that
Hi,
In case you were unable to make yesterday's Nova meeting...
If you have a suggestion for a Nova design summit session, please
ensure you add it to before the next Nova meeting (7th May):
https://etherpad.openstack.org/p/liberty-nova-summit-ideas
Shortly after that Nova meeting, the (mostly)
On 05/01/2015 12:54 AM, Deepak Shetty wrote:
Hi,
Have we considered cloud-init and qemu guest agent, I remember there
was some discussion around this
in the prev summit, but i couldn't find any etherpad/notes on that.
I had one more question in this regards. Is it possible to do some
kind
Hi,
Just a quick reminder that blueprints and nova-specs need to be
approved for liberty, even if they have already been approved for a
previous release.
I added deadline in the subject mostly just to get your attention. We
haven't agreed a deadline for spec and blueprint submissions yet, but
+1 :)
2015-04-30 20:30 GMT+09:00 John Garbutt j...@johngarbutt.com:
Hi,
I propose we add Melanie to nova-core.
She has been consistently doing great quality code reviews[1],
alongside a wide array of other really valuable contributions to the
Nova project.
Please respond with comments,
Hi All,
Thank you for adding me to this team.
It will be my pleasure to work with you all together.
Till now, everyone has helped me in many or some way.
Thank you for all the support and this honor.
Looking forward for contributing more.
Thanks Regards
Madhuri Kumari
On Fri, May 1, 2015
Hmm The cinder volumes dont automount either. /dev/vdx shows up, but you
have to format/mount it yourself.
Maybe both teams could share a common solution? Im guessing it will have to be
an agent...
Thanks,
Kevin
From: Deepak Shetty
Sent: Thursday, April
45 matches
Mail list logo
