Chris Friesen wrote:
On 07/15/2015 09:31 AM, Joshua Harlow wrote:
I do like experiments!
What about going even farther and trying to integrate somehow into mesos?
https://mesos.apache.org/documentation/latest/mesos-architecture/
Replace the hadooop executor, MPI executor with a 'VM executor'
Thanks, but we don't use the blueprint process for feature requests in
Neutron. Just file a bug in launchpad and give in an 'rfe' tag, which
stands for request for enhancement.
On Tue, Jul 14, 2015 at 5:29 AM, yan_xing...@163.com yan_xing...@163.com
wrote:
Thank you, Kevin.
I search the
I'm guessing Salvatore might just be suggesting that we restrict users from
populating values that have special meaning (e.g. l3 agent router interface
ports). I don't think at this point we could constrain the owner field to
essentially an enum at this point.
On Wed, Jul 15, 2015 at 10:22 PM,
On 07/15/2015 11:25 AM, Joshua Harlow wrote:
So I've been following the TC work on tags, and have been slightly
confused by the whole work, so I am wondering if I can get a
'explainlikeimfive' (borrowing from reddit terminology) edition of it.
I'll try :)
You need to think of tags as the
Thanks that helps! (and I hope it helps others to),
A few questions inline...
Stefano Maffulli wrote:
On 07/15/2015 11:25 AM, Joshua Harlow wrote:
So I've been following the TC work on tags, and have been slightly
confused by the whole work, so I am wondering if I can get a
- Original Message -
From: Calum Loudon calum.lou...@metaswitch.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Hi Steve
I missed the linked mail as it was sent to the openstack-operators list, not
openstack-dev - was that
Hi HongBin,
I think flavors introduces more confusion than nova_instance_type or
instance_type.
As flavors not have binding with 'vm' or 'baremetal',
Let me summary the initial question:
We have two kinds of templates for kubernetes now,
(as templates in heat not flexible like programming
Kai,
Sorry for the confusion. To clarify, I was thinking how to name the field you
proposed in baymodel [1]. I prefer to drop it and use the existing field
‘flavor’ to map the Heat template.
[1] https://review.openstack.org/#/c/198984/6
From: Kai Qiang Wu [mailto:wk...@cn.ibm.com]
Sent:
On Tue, Jun 30, 2015 at 6:09 PM, Julien Danjou jul...@danjou.info wrote:
On Mon, Jun 29 2015, Ildikó Váncsa wrote:
I think removing options from the API requires version bump. So if we
plan to
do this, that should be introduced in v3 as opposed to v2, which should
remain
the same and
Thanks Ihar. Went through your email and updated HEADS to resolve merging
conflicts for my patch.
On Wed, Jul 15, 2015 at 1:03 PM, Ihar Hrachyshka ihrac...@redhat.com
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/15/2015 07:17 PM, Madhusudhan Kandadai wrote:
Hello,
I
Hi,
I believe we are all receiving a large number of Fuel related messages
everyday, but not all of us have the abundant bandwidth to read them.
Maybe we can consider adding 'Fuel' to the topic categories we can check
on/off when customising the subscription.
Currently, the option is to filter
- Original Message -
Yes please.
This would be a good starting point.
I also think that the ability of editing it, as well as the value it could be
set to, should be constrained.
FYI the oVirt project uses this field to identify ports it creates and manages.
So if you're going to
Hello OpenStackers!
The Intel PCI/SRIOV/NGFW/PTAS CI located in China, due to reasons beyond
our control, lost connectivity to the Jenkins servers. Although the CI
system is working fine we haven’t been able to report results back for
about a month now.
We are actively looking for a
Welcome Tom!
2015-07-15 6:53 GMT+08:00 Tom Cammann tom.camm...@hp.com:
Thanks team, happy to be here :)
Tom
On 14 Jul 2015, at 23:02, Adrian Otto adrian.o...@rackspace.com wrote:
Tom,
It is my pleasure to welcome you to the magnum-core group. We are happy
to have you on the team.
I'd agree with Angus.
在 2015-07-16 12:05:25，Angus Salkeld asalk...@mirantis.com 写道：
On Tue, Jun 30, 2015 at 6:09 PM, Julien Danjou jul...@danjou.info wrote:
On Mon, Jun 29 2015, Ildikó Váncsa wrote:
I think removing options from the API requires version bump. So if we plan to
do this, that
-- Original --
From: “Adrian Otto”adrian.o...@rackspace.com;
Date: Wed, Jul 15, 2015 02:31 AM
To: “OpenStack Development Mailing List (not for usage
questions)“openstack-dev@lists.openstack.org;
Subject: Re: [openstack-dev] [magnum][bp] Power Magnum to run
On 07/15/2015 10:19 PM, yongli he wrote:
Hello OpenStackers!
The Intel PCI/SRIOV/NGFW/PTAS CI located in China, due to reasons beyond
our control, lost connectivity to the Jenkins servers.
The great firewall of China is making quite a few folks unhappy.
Although the CI
system is working
Industrial Base, Longgang, Shenzhen
(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402
OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
Tricircle IRC Meeting chatlog 20150715.docx
Description
Hi Hong Bin,
Thanks for your reply.
I think it is better to discuss the 'platform' Vs instance_type Vs others
case first.
Attach: initial patch (about the discussion):
https://review.openstack.org/#/c/200401/
My other patches all depend on above patch, if above patch can not reach a
On Jul 15, 2015, at 1:39 PM,
hongbin...@huawei.commailto:hongbin...@huawei.com wrote:
+1 for the idea of using Nova flavor directly.
Our initial resistance to using flavor is that you may want the same bay to
have a combination of different flavors in it. I suppose this might still be
Adam Young wrote:
On 07/03/2015 08:36 AM, Samuel de Medeiros Queiroz wrote:
Hi Thierry,
Thanks for clarifying. A Spec Freeze Exception is what I was supposed
to ask for.
Rectifying:
On behalf of the team working on the Dynamic Policies subject, I would
like to ask for a *Spec Freeze
Hi all,
I have puppet for mistral and i would like to contribute it.
Any objection/comments?
Thanks
Limor Stotland
ALCATEL-LUCENT
SENIOR SOFTWARE ENGINEER
CLOUDBAND BUSINESS UNIT
16 Atir Yeda St. Kfar-Saba 44643, ISRAEL
T: +972 (0) 9 793 3166
M: +972 (0) 54 585 3736
Hi Team,
We will have our weekly meeting today at UTC1300, we will be discussing
Saggi's new patch
https://review.openstack.org/201224
--
Zhipeng (Howard) Huang
Standard Engineer
IT Standard Patent/IT Prooduct Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei
Hi,
The latest release of os-brick is not compatible with Python 3.
Different patches were merged to fix Python 3 support. tox -e py34 now
executes all tests and all tests pass on Python 3.4.
I need a release of os-brick to port Cinder to Python 3. A Python 3
issue in os-brick blocks my 4
Monty Taylor wrote:
[...]
An epoch, being a tool designed for package maintainers to solve package
maintainer problems, is not a tool designed to solve ease of
communication issues for regular users. Most regular users immediately
grasp that 2.0.0 1.0.0. Most regular users do NOT intuitively
Limor,
No objections from my side. Just follow regular OpenStack procedures to do it.
Thanks
Renat Akhmerov
@ Mirantis Inc.
On 15 Jul 2015, at 14:19, BORTMAN, Limor (Limor)
limor.bort...@alcatel-lucent.com wrote:
Hi all,
I have puppet for mistral and i would like to contribute it.
Hi,
Are there any suggested steps on how to execute post-deployment (OSPd) tuning
of components?
I see two possible scenarios, but maybe they are the same:
a) configuration changes to a component which is managed by OSPd (cinder,
nova, etc);
b) installation of additional components (Sahara,
On 15 Jul 2015, at 14:23, ELISHA, Moshe (Moshe)
moshe.eli...@alcatel-lucent.com wrote:
With the use cases I had encountered – the columns listed in the BP were OK.
Do you have any suggestion for other columns?
Nothing specific at the moment. Need to carefully research that in a BP scope.
Hi,
On 09/07/2015 16:29, Ian Cordasco wrote:
Thanks for your hard work Victor! I'll bring up a new release today in the
Glance meeting (currently running) and see if Nik and I can bug the
release managers for a new release today.
Any update on this release?
In the meeting report, I read:
2015-07-15 5:14 GMT+08:00 Matt Riedemann mrie...@linux.vnet.ibm.com:
On 7/14/2015 3:43 PM, Cale Rath wrote:
Hi,
I created a patch to fail on the proxy call to Neutron for used limits,
found here: https://review.openstack.org/#/c/199604/
This patch was done because of this:
Hi all,
I have puppet for mistral and i would like to contribute it.
Any objection/comments?
Thanks
Limor Stotland
ALCATEL-LUCENT
SENIOR SOFTWARE ENGINEER
CLOUDBAND BUSINESS UNIT
16 Atir Yeda St. Kfar-Saba 44643, ISRAEL
T: +972 (0) 9 793 3166
M: +972 (0) 54 585 3736
I agree. We will try to allocate someone soon for this but it seems that all
are very busy.
With the use cases I had encountered – the columns listed in the BP were OK. Do
you have any suggestion for other columns?
Another important thing – when I changed the columns just for testing purposes
It is uncommon that the id can be set when creating resource.
Other resource can not, e.g. instance.
I want to know why this is happend only in flavor. history logical or
something else?
--
Lei Zhang
Blog: http://xcodest.me
twitter/weibo: @jeffrey4l
Matt Riedemann mrie...@linux.vnet.ibm.com wrote on 07/14/2015 07:28:45
PM:
From: Matt Riedemann mrie...@linux.vnet.ibm.com
To: openstack-dev@lists.openstack.org
Date: 07/14/2015 07:40 PM
Subject: Re: [openstack-dev] [nova] Switching the bug status of ~200
bugs at once; Problem?
[...]
Some comments inline.
Salvatore
On 15 July 2015 at 10:24, Alex Xu sou...@gmail.com wrote:
2015-07-15 5:14 GMT+08:00 Matt Riedemann mrie...@linux.vnet.ibm.com:
On 7/14/2015 3:43 PM, Cale Rath wrote:
Hi,
I created a patch to fail on the proxy call to Neutron for used limits,
found
Doug Hellmann wrote:
At one point Robert proposed that we change the policy for approving
constraint changes like https://review.openstack.org/#/c/201408/ to
allow a single reviewer to approve it, assuming the tests were green.
Is that our current policy, or are we waiting for the integration
Thomas Goirand wrote:
On 07/14/2015 10:29 AM, Ihar Hrachyshka wrote:
On 07/14/2015 12:33 AM, Thomas Goirand wrote:
Effectively, under these conditions, I am giving up doing any kind
of coordination between distros for security patches of Icehouse.
:(
As far as I know, there was no real
Congratulations Miguel :-)
-Original Message-
From: Miguel Angel Ajo [mailto:mangel...@redhat.com]
Sent: Tuesday, July 14, 2015 7:45 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] - Proposing Miguel Angel Ajo for the
Control
Fuelers,
I'd like to nominate Denys Klepikov for the fuel-docs-core team.
He has contributed a lot into documentation to Fuel over the past several
months with being diligent reviewer.
He has been working hard to improve UX, clarifying complex aspects and
providing detailed feedback for the
Can i understand the use case for that?
What i don't get it is how will you know the MAC for a new created instance
via HEAT so you can set at the same time the SG based on MAC?
On Tue, Jul 14, 2015 at 12:29 PM, yan_xing...@163.com yan_xing...@163.com
wrote:
Thank you, Kevin.
I search the
+1
Great work, Denys!
On Wed, Jul 15, 2015, 00:04 Irina Povolotskaya ipovolotsk...@mirantis.com
wrote:
Fuelers,
I'd like to nominate Denys Klepikov for the fuel-docs-core team.
He has contributed a lot into documentation to Fuel over the past several
months with being diligent reviewer.
Moshe, thanks for addressing this.
I think we need to implement this BP in this cycle (actually asap) as I think
it can potentially create problems with real usage now. So I fully support it.
One thing we need to do is to see what other columns (besides listed out in BP)
should also be
Hi Vivek and LBaaS folks,
I added [horizon] tag so that Horizon folks can be aware of this thread.
Before jumping into LBaaS specific topic, let me share the current effort
As you may know, Horizon team itself is exploring a way how to make
development of each panel fast and smooth.
- One
Hi there,
I finally figured it out that the problem is caused by the mismatch of the
VLAN range between my openstack installation and the physical switch
setting. Thank you all for your kindly help.
Best regards,
Lily Xing
On Mon, Jul 6, 2015 at 2:02 PM, Lily.Sing lily.s...@gmail.com wrote:
On 14/07/15 11:05, Mark Kirkwood wrote:
On 13/07/15 06:44, Emilien Macchi wrote:
Yeah, I guess I should raise a bug with Ubuntu so it (maybe) gets sorted
out. However in the meantime we may have to work around it by amending
the dir permissions in puppet (the alternative - rolling our own
Thanks, Julio, for sharing this.
Regards,
Qiming
On Tue, Jul 14, 2015 at 12:08:39PM -0500, Julio E Ruano wrote:
Hi All,
I just wanted to share where all of the TOSCA reference material is
accessible. It is maintained through an OASIS TC here -
Hi Bob, Miguel
On Tue, Jul 14, 2015 at 5:19 PM, Robert Kukura kuk...@noironetworks.com
wrote:
I haven't had a chance to review this patch in detail yet, but am
wondering if this is being integrated with ML2 as an extension driver? If
so, that should clearly address how dictionaries are
Hi,
Let’s move it into the LBaaS repo that seems like the right place for me —
Thanks,
German
From: Jain, Vivek vivekj...@ebay.commailto:vivekj...@ebay.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
Hello Mike!
Thanks for looking into this. Yes, the fails are caused by the two open
bugs i mentioned [1,2].
We will continue to see into those.
Regards
Silvan
[1] https://bugs.launchpad.net/nova/+bug/1465416
[2] https://bugs.launchpad.net/cinder/+bug/1473116
2015-07-15 0:07 GMT+02:00 Mike
So I've been following the TC work on tags, and have been slightly
confused by the whole work, so I am wondering if I can get a
'explainlikeimfive' (borrowing from reddit terminology) edition of it.
I always thought tags were going to be something like:
http://i.imgur.com/rcAnMkX.png
(I'm
Sean,
OK, moving thread to openstack-dev.
We'd like to help with this work if there is more to do. What are the next
steps and what areas need help?
Thanks,
Will
-Original Message-
From: Sean Dague [mailto:s...@dague.net]
Sent: Wednesday, July 15, 2015 3:10 AM
To: Du, Dolpher;
John Griffith wrote:
On Wed, Jul 15, 2015 at 12:25 PM, Joshua Harlow harlo...@outlook.com
mailto:harlo...@outlook.com wrote:
So I've been following the TC work on tags, and have been slightly
confused by the whole work, so I am wondering if I can get a
'explainlikeimfive'
Hello,
I have noticed that neutron project got rid of
neutron/db/migration/alembic_migrations/versions/HEAD file and renamed it
to neutron/db/migration/alembic_migrations/versions/HEADS
May I know the reason why this happened? I may have overlooked some
documentation with respect to the change.
On 16 July 2015 at 02:18, Ed Leafe e...@leafe.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
...
What I'd like to investigate is replacing the current design of having
the compute nodes communicating with the scheduler via message queues.
This design is overly complex and has
On 7/15/2015 11:23 AM, Nikola Đipanov wrote:
I'll keep this email brief since this has been a well known issue for
some time now.
Problem: Libvirt can't honour device names specified at boot for any
volumes requested as part of block_device_mapping. What we currently do
is in case they do get
The osapi_v3.enabled option is False by default [1] even though it's
marked as the CURRENT API and the v2 API is marked as SUPPORTED (and
we've frozen it for new feature development).
I got looking at this because osapi_v3.enabled is True in nova.conf in
both the
On Wed, Jul 15, 2015 at 12:25 PM, Joshua Harlow harlo...@outlook.com
wrote:
So I've been following the TC work on tags, and have been slightly
confused by the whole work, so I am wondering if I can get a
'explainlikeimfive' (borrowing from reddit terminology) edition of it.
I always thought
All,
This week is the L4-L7 mid cycle so we will skip today¹s meeting ‹
German
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
On 07/15/2015 01:44 PM, Matt Riedemann wrote:
The osapi_v3.enabled option is False by default [1] even though it's
marked as the CURRENT API and the v2 API is marked as SUPPORTED (and
we've frozen it for new feature development).
I got looking at this because osapi_v3.enabled is True in
Wouldn't it be valid to assign flavors to groups of provider networks? e.g.
a tenant wants to attach to a network that is wired up to a 40g router so
he/she chooses a network of the fat pipe flavor.
On Wed, Jul 15, 2015 at 10:40 AM, Madhusudhan Kandadai
madhusudhan.openst...@gmail.com wrote:
On 7/15/2015 11:23 AM, Nikola Đipanov wrote:
I'll keep this email brief since this has been a well known issue for
some time now.
Problem: Libvirt can't honour device names specified at boot for any
volumes requested as part of block_device_mapping. What we currently do
is in case they do get
What you describe is a spike. It's a grand plan, and you don't need
anyone's permission, so huzzah for the spike!
As far as what should be improved, I hear a lot that having multiple
schedulers does not scale well, so I'd suggest that as a primary target
(maybe measure the _current_ problem, and
On 07/15/15 at 12:19pm, Matt Riedemann wrote:
On 7/15/2015 11:23 AM, Nikola Đipanov wrote:
I'll keep this email brief since this has been a well known issue for
some time now.
Problem: Libvirt can't honour device names specified at boot for any
volumes requested as part of
On 14 July 2015 at 21:43, Cale Rath ctr...@linux.vnet.ibm.com wrote:
Hi,
I created a patch to fail on the proxy call to Neutron for used limits,
found here: https://review.openstack.org/#/c/199604/
This patch was done because of this:
Dmitry
You can fix it by declaring that developer should use particular pypi
mirror.
On Wed, Jul 15, 2015 at 2:46 PM, Dmitry Pyzhov dpyz...@mirantis.com wrote:
Vladimir,
We do break developer's workflow in stable branches if we force them to
use our local mirrors. Yes, we can hardcode
Hi Stackers,
I've created a short list of Cinder API functions (only API v2 and
extensions) and compared it to rally scenarios [2].
We've got pretty good coverage for volumes, snapshots and backups APIs. But
we have not any scenarios for the rest of API methods. Looking throw the
review requests
Hi Steve
I missed the linked mail as it was sent to the openstack-operators list, not
openstack-dev - was that intentional?
On the substance of the mail, +1 to adding Daniel and Yuriy to the core
reviewers list.
cheers
Calum
-Original Message-
From: Steve Gordon
On Wed, Jul 15, 2015 at 6:52 PM, Peng Zhao p...@hyper.sh wrote:
-- Original -- From: “Adrian Otto”
adrian.otto@rackspace. com ; Date: Wed, Jul 15, 2015 02:31 AM To: “OpenStack
Development Mailing List (not for usage questions)“ openstack-dev@
Victor,
That was related to stable/kilo branch as stated on the line above:
14:39:58 nikhil_k jokke_: was that you on python-glanceclient stable/kilo
14:39:59 jokke_ also queued up bunch of stable stuff ... glance_store gotta
wait until Cinder gets their client requirements fixed, but
Hello,
I'm not 100% sure about patch [1] I've sent and I'm looking into ideas.
Neutron API in liberty will require lbaas, fwaas and vpnaas packages installed
if they are set in service_plugins or it won't even start the neutron service.
For the modules to work one also needs to run
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/14/2015 09:14 PM, Thomas Goirand wrote:
On 07/14/2015 10:29 AM, Ihar Hrachyshka wrote:
On 07/14/2015 12:33 AM, Thomas Goirand wrote:
I missed this announce...
On 07/02/2015 05:32 AM, Jeremy Stanley wrote:
Per the Icehouse EOL
On 07/15/2015 04:17 AM, BORTMAN, Limor (Limor) wrote:
Hi all,
I have puppet for mistral and i would like to contribute it.
Any objection/comments?
We have a recent Wiki page that explains this process:
https://wiki.openstack.org/wiki/Puppet/New_module
Please let us know any feedback,
Hi all,
I'm unable to make the meeting today and was unable to get an alternative
facilitator to run the meeting, as such it is canceled. Please note that I am
still seeking comment on:
[Openstack-operators] [nfv][telco] On-going management of telcowg-usecases
repository
Hi,
I've seen that the latest version of taskflow needs fasteners, which
handles lock stuff. Why can't this goes into oslo.concurrency?
Cheers,
Thomas Goirand (zigo)
__
OpenStack Development Mailing List (not for usage
On Wed, Jul 15, 2015 at 12:44 PM, Joshua Harlow harlo...@outlook.com
wrote:
John Griffith wrote:
On Wed, Jul 15, 2015 at 12:25 PM, Joshua Harlow harlo...@outlook.com
mailto:harlo...@outlook.com wrote:
So I've been following the TC work on tags, and have been slightly
confused by
On Jul 15, 2015, at 1:08 PM, Maish Saidel-Keesing mais...@maishsk.com wrote:
* Consider the cost of introducing a brand new technology into the
deployer space. If there _is_ a way to get the desired improvement with,
say, just MySQL and some clever sharding, then that might be a smaller
pill
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/15/2015 07:17 PM, Madhusudhan Kandadai wrote:
Hello,
I have noticed that neutron project got rid of
neutron/db/migration/alembic_migrations/versions/HEAD file and
renamed it to
neutron/db/migration/alembic_migrations/versions/HEADS
As the Neutron L3 Lieutenant along with Kevin Benton for control
plane, and Assaf Muller for testing, I would like to propose Cedric
Brandily as a member of the Neutron core reviewer team under these
areas of focus.
Cedric has been a long time contributor to Neutron showing expertise
particularly
Excerpts from Yuriy Taraday's message of 2015-07-15 13:14:13 +:
Hello, oslo team.
With recent mock nightmare we should not release a new stable version of
oslotest so that projects that depend on oslotest but don't directly depend
on mock will be unblocked in gate.
I found out about
+1, Cedric has been a great contributor for a while now!
On Wed, Jul 15, 2015 at 1:47 PM, Carl Baldwin c...@ecbaldwin.net wrote:
As the Neutron L3 Lieutenant along with Kevin Benton for control
plane, and Assaf Muller for testing, I would like to propose Cedric
Brandily as a member of the
Heads up. Tacker project now supports installation using a devstack plugin.
The latest Tacker installation instruction is available in this wiki [1]
Note, the team continues to meet weekly in IRC [2]. Feel free to join if
you are interested in an ETSI MANO complaint NFV Orchestrator / VNF
That begins to looks like nova’s metadata tags and scheduler, which is a valid
use case. The underpinnings of flavors could do this, but it’s not in the
initial implementation.
doug
On Jul 15, 2015, at 12:38 PM, Kevin Benton blak...@gmail.com wrote:
Wouldn't it be valid to assign flavors
+1
On Jul 15, 2015, at 1:07 PM, Kyle Mestery mest...@mestery.com wrote:
+1, Cedric has been a great contributor for a while now!
On Wed, Jul 15, 2015 at 1:47 PM, Carl Baldwin c...@ecbaldwin.net
mailto:c...@ecbaldwin.net wrote:
As the Neutron L3 Lieutenant along with Kevin Benton for
On 16 July 2015 at 07:27, Ed Leafe e...@leafe.com wrote:
On Jul 15, 2015, at 1:08 PM, Maish Saidel-Keesing mais...@maishsk.com wrote:
* Consider the cost of introducing a brand new technology into the
deployer space. If there _is_ a way to get the desired improvement with,
say, just MySQL and
I've updated the documentation on the wiki with this criteria
https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Confirm_and_triage_bugs
On Tue, Jul 14, 2015 at 4:22 PM Mike Scherbakov mscherba...@mirantis.com
wrote:
Sounds good to start, we can always adjust later if needed. I actually
From what I’m hearing, Akihiro is recommending that we put it somewhere where
it’s easy to add horizon cores to the repo, which seems like it’d be very
useful. I think we can roll a parallel repo under the neutron tent pretty
easily. For the sake of getting collaboration moving, I’d suggest:
Hi Everyone,
Recently I have started reviewing the patch series about nested quotas in nova
[1] and I'm having trouble understanding where we currently are with identity
v3 support in nova. From what I read in a semi recent proposal [2] I think
things mostly just work if you configure to run
Please note the IRC meeting is scheduled for 16:00 UTC in
#openstack-meeting-alt
Please review meeting agenda and update if there is something you wish to
discuss.
https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda
--
--
Andrew Woodward
Mirantis
Fuel Community Ambassador
Ceph
One thing I've noticed over the last month or so looking at many
projects requirements handling is that many projects have deps
statements in tox.ini.
There are a couple of nuances here I want to call out - and I want
advice on where to document for people to find this.
Firstly, this:
deps =
+1!
On Wed, Jul 15, 2015, Carl Baldwin c...@ecbaldwin.net wrote:
As the Neutron L3 Lieutenant along with Kevin Benton for control
plane, and Assaf Muller for testing, I would like to propose Cedric
Brandily as a member of the Neutron core reviewer team under these
areas of focus.
Cedric
In re: Static CPU frequency. For modern Intel CPUs this really isn't true.
Turbo Boost is a feature that allows certain CPUs in certain conditions to
actually run at a higher clock rate that what is advertised at power on (the
havoc this causes code that depends upon timing based upon CPU
+1
On 07/15/2015 02:47 PM, Carl Baldwin wrote:
As the Neutron L3 Lieutenant along with Kevin Benton for control
plane, and Assaf Muller for testing, I would like to propose Cedric
Brandily as a member of the Neutron core reviewer team under these
areas of focus.
Cedric has been a long time
On 10:45 Jul 15, Victor Stinner wrote:
Hi,
The latest release of os-brick is not compatible with Python 3.
Different patches were merged to fix Python 3 support. tox -e py34
now executes all tests and all tests pass on Python 3.4.
I need a release of os-brick to port Cinder to Python 3. A
I agree with German. Let’s keep things together for now. Susanne
From: Eichberger, German
Sent: Wednesday, July 15, 2015 1:31 PM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Balle, Susanne; Tonse, Milan
Subject: Re: [openstack-dev] [neutron][lbaas] Horizon support for
On 07/15/15 20:40, Clint Byrum wrote:
What you describe is a spike. It's a grand plan, and you don't need
anyone's permission, so huzzah for the spike!
As far as what should be improved, I hear a lot that having multiple
schedulers does not scale well, so I'd suggest that as a primary target
In our production swift cluster, we have container sync middleware enabled in
the pipeline. But
swift container sync is not configured.
We noticed 100% CPU utilization and a lot of read/write i/os from the
swift-container-sync process
on our meta data nodes recently after we have seen
+1 Excellent addition to the team.
Edgar
On 7/15/15, 11:47 AM, Carl Baldwin c...@ecbaldwin.net wrote:
As the Neutron L3 Lieutenant along with Kevin Benton for control
plane, and Assaf Muller for testing, I would like to propose Cedric
Brandily as a member of the Neutron core reviewer team
On 07/15/2015 09:31 AM, Joshua Harlow wrote:
I do like experiments!
What about going even farther and trying to integrate somehow into mesos?
https://mesos.apache.org/documentation/latest/mesos-architecture/
Replace the hadooop executor, MPI executor with a 'VM executor' and perhaps we
could
Chris Friesen wrote:
On 07/15/2015 09:31 AM, Joshua Harlow wrote:
I do like experiments!
What about going even farther and trying to integrate somehow into mesos?
https://mesos.apache.org/documentation/latest/mesos-architecture/
Replace the hadooop executor, MPI executor with a 'VM executor'
On 07/15/2015 08:18 AM, Ed Leafe wrote:
What I'd like to investigate is replacing the current design of having
the compute nodes communicating with the scheduler via message queues.
This design is overly complex and has several known scalability
issues. My thought is to replace this with a
1 - 100 of 155 matches
Mail list logo
