+1
From: chandankumar
chandankumar.093...@gmail.commailto:chandankumar.093...@gmail.com
Reply-To: OpenStack List
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Friday, August 8, 2014 at 2:14 PM
To: OpenStack List
Hi,
I took a look at https://review.openstack.org/#/c/105331/ and had one minor
issue which I think can be addressed. Prior to approving we need to understand
what the state of the V2 API will be.
Thanks
Gary
From: Vijay Venkatachalam
In the past there was smokestack that used a fedora version of libvirt.
Any idea what happened to that?
On 8/11/14, 12:53 PM, Daniel P. Berrange berra...@redhat.com wrote:
On Fri, Aug 08, 2014 at 09:06:29AM -0400, Russell Bryant wrote:
On 08/07/2014 08:06 PM, Michael Still wrote:
It seems to
Hi,
At the moment all of the drivers are required CI support. Are there any plans
regarding the PIC support. I understand that this is something that requires
specific hardware. Are there any plans to add this?
Thanks
Gary
___
OpenStack-dev mailing
-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Nova] PCI support
Gary,
Cisco is adding it in our CI testbed. I guess that mlnx is doing the same for
their MD as well.
-Robert
On 8/11/14, 9:05 AM, Gary Kotton
gkot...@vmware.commailto:gkot...@vmware.com wrote:
Hi,
At the moment all
On 8/11/14, 6:06 PM, Dan Smith d...@danplanet.com wrote:
As the person who -2'd the review, I'm thankful you raised this issue on
the ML, Jay. Much appreciated.
The metadetails term isn't being invented in this patch, of course. I
originally complained about the difference when this was
Date: Tuesday, August 12, 2014 at 10:25 AM
To: OpenStack List
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Cc: Gary Kotton gkot...@vmware.commailto:gkot...@vmware.com
Subject: RE: [openstack-dev] [Nova] PCI support
Hi Gary,
Mellanox already established CI support
sense?
Thanks
Gary
From: Irena Berezovsky ire...@mellanox.commailto:ire...@mellanox.com
Date: Wednesday, August 13, 2014 at 9:01 AM
To: Gary Kotton gkot...@vmware.commailto:gkot...@vmware.com, OpenStack List
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: RE
Huge +1
On 8/13/14, 5:19 PM, Paul Michali (pcm) p...@cisco.com wrote:
+1
PCM (Paul Michali)
MAIL Š..Š. p...@cisco.com
IRC ŠŠ..Š pcm_ (irc.freenode.com)
TW ŠŠŠ... @pmichali
GPG Key Š 4525ECC253E31A83
Fingerprint .. 307A 96BB 1A4C D2C7 931D 8D2D 4525 ECC2 53E3 1A83
On Aug 13, 2014, at 10:05
+1
From: Eric Windisch ewindi...@docker.commailto:ewindi...@docker.com
Reply-To: OpenStack List
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Friday, August 15, 2014 at 9:45 PM
To: OpenStack List
Hi,
Over the last few weeks I have seen a number of patches where LOG.warn is
replacing LOG.warning. I think that if we do something it should be the
opposite as warning is the documented one in python 2 and 3
https://docs.python.org/3/howto/logging.html.
Any thoughts?
Thanks
Gary
From: Joe Gordon joe.gord...@gmail.commailto:joe.gord...@gmail.com
Reply-To: OpenStack List
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Monday, August 18, 2014 at 9:31 PM
To: OpenStack List
Hi,
Minesweeper is back up and running - this is now called Vmware NSX CI.
A patch for the deprecation of the ESX driver resulted in endless Minesweeper
failures (https://review.openstack.org/#/c/108854/). These were resolved by a
number of patches, the last being
Hi,
A few cycles ago the Nova group decided to remove @author from copyright
statements. This is due to the fact that this information is stored in git.
After adding a similar hacking rule to Neutron it has stirred up some debate.
Does anyone have any reason to for us not to go ahead with
Hi,
Very nice write up. I take my hat off for taking the time and doing a
postmortem. As a community we really need to work on how we communicate
with one another. At the end of the day we all have the common goal in the
success of the project.
At times I feel like things are done very quickly
Hi,
I do not think that Nova is in a death spiral. I just think that the
current way of working at the moment is strangling the project. I do not
understand why we need to split drivers out of the core project. Why not
have the ability to provide Œcore review¹ status to people for reviewing
those
On 9/4/14, 4:30 PM, Sean Dague s...@dague.net wrote:
On 09/04/2014 09:21 AM, Daniel P. Berrange wrote:
On Thu, Sep 04, 2014 at 03:07:24PM +0200, Nikola Đipanov wrote:
On 09/04/2014 02:31 PM, Sean Dague wrote:
On 09/04/2014 07:58 AM, Nikola Đipanov wrote:
Hi team,
I am requesting the
On 9/8/14, 7:23 PM, Sylvain Bauza sba...@redhat.com wrote:
Le 08/09/2014 18:06, Steven Dake a écrit :
On 09/05/2014 06:10 AM, Sylvain Bauza wrote:
Le 05/09/2014 12:48, Sean Dague a écrit :
On 09/05/2014 03:02 AM, Sylvain Bauza wrote:
Le 05/09/2014 01:22, Michael Still a écrit :
On Thu,
On 9/11/14, 2:55 PM, Thierry Carrez thie...@openstack.org wrote:
Sean Dague wrote:
[...]
Why don't we start with let's clean up the virt interface and make it
more sane, as I don't think there is any disagreement there. If it's
going to take a cycle, it's going to take a cycle anyway (it
On 9/11/14, 4:30 PM, Sean Dague s...@dague.net wrote:
On 09/11/2014 09:09 AM, Gary Kotton wrote:
On 9/11/14, 2:55 PM, Thierry Carrez thie...@openstack.org wrote:
Sean Dague wrote:
[...]
Why don't we start with let's clean up the virt interface and make it
more sane, as I don't think
Hi,
I am not sure why your setup is not working. The Vmware configuration looks
correct. Please note that the ML2 plugin is currently not supported when
working with the Vmware driver. You should use traditional nova networking.
Please note that there are plans in K to add this support.
Thanks
On 9/16/14, 11:12 AM, Daniel P. Berrange berra...@redhat.com wrote:
On Tue, Sep 16, 2014 at 07:30:26AM +1000, Michael Still wrote:
On Tue, Sep 16, 2014 at 12:30 AM, Russell Bryant rbry...@redhat.com
wrote:
On 09/15/2014 05:42 AM, Daniel P. Berrange wrote:
On Sun, Sep 14, 2014 at 07:07:13AM
Hi,
Below is a short update of the current status of the driver in Juno.
We managed to complete the following specs:
* Integration with oslo.vmware
(https://github.com/openstack/nova-specs/blob/master/specs/juno/use-oslo-vmware.rst)
* Hot plug interface
Hi,
I think that it was very informative and useful. I have forwarded it to a
number of new people starting to work on OpenStack and who were wondering
how to use mockŠ So two birds with one stone.
Thanks!
Gary
On 9/22/14, 7:27 PM, Jay Pipes jaypi...@gmail.com wrote:
Hi all,
OK, so we had our
Hi,
An example for this is:
http://logs.openstack.org/94/59994/10/check/gate-nova-docs/b0f3910/console.html
Any ideas?
Thanks
Gary
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
Hi,
Saw that this was dealt with in most projects. I have posted the Nova review -
https://review.openstack.org/61329
Thanks
Gary
From: Administrator gkot...@vmware.commailto:gkot...@vmware.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
On 12/11/13 12:43 AM, Matt Riedemann mrie...@linux.vnet.ibm.com wrote:
On Tuesday, December 10, 2013 4:17:45 PM, Maithem Munshed 71510 wrote:
Hello,
I was wondering, what is the reason behind having nova audit resources
as opposed to using usage stats directly from what is reported by the
Hi,
At the moment the administrator is able to retrieve diagnostics for a running
VM. Currently the implementation is very loosely defined, that is, each driver
returns whatever they have to return. This is problematic in a number of
respects:
1. The tempest tests were written specifically
On 12/16/13 5:25 PM, Daniel P. Berrange berra...@redhat.com wrote:
On Mon, Dec 16, 2013 at 06:58:24AM -0800, Gary Kotton wrote:
Hi,
At the moment the administrator is able to retrieve diagnostics for a
running VM. Currently the implementation is very loosely defined, that
is, each driver
. Berrange berra...@redhat.com wrote:
On Mon, Dec 16, 2013 at 03:37:39PM +, John Garbutt wrote:
On 16 December 2013 15:25, Daniel P. Berrange berra...@redhat.com
wrote:
On Mon, Dec 16, 2013 at 06:58:24AM -0800, Gary Kotton wrote:
I'd like to propose the following for the V3 API (we will not touch
Hi,
Currently there are 2 VMware drivers:
* VMwareVCDriver – this lets nova compute communicate with a vCenter server
(which manages the ESX hosts)
* VMwareESXDriver – this lets nova compute manage the ESX host
Thanks
Gary
From: Ray Sun xiaoq...@gmail.commailto:xiaoq...@gmail.com
Would it be possible that an additional core please take a look at
https://review.openstack.org/#/c/51793/?
Thanks
Gary
From: Shawn Hartsock harts...@acm.orgmailto:harts...@acm.org
Date: Wednesday, December 18, 2013 6:32 PM
To: OpenStack Development Mailing List (not for usage questions)
On 12/19/13 5:50 PM, Daniel P. Berrange berra...@redhat.com wrote:
On Tue, Dec 17, 2013 at 04:28:30AM -0800, Gary Kotton wrote:
Hi,
Following the discussion yesterday I have updated the wiki - please see
https://urldefense.proofpoint.com/v1/url?u=https://wiki.openstack.org/wik
i
On 12/19/13 6:07 PM, Daniel P. Berrange berra...@redhat.com wrote:
On Thu, Dec 19, 2013 at 08:02:16AM -0800, Gary Kotton wrote:
On 12/19/13 5:50 PM, Daniel P. Berrange berra...@redhat.com wrote:
On Tue, Dec 17, 2013 at 04:28:30AM -0800, Gary Kotton wrote:
Hi,
Following
Hi,
There seems to be an issue with the hyper CI. Please see -
https://review.openstack.org/#/c/52687/. This code does is not related to the
HyperV driver.
Thanks
Gary
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
Hi,
Following all of the discussion I have done the following:
1. Update the wiki with all of the details -
https://wiki.openstack.org/wiki/Nova_VM_Diagnostics
2. Renamed the BP. It is now called v3-diagnostics
https://blueprints.launchpad.net/openstack/?searchtext=v3-diagnostics
3. Posted a patch
Hi,
It seems that she/he is behaving oddly again. I have posted a patch that does
not have any database changes and it has give me a –1….
Happy new year
Gary
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
+1
On 1/6/14 7:55 PM, Florent Flament florent.flament-...@cloudwatt.com
wrote:
+1
- Original Message -
From: Sean Dague s...@dague.net
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Monday, January 6, 2014 5:30:09 PM
Subject: Re:
Hi,
Anyone aware of the following:
2014-01-07
11:59:47.428http://logs.openstack.org/10/60010/2/check/gate-nova-python27/ebd53ea/console.html#_2014-01-07_11_59_47_428
| Requirement already satisfied (use --upgrade to upgrade): markupsafe in
./.tox/py27/lib/python2.7/site-packages (from
Hi,
In order for the VM to be booted the image needs to be on a datastore
accessible by the host. By default the data tore will not have the image. This
is copied from glance tot he datastore. This is most probably where the problem
is. This may take a while depending on the connectivity
a 1G image. This
takes about 2 minutes to upload to the cache. Please note that I am running on
a virtual setup so thing take far longer than they would if it was bare metal
Best Regards
-- Ray
On Wed, Jan 8, 2014 at 4:31 PM, Gary Kotton
gkot...@vmware.commailto:gkot...@vmware.com wrote:
Hi
Hi,
I was looking into SSH failures and stumbled upon the following tempest issue.
The validations would not take into account the neutron agent heartbeat
timeout. This would cause tests to occasionally fail. In short there was a
window of at most 4 second for the test test_list_agent to run in
Hi,
1 in 3 failures today are due to:
2014-01-23
11:54:03.879http://logs.openstack.org/14/68614/1/check/gate-nova-python27/e11a79c/console.html#_2014-01-23_11_54_03_879
|
2014-01-23
Hi,
Just an update regarding the instance groups:
1. The API has been posted - https://review.openstack.org/#/c/62557/
2. The CLI has been posted - https://review.openstack.org/#/c/32904/
Thanks
Gary
On 1/28/14 12:45 PM, Khanh-Toan Tran khanh-toan.t...@cloudwatt.com
wrote:
Dear all,
If we
Hi,
Lats week there were some infra problems. These have been addressed and
minesweeper is back in action.
Thanks
Gary
On 1/25/14 4:58 PM, Matt Riedemann mrie...@linux.vnet.ibm.com wrote:
Seeing a few patches where vmware minesweeper is saying the build
failed, but looks like an infra issue? An
Hi,
At the moment we have a terribly long queue for minesweeper. We are able to
reduce this considerably by running tempest tests in parallel. We have
encountered 2 race conditions when we do this and it would be very helpful if
we can get the following patches in – they will help with the
On 1/29/14 7:39 PM, Russell Bryant rbry...@redhat.com wrote:
On 01/29/2014 12:27 PM, Daniel P. Berrange wrote:
On Wed, Jan 29, 2014 at 11:47:07AM -0500, Russell Bryant wrote:
Greetings,
A while back I mentioned that we would revisit the potential
deprecation
of nova-network in Icehouse
the scheduler and nova
objects that I would like to clear up. In one scheduler/gantt meeting, Gary
Kotton offered to convert the scheduler to use Nova objects. In another I heard
that with the creation of Gantt, the scheduler would avoid using any Nova
specific features including Nova objects.
I can
Hi,
The following patches will really help minesweeper:
1. Treat exceptions that are caused by parallel tests. This enables us to
run parallel jobs (we have very promising results of running 8 parallel
test jobs):
https://review.openstack.org/#/c/70137/
Hi,
It has come to my attention that this blueprint
(https://blueprints.launchpad.net/nova/+spec/vmware-image-cache-management) has
been deferred to the next milestone series. The blueprint ensures that the
driver has aging for cached images. This is a critical issue for the driver and
is
Hi,
Thanks for the detailed mail. For the first step of moving the code into
OSLO we are trying to be as conservative as possible (similar to the fork
lift of the scheduler code). That is, we are taking working code and
moving it to the common library, not doing any rewrites and using the same
On 2/6/14 1:58 PM, Matthew Booth mbo...@redhat.com wrote:
On 06/02/14 11:24, Gary Kotton wrote:
Hi,
Thanks for the detailed mail. For the first step of moving the code into
OSLO we are trying to be as conservative as possible (similar to the
fork
lift of the scheduler code). That is, we
Hi,
Anyone aware of:
2014-02-08
06:49:42.022http://logs.openstack.org/93/61693/9/check/gate-nova-python26/9db0d67/console.html#_2014-02-08_06_49_42_022
| ${PYTHON:-python} -m subunit.run discover -t ./ ./nova/tests --load-list
/tmp/tmp.aaa9SCw11a/tmpuyhFPj
2014-02-08
Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Nova] Gate broken
On Sat, Feb 8, 2014 at 3:29 PM, Gary Kotton
gkot...@vmware.commailto:gkot...@vmware.com wrote:
Hi,
Anyone aware of:
It is caused the new
Hi,
I saw that one of the days there will be talk about Gantt. Would it be possible
that people not at the local meet up can join this discussion?
Thanks
Gary
From: Dugger, Donald D
donald.d.dug...@intel.commailto:donald.d.dug...@intel.com
Reply-To: OpenStack Development Mailing List (not for
+1
On 2/11/14 1:28 AM, Mark McClain mmccl...@yahoo-inc.com wrote:
All-
I¹d like to nominate Oleg Bondarev to become a Neutron core reviewer.
Oleg has been valuable contributor to Neutron by actively reviewing,
working on bugs, and contributing code.
Neutron cores please reply back with
Hi,
The commit
https://github.com/openstack/nova/commit/c4bf32c03283cbedade9ab8ca99e5b13b9b86ccb
added a warning that the ESX driver is not tested. My understanding is that
there are a number of people using the ESX driver so it should not be
deprecated. In order to get the warning removed we
cannot do live migration
in the condition of between ESX servers in one cluster.
2014-02-13 16:47 GMT+08:00 Gary Kotton
gkot...@vmware.commailto:gkot...@vmware.com:
Hi,
The commit
https://github.com/openstack/nova/commit/c4bf32c03283cbedade9ab8ca99e5b13b9b86ccbhttps://urldefense.proofpoint.com/v1
Hi,
It seems that the command 'reverify bug number' is not working. Anyone else
experienced this lately.
Thanks
Gary
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-December/021649.htmlk=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0Ar=eH0pxTUZo8NPZyF6hgoMQu%2BfDtysg45MkPhCZFxPEq8%3D%0Am=B8yQ75uRFa7dyD%2FbgPgO%2FMT2x229MkK1vHWBVAzpFtM%3D%0As=d9cbcbde99b7c88c15ca138499de8f36edd4247ce351e41b241d675b09b79956
-Sylvain
2014-02-17 13:00 GMT+01:00 Gary Kotton
gkot
=8fc4d7e6970936977dc85989e4e7e9429afb15f5091a768efa4ce236417d9c9b
Note that core team can trigger gate jobs by re-approving the patch.
Thanks,
Akihiro
(2014/02/17 22:03), Gary Kotton wrote:
Hi,
The reverify no bug was removed. But reverify bug # used to work.
That no longer does. With the constant gate failures how can we
I will help out.
Thanks
Gary
From: Tracy Jones tjo...@vmware.commailto:tjo...@vmware.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Tuesday, February 18, 2014 9:48 PM
To: OpenStack
Hi,
Plesae note that regarding the Vmware driver the maintenance mode only works
with the ESX driver and not the VC driver. For the VC driver there is a patch
in review - https://review.openstack.org/#/c/72143/
Thanks
Gary
From: Jay Lau jay.lau@gmail.commailto:jay.lau@gmail.com
On 2/19/14 10:31 PM, Alan Pevec ape...@gmail.com wrote:
Yeah it's pip weirdness where things falls apart because of version
cap. It's
basically installing bin/swift from 1.9 when it sees the version
requirement
but it leaves everything in python-swiftclient namespace from master.
So I've
Hi,
This is something that would be nice to add as an extension. At the moment it
is not part of our near term development plans. It would be nice to engage the
community to discuss and see how this can be exposed correctly using the Nova
API's. It may be something worthwhile discussing at the
Hi,
This is the same channel as nova – that is #openstack-nova
Thanks
Gary
From: wu jiang win...@gmail.commailto:win...@gmail.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Monday, March
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
Hi,
Anyone know how I cam solve the error below:
Running setup.py install for jsonpatch
/usr/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution
option: 'entry_poimts'
warnings.warn(msg)
changing mode of build/scripts-2.7/jsondiff from 664 to 775
changing
Hi,
I have provided a solution for the single node setup that. That is, we
make use of the nova lock utilities to provide locking so that that the
cached images will not be removed whilst an instance is spawned. I hope
that this will unblock the feature an enable us to continue with the FFE.
The
Hi,
The client gate seems to be broken with the following error:
2014-03-10
08:19:39.566http://logs.openstack.org/74/67074/8/check/gate-python-novaclient-pypy/44c12e7/console.html#_2014-03-10_08_19_39_566
| Running setup.py install for python-mimeparse
2014-03-10
Regarding the spawn there are a number of patches up for review at the
moment - they are all mutually exclusive and hopefully will make the
process a lot smoother.
https://review.openstack.org/#/q/topic:bp/vmware-spawn-refactor,n,z
In addition to this we have a patch up for review with the OSLO
Hi,
The gate is once again broken:
2013-10-10 05:15:05.036 | Traceback (most recent call last):
2013-10-10 05:15:05.036 | File
/home/jenkins/workspace/gate-nova-python26/nova/tests/test_api.py, line 389,
in test_group_name_valid_length_security_group
2013-10-10 05:15:05.036 |
Same on trunk!
From: Administrator gkot...@vmware.commailto:gkot...@vmware.com
Reply-To: OpenStack Development Mailing List
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Thursday, October 10, 2013 9:10 AM
To: OpenStack Development Mailing List
/grizzly
Hi Gary:
Same problem with me. There may be some races between the parallelled unittests.
2013/10/10 Gary Kotton gkot...@vmware.commailto:gkot...@vmware.com
Hi,
The gate is once again broken:
2013-10-10 05:15:05.036 | Traceback (most recent call last):
2013-10-10 05:15:05.036 | File
Hi,
I am dealing this with this – please see https://review.openstack.org/50904
Thanks
Gary
From: Chang Bo Guo guoc...@cn.ibm.commailto:guoc...@cn.ibm.com
Reply-To: OpenStack Development Mailing List
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Thursday,
was not updated. Maybe someone
who is familiar with that can chime in.
Thanks
Gary
On 10/10/13 12:20 PM, Alan Pevec ape...@gmail.com wrote:
2013/10/10 Gary Kotton gkot...@vmware.com:
The problem seems to be with the boto python library. I am not really
familiar with this but I have seen this is the last
FYI
On 10/10/13 9:43 PM, Russell Bryant rbry...@redhat.com wrote:
Greetings,
We already have more proposals for the Nova design summit track than
time slots. Please get your proposals in as soon as possible, and
ideally no later than 1 week from today - Thursday, October 17. At that
point we
Yup, it seems to be hypervisor specific. I have added in the Vmware support
following you correcting in the Vmware driver.
Thanks
Gary
From: Matt Riedemann mrie...@us.ibm.commailto:mrie...@us.ibm.com
Reply-To: OpenStack Development Mailing List
States
From:Gary Kotton gkot...@vmware.commailto:gkot...@vmware.com
To:OpenStack Development Mailing List
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org,
Date:10/12/2013 01:42 PM
Subject:Re: [openstack-dev] [nova] Looking
Hi,
I agree with Phil. This has been on the agenda of the scheduling meetings
for over a month now.
Thanks
Gary
On 10/15/13 2:40 PM, Day, Phil philip@hp.com wrote:
Hi Alex,
My understanding is that the 17th is the deadline and that Russell needs
to be planning the sessions from that point
Kudos to Sreeram. Great work here.
From: Sreeram Yerrapragada
syerraprag...@vmware.commailto:syerraprag...@vmware.com
Reply-To: OpenStack Development Mailing List
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Saturday, October 19, 2013 1:29 AM
To: OpenStack
Hi,
I have encountered a few issues regarding the resource tracking and hopefully
someone can help clarify here. From what I understand we just seem to ignore
the actual used disk and memory from the hypervisor and calculate it according
to the allocated instances. For example, if the
Hi,
The gate for stable Hanava is broken in Nova with the following error:
==
2013-10-24
12:48:35.629http://logs.openstack.org/95/53595/1/check/check-tempest-devstack-vm-full/14c606f/console.html#_2013-10-24_12_48_35_629
|
On 10/24/13 4:46 PM, Dan Smith d...@danplanet.com wrote:
In the last meeting we discussed an idea that I think is worth trying at
least for icehouse-1 to see if we like it or not. The idea is that
*every* blueprint starts out at a Low priority, which means best
effort, but no promises.
/53699/)
On Thu, Oct 24, 2013 at 2:51 PM, Gary Kotton
gkot...@vmware.commailto:gkot...@vmware.com wrote:
Hi,
The gate for stable Hanava is broken in Nova with the following error:
==
2013-10-24
12:48:35.629http
Hi,
In the case of stable back ports which have Fixes bug: #XYZ we will have to
change this to the new format Closes-bug: #XYZ. Any thoughts on this?
Thanks
Gary
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
placement concerns that extend
to finding a capable hypervisor for the VM that someone would like to
boot, and then just slightly beyond.
+1
[Gary Kotton] When we proposed the initial VM ensembles this was one of the
option that was considered. The guys from Heat did not like this approach. I
Hi,
Over the last few days I have noticed that bug fixes posted to gerrit are not
updated in Launchpad. Am I doing something wrong? I think that the commit
message is the correct format: Closes-Bug: #bug number.
Any ideas?
Thanks
Gary
___
OpenStack-dev
Hi,
I think that John has a very valid point. My understanding from the
session was that this should be a stand alone tool that will also work
across services, that is, if neutron is configured then it will check that
the neutron credentials are correct.
Thanks
Gary
On 11/11/13 1:55 PM, John
I am in favor/favour of the -1 with suggestions on what to change. The
more input we can provide on a review the better.
Thanks
Gary
On 11/11/13 8:21 PM, Collins, Sean (Contractor)
sean_colli...@cable.comcast.com wrote:
As long as the -1's include a correction that can be copied
and pasted, I
Please delete the file - /usr/bin/nova-rootwrap (this code was updated to use
the openstack common root wrap code).
I also hit the same issue yesterday
Thanks
Gary
From: Sullivan, Jon Paul
jonpaul.sulli...@hp.commailto:jonpaul.sulli...@hp.com
Reply-To: OpenStack Development Mailing List (not
Hi,
The gating for the stable version is broken when the running the neutron gate.
Locally this works but the gate has problem. All of the services are up and
running correctly. There are some exceptions with the ceilometer service but
that is not related to the neutron gating.
The error
Thanks. Looks like something fishy with tempest. When I just run neutron
everything is well and fine.
On 11/17/13 5:50 PM, Matt Riedemann mrie...@linux.vnet.ibm.com wrote:
On Sunday, November 17, 2013 7:46:39 AM, Gary Kotton wrote:
Hi,
The gating for the stable version is broken when
Thanks for dealing with this!
On 11/17/13 10:45 PM, Sean Dague s...@dague.net wrote:
Clark,
Thanks for tracking that down, just pushed those changes to the gate.
On Sun, Nov 17, 2013 at 3:03 PM, Clark Boylan clark.boy...@gmail.com
wrote:
On Sun, Nov 17, 2013 at 7:53 AM, Gary Kotton gkot
+1
On 11/23/13 4:53 PM, Sean Dague s...@dague.net wrote:
+1 would be happy to have Matt on the team
On Fri, Nov 22, 2013 at 8:23 PM, Brian Elliott bdelli...@gmail.com
wrote:
+1
Solid reviewer!
Sent from my iPad
On Nov 22, 2013, at 2:53 PM, Russell Bryant rbry...@redhat.com wrote:
On 11/22/13 2:47 PM, Daniel P. Berrange berra...@redhat.com wrote:
On Fri, Nov 22, 2013 at 11:25:51AM +, John Garbutt wrote:
On Fri, Nov 15, 2013 at 2:21 PM, Russell Bryant rbry...@redhat.com
wrote:
In particular, has there been a decision made about whether it will
definitely be
Hi,
To whoever fixed the gate – Thanks! Can someone please let us know what the
problems were.
Thanks
Gary
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Hi,
Thanks. I think that it may also be good to discuss Robert Collins proposal of
moving the scheduler out of Nova.
Thanks
Gary
From: Dugger, Donald D
donald.d.dug...@intel.commailto:donald.d.dug...@intel.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
+1
On 11/27/13 3:29 PM, Andrew Laski andrew.la...@rackspace.com wrote:
+1
On 11/26/13 at 02:32pm, Russell Bryant wrote:
Greetings,
I would like to propose that we re-add Dan Prince to the nova-core
review team.
Dan Prince has been involved with Nova since early in OpenStack's
history (Bexar
On 11/28/13 12:10 AM, Robert Collins robe...@robertcollins.net wrote:
On 25 November 2013 21:51, Sylvain Bauza sylvain.ba...@bull.net wrote:
As said earlier, I also would love to join the team, triggering a few
blueprints or so.
By the way, I'm currently reviewing the Scheduler code. Do you
1 - 100 of 585 matches
Mail list logo
