Hi
There are 2 fields in the L7 model that are candidates for being a closed set
(Enum).
I would like to hear your opinion.
Entity: L7Rule
Field : type
Description: this field holds the part of the request where we should look for
a value
Possible values: URL,HEADER,BODY,(?)
Entity: L7Rule
It seems this work item is made of several blueprints, some of which are
not yet approved. This is true at least for the Neutron blueprint regarding
policy extensions.
Since I first looked at this spec I've been wondering why nova has been
selected as an endpoint for network operations rather
On 16 February 2014 17:57, Jay Pipes jaypi...@gmail.com wrote:
Personally, I believe having Gerrit and Jenkins as the default will turn
more people off Solumn than attract them to it.
Just because we in the OpenStack community love our gating workflow and
think it's all groovy does not mean
On 15 February 2014 12:15, Dirk Müller d...@dmllr.de wrote:
I agree, and changing defaults has a cost as well: Every deployment
solution out there has to detect the value change, update their config
templates and potentially also migrate the setting from the old to the
new default for
On Feb 16, 2014, at 2:31 AM, Robert Collins robe...@robertcollins.net
wrote:
On 16 February 2014 17:57, Jay Pipes jaypi...@gmail.com wrote:
Personally, I believe having Gerrit and Jenkins as the default will turn
more people off Solumn than attract them to it.
Just because we in the
(removing extra space from the subject - let email clients apply their filters)
From: Avishay Balderman
Sent: Sunday, February 16, 2014 9:56 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [Neutron][LBaaS] L7 data types
Hi
There are 2 fields in the L7
Hi stackers:
I found that when creating network subnet and other resources, the attribute
tenant_id
can be set by admin tenant. But we did not verify that if the tanent_id is real
in keystone.
I know that we could use neutron without keystone, but do you think tenant_id
should
be verified
Thanks Gary, clear now. ;-)
2014-02-16 21:40 GMT+08:00 Gary Kotton gkot...@vmware.com:
Hi,
There are two issues here.
The first is a bug fix that is in review:
- https://review.openstack.org/#/c/69209/ (this is where they have the
same configuration)
The second is WIP:
-
During the last IRC call we started talking about network services and how
they can be integrated into the group Policy framework.
In particular, with the redirect action we need to think how we can
specify the network services we want to redirect the traffic to/from. There
has been a
Hi Gary,
One more question, when using VCDriver, I can use it in the following two
ways:
1) start up many nova computes and those nova computes manage same vcenter
clusters.
2) start up many nova computes and those nova computes manage different
vcenter clusters.
Do we have some best practice
Yes, [1] can be done without [2] and [3].
As you are well aware [2] is now merged with group policy discussions.
IMHO all or nothing approach will not get us anywhere.
By the time we line up all our ducks in row. New features/ideas/blueprints
will keep Emerging.
Regards
-Harshad
On Feb 16,
Comments Inline
Regards
-Harshad
On Sat, Feb 15, 2014 at 11:39 PM, Allamaraju, Subbu su...@subbu.org wrote:
Harshad,
Curious to know if there is a broad interest in an AWS compatible API in
the community?
We started looking at this as some our customers/partners were interested
in get
Harshad,
Thanks for clarifying.
We started looking at this as some our customers/partners were interested in
get AWS API compatibility. We have this blueprint and code review pending for
long time now. We will know based on this thread wether the community is
interested. But I assumed
IMHO I don't see two implementations. Since right now we have only
one. As a community if we decide to add new abstractions then we will
have to change software in every component where the new abstraction
makes difference. That's normal software development process.
Regards
-Harshad
On Feb 16,
Harshad,
I tried to find some discussion around this blueprint.
Could you provide us with some notes or threads ?
Also, about the code review you mention. which one are you talking about :
https://review.openstack.org/#/c/40071/
https://review.openstack.org/#/c/49470/
Harshad,
This is great. At least there is consensus on what it is and what it is not. I
would leave it to others to discuss merits of a an AWS compat VPC API for
Icehouse.
Perhaps this is a good topic to discuss at the Juno design summit.
Subbu
On Feb 16, 2014, at 10:15 AM, Harshad Nakil
On 15 February 2014 09:58, Sean Dague s...@dague.net wrote:
Lastly, I'm going to propose a merge to infra/config to put our
undercloud story (which exercises the seed's ability to deploy via
heat with bare metal) as a check experimental job on our dependencies
(keystone, glance, nova,
On 15 February 2014 12:21, James E. Blair jebl...@openstack.org wrote:
You won't end up with -1's everywhere, you'll end up with jobs stuck in
the queue indefinitely, as we saw when the tripleo cloud failed
recently. What's worse is that now that positive check results are
required for
I agree with JC that we need to pause and discuss VPC model with in
openstack before considering AWS compatibility. As Subbu said, We need this
discussion in Juno summit and get consensus.
Thanks,
-Ravi.
On Sun, Feb 16, 2014 at 10:31 AM, Allamaraju, Subbu su...@subbu.org wrote:
Harshad,
IMO, VPC means to have managed set of resources not just limited to
networks but also projects.
I feel its not about incrementally starting with AWS compatibility, But
doing it right with AWS compatibility into consideration.
Thanks,
-Ravi.
On Sun, Feb 16, 2014 at 8:47 AM, Harshad Nakil
On Feb 15, 2014, at 4:36 AM, Vinod Kumar Boppanna
vinod.kumar.boppa...@cern.ch wrote:
Dear Vish,
I completely agree with you. Its like a trade off between getting
re-authenticated (when in a hierarchy user has different roles at different
levels) or parsing the entire hierarchy till
Hey;
I'm trying to get the l3 metering agent included in Neutron to do...
something, and I suspect that I'm doing something terribly wrong.
I'm looking at the docs on
https://wiki.openstack.org/wiki/Neutron/Metering/Bandwidth
and trying to run it on Devstack (yes, I know), and I was wondering
On 17 February 2014 10:20, Mike Spreitzer mspre...@us.ibm.com wrote:
Kevin, I changed no code, it was a fresh DevStack install.
Thanks Robert, I tried following your leads but got nowhere, perhaps I need
a few more clues.
I am not familiar with bzr (nor baz), and it wasn't obvious to me how
Hi Mike,
Looks like you have some syntax error for some accidental reason. Could you
please do the following:
0) install flake8;
1) run ./run_tests.sh -p pep8.log into your Heat directory;
2) Attach to the letter and send it to the list.
Thank you,
Alexander
2014-02-17 1:20 GMT+04:00 Mike
keystoneclient.middlware.auth_token passes a project ID (and name, for
convenience) to the underlying application through the WSGI environment,
and already ensures that this value can not be manipulated by the end user.
Project ID's (redundantly) passed through other means, such as URLs, are up
On 15 February 2014 16:52, Soren Hansen so...@linux2go.dk wrote:
Den 15/02/2014 00.19 skrev Adam Young ayo...@redhat.com:
Could you please spend 5 minutes on the blueprint
https://blueprints.launchpad.net/horizon/+spec/user-registration and add
your suggestions in the white board.
Does it
Robert Collins robe...@robertcollins.net wrote on 02/16/2014 05:26:50
PM:
I would have expected run_tests.sh to tox which creates a venv, but
heat seems different. So you'll need to install testrepository via
your system tox, not one from a venv.
I don't think I have a system tox. `pip list
On 17 February 2014 13:50, Mike Spreitzer mspre...@us.ibm.com wrote:
Robert Collins robe...@robertcollins.net wrote on 02/16/2014 05:26:50 PM:
I would have expected run_tests.sh to tox which creates a venv, but
heat seems different. So you'll need to install testrepository via
your system
Hi!
The nascent tripleo-gate is now running on all tripleo repositories,
*and should pass*, but are not yet voting. They aren't voting because
we cannot submit to the gate unless jenkins votes verified... *and* we
have no redundancy for the tripleo-ci cloud now, so any glitch in the
current
Hi Carlos,
We have just started looking at the same issues you have mentioned. Please
follow the email thread started by me earlier today ([openstack-dev]
[neutron][policy] Using network services with network policies). We will be
spending more time on these topics during our upcoming weekly IRC
Hi sahid,
I have tested `scp -l xxx src dst` (local scp copy) and believe that the `-l`
option is invalid in this situation,
it seems that `-l` only valid in remote copy.
2014-02-17
Wangpan
发件人:sahid sahid.ferdja...@cloudwatt.com
发送时间:2014-02-14 17:58
主题:Re: [openstack-dev] [nova] Should
Hi yunhong,
I agree with you of the taking I/O bandwidth as a resource, but it may be not
so easy to implement.
Your another thinking about the launch time may be not so terrible, only the
first boot it will be affected.
2014-02-17
Wangpan
发件人:yunhong jiang yunhong.ji...@linux.intel.com
On Sun, Feb 16, 2014 at 3:26 AM, Salvatore Orlando sorla...@nicira.com wrote:
It seems this work item is made of several blueprints, some of which are not
yet approved. This is true at least for the Neutron blueprint regarding
policy extensions.
Since I first looked at this spec I've been
https://bugs.launchpad.net/neutron/+bug/1280941
I haven't done a chapter-and-verse trace of what happened, but it
looks like a latent bug in the neutronclient lib was tickled by some
neutron change, fixed in neutronclient, and then neutron started using
the feature without bumping
+1
On Feb 13, 2014 5:52 PM, Nachi Ueno na...@ntti3.com wrote:
+1
2014年2月12日水曜日、Mayur Patilram.nath241...@gmail.comさんは書きました:
+1
*--*
*Cheers,*
*Mayur*
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
Trovesters,
One reason for the longer running test was that for the configuration
groups i added a creation of a new instance. This is to test a new instance
will be created with a configuration group applied. This might be causing
the run to be a little longer but i am surprised that its taking
I'd like to make it sure.
The followings pages seems still have old time.
Which is correct? 1700UTC or 1900UTC Thursday?
https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy
https://wiki.openstack.org/wiki/Meetings#Neutron_Group_Policy_Sub-Team_Meeting
Thanks,
On Tue, Feb 11, 2014 at
On Thu, 2014-02-13 at 19:35 -0700, Christopher Yeoh wrote:
On Thu, 13 Feb 2014 21:10:01 -0500
Sean Dague s...@dague.net wrote:
On 02/13/2014 08:28 PM, Christopher Yeoh wrote:
On Thu, 13 Feb 2014 15:54:23 -0500
Sean Dague s...@dague.net wrote:
So one question I have around a
On 15 Feb 2014, at 04:01, Nikolay Makhotkin nmakhot...@mirantis.com wrote:
Dmitri, in our concerns under word 'input' we assume a block contains the
info about how the input data will be taken for corresponding task from
initial context. So, it will be a kind of expression (e.g. YAQL).
Dmitri,
Right now https://etherpad.openstack.org/p/mistral-poc is the only place where
we described it. It shouldn’t be considered a specification, it was rather a
playground where we tried to shape up our ideas. We’ll fix it using our latest
ideas and changes captured in the code and create
Hi John,
I have made the changes you suggested.
And, yes, we've tested this out in a live system.
On Fri, Feb 14, 2014 at 1:43 AM, John Garbutt
john.garb...@rackspace.co.ukwrote:
Its too late for this cycle. We will have to wait until Juno for any
blueprints.
On Thu, 2014-02-13 at 08:45 -0600, Dean Troyer wrote:
FWIW, an early proposal to address this, as well as capability
discovery, still lives
at https://etherpad.openstack.org/p/api-version-discovery-proposal.
I've lost track of where this went, and even which design summit this
is from, but
Hi All,
I'm just curious on how the manager.py is choosing backend while creating
volume, I know volume type is set but where is this being processed?
I am sorry if this is a basic question, but didn't got any help from
#openstack-dev IRC channel so was left without option to post here.
--
On Thu, 2014-02-13 at 08:37 -0500, Sean Dague wrote:
On 02/13/2014 07:50 AM, Jamie Lennox wrote:
Hi all,
I am one of i think a number of efforts trying to make clients be
interoperable between different versions of an API.
What i would like to talk about specifically here are the
I think you should look at the cinder scheduler code that selects a host
based on the volume type.
https://github.com/openstack/cinder/tree/master/cinder/scheduler.
BTW, cinder dev tend to hang out on #openstack-cinder channel.
Thanks,
Subbu
On Mon, Feb 17, 2014 at 11:35 AM, iKhan
Hello,
In current PCI passthrough implementation, a pci device is only allowed to be
assigned to a instance while the instance is being created, it is not allowed
to be assigned or removed from the instance while the instance is running or
stop.
Besides, I noticed that the basic
Hi,
I'm looking for few reviews on *use-bufferedhttp-in-swiftclient
https://blueprints.launchpad.net/python-swiftclient/+spec/use-bufferedhttp-in-swiftclient*
and
use-expect-100-continue-header-while-uploadinghttps://blueprints.launchpad.net/python-swiftclient/+spec/should-use-100-continue-header
Hi, Apologies for chiming in late on this. Yes, we have been
incubating the service insertion and chaining features [2] for some
time now. The plan was to have a FW-VPN chain working by Icehouse
release. Towards that end the first step was to introduce the notion
of a service insertion context
Thanks Mohammad for bringing this up. I responded in another thread:
http://lists.openstack.org/pipermail/openstack-dev/2014-February/027306.html
~Sumit.
On Sun, Feb 16, 2014 at 7:27 AM, Mohammad Banikazemi m...@us.ibm.com wrote:
During the last IRC call we started talking about network
Hi,
I would add another candidate for being a closed set:
L7VipPolicyAssociation.action (use_backend, block, etc.)
Thanks,
Oleg
On Sun, Feb 16, 2014 at 3:53 PM, Avishay Balderman avish...@radware.comwrote:
(removing extra space from the subject - let email clients apply their
filters)
Hi, Craig.
Yes, i thought about configurations test suits.
For now core team, maybe, should extend gate running time.
But for the tempest tests i would suggest to exclude some tests from
'gate'-group (the longest ones).
We need to deal with it asap, because gate failing for four or five days.
Clint,
We're collaborating with Murano. We may need to do it in a way that others
could see it though. There are several things here:
Murano doesn’t really have a “workflow engine” similar to Mistral’s. People get
confused with that but it’s just a legacy terminology, I think Murano folks
On Mon, 2014-02-17 at 16:09 +1000, Jamie Lennox wrote:
On Thu, 2014-02-13 at 08:37 -0500, Sean Dague wrote:
On 02/13/2014 07:50 AM, Jamie Lennox wrote:
Hi all,
I am one of i think a number of efforts trying to make clients be
interoperable between different versions of an API.
Hi,
This is a reminder that we’ll have an IRC community meeting today at
#openstack-meeting at 16.00 UTC.
Here’s the agenda:
Review action items
Discuss current status
Continue DSL discussion
Open discussion (roadblocks, suggestions, etc.)
Please let us know if you have other topics to
54 matches
Mail list logo