penStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
--
Sean Dague
http://dague.net
_
complex (37)
./nova/tests/functional/api_samples_test_base.py:144:5: C901
'ApiSampleTestBase._compare_result' is too complex (36)
I honestly think this is one of the things that you declare a flag day a
couple weeks out, warn everyone they a
, we document it a bit here (though patches are welcome if you have
ideas on making it more clear) -
https://docs.openstack.org/devstack/latest/development.html#testing-a-patch-series
-Sean
--
Sean Dague
http://dague.net
___
Mailing list:
tifact of the way that paste builds pipelines, and
the way our resources need urls. I was trying to see if we generate it
on our side, but I'm not seeing it, so I suspect this is just a
consequence of the resource mapper and
Public bug reported:
One of the really nice things about the Ubuntu doc in Unity is that once
a window sent a WM_URGENT signal, it was highlighted until you visited
it. That made it easy to circle around when folks were trying to get you
on IRC or the like without having to regularly poll.
Since
Public bug reported:
One of the really nice things about the Ubuntu doc in Unity is that once
a window sent a WM_URGENT signal, it was highlighted until you visited
it. That made it easy to circle around when folks were trying to get you
on IRC or the like without having to regularly poll.
Since
> Thanks.
>
>
> [1]: https://review.openstack.org/#/c/441203
> https://review.openstack.org/#/c/455709
>
> 2017-09-08 3:18 GMT+08:00 Sean Dague <mailto:s...@dague.net>>:
>
> This is an email that's probably overdue, but time gets away fro
vstack
>> codebase
>
> +2 on both of these proposals!
Agreed +2.
-Sean
--
Sean Dague
http://dague.net
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ..
own / rebuild when started. I'd be happy to be
wrong about that, but was told in the past that it was just an OVS
limitation.
-Sean
--
Sean Dague
http://dague.net
__
OpenStack Development Mailing List (not f
ow this is effectively a silent 500 (giving a
202 that we know will never actually do what is asked).
-Sean
--
Sean Dague
http://dague.net
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
objectstorage.softlayer.net/v1/AUTH_3d8e6ecb-f597-448c-8ec2-164e9f710dd6/pkvmci/nova/11/457711/35/check/tempest-dsvm-full-xenial/ec523a2/";
rel="nofollow">tempest-dsvm-full-xenial SUCCESS
in 53m 59s
Those css classes are used as selectors by the Toggle CI code to extract
test resu
hat are near the problem, they got confusing quick. I really
think that some more pictoral upgrade safety cards or something
explaining the things you need to consider, and what parts projects
handle for you would be really useful. And then revisit whatever the
tagging structure is going to be later.
ive things.
There is a stop gap work around that's running tests right now -
https://review.openstack.org/#/c/509394/1/devstack-vm-gate-wrap.sh
If it passes I'll approve it to get folks back to work. A longer term
solution is probably n
vendor data is presented over both, if both are
> enabled; config drive is presumably more secure.
>
> thanks,
> Pino
>
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-r
keys, that would be ++. Rebuild
doesn't wait on that, but Barbican urls for keys seems like a much
better world to be in.
-Sean
--
Sean Dague
http://dague.net
__
OpenStack Development Mailing List (not for usage questions)
U
tively be treated like 3rd party CI during
the transition. Sounds good.
The 80 / 20 split seems very reasonable, and a good way to let teams get
back to work while letting the v3 effort make forward progress with real
load to smoke out the issues.
Thanks for flipping over to this model.
patience! This is a giant rollout with a
> bunch of changes in it, so we really do appreciate everyone's
> understanding as we work through it all.
>
> Monty
>
> __
> OpenStack Development Mailing List (not for usa
The project was shut down for that reason so that no one would
mistakenly assume there was any maintenance or support on it. If you or
others want to revive the project, that would be fine, as long as we can
identify 2 individuals who will step up as maintainers.
-Sea
this fall, and thanks for letting me
represent you the past 4 years.
-Sean
--
Sean Dague
http://dague.net
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-re
fold. Digging out of the multi year hole of "close but not
exactly the same" API differences between nova-net and neutron really
makes me want to make sure we never intentionally inflict that confusion
on folks again.
-Sean
--
Sean Dague
http://dague.net
__
out if the folks that mostly had it would also need it
on reboot.
-Sean
--
Sean Dague
http://dague.net
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.or
my back of the envelope math and
spot checking on resources used, these really aren't a big concern.
But it's harder to see that until we really start accounting for CI time
by project / person, and what kinds of things really do consume th
cess.
If people are deeply concerned about CI resources, step one is to get
some better accounting into the existing system to see where resources
are currently spent, and how we could ensure that time is fairly spread
around to ensure maximum productivity by all developers.
-Sean
-
re to explain the
differences between them. Based on the confusion that kept seeming to
come during discussions at the PTG, I think we need to circle around and
figure out if there are different ways to explain this to have greater
clarity.
-Sean
This appears like it might be an issue with the ppa in pike
** Also affects: qemu
Importance: Undecided
Status: New
** Project changed: qemu => ubuntu
** Package changed: ubuntu => qemu (Ubuntu)
--
You received this bug notification because you are a member of qemu-
devel-ml, which i
This appears like it might be an issue with the ppa in pike
** Also affects: qemu
Importance: Undecided
Status: New
** Project changed: qemu => ubuntu
** Package changed: ubuntu => qemu (Ubuntu)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team
This appears like it might be an issue with the ppa in pike
** Also affects: qemu
Importance: Undecided
Status: New
** Project changed: qemu => ubuntu
** Package changed: ubuntu => qemu (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
On 09/19/2017 09:00 AM, Sean Dague wrote:
> I've been iterating through gerrit dashboards this morning trying to
> figure out why they no longer show any changes.
>
> It looks like the query: label:Code-Review>=-2,self now matches changes
> you haven't voted on. P
a -2,-1,+1,+2 vote on them.
I'll be poking around today to figure out what the options are to get
equivalent functionality is out of the system, then update the gerrit
dashboards in gerrit-dash-creator based on that.
-Sean
--
Sean Dagu
-s-proxy.txt.gz
>
> People new to OpenStack don't really know that 'q' means neutron.
>
>
>
> On Thu, Sep 7, 2017 at 5:45 AM, Sean Dague <mailto:s...@dague.net>> wrote:
>
> On 08/31/2017 06:27 AM, Sean Dague wrote:
> > The work that starte
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1715615
Title:
it throws 'Unexpected API Error ' when i try to create fi
This is working as designed. It's not possible for Nova to map anything
until it's registered. Additional documentation for Ironic might be
appropriate here.
** Tags added: ironic
** Changed in: nova
Status: New => Won't Fix
--
You received this bug notification because you are a member
p and getting this rolling.
Eric
Approved for merge, should be in shortly.
Eric, thanks again for stepping up and pulling this all together. Very
much appreciated.
-Sean
--
Sean Dague
http://dagu
re welcome as well, as this is the first attempt to do this.
Minutes from MHVLUG Leadership Meeting - 3Q 2017
Attendees
=====
* Sean Dague (president)
* Matt Johnson (program direct
stemd.html
Thanks,
Eric Fried (efried)
Thank you Eric. Would love to get a recommended pdb path into the docs.
Ping me as soon as it's up for review, and I'll get it merged quickly.
Thanks for stepping up here, it's highly appreciated.
willing to step up there. If so please feel free to reach out,
and we can carve out some PTG time in helping a new push organize here.
However, without new leadership here, the current plan is to just put
the effort to rest.
-Sean
--
Sean Dague
http:/
On 08/31/2017 06:27 AM, Sean Dague wrote:
> The work that started last cycle to make devstack only have a single
> execution mode, that was the same between automated QA and local, is
> nearing it's completion.
>
> https://review.openstack.org/#/c/499186/ is the patch that
ested qemu, this hasn't
been used for a very long time.
I think this classifies as the kind of thing we can straight remove, and
it will simplify a few things if we do.
-Sean
--
Sean Dague
http://dague.net
_
** Changed in: nova
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1714416
Title:
Incorrect response returned for invalid Accept header
Status in Cinder:
This should be tracked by a blueprint, not a bug, on the nova side.
** Changed in: nova
Status: New => Opinion
** Tags added: ironic
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.la
This is pretty much working as designed. Nova is the owner of that
state, and will drive services to that state.
** Changed in: nova
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute
Kernel panics in guests are unlikely to be Nova bugs. This is probably
an underlying kvm / libvirt issue.
** Changed in: nova
Status: New => Incomplete
** Also affects: openstack-gate
Importance: Undecided
Status: New
** No longer affects: nova
--
You received this bug notific
For questions like this, please engage in IRC or the mailing list
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1713466
This is really only a devstack fix
** Changed in: nova
Status: New => Confirmed
** No longer affects: nova
** No longer affects: neutron
** No longer affects: cinder
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutro
ously making jobs pretend to be grenade to keep
screen running), now is the time to run tests against this patch and see
where things stand.
-Sean
--
Sean Dague
http://dague.net
__
OpenStack Development Mailing List (no
he prefered devstack
way for doing SSL is with the tls-proxy, which is how we run in the gate
now. All endpoints get set as https, and are sent through an apache
proxy that terminates them.
This maps much closer to production models of doing haproxy, or some
other terminator.
-Sean
ect from
> a core maintainer of the project.
>
> So to the existing core team members, please respond with a yay/nay and
> after about a week or so we should have a decision (knowing a few cores
> are on vacation right now).
>
+1
--
Sean Dague
http://dague.net
___
or glance docs or cinder docs, etc.
The following change will bring back local search behavior like that -
https://review.openstack.org/#/c/493107/
It will need to be landed and release, and probably backported to
stable/pike give
On 08/11/2017 10:49 AM, Anne Gentle wrote:
> On Fri, Aug 11, 2017 at 8:10 AM, Sean Dague wrote:
>> On 08/11/2017 08:50 AM, Anne Gentle | Just Write Click wrote:
>>> Yeah, I need to circle back in the theme work to make sure both search
>>> scopes are available. My p
_search = True" which would get rid of swift_search
and just use baked in local search. Then on a per site basic people
could turn it on / off, and openstackdocstheme could still be used for
sites that want global search.
-Sean
--
Sean Dague
http://dague.net
nce docs or cinder docs, etc.
Equally problematic, in the rbd search above it returns content from all
published branches, and seems to be coming back in reverse order. So
mitaka content is the first link for folks for searching from latest docs.
-Sean
--
Sean Dague
http://dague.net
of this imported documentation is going to need
some heavy pruning / editing next cycle to get into shape).
For now it's just a copy and paste of the old opts.
-Sean
--
Sean Dague
http://dague.net
__
OpenStack D
On 08/09/2017 09:24 AM, Sean Dague wrote:
> On 08/09/2017 09:19 AM, Doug Hellmann wrote:
>> Excerpts from Sean Dague's message of 2017-08-08 17:01:29 -0400:
>>> When trying to import
>>> https://github.com/openstack/openstack-manuals/blob/6f9fc171800e8a43501
the 'show-options' directive. It uses
> the same inputs as the sample file generator. See
> https://docs.openstack.org/oslo.config/latest/reference/sphinxext.html for
> details
So in this case we could:
.. show-options::
oslo.vmware
And that would have the same impact?
-Sean
-
cinder ref once it shows up?
If anyone has thoughts on the best resolutions here, that would be great.
-Sean
--
Sean Dague
http://dague.net
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
r content goes in /admin. See
> http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html#proposed-change
> for details.
Ok, I guess a lot of things got binned incorrectly during the
transition. I think the definition of user was less c
On 08/07/2017 05:04 PM, Clark Boylan wrote:
> On Wed, Aug 2, 2017, at 01:44 PM, Clark Boylan wrote:
>> On Wed, Aug 2, 2017, at 11:37 AM, Sean Dague wrote:
>>> On 08/02/2017 12:28 PM, Clark Boylan wrote:
>>>> On Wed, Aug 2, 2017, at 07:55 AM, Matt Riedemann wrote:
>
be a couple of sections and
landing documents where appropriate.
Please chime in if you have opinions. Otherwise I'm going to start
writing the rest of this tomorrow to try to get it all sorted for RC.
-Sean
--
Sean Dague
http:/
to flow again. The immediate spam flood seems over,
but just an FYI on what happened.
-Sean
--
Sean Dague
http://dague.net
___
Mid-Hudson Valley Linux Users Group http://mhvlug.org
https://mhvlug.org/cgi-bin/mailman/listinfo
Exposing system metadata in the compute API is something we really don't
want to do.
** Changed in: nova
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launch
So, this really seems like going out of the way to break the system. A
better error message would be fine if it was submitted, but this is very
unlikely to hit in the real world.
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Undecided => Wishlist
** Tags ad
o think that "Copy and Modify" is a better paradigm. Or "New Flavor
based on X" which will prefill based on an existing one.
The Delete flavor button should come with a giant warning of "This will
make a lot of information in your environment confusing, you sho
o this
is useful to them so that they can create new instances like the ones there.
The only way to change the flavor of an instance is to resize it.
-Sean
--
Sean Dague
http://dague.net
__
OpenStack Development Mailing L
e and users:
* CLI users (nova cli or openstack client)
* Horizon users
* API users (possibly using python APIs, possibly others)
When a person shows up at our site from where ever, we should assume
they are a CLI user. It&#
; would be a simple enough
>> rule that we wouldn't have to think too hard about where to put
>> individual example files, which would speed up the migration.
>
> If I find a doc that tells me how to set up a VM with a Neutron
> network and ports and subnets and floating IP
we could get a weekly report of 404 urls posted somewhere public,
that would be extremely useful, because the easy ones based on git
renames are done, and everything else is going to require human
inspection to figure out what the right landing target is.
-Sean
--
Sean Dague
http://dague.
, than if I am not
> *running* nova but am trying to use a nova deployed by someone else
> and I start from the python-novaclient or python-openstackclient
> docs because I installed one of those in order to talk to nova.
>
&
An issue with the xenserver CI was identified. Once we get this patch
in, and backported to ocata, it should also address a frequent grenade
multinode fail scenario which is plaguing the gate.
-Sean
On 08/02/2017 07:17 AM, Sean Dague wrote:
The 3 node scenarios in Neutron (which are
this impacts your CI / jobs, please speak up. The CI runs on both the
main and experimental queue on devstack for this change look pretty
good, so I think we're safe to move forward this time. But we also
thought that the last time
cells v1 is deprecated, we're not going to document it fully
** Changed in: nova
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1674486
Ti
This references the old api-ref, marking won't fix. If this is an issue
in the new one please update the bug.
** Changed in: nova
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (n
*** This bug is a duplicate of bug 1683972 ***
https://bugs.launchpad.net/bugs/1683972
** This bug has been marked a duplicate of bug 1683972
Overlapping iSCSI volume detach/attach can leave behind broken SCSI devices
and multipath maps.
--
You received this bug notification because you
This references the wadl, it can be closed
** Changed in: nova
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1616134
Title:
api
This is apparently fixed in os-vif for Newton and beyond. Marking
Invalid on the Nova side because the logic doesn't live in Nova in any
supported version.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
There definitely could be enhancements to the recovery mode when things
start up again, but this is more than a simple bug, and probably needs a
spec to work through all the edge conditions here.
The Nova spec process is here - https://specs.openstack.org/openstack
/nova-specs/
** Changed in: nov
*** This bug is a duplicate of bug 1562681 ***
https://bugs.launchpad.net/bugs/1562681
** Tags added: evacuate
** This bug has been marked a duplicate of bug 1562681
Post instance evacuation, image metadata is not retained when using shared
storage
--
You received this bug notification
It does feel like it might be better to fix this on the client side.
Marking as opinion as the patch author abandoned the nova patch. It is
welcome to come back later.
** Changed in: nova
Status: New => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engin
** Changed in: nova
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1454418
Title:
Evacuate fails when using cells - AttributeError:
This would be a spec enhancement I think, please look at the specs
process here - https://specs.openstack.org/openstack/nova-
specs/readme.html
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Undecided => Wishlist
--
You received this bug notification becaus
Managing the AppArmor config is currently beyond scope for Nova, thus
marking this as Opinion. It would be good if those rules from the
distros were able to do this better.
If you wanted to put that in scope for Nova, that would require a Nova
spec - https://specs.openstack.org/openstack/nova-spec
Evacuate behavior changes are so dicey at this point that I think
anything like this probably needs a spec to actually think through the
edge conditions.
Please dive in here if you are interested -
https://specs.openstack.org/openstack/nova-specs/readme.html
** Tags added: evacuate
** Changed in
** Tags added: note-to-self
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchp
I expect this was an issue with a stale installation of dependencies. If
this is still an issue, please reopen
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (no
I think this is the kind of enhancement that would come through the
specs process - https://specs.openstack.org/openstack/nova-
specs/readme.html
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Undecided => Wishlist
--
You received this bug notification beca
I think on the Nova side this is pretty much working as designed. If
there is different / better ironic behavior, perhaps it could be brought
up with the Ironic team?
** Changed in: nova
Status: New => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engine
If there is a request for a Nova feature here, please bring it in via
the Nova Specs process - https://specs.openstack.org/openstack/nova-
specs/readme.html
** Changed in: nova
Status: New => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team
This is really a note to self. Moving to Opinion as there are a lot of
mights here. :)
** Tags added: note-to-self
** Changed in: nova
Status: New => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Comput
The device_name was removed from the API. I think the only place it ever
worked was xenserver.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bug
What real world scenario would you expect to expose a situation where
the neutron environment is turned off and nova-compute is restarted?
This seems pretty synthetic, and the fact that it recovers ones the
neutron agent restarts seems like most of the environment is working as
expected.
** Change
Working as design, device_name is since removed from the API.
** Tags added: shelve
** Changed in: nova
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launch
** Changed in: nova
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1677892
Title:
nova scheduler_default_filter ComputeCapabilities filte
I think this is one of those edge cases that the work around you
provided is the right way through. The decorating on images is meant to
be part of the original image build process, and doesn't magically fix
things.
** Changed in: nova
Status: New => Won't Fix
--
You received this bug not
If nova cli allows you to do that, it means the REST API allows you to
do that. Permissions should not be done on the client side as they can
be circumvented with curl.
This looks like it's a permissions issue on the server side where you'd
like a different policy?
** Changed in: nova
Stat
Ok, given the docs are fixed, lets put this into Opinion (which is a
closed state) for the actual code changes which don't have concensus.
** Changed in: nova
Status: New => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscri
Fixed in docs.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1679703
Title:
Unable to boot instance with VF( direct-port ) because the
Self over allocating VCPUs is not a good idea. If your machine only has
4 CPUs and you expose that as 5 CPUs to a guest, you'll get
pathologically bad performance as the guest tries to optimize workloads
across those, which are causing cache flushes in the CPUs below.
Definitely in the Won't Fix c
er (or fix it themselves).
Choosing to do a driver out of tree is not recommended and comes with
all of these risks.
-Sean
--
Sean Dague
http://dague.net
__
OpenStack Development Mailing List (not for usage questions
** Changed in: nova
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1682811
Title:
nova boot apis raises 500 error if scheduler_hints
ad
This really should come in as a spec, it's a feature add.
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Undecided => Wishlist
** Tags added: needs-spec
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is sub
ly getting in
bounds to paths on the site that haven't been there for 8 years.
It would be really good if we had a way (manual or automated) to have
301 redirects, that are fixable by the teams that now own the
documentation (the project teams).
-Sean
--
Sean Dague
h
1 - 100 of 5121 matches
Mail list logo
