Hi all,
We are in advance stage of resolving migration with SR-IOV and to improve the
coverage in that part.
We have proposed the following patches to fix SR-IOV migration and its race
conditions:
[1] - Allocate PCI devices on migration: https://review.openstack.org/#/c/328983
[2] - Update bind
I personally like this solution, it seems much more scalable. This follows
the same pattern of the API docs (moving the content to project repos),
which puts the onus back on the project team to maintain and create
documentation. I'm also hoping this results in less duplication between the
guides a
On 09/07/16 07:02, Matt Kassawara wrote:
> Currently, OpenStack provides central documentation (primarily in the
> openstack-manuals repository) for operators and users. The single location
> and consistent structure eases audiences of various technical expertise into
> OpenStack, typically oper
Dell - Internal Use - Confidential
+2
From: Emilien Macchi [mailto:[email protected]]
Sent: Tuesday, June 28, 2016 6:01 PM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [TripleO] TripleO deep dive hour?
Excellent idea, it would also be a good opportunity to take notes and
Hi,
Does anyone have some experience or some document for how to configure
keystone work with https? If so, can you please help share with me or show
some links that can help?
--
Thanks,
Jay Lau (Guangya Liu)
__
OpenStack D
OK, then I will work on it in O
On Thu, Jul 7, 2016 at 12:15 AM, Matt Riedemann
wrote:
> On 7/4/2016 1:12 AM, Zhenyu Zheng wrote:
>
>> I'm willing to work on this, should this be a Blueprint for O?
>>
>>
> The spec will need to be re-proposed for Ocata and any adjustments for the
> sorting/pagin
Hello Everybody!!!
I request everybody to lease review https://review.openstack.org/#/c/326894/
Regards
Vikas
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]
Just a reminder that we're having an API sprint this week, details are
here: https://etherpad.openstack.org/p/keystone-api-sprint
The goals is to get the APIs in the specs repo (most accurate and
up-to-date) [1] to match the APIs defined in the keystone repo (recently
migrated over from the api-si
With Install Guide and API references, we had specific problems to
solve. Which ones do you see exactly with other guides?
Also, before we discuss moving further documentation around, I'd like to
see first how the API references and Install guides work out and what we
need to improve there - befo
Hi Jay, Dmitry and guys
I submit two patches to try recover nodes which stuck in deploying state:
1. fix the issue of the ironic-conductor was brought up with a different
hostname.
https://review.openstack.org/325026
2. clear the lock of nodes in maintenance states
https://review.opens
10 matches
Mail list logo
