Hello,
we are finishing up the development of the Spark plugin for Savanna.
In the next few days we will deploy it on an OpenStack cluster with real
users to iron out the last few things. Hopefully next week we will put
the code on a public github repository in beta status.
You can find the b
On Thu, Jan 9, 2014 at 2:35 PM, 黎林果 wrote:
> Hi Chris,
> Thanks for you reply.
>
> It's not only hard coded for swap volumes. In function
> '_create_instance' which for creating instance of nova/compute/api.py,
> the '_prepare_image_mapping' function will be called. And it hard code
> to True, to
Hi Eric,
I tried running the 'docker run' command without -d and it gets following
error
$ sudo docker run -d=false -p 5042:5000 -e SETTINGS_FLAVOR=openstack -e
OS_USERNAME=admin -e OS_PASSWORD=password -e OS_TENANT_NAME=admin -e
OS_GLANCE_URL=http://127.0.0.1:9292 -e OS_AUTH_URL=
http://127.0.0.
Hi Chris,
Thanks for you reply.
It's not only hard coded for swap volumes. In function
'_create_instance' which for creating instance of nova/compute/api.py,
the '_prepare_image_mapping' function will be called. And it hard code
to True, too.
values = block_device.BlockDeviceDict({
Is there any way to have WSME pass through arbitrary attributes to the created
object? There is nothing that i can see in the documentation or code that would
seem to support this.
In keystone we have the situation where arbitrary data was able to be attached
to our resources. For example ther
On Wed, 2014-01-08 at 18:46 -0800, Sukhdev Kapur wrote:
> Dear fellow developers,
> I am running few Neutron tempest tests and noticing an intermittent
> failure of tempest.scenario.test_network_basic_ops.
> I ran this test 50+ times and am getting intermittent failure. The
> pass rate is apps.
We are working on cleaning up the Keystone code with an eye to Oslo and
reuse:
https://review.openstack.org/#/c/56333/
On 01/08/2014 02:47 PM, Georgy Okrokvertskhov wrote:
Hi,
Keep policy control in one place is a good idea. We can use standard
policy approach and keep access control configu
Can you include the following in the agenda?
1. External/3rd Party testing
2. Common code for collecting status/statistics
From: Eugene Nikanorov [mailto:enikano...@mirantis.com]
Sent: Wednesday, January 08, 2014 7:58 PM
To: OpenStack Development Mailing List
Subject: [openstack-dev
Hi, guys.
> jay wrote:
> > So you are saying that the Synaps server is storing 14,400,000 samples
> > in memory (2 days of 5000 samples per minute)? Or are you saying that
> > Synaps is storing just the 5000 alarm records in memory and then
> > processing (determining if the alarm condition was me
On Thu, Jan 9, 2014 at 9:25 AM, 黎林果 wrote:
> Hi All,
>
>Attach a volume when creating a server, the API contains
> 'block_device_mapping', such as:
> "block_device_mapping": [
> {
> "volume_id": "",
> "device_name": "/dev/vdc",
> "de
Dear fellow developers,
I am running few Neutron tempest tests and noticing an intermittent failure
of tempest.scenario.test_network_basic_ops.
I ran this test 50+ times and am getting intermittent failure. The pass
rate is apps. 70%. The 30% of the time it fails mostly in
_check_public_network_c
Hi all,
The [state-management] project team holds a weekly meeting in
#openstack-meeting on thursdays, 2000 UTC. The next meeting is tommorow,
2014-01-09!!!
As usual, everyone is welcome :-)
Link: https://wiki.openstack.org/wiki/Meetings/StateManagement
Taskflow: https://wiki.openstack.org
Clint & Steve
One scenario we are trying to see is whether and how Heat software-config
enables deployment of images available from third party as virtual
appliances, providing network, security or acceleration capabilities. The
vendor in some cases might not allow rebuilding and/or may not hav
Hi All,
Attach a volume when creating a server, the API contains
'block_device_mapping', such as:
"block_device_mapping": [
{
"volume_id": "",
"device_name": "/dev/vdc",
"delete_on_termination": "true"
}
]
It allows the op
Hi folks
OpenStack process tend to have many config options, and many hosts.
It is a pain to manage this tons of config options.
To centralize this management helps operation.
We can use chef or puppet kind of tools, however
sometimes each process depends on the other processes configuration.
For
Rick,
Thanks for your response.
I make another testing to upload my iso to my ESXi host directly, the speed
is much faster now, avg is more than 40 MB/s. By the way, 200.21.0.99 is my
vcenter server.
I will keep you update if I have some new found. Thanks a lot.
Best Regards
-- Ray
On Thu, Jan
Hi,
Here is how we are doing this for Solum:
Keystone auth:
https://github.com/stackforge/solum/blob/master/solum/api/auth.py
Additional Hook: https://review.openstack.org/#/c/64458/ (auth.py for hook
code and config.py for hooks)
Here is an e-mail thread with discussion:
http://lists.openstack.
2014/1/9 Russell Bryant
> On 01/08/2014 09:53 AM, John Garbutt wrote:
> > On 8 January 2014 10:02, David Xie wrote:
> >> In nova/compute/api.py#2289, function resize, there's a parameter named
> >> flavor_id, if it is None, it is considered as cold migration. Thus, nova
> >> should skip resize v
I need to add an additional layer of authorization between auth_token and
the reporting API.
I know it's as simple as creating a WSGI element and adding it to the
pipeline. Examining the code I haven't figured out where to begin doing
this.
I'm not using Apache and mod_wsgi, just the rep
Hi All,
As you know the gate has been in particularly bad shape (gate queue over
100!) this week due to a number of factors. One factor is how many major
outstanding bugs we have in the gate. Below is a list of the top 4 open
gate bugs.
Here are some fun facts about this list:
* All bugs have be
On 1/8/2014 12:40 PM, Joe Gordon wrote:
On Jan 8, 2014 7:12 AM, "Matt Riedemann" mailto:mrie...@linux.vnet.ibm.com>> wrote:
>
> I'd like to propose that we add another item to the list here [1]
that is basically related to what happens when the 3rd party CI job
votes a -1 on your patch. Thi
Greetings Stackers!
The VMwareAPI subteam had a two week break from meetings. So happy new
year to all! I hope everyone had a nice break. The Icehouse-2
milestone is coming up January 23rd! That means if you have a patch in
flight right now we need to get you ready for core-reviewers in the
next 2
- Original Message -
> From: "Jay Pipes"
> To: openstack-dev@lists.openstack.org
> Sent: Wednesday, January 8, 2014 2:29:22 PM
> Subject: Re: [openstack-dev] [Neutron] Multiple config files for neutron
> server
>
> On Wed, 2014-01-08 at 07:21 -0500, Sean Dague wrote:
> > On 01/06/2014
Currently I know, alessandro pilotti has done work and has heat templates for
Windows instances, including deploying ad nodes, exchange and SharePoint.
P
Sent from my Verizon Wireless 4G LTE Smartphone
Original message
From: "Chan, Winson C"
Date:01/08/2014 3:47 PM (GMT-05:00
We're in agreement. What little entry there might be in a system of such
a small size would be entirely manageable by a single administrator...
I care about that deployment, deeply, as that is how things like OpenStack
take root in IT departments.. with somebody playing around. However, what
I car
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_January.2C_9
http://www.timeanddate.com/worldclock/fixedtime.html?msg=Savanna+Meeting&iso=20140109T18
--
Sincerely yours,
Ser
Hi Doug,
OK, so like I said, we did not design the system with the idea that a user of
the cloud (rather than the deployer of the cloud) would have any control over
what data was collected. They can ask questions about only some of the data,
but they can't tell ceilometer what to collect.
There
Does anybody know if this blueprint is being actively work on?
https://blueprints.launchpad.net/heat/+spec/windows-instances If this is not
active, can I take ownership of this blueprint? My team wants to add support
for Windows in Heat for our internal deployment.
_
On Wed, Jan 8, 2014 at 3:09 PM, Kodam, Vijayakumar (EXT-Tata Consultancy
Ser - FI/Espoo) wrote:
>>
>
>
> >
> >From: ext Doug Hellmann [doug.hellm...@dreamhost.com]
> >Sent: Wednesday, January 08, 2014 8:26 PM
On Wed, Jan 8, 2014 at 2:08 PM, Tim Bell wrote:
>
>
> Thanks for the clarifications. Given the role descriptions as provided, I
> no longer think there is a need for an API call or per project meter
> enable/disable. Thus, the inotify approach would seem to be viable (and
> much simpler to implem
On 2014-01-07 07:17:58 -0500 (-0500), Sean Dague wrote:
> This looks like it's a 100% failure bug at this point. I expect that
> because of timing it's based on a change in the base image due to
> nodepool rebuilding.
Actually not... Nova's Python 2.7 unit tests don't run on
nodepool-managed worke
>
>
>From: ext Doug Hellmann [doug.hellm...@dreamhost.com]
>Sent: Wednesday, January 08, 2014 8:26 PM
>To: OpenStack Development Mailing List (not for usage questions)
>Subject: Re: [openstack-dev] [Ceilometer] Dy
Note that, per the most recent updates in the bug, netaddr has
started uploading their releases to PyPI again so we should
hopefully be able to revert any workarounds we added for it. This
unfortunately does not hold true for other requirements of some
projects (netifaces in swift, lazr.restful in
Hi,
Keep policy control in one place is a good idea. We can use standard policy
approach and keep access control configuration in json file as it done in
Nova and other projects.
Keystone uses wrapper function for methods. Here is a wrapper code:
https://github.com/openstack/keystone/blob/master/k
On Wed, Jan 8, 2014 at 10:43 AM, Eric Windisch
wrote:
About spur: spur is looks ok, but it a bit complicated inside (it uses
separate threads for non-blocking stdin/stderr reading [1]) and I
don't
know how it would work with eventlet.
That does sound like it might cause is
On Wed, 2014-01-08 at 07:21 -0500, Sean Dague wrote:
> On 01/06/2014 02:58 PM, Jay Pipes wrote:
> > On Mon, 2014-01-06 at 23:45 +0400, Eugene Nikanorov wrote:
> >> Hi folks,
> >>
> >>
> >> Recently we had a discussion with Sean Dague on the matter.
> >> Currently Neutron server has a number of conf
On Wed, 2014-01-08 at 14:26 +0100, Thierry Carrez wrote:
> Tim Bell wrote:
> > +1 from me too UpgradeImpact is a much better term.
>
> So this one is already documented[1], but I don't know if it actually
> triggers anything yet.
>
> Should we configure it to post to openstack-operators, the
Thanks for the clarifications. Given the role descriptions as provided, I no
longer think there is a need for an API call or per project meter
enable/disable. Thus, the inotify approach would seem to be viable (and much
simpler to implement since the state is clearly defined across daemon rest
On Jan 8, 2014 7:12 AM, "Matt Riedemann" wrote:
>
> I'd like to propose that we add another item to the list here [1] that is
basically related to what happens when the 3rd party CI job votes a -1 on
your patch. This would include:
>
> 1. Documentation on how to analyze the results and a good ove
On 1/7/14 2:53 PM, Michael Still wrote:
Hi. Thanks for reaching out about this.
It seems this patch has now passed turbo hipster, so I am going to
treat this as a more theoretical question than perhaps you intended. I
should note though that Joshua Hesketh and I have been trying to read
/ triage
On Wed, Jan 8, 2014 at 12:35 PM, Ildikó Váncsa
wrote:
> Hi Doug,
>
>
>
> Answers inline again.
>
>
>
> Best Regards,
>
> Ildiko
>
>
>
> On Wed, Jan 8, 2014 at 3:16 AM, Ildikó Váncsa
> wrote:
>
> Hi,
>
> I've started to work on the idea of supporting a kind of tenant/project
> based configuration
On Wed, Jan 8, 2014 at 12:37 PM, Ben Nemec wrote:
> On 2014-01-08 11:16, Sean Dague wrote:
>
>> On 01/08/2014 12:06 PM, Doug Hellmann wrote:
>>
>>
>>> Yeah, that's what made me start thinking oslo.sphinx should be called
>>> something else.
>>>
>>> Sean, how strongly do you feel about not instal
Hi,
> > My idea was just about providing the possibility to configure the data
> > collection in Ceilometer differently for the different tenants, I
> > didn't mean to link it to an API or at least not on the first place.
> > It could be done by the operator as well, for instance, if the pollin
On Mon, Jan 6, 2014 at 3:50 PM, Jon Bernard wrote:
> Hello all,
>
> I would like to propose instance-level snapshots as a feature for
> inclusion in Nova. An initial draft of the more official proposal is
> here [1], blueprint is here [2].
>
> In a nutshell, this feature will take the existing c
On Wed, Jan 8, 2014 at 11:02 PM, Sean Dague wrote:
> On 01/08/2014 11:40 AM, Noorul Islam Kamal Malmiyoda wrote:
>>
>> On Jan 8, 2014 9:58 PM, "Georgy Okrokvertskhov"
>> mailto:gokrokvertsk...@mirantis.com>> wrote:
>>>
>>> Hi,
>>>
>>> I do understand why there is a push back for this patch. This p
On Wed, Jan 08 2014, Ildikó Váncsa wrote:
> My idea was just about providing the possibility to configure the data
> collection in Ceilometer differently for the different tenants, I didn't
> mean to link it to an API or at least not on the first place. It could be
> done by the operator as well,
Hi,
(You didn't Cc the list, not sure if it was on purpose. I'm not adding it back
to not break any confidentiality, but feel free to do so.)
Sorry that was just a mistake.
> > The point is to configure the data collection configuration for the
> > currently existing meters differently for ten
On 2014-01-08 11:16, Sean Dague wrote:
On 01/08/2014 12:06 PM, Doug Hellmann wrote:
Yeah, that's what made me start thinking oslo.sphinx should be called
something else.
Sean, how strongly do you feel about not installing oslo.sphinx in
devstack? I see your point, I'm just looking for alternat
Hi Doug,
Answers inline again.
Best Regards,
Ildiko
On Wed, Jan 8, 2014 at 3:16 AM, Ildikó Váncsa
mailto:ildiko.van...@ericsson.com>> wrote:
Hi,
I've started to work on the idea of supporting a kind of tenant/project based
configuration for Ceilometer. Unfortunately I haven't reached the poin
The logic makes sense to me here. I’m including Evan Callicoat in this response
in case he has any comments on the points you make below.
Vish
On Jan 7, 2014, at 4:57 AM, Ian Wells wrote:
> See Sean Collins' review https://review.openstack.org/#/c/56381 which
> disables hairpinning when Neut
On 01/08/2014 11:40 AM, Noorul Islam Kamal Malmiyoda wrote:
>
> On Jan 8, 2014 9:58 PM, "Georgy Okrokvertskhov"
> mailto:gokrokvertsk...@mirantis.com>> wrote:
>>
>> Hi,
>>
>> I do understand why there is a push back for this patch. This patch is
> for infrastructure project which works for multipl
On Jan 6, 2014, at 3:50 PM, Jon Bernard wrote:
> Hello all,
>
> I would like to propose instance-level snapshots as a feature for
> inclusion in Nova. An initial draft of the more official proposal is
> here [1], blueprint is here [2].
>
> In a nutshell, this feature will take the existing cr
Let me give you a more concrete example, since you still think one size fits
all here.
I am using OpenStack on my home server now. In the past, I had one machine with
lots of services on it. At times, I would update one service and during the
update process, a different service would break.
La
On 01/08/2014 12:06 PM, Doug Hellmann wrote:
> Yeah, that's what made me start thinking oslo.sphinx should be called
> something else.
>
> Sean, how strongly do you feel about not installing oslo.sphinx in
> devstack? I see your point, I'm just looking for alternatives to the
> hassle of renamin
Excerpts from Jan Provaznik's message of 2014-01-08 03:00:19 -0800:
> On 01/07/2014 09:01 PM, James Slagle wrote:
> > Hi,
> >
> > I'd like to discuss some possible ways we could install the OpenStack
> > components from packages in tripleo-image-elements. As most folks are
> > probably aware, ther
On 01/07/2014 06:30 PM, Ray Sun wrote:
Stackers,
I tried to create a new VM using the driver VMwareVCDriver, but I found
it's very slow when I try to create a new VM, for example, 7GB Windows
Image spent 3 hours.
Then I tried to use curl to upload a iso to vcenter directly.
curl -H "Expect:" -v
Yeah, that could work. The main thing is to try and keep policy control in one
place if you can rather than sprinkling it all over the place.
From: Georgy Okrokvertskhov
mailto:gokrokvertsk...@mirantis.com>>
Reply-To: OpenStack Dev
mailto:openstack-dev@lists.openstack.org>>
Date: Wednesday, Jan
On Wed, Jan 8, 2014 at 11:53 AM, Ben Nemec wrote:
> On 2014-01-08 10:50, Doug Hellmann wrote:
>
>
>
>
> On Wed, Jan 8, 2014 at 11:31 AM, Ben Nemec wrote:
>
>> On 2014-01-08 08:24, Doug Hellmann wrote:
>>
>>
>>
>>
>> On Tue, Jan 7, 2014 at 12:32 PM, Ben Nemec wrote:
>>
>>> On 2014-01-07 07:16
On 2014-01-08 10:50, Doug Hellmann wrote:
> On Wed, Jan 8, 2014 at 11:31 AM, Ben Nemec wrote:
>
> On 2014-01-08 08:24, Doug Hellmann wrote:
>
> On Tue, Jan 7, 2014 at 12:32 PM, Ben Nemec wrote:
>
> On 2014-01-07 07:16, Doug Hellmann wrote:
>
> On Tue, Jan 7, 2014 at 6:24 AM, Michael Ke
Excerpts from Jay Dobies's message of 2014-01-08 08:09:51 -0800:
> There were so many places in this thread that I wanted to jump in on as
> I caught up, it makes sense to just summarize things in once place
> instead of a half dozen quoted replies.
>
> I agree with the sentiments about flexibil
Excerpts from James Slagle's message of 2014-01-08 07:03:39 -0800:
> On Tue, Jan 7, 2014 at 11:20 PM, Robert Collins
> wrote:
> > On 8 January 2014 12:18, James Slagle wrote:
> >> Sure, the crux of the problem was likely that versions in the distro
> >> were too old and they needed to be updated.
On Wed, Jan 8, 2014 at 11:31 AM, Ben Nemec wrote:
> On 2014-01-08 08:24, Doug Hellmann wrote:
>
>
>
>
> On Tue, Jan 7, 2014 at 12:32 PM, Ben Nemec wrote:
>
>> On 2014-01-07 07:16, Doug Hellmann wrote:
>>
>>
>>
>>
>> On Tue, Jan 7, 2014 at 6:24 AM, Michael Kerrin wrote:
>>
>>> I have been seei
On Wed, Jan 8, 2014 at 10:19 AM, Doug Hellmann
wrote:
>
>
>
> On Wed, Jan 8, 2014 at 9:34 AM, Sergey Skripnick
> wrote:
>
>>
>>
>>
I'd like to explore whether the paramiko team will accept this code (or
something like it). This seems like a perfect opportunity for us to
contribute
On Wed, Jan 8, 2014 at 10:43 AM, Eric Windisch wrote:
>
>>
>>> About spur: spur is looks ok, but it a bit complicated inside (it uses
>>> separate threads for non-blocking stdin/stderr reading [1]) and I don't
>>> know how it would work with eventlet.
>>>
>>
>> That does sound like it might cause
On 2014-01-08 08:24, Doug Hellmann wrote:
> On Tue, Jan 7, 2014 at 12:32 PM, Ben Nemec wrote:
>
> On 2014-01-07 07:16, Doug Hellmann wrote:
>
> On Tue, Jan 7, 2014 at 6:24 AM, Michael Kerrin wrote:
>
> I have been seeing this problem also.
>
> My problem is actually with oslo.sphinx. I
On 01/08/2014 09:53 AM, John Garbutt wrote:
> On 8 January 2014 10:02, David Xie wrote:
>> In nova/compute/api.py#2289, function resize, there's a parameter named
>> flavor_id, if it is None, it is considered as cold migration. Thus, nova
>> should skip resize verifying. However, it doesn't.
>>
>>
Hi Kurt,
As for WSGI middleware I think about Pecan hooks which can be added before
actual controller call. Here is an example how we added a hook for keystone
information collection:
https://review.openstack.org/#/c/64458/4/solum/api/auth.py
What do you think, will this approach with Pecan hooks
On Jan 8, 2014 9:58 PM, "Georgy Okrokvertskhov" <
gokrokvertsk...@mirantis.com> wrote:
>
> Hi,
>
> I do understand why there is a push back for this patch. This patch is
for infrastructure project which works for multiple projects. Infra
maintainers should not know specifics of each project in deta
On Wed, Jan 8, 2014 at 11:16 AM, Ildikó Váncsa
wrote:
> Hi Doug,
>
>
>
> See my answers inline.
>
>
>
> Best Regards,
>
> Ildiko
>
>
>
> *From:* Doug Hellmann [mailto:doug.hellm...@dreamhost.com]
> *Sent:* Wednesday, January 08, 2014 4:10 PM
>
> *To:* OpenStack Development Mailing List (not for u
Excerpts from Derek Higgins's message of 2014-01-08 02:11:09 -0800:
> On 08/01/14 05:07, Clint Byrum wrote:
> > Excerpts from Fox, Kevin M's message of 2014-01-07 16:27:35 -0800:
> >> Another piece to the conversation I think is update philosophy. If
> >> you are always going to require a new image
On Wed, Jan 08 2014, Ildikó Váncsa wrote:
(Your answers are very hard to read inline in my text MUA, it'd really
help if you could quote properly with > the emails you answer to).
> ildikov: Sorry, my explanation was not clear. I meant there the
> configuration of data collection for projects, wh
Hi,
I do understand why there is a push back for this patch. This patch is for
infrastructure project which works for multiple projects. Infra maintainers
should not know specifics of each project in details. If this patch is a
temporary solution then who will be responsible to remove it?
If we n
On Wed, Jan 08 2014, Kodam, Vijayakumar (EXT-Tata Consultancy Ser - FI/Espoo)
wrote:
> According to the latest update:
> User calls the API(1) to disable a meter along with a meter id.
What's an user? An end-user or an operator?
I don't think we want to allow a user to disable a meter. I don't
Hi Doug,
See my answers inline.
Best Regards,
Ildiko
From: Doug Hellmann [mailto:doug.hellm...@dreamhost.com]
Sent: Wednesday, January 08, 2014 4:10 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Ceilometer] Dynamic Meters in Ceilometer
On We
There were so many places in this thread that I wanted to jump in on as
I caught up, it makes sense to just summarize things in once place
instead of a half dozen quoted replies.
I agree with the sentiments about flexibility. Regardless of my personal
preference on source v. packages, it's bee
From: ext Tim Bell [mailto:tim.b...@cern.ch]
Sent: Tuesday, January 07, 2014 8:22 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Ceilometer] Dynamic Meters in Ceilometer
Thinking using inotify/configuration file changes to implement dynamic met
Hi,
>-Original Message-
>From: ext Neal, Phil [mailto:phil.n...@hp.com]
>Sent: Wednesday, January 08, 2014 12:50 AM
>To: OpenStack Development Mailing List (not for usage questions)
>Subject: Re: [openstack-dev] [Ceilometer] Dynamic Meters in Ceilometer
>
>
>For multi-node deployments, im
>
>
>
>> About spur: spur is looks ok, but it a bit complicated inside (it uses
>> separate threads for non-blocking stdin/stderr reading [1]) and I don't
>> know how it would work with eventlet.
>>
>
> That does sound like it might cause issues. What would we need to do to
> test it?
>
Looking at
在 2014年1月8日，20:24，Nir Yechiel 写道：
> Hi Dong,
>
> Can you please clarify this blueprint? Currently in Neutron, If an instance
> has a floating IP, then that will be used for both inbound and outbound
> traffic. If an instance does not have a floating IP, it can make connections
> out using th
2014/1/8 John Garbutt
> On 8 January 2014 10:02, David Xie wrote:
> > In nova/compute/api.py#2289, function resize, there's a parameter named
> > flavor_id, if it is None, it is considered as cold migration. Thus, nova
> > should skip resize verifying. However, it doesn't.
> >
> > Like Jay said,
On Wed, Jan 8, 2014 at 9:34 AM, Sergey Skripnick wrote:
>
>
>
>>> I'd like to explore whether the paramiko team will accept this code (or
>>> something like it). This seems like a perfect opportunity for us to
>>> contribute
>>> upstream.
>>>
>>
>> +1
>>
>> The patch is not big and the code seems
Thanks Russell, OK, will file a bug for first issue.
For second question, I want to show some of my comments here. I think that
we should disable cold migration for an ACTIVE VM as cold migrating will
first destroy the VM then re-create the VM when using KVM, I did not see a
use case why someone w
Anne Gentle writes:
> On Wed, Jan 8, 2014 at 8:26 AM, Noorul Islam Kamal Malmiyoda <
> noo...@noorul.com> wrote:
>
>>
>> On Jan 8, 2014 6:11 PM, "Sean Dague" wrote:
>> >
>> > On 01/07/2014 11:27 PM, Noorul Islam Kamal Malmiyoda wrote:
>> > > On Wed, Jan 8, 2014 at 9:43 AM, Georgy Okrokvertskhov
On Wed, Jan 8, 2014 at 3:16 AM, Ildikó Váncsa wrote:
> Hi,
>
> I've started to work on the idea of supporting a kind of tenant/project
> based configuration for Ceilometer. Unfortunately I haven't reached the
> point of having a blueprint that could be registered until now. I do not
> have a deep
On Tue, Jan 7, 2014 at 11:20 PM, Robert Collins
wrote:
> On 8 January 2014 12:18, James Slagle wrote:
>> Sure, the crux of the problem was likely that versions in the distro
>> were too old and they needed to be updated. But unless we take on
>> building the whole OS from source/git/whatever eve
I'd like to propose that we add another item to the list here [1] that
is basically related to what happens when the 3rd party CI job votes a
-1 on your patch. This would include:
1. Documentation on how to analyze the results and a good overview of
what the job does (like the docs we have fo
On Wednesday, 8 January, 2014 at 22:53, John Garbutt wrote:
> On 8 January 2014 10:02, David Xie (mailto:david.script...@gmail.com)> wrote:
> > In nova/compute/api.py#2289, function resize, there's a parameter named
> > flavor_id, if it is None, it is considered as cold migration. Thus, nova
> > s
On 01/08/2014 09:48 AM, Matt Riedemann wrote:
Another question. This patch [1] failed turbo-hipster after it was
approved but I don't know if that's a gating or just voting job, i.e.
should someone do 'reverify migrations' on that patch or just let it sit
and ignore turbo-hipster?
[1] https:
On Tue, Jan 7, 2014 at 11:13 PM, Swapnil Kulkarni <
swapnilkulkarni2...@gmail.com> wrote:
> Let me know in case I can be of any help getting this resolved.
>
Please try running the failing 'docker run' command manually and without
the '-d' argument. I've been able to reproduce an error myself, b
On Wed, Jan 8, 2014 at 8:26 AM, Noorul Islam Kamal Malmiyoda <
noo...@noorul.com> wrote:
>
> On Jan 8, 2014 6:11 PM, "Sean Dague" wrote:
> >
> > On 01/07/2014 11:27 PM, Noorul Islam Kamal Malmiyoda wrote:
> > > On Wed, Jan 8, 2014 at 9:43 AM, Georgy Okrokvertskhov
> > > wrote:
> > >> Should we r
From: Ray Sun mailto:xiaoq...@gmail.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Wednesday, January 8, 2014 4:09 PM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.op
On 8 January 2014 10:02, David Xie wrote:
> In nova/compute/api.py#2289, function resize, there's a parameter named
> flavor_id, if it is None, it is considered as cold migration. Thus, nova
> should skip resize verifying. However, it doesn't.
>
> Like Jay said, we should skip this step during col
On 01/08/2014 09:26 AM, Noorul Islam Kamal Malmiyoda wrote:
On Jan 8, 2014 6:11 PM, "Sean Dague" mailto:s...@dague.net>> wrote:
>
> On 01/07/2014 11:27 PM, Noorul Islam Kamal Malmiyoda wrote:
> > On Wed, Jan 8, 2014 at 9:43 AM, Georgy Okrokvertskhov
> > mailto:gokrokvertsk...@mirantis.com>>
On 01/08/2014 04:52 AM, Jay Lau wrote:
> Greetings,
>
> I have a question related to cold migration.
>
> Now in OpenStack nova, we support live migration, cold migration and resize.
>
> For live migration, we do not need to confirm after live migration finished.
>
> For resize, we need to confi
On Tuesday, January 07, 2014 4:53:01 PM, Michael Still wrote:
Hi. Thanks for reaching out about this.
It seems this patch has now passed turbo hipster, so I am going to
treat this as a more theoretical question than perhaps you intended. I
should note though that Joshua Hesketh and I have been
I'd like to explore whether the paramiko team will accept this code (or
something like it). This seems like a perfect opportunity for us to
contribute
upstream.
+1
The patch is not big and the code seems simple and reasonable enough
to live within paramiko.
Cheers,
FF
I sent a pull
Hi neutrons,
Lets continue keeping our regular lbaas meetings. Let's gather on
#openstack-meeting at 14-00 UTC on this Thursday, 09.01.2014.
We'll discuss our progress and future plans.
Thanks,
Eugene.
___
OpenStack-dev mailing list
OpenStack-dev@lists
On Tue, Jan 7, 2014 at 12:32 PM, Ben Nemec wrote:
> On 2014-01-07 07:16, Doug Hellmann wrote:
>
>
>
>
> On Tue, Jan 7, 2014 at 6:24 AM, Michael Kerrin wrote:
>
>> I have been seeing this problem also.
>>
>> My problem is actually with oslo.sphinx. I ran sudo pip install -r
>> test-requirements.
On Jan 8, 2014 6:11 PM, "Sean Dague" wrote:
>
> On 01/07/2014 11:27 PM, Noorul Islam Kamal Malmiyoda wrote:
> > On Wed, Jan 8, 2014 at 9:43 AM, Georgy Okrokvertskhov
> > wrote:
> >> Should we rather revert patch to make gate working?
> >>
> >
> > I think it is always good to have test packages re
Gary,
Thanks. Curretly, our upload speed is in the normal range?
Best Regards
-- Ray
On Wed, Jan 8, 2014 at 4:31 PM, Gary Kotton wrote:
> 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.
> Th
1 - 100 of 123 matches
Mail list logo
