On 4 March 2014 17:07, Jay Pipes jaypi...@gmail.com wrote:
I would advise dropping the custom CI setup and going with a method that
specifically uses the upstream openstack-dev/devstack and
openstack-infra/devstack-gate projects.
This sounds great to me. Thank you for all the work you are
Well I use a 8 cores 128G RAM physical host :) I did not see much of the
CPU consumption for these 100 containers, so I suspect we can use less
resources.
-Message d'origine-
De : David Peraza [mailto:david_per...@persistentsys.com]
Envoyé : lundi 3 mars 2014 20:27
À : OpenStack
Georgy Okrokvertskhov gokrokvertsk...@mirantis.com wrote on 05/03/2014
00:32:08:
From: Georgy Okrokvertskhov gokrokvertsk...@mirantis.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date: 05/03/2014 00:34
Subject: Re: [openstack-dev]
Hi Liuji,
I'm the owner of bp support-libvirt-vcpu-topology,
There are four main reasons that I did not continue to work on it:
1. the design proposal has not confirmed by core developers of nova
2. this bp is not accepted in Icehouse development stage
3. Daniel expects that this bp should
Hi Stan,
thanks for sharing your thoughts about Murano and relation to TOSCA. I have
added a few comments below.
From: Stan Lagun sla...@mirantis.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date: 05/03/2014 00:51
Subject: Re:
Forgot to provide the email addresses of Paul and Simon in my last mail:
paul.lip...@ca.com
smo...@de.ibm.com
Regards,
Thomas
From: Thomas Spatzier/Germany/IBM@IBMDE
To: OpenStack Development Mailing List \(not for usage questions\)
openstack-dev@lists.openstack.org
Date: 05/03/2014 10:21
Hi,
I have implemented the Nova V2 and V3 APIs for Domain Quota Management. But
what i want to know whether is there any standard in using the ALIAS for the
URLs.
For example, i thought of using domain-quota-sets or os-domain-quota-sets.
Can any body tell me whether i can use ALIAS like the
I think today and I have a good name for package (instead of
'mistral/model')
How do you think about to name it 'mistral/workbook'? I.e., It means that
it contains modules for work with workbook representation - tasks,
services, actions and workflow.
This way we able to get rid of any confusing.
On 03/04/2014 10:44 PM, Christopher Yeoh wrote:
On Tue, 04 Mar 2014 16:09:21 -0800
Dan Smith d...@danplanet.com wrote:
What I'd like to do next is work through a new proposal that
includes keeping both v2 and v3, but with a new added focus of
minimizing the cost. This should include a path
Hi
What is the current status of the work around multi-attach-volume [1]? We have
some cluster related use cases that would benefit from being able to attach a
volume from several instances.
[1] https://wiki.openstack.org/wiki/Cinder/blueprints/multi-attach-volume
Best regards
Niklas Widell
On Tue, Mar 04, 2014 at 02:06:16PM -0800, Clint Byrum wrote:
Excerpts from Steven Hardy's message of 2014-03-04 09:39:21 -0800:
Hi all,
As some of you know, I've been working on the instance-users blueprint[1].
This blueprint implementation requires three new items to be added to the
Hi team,
We have some issues with the requirements for different Murano components:
linkhttps://docs.google.com/a/mirantis.com/spreadsheet/pub?key=0Aiup6hoNUUUedGt3cnJIMHAxbTlHdlFDZGhxLS1yRXcoutput=html
I suggest to discuss these issues in etherpad:
Hi Robert, Sandhya,
I have pushed the reference implementation SriovAgentMechanismDriverBase as
part the following WIP:
https://review.openstack.org/#/c/74464/
The code is in mech_agent.py, and very simple code for mech_sriov_nic_switch.py.
Please take a look and review.
BR,
Irena
On Mon, Mar 03, 2014 at 09:19:34AM +0100, Radomir Dopieralski wrote:
On 27/02/14 11:52, Petr Blaho wrote:
I agree with you w/r/t to indirection when accessing data but I like the
idea that when I look at json repsonse I see what type of resource it
is. That wrapper element describes it.
I mean we still have the tempest/stress/actions/ and we could put something
like that in there. In general I would like to discuss this topic in the next
QA meeting..
@Julien: are you able to join the next meeting? It would be 22:00 UTC.
@Marc : so next Thrusday (3/6/2014) ? Yes I can be there.
Hi,
We decided multi-attach feature must be implemented as an extension to
core functionality in Cinder, but currently we have not a clear
extension support in Cinder, IMO it's the biggest blocker now. And the
other issues have been listed at
I like this plan as it addresses my primary concern of getting deployments
comfortable with the transition.
We don't mention SDKs in the plan. It seems like getting at least one SDK
to use v3 would provide us additional data in the transition. There is
clear risk associated with that, but it
On Wed, 2014-03-05 at 05:43 +, Kenichi Oomichi wrote:
-Original Message-
From: Dan Smith [mailto:d...@danplanet.com]
Sent: Wednesday, March 05, 2014 9:09 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Nova] Concrete Proposal
On 03/05/2014 08:52 AM, Christopher Lefelhocz wrote:
I like this plan as it addresses my primary concern of getting deployments
comfortable with the transition.
We don't mention SDKs in the plan. It seems like getting at least one SDK
to use v3 would provide us additional data in the
Hello,
Recently, I found a serious issue about network-nodes startup time,
neutron-rootwrap eats a lot of cpu cycles, much more than the processes
it's wrapping itself.
On a database with 1 public network, 192 private networks, 192
routers, and 192 nano VMs, with OVS plugin:
Hi Irena,
My MD has to take care of admin state changes since I have no L2
agent. I think that is what Bob also alluded to. That being said, I am not
doing anything specific to handle admin_state_up/down. The SR-IOV port on
my device is always going to be up, for now atleast.
Thanks,
Sandhya
Hi Sean,
See embedded commentsŠ
Thanks,
Robert
On 3/4/14 3:25 PM, Collins, Sean sean_colli...@cable.comcast.com wrote:
On Tue, Mar 04, 2014 at 02:08:03PM EST, Robert Li (baoli) wrote:
Hi Xu Han Sean,
Is this code going to be committed as it is? Based on this morning's
discussion, I
Hi:
I'm Fang Zhen, an M.S student from China. My current research work is on
scheduling policy on cloud computing. I have been following the openstack
for about 2 years.I always thought of picking a blueprint and implementing
it with the community's guidance.Luckily, open-stack participates GSOC
Nova is now feature frozen for the Icehouse release. Patches for
blueprints not already merged will need a feature freeze exception (FFE)
to be considered for Icehouse.
If you would like to request a FFE, please do so on the openstack-dev
mailing list with a prefix of [Nova] FFE Request: .
In
On 03/05/2014 09:59 AM, 方祯 wrote:
Hi:
I'm Fang Zhen, an M.S student from China. My current research work is on
scheduling policy on cloud computing. I have been following the
openstack for about 2 years.I always thought of picking a blueprint and
implementing it with the community's
Hi Fang,
Gantt subteam owns weekly meetings every Tuesdays 1500 UTC at
#openstack-meeting IRC channel, where we discuss about the steps for
forklifting Nova scheduler into a separate service.
As there is now FeatureFreeze period, there are no patches targeted to
be merged before next Juno
Miguel Angel Ajo wrote:
[...]
The overhead comes from python startup time + rootwrap loading.
I suppose that rootwrap was designed for lower amount of system calls
(nova?).
Yes, it was not really designed to escalate rights on hundreds of
separate shell commands in a row.
And, I
Hi Robert,
I'm reaching out to you off-list for this:
On Wed, Mar 05, 2014 at 09:48:46AM EST, Robert Li (baoli) wrote:
As a result of this change, it will end up having two LLA addresses in the
router's qr interface. It would have made more sense if the LLA will be
replacing the qr
Hi,
https://blueprints.launchpad.net/cinder/+spec/cinder-rbd-driver-qos
I've been looking at this blueprint with a view to contributing on it, assuming
I can take it. I am unclear as to whether or not it is still valid. I can see
that it was registered around a year ago and it appears the
Hi,
I'm wondering why in this commit:
https://github.com/openstack/oslo-incubator/commit/630d3959b9d001ca18bd2ed1cf757f2eb44a336f
...the slave_connection option was removed. It seems like a useful option
to have, even if a lot of projects weren't yet using it.
Darren
After reading this I feel it requires me to ask the question:
Do flavors have datastores or do datastores have flavors?
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Hey, Danies.
Datastore has a set of flavor that allowed to be used while instance
provisioning with the given datastore.
Best regards,
Denis Makogon
On Wed, Mar 5, 2014 at 5:28 PM, Daniel Salinas imsplit...@gmail.com wrote:
After reading this I feel it requires me to ask the question:
Do
Hi Fang,
Agree with Russell. Also please update the wiki with your information
https://wiki.openstack.org/wiki/GSoC2014 and also information about
the mentor/ideas as well (if you have not yet done so already). You
can reach out to folks on #openstack-gsoc and #openstack-nova IRC
channels as well
Dina Belova wrote:
I think your idea is really interesting. I mean, that thought “Gantt -
where to schedule, Climate - when to schedule” is quite understandable
and good looking.
Would Climate also be usable to support functionality like Spot
Instances ? Schedule when spot price falls under X
Hi,
Unfortunately we did not get the ISO support approved by the deadline. If
possible can we please get the FFE.
The feature is completed and has been tested extensively internally. The
feature is very low risk and has huge value for users. In short a user is able
to upload a iso to glance
Anne Gentle wrote:
It feels like it should be part of a scheduler or reservation program
but we don't have one today. We also don't have a workflow, planning, or
capacity management program, all of which these use cases could fall under.
(I should know this but) What are the options when a
Hi - Please consider the image cache aging BP for FFE
(https://review.openstack.org/#/c/56416/)
This is the last of several patches (already merged) that implement image cache
cleanup for the vmware driver. This patch solves a significant customer pain
point as it removes unused images from
Hello Darren,
This option is removed since oslo.db will no longer manage engine
objects on it's own. Since it will not store engines it cannot handle
query dispatching.
Every project that wan't to use slave_connection will have to implement
this logic (creation of the slave engine and query
On Tue, Mar 4, 2014 at 6:21 PM, Qin Zhao chaoc...@gmail.com wrote:
Hi Joe, my meaning is that cloud users may not hope to create new instances
or new images, because those actions may require additional approval and
additional charging. Or, due to instance/image quota limits, they can not do
Hi Irena,
The main reason for me to do it that way is how vif_details should be
setup in our case. Do you need vlan in vif_details? The behavior in the
existing base classes is that the vif_details is set during the driver
init time. In our case, it needs to be setup during bind_port().
thanks,
On Wed, Mar 5, 2014 at 5:53 AM, Julien Danjou jul...@danjou.info wrote:
On Tue, Mar 04 2014, Joe Gordon wrote:
So since tools/config/check_uptodate.sh is oslo code, I assumed this
issue falls into the domain of oslo-incubator.
Until this gets resolved nova is considering
This has actually come up before, too:
http://lists.openstack.org/pipermail/openstack-dev/2013-July/012539.html
-Ben
On 2014-03-05 08:42, Miguel Angel Ajo wrote:
Hello,
Recently, I found a serious issue about network-nodes startup time,
neutron-rootwrap eats a lot of cpu cycles, much
Hi Sean,
Sorry for your frustration. I actually provided the comments about the two
LLAs in the review (see patch set 1). If the intent for these changes is
to allow RAs from legitimate sources only, I'm afraid that that goal won't
be reached with them. I may be completely wrong, but so far I
Hi Robert,
I think what you mentioned can be achieved by calling into specific MD method
from
SriovAgentMechanismDriverBase .try_to_bind_segment_for_agent mehod, maybe
something like 'get_vif_details' before it calls to context.set_binding.
Would you mind to continue discussion over patch gerrit
On Wed, Mar 5, 2014 at 10:43 AM, Alexei Kornienko
alexei.kornie...@gmail.com wrote:
Hello Darren,
This option is removed since oslo.db will no longer manage engine objects
on it's own. Since it will not store engines it cannot handle query
dispatching.
Every project that wan't to use
Hi Mark,?
We have the codebase and the 3rd Party CI setup in place for review.
Freescale CI is currently in non-voting status.
Kindly please consider the Blueprint and the codebase for FFE (icehouse
release).
Blueprint:
Hi Gokul,
Thanks for working out how all these policy initiatives relate to each other.
I'll be spending some time diving into the ones I hadn't heard about.
I made some additional comments about Congress below.
Tim
- Original Message -
From: Jay Lau jay.lau@gmail.com
To:
- Original Message -
Miguel Angel Ajo wrote:
[...]
The overhead comes from python startup time + rootwrap loading.
I suppose that rootwrap was designed for lower amount of system calls
(nova?).
Yes, it was not really designed to escalate rights on hundreds of
Hey,
Sorry I missed this thread a couple of days ago. I am working on a first-pass
of this and hope to have something soon. So far I've mostly focused on getting
OpenVZ and the HP LH SAN driver working for online extend. I've had trouble
with libvirt+kvm+lvm so I'd love some help there if you
Hi folks,
This did not make it in fully. Outstanding patches are:
https://review.openstack.org/#/c/71064/
https://review.openstack.org/#/c/71065/
https://review.openstack.org/#/c/71067/
https://review.openstack.org/#/c/71067/
https://review.openstack.org/#/c/71479/
On 03/05/2014 06:42 AM, Miguel Angel Ajo wrote:
Hello,
Recently, I found a serious issue about network-nodes startup time,
neutron-rootwrap eats a lot of cpu cycles, much more than the processes
it's wrapping itself.
On a database with 1 public network, 192 private networks,
Hi Joe,
If we assume the user is willing to create a new instance, the workflow you
are saying is exactly correct. However, what I am assuming is that the user
is NOT willing to create a new instance. If Nova can revert the existing
instance, instead of creating a new one, it will become the
Why accept it?
* It's low risk but needed refactoring that will make the code that has
been a source of occasional bugs.
* It is very low risk internal refactoring that uses code that has been
in tree for some time now (BDM objects).
* It has seen it's fair share of reviews
Yeah, this has
On 03/05/14 at 09:05am, Dan Smith wrote:
Why accept it?
* It's low risk but needed refactoring that will make the code that has
been a source of occasional bugs.
* It is very low risk internal refactoring that uses code that has been
in tree for some time now (BDM objects).
* It has seen it's
On 03/05/14 at 07:37am, Tracy Jones wrote:
Hi - Please consider the image cache aging BP for FFE
(https://review.openstack.org/#/c/56416/)
This is the last of several patches (already merged) that implement image cache
cleanup for the vmware driver. This patch solves a significant customer
On Wed, Mar 5, 2014 at 8:59 AM, Qin Zhao chaoc...@gmail.com wrote:
Hi Joe,
If we assume the user is willing to create a new instance, the workflow you
are saying is exactly correct. However, what I am assuming is that the user
is NOT willing to create a new instance. If Nova can revert the
Hello All.
We suppose to have common database code oslo.db library. So we decided to
let end applications to cope with engines, not oslo.db. For example, see
work with slave engine in Nova [1]. These is also patch to oslo with more
details - [2]
Also, Darren, please inform us about your usecase
On Wed, Mar 5, 2014 at 8:51 AM, Miguel Angel Ajo Pelayo
mangel...@redhat.com wrote:
- Original Message -
Miguel Angel Ajo wrote:
[...]
The overhead comes from python startup time + rootwrap loading.
I suppose that rootwrap was designed for lower amount of system calls
Since I received some mails privately, I'd like to start weekly IRC meeting.
The first meeting will be
Tuesdays 23:00UTC from March 11, 2014
#openstack-meeting
https://wiki.openstack.org/wiki/Meetings/ServiceVM
If you have topics to discuss, please add to the page.
Sorry if the time is
Hi,
In
https://docs.google.com/document/d/1D-1n8nCEFurYzvEBxIRfXfffnImcIPwWSctAG-NXonY/edit?usp=sharing
referenced by the Wiki, I have added the section that address the items raised
on the last irc meeting.
Regards,
-Sam.
From: Samuel Bercovici
Sent: Wednesday, February 26,
Hi all,
So yeah, we could restore the option and put creation of a slave
engine instance to EngineFacade class, but I don't think we want this.
The only reason why slave connections aren't implemented e.g. in
SQLAlchemy is that, SQLAlchemy, as a library can't decide for you how
those engines
All,
Feature freeze for Ironic is now in effect, and the icehouse-3
milestone-proposed branch has been created:
http://git.openstack.org/cgit/openstack/ironic/log/?h=milestone-proposed
I have bumped to the next cycle any blueprints which were targeted to
Icehouse but not yet completed, and
Hi folks,
We'll be having the Savanna team meeting as usual in
#openstack-meeting-alt channel.
Agenda:
https://wiki.openstack.org/wiki/Meetings/SavannaAgenda#Agenda_for_March.2C_6
http://www.timeanddate.com/worldclock/fixedtime.html?msg=Savanna+Meetingiso=20140306T18
--
Sincerely yours,
On Mar 5, 2014, at 6:42 AM, Miguel Angel Ajo majop...@redhat.com wrote:
Hello,
Recently, I found a serious issue about network-nodes startup time,
neutron-rootwrap eats a lot of cpu cycles, much more than the processes it's
wrapping itself.
On a database with 1 public
Thanks you for the participants who joined the kick-off meeting for work
in the community toward Disaster Recovery for OpenStack.
We captured the meeting notes on the Etherpad - see
https://etherpad.openstack.org/p/juno-disaster-recovery-call-for-stakeholders
Per the consensus in the meeting
Hi
Sorry for not cc openstack-dev at first (haven't got familiar with
OpenStack's GSoC
custom... but it's quite a different flavor compared with my last mentoring
org). I just
sent it to the possible mentors. But it turns out that openstack-dev gives
lots of
benefit. :)
I noticed that Fang also
Hi Chenchong, Fang,
I am glad that you have expressed interested in this project for GSoC. It is a
big project I agree in terms of its scope. But it is good to start with smaller
goals.
It will be interesting to see what incremental things can be added to the
current Nova scheduler to
On 03/05/2014 12:18 PM, Andrew Laski wrote:
On 03/05/14 at 09:05am, Dan Smith wrote:
Why accept it?
* It's low risk but needed refactoring that will make the code that has
been a source of occasional bugs.
* It is very low risk internal refactoring that uses code that has been
in tree for
On 03/05/2014 12:27 PM, Andrew Laski wrote:
On 03/05/14 at 07:37am, Tracy Jones wrote:
Hi - Please consider the image cache aging BP for FFE
(https://review.openstack.org/#/c/56416/)
This is the last of several patches (already merged) that implement
image cache cleanup for the vmware
On 03/05/2014 10:34 AM, Gary Kotton wrote:
Hi,
Unfortunately we did not get the ISO support approved by the deadline.
If possible can we please get the FFE.
The feature is completed and has been tested extensively internally. The
feature is very low risk and has huge value for users. In
On 03/05/2014 05:37 AM, Zhi Yan Liu wrote:
Hi,
We decided multi-attach feature must be implemented as an extension to
core functionality in Cinder, but currently we have not a clear
extension support in Cinder, IMO it's the biggest blocker now. And the
other issues have been listed at
Has anyone tried compiling rootwrap under Cython? Even with non-optimized
libraries,
Cython sometimes sees speedups.
Best Regards,
Solly Ross
- Original Message -
From: Vishvananda Ishaya vishvana...@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
Hi Joe,
For example, I used to use a private cloud system, which will calculate
charge bi-weekly. and it charging formula looks like Total_charge =
Instance_number*C1 + Total_instance_duration*C2 + Image_number*C3 +
Volume_number*C4. Those Instance/Image/Volume number are the number of
those
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
tomorrow Thursday, March 6th at 22: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 add an item to
Hi neutron lbaas folks,
Let's meet tomorrow, Thursday, 06 at 14-00 on #openstack-meeting to
continue discussing the object model.
We had discussed with Samuel Bercovici proposals at hand and currently
there are two main proposals that we are evaluating.
Both of them allow to add two major
Hi,
We would like to make a request for FFE for the Solver Scheduler work. A lot
of work has gone into it since Sep’13, and the first patch has gone through
several iteration after some reviews. The first patch -
https://review.openstack.org/#/c/46588/ introduces the main solver scheduler
Hi community,
Another interesting questions were raised during object model discussion
about how pool statistics and health monitoring should be used in case of
multiple vips sharing one pool.
Right now we can query statistics for the pool, and some data like in/out
bytes and request count will
Hi everyone,
We just hit feature freeze, so please do not approve changes that add
features or new configuration options unless those have been granted a
feature freeze exception.
This is also string freeze, so you should avoid changing translatable
strings. If you have to modify a translatable
Here in Austin we are gearing up for the onslaught of visitors for the SXSW
festival next week. My first visit there was in 2003, and yes I had to look
it up in my blog,
http://justwriteclick.com/2006/03/14/a-trip-report-from-sxsw-interactive-2003/for
those who are into retro tech. :) I'll be
On Mar 5, 2014, at 8:16 AM, Russell Bryant rbry...@redhat.com wrote:
I think SDK support is critical for the success of v3 long term. I
expect most people are using the APIs through one of the major SDKs, so
v3 won't take off until that happens. I think our top priority in Nova
to help
Hi All,
I would like to request FFE for the following patch
https://review.openstack.org/#/c/62599/
The design and the patch has gone through many reviews. We have reached out
to folks working on other advanced services as well.
This will be a first good step towards true service integration
On 03/05/2014 03:40 PM, Yathiraj Udupi (yudupi) wrote:
Hi,
We would like to make a request for FFE for the Solver Scheduler work.
A lot of work has gone into it since Sep’13, and the first patch has
gone through several iteration after some reviews. The first patch
-
Sorry, This is request for FFE.
I meant Approver of the BP was Joe Gordon below.. not sponsor, probably the
wrong word.
Thanks
Yathi.
On 3/5/14, 12:40 PM, Yathiraj Udupi (yudupi)
yud...@cisco.commailto:yud...@cisco.com wrote:
Hi,
We would like to make a request for FFE for the Solver
AWESOME!!
If may I ask, does IPv6 bits got included into this milestone?! I'm very
anxious to start testing it with Ubuntu 14.04 plus the official devel
packages from Canonical.
Thanks a lot!!
Best,
Thiago
On 5 March 2014 17:46, Thierry Carrez thie...@openstack.org wrote:
Hi everyone,
We
I'd like to nominate Radomir Dopieralski to Horizon Core. I find his reviews
very insightful and more importantly have come to rely on their quality. He has
contributed to several areas in Horizon and he understands the code base well.
Radomir is also very active in tuskar-ui both
Hi all,
The [state-management] project team holds a weekly meeting in
#openstack-meeting on thursdays, 2000 UTC. The next meeting is tommorow,
2014-03-06!!!
As usual, everyone is welcome :-)
Link: https://wiki.openstack.org/wiki/Meetings/StateManagement
Taskflow:
Hi Eugene,
Having an aggregate call to get all of the stats and statuses is good, but we
should also keep the ability to retrieve statistics or the status of individual
resources IMHO.
Thanks
Youcef
From: Eugene Nikanorov [mailto:enikano...@mirantis.com]
Sent: Wednesday, March 05, 2014 12:42
On Wednesday, March 5, 2014 at 12:41 PM, Eugene Nikanorov wrote:
Hi community,
Another interesting questions were raised during object model discussion
about how pool statistics and health monitoring should be used in case of
multiple vips sharing one pool.
Right now we can query
Hello openstackers,
I'm excited to share that we have finished work on pilot implementation of
MagnetoDB, a key-value storage service for OpenStack.
During pilot development we have reached the following goals:
-
evaluated python cassandra clients maturity
-
evaluated python web
Hi，
I would like to make a request for FFE for one patch in novaclient for PCI V3
API : https://review.openstack.org/#/c/75324/
Though the V3 API will not release in Icehouse but all the PCI patches for V3
API have been merged, and this is the last for V3,
I think some people may use the V3
Hi,
https://blueprints.launchpad.net/cinder/+spec/vmdk-storage-policy-volume-type
.
This is a blueprint that I am working on since Dec 2013 and as far I
remember it was targetted to icehouse-3. Just today I noticed that it was
moved to future, so should have feel through the cracks for core
Hi,
I am working for Nova API tests in Tempest, and I'd like to ask
opinions about the ways.
Tempest generates a request and sends it to each RESTful API.
Then Tempest receives a response from the API and verifies the
response.
From the viewpoint of the backward compatibility, it is important
-Original Message-
From: Jay Pipes [mailto:jaypi...@gmail.com]
Sent: Wednesday, March 05, 2014 10:52 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Nova] Concrete Proposal for Keeping V2 API
On Wed, 2014-03-05 at 05:43 +, Kenichi Oomichi wrote:
Hi
Here a test result:
http://logs.openstack.org/25/78325/3/check/gate-rally-pep8/323b39c/console.htmland
its result is different from in my local environment. So I want to
check some details of official test environment, for example
/home/jenkins/workspace/gate-rally-pep8/tox.ini.
I guess it is
I already check the stable/havana and master branch via devstack, the
problem is still in havana, but master branch is not affected
I think it is important to fix it for havana too, since some high level
application may depends on the returned faultstring. Currently, I'm not
sure mater branch fix
Folks,
I took a crack at using our DSL to build a real-world workflow.
Just to see how it feels to write it. And how it compares with alternative
tools.
This one automates a page from OpenStack operation guide:
Hi Anand,
I don't think it's fully documented in the API spec yet, but there is a
patchset being reviewed in gerrit that shows how the API would look like
(LbaasSSLDBMixin class):
https://review.openstack.org/#/c/74031/5/neutron/db/loadbalancer/lbaas_ssl_db.py
Thanks,
Youcef
From:
On Mar 5, 2014 6:58 PM, Dmitri Zimine d...@stackstorm.com wrote:
Folks,
I took a crack at using our DSL to build a real-world workflow.
Just to see how it feels to write it. And how it compares with
alternative tools.
This one automates a page from OpenStack operation guide:
Hi David,
That is an interesting idea, I'd like to join in :-)
-Original Message-
From: David Kranz [mailto:dkr...@redhat.com]
Sent: Wednesday, March 05, 2014 3:31 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [qa][nova] Ownership and path to schema definitions
On Tue, 04 Mar 2014 13:31:07 -0500
David Kranz dkr...@redhat.com wrote:
I think it would be a good time to have at least an initial
discussion about the requirements for theses schemas and where they
will live. The next step in tempest around this is to replace the
existing negative test files
1 - 100 of 116 matches
Mail list logo
