Hello Everyone,
We are just back from a week in China where we met with various local
community
members to discuss about Dragonflow roadmap and design.
We will have a nice number of people from different companies joining us on
the development
of Dragonflow and some are planning to deploy it.
We
Hi, all:
I spend some times to collect oslo.* versions of openstack
projects(which has related puppet module), please check it in following
table:
https://github.com/openstack/puppet-oslo#module-description
From the table, we can find most of oslo.* libraries are the same among
the o
Adam,
Any modern datacenter network, especially those with 10 Gbps or faster
connectivity, should support jumbo frames for performance reasons. However,
depending on the network infrastructure, jumbo frames does not always mean
a 9000 MTU, so neutron should support a configurable value rather than
Hey Folks,
So on Friday our CI unit tests for puppet version 3.8 started
failing[0] due to an update to facter which seems to have issues with
one of our ceph facts[1]. This has blocked up the pipeline, so in
order to unstick it we are looking at updating the ceph
osd_devices_list fact[2] to addr
Adam Lawson wrote on 01/23/2016 02:27:46 PM:
> For the sake of over-simplification, is there ever a reason to NOT
> enable jumbo frames in a cloud/SDN context where most of the traffic
> is between virtual elements that all support it? I understand that
> some switches do not support it and tra
I guess my wisdom would be 'why'? What does this enable you to do that you
couldn't do with similar ease with the formats we have and are people
trying to do that frequently.
We've seen in cinder that image formats have a definite security surface to
them, and with glance adding arbitrary conversi
For the sake of over-simplification, is there ever a reason to NOT enable
jumbo frames in a cloud/SDN context where most of the traffic is between
virtual elements that all support it? I understand that some switches do
not support it and traffic form the web doesn't support it either but
besides t
Hi Roland,
> I don't think it would be difficult to add support for non-periodic
> metrics/alarms. There are a couple of approaches we could take, so a design
> discussion would be good to have if you are interested in implementing this.
> This is feature that we are not working on right now, b
Excerpts from Brian Rosmaita's message of 2016-01-23 06:54:26 -0800:
> Please provide feedback about a proposal to add 'tar' as a new Glance
> disk_format.[0]
>
> The Ironic team is adding support for "OS tarball images" in Mitaka. This is
> a compressed tar archive of a / (root filesystem). Th
We are thrilled to announce the release of:
oslo.versionedobjects 1.4.0: Oslo Versioned Objects library
This release is part of the mitaka release series.
With source available at:
http://git.openstack.org/cgit/openstack/oslo.versionedobjects
With package available at:
https://pypi.py
We are delighted to announce the release of:
oslo.db 4.3.1: Oslo Database library
This release is part of the mitaka release series.
With source available at:
http://git.openstack.org/cgit/openstack/oslo.db
With package available at:
https://pypi.python.org/pypi/oslo.db
Please report
Please provide feedback about a proposal to add 'tar' as a new Glance
disk_format.[0]
The Ironic team is adding support for "OS tarball images" in Mitaka. This is a
compressed tar archive of a / (root filesystem). These tarballs are created by
first installing the OS packages in a chroot and t
Hello,
Why don't we introduce additional state for nodes like 're-deploying'. If
deployment was stopped we don't erase nodes with this state, but change the
status to 'error' or 'ready' , for example.
Or we can add warning message that 'stop' button would destroy every and
each node.
On Fri, Jan
Hi Deklan,
Following up our conversation on restoring from swift, yes there's a bug,
you are right, I've reproduced it.
It can be reproduced when python-swiftclient 2.7.0 is installed on the
system.
In Liberty and Mitaka the requirement is python-swiftclient>=2.2.0.
The issue should be solved by
> On Jan 23, 2016, at 5:51 AM, Julien Danjou wrote:
>
>> On Fri, Jan 22 2016, Doug Hellmann wrote:
>>
>> The openstack/releases repo is used to produce releases for managed
>> projects, but all projects may submit information about their releases
>> to have that data published for reference. I
On Fri, Jan 22 2016, Doug Hellmann wrote:
> The openstack/releases repo is used to produce releases for managed
> projects, but all projects may submit information about their releases
> to have that data published for reference. If you are the release
> liaison for a project, and you are tagging
16 matches
Mail list logo