thanks for sharing, useful indeed.
On Fri, Oct 2, 2015 at 8:51 PM, Ricardo Carrillo Cruz <
ricardo.carrillo.c...@gmail.com> wrote:
> Erm, yeah, I hear your pain with processing output with awk.
>
> Having the option to output CSV is cool :-).
> Thanks for sharing.
>
> Cheers
>
> 2015-10-02 21:4
Hi,
There is an option in Neutron called max_fixed_ips_per_port that limits the
number of IP addresses that can be assigned to each port. It doesn't appear
to have a clear use case since we prevent users from setting IPs on ports
attached to networks they don't own (shared networks). I have filed
> Now the next challenge is with Ubuntu packages, only python-libvirt
> 1.2.15 is available in Ubuntu Willy. :-/
>
> Just create a PPA and build 1.2.17 from the git sources by copying the
`debian` directory from the package.
I can do it for you over the weekend if you want it.
Pavel
_
On 2015-10-02 4:18 PM, Pavel Boldin wrote:
>
> You have to pass device names from /dev/, e.g., if a VM has
> ephemeral disk
> attached at /dev/vdb you need to pass in 'vdb'. Format expected by
> migrate_disks is ",...".
>
>
> This is the format expected by the `virsh' utility and
Resending, forgot to subscribe.
> You have to pass device names from /dev/, e.g., if a VM has ephemeral disk
> attached at /dev/vdb you need to pass in 'vdb'. Format expected by
> migrate_disks is ",...".
>
This is the format expected by the `virsh' utility and will not work in
Python.
The lib
Erm, yeah, I hear your pain with processing output with awk.
Having the option to output CSV is cool :-).
Thanks for sharing.
Cheers
2015-10-02 21:49 GMT+02:00 Thomas Goirand :
> Hi,
>
> I saw the csv output format of openstackclient going and coming back.
> Please leave it in, it's super usefu
Hey All,
So I was working on Bug 1493520 which is about what happens when a
controller runs out of space. For this I came up with a solution[1] to
leverage pacemaker to migrate services away from the controller when
it runs out of space. This works great for rabbitmq/mysql where if
they run out o
Hi,
I saw the csv output format of openstackclient going and coming back.
Please leave it in, it's super useful, especially when you combine it
with "q-text-as-data". Just try to apt-get install q-text-as-data" and
try by yourself:
openstack endpoint list --long -f csv | \
q -d , -H 'SELE
On Fri, Oct 02, 2015 at 10:07:32PM +0300, Gal Sagie wrote:
> If you are not familiar with Kuryr you can read my blog post about it here
> [1].
> Basically we already have a working demo integrating with Neutron and we
> are going to show
> it in OpenStack Tokyo (probably in the keynotes and in a sp
Hello there,
A couple of people were asking me about the status of the security spec[1] for
openstack-ansible. Here are a few quick updates as of today:
* We've moved away from considering CIS temporarily due to licensing and
terms of use issues
* We're currently adapting the RHEL 6 STIG[2
Hi Ben,
If you are not familiar with Kuryr you can read my blog post about it here
[1].
Basically we already have a working demo integrating with Neutron and we
are going to show
it in OpenStack Tokyo (probably in the keynotes and in a specific Kuryr
session).
For the OVN part, there are some are
On 2015-10-02 17:16:30 + (+), Jeremy Stanley wrote:
> A bug was introduced into jenkins-job-builder earlier today which
> caused some select jobs to always pass. The regression has been
> identified, reverted and all affected jobs updated, but any changes
> should be rechecked to get accura
On 10/02/2015 02:26 PM, Murali R wrote:
> Hi Russell,
>
> Thank you these are really good. Had a quick question. When you create a
> logical switch in your first script (line 23) - at what point is it
> associated with br-int ? Is it on line 45? So I can create any switch
> and when I associated l
Thanks Matt for raising this topic once again, I strongly agree with
you, I've even added the following wording to our backports policy back
in March to address the same problem:
"For a bug targeted for stable release series, cherry-pick the fix
commit onto the stable/x.x branch for each serie
Hi Russell,
Thank you these are really good. Had a quick question. When you create a
logical switch in your first script (line 23) - at what point is it
associated with br-int ? Is it on line 45? So I can create any switch and
when I associated logical port it associates logical switch ? Or is the
Tim,
Answers to your questions while I was away:
>Do you think docker images would be significantly smaller than the VM?
>If not, I don't see a good reason to move to docker.
Yes it will be smaller because we will not be shipping the OS image
>BTW—I tried the ssh, and it worked great.
Cool
>is
Moshe Levi wrote:
-Original Message-
From: Sean M. Collins [mailto:s...@coreitpro.com]
Sent: Thursday, October 01, 2015 6:42 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] New cycle started. What are you up
to, folks?
On Thu,
A bug was introduced into jenkins-job-builder earlier today which
caused some select jobs to always pass. The regression has been
identified, reverted and all affected jobs updated, but any changes
should be rechecked to get accurate results if they ran one or more
of the following jobs between 04:
Forwarding since Chris isn’t subscribed.
*From:* Chris Clason [mailto:ccla...@mirantis.com]
*Sent:* Friday, October 02, 2015 6:30 PM
*To:* Sheena Gregson ; OpenStack Development Mailing
List (not for usage questions)
*Subject:* Re: [openstack-dev] [Fuel] 8.0 Region name support / Multi-DC
We
On Fri, Oct 02, 2015 at 06:20:31AM +, Koniszewski, Pawel wrote:
> > -Original Message-
> > From: Mathieu Gagné [mailto:mga...@internap.com]
> > Sent: Thursday, October 1, 2015 7:24 PM
> > To: OpenStack Development Mailing List (not for usage questions)
[. . .]
> > >> I have taken the
Plans for multi-DC: my understanding is that we are working on developing a
whitepaper in Q4 that will provide a possible OpenStack multi-DC
configuration, but I do not know whether or not we intend to include Fuel
in the scope of this work (my guess would be no). Chris – I copied you in
case you
Voting for the TC Election is now open and will remain open until 23:59
UTC October 9th 2015.
We are electing 6 positions from a pool of 19 candidates[0].
When you receive your email providing your link to the ballot, follow
the instructions that are available on the page where you may vote. If
y
Dear Fuelers,
I would like to nominate Alexander Adamov and Olena Logvinova for the
fuel-docs-core status:
http://stackalytics.com/?user_id=aadamov&release=all&project_type=all&module=fuel-docs
http://stackalytics.com/?user_id=ologvinova&release=all&project_type=all&module=fuel-docs
They are mak
We're happy to announce the release of:
* puppet-nova 5.2.1
* puppet-neutron 5.2.1
* puppet-cinder 5.2.0
* puppet-glance 5.2.0
* puppet-ceilometer 5.2.0
* puppet-heat 5.2.0
* puppet-keystone 5.2.0
* puppet-openstack_extras 5.1.0
More details about releases:
https://wiki.openstack.org/wiki/Puppet/r
Very nice thread. Sharing is caring, so... (please notice some of my
ideas are aligned with Ihar):
* Kill bugs
* Kill bugs
* Kill bugs
* RPC Neutron Objects Callback:
- upgrade path: That wasn't needed before, but we're going to need it.
- implement an strategy to avoid the out-of-order
On 2015-10-02 10:20:49 -0500 (-0500), Kevin L. Mitchell wrote:
[...]
> it feels wrong for us to install dependencies not directly related
> to testing, even if we also test the doc generation.
[...]
It's a bit of a mischaracterization to suggest that there is some
specific set of "dependencies [..
Hi all
> Not all of these are covered by specs yet and all the existing specs need
> reviews. Please look at the etherpad and see if there is anything you think is
> missing.
What about adding a way to migrate files which are not migrated at the moment,
like console.log?
I think that could be
On 10/02/2015 11:32 AM, Russell Bryant wrote:
> On 10/01/2015 03:26 PM, Russell Bryant wrote:
>> On 10/01/2015 09:45 AM, Ihar Hrachyshka wrote:
>>> Hi all,
>>>
>>> I talked recently with several contributors about what each of us
>>> plans for the next cycle, and found it’s quite useful to share
On 01/10/15 14:47, Ihar Hrachyshka wrote:
> Hi all,
>
> I talked recently with several contributors about what each of us plans for
> the next cycle, and found it’s quite useful to share thoughts with others,
> because you have immediate yay/nay feedback, and maybe find companions for
> next adv
On 10/01/2015 03:26 PM, Russell Bryant wrote:
> On 10/01/2015 09:45 AM, Ihar Hrachyshka wrote:
>> Hi all,
>>
>> I talked recently with several contributors about what each of us
>> plans for the next cycle, and found it’s quite useful to share
>> thoughts with others, because you have immediate y
On 09/27/2015 04:18 PM, Russell Bryant wrote:
> On 09/27/2015 06:50 AM, Kevin Benton wrote:
>> Assuming it implements the normal provider networks API, you just
>> specify the segmentation_id when you create the network.
>>
>> neutron net-create NET_NAME --provider:network_type vlan
>> --provider:
Folks,
i've dug around 8.0 roadmap and didn't find anythind regarding Multi-DC
support.
My ask is about tiny(but useful) feature: give user ability to *specify
Region name in UI.*
Region name is already in every puppet module, so we just need to add this
to UI.
Do we have smth already?
More ge
On Fri, 2015-10-02 at 11:00 -0400, Sean Dague wrote:
> On 10/02/2015 10:53 AM, Kevin L. Mitchell wrote:
> > The Pillow-breaking-gate issue was related to having doc dependencies
> > listed in the test-requirements.txt; however, those dependencies are not
> > needed for testing, except for doc testi
On 02/10/15 10:55, Sergey Kraynev wrote:
Thank you all for the feedback :)
Let's continue with the same time frames.
Zane, I will try to move main/complex questions on the 2000 UTC
meetings to allow you to debate in it :)
Thanks, but don't slow anything down for my benefit :) I think it would
On 02/10/15 16:03, Jeremy Stanley wrote:
> On 2015-10-02 11:33:05 + (+), Neil Jerram wrote:
> [...]
>> For the PyPI registration I put 0.1.0, but that doesn't mean that I
>> expect that to be the version number when networking-calico is actually
>> released. I guessed that PyPI might impose
On 10/02/2015 10:53 AM, Kevin L. Mitchell wrote:
> The Pillow-breaking-gate issue was related to having doc dependencies
> listed in the test-requirements.txt; however, those dependencies are not
> needed for testing, except for doc testing and generation. What do
> people think about creating a n
On 2015-10-02 11:33:05 + (+), Neil Jerram wrote:
[...]
> For the PyPI registration I put 0.1.0, but that doesn't mean that I
> expect that to be the version number when networking-calico is actually
> released. I guessed that PyPI might impose an increasing version number
> requirement, and
Thank you all for the feedback :)
Let's continue with the same time frames.
Zane, I will try to move main/complex questions on the 2000 UTC
meetings to allow you to debate in it :)
On 1 October 2015 at 20:13, x Lyn wrote:
> +1 for 7:00
>
> Sent from my iPhone
>
>> On Oct 1, 2015, at 10:36 PM, Z
The Pillow-breaking-gate issue was related to having doc dependencies
listed in the test-requirements.txt; however, those dependencies are not
needed for testing, except for doc testing and generation. What do
people think about creating a new "doc-requirements.txt" file that would
contain only th
Hello,
thanks for bringing up this topic, that's what I wanted to discuss on next
puppet-openstack irc meeting.
So, user case is following: users may want to install Debian packages on
Ubuntu host or vice versa,
the same problem can probably happen with CentOS, RHEL, Fedora; or users
may use non-
On Fri, Oct 2, 2015 at 7:43 AM, Ivan Udovichenko
wrote:
> Hello,
>
> On 10/02/2015 03:15 PM, Emilien Macchi wrote:
>> Hey Thomas,
>>
>> On 10/02/2015 04:33 AM, Thomas Goirand wrote:
>> [...]
>>> We also may need, at some point, to add the type mosdebian and moscentos
>>> to the list of supported p
Hello everyone,
Due to release-critical issues spotted in Manila during RC1 testing, a
new release candidate was created for Liberty. The list of RC2 fixes, as
well as RC2 tarballs are available at:
https://launchpad.net/manila/liberty/liberty-rc2
Unless new release-critical issues are found tha
On Fri, Oct 2, 2015 at 6:33 AM, Neil Jerram
wrote:
> On 02/10/15 11:42, Neil Jerram wrote:
> > Thanks Kyle! I'm looking at this now for networking-calico.
>
> Done, please see https://pypi.python.org/pypi/networking-calico.
>
> When you release, how will the version number be decided? And should
On 10/02/2015 05:48 AM, Francesc Pinyol Margalef wrote:
> Hi,
> In a previous message in general openstack list I reported a problem
> when trying to mount an NFS volume from a Fujitsu Eternus DX
> http://lists.openstack.org/pipermail/openstack/2015-July/013578.html
>
> The issue is that this file
Excerpts from Doug Hellmann's message of 2015-09-28 16:16:59 -0400:
> It has been a while since we've reviewed the requirements-core team
> members. Since it's the end of the cycle, I did a quick scan of the
> stats this week and I am proposing some changes based on participation.
>
> I spoke with
Hi all,
The case of automatic evacuation (or resurrection currently), is a topic
which surfaces once in a while, but it isn't yet fully supported by
OpenStack and/or by the cluster services. There was some attempts to
bring the feature into OpenStack, however it turns out it cannot be
easily i
On Fri, Oct 02, 2015 at 08:19:47AM +0300, Gal Sagie wrote:
> *OVN*
>
>1) OVN integration with Kuryr
Can you say anything more about what that entails?
Thanks,
Ben.
__
OpenStack Development Mailing List (not for usage q
Hello,
On 10/02/2015 03:15 PM, Emilien Macchi wrote:
> Hey Thomas,
>
> On 10/02/2015 04:33 AM, Thomas Goirand wrote:
> [...]
>> We also may need, at some point, to add the type mosdebian and moscentos
>> to the list of supported package suite, as there still will be some
>> differences between th
Hey Thomas,
On 10/02/2015 04:33 AM, Thomas Goirand wrote:
[...]
> We also may need, at some point, to add the type mosdebian and moscentos
> to the list of supported package suite, as there still will be some
> differences between the upstream Debian or CentOS packages. What is the
> best way to a
I'm not sure if core reviewers should be so harsh. But the guideline seems
to be very useful. Guys, please don't create backports too early.
On Fri, Oct 2, 2015 at 2:00 PM, Matthew Mosesohn
wrote:
> Hi Fuelers,
>
> I would like to address a concern I have with backporting policy. I'm sure
> all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi All
The Ubuntu OpenStack Engineering team is pleased to announce the
general availability of the first release candidates for the OpenStack
Liberty release in Ubuntu 15.10 development and for Ubuntu 14.04 LTS
via the Ubuntu Cloud Archive.
Furthe
On 02/10/15 09:08, Thierry Carrez wrote:
> Hayes, Graham wrote:
>> In previous years we have had "related open source project" sessions at
>> the design summit, is that happening this year, or is space at too much
>> of a premium?
>
> With the set up of the big tent, a larger number of project tea
On 02/10/15 11:42, Neil Jerram wrote:
> Thanks Kyle! I'm looking at this now for networking-calico.
Done, please see https://pypi.python.org/pypi/networking-calico.
When you release, how will the version number be decided? And should I
make a change to put that version into the source somewhere,
Hi Fuelers,
I would like to address a concern I have with backporting policy. I'm sure
all of you know that we should always land patches to master before it
reaches stable/X.X branch. What you are not aware of probably is that many
people are making cherry picks well in advance of gathering revie
On 30/09/15 19:58, Kyle Mestery wrote:
> Folks:
>
> In trying to release some networking sub-projects recently, I ran into
> an issue [1] where I couldn't release some projects due to them not
> being registered on pypi. I have a patch out [2] which adds pypi
> publishing jobs, but before that can
> -Original Message-
> From: Sean M. Collins [mailto:s...@coreitpro.com]
> Sent: Thursday, October 01, 2015 6:42 PM
> To: OpenStack Development Mailing List (not for usage questions)
>
> Subject: Re: [openstack-dev] [neutron] New cycle started. What are you up
> to, folks?
>
> On Thu, O
Hi everybody,
I'm trying to to achieve 2 things:
#1 Add common macvtap support for all kind of interfaces to neutron core
(via a macvtap ml2-plugin & agent) [1]. There has been a long discussion
where this should land but finally we Kyle decided to do it in tree [2].
For the agent part, Sean Co
Greetings,
First and foremost, thanks to all the amazing candidates running for
the TC. I'm very excited to see new candidacies, other candidacies
from the previous terms and exciting proposals.
Just like for the PTL elections, I took the time to share a few
thoughts about the upcoming TC voting
Hi,
In a previous message in general openstack list I reported a problem
when trying to mount an NFS volume from a Fujitsu Eternus DX
http://lists.openstack.org/pipermail/openstack/2015-July/013578.html
The issue is that this file server does not allow mounts as root, and
this behaviour cannot be
Hi,
+1 to Evgeniy... Since 'critical' and 'high' were cleared up from SCF to
Release we should assume that new Cricital and High bugs are introduced by
'new' features. In this case feature team should fix it.
--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser
On Fri, Oct 2, 2015 at
Hi!
I've already discussed the topic on IRC with Emilien, however, it came
back within Mirantis, and as I don't have puppet skills, I was not able
to answer my colleagues correctly. Opening this thread is an attempt to
solve the issue once and for all. Hopefully, Emilien (and other puppet
guys) wi
On 10/01/2015 09:39 PM, Thomas Goirand wrote:
> On 09/30/2015 01:58 PM, Thomas Goirand wrote:
>> 3/ Horizon dependencies still in NEW queue
>> ==
>>
>> It is also worth noting that Horizon hasn't been fully FTP master
>> approved, and that some packages are s
Hi Mike,
According to the description of the role, I wouldn't say that the role is
less architectural than
political, since PTL should review designs and resolve conflicts between
cores (which are
usually technical), PTL should also have strong skills in software
architecture, and understanding
of
On 09/30/2015 10:08 AM, Dougal Matthews wrote:
Hi,
What is the standard practice for defining public API's for OpenStack
libraries? As I am working on refactoring and updating tripleo-common I have
to grep through the projects I know that use it to make sure I don't break
anything.
Personally I
Hayes, Graham wrote:
> In previous years we have had "related open source project" sessions at
> the design summit, is that happening this year, or is space at too much
> of a premium?
With the set up of the big tent, a larger number of project teams need
space at the Summit, and it is easier than
Hi Dmitry,
Thanks for the information.
>> My personal opinion is that we can ignore our medium-priority technical
debt bugs for now. We should fix them but there is nothing that cannot be
postponed here. We will continue fixing them in background. The only
exception here should be bugs related to
A library that seems to have a pretty nice abstraction for this kind of
thing/pattern, could be an idea to use it, or have something similar
like it...
https://boltons.readthedocs.org/en/latest/fileutils.html#atomic-file-saving
-Josh
On Sat, 26 Sep 2015 10:48:39 +0200
Julien Danjou wrote:
> On
67 matches
Mail list logo