Hi Nachi and the teams,
(2014/03/26 9:57), Salvatore Orlando wrote:
I hope we can sort this out on the mailing list IRC, without having to
schedule emergency meetings.
Salvatore
On 25 March 2014 22:58, Nachi Ueno na...@ntti3.com mailto:na...@ntti3.com
wrote:
Hi Nova, Neturon Team
Thanks, will take a look
On Tuesday, March 25, 2014 11:33 PM, Collins, Sean
sean_colli...@cable.comcast.com wrote:
On Fri, Mar 21, 2014 at 08:35:05PM EDT, Rajdeep Dua wrote:
Sean,
If you can point me to the project file in github which needs to be modified
, i will include these docs
On 03/25/2014 09:17 PM, Robert Collins wrote:
TripleO has just seen an influx of new contributors. \o/. Flip side -
we're now slipping on reviews /o\.
In the meeting today we had basically two answers: more cores, and
more work by cores.
We're slipping by 2 reviews a day, which given 16 cores
Hi,
thanks for this very interesting use case!
May be you can still use VXLAN or GRE for tenant networks, to bypass
the 4k limit of vlans. then you would have to send packets to the vlan
tagged interface, with the tag assigned by the VDP protocol, and this
traffic would be encapsulated inside the
The thread branched, and it's getting long.
I'm trying to summarize the discussion for other people to quickly catch up.
- The bug being targeted is https://bugs.launchpad.net/neutron/+bug/1297469
It has also been reported as
https://bugs.launchpad.net/neutron/+bug/1252620 and
as
I have compiled a new linux kernel with CONFIG_VIRTIO_BLK=y. But it doesn't
boot and kernel panics. To kernel command line i tried passing
root=/dev/vda and root=/dev/vda1 but same kernel panic comes every time.
VIRTIO_NET was working fine when VIRTIO_BLK was not enabled and VM booted
up fine. But
Hi Thomas,
Can you share some documentation of what you're doing right now with
TOSCA-compliant layer?
We would like to join to this effort.
Thanks,
Dmitry
On Wed, Mar 26, 2014 at 10:38 AM, Thomas Spatzier
thomas.spatz...@de.ibm.com wrote:
Excerpt from Zane Bitter's message on 26/03/2014
Russell Bryant wrote:
[...]
First, it seems there isn't a common use of deprecated. To me,
marking something deprecated means that the deprecated feature:
- has been completely replaced by something else
- end users / deployers should take action to migrate to the
new thing
Doug Hellmann wrote:
In the last project meeting, we discussed updating the list of core
reviewers on the global requirements project. The review stats for the
last 90 days on the project show that several current core reviewers
haven't been active, so as a first step before adding new cores I
Hi Radomir,
I quickly looked at xstatic and I have the impression that you have to handle
manually the retrievement of the javascript library files and the version of
the scripts. What do you think of wrapping bower in a script in order to
dynamically generate packages with the right versions?
On 26/03/14 11:43, Maxime Vidori wrote:
[...]
I propose a more general solution of using xstatic-* Python packages,
which contain basically just the files that we want to bundle, plus some
small amount of metadata. All of the JavaScript (and any static files,
really, including styles, fonts
Sounds like an extra weighter to try and balance load between your two AZs
might be a nicer way to go.
The easiest way might be via cells, one for each AZ . But not sure we
merged that support yet. But there are patches for that.
John
On 25 Mar 2014 20:53, Sangeeta Singh sin...@yahoo-inc.com
(Removing [Heat] from the subject.)
So here are the steps i think are necessary to get the PKI setup done
and safely passed through Jenkins. If anyone thinks something is
redundant or missing, please shout:
1. Patch to os-cloud-config:
* Generation of keys and certs for cases user doesn't
Hi,
there's been a review up for some time [0] that wants to raise the version of
lesscpy to 0.10.1. It's specific to horizon and contains some important fixes
that we'll likely want to include. So I'd like to ask for an exception for
this one.
[0] https://review.openstack.org/#/c/70619/
--
I would say that the requirement is not valid. A host aggregate con only have
one availability zone so what you actually can have is a compute node that's
part of 2 host aggregates, which actually have the same availability zone.
In the scenario you mentioned below where you create the
I'm not sure why there's so much resistance to Python package version
minimums being increased. Everybody should be using virtualenvs anyway so
it's not like there's some sort of need to support old libraries because
that's what's on deployed OSes.
I understand supporting old kernels, system
Hi Ramy,
There is quite a bit of difference between FC and iSCSI (e.g. iqn vs WWN ..)
While iSER is just an alternative iSCSI transport, and use the exact same tools
on the initiator and target like iSCSI/TCP
Most iSER capable iSCSI targets don't even have a separate configuration for
TCP or
Hi,
Could you possibly add whats new in the changelog as well?
Thanks
chuck
On Wed, Mar 26, 2014 at 8:14 AM, Sascha Peilicke sasc...@mailbox.orgwrote:
Hi,
there's been a review up for some time [0] that wants to raise the version
of
lesscpy to 0.10.1. It's specific to horizon and
On 03/25/2014 10:01 PM, Dolph Mathews wrote:
Given that intention, I believe the proper thing to do is to actually
leave the API marked as fully supported / stable. Keystone should be
working with other OpenStack projects to migrate them to v3. Once that
is complete,
On 03/26/2014 06:30 AM, Thierry Carrez wrote:
Russell Bryant wrote:
[...]
First, it seems there isn't a common use of deprecated. To me,
marking something deprecated means that the deprecated feature:
- has been completely replaced by something else
- end users / deployers should take
It's not expected that you are installing all of openstack into venvs,
it's expected that it works at a system level.
That's always been a design point given that Linux distributions
actually want to ship all this stuff.
-Sean
On 03/26/2014 08:28 AM, Adam Nelson wrote:
I'm not sure why
All,
I know there's a preference for using a proxy to terminate
SSL connections rather than using the native python code.
There's a good write up of configuring the various proxies here:
http://docs.openstack.org/security-guide/content/ch020_ssl-everywhere.html
If we're not using native
Just spotted the openstack-ssl element which uses 'stunnel'...
On Wed, 26 Mar 2014, stuart.mcla...@hp.com wrote:
All,
I know there's a preference for using a proxy to terminate
SSL connections rather than using the native python code.
There's a good write up of configuring the various
Hi Sean,
Unless I have missed something, this is my thinking:
-- I understand that the goal is to allow RAs from designated sources
only.
-- initially, xuhanp posted a diff for
https://review.openstack.org/#/c/72252. And my comment was that subnet
that was created with gateway ip not on the
On 26/03/14 11:50, Ladislav Smola wrote:
On 03/25/2014 09:17 PM, Robert Collins wrote:
TripleO has just seen an influx of new contributors. \o/. Flip side -
we're now slipping on reviews /o\.
In the meeting today we had basically two answers: more cores, and
more work by cores.
We're
Hi
We don't have a strong attachment to stunnel though, I quickly dropped it in
front of our CI/CD undercloud and Rob wrote the element so we could repeat the
deployment.
In the fullness of time I would expect there to exist elements for several SSL
terminators, but we shouldn't necessarily
On 25/03/14 20:17, Robert Collins wrote:
TripleO has just seen an influx of new contributors. \o/. Flip side -
we're now slipping on reviews /o\.
In the meeting today we had basically two answers: more cores, and
more work by cores.
We're slipping by 2 reviews a day, which given 16 cores
Over the course of the Icehouse release, the Oslo team has invested a lot
of time in creating processes and tools to prepare for releasing code from
the incubator as a set of new libraries. The plan we have put together for
creating 9 new libraries during the Juno release is available for review
On 26/03/14 12:14, Sascha Peilicke wrote:
Hi,
there's been a review up for some time [0] that wants to raise the version of
lesscpy to 0.10.1. It's specific to horizon and contains some important fixes
that we'll likely want to include. So I'd like to ask for an exception for
this one.
Hi,
I currently have a patch up for review
(https://review.openstack.org/#/c/81373/) to limit psutil be 2.0.0.
2.0.0 just came out a couple weeks ago, and breaks the API in a major way.
Until we can port our code to the
latest version, I suggest we limit the version of psutil to 1.x (currently
On 03/25/2014 02:50 PM, Sangeeta Singh wrote:
What I am trying to achieve is have two AZ that the user can select
during the boot but then have a default AZ which has the HV from both
AZ1 AND AZ2 so that when the user does not specify any AZ in the boot
command I scatter my VM on both the AZ
On 03/26/2014 10:30 AM, Solly Ross wrote:
Hi,
I currently have a patch up for review
(https://review.openstack.org/#/c/81373/) to limit psutil be 2.0.0.
2.0.0 just came out a couple weeks ago, and breaks the API in a major way.
Until we can port our code to the
latest version, I suggest
Jorge: I agree with you around ensuring different drivers support the API
contract and the no vendor lock-in.
All: How do we move this forward? It sounds like we have agreement that
this is worth investigating.
How do we move forward with the investigation and how to best architect
this? Is this
Thanks Chris.
Sounds like you're saying building out the apache element may be a sensible
next step?
-Stuart
Hi
We don't have a strong attachment to stunnel though, I quickly dropped it in
front of our CI/CD undercloud and Rob wrote
I think it can be used as a capability of the host.
How do you think If regarding it as one type of the HostSate, and return
it in the nova.scheduler.host_manager.HostManager:get_all_host_states
method ?
2014-03-26 11:09 GMT+08:00 Gouzongmei gouzong...@huawei.com:
Hi, Yang, Yi y
Agree
Hi Dimitry,
the current working draft for the simplified profile in YAML is available
at [1]. Note that this is still work in progress, but should already give a
good impression of where we want to go. And as I said, we are open for
input.
The stackforge project [2] that Sahdev from our team
This is a development list and your question sounds like a usage one.
Please try asking on the users list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Thanks.
-Ben
On 03/26/2014 04:24 AM, saurabh agarwal wrote:
I have compiled a new linux kernel with CONFIG_VIRTIO_BLK=y.
Shaunak Kashyap wrote:
We are looking to setup a recurring IRC meeting in one of the
openstack-meeting* rooms for the
https://wiki.openstack.org/wiki/OpenStack-SDK-PHP project. What is the
process for setting this up (i.e. “reserving” a room for a particular time
slot each week)?
Is
This all makes sense to me. I would suggest a blueprint and a pull request as
soon as Juno opens.
Vish
On Mar 25, 2014, at 8:07 AM, Shlomi Sasson shlo...@mellanox.com wrote:
Hi,
I want to share with the community the following challenge:
Currently, Vendors who have their iSCSI driver,
On Wednesday 26 March 2014 13:49:48 Julie Pichon wrote:
On 26/03/14 12:14, Sascha Peilicke wrote:
Hi,
there's been a review up for some time [0] that wants to raise the version
of lesscpy to 0.10.1. It's specific to horizon and contains some
important fixes that we'll likely want to
Aplogies for double-posting.
I've commented again regarding the alternatives to the solution currently
on review.
Please find more info on the bug report [1]
I've attached patches for a hackish but (imo) cleaner solution, and patches
for a compact fix along the lines of what I and Akihiro were
Thank you very much for the info!
On Wed, Mar 26, 2014 at 6:07 PM, Thomas Spatzier thomas.spatz...@de.ibm.com
wrote:
Hi Dimitry,
the current working draft for the simplified profile in YAML is available
at [1]. Note that this is still work in progress, but should already give a
good
Personally I view this as a bug. There is no reason why we shouldn’t support
arbitrary grouping of zones. I know there is at least one problem with zones
that overlap regarding displaying them properly:
https://bugs.launchpad.net/nova/+bug/1277230
There is probably a related issue that is
Excerpts from Chris Jones's message of 2014-03-26 06:58:59 -0700:
Hi
We don't have a strong attachment to stunnel though, I quickly dropped it in
front of our CI/CD undercloud and Rob wrote the element so we could repeat
the deployment.
In the fullness of time I would expect there to
On Tue, Mar 25, 2014 at 5:34 PM, Brant Knudson b...@acm.org wrote:
On Mon, Mar 24, 2014 at 5:49 AM, Sean Dague s...@dague.net wrote:
...
Part of the challenge is turning off DEBUG is currently embedded in code
in oslo log, which makes it kind of awkward to set sane log levels for
On Tue, Mar 25, 2014 at 11:41 PM, Clint Byrum cl...@fewbar.com wrote:
Excerpts from Dolph Mathews's message of 2014-03-25 19:01:17 -0700:
On Tue, Mar 25, 2014 at 5:50 PM, Russell Bryant rbry...@redhat.com
wrote:
We discussed the deprecation of the v2 keystone API in the
cross-project
Code which breaks:
Glance's mutliprocessing tests will break (the reason we should limit it now).
For the future, people attempting to use psutil will have no clear version
target
(Either they use 1.x and break with the people who install the latest version
from pip,
of they use 2.0.0 and break
Hi
On 26 March 2014 16:51, Clint Byrum cl...@fewbar.com wrote:
quite a bit differently than app serving), there is a security implication
in having the private SSL keys on the same box that runs the app.
This is a very good point, thanks :)
--
Cheers,
Chris
On 03/26/2014 10:47 AM, Vishvananda Ishaya wrote:
Personally I view this as a bug. There is no reason why we shouldn’t
support arbitrary grouping of zones. I know there is at least one
problem with zones that overlap regarding displaying them properly:
- Original Message -
From: Sangeeta Singh sin...@yahoo-inc.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Tuesday, March 25, 2014 9:50:00 PM
Subject: [openstack-dev] [nova][scheduler] Availability Zones and Host
Thanks Thierry. I’ve added the meeting to the wiki page.
Shaunak
On Mar 26, 2014, at 12:25 PM, Thierry Carrez thie...@openstack.org wrote:
Shaunak Kashyap wrote:
We are looking to setup a recurring IRC meeting in one of the
openstack-meeting* rooms for the
On 3/25/2014 1:50 PM, Matt Wagner wrote:
This would argue to me that the easiest thing for Ceilometer might be
to query us for IPMI stats, if the credential store is pluggable.
Fetch these bare metal statistics doesn't seem too off-course for
Ironic to me. The alternative is that
From: Baldassin, Santiago B
santiago.b.baldas...@intel.commailto:santiago.b.baldas...@intel.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Wednesday, March 26, 2014 at 5:17 AM
To:
Comments inline.
On 3/26/14, 10:28 AM, Eoghan Glynn wrote:
On 3/25/2014 1:50 PM, Matt Wagner wrote:
This would argue to me that the easiest thing for Ceilometer might be
to query us for IPMI stats, if the credential store is pluggable.
Fetch these bare metal statistics doesn't seem too
On Mon, Mar 24, 2014 at 10:35 AM, Elizabeth Krumbach Joseph
l...@princessleia.com wrote:
Hi everyone,
The OpenStack Infrastructure (Infra) team is hosting our weekly
meeting tomorrow, Tuesday March 25th, at 19:00 UTC in
#openstack-meeting
Meeting minutes and logs from yesterday here:
On 03/26/2014 12:56 PM, Doug Hellmann wrote:
On Tue, Mar 25, 2014 at 11:41 PM, Clint Byrum cl...@fewbar.com
1 out of every 2 API calls on these clouds produces one of these errors
in Keystone. That is just pointless. :-P
This is a good point. The other thing we discussed was
On 3/26/14, 10:17 AM, Khanh-Toan Tran khanh-toan.t...@cloudwatt.com
wrote:
- Original Message -
From: Sangeeta Singh sin...@yahoo-inc.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Tuesday, March 25, 2014 9:50:00 PM
On 3/26/14, 10:17 AM, Khanh-Toan Tran khanh-toan.t...@cloudwatt.com
wrote:
- Original Message -
From: Sangeeta Singh sin...@yahoo-inc.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Tuesday, March 25, 2014 9:50:00 PM
On 03/26/2014 11:17 AM, Khanh-Toan Tran wrote:
I don't know why you need a
compute node that belongs to 2 different availability-zones. Maybe
I'm wrong but for me it's logical that availability-zones do not
share the same compute nodes. The availability-zones have the role
of partition your
Let's discuss it on weekly LBaaS meeting tomorrow.
Thanks,
Eugene.
On Wed, Mar 26, 2014 at 7:03 PM, Susanne Balle sleipnir...@gmail.comwrote:
Jorge: I agree with you around ensuring different drivers support the
API contract and the no vendor lock-in.
All: How do we move this forward? It
This is an issue that affects all of our git repos. If you are using
oslo.config, you will likely also be using the sample config generator.
However, for some reason we are all checking this generated file in.
This makes no sense, as we humans are not editting it, and it often
picks up config
I have submitted a couple of changes to start us down the path to better
optional dependency support, as discussed below. There are still some
issues to be worked out, like how to specify a default for a particular
project (I punted on this for the oslo.messaging POC and left kombu as a
hard
On Mar 24, 2014, at 2:09 PM, Joe Gordon joe.gord...@gmail.com wrote:
On Mon, Mar 24, 2014 at 3:49 AM, Sean Dague s...@dague.net wrote:
Here is some preliminary views (it currently ignores the ceilometer
logs, I haven't had a chance to dive in there yet).
It actually looks like a huge
On 03/26/2014 02:10 PM, Clint Byrum wrote:
This is an issue that affects all of our git repos. If you are using
oslo.config, you will likely also be using the sample config generator.
However, for some reason we are all checking this generated file in.
This makes no sense, as we humans are
On 03/25/2014 11:07 AM, Shlomi Sasson wrote:
I am not sure what will be the right approach to handle this, I already have
the code, should I open a bug or blueprint to track this issue?
Best Regards,
Shlomi
A blueprint around this would be appreciated. I have had similar
thoughts
On 3/25/14 11:55 AM, Ruslan Kamaldinov rkamaldi...@mirantis.com wrote:
* Murano DSL will focus on:
a. UI rendering
One of the primary reasons I am opposed to using a different DSL/project
to accomplish this is that the person authoring the HOT template is
usually the system architect, and
Team, what do you think about doing this for Marconi? It looks like we
indeed have a sample checked in:
https://review.openstack.org/#/c/83006/1/etc/marconi.conf.sample
Personally, I think we should keep the sample until generate_sample.sh
works on OS X (we could even volunteer to fix it);
On 26/03/14 14:10, Clint Byrum wrote:
This is an issue that affects all of our git repos. If you are using
oslo.config, you will likely also be using the sample config generator.
However, for some reason we are all checking this generated file in.
This makes no sense, as we humans are not
On Wed, 2014-03-26 at 09:47 -0700, Vishvananda Ishaya wrote:
Personally I view this as a bug. There is no reason why we shouldn’t
support arbitrary grouping of zones. I know there is at least one
problem with zones that overlap regarding displaying them properly:
Yes, Vish description describes the uses cases and the need for multiple
overlapping
availability zones nicely.
If multiple availability zone can be specified in the launch command that
will allow
End user to select hosts that satisfy all there constraints.
Thanks,
Sangeeta
On 3/26/14, 11:00
My assumption on the depreciation messages is that this is targeted at non-core
OpenStack applications.
OpenStack developer pressure should be established within the projects, not by
overwhelming production clouds with logs that something is depreciated.
Equally, asking locally developed
On Wed, Mar 26, 2014 at 11:15 AM, Vishvananda Ishaya
vishvana...@gmail.comwrote:
On Mar 24, 2014, at 2:09 PM, Joe Gordon joe.gord...@gmail.com wrote:
On Mon, Mar 24, 2014 at 3:49 AM, Sean Dague s...@dague.net wrote:
Here is some preliminary views (it currently ignores the ceilometer
On Wed, Mar 26, 2014 at 1:10 PM, Clint Byrum cl...@fewbar.com wrote:
This is an issue that affects all of our git repos. If you are using
oslo.config, you will likely also be using the sample config generator.
However, for some reason we are all checking this generated file in.
This makes no
On Wed, Mar 26, 2014 at 9:51 AM, Doug Hellmann
doug.hellm...@dreamhost.comwrote:
On Tue, Mar 25, 2014 at 5:34 PM, Brant Knudson b...@acm.org wrote:
On Mon, Mar 24, 2014 at 5:49 AM, Sean Dague s...@dague.net wrote:
...
Part of the challenge is turning off DEBUG is currently embedded
This is really interesting discussion but was thrown off by the different use
of ‘functional testing.’ I decided to reconcile it with my understanding and
ended up with this two-pager. Sharing it in case it helps:
I haven't gotten to my email back log yet, but want to point out that I
agree with everything Robert just said. I also raised these concerns on the
original ceilometer BP, which is what gave rise to all the work in ironic
that Haomeng has been doing (on the linked ironic BP) to expose these
Salvatore Orlando sorla...@nicira.com writes:
On another note, we noticed that the duplicated jobs currently executed for
redundancy in neutron actually seem to point all to the same build id.
I'm not sure then if we're actually executing each job twice or just
duplicating lines in the
Where is the RC bug tracking this?
If it's that bad, we really need to be explicit about this with a
critical bug at this stage of the release.
-Sean
On 03/26/2014 01:14 PM, Solly Ross wrote:
Code which breaks:
Glance's mutliprocessing tests will break (the reason we should limit it
What bug tracker should I file under? I tried filing one under the openstack
common infrastructure tracker,
but was told that it wasn't the correct place to file such a bug.
Best Regards,
Solly Ross
- Original Message -
From: Sean Dague s...@dague.net
To: OpenStack Development Mailing
Hi folks,
Lets keep our regular meetings. Th next one on Thursday, 27, at 14-00 UTC.
The agenda for the meeting:
1) Object model discussion update
2) Requirements glossary QA
3) Open discussion
Thanks,
Eugene.
___
OpenStack-dev mailing list
Eugene,
I assume the object model discussion will still continue. Many were of the
opinion the model with the load balancer is a good one but you stated that
others that were not present at those meetings did not have that same opinion,
such as Mark Mcclain. Mark hasn't been in those meetings
Which ever project is going to explode under this combination.
-Sean
On 03/26/2014 03:32 PM, Solly Ross wrote:
What bug tracker should I file under? I tried filing one under the openstack
common infrastructure tracker,
but was told that it wasn't the correct place to file such a
On Tue, Mar 25, 2014 at 1:49 AM, Maru Newby ma...@redhat.com wrote:
On Mar 21, 2014, at 9:01 AM, David Kranz dkr...@redhat.com wrote:
On 03/20/2014 04:19 PM, Rochelle.RochelleGrober wrote:
-Original Message-
From: Malini Kamalambal [mailto:malini.kamalam...@rackspace.com]
Hi folks,
I've made a small patch set to illustrate the idea and usage of flavors as
I see it.
https://review.openstack.org/#/c/83055/
I think gerrit can be a good place to discuss important implementation
details on a given example service plugin, take a look at test_flavors.py
file where it
On Wed, Mar 26, 2014 at 12:32 PM, Solly Ross sr...@redhat.com wrote:
What bug tracker should I file under? I tried filing one under the openstack
common infrastructure tracker,
but was told that it wasn't the correct place to file such a bug.
Best Regards,
Solly Ross
- Original
Excerpts from Anne Gentle's message of 2014-03-26 11:49:29 -0700:
On Wed, Mar 26, 2014 at 1:10 PM, Clint Byrum cl...@fewbar.com wrote:
This is an issue that affects all of our git repos. If you are using
oslo.config, you will likely also be using the sample config generator.
However,
Excerpts from Steven Hardy's message of 2014-03-26 11:27:58 -0700:
On Wed, Mar 26, 2014 at 11:10:04AM -0700, Clint Byrum wrote:
This is an issue that affects all of our git repos. If you are using
oslo.config, you will likely also be using the sample config generator.
However, for some
Here's the bug for Glance: https://bugs.launchpad.net/glance/+bug/1298039
- Original Message -
From: Clark Boylan clark.boy...@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Wednesday, March 26, 2014 4:04:12 PM
Subject:
- Original Message -
On 27 March 2014 06:28, Eoghan Glynn egl...@redhat.com wrote:
On 3/25/2014 1:50 PM, Matt Wagner wrote:
This would argue to me that the easiest thing for Ceilometer might be
to query us for IPMI stats, if the credential store is pluggable.
Fetch these
Also, some systems have more sophisticated IPMI topology than a single node
instance, like in case of chassis-based systems. Some other systems might
use vendor-specific IPMI extensions or alternate platform management
protocols, that could require vendor-specific drivers to terminate.
Going for
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
tomorrow Thursday, March 27th at 17:00 UTC in the #openstack-meeting
channel.
The agenda for tomorrow's meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome to add an item to
I haven't gotten to my email back log yet, but want to point out that I agree
with everything Robert just said. I also raised these concerns on the
original ceilometer BP, which is what gave rise to all the work in ironic
that Haomeng has been doing (on the linked ironic BP) to expose these
On Mar 26, 2014, at 11:40 AM, Jay Pipes jaypi...@gmail.com wrote:
On Wed, 2014-03-26 at 09:47 -0700, Vishvananda Ishaya wrote:
Personally I view this as a bug. There is no reason why we shouldn’t
support arbitrary grouping of zones. I know there is at least one
problem with zones that
I can't agree more on this. Although the name sounds identical to AWS, Nova
AZs are *not* for segregating compute nodes, but rather exposing to users a
certain sort of grouping.
Please see this pointer for more info if needed :
On Wed, Mar 26, 2014 at 12:18 PM, Eric Harney ehar...@redhat.com wrote:
On 03/25/2014 11:07 AM, Shlomi Sasson wrote:
I am not sure what will be the right approach to handle this, I already
have the code, should I open a bug or blueprint to track this issue?
Best Regards,
Shlomi
A
On 03/25/2014 04:49 AM, Maru Newby wrote:
On Mar 21, 2014, at 9:01 AM, David Kranz dkr...@redhat.com wrote:
On 03/20/2014 04:19 PM, Rochelle.RochelleGrober wrote:
-Original Message-
From: Malini Kamalambal [mailto:malini.kamalam...@rackspace.com]
Sent: Thursday, March 20, 2014
=== Long-running delegate [1] actions ==
Yes, the third model of lazy / passive engine is needed.
Obviously workflows contain a mix of different tasks, so this 3rd model should
handle both normal tasks (run on a workers and return) and long running
delegates. The active mechanism which is
Cool, sounds great.
I think all 3 models can co-exist (since each serves a good purpose), it'd be
intersting to see how the POC 'engine' can become a taskflow 'engine' (aka the
lazy_engine).
As to scalability I agree lazy_engine would be nicer, but how much more
scalable is a tough one to
Hi Nader,
When I wrote this, the intention was that original_network only really
makes sense during an update_network call (ie when there's an existing
network that you are modifying). In a create_network call, the assumption
is that no network exists yet, so there is no original network to set.
Next week during the VMwareAPI subteam meeting I would like to discuss
blueprint priority order and tentative scheduling for Juno. I have a
proposal for the order that I would like to conduct a formal vote on
and I hope that we as a community can abide by the vote's results.
In short, we
1 - 100 of 114 matches
Mail list logo
