Hi,
Patch [1] is merged now so You can rebase Your patches for master branch and
pep8 should be fine now.
[1] https://review.openstack.org/#/c/592884/
> Wiadomość napisana przez Slawomir Kaplonski w dniu
> 17.08.2018, o godz. 10:16:
>
> Hi,
>
> It looks that pep8 job in Neutron is currently
Hi All,
I tried to install openstack kolla by following kolla documentation:
https://docs.openstack.org/kolla-ansible/latest/user/quickstart.html
When doing this command: "kolla-ansible -i ./multinode bootstrap-servers",
I observed following error:
Error message is "fatal: [control01]: FAILED! =>
Hi, the interface name must be the same for all nodes including localhost
(deployment host). If the iface names are not the same along all the hosts
will have to:
- Comment network_interface (or the interface var which name differs)
- Set the variable with an appropriate value at inventory file on
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
technical caveats? Perhaps with modifications of some sort to support
the needs of those projects?
I think ignoring the po
On Fri, 17 Aug 2018, Tom Barron wrote:
Has there been a discussion on record of how use of placement by cinder would
affect "standalone" cinder (or manila) initiatives where there is a desire to
be able to run cinder by itself (with no-auth) or just with keystone (where
OpenStack style multi-t
https://review.openstack.org/#/c/593289/ should fix the similar
problem you found with CommentedSeq.
Doug
Excerpts from super user's message of 2018-08-18 11:15:20 +0900:
> The problem was fixed.
>
> Nguyen Hai
>
> On Fri, Aug 17, 2018 at 11:47 PM Doug Hellmann
> wrote:
>
> > I was not able
Excerpts from Chris Dent's message of 2018-08-18 13:25:25 +0100:
>
> 2. There are other projects actively using placement, not merely
> interested. If you search codesearch.o.o for terms like "resource
> provider" you can find them. But to rattle off those that I'm aware
> of (which I'm certain is
Mark, shall I start the retirement of astara now? I would appreciate a
"go ahead" - unless you want to do it yourself...
Andreas
On 2018-02-23 14:34, Andreas Jaeger wrote:
On 2018-01-11 22:55, Mark McClain wrote:
Sean, Andreas-
Sorry I missed Andres’ message earlier in December about retirin
Hi Eduardo,
Thanks for your suggestion which is very helpful. Indeed, network_interface
is not same in localhost and other nodes. Furthermore, the reason it failed
is "network_interface" must have configured IPv4 address and up. This is
not mentioned *explicitly *in the quick start documentation.
> So my hope is that (in no particular order) Jay Pipes, Eric Fried,
> Takashi Natsume, Tetsuro Nakamura, Matt Riedemann, Andrey Volkov,
> Alex Xu, Balazs Gibizer, Ed Leafe, and any other contributor to
> placement whom I'm forgetting [1] would express their preference on
> what they'd like to see
On 8/13/2018 11:22 PM, Sean McGinnis wrote:
Support Pre Upgrade Checks (upgrade-checkers)
-
One of the hot topics we've been discussing for some time at Forum and PTG
events has been making upgrades better. To that end, we want to add tooling for
each s
On 8/13/2018 9:30 PM, Rambo wrote:
1.Only in one region situation,what will happen in the cloud as
expansion of cluster size?Then how solve it?If have the limit physical
node number under the one region situation?How many nodes would be the
best in one regione?
This question seems a b
+ops list
On 8/18/2018 10:20 PM, Matt Riedemann wrote:
On 8/13/2018 9:30 PM, Rambo wrote:
1.Only in one region situation,what will happen in the cloud
as expansion of cluster size?Then how solve it?If have the limit
physical node number under the one region situation?How many nodes
wo
On 8/13/2018 4:42 PM, melanie witt wrote:
From what I find in the PTG notes [1] and the spec, it looks like this
didn't go forward for lack of general interest. We have a lot of work to
review every cycle and we generally focus on functionality that impact
operators the most and look for +1s o
14 matches
Mail list logo
