Hi,
Quantum security groups works with IP overlapping environment and I believe
Grizzly Quantum truely supports IP overlapping. For example, the iptables
based implementation takes into account the interface name in addition to
IP addresses, so it works with overlapping IP.
One thing to be noted
penstack.org/settings
>
> Gerrit-MessageType: newpatchset
> Gerrit-Change-Id: I7826087147e0713edaaea85a72283998295e2281
> Gerrit-PatchSet: 3
> Gerrit-Project: openstack/quantum
> Gerrit-Branch: master
> Gerrit-Owner: Mark McLoughlin
> Gerrit-Reviewer: Akihiro Motoki
>
Hi,
> Date: Wed, 22 May 2013 13:04:13 +0800
> From: gong yong sheng
> Subject: [Quantum-core] lower case config group name
>
> hi zhongyue,
>
> when the oslo.config will be compatible?
> https://bugs.launchpad.net/quantum/+bug/1182662
>
> the lower case group name is introduced by:
I will go.
Spirit-of-77 seem to have enough space.
Two parties on OpenStack summit schedule will be held there.
Akihiro
> Date: Sat, 13 Apr 2013 20:40:59 -0700
> From: Dan Wendlandt
> Subject: [Quantum-core] quantum beer bash sunday @ 8pm
>
> Hi folks,
>
> The area around the conv
;
> Hi Akihiro,
>
> I also noticed this a few days back and filed this
> https://bugs.launchpad.net/nova/+bug/
> 1160560 , the patch https://review.openstack.org/#/c/25563/ merged last
> night that fixes this
> issue.
>
> Thanks,
>
> Aa
Hi,
I found the bug that vm launch with port-id does not work.
https://bugs.launchpad.net/nova/+bug/1161211
The patch for nova is available at https://review.openstack.org/#/c/25594/
It is worth fixing it before Grizzly release.
Could you ask nova-core to check it?
Thanks,
Akihiro
--
Mailing l
Hi Gabriel,
(cc: quantum-core)
I summarize the current status of Horizon Quantum-realted topic.
There are several number of fixes/improvements are proposed.
Qunatum related bugs: https://bugs.launchpad.net/horizon/+bugs?field.tag=quantum
- The most important one for RC1 is https://review.opensta
Thanks for releasing.
Good point. Why not >=2.2.0,<3.0.0?
Of cource I don't think we have quantumclient 2.9.10 :-)
On launchpad I noticed 2.2.1 milestone is created.
Are there any guidelines for 2.2.1 and 3.0.0?
I think small fixes in 2.0 series should be targeted to 2.2.1 and
others should go to
Hi,
I added how to run Horizon LBaaS to the wiki.
https://wiki.openstack.org/wiki/Quantum/LBaaS/HowToRun
Is it better to post the dev ML?
Thanks,
Akihiro
--
Mailing list: https://launchpad.net/~quantum-core
Post to : quantum-core@lists.launchpad.net
Unsubscribe : https://launchpad.net/~qu
Hi,
> I wanted to draw attention to my comments on this review, since several of
> you aren't on there ( https://review.openstack.org/#/c/23360/). From
> comments, it seems that the OVS plugin will fail if it is run with an
> agent not configured with the "state-report" flag.
I totally agree wit
Hi,
In the review https://review.openstack.org/#/c/21924/,
we are dropping external_id column from the securitygroups table.
In my understanding, db migration is prepared to migrate from the previous
release to the new release (from Folsom to Grizzly at the moment).
I am wondering which is better
Sorry. I sent the wrong link.
https://review.openstack.org/#/c/22405/
>>>>> Date: Wed, 20 Feb 2013 17:30:50 +0900
>>>>> From: Akihiro MOTOKI
>>>>> Subject: Re: [Quantum-core] branches on db migration scripts
>
> Hi,
>
> I uploaded the pa
t;>> From: Dan Wendlandt
>>>>> Subject: Re: [Quantum-core] branches on db migration scripts
>
> Sounds good. Mark, I'm fine if this commit happens after the G-3 branch
> deadline tomorrow night,
> as we can always cherry-pick individual commits.
>
with this, even if fixing the migration script is something
which will the require the reviewers just to rubberstamp the patches.
We can start filing a bug with critical or high priority and ensure it
targets G-3.
Salvatore
On 18 February 2013 14:01, Akihiro MOTOKI wrote:
Hi,
Several patches cont
Hi,
Several patches contains db migration scripts and now we are merging several
patches.
It leads to branches in db migration scripts. In a usual process, we need to
rebase
the patch to catch up the latest, but it forces us to do another review and
approval.
How about having a special rule th
antum-core] Move auth_token configurations to
>>>>> quantum.conf,
>
> Thanks for the clarification.
>
> On 02/13/2013 08:56 AM, Akihiro MOTOKI wrote:
> > We alerady decided not to backport it. I would like to share the detail.
> >
> > Actually auth_token configura
We alerady decided not to backport it. I would like to share the detail.
Actually auth_token configuration in quantum.conf does not work in stable/folsom
and we cannot backport it. In Folsom, keystone provides auth_token middleware
and this middle does not check the configurations in quantum.con
>>>>> Date: Mon, 11 Feb 2013 17:02:11 +0200
>>>>> From: Gary Kotton
>>>>> Subject: Re: [Quantum-core] Move auth_token configuration to
>>>>> quantum.conffrom api-paste
>
> On 02/11/2013 04:46 PM, Akihiro MOTOKI wrote:
> >
least with the high-level goal of simplifying configuration to
> avoid most users having
> to deal with api-paste.ini, so long as backward compat is properly handled.
> Thanks for working on
> this.
>
> Dan
>
> On Sat, Feb 9, 2013 at 6:09 AM, Akihiro
Hi,
We have the configurations of keystone auth_token in api-paste.ini.
keystoneclient.middleware.auth_token now allows the main application
such as quantum to have auth_token configuration in its configuration
file e.g., quantum.conf.
I think it is better to have auth_token configurations in qua
Hi Gary, Paul,
> Date: Mon, 28 Jan 2013 13:57:35 +0200
> From: Gary Kotton
> Subject: Re: [Quantum-core] https://review.openstack.org/#/c/19649/
>
> On 01/28/2013 01:55 PM, Paul Michali wrote:
> > On Jan 28, 2013, at 2:20 AM, Gary Kotton wrote:
> >
> >> Hi,
> >> It has come to my att
lation) that we could explore if desirable, though
> I would much prefer
> that we are able to converge on using a single namespace-based design that
> does not require extra
> bagge for isolation.
>
> Dan
>
> On Fri, Jan 11, 2013 at 6:24 AM, Gary Kotton wrote:
>
>
Hi guys,
I had quite a bad cold was absent from last Thurday,
so I was forced to skip review days on last Friday and this Monday.
Now getting better (not perfectly :-( )
and I am catching up mails and reviews.
Thanks,
Akihiro
--
Mailing list: https://launchpad.net/~quantum-core
Post to : qu
Hi,
There are several patches posted which requires db migrations.
When I created a db migration script Mark helps me.
I believe it is worth sharing db migration procedure before documented.
I pasted the procedure in the Wiki.
http://wiki.openstack.org/Quantum/DatabaseMigration
Thanks,
Akihiro
Hi Aaron,
>>>>> Date: Tue, 15 Jan 2013 00:40:13 -0800
>>>>> From: Aaron Rosen
>>>>> Subject: Re: [Quantum-core] [openstack-dev] Proposed Quantum Port
>>>>> SecurityAPI/Blueprint
>
> In line
>
> On Mon, Jan 14, 2013 at 5
.
> > It's not possible to support port security on a
> > port for only one ipaddress and not the other because of the reason i
> > mentioned previously. The user could create another port with out port
> > security though.
Thanks,
Akihiro
>
; https://docs.google.com/document/d/18trYtq3wb0eJK2CapktN415FRIVasr7UkTpWn9mLq5M/edit
>
> Thanks,
>
> Aaron
>
> ___
> OpenStack-dev mailing list
> openstack-...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinf
Hi folks,
I have noticed that there is a case two subnets not connected
each other via a router can communicate each other
by changing default gateway to the IP address of the DHCP servers
in a setup where l3-agent and dhcp-agent run on a same host without namespace.
A simple solution to avoid it
Hi,
I updated ReviewDays page.
http://wiki.openstack.org/Quantum/ReviewDays
The current assigned reviewer is temporary.
I just copied coredevs with * mark (or assigned on same day more than three
times)
Please update it.
I added "Weekly Defaults" rows at the bottom of the table
to make it easie
stick around a
> couple minutes after
> the project meeting to chat about Horizon + Quantum during the Horizon
> meeting that$B!G(Bd be awesome.
>
> Thanks!
>
> - Gabriel
>
> From: Dan Wendlandt [mailto:d...@nicira.com]
> Sent: Tuesday, December 11, 2012 1:10 PM
>
Hi,
I posted a patch for quantumclient: https://review.openstack.org/#/c/17345/
During the review a question is raised whether we need to support underscore
style (xxx_yyy) for new options?
I think it is good to share this and make some consensus among the core devs.
Previously we use underscore
Hi,
Thanks for updating.
(2012/11/27 19:31), Gary Kotton wrote:
Hi,
We have the following:
Stable pending review:
- https://review.openstack.org/#/c/16961/ (bug 1083387) [added this
morning]
- https://review.openstack.org/#/c/16223/ (bug 1078210) [Enables Nova to
create the bridge
t;>> Date: Sun, 25 Nov 2012 12:06:03 -0800
>>>>> From: Dan Wendlandt
>>>>> Subject: Re: Horizon Quantum related BPs for Grizzly
>
> On Sun, Nov 25, 2012 at 8:31 AM, Akihiro MOTOKI wrote:
>
> Hi Dan, Gabriel,
>
> Sorry for no actio
>>>>> Date: Mon, 19 Nov 2012 13:36:19 +0200
>>>>> From: Gary Kotton
>>>>> Subject: Re: [Quantum-core] G-1 review status
>
> On 11/19/2012 01:07 PM, Akihiro MOTOKI wrote:
> >> I was also reviewing the metadata patch, but it seems there
> I was also reviewing the metadata patch, but it seems there are plenty of
> core devs on it.
> So I will move to the iptables security group
> patch, https://review.openstack.org/#/c/16210/,
> where Gary is the only core at the moment.
I am also reviewing iptables security group patch.
I crea
t_id (+ sometimes port_id).
If we want to know more detail, port-show (or router-port-list) can be used.
This is just my preference.
I also understand selecting some field to be displayed needs more logic
and requires additional changes if router resources is changed in future.
--
Akihiro MOTO
uot; section
Thanks,
Akihiro Motoki
(2012/09/28 2:11), Dan Wendlandt wrote:
On Thu, Sep 27, 2012 at 7:29 AM, Akihiro MOTOKI wrote:
Hi,
- Advanced Config Options - L3 Agent: (no owner yet... any volunteers?).
I am trying to add descriptions related to namespace (as I said in the last
IRC mee
Hi,
> - Advanced Config Options - L3 Agent: (no owner yet... any volunteers?).
I am trying to add descriptions related to namespace (as I said in the last IRC
meeting).
This requires adding config options of L3 agent, so I will take it.
Regarding namespace, we need to add additional descripti
38 matches
Mail list logo
