Excerpts from Jay Pipes's message of 2014-01-07 21:26:44 -0800:
> On Wed, 2014-01-08 at 17:20 +1300, 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.
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
knowledge about the collector and compute agent services, but
Dear PTL,
I am working on a commit 'Deploy VMware vCenter templates' which was -2 in
Havana due to feature freeze. Could you please help to remove the -2 so as
we can move on?
https://review.openstack.org/#/c/34903/
Thanks!
Best Regards
---
Meng Qing Xin___
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 between
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
I feel that we are getting quite far away from supporting my use case. Use
case: VM wants to connect to different 'normal' Neutron networks from one
VNIC. VLANs are proposed in blueprint since it's a common way to separate
'networks'. It is just a way to connect to different Neutron networks, it
do
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 confirm, as we want to give end user an opportunity
to rollbac
Hi Ivan,
Indeed, nodepool nodes have MySQL and PostgreSQL installed and
running. There are databases you can access from your tests
(mysql://openstack_citest:openstack_citest@localhost/openstack_citest
and postgresql://openstack_citest:openstack_citest@localhost/openstack_citest).
[1] is a great e
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 and no customization after
>> build ever, ever, the messiness that source u
Hi,
Your result is interesting and not surprising due to the different design
you have described.
The Ceilo team will work on the improvements IIUC.
I found two relevant links [1] [2]
@jay : the first case seems to be impossible, no scalable .. I bet for the
last :)
@June li
I am curious to know
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 cold migration, does it make
sense?
On Wed, Jan 8, 20
Trinath,
Tempest tests should be backend-agnostic, so specific tests for your
mechanism driver is not needed.
You need specific testing environment for that which will run tempest tests
against a deployment with mechanism drivers you want to test. See also:
http://ci.openstack.org/third_party.html
Hi all,
going back to the original topic of making the logs public, I have a
question:
how long should the logs be kept? One week? One month?
cheers,
Rossella
On Tue, Jan 7, 2014 at 1:22 PM, Torbjorn Tornkvist wrote:
> My problem seem to be the same as reported here:
>
>
> https://bitbucket
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, there is a "fork" of tripleo-image-elements called
tripleo-puppet-elements which does insta
On Wed, Jan 01, 2014 at 02:33:09PM +0800, Thomas Goirand wrote:
> Hi,
>
> I was wondering if it would be possible for NoVNC to switch from
> websockify to sockjs-client, which is available here:
>
> https://github.com/sockjs/sockjs-client
>
> This has the advantage of not using flash at all (pur
Hi,
Patch sets that are cascaded has have the following errors:
"Database migration testing failed either due to migrations unable to be
applied correctly or taking too long.
This change was unable to be automatically merged with the current state of the
repository. Please rebase your change an
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 configuration files used for
>> different purposes:
>> - neutron.conf
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 the
gateway IP (SNAT using PAT/NAT Overload). Does
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 reside in
> test-requirements.txt. So -1 on reverting that pat
On 01/08/2014 07:15 PM, Rossella Sblendido wrote:
> Hi all,
>
> going back to the original topic of making the logs public, I have a
> question:
>
> how long should the logs be kept? One week? One month?
Infra currently keeps logs for 6 months. I think matching the infra log
archiving time frame
On 01/08/2014 07:43 PM, Daniel P. Berrange wrote:
> On Wed, Jan 01, 2014 at 02:33:09PM +0800, Thomas Goirand wrote:
>> Hi,
>>
>> I was wondering if it would be possible for NoVNC to switch from
>> websockify to sockjs-client, which is available here:
>>
>> https://github.com/sockjs/sockjs-client
>>
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 same way as
SecurityImpact posts to openstack-security ?
[1]
https://w
Hi,
I am trying to run cinder unit tests via run_tests.sh since my tox has some
issues. Following is the error I am getting while running run_tests.sh
error in setup command: Error parsing /RMCUT/cinder/havana/setup.cfg:
OSError: [Errno 2] No such file or directory
Running ` python setup.py tes
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
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
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.
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
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
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
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 01/08/2014 09:26 AM, Noorul Islam Kamal Malmiyoda wrote:
On Jan 8, 2014 6:11 PM, "Sean Dague" mailto:[email protected]>> 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:[email protected]>>
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
From: Ray Sun mailto:[email protected]>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:[email protected]>>
Date: Wednesday, January 8, 2014 4:09 PM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:[email protected]
On Wed, Jan 8, 2014 at 8:26 AM, Noorul Islam Kamal Malmiyoda <
[email protected]> 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
On Tue, Jan 7, 2014 at 11:13 PM, Swapnil Kulkarni <
[email protected]> 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 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 Wednesday, 8 January, 2014 at 22:53, John Garbutt wrote:
> On 8 January 2014 10:02, David Xie (mailto:[email protected])> 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 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 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
Anne Gentle writes:
> On Wed, Jan 8, 2014 at 8:26 AM, Noorul Islam Kamal Malmiyoda <
> [email protected]> 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
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
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
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,
在 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
>
>
>
>> 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
Hi,
>-Original Message-
>From: ext Neal, Phil [mailto:[email protected]]
>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
From: ext Tim Bell [mailto:[email protected]]
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
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
Hi Doug,
See my answers inline.
Best Regards,
Ildiko
From: Doug Hellmann [mailto:[email protected]]
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
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,
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, 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
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 8, 2014 at 11:16 AM, Ildikó Váncsa
wrote:
> Hi Doug,
>
>
>
> See my answers inline.
>
>
>
> Best Regards,
>
> Ildiko
>
>
>
> *From:* Doug Hellmann [mailto:[email protected]]
> *Sent:* Wednesday, January 08, 2014 4:10 PM
>
> *To:* OpenStack Development Mailing List (not for u
On Jan 8, 2014 9:58 PM, "Georgy Okrokvertskhov" <
[email protected]> 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
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 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.
>>
>>
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 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 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 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
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.
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
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
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
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:[email protected]>>
Reply-To: OpenStack Dev
mailto:[email protected]>>
Date: Wednesday, Jan
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
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/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
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 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
On 01/08/2014 11:40 AM, Noorul Islam Kamal Malmiyoda wrote:
>
> On Jan 8, 2014 9:58 PM, "Georgy Okrokvertskhov"
> mailto:[email protected]>> wrote:
>>
>> Hi,
>>
>> I do understand why there is a push back for this patch. This patch is
> for infrastructure project which works for multipl
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
Hi Doug,
Answers inline again.
Best Regards,
Ildiko
On Wed, Jan 8, 2014 at 3:16 AM, Ildikó Váncsa
mailto:[email protected]>> 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
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,
(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 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,
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:[email protected]>> wrote:
>>>
>>> Hi,
>>>
>>> I do understand why there is a push back for this patch. This p
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
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 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
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 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 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
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 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
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, 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
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
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
>
>
>From: ext Doug Hellmann [[email protected]]
>Sent: Wednesday, January 08, 2014 8:26 PM
>To: OpenStack Development Mailing List (not for usage questions)
>Subject: Re: [openstack-dev] [Ceilometer] Dy
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
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 Wed, Jan 8, 2014 at 3:09 PM, Kodam, Vijayakumar (EXT-Tata Consultancy
Ser - FI/Espoo) wrote:
>>
>
>
> >
> >From: ext Doug Hellmann [[email protected]]
> >Sent: Wednesday, January 08, 2014 8:26 PM
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.
_
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
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
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
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
1 - 100 of 123 matches
Mail list logo
