at 5:10 PM, John Garbutt j...@johngarbutt.com
wrote:
On 22 June 2015 at 09:18, Sahid Orentino Ferdjaoui
sahid.ferdja...@redhat.com wrote:
On Sun, Jun 21, 2015 at 07:18:10PM +0300, Joe Gordon wrote:
On Fri, Jun 19, 2015 at 12:55 PM, Peng Zhao p...@hyper.sh wrote:
Hi, all,
I
On 22 June 2015 at 23:03, Matt Riedemann mrie...@linux.vnet.ibm.com wrote:
On 6/22/2015 4:38 PM, Matt Riedemann wrote:
On 6/22/2015 4:32 PM, Russell Bryant wrote:
On 06/22/2015 05:23 PM, Matt Riedemann wrote:
The check-tempest-dsvm-cells job has been in nova's check queue since
January
On 23 June 2015 at 03:30, Adam Young ayo...@redhat.com wrote:
On 06/22/2015 10:13 PM, Sajeesh Cimson Sasi wrote:
From: Adam Young [ayo...@redhat.com]
Sent: 23 June 2015 00:01:48
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev]
On 22 June 2015 at 09:18, Sahid Orentino Ferdjaoui
sahid.ferdja...@redhat.com wrote:
On Sun, Jun 21, 2015 at 07:18:10PM +0300, Joe Gordon wrote:
On Fri, Jun 19, 2015 at 12:55 PM, Peng Zhao p...@hyper.sh wrote:
Hi, all,
I would like to propose nova-hyper driver:
On 22 June 2015 at 00:14, Michael Still mi...@stillhq.com wrote:
As an aside, do we think that exposing the exact version of a server
process is safe from a security perspective?
During discussions in the Nova API meeting, it was noted that while we
do expose the exact API version, we are not
A quick bump for this thread because...
* liberty-1 is next week
* spec freeze is on June 25th
* people are unsure about the exception process
On 10 June 2015 at 16:45, John Garbutt j...@johngarbutt.com wrote:
On 4 June 2015 at 12:42, John Garbutt j...@johngarbutt.com wrote:
Hi,
Following up
On 15 June 2015 at 08:03, 郑振宇 zheng.zhe...@outlook.com wrote:
Hi All,
When querying instance actions using API: nova instance-action-list, nova
will response with a table show in below:
root@controller:~# nova instance-action-list
fcbba82f-60a1-4785-84f2-88bcf2da7e7e
Hi,
We have merged the spec that describes the priorities for the Liberty
release, as discussed at the summit:
http://specs.openstack.org/openstack/nova-specs/priorities/liberty-priorities.html
The tracking of spec and code reviews for these is happening in the
usual etherpad:
On 6 June 2015 at 11:16, Kashyap Chamarthy kcham...@redhat.com wrote:
On Fri, Jun 05, 2015 at 10:47:31AM +0100, John Garbutt wrote:
Hi,
So in the interests of filling up your inbox yet further...
We have lots of etherpads from the summit:
https://wiki.openstack.org/wiki/Design_Summit
On 5 June 2015 at 10:50, John Garbutt j...@johngarbutt.com wrote:
On 4 June 2015 at 12:54, John Garbutt j...@johngarbutt.com wrote:
Hi,
We have a regular Nova project meeting with alternating times, as
described here:
https://wiki.openstack.org/wiki/Meetings/Nova
I will lean towards
On 4 June 2015 at 12:42, John Garbutt j...@johngarbutt.com wrote:
Hi,
Following up from nova-meetings and this summit session:
https://etherpad.openstack.org/p/YVR-nova-liberty-process
snip
With that in mind, does this seem like a good idea?
June 12: spec review day (to be confirmed)
Note
talked also with John Garbutt and it seem that the recommendation is to
filter only doc and test folders,
but still I would like to filter some other folders like
1. nova/nova/virt/hyperv
2. nova/nova/virt/ironic
3. nova/nova/virt/vmwareapi
4. nova/nova/virt/xenapi
Is there any Nova CI
Hi,
I still think we need to look at lot more carefully at why using an
isolated service tenant would not work.
Sure, thats a bit rich coming from someone trying to limit the scope
of Nova, but really I am just trying to work out what the problem is
you are tying to solve, and specifically what
Hi,
So in the interests of filling up your inbox yet further...
We have lots of etherpads from the summit:
https://wiki.openstack.org/wiki/Design_Summit/Liberty/Etherpads#Nova
I have extracted all the action items here:
https://etherpad.openstack.org/p/YVR-nova-liberty-summit-action-items
On 4 June 2015 at 12:54, John Garbutt j...@johngarbutt.com wrote:
Hi,
We have a regular Nova project meeting with alternating times, as
described here:
https://wiki.openstack.org/wiki/Meetings/Nova
I will lean towards no change of the times, given we are used to them.
But I want to double
On 4 June 2015 at 10:40, Jens Rosenboom j.rosenb...@x-ion.de wrote:
2015-06-03 14:25 GMT+02:00 John Garbutt j...@johngarbutt.com:
On 3 June 2015 at 12:52, Jay Pipes jaypi...@gmail.com wrote:
On 06/03/2015 02:34 AM, Chris Friesen wrote:
On 06/03/2015 12:16 AM, Jens Rosenboom wrote:
I'm
On 3 June 2015 at 20:51, Amrith Kumar amr...@tesora.com wrote:
Several of us including Bruno Lago, Victoria Martinez de la Cruz (vkmc),
Flavio Percoco, Nikhil Manchanda (SlickNik), Vipul Sabhaya (vipul), Doug
Shelley (dougshelley66), and several others from the Trove team met in
Vancouver and
On 3 June 2015 at 13:39, Jay Pipes jaypi...@gmail.com wrote:
On 06/03/2015 08:25 AM, Zhipeng Huang wrote:
Hi All,
As I understand, Neutron by far has the clearest big tent mode via its
in-tree/out-of-tree decomposition, thanks to Kyle and other Neutron team
members effort.
So my question
On 3 June 2015 at 00:47, Fei Long Wang feil...@catalyst.net.nz wrote:
On 02/06/15 01:51, Jay Pipes wrote:
Please assign me as the CPL for Glance from Nova.
I'm happy to work with Jay for Nova from Glance :)
I have added you both here:
On 4 June 2015 at 09:51, John Garbutt j...@johngarbutt.com wrote:
On 3 June 2015 at 00:47, Fei Long Wang feil...@catalyst.net.nz wrote:
On 02/06/15 01:51, Jay Pipes wrote:
Please assign me as the CPL for Glance from Nova.
I'm happy to work with Jay for Nova from Glance :)
I have added you
On 1 June 2015 at 14:11, Flavio Percoco fla...@redhat.com wrote:
On 01/06/15 13:30 +0100, John Garbutt wrote:
On 1 June 2015 at 13:10, Flavio Percoco fla...@redhat.com wrote:
On 01/06/15 11:57 +0100, John Garbutt wrote:
I'm happy you brought this up. What are Nova's plans to adopt Glance's
v2
Hi,
We had a great discussion at the summit around priorities:
https://etherpad.openstack.org/p/YVR-nova-liberty-priorities
I have made a stab at writing that up here, please to review if you
are interested:
https://review.openstack.org/#/c/187272/
Note we plan to keep focus on the reviews
Hi,
We have a regular Nova project meeting with alternating times, as
described here:
https://wiki.openstack.org/wiki/Meetings/Nova
I will lean towards no change of the times, given we are used to them.
But I want to double check there if there is a group of contributors
we are accidentally
This was sent in another thread, but its a quick read out form one the
Nova sessions at the summit that we might want a Nova specific
discussion on...
-- Forwarded message --
From: John Garbutt j...@johngarbutt.com
Date: 3 June 2015 at 17:57
Subject: Re: [openstack-dev] [all
Hi,
Following up from nova-meetings and this summit session:
https://etherpad.openstack.org/p/YVR-nova-liberty-process
We agreed we follow the same deadlines as kilo, roughly. Importantly,
we wanted to keep the blueprint freeze, and non-priority feature
freeze process from kilo.
This means we
On 2 June 2015 at 23:48, Kevin L. Mitchell kevin.mitch...@rackspace.com wrote:
On Tue, 2015-06-02 at 16:16 -0600, David Lyle wrote:
The Horizon project also uses the nova policy.json file to do role
based access control (RBAC) on the actions a user can perform. If the
defaults are hidden in
On 2 June 2015 at 17:22, Sean Dague s...@dague.net wrote:
Nova has a very large API, and during the last release cycle a lot of
work was done to move all the API checking properly into policy, and not
do admin context checks at the database level. The result is a very
large policy file -
On 3 June 2015 at 14:09, Thierry Carrez thie...@openstack.org wrote:
John Garbutt wrote:
Given we are thinking Liberty is moving to semantic versioning, maybe
it could look like this:
* 12.0.1 (liberty-1) will have some features (hopefully), and will be a tag
* 12.0.2.dev1 is the first commit
Hi,
(To be clear, this is a proposal to be discussed and not a decision.)
The version number can help us communicate that:
* you can consume a milestone release
** ... but the docs and translations may not be totally up to date
* you can consume any commit
** ... but there is no formal tracking
On 3 June 2015 at 12:52, Jay Pipes jaypi...@gmail.com wrote:
On 06/03/2015 02:34 AM, Chris Friesen wrote:
On 06/03/2015 12:16 AM, Jens Rosenboom wrote:
I'm wondering though whether the current API behaviour here should be
changed more generally. Is there a plausible reason to silently
On 3 June 2015 at 13:53, Ed Leafe e...@leafe.com wrote:
On Jun 2, 2015, at 5:58 AM, Alexis Lee alex...@hp.com wrote:
If you allocate all the memory of a box to high-mem instances, you may
not be billing for all the CPU and disk which are now unusable. That's
why flavors were introduced,
On 3 June 2015 at 15:22, Doug Hellmann d...@doughellmann.com wrote:
Excerpts from John Garbutt's message of 2015-06-03 14:24:40 +0100:
On 3 June 2015 at 14:09, Thierry Carrez thie...@openstack.org wrote:
John Garbutt wrote:
Given we are thinking Liberty is moving to semantic versioning
On 3 June 2015 at 15:37, Daniel P. Berrange berra...@redhat.com wrote:
On Wed, Jun 03, 2015 at 10:26:03AM -0400, Doug Hellmann wrote:
Excerpts from Daniel P. Berrange's message of 2015-06-03 14:28:01 +0100:
On Wed, Jun 03, 2015 at 03:09:28PM +0200, Thierry Carrez wrote:
John Garbutt wrote
On 3 June 2015 at 17:35, Thierry Carrez thie...@openstack.org wrote:
John Garbutt wrote:
I support moving nova to intermediate release, but not this cycle.
+1
My main motivation here is actually making it clear how useful a
milestone release can be to get access to a feature you really
+1 to ttx and Jame's points on trust and relationships, indeed
referencing the summit session that ttx mentioned:
https://etherpad.openstack.org/p/liberty-cross-project-in-team-scaling
On 3 June 2015 at 16:01, Nikola Đipanov ndipa...@redhat.com wrote:
On 06/03/2015 02:43 PM, Boris Pavlovic
On 29 May 2015 at 22:38, Doug Hellmann d...@doughellmann.com wrote:
As with our other semver projects, we will use pbr’s interpretation of the
semver rules (http://docs.openstack.org/developer/pbr/semver.html) for minor
updates and patch releases. I don’t believe we discussed whether to
On 28 May 2015 at 19:26, Vladik Romanovsky
vladik.romanov...@enovance.com wrote:
As part of the work to object-ify the image metadata dicts, I'm looking
at the current way the libvirt driver fetches image metadata for an
instance, in cases where the compute manager hasn't already passed it
Just to follow up here, we agreed the nova-docker team would report
back in a nova IRC team meeting on how things are going post
liberty-1.
Thanks,
John
On 27 May 2015 at 16:29, Davanum Srinivas dava...@gmail.com wrote:
Bich,
Sure thing, just start on #nova-docker irc channel and we can talk
On 1 June 2015 at 13:10, Flavio Percoco fla...@redhat.com wrote:
On 01/06/15 11:57 +0100, John Garbutt wrote:
On 26/05/15 13:54 -0400, Nikhil Komawar wrote:
On 5/26/15 12:57 PM, Jesse Cook wrote:
We also had some hallway talk about putting the v1 and v2 APIs on top
of
the v3 API
On 31 May 2015 at 14:15, Xu, Hejie hejie...@intel.com wrote:
Replied in line with prefix [alex]
-Original Message-
From: John Garbutt [mailto:j...@johngarbutt.com]
1)
We agreed changing a 500 error to an existing error (or making it succeed in
the usual way) is a change
On 29 May 2015 at 19:58, Jay Pipes jaypi...@gmail.com wrote:
On 05/29/2015 05:04 AM, John Garbutt wrote:
On 29 May 2015 at 09:00, Sahid Orentino Ferdjaoui
sahid.ferdja...@redhat.com wrote:
On Fri, May 29, 2015 at 08:47:01AM +0200, Jens Rosenboom wrote:
As the discussion in https
On 29 May 2015 at 17:10, Chris Friesen chris.frie...@windriver.com wrote:
On 05/29/2015 06:27 AM, John Garbutt wrote:
On 27 May 2015 at 23:36, Robert Collins robe...@robertcollins.net wrote:
On 26 May 2015 at 03:37, Chris Friesen chris.frie...@windriver.com
wrote:
Basically the problem
On 26/05/15 13:54 -0400, Nikhil Komawar wrote:
On 5/26/15 12:57 PM, Jesse Cook wrote:
We also had some hallway talk about putting the v1 and v2 APIs on top
of
the v3 API. This forces faster adoption, verifies supportability via v1
and
v2 tests, increases supportability of v1 and v2
On 29 May 2015 at 18:32, Neil Jerram neil.jer...@metaswitch.com wrote:
Hi all,
Per yesterday's IRC meeting [1], and discussion in Vancouver, Nova work is
being somewhat driven by the etherpad at [2]. But this etherpad doesn't
have a section for libvirt / vif driver changes. The log at [1]
On 29 May 2015 at 09:00, Sahid Orentino Ferdjaoui
sahid.ferdja...@redhat.com wrote:
On Fri, May 29, 2015 at 08:47:01AM +0200, Jens Rosenboom wrote:
As the discussion in https://review.openstack.org/179569 still
continues about whether this is just a bug fix, or an API change
that will need a
On 27 May 2015 at 23:36, Robert Collins robe...@robertcollins.net wrote:
On 26 May 2015 at 03:37, Chris Friesen chris.frie...@windriver.com wrote:
Hi all,
I've just opened a bug around booting multiple instances at once, and it was
suggested on IRC that I mention it here to broaden the
On 15 May 2015 at 14:13, Daniel P. Berrange berra...@redhat.com wrote:
On Fri, May 15, 2015 at 12:41:20PM +0100, Matthew Booth wrote:
I was looking at the migrations api, and I noticed that the api passes
the request query unchecked to get_migrations, where it ultimately ends
up in a db query.
On 15 May 2015 at 13:28, Daniel P. Berrange berra...@redhat.com wrote:
On Fri, May 15, 2015 at 11:51:22AM +0100, Daniel P. Berrange wrote:
On Thu, May 14, 2015 at 02:23:25PM -0500, Matt Riedemann wrote:
There are some workarounds in the code [3] I'd like to see removed by
bumping the minimum
On 14 May 2015 at 21:55, Boris Pavlovic bo...@pavlovic.me wrote:
Robert,
So I think we should explicitly leave room for experimentation and
divergence, but also encourage a single common path - don't be
different to be different, be difference because it is important in
this specific case.
On 15 May 2015 at 12:28, Daniel P. Berrange berra...@redhat.com wrote:
One other thing I should have mentioned is that we don't actually have
one single minimum libvirt version. We actually have a couple of different
minimum versions based on either the architecture or the hypervisor.
For
On 15 May 2015 at 17:41, Daniel P. Berrange berra...@redhat.com wrote:
On Fri, May 15, 2015 at 05:27:35PM +0100, John Garbutt wrote:
On 15 May 2015 at 11:51, Daniel P. Berrange berra...@redhat.com wrote:
On Thu, May 14, 2015 at 02:23:25PM -0500, Matt Riedemann wrote:
The minimum required
On 15 May 2015 at 11:51, Daniel P. Berrange berra...@redhat.com wrote:
On Thu, May 14, 2015 at 02:23:25PM -0500, Matt Riedemann wrote:
The minimum required version of libvirt in the driver is 0.9.11 still [1].
We've been gating against 1.2.2 in Ubuntu Trusty 14.04 since Juno.
The libvirt
On 12 May 2015 at 20:33, Sean Dague s...@dague.net wrote:
On 05/12/2015 01:12 PM, Jeremy Stanley wrote:
On 2015-05-12 10:04:11 -0700 (-0700), Clint Byrum wrote:
It's a nice up side. However, as others have pointed out, it's only
capable of displaying the most basic pieces of the architecture.
On 13 May 2015 at 16:48, Dugger, Donald D donald.d.dug...@intel.com wrote:
I’d like to get together to talk about what kind of APIs/requirements
different projects would need from a common scheduler. To that end room 221
is available on Tues. at 3:40PM. If you’re at all interested in a common
On 13 May 2015 at 14:36, Dugger, Donald D donald.d.dug...@intel.com wrote:
Rm 221 on Tues. would be perfect, I'd like to reserve that and I'll send out
an email
to announce we want to talk cross-project scheduler interfaces at that time.
Its possible some of that will come up in this
On 14 May 2015 at 07:18, Manickam, Kanagaraj kanagaraj.manic...@hp.com wrote:
Hi Nova team,
This mail is regarding an help required on the migration from
sqlalchemy migration tool to alembic tool.
Heat is currently using sqlalchemy-migration tool and In liberty release,
we are
On 11 May 2015 at 23:46, Boris Pavlovic bo...@pavlovic.me wrote:
Couldn't we just use real image files to do this. IIRC, gerrit supports
displaying image files which are included in a commit. For example, I've
been
planning to copy these images:
+1 for real images
One suggestion I remember
On 9 May 2015 at 17:55, Adrian Otto adrian.o...@rackspace.com wrote:
On the subject of extending the Nova API to accommodate special use cases of
containers that are beyond the scope of the Nova API, I think we should
resist that, and focus those container-specific efforts in Magnum.
+1
The
Hi,
Thanks for all the summit session submissions. After chewing through
that with all the members of nova-drivers, and during recent
nova-meetings, we have a mostly final list of sessions.
I have uploaded the first draft of the schedule:
On 1 May 2015 at 16:14, Davanum Srinivas dava...@gmail.com wrote:
Anyone still interested in this work? :)
* there's a stable/kilo branch now (see
http://git.openstack.org/cgit/stackforge/nova-docker/).
* CI jobs are running fine against both nova trunk and nova's
stable/kilo branch.
*
On 30 April 2015 at 18:54, Mike Bayer mba...@redhat.com wrote:
On 4/30/15 11:16 AM, Dan Smith wrote:
There is an open discussion to replace mysql-python with PyMySQL, but
PyMySQL has worse performance:
https://wiki.openstack.org/wiki/PyMySQL_evaluation
My major concern with not moving to
I would really to start collecting more of this information.
Maybe my expanding this:
https://github.com/openstack/nova/blob/master/doc/source/support-matrix.ini
http://docs.openstack.org/developer/nova/support-matrix.html
Although it feels like it will need an extra dimention adding,
possibly a
that helps.
Thanks,
John
John
On Wed, May 6, 2015 at 2:55 AM, John Garbutt j...@johngarbutt.com wrote:
On 6 May 2015 at 09:39, Lucas Alvares Gomes lucasago...@gmail.com wrote:
Hi
I noticed last night that there are 23 bugs currently filed in nova
tagged as ironic related. Whilst some of those
On 8 May 2015 at 00:24, Brent Eagles beag...@redhat.com wrote:
Hi,
On Thu, May 07, 2015 at 10:03:30PM +, Sean M. Collins wrote:
On Wed, Apr 22, 2015 at 06:41:58PM EDT, Jay Pipes wrote:
Agreed. I'm hoping that someone in the Nova community -- note, this does
not need to be a Nova core
On 7 May 2015 at 22:52, Joshua Harlow harlo...@outlook.com wrote:
Hi all,
In seeing the following:
- https://review.openstack.org/#/c/169836/
- https://review.openstack.org/#/c/163274/
- https://review.openstack.org/#/c/138607/
Vilobh and I are starting to come to the conclusion that the
On 9 May 2015 at 15:02, Mike Bayer mba...@redhat.com wrote:
On 5/9/15 6:45 AM, John Garbutt wrote:
I am leaning towards us moving to making DB calls with a thread pool and
some fast C based library, so we get the 'best' performance. Is that a crazy
thing to be thinking? What am I missing here
On 30 April 2015 at 12:30, John Garbutt j...@johngarbutt.com wrote:
Hi,
I propose we add Melanie to nova-core.
She has been consistently doing great quality code reviews[1],
alongside a wide array of other really valuable contributions to the
Nova project.
Please respond with comments
On 6 May 2015 at 09:39, Lucas Alvares Gomes lucasago...@gmail.com wrote:
Hi
I noticed last night that there are 23 bugs currently filed in nova
tagged as ironic related. Whilst some of those are scheduler issues, a
lot of them seem like things in the ironic driver itself.
Does the ironic
On Monday, May 4, 2015, Michael Still mi...@stillhq.com wrote:
Hi,
I just wanted to let people know that I am going through abandoning
old specs for Nova at the moment. The criteria I am using is:
- spec targets kilo
- no review comments or other activity since January or February
I
Hi,
In case you were unable to make yesterday's Nova meeting...
If you have a suggestion for a Nova design summit session, please
ensure you add it to before the next Nova meeting (7th May):
https://etherpad.openstack.org/p/liberty-nova-summit-ideas
Shortly after that Nova meeting, the (mostly)
Hi,
Just a quick reminder that blueprints and nova-specs need to be
approved for liberty, even if they have already been approved for a
previous release.
I added deadline in the subject mostly just to get your attention. We
haven't agreed a deadline for spec and blueprint submissions yet, but
Hi,
I propose we add Melanie to nova-core.
She has been consistently doing great quality code reviews[1],
alongside a wide array of other really valuable contributions to the
Nova project.
Please respond with comments, +1s, or objections within one week.
Many thanks,
John
[1]
Thanks for your comments on the patch I see what you are trying to do
now, I think.
However, still a bit concerned about the unit tests, but its probably
easier to discuss that in gerrit.
Thanks,
johnthetubaguy
On 24 April 2015 at 04:25, Rui Chen chenrui.m...@gmail.com wrote:
Hi all:
I'm
I see these changes as really important.
We need to establish good patterns other SDKs can copy.
On 24 April 2015 at 12:05, Alex Xu sou...@gmail.com wrote:
2015-04-24 18:15 GMT+08:00 Andrey Kurilin akuri...@mirantis.com:
When user execute cmd without --os-compute-version. The nova client
On 22 April 2015 at 23:41, Jay Pipes jaypi...@gmail.com wrote:
On 04/22/2015 04:33 PM, Kyle Mestery wrote:
On Wed, Apr 22, 2015 at 3:28 PM, Sean M. Collins s...@coreitpro.com
mailto:s...@coreitpro.com wrote:
Hi,
Kyle Mestery has asked me to serve as a cross-project liaison between
On 16 April 2015 at 18:11, Anthony PERARD anthony.per...@citrix.com wrote:
Hi all,
With libvirt_type=xen, the tempest test
tempest.scenario.test_volume_boot_pattern.TestVolumeBootPattern.test_volume_boot_pattern
fail.
This is because it setup a volume with 'vda' as device_name and nova
On 14 April 2015 at 18:44, Russell Bryant rbry...@redhat.com wrote:
On 04/14/2015 12:22 PM, Matt Riedemann wrote:
This came up in IRC this morning, but the hypervisor support matrix is
listing evacuate as 'missing' for the libvirt driver:
I have updated the bug so it's high priority and tagged with
kilo-rc-potential, and added your note from below as a comment on the bug.
It looks like it might be worth a backport so it gets into RC2? Can anyone
take that bit on please?
Thanks,
John
On Sunday, April 12, 2015, Gary Kotton
On 8 April 2015 at 21:19, Anita Kuno ante...@anteaya.info wrote:
On 04/08/2015 02:25 PM, John Garbutt wrote:
Hi,
I am johnthetubaguy on IRC.
I would like to run for the OpenStack Compute (Nova) PTL position.
I currently work as a Principal Engineer at Rackspace, focusing on
software
Hi,
I am johnthetubaguy on IRC.
I would like to run for the OpenStack Compute (Nova) PTL position.
I currently work as a Principal Engineer at Rackspace, focusing on
software development for the Rackspace public cloud.
Background
==
I started working with Nova in late 2010, working on
Generally the VM is powered down, then has the additional resources
added (such as increasing the size of the disk), then is started back
up again.
There have been some suggested blueprints/specs for a live resize,
where thats possible. But I have not seen any work on that recently,
as far as I
On 21 March 2015 at 18:12, Joe Gordon joe.gord...@gmail.com wrote:
On Sat, Mar 21, 2015 at 8:31 AM, Monty Taylor mord...@inaugust.com wrote:
On 03/21/2015 01:21 AM, Chris Friesen wrote:
Hi,
I've recently been playing around a bit with API microversions and I
noticed something that may be
On 16 March 2015 at 14:15, Sean Dague s...@dague.net wrote:
Our current top level shipped example paste.ini for Nova includes the
following set of endpoint definitions:
[composite:osapi_compute]
use = call:nova.api.openstack.urlmap:urlmap_factory
/: oscomputeversions
/v1.1:
On 12 March 2015 at 12:26, Luis Tomas l...@cs.umu.se wrote:
On 03/12/2015 12:34 PM, John Garbutt wrote:
On 12 March 2015 at 08:41, Luis Tomas l...@cs.umu.se wrote:
Hi,
As part of an European (FP7) project, named ORBIT
(http://www.orbitproject.eu/), I'm working on including the possibility
Hi,
On 11 March 2015 at 06:35, Kekane, Abhishek abhishek.kek...@nttdata.com wrote:
In case of start/stop API’s cpu/memory are not released/reassigned. We can
modify these API’s to release
the cpu and memory while stopping the instance and reassign the same while
starting the instance. In this
Hi,
Just a quick update on where we are at with the release:
https://wiki.openstack.org/wiki/Kilo_Release_Schedule
Please help review all the code we want to merge before FeatureFreeze:
https://etherpad.openstack.org/p/kilo-nova-priorities-tracking
https://launchpad.net/nova/+milestone/kilo-3
Hi,
I think I agree with Jay here, but let me explain...
On 8 March 2015 at 12:10, Alex Xu sou...@gmail.com wrote:
Thanks for Jay point this out! If we have agreement on this and document it,
that will be great for guiding developer how to add new API.
+1
Please could you submit a dev ref
Hi,
I would really like to help make these logging improvements a reality.
On 5 March 2015 at 12:13, Kuvaja, Erno kuv...@hp.com wrote:
We had our first logging workgroup meeting [1] yesterday where we agreed 3
main priorities for the group to focus on.
This time really doesn't work for me I
Hi,
So we have now released kilo-2 and past the non-priority Feature
Freeze for kilo.
Please note 5th March is the General FeatureProposalFreeze:
https://wiki.openstack.org/wiki/Kilo_Release_Schedule
For kilo we agreed to focus on bug fixes, and the other agreed
priority 'slots'. The plan is we
Hi,
Thanks for this updates. Thats super useful.
On 28 January 2015 at 13:21, Gary Kotton gkot...@vmware.com wrote:
Ephemeral disk support -
https://blueprints.launchpad.net/nova/+spec/vmware-ephemeral-disk-support
I have made that medium, to raise it above the others.
The following BP’s
Hi,
In kilo we agreed to focus more on stability and technical debt
related work. As such...
If your code is *not* on this list of kilo priorities:
http://specs.openstack.org/openstack/nova-specs/priorities/kilo-priorities.html
Then the following dates apply (as previously announced)...
22nd
Hi all,
With the release of kilo-1 we have frozen the approval of new specs for kilo.
This is to make sure we can focus on our agreed kilo priorities:
http://specs.openstack.org/openstack/nova-specs/priorities/kilo-priorities.html
As always, there are exceptions, here is how:
1) email ML,
On 20 November 2014 09:32, Flavio Percoco fla...@redhat.com wrote:
On 20/11/14 20:17 +1100, Michael Still wrote:
Hi,
as discussed at the summit, we want to do a better job of tracking the
progress of work on our priorities for Kilo. To that end, we have
agreed to discuss the current state
On 20 November 2014 09:25, Sylvain Bauza sba...@redhat.com wrote:
Le 20/11/2014 10:17, Michael Still a écrit :
Hi,
as discussed at the summit, we want to do a better job of tracking the
progress of work on our priorities for Kilo. To that end, we have
agreed to discuss the current state of
On 11/11/2014 3:04 PM, Andrew Laski wrote:
We had a great discussion on cells at the summit which is captured at
https://etherpad.openstack.org/p/kilo-nova-cells. One of the tasks we
agreed upon there was to form a subgroup to co-ordinate this effort
and
report progress to the Nova meeting
On 17 October 2014 02:28, Matt Riedemann mrie...@linux.vnet.ibm.com wrote:
On 10/16/2014 7:26 PM, Christopher Aedo wrote:
On Tue, Sep 9, 2014 at 2:19 PM, Mike Scherbakov
mscherba...@mirantis.com wrote:
On Tue, Sep 9, 2014 at 6:02 PM, Clint Byrum cl...@fewbar.com wrote:
The idea is not
Hi,
I would like to run for a seat on the Technical Committee, to help
serve the whole OpenStack community during this time of change.
I am employed by Rackspace, working on their public cloud. I am
currently focus mostly on Nova. I am nova-core, and currently nova's
blueprint czar. I am
there's really no reason that an approved Juno spec should not be
reapproved.
Chris
Thanks
Gary
On 9/29/14, 1:07 PM, John Garbutt j...@johngarbutt.com wrote:
On 27 September 2014 00:31, Joe Gordon joe.gord...@gmail.com
wrote:
On Thu, Sep 25, 2014 at 9:21 AM, John Garbutt
On 30 September 2014 14:04, joehuang joehu...@huawei.com wrote:
Hello, Dear TC and all,
Large cloud operators prefer to deploy multiple OpenStack instances(as
different zones), rather than a single monolithic OpenStack instance because
of these reasons:
1) Multiple data centers
On 27 September 2014 00:31, Joe Gordon joe.gord...@gmail.com wrote:
On Thu, Sep 25, 2014 at 9:21 AM, John Garbutt j...@johngarbutt.com wrote:
On 25 September 2014 14:10, Daniel P. Berrange berra...@redhat.com
wrote:
The proposal is to keep kilo-1, kilo-2 much the same as juno. Except,
we
201 - 300 of 446 matches
Mail list logo
