os-vif has been integrated into nova since the newton cycle. With the
integration of os-vif, the expectation is that all the old, non-os-vif
plugging/unplugging code found in [1] will be replaced by code that harnesses
os-vif plugins [2]. This has happened for a few of the VIF types, and newer
VIFs
On Thu, 2017-07-13 at 07:54 -0600, Kevin Benton wrote:
> On Thu, Jul 13, 2017 at 7:26 AM, Stephen Finucane
wrote:
>
> > os-vif has been integrated into nova since the newton cycle. With the
> > integration of os-vif, the expectation is that all the old, non-os-vif
> >
On Fri, 2017-07-21 at 10:33 -0400, Doug Hellmann wrote:
> Excerpts from Alexandra Settle's message of 2017-07-21 13:41:58 +:
> > Hey everyone,
> >
> > Put your hand in the air* if you’re attending the PTG!
> >
> > Myself and the potential PTL will need to start planning shortly, and it
> > wo
On Wed, 2017-08-02 at 09:55 -0500, Matt Riedemann wrote:
> Now that Stephen Finucane is back from enjoying his youth and
> gallivanting all over Europe, and we talked about a few things in IRC
> this morning on the docs migration for Nova, I wanted to dump my
> concerns here
On Wed, 2017-08-02 at 09:55 -0500, Matt Riedemann wrote:
> Now that Stephen Finucane is back from enjoying his youth and
> gallivanting all over Europe, and we talked about a few things in IRC
> this morning on the docs migration for Nova, I wanted to dump my
> concerns here
On Wed, 2017-08-02 at 09:28 -0600, Chris Friesen wrote:
> On 08/02/2017 09:22 AM, Stephen Finucane wrote:
> > On Wed, 2017-08-02 at 09:55 -0500, Matt Riedemann wrote:
> > > 3. The patch for the import of the admin guide [8] is missing some CLI
> > > specific pages wh
On Wed, 2017-08-02 at 09:28 -0700, Clark Boylan wrote:
> On Wed, Aug 2, 2017, at 07:55 AM, Matt Riedemann wrote:
> > Now that Stephen Finucane is back from enjoying his youth and
> > gallivanting all over Europe, and we talked about a few things in IRC
> > this morning on t
On Tue, 2017-08-22 at 20:18 -0500, Matt Riedemann wrote:
> I'm proposing that we add gibi to the nova core team. He's been around
> for awhile now and has shown persistence and leadership in the
> multi-release versioned notifications effort, which also included
> helping new contributors to Nov
Nova has a feature whereby it will provide instance host names that cloud-init
can extract and use inside the guest, i.e. this won't happen without cloud-
init. These host names are fully qualified domain names (FQDNs) based upon the
instance name and local domain name. However, as noted in bug #16
On Mon, 2017-09-04 at 11:51 +, Gary Kotton wrote:
> On 9/4/17, 11:18 AM,
"Stephen Finucane" wrote:
> > Nova has a feature whereby
it will provide instance host names that cloud-
> > init can extract and use
inside the guest, i.e. this won't happen without
> &
On Tue, 2017-09-05 at 12:30 -0500, Ben Nemec wrote:
> On 09/04/2017 07:48 AM, Stephen Finucane wrote:
> > On Mon, 2017-09-04 at 11:51 +, Gary Kotton wrote:
> > > On 9/4/17, 11:18 AM, "Stephen Finucane" wrote:
> > > > Nova has a feature whereby
On Wed, 2017-09-06 at 15:06 +, Jeremy Stanley wrote:
> On 2017-09-06 10:40:14 +0100 (+0100), Stephen Finucane wrote:
> [...]
> > OK, and we do want to use a FQDN as the hostnames inside the
> > guest? That's my key question. Random ServerFault questions seems
> >
Hey,
NUMA locality matters as much for NICs used e.g for Open vSwitch as for SR-IOV
devices. At the moment, nova support NUMA affinity for PCI passthrough devices
and SR-IOV devices, but it makes no attempt to do the same for other NICs. In
the name of NFV enablement, we should probably close this
On Mon, 2017-09-25 at 17:36 +0200, Jakub Jursa wrote:
> Hello everyone,
>
> We're experiencing issues with running large instances (~60GB RAM) on
> fairly large NUMA nodes (4 CPUs, 256GB RAM) while using cpu pinning. The
> problem is that it seems that in some extreme cases qemu/KVM can have
> sig
On Tue, 2017-10-03 at 12:57 -0700, Mike Perez wrote:
> I noticed that the project creator [1] and cookiecutter [2] promote using
> launchpad. If we're migrating projects to storyboard today, should we stop
> promoting launchpad for new projects?
Not to hijack the thread but, we're moving projects
The Python packaging ecosystem is shifting under our feet and we have a couple
of things in pbr we need to look at over the next few months (Pipfiles, pyenv,
changes in setuptools setup.cfg, ...). We should probably track these somewhere
and Storyboard [1] seems like a better candidate for doing th
Hey,
I'm not actually sure what the protocol is for adding/removing cores to a
library project without a PTL, so I'm just going to put this out there: I'd
like to propose the following changes to the os-vif core team.
- Add 'nova-core'
os-vif makes extensive use of objects and we've had a few
On Tue, 2017-10-24 at 15:32 +0100, Stephen Finucane wrote:
> Hey,
>
> I'm not actually sure what the protocol is for adding/removing cores to a
> library project without a PTL, so I'm just going to put this out there: I'd
> like to propose the following changes to th
As part of the documentation onboarding session this morning, we gave a small
talk on how people can actually avoid writing documentation (or rather use the
documentation they have already stored in their code). There seems to be a
general lack of awareness about these tools and I've uploaded the s
I'm not sure what the procedure for this is but here goes.
I've noticed that the 'os-api-ref' project seems to have its own group
of cores [1], many of whom are no longer working on OpenStack (at
least, not full-time), and has a handful of open patches against it
[2]. Since the doc team has recent
On Tue, 2018-01-09 at 16:30 +0530, Sriharsha Basavapatna wrote:
> On Tue, Jan 9, 2018 at 2:20 PM, Sriharsha Basavapatna
> wrote:
> > Hi Andreas,
> >
> > On Tue, Jan 9, 2018 at 12:04 PM, Andreas Jaeger
> > wrote:
> > > On 2018-01-09 07:00, Sriharsha Basavapatna wrote:
> > > > Hi,
> > > >
> > > >
On Tue, 2018-01-09 at 10:25 +0100, Gaetan wrote:
> Hello
>
> I have submitted this patch ([1]) that add support for v_version in
> PBR. Basically I can tag v1.0.0 instead of 1.0.0 to release 1.0.0.
>
> However, after rework it appears PBR does not behaves well, even if
> the unit tests pass:
> On
On Thu, 2018-01-04 at 15:39 +, Stephen Finucane wrote:
> I'm not sure what the procedure for this is but here goes.
>
> I've noticed that the 'os-api-ref' project seems to have its own group
> of cores [1], many of whom are no longer working on OpenStack (at
&g
On Thu, 2016-08-25 at 14:11 +0400, Fawaz Mohammed wrote:
> Have you enabled huge page on the host level?
> Do you have enough vn.nr_hugepages?
> As per your requirements, you need a host with 512 hugepage (1G/2M).
> Check your host's /etc/sysctl.conf file and see vm.nr_hugepages
> value.
As a more
On Fri, 2018-02-09 at 09:01 -0600, Matt Riedemann wrote:
> I'd like to add Takashi to the python-novaclient core team.
>
> python-novaclient doesn't get a ton of activity or review, but Takashi
> has been a solid reviewer and contributor to that project for quite
> awhile now:
>
> http://stacka
tl;dr: Make sure you stop using pbr's autodoc feature before converting
them to the new PTI for docs.
There have been a lot of patches converting projects to use the new
Project Testing Interface for building docs [1]. Generally, these make
the following changes:
1. Move any requirements for b
On Wed, 2018-03-21 at 09:57 -0500, Sean McGinnis wrote:
> On Wed, Mar 21, 2018 at 10:49:02AM +0000, Stephen Finucane wrote:
> > tl;dr: Make sure you stop using pbr's autodoc feature before converting
> > them to the new PTI for docs.
> >
> > [snip]
> >
>
On Fri, 2018-03-23 at 12:23 -0400, Doug Hellmann wrote:
> Excerpts from Monty Taylor's message of 2018-03-23 08:03:22 -0500:
> > On 03/22/2018 05:43 AM, Stephen Finucane wrote:
> > >
> > > That's unfortunate. What we really need is a migration path from t
+1
On Mon, 2018-03-26 at 19:00 -0700, melanie witt wrote:
> Howdy everyone,
>
> I'd like to propose that we add Eric Fried to the nova-core team.
>
> Eric has been instrumental to the placement effort with his work on
> nested resource providers and has been actively contributing to many
> oth
As noted last week [1], we're trying to move away from pbr's autodoc
feature as part of the new docs PTI. To that end, I've created
sphinxcontrib-apidoc, which should do what pbr was previously doing for
us by via a Sphinx extension.
https://pypi.org/project/sphinxcontrib-apidoc/
This works by
On Wed, 2018-03-28 at 14:14 -0500, Sean McGinnis wrote:
> On Thu, Mar 22, 2018 at 10:43:45AM +0000, Stephen Finucane wrote:
> > On Wed, 2018-03-21 at 09:57 -0500, Sean McGinnis wrote:
> > > On Wed, Mar 21, 2018 at 10:49:02AM +, Stephen Finucane wrote:
> > > > t
On Thu, 2018-03-29 at 07:47 -0500, Sean McGinnis wrote:
> > >
> > > It's not mentioned here, but I discovered today that Cinder is using the
> > > sphinx.ext.autodoc module. Is there any issue with using this?
> > >
> >
> > Nope - sphinx-apidoc and the likes use autodoc under the hood. You can
>
On Mon, 2018-04-02 at 19:41 -0400, Zane Bitter wrote:
> On 28/03/18 10:31, Stephen Finucane wrote:
> > As noted last week [1], we're trying to move away from pbr's autodoc
> > feature as part of the new docs PTI. To that end, I've created
> > sphinxcontrib-
On Tue, 2018-04-03 at 12:04 -0400, Zane Bitter wrote:
> On 03/04/18 06:28, Stephen Finucane wrote:
> > On Mon, 2018-04-02 at 19:41 -0400, Zane Bitter wrote:
> > > On 28/03/18 10:31, Stephen Finucane wrote:
> > > > As noted last week [1], we're trying to move away
On Thu, 2018-04-05 at 16:36 -0400, Zane Bitter wrote:
> On 21/03/18 06:49, Stephen Finucane wrote:
> > As noted by Monty in a prior openstack-dev post [2], some projects rely
> > on a pbr extension to the 'build_sphinx' setuptools command which can
> > automatical
On Wed, 2018-03-28 at 15:31 +0100, Stephen Finucane wrote:
> As noted last week [1], we're trying to move away from pbr's autodoc
> feature as part of the new docs PTI. To that end, I've created
> sphinxcontrib-apidoc, which should do what pbr was previously doing
On Fri, 2018-04-06 at 08:02 -0500, Sean McGinnis wrote:
> > >
> > > How can we enable warning_is_error in the gate with the new PTI? It's
> > > easy enough to add the -W flag in tox.ini for local builds, but as you
> > > say the tox job is never called in the gate. In the gate zuul checks for
>
On Wed, 2018-04-25 at 12:06 -0500, Sean McGinnis wrote:
> > > >
> > > > [1] https://review.openstack.org/#/c/564232/
> > > >
> > >
> > > The only concern I have is that it may slow the transition to the
> > > python 3 version of the jobs, since someone would have to actually
> > > fix the warnin
On Tue, 2018-05-08 at 11:49 +0200, Balázs Gibizer wrote:
> Hi,
>
> The oslo UUIDField emits a warning if the string used as a field value
> does not pass the validation of the uuid.UUID(str(value)) call [3]. All
> the offending places are fixed in nova except the nova-manage cell_v2
> map_insta
I imagine most people have been seeing warnings like the one below
raised by various openstack packages recently:
.tox/py27/lib/python2.7/site-packages/psycopg2/__init__.py:144: UserWarning:
The psycopg2
wheel package will be renamed from release 2.8; in order to keep installing
from binary
On Tue, 2018-05-15 at 07:24 -0400, Doug Hellmann wrote:
> Excerpts from Stephen Finucane's message of 2018-05-15 11:44:11 +0100:
> > I imagine most people have been seeing warnings like the one below
> > raised by various openstack packages recently:
> >
> > .tox/py27/lib/python2.7/site-packages
On Thu, 2018-04-26 at 15:49 +0100, Stephen Finucane wrote:
> On Wed, 2018-04-25 at 12:06 -0500, Sean McGinnis wrote:
> > > > >
> > > > > [1] https://review.openstack.org/#/c/564232/
> > > > >
> > > >
> > > > The only c
There have been a couple of threads about an updated "PTI" for
documentation bouncing around the mailing list of late.
* http://lists.openstack.org/pipermail/openstack-dev/2018-March/128817
.html
* http://lists.openstack.org/pipermail/openstack-dev/2018-March/128594
.html
I've been told t
On Mon, 2018-06-04 at 10:49 -0700, Nadathur, Sundar wrote:
> Hi,
>
> Cyborg needs to create RCs and traits for accelerators. The
> original plan was to do that with nested RPs. To avoid rushing
> the
> Nova developers, I had proposed that Cyborg could start by
> applying
>
On Wed, 2018-06-06 at 16:04 -0400, Doug Hellmann wrote:
> I have started submitting a series of patches to fix up the tox.ini
> settings for projects as a step towards running "python3 first"
> [1]. The point of doing this now is to give teams a head start on
> understanding the work involved as we
nova has worked hard over the last few cycles to identify and reduce
the amount of tech debt we're carrying. One such item identified early
on was the lack of automated testing and upstream documentation for NFV
features, such as CPU pinning, realtime, hugepages, SR-IOV, and PCI
passthrough. We dis
On Thu, 2016-12-01 at 14:48 +, Moshe Levi wrote:
> Hi all,
>
> I would like to update the frequency of the SR-IOV meeting to be bi-
> weekly [1].
> Does anyone see value in keeping it as weekly meeting?
>
> [1] - https://review.openstack.org/#/c/405415/
Seeing as we don't have any specs dur
Just a quick heads up that an upcoming change to nova's 'tox.ini' will
change the behaviour of multiple environments slightly.
https://review.openstack.org/#/c/534382/9
With this change applied, tox will start sharing environment
directories (e.g. '.tox/py27') among environments with identical
On Fri, 2018-07-13 at 15:23 -0500, Matt Riedemann wrote:
> There are currently no open changes for the nova-network API removal
> tracked here [1] but there are at least two low-hanging fruit APIs to
> remove:
>
> * os-floating-ips-bulk
> * os-floating-ips-dns
The two of these are done now.
*
On Wed, 2018-08-01 at 09:27 -0400, Doug Hellmann wrote:
> Moisés Guimarães (moguimar) did quite a bit of work on oslo.config
> during the Rocky cycle to add driver support. Based on that work,
> and a discussion we have had since then about general cleanup needed
> in oslo.config, I think he would
tl;dr: It seems Paste [1] may be entering unmaintained territory and we
may need to do something about it.
I was cleaning up some warning messages that nova was issuing this
morning and noticed a few coming from Paste. I was going to draft a PR
to fix this, but a quick browse through the Bitbucket
On Wed, 2018-07-25 at 15:22 +0530, pranab boruah wrote:
> Hello folks,
> I have filed a bug in os-vif:
> https://bugs.launchpad.net/os-vif/+bug/1778724 and working on a
> patch. Any feedback/comments from you guys would be extremely
> helpful.
> Bug details:
> OVS DB server has the feature of lis
I saw lots of print
> > statements which are easy to fix, though I even wonder if the code in
> > the python-novnc package is useful. Who's using it? Nova-novncproxy?
> > That's unlikely, since I didn't package a Python 3 version for it.
>
> Stephen Finucane (step
On Mon, 2018-08-13 at 17:39 -0500, Ben Nemec wrote:
>
> On 08/08/2018 08:18 AM, Doug Hellmann wrote:
> > Excerpts from Doug Hellmann's message of 2018-08-01 09:27:09 -0400:
> > > Moisés Guimarães (moguimar) did quite a bit of work on oslo.config
> > > during the Rocky cycle to add driver support.
On Fri, 2018-08-24 at 07:55 +, Guo, Ruijing wrote:
> Hi, All,
>
> I am verifying numa aware vwitch features
> (https://specs.openstack.org/openstack/nova-specs/specs/rocky/approved/numa-aware-vswitches.html).
> But the result is not my expectation.
>
> What I missing?
>
>
> Nova confi
On Fri, 2018-08-24 at 09:13 -0500, Matt Riedemann wrote:
> On 8/24/2018 8:58 AM, Stephen Finucane wrote:
> > Using this won't add a NUMA topology - it'll just control how any
> > topology present will be mapped to the guest. You need to enable
> > dedicated CPUs
30 31
> > node 1 size: 64502 MB
> > node 1 free: 44945 MB
> > node distances:
> > node 0 1
> > 0: 10 21
> > 1: 21 10
> >
> > Thanks,
> > -Ruijing
> >
> > -Original Message-
> > From: Stephen Finucane [ma
On Sat, 2018-08-25 at 08:08 +0800, Alex Xu wrote:
>
>
> 2018-08-18 20:25 GMT+08:00 Chris Dent :
> > On Fri, 17 Aug 2018, Doug Hellmann wrote:
> >
> > > If we ignore the political concerns in the short term, are there
> > > other projects actually interested in using placement? With what
> > > te
On Sat, 2018-08-25 at 08:08 +0800, Alex Xu wrote:
>
>
> 2018-08-18 20:25 GMT+08:00 Chris Dent :
> > On Fri, 17 Aug 2018, Doug Hellmann wrote:
> >
> > > If we ignore the political concerns in the short term, are there
> > > other projects actually interested in using placement? With what
> > > te
On Mon, 2018-08-27 at 14:23 -0700, melanie witt wrote:
> On Mon, 27 Aug 2018 10:31:50 -0500, Matt Riedemann wrote:
> > On 8/24/2018 7:36 AM, Chris Dent wrote:
> > >
> > > Over the past few days a few of us have been experimenting with
> > > extracting placement to its own repo, as has been discuss
3 4 5 6 7 16 17 18 19 20 21 22 23 node 0 size:
> > > 64412 MB node 0 free: 47658 MB node 1 cpus: 8 9 10 11 12 13 14 15 24
> > > 25 26 27 28 29 30 31 node 1 size: 64502 MB node 1 free: 44945 MB
> > > node distances:
> > > node 0 1
> > > 0: 10
On Fri, 2018-08-31 at 10:03 +1000, Tony Breeds wrote:
> On Thu, Aug 30, 2018 at 09:12:57PM +, Jeremy Stanley wrote:
> > On 2018-08-31 01:13:58 +0800 (+0800), Rico Lin wrote:
> > [...]
> > > What needs to be done for this is full topic categories support
> > > under `options` page so people get
On Fri, 2018-08-31 at 10:45 -0500, Eric Fried wrote:
> The openstack/placement project [1] and its core team [2] have been
> established in gerrit.
>
> I hereby nominate Chris Dent for membership in the placement-core team.
> He has been instrumental in the design, implementation, and stewardship
On Mon, 2018-09-10 at 13:48 -0600, Doug Hellmann wrote:
> Melanie gave me the go-ahead to propose the patches, so here's the list
> of patches for the zuul migration, doc job update, and python 3.6 unit
> tests for the nova repositories.
I've reviewed/+2d all of these on master and think Sylvain w
On Tue, 2018-09-18 at 12:42 +, Bedyk, Witold wrote:
> Stephen,
>
> could you please share your presentation slides?
>
> Thanks
> Witek
Yup. They're available here:
https://docs.google.com/presentation/d/1gaRFmUEJEmy-8lCFsxauQLZNB2ch4hPQ0L4yO11vgL0/edit
Stephen
>
> > -Original Message
FYI, Sphinx 1.8.0 contained a minor issue (introduced by yours truly)
which resulted in an incorrect default doctree directory [1]. This
would manifest itself in a 'docs/source/.doctree' directory being
created and would only affects projects that call 'sphinx-build' from
tox without specifying the
The tests in os-api-ref recently broke:
http://logs.openstack.org/62/606362/1/check/openstack-tox-py35/8b709de/testr_results.html.gz
Specifically, we're seeing errors likes this:
ft1.1:
os_api_ref.tests.test_basic_example.TestBasicExample.test_rest_method_StringException:
Traceback (most
On Thu, 2018-10-04 at 12:03 +, Bob Ball wrote:
> Hi Melanie,
>
> We recommend using novncproxy_base_url with
> vncserver_proxyclient_address set to the dom0's management IP
> address.
>
> We don't currently use nova-console, so deprecation would be the best
> approach.
>
> Thanks,
>
> Bob
On Thu, 2018-10-04 at 07:21 -0400, Doug Hellmann wrote:
> Stephen Finucane writes:
>
> > The tests in os-api-ref recently broke:
> >
> >
> > http://logs.openstack.org/62/606362/1/check/openstack-tox-py35/8b709de/testr_results.html.gz
> >
> > Sp
On Thu, 2018-10-04 at 18:00 -0400, Doug Hellmann wrote:
> Stephen Finucane writes:
>
> > On Thu, 2018-10-04 at 07:21 -0400, Doug Hellmann wrote:
> > > Stephen Finucane writes:
>
> [snip]
>
> > > > Anyway, we can go figure out what's changed
On Wed, 2018-10-10 at 18:51 +, Jeremy Stanley wrote:
> On 2018-10-10 13:35:00 -0500 (-0500), Greg Hill wrote:
> [...]
> > We plan to still have a CI gatekeeper, probably Travis CI, to make sure PRs
> > past muster before being merged, so it's not like we're wanting to
> > circumvent good contri
On Wed, 2018-10-10 at 13:35 -0500, Greg Hill wrote:
> > If it's just about preferring the pull request workflow versus the
> > Gerrit rebase workflow, just say so. Same for just preferring the Github
> > UI versus Gerrit's UI (which I agree is awful).
>
> I mean, yes, I personally prefer the Git
On Mon, 2018-10-15 at 10:07 -0700, melanie witt wrote:
> Hey all,
>
> Milestone s-1 is coming up next week on Thursday Oct 25 [1] and I was
> thinking it would be a good idea to have a spec review day next week on
> Tuesday Oct 23 to spend some focus on spec reviews together.
>
> Spec freeze is
On Fri, 2016-09-23 at 13:33 -0400, Prasanth Anbalagan wrote:
> Adding the project to email subject.
>
> Thanks
> Prasanth Anbalagan
>
> On Fri, 2016-09-23 at 12:56 -0400, Prasanth Anbalagan wrote:
> >
> > Hi,
> >
> > Continuing the topic on the need for integration style tests for
> > Nova
> >
On Wed, 2016-09-21 at 11:16 -0400, Doug Hellmann wrote:
> Excerpts from Matt Riedemann's message of 2016-09-21 09:49:29 -0500:
> >
> > Nova has policy defaults in code now and we can generate the
> > sample
> > using oslopolicy-sample-generator but we'd like to get the default
> > policy sample
On Mon, 2016-11-07 at 11:50 +, Matthew Booth wrote:
> I'd like to follow up on the discussions we had in Barcelona around
> review cadence. I took a lot away from these discussions, and I
> thought they were extremely productive. I think the summary of the
> concerns was:
>
> Nova is a compl
76 matches
Mail list logo