Hi,
I haven’t read through those (need to go spend time with family so replying
quickly) but given the dates the planning phases for Quantum/Neutron LBaaS
and Libra LBaaS were at the same time.
There was an internal evaluation of the current LBaaS solutions done at the
time and it was
On 01/19/2014 02:06 AM, Yair Fried wrote:
MT:Is your issue here that it's just called basic ops and you don't think
that's
reflective of what is being tested in that file anymore
No.
My issue is, that the current scenario is, in fact, at least 2 separate
scenarios:
1. original basic_ops
- Original Message -
From: Sean Dague s...@dague.net
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Sunday, January 19, 2014 1:53:21 PM
Subject: Re: [openstack-dev] [qa][Neutron][Tempest][Network] Break down
Diesel seems to be a subset of what Solum delivers.
For reference:
Solum Wiki: https://wiki.openstack.org/wiki/Solum
Solum Roadmap: https://wiki.openstack.org/wiki/Solum/HighLevelRoadmap
We should discuss combining efforts instead of duplicating initiatives.
On 01/16/2014 08:10 AM, Alexander Ignatov wrote:
Matthew,
I'm ok with proposed solution. Some comments/thoughts below:
-
FIX - @rest.post_file('/plugins/plugin_name/version/convert-config/name')
- this is an RPC call, made only by a client to do input validation,
move to POST
On 01/16/2014 09:19 PM, Andrey Lazarev wrote:
My 5 cents:
--
REMOVE - @rest.put('/node-group-templates/node_group_template_id') -
Not Implemented
REMOVE - @rest.put('/cluster-templates/cluster_template_id') - Not
Implemented
--
Disagree with that. Samsung people did great job in both
Excerpts from Thomas Herve's message of 2014-01-19 01:52:56 -0800:
Hi,
I haven’t read through those (need to go spend time with family so replying
quickly) but given the dates the planning phases for Quantum/Neutron LBaaS
and Libra LBaaS were at the same time.
There was an
On 01/10/2014 04:05 AM, Daniele Venzano wrote:
On 01/09/14 19:12, Matthew Farrellee wrote:
This is definitely great news!
+2 to the things Sergey mentioned below.
Additionally, will you fill out the blueprint or wiki w/ details that
will help others write integration tests for your plugin?
Hi all,
I've been thinking about how we should treat third-party drivers in Ironic
for a while, and had several discussions at the Hong Kong summit and last
week at LCA. Cinder, Nova, Neutron, and TripleO are all having similar
discussions, too. What follows is a summary of my thoughts and a
On Sat, 2014-01-18 at 09:13 -0500, Doug Hellmann wrote:
I like the idea of a fresh start, but I don't think that's
incompatible with the other work to clean up the existing clients.
That cleanup work could help with creating the backwards compatibility
layer, if a new library needs to include
I have been seeing in the past 2 days timeout failures on gate jobs which I
am struggling to explain. An example is available in [1]
These are the usual failure that we associate with bug 1253896, but this
time I can verify that:
- The floating IP is correctly wired (IP and NAT rules)
- The DHCP
On Wed, Jan 15, 2014 at 4:56 PM, Vishvananda Ishaya
vishvana...@gmail.comwrote:
On Jan 14, 2014, at 2:10 PM, Jon Bernard jbern...@tuxion.com wrote:
snip
As you’ve defined the feature so far, it seems like most of it could
be implemented client side:
* pause the instance
*
Hi all,
I'd like you to examine a change. Please visit
[neutron]
https://review.openstack.org/#/c/63981/
‘ipt_mgr.ipv6 written in the wrong ipt_mgr.ipv4’
[nova]
https://review.openstack.org/#/c/64241/
'Add API schema for v3 multinic API'
[python-keystoneclient]
It is being fixed https://review.openstack.org/#/c/61717/
Thanks,
Jay
2014/1/20 li zheming lizhemin...@gmail.com
hi all:
when I use cmd nova migration-list, it return error,like this:
openstack@ openstack@devstack:/home$devstack:/home$ nova
migration-list
ERROR: 'unicode'
On Mon, Jan 20, 2014 at 6:17 AM, Devananda van der Veen
devananda@gmail.com wrote:
1. each driver must adhere to the existing driver interfaces.
2. each driver must have comprehensive unit test coverage and sufficient
inline documentation.
3. vendors are responsible for fixing bugs in
Ok .thanks Jay
I consider it is error in novaclient before.
it is my misunderstand. thank you very much!
lizheming
2014/1/20 Jay Lau jay.lau@gmail.com
It is being fixed https://review.openstack.org/#/c/61717/
Thanks,
Jay
2014/1/20 li zheming lizhemin...@gmail.com
hi all:
-Original Message-
From: Kurt Griffiths [mailto:kurt.griffi...@rackspace.com]
Sent: Saturday, January 18, 2014 4:47 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [wsme] Undefined attributes in WSME
FWIW, I believe Nova is looking
On Jan 19, 2014, at 5:37 PM, Jamie Lennox
jamielen...@redhat.commailto:jamielen...@redhat.com wrote:
On Sat, 2014-01-18 at 09:13 -0500, Doug Hellmann wrote:
I like the idea of a fresh start, but I don't think that's
incompatible with the other work to clean up the existing clients.
That cleanup
+1, that is another point Rob. When I started this thread my main interest was
disk and then firmware. It is clear we really need to have a clear discussion
on this, as imho I would not be supportive or lease baremetal to tenants if I
can not guarantee the service, otherwise the cost of risking
Hope this thread isn't dead.
Mike - thanks for highlighting some really key issues at scale.
On a related note, can someone from the Ceilometer comment about the store and
forward requirement? Currently scaling RabbitMQ is non-trivial. Though cells
help make the problem smaller, as Paul
On 20 January 2014 18:10, Alan Kavanagh alan.kavan...@ericsson.com wrote:
+1, that is another point Rob. When I started this thread my main interest
was disk and then firmware. It is clear we really need to have a clear
discussion on this, as imho I would not be supportive or lease baremetal
Hi CM guys,
jd__ wanted to hold off the patch https://review.openstack.org/58747 because he
thinks it's not generic enough and want to have a further discussion about the
resource loader support. So I put it here my original thought and design about
the patch as a start point.
The initial
At work we're currently looking at related use cases, and access keys are
useful without keystone actually managing passwords. The only issue with
https://blueprints.launchpad.net/keystone/+spec/access-key-authentication is
that it requires client side code changes, which is a non-starter in
On 18 Jan 2014, at 19:02, Jay Pipes jaypi...@gmail.com wrote:
On Sat, 2014-01-18 at 09:06 +, Andrew Hutchings wrote:
I’m not sure what is public and what isn’t so I won’t name names.
They are currently talking to us about the best ways of working with
us. Both companies want to use
On 19 Jan 2014, at 09:52, Thomas Herve thomas.he...@enovance.com wrote:
Hi,
I haven’t read through those (need to go spend time with family so replying
quickly) but given the dates the planning phases for Quantum/Neutron LBaaS
and Libra LBaaS were at the same time.
There was an
On Sun, Jan 19, 2014 at 7:53 AM, Matthew Farrellee m...@redhat.com wrote:
On 01/16/2014 09:19 PM, Andrey Lazarev wrote:
My 5 cents:
--
REMOVE - @rest.put('/node-group-templates/node_group_template_id') -
Not Implemented
REMOVE - @rest.put('/cluster-templates/cluster_template_id') -
Hey,
I have to bring up this topic again. A patch
https://review.openstack.org/#/c/66101/ has been uploaded for review to
resolve the cold migration auto confirm issue.
One question want to get some input from you guys: Do we need to
distinguish V2 and V3 API for this behavior? My thinking is
Inlined.
Thanks,
Andrew.
On Sun, Jan 19, 2014 at 7:50 AM, Matthew Farrellee m...@redhat.com wrote:
On 01/16/2014 08:10 AM, Alexander Ignatov wrote:
Matthew,
I'm ok with proposed solution. Some comments/thoughts below:
-
FIX - @rest.post_file('/plugins/plugin_name/version/
28 matches
Mail list logo
