If these are just feature branches and they aren't intended to be
deployed for long life cycles, why don't we just skip the db migration
and enable auto-schema generation inside of the feature branch? Then a
migration can be created once it's time to actually merge into master.
On Tue, Sep 23,
On 09/22/2014 07:22 PM, Mark Washenberger wrote:
Greetings,
I will not be running for PTL for Glance for the Kilo release.
I want to thank all of the nice folks I've worked with--especially the
attendees and sponsors of the mid-cycle meetups, which I think were a
major success and one of
On 09/23/2014 11:03 PM, Doug Hellmann wrote:
James Carey (jecarey) from IBM has done the 3rd most reviews of oslo.i18n
this cycle [1]. His feedback has been useful, and I think he would be a good
addition to the team for maintaining oslo.i18n.
Let me know what you think, please.
Doug
On 09/23/2014 11:59 PM, Joe Gordon wrote:
On Tue, Sep 23, 2014 at 9:13 AM, Zane Bitter zbit...@redhat.com
mailto:zbit...@redhat.com wrote:
On 22/09/14 22:04, Joe Gordon wrote:
To me this is less about valid or invalid choices. The Zaqar team is
comparing Zaqar to
I think Joe's idea pretty sums it up, ASF model is definitely worth
following (Mesos is awesome). Non layer #1 projects will still be
shepherded but not that closely coupled to make OpenStack over-bloated.
Incubation projects can't be just dropped.
On Wed, Sep 24, 2014 at 2:46 AM, Joe Gordon
Hi Folks!
Please note that the IRC channel for the weekly Octavia meeting has changed
(see below)!
We've got the following agenda for tomorrow's Octavia meeting, so far:
- Review progress on action items from last week
- From blogan: Neutron lbaas v1 and v2 right now creates a neutron
On 24 September 2014 16:38, Jay Pipes jaypi...@gmail.com wrote:
On 09/23/2014 10:29 PM, Steven Dake wrote:
There is a deployment program - tripleo is just one implementation.
Nope, that is not correct. Like it or not (I personally don't), Triple-O is
*the* Deployment Program for OpenStack:
Excerpts from Jay Pipes's message of 2014-09-23 21:38:37 -0700:
On 09/23/2014 10:29 PM, Steven Dake wrote:
There is a deployment program - tripleo is just one implementation.
Nope, that is not correct. Like it or not (I personally don't), Triple-O
is *the* Deployment Program for OpenStack:
On 09/24/2014 03:48 AM, Devananda van der Veen wrote:
I've taken a bit of time out of this thread, and I'd like to jump back
in now and attempt to summarize what I've learned and hopefully frame
it in such a way that it helps us to answer the question Thierry
asked:
I *loved* it! Thanks a
I am writing to announce my candidacy for OpenStack Deployment PTL.
Those of you involved with the deployment program may be surprised to
see my name here. I've been quiet lately, distracted by an experiment
which was announced by Allison Randal a few months back. [1]
The experiment has been
Hi Mark,
Many thanks for your great work and leadership! Personally I have to
say thank you for your mentorship for me. Let's still keep in touch in
Glance/OpenStack.
zhiyan
On Tue, Sep 23, 2014 at 1:22 AM, Mark Washenberger
mark.washenber...@markwash.net wrote:
Greetings,
I will not be
On Wed, Sep 24, 2014 at 12:40 AM, Steven Dake sd...@redhat.com wrote:
I'm pleased to announce the development of a new project Kolla which is
Greek for glue :). Kolla has a goal of providing an implementation that
deploys OpenStack using Kubernetes and Docker. This project will begin as a
On 09/24/2014 12:06 AM, Joe Gordon wrote:
On Tue, Sep 23, 2014 at 2:40 AM, Flavio Percoco fla...@redhat.com
mailto:fla...@redhat.com wrote:
On 09/23/2014 05:13 AM, Clint Byrum wrote:
Excerpts from Joe Gordon's message of 2014-09-22 19:04:03 -0700:
[snip]
To
Hello,
Currently I am trying to use Trove services configured with devstack. The
services are configured and it has also created a default datastore for
MySQL image on ubuntu, but the launch instances always gets error polling
timeout I tried the same installation with redstack, created new image
On Wed, Sep 24, 2014 at 08:26:44AM +1000, Michael Still wrote:
On Tue, Sep 23, 2014 at 8:58 PM, Daniel P. Berrange berra...@redhat.com
wrote:
On Tue, Sep 23, 2014 at 02:27:52PM +0400, Roman Bogorodskiy wrote:
Michael Still wrote:
Hi.
I know we've been talking about deprecating
-Original Message-
From: Jay Pipes [mailto:jaypi...@gmail.com]
Sent: Wednesday, September 24, 2014 7:19 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Nova] [All] API standards working group
On 09/23/2014 05:03 PM, Rochelle.RochelleGrober wrote:
-Original Message-
From: Jay Pipes [mailto:jaypi...@gmail.com]
Sent: Wednesday, September 24, 2014 12:47 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Nova] Some ideas for micro-version
implementation
On 09/22/2014 04:27 PM, Brant Knudson wrote:
On
Relying again on automatic schema generation could be error-prone. It can
only be enabled globally, and does not work when models are altered if the
table for the model being altered already exists in the DB schema.
I don't think it would be a big problem to put these migrations in the main
Please keep me in the loop.
The importance of ensuring consistent style across Openstack APIs increases
as the number of integrated project increases.
Unless we decide to merge all API endpoints as proposed in another thread!
[1]
Regards,
Salvatore
[1]
Hi, all
I am just a little confused why alarm name should be unique per project,
anyone knows this?
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On 09/24/2014 12:23 PM, Long Suo wrote:
Hi, all
I am just a little confused why alarm name should be unique per project,
anyone knows this?
Good point, I admit I can't find a compelling reason for that either.
Perhaps someone else can?
Also, an interesting use-case comes to mind, where
TL;DR Is there any reason why stack-update doesn¹t reuse the existing
parameters when I extend my stack definition with a resource that uses
them?
I have created a stack from the hello_world.yaml template
(https://github.com/openstack/heat-templates/blob/master/hot/hello_world.ya
ml)
It has the
On 09/18/2014 02:53 PM, Monty Taylor wrote:
Hey all,
I've recently been thinking a lot about Sean's Layers stuff. So I wrote
a blog post which Jim Blair and Devananda were kind enough to help me edit.
http://inaugust.com/post/108
When I first read Monty's post, my basic reaction was yes,
On 24/09/14 13:50, Dimitri Mazmanov wrote:
TL;DR Is there any reason why stack-update doesn¹t reuse the existing
parameters when I extend my stack definition with a resource that uses
them?
Hey Dimitri,
There is an open bug for this feature:
https://bugs.launchpad.net/heat/+bug/1224828
and
I am writing to announce my candidacy for OpenStack Release Cycle
Management PTL.
This is a little-known program, so I'll take the bi-yearly opportunity
to explain what this covers:
1. Release Management
This is about coordinating the process that will turn the master
branches of the integrated
On 09/24/2014 05:26 AM, Kenichi Oomichi wrote:
-Original Message-
From: Jay Pipes [mailto:jaypi...@gmail.com]
Sent: Wednesday, September 24, 2014 12:47 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Nova] Some ideas for micro-version implementation
On 09/22/2014
Hello
I would like to be able to specify the UUID of an instance when I create
it. I found this discussion about this matter:
https://lists.launchpad.net/openstack/msg22387.html
but I could not find any blueprint, anyway I understood this
modification should not comport any particular issue.
On 23/09/14 17:59, Joe Gordon wrote:
Zaqar is aiming for low latency per message, SQS doesn't appear to be.
I've seen no evidence that Zaqar is actually aiming for that. There are
waaay lower-latency ways to implement messaging if you don't care about
durability (you wouldn't do
On 09/24/2014 03:57 AM, Clint Byrum wrote:
Excerpts from Jay Pipes's message of 2014-09-23 21:38:37 -0700:
On 09/23/2014 10:29 PM, Steven Dake wrote:
There is a deployment program - tripleo is just one implementation.
Nope, that is not correct. Like it or not (I personally don't), Triple-O
Swapnil,
If the default image being created by devstack gives you a timeout on launch, I
don’t think your issue is with the image itself.
Your best guide (for now) for creating a guest image is to follow the template
that devstack uses. I’m on the hook for writing some documentation on how to
On 23/09/14 19:29, Devananda van der Veen wrote:
On Mon, Sep 22, 2014 at 5:47 PM, Zane Bitter zbit...@redhat.com wrote:
On 22/09/14 17:06, Joe Gordon wrote:
If 50,000 messages per second doesn't count as small-to-moderate then
Zaqar
does not fulfill a major SQS use case.
It's not a drop-in
On Wed, Sep 24, 2014 at 9:16 AM, Jay Pipes jaypi...@gmail.com wrote:
On 09/24/2014 03:19 AM, Robert Collins wrote:
On 24 September 2014 16:38, Jay Pipes jaypi...@gmail.com wrote:
On 09/23/2014 10:29 PM, Steven Dake wrote:
There is a deployment program - tripleo is just one implementation.
On Wed, Sep 24, 2014 at 9:41 AM, James Slagle james.sla...@gmail.com wrote:
And it looks to me like what's being proposed here is that there is a
group of folks who intend to work on Knoll, and they are indicating
Oops, I meant Kolla, obviously :-).
--
-- James Slagle
--
I think we should aim to /always/ have 3 notifications using a pattern
of
try:
...notify start...
...do the work...
...notify end...
except:
...notify abort...
Precisely my viewpoint as well. Unless we standardize on the above, our
+1.
Or at least provide a way to specify an external UUID for the instance, and can
retrieve the instance through the external UUID which may be linked to external
system's object.
Chaoyi Huang ( joehuang )
发件人: Pasquale Porreca
On 09/24/2014 09:41 AM, James Slagle wrote:
On Wed, Sep 24, 2014 at 9:16 AM, Jay Pipes jaypi...@gmail.com wrote:
There are zero programs in the OpenStack governance repository that have
competing implementations for the same thing.
Like it or not, the TC process of blessing these teams has
On 09/24/2014 09:48 AM, Day, Phil wrote:
I think we should aim to /always/ have 3 notifications using a
pattern of
try: ...notify start...
...do the work...
...notify end... except: ...notify abort...
Precisely my viewpoint as well. Unless we standardize on the above,
our notifications are
Hi Amrith,
Thanks for the response.
I did check that, the instance is active and I can access it. Is there
anyway to check the guestagent in the image, update if its required and
create snapshot which can be used later?
Best Regards,
Swapnil Kulkarni
irc : coolsvap
On Wed, Sep 24, 2014 at 7:08
Apologies in advance for possible repetition and pedantry...
On 09/24/2014 02:48 AM, Devananda van der Veen wrote:
2. Single Delivery - each message must be processed *exactly* once
Example: Using a queue to process votes. Every vote must be counted only
once.
It is also important to
Ive had good luck recently enabling heat suppprt and then tweaking the trove
default template to use a standard image and install the guest agent at launch.
So no custom image needed.
Thanks,
Kevin
From: Swapnil Kulkarni
Sent: Wednesday, September 24, 2014
I'm interesting in the group too!
On 2014年09月24日 18:01, Salvatore Orlando wrote:
Please keep me in the loop.
The importance of ensuring consistent style across Openstack APIs
increases as the number of integrated project increases.
Unless we decide to merge all API endpoints as proposed in
It is an important topics towards good user experience.
There are many inconsistencies across projects and every API has pros and cons.
We need to share API best practices and it is nice.
I am interested in the topic both as Neutron developer and
from API consumer as Horizon developer.
If the
You can add me to this list as well.
Thanks!
Lance
On Wed, Sep 24, 2014 at 9:41 AM, Alex Xu x...@linux.vnet.ibm.com wrote:
I'm interesting in the group too!
On 2014年09月24日 18:01, Salvatore Orlando wrote:
Please keep me in the loop.
The importance of ensuring consistent style across
On 9/24/14, 9:51 AM, Lance Bragstad lbrags...@gmail.com wrote:
You can add me to this list as well.
Thanks!
Lance
On Wed, Sep 24, 2014 at 9:41 AM, Alex Xu
x...@linux.vnet.ibm.com wrote:
I'm interesting in the group too!
On 2014年09月24日 18:01, Salvatore Orlando wrote:
Please keep me
vNext seems an interesting idea, I thought the implementation way for Nova
a little. API Route Discoverability is a nice design, but a root / URL
will conflict on current list versions API.
Maybe there would be a workaround.
Completely agreed, Ken'ichi. The root URL that returns the
confirmed
On 24/09/14 08:56 AM, Thierry Carrez wrote:
I am writing to announce my candidacy for OpenStack Release Cycle
Management PTL.
This is a little-known program, so I'll take the bi-yearly opportunity
to explain what this covers:
1. Release Management
This is about coordinating
confirmed
On 24/09/14 04:03 AM, Clint Byrum wrote:
I am writing to announce my candidacy for OpenStack Deployment PTL.
Those of you involved with the deployment program may be surprised to
see my name here. I've been quiet lately, distracted by an experiment
which was announced by Allison
On Wed, Sep 24, 2014 at 10:03 AM, Jay Pipes jaypi...@gmail.com wrote:
On 09/24/2014 09:41 AM, James Slagle wrote:
Meaning: exactly what you seem to claim is not possible due to some
perceived blessing, is indeed in fact happening, or trying to come
about.
:) Talking about something on the
I am interested in participating as well.
Thanks,
Brad
Brad Topol, Ph.D.
IBM Distinguished Engineer
OpenStack
(919) 543-0646
Internet: bto...@us.ibm.com
Assistant: Kendra Witherspoon (919) 254-0680
From: Morgan Fainberg morgan.fainb...@gmail.com
To: Dolph Mathews
Hi,
The convergence spec is really big to be seen and understood in entirety
without going through multiple iterations. It is probably a good idea to
break the spec into multiple implementable specs and move a chunk of
material from main convergence spec to individual implementable specs
like
On Tue, 2014-09-23 at 18:18 -0400, Jay Pipes wrote:
Yes, I'd be willing to head up the working group... or at least
participate in it.
I'll raise my hand to participate…
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
___
OpenStack-dev
On 24-Sep-14 00:25, Joshua Harlow wrote:
I believe heat has its own dependency graph implementation but if that was
switched to networkx[1] that library has a bunch of nice read/write
capabilities.
See: https://github.com/networkx/networkx/tree/master/networkx/readwrite
And one made for
Hey Devs,
I just got clarification on what it was meant by 'commercial developer.' If
developer participates in commercial consulting, develops commercial per-order
customization / implementation for OpenStack (if any) – they are considered a
commercial developer.
As long as you do not meet
On Tue, Sep 23, 2014 at 5:18 PM, Jay Pipes jaypi...@gmail.com wrote:
Yes, I'd be willing to head up the working group... or at least
participate in it.
I'll bring an API consumer's perspective.
dt
--
Dean Troyer
dtro...@gmail.com
___
On 24/09/14 08:47, Tomas Sedovic wrote:
On 24/09/14 13:50, Dimitri Mazmanov wrote:
TL;DR Is there any reason why stack-update doesn¹t reuse the existing
parameters when I extend my stack definition with a resource that uses
them?
Hey Dimitri,
There is an open bug for this feature:
Le 24/09/2014 17:41, Andrew Melton a écrit :
Hey Devs,
I just got clarification on what it was meant by 'commercial
developer.' If developer participates in commercial consulting,
develops commercial per-order customization / implementation for
OpenStack (if any) – they are considered a
Hi all,
Thanks to those who attended today's meeting, please find links to the minutes
and log below:
Minutes:
http://eavesdrop.openstack.org/meetings/nfv/2014/nfv.2014-09-24-14.03.html
Minutes (text):
http://eavesdrop.openstack.org/meetings/nfv/2014/nfv.2014-09-24-14.03.txt
Log:
Hi Everyone,
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
this Thursday, September 25th at 17:00 UTC in the #openstack-meeting channel.
The agenda for tomorrow's meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome to
On Sep 24, 2014, at 9:42 AM, Dean Troyer dtro...@gmail.com wrote:
I'll bring an API consumer's perspective.
+1
I’d bring an API consumer’s perspective as well.
Looks like there’s lots of support for an API WG. What’s the next step?
Form a WG under the User Committee [1] or is there
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Neutron FWaaS rules lack port restrictions when using protocol 'any'
- ---
### Summary ###
A bug in the Neutron FWaaS (Firewall as a Service) code results in
iptables rules being generated that do not reflect desired port
restrictions. This behaviour
On Wed, Sep 24, 2014 at 11:42 AM, Dean Troyer dtro...@gmail.com wrote:
On Tue, Sep 23, 2014 at 5:18 PM, Jay Pipes jaypi...@gmail.com wrote:
Yes, I'd be willing to head up the working group... or at least
participate in it.
I'll bring an API consumer's perspective.
I would love to
On 09/24/2014 12:48 PM, Everett Toews wrote:
On Sep 24, 2014, at 9:42 AM, Dean Troyer dtro...@gmail.com wrote:
I'll bring an API consumer's perspective.
+1
I’d bring an API consumer’s perspective as well.
Looks like there’s lots of support for an API WG. What’s the next step?
Form a WG
Sorry for the vague subject[1]. I just wanted to commend Flavio Percoco
and the Zaqar team for maintaining poise and being excellent citizens
of OpenStack whilst being questioned intensely by the likes of me,
and others.
I feel that this questioning has been useful, and will allow us to reason
Sounds like an interesting project/goal and will be interesting to see where
this goes.
A few questions/comments:
How much golang will people be exposed to with this addition?
Seeing that this could be the first 'go' using project it will be interesting
to see where this goes (since afaik
Hi Sharan,
Yes, file bug, commit new image to review.
Thanks,
Andrew.
On Wed, Sep 24, 2014 at 10:16 AM, Sharan Kumar M
sharan.monikan...@gmail.com wrote:
Hi all,
In this documentation
http://docs.openstack.org/developer/sahara/overview.html#details, the
missing services were added. And I
On 09/24/2014 06:07 PM, Clint Byrum wrote:
I just wanted to commend Flavio Percoco and the Zaqar team for
maintaining poise and being excellent citizens of OpenStack whilst
being questioned intensely by the likes of me, and others.
+1
___
On 09/24/2014 07:07 PM, Clint Byrum wrote:
Sorry for the vague subject[1]. I just wanted to commend Flavio Percoco
and the Zaqar team for maintaining poise and being excellent citizens
of OpenStack whilst being questioned intensely by the likes of me,
and others.
And I'd personally like to
On 18/09/14 14:53, Monty Taylor wrote:
Hey all,
I've recently been thinking a lot about Sean's Layers stuff. So I wrote
a blog post which Jim Blair and Devananda were kind enough to help me edit.
http://inaugust.com/post/108
Thanks Monty, I think there are some very interesting ideas in
Seems like there is some overlap with the end user (i.e. consumer) working
group at https://wiki.openstack.org/wiki/End_User_Working_Group
Sounds like it would be worth discussing with them on how to focus on these
needs. The scope of the end user is much larger than just the API but a
@Nejc Saje
you're talking about group alarm, I'm going to try it on Kilo
On Wed, Sep 24, 2014 at 7:34 PM, Nejc Saje ns...@redhat.com wrote:
On 09/24/2014 12:23 PM, Long Suo wrote:
Hi, all
I am just a little confused why alarm name should be unique per project,
anyone knows this?
Good
Folks – we have gotten into a couple of loose habits in our mad dash to beta 1
that we need to tighten up on. I’ve asked Ryan to set geritt up to fail
reviews when the commit id does not contain one of the following, so please add
them to your commit. In addition please make your commit
Excerpts from Robert Collins's message of 2014-09-23 21:14:47 -0700:
No one helped me edit this :)
http://rbtcollins.wordpress.com/2014/09/24/what-poles-for-the-tent/
I hope I haven't zoned out and just channelled someone else here ;)
This sounds like API's are what matters. You did
SORRY – please ignore that email – it was clearly internal…… I used the wrong
ML (blush)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On 09/24/2014 10:05 AM, Jay Pipes wrote:
Whatever it ends up being, it needs to have some teeth to it. Otherwise,
we're going to end up in the exact same place we're in now, where each
project does something slightly different.
+1
I think getting started and produce some material to discuss
On 09/24/2014 02:51 PM, Tracy Jones wrote:
SORRY – please ignore that email – it was clearly internal…… I used the wrong
ML (blush)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
here are the updated fedora images, could we get them hosted at
sahara-files.mirantis.com please
https://mimccune.fedorapeople.org/sahara-juno-vanilla-1.2.1-fedora-20.qcow2
https://mimccune.fedorapeople.org/sahara-juno-vanilla-2.4.1-fedora-20.qcow2
md5sum
7e8a39bb4d43ebf07ceeaf66670d8726
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/19/2014 09:01 PM, Monty Taylor wrote:
except exc.Unauthorized:
raise exc.CommandError(Invalid OpenStack credentials.)
except exc.AuthorizationFailure:
raise exc.CommandError(Unable to authorize user)
On 19/09/14 22:37, Monty Taylor wrote:
I think we can do what you're saying and generalize a little bit. What
if we declared programs, as needed, when we think there is a need to
pick a winner. (I think we can all agree that early winner picking is
an unintended but very real side effect of the
On 09/24/2014 02:48 PM, Clint Byrum wrote:
Excerpts from Robert Collins's message of 2014-09-23 21:14:47 -0700:
No one helped me edit this :)
http://rbtcollins.wordpress.com/2014/09/24/what-poles-for-the-tent/
I hope I haven't zoned out and just channelled someone else here ;)
This sounds
Hi all,
In this bug https://bugs.launchpad.net/sahara/+bug/1371360 its said that
Cinder itself has replication and using it with HDFS will increase
replication even more. That said, will mentioning this in the documentation
and also stating that it makes sense to use Cinder when replication
On 2014-09-24 13:55:57 -0400 (-0400), Zane Bitter wrote:
[...]
* Assumption #2: Yawnoc's Law
Don't bother Googling that, I just made it up. It's the reverse of
Conway's Law:
Infra engineers who design governance structures for OpenStack
are constrained to produce designs that are
Hi,
I would like to discuss the documentation process and align it to OpenStack
flow.
At the moment we add special tags to bugs in Launchpad which is not optimal
as everyone can add/remove tags
cannot participate in documentation process or
enforce documentation process.
I suggest to switch to
Hi Joe,
Tools like Pumphouse [1] (migrates workloads, e.g. instances, between
two OpenStack clouds) would benefit from supporting this (Pumphouse
would be able to replicate user instances in a new cloud up to their
UUIDs).
Are there any known gotchas with support of this feature in REST APIs
(in
On Wed, Sep 24, 2014 at 2:58 PM, Roman Podoliaka rpodoly...@mirantis.com
wrote:
Are there any known gotchas with support of this feature in REST APIs
(in general)?
I'd be worried about relying on a user-defined attribute in that use case,
that's ripe for a DOS. Since these are cloud-unique I
confirmed
On 24/09/14 04:28 PM, Devananda van der Veen wrote:
Hi all,
I would like to announce my candidacy for the PTL role of the Bare Metal
Provisioning program.
I have been the PTL of Ironic since I began the project at the Havana summit,
and I am partly to blame for the baremetal
On Wed, Sep 24, 2014 at 11:05 AM, David Stanek dsta...@dstanek.com wrote:
On Wed, Sep 24, 2014 at 11:42 AM, Dean Troyer dtro...@gmail.com wrote:
On Tue, Sep 23, 2014 at 5:18 PM, Jay Pipes jaypi...@gmail.com wrote:
Yes, I'd be willing to head up the working group... or at least
participate
On Wed, Sep 24, 2014 at 12:18 AM, Jay Pipes jaypi...@gmail.com wrote:
Yes, I'd be willing to head up the working group... or at least
participate in it.
I am certainly interested, count me in.
Chmouel
___
OpenStack-dev mailing list
The Neutron L3 Subteam will meet tomorrow at the regular time and
place. The agenda and details are posted [1].
I think the RC1 ship will have sailed for most potential fixes by then
so I'd like to take some time during the meeting tomorrow to chat
about the work that is coming up for Kilo.
Yes, IIRC, these extra properties will be handled to lower case, see
https://github.com/openstack/glance/blob/master/glance/common/utils.py#L236
What's the nova bug you're talking about? Cheers.
On 24/09/14 16:21, Chen CH Ji wrote:
Got following result when doing bug analysis on nova , is
On 9/24/2014 3:17 PM, Dean Troyer wrote:
On Wed, Sep 24, 2014 at 2:58 PM, Roman Podoliaka
rpodoly...@mirantis.com mailto:rpodoly...@mirantis.com wrote:
Are there any known gotchas with support of this feature in REST APIs
(in general)?
I'd be worried about relying on a user-defined
I'd like to announce my candidacy for TripleO PTL.
I think most folks who have worked in the TripleO community probably know me.
For those who don't, I work for Red Hat, and over the last year and a half that
I've been involved with TripleO I've worked in different areas. My focus has
been on
Thanks Julie! It worked.
Actually I had different email address as a foundation member and for
gerrit account.
At last I could submit my first fix.
Sorry for the late reply.
And thank you very much once again for your help.
Thanks Regards,
Tahmina Ahmed
On Tue, Sep 23, 2014 at 7:19 PM, Julie
Hi folks,
We'll be having the Sahara team meeting as usual in
#openstack-meeting-alt channel.
Agenda: https://wiki.openstack.org/wiki/Meetings/SaharaAgenda#Next_meetings
http://www.timeanddate.com/worldclock/fixedtime.html?msg=Sahara+Meetingiso=20140925T18
--
Sincerely yours,
Sergey Lukjanov
Hi Adam,
For me the thing needs to be user friendly. So my main question is how do
things look in Horizon? Will there just be a popup saying Establish Trust
(Y/N). I am wondering as you how other teams are handling that...
Thanks,
German
-Original Message-
From: Adam Harwell
Excerpts from Steven Dake's message of 2014-09-23 15:40:29 -0700:
*Hi folks,***
*
I'm pleased to announce the development of a new project Kolla which is
Greek for glue :). Kolla has a goal of providing an implementation that
deploys OpenStack using Kubernetes and Docker. This project
Apparently I've mistakenly though that feature branch will form separate
optional component.
If it will eventually be a part of neutron - then it's fine.
Thanks,
Eugene.
On Wed, Sep 24, 2014 at 1:30 PM, Salvatore Orlando sorla...@nicira.com
wrote:
Relying again on automatic schema generation
Yeah, I was hoping for something like that... Essentially, Horizon would
need to detect that particular response and be prepared to make a simple
Yes/No dialog pop up to create that Trust, then continue with the original
operation again automatically afterwards. That said, I have not looked at
Steven
I have to ask what is the motivation and benefits we get from integrating
Kubernetes into Openstack? Would be really useful if you can elaborate and
outline some use cases and benefits Openstack and Kubernetes can gain.
/Alan
From: Steven Dake [mailto:sd...@redhat.com]
Sent:
Hi,
so, I'd really like to see https://review.openstack.org/#/c/121663/
merged in rc1. That patch is approved right now.
However, it depends on https://review.openstack.org/#/c/119521/, which
is not approved. 119521 fixes a problem where we make five RPC calls
per call to get_network_info, which
+1
From: Gordon Sim [g...@redhat.com]
Sent: Wednesday, September 24, 2014 10:26 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Zaqar] The horse is dead. Long live the horse.
On 09/24/2014 06:07 PM, Clint
1 - 100 of 129 matches
Mail list logo
