On 7/20/18 2:13 AM, Ben Nemec wrote:
On 07/19/2018 03:37 PM, Emilien Macchi wrote:
Today I played a little bit with Standalone deployment [1] to deploy a
single OpenStack cloud without the need of an undercloud and overcloud.
The use-case I am testing is the following:
"As an operator, I want
On Fri, Jul 20, 2018 at 01:05:26PM +1000, Tony Breeds wrote:
>
> Hello folks,
> So really the subject says it all. I fell like at the time we
> created the Stable branch project team that was the only option. Since
> then we have crated the SIG structure and in my opinion that's a better
> f
team and Opening the Extended Maintenance SIG
Reply-To:
Hello folks,
So really the subject says it all. I fell like at the time we
created the Stable branch project team that was the only option. Since
then we have crated the SIG structure and in my opinion that's a better
fit. We've also
Hi Miguel,
I'd like to ask Feature Freeze Exeption regarding FWaaS v2 logging.
Following patches are under reviewing now. So, could you please add these
patches into FFE?
01. openstack/neutron-fwaas https://review.openstack.org/#/c/530694
02. openstack/neutron-fwaas https://review.openst
On 07/19/2018 03:37 PM, Emilien Macchi wrote:
Today I played a little bit with Standalone deployment [1] to deploy a
single OpenStack cloud without the need of an undercloud and overcloud.
The use-case I am testing is the following:
"As an operator, I want to deploy a single node OpenStack, th
Today I played a little bit with Standalone deployment [1] to deploy a
single OpenStack cloud without the need of an undercloud and overcloud.
The use-case I am testing is the following:
"As an operator, I want to deploy a single node OpenStack, that I can
extend with remote compute nodes on the ed
I've proposed [1] to add extra logging on the Nova side. Let's see if
that helps us catch the root cause of this.
[1] https://review.openstack.org/584032
On Thu, Jul 19, 2018 at 12:50 PM, Artom Lifshitz wrote:
> Because we're waiting for the volume to become available before we
> continue with t
On 07/19/2018 11:55 AM, Paul Belanger wrote:
On Thu, Jul 19, 2018 at 05:30:27PM +0200, Cédric Jeanneret wrote:
Hello,
While trying to get a new validation¹ in the undercloud preflight
checks, I hit an (not so) unexpected issue with the CI:
it doesn't provide flavors with the minimal requireme
On Thu, Jul 19, 2018 at 05:30:27PM +0200, Cédric Jeanneret wrote:
> Hello,
>
> While trying to get a new validation¹ in the undercloud preflight
> checks, I hit an (not so) unexpected issue with the CI:
> it doesn't provide flavors with the minimal requirements, at least
> regarding the disk space
I saw your storyboard for this. Thank you for creating a story.
Since the controllers manage the certificates for the amphora (both
generation and rotation) the overhead to an operator should be
extremely low and limited to initial installation configuration.
Since we have automated the certifica
Because we're waiting for the volume to become available before we
continue with the test [1], its tag still being present means Nova's
not cleaning up the device tags on volume detach. This is most likely
a bug. I'll look into it.
[1]
https://github.com/openstack/tempest/blob/master/tempest/api/
Greetings OpenStack community,
Today's meeting was again very brief as this time elmiko and dtantsur were out.
There were no major items of discussion, but we made plans to check on the
status of the GraphQL prototyping (Hi! How's it going?).
In addition to the light discussion there was also
The primary issue I think is that the Nova folks think there is too much in
Nova already.
So there are probably more features that can be done to make it more in line
with vCenter, and more features to make it more functionally like AWS. And at
this point, neither are probably easy to get in.
Hi all,
A spin-off discussion in https://review.openstack.org/#/c/579177/ resulted
in an idea to update our RST conventions for headings level 2 and 3 so that
our guidelines follow recommendations from
http://docutils.sourceforge.net/docs/user/rst/quickstart.html#sections.
The updated conventions
On 18-07-19 10:42:11, Sean McGinnis wrote:
>
> Development Focus
> -
>
> Teams should be focused on implementing planned work. Work should be wrapping
> up on client libraries to meet the client lib deadline Thursday, the 26th.
>
> General Information
> ---
>
> T
Development Focus
-
Teams should be focused on implementing planned work. Work should be wrapping
up on client libraries to meet the client lib deadline Thursday, the 26th.
General Information
---
The final client library release is on Thursday the 26th. Releases
Hello,
While trying to get a new validation¹ in the undercloud preflight
checks, I hit an (not so) unexpected issue with the CI:
it doesn't provide flavors with the minimal requirements, at least
regarding the disk space.
A quick-fix is to disable the validations in the CI - Wes has already
pushe
Hi all -
Follow up on the Edge paper specifically:
https://translate.openstack.org/iteration/view/edge-computing/pot-translation/documents?dswid=-3192
This is now available. As I mentioned on IRC this morning, it should be
VERY close to the PDF. Probably just needs a quick review.
Let me k
Hi everyone,
Due to we have two core members who cannot join the weekly meeting, we
think it would be better to skip this meeting and resume on next week.
If you have any questions, please reply to this thread.
Best regards,
Lujin
On Thu, Jul 19, 2018 at 6:02 AM Raoul Scarazzini wrote:
[...]
> Small question aside related to all-in-one: we're talking about use
> cases in which we might want to go from 1 to 3 controllers, but how this
> can become a thing? I always thought to all-in-one as a developer/ci
> "tool", so why we
Zane Bitter wrote:
[...]
And I'm not convinced that's an either/or choice...
I said specifically that it's an either/or/and choice.
I was speaking more about the "we need to pick between two approaches,
let's document them" that the technical vision exercise started as.
Basically I mean I'm
Hi,
Since some time we see that test
tempest.api.compute.servers.test_device_tagging.TaggedAttachmentsTest.test_tagged_attachment
is failing sometimes.
Bug about that is reported for Tempest currently [1] but after small patch [2]
was merged I was today able to check what cause this issue.
Tes
On 18/07/2018 22:36, Michele Baldessari wrote:
[...]
> Besides E), I think a reasonable use case is to be able to have a small
> all-in-one installation that mimicks a more "real-world" overcloud.
> I think there is a bit of value in that, as long as the code to make it
> happen is not horribly hug
On 07/18/2018 06:42 AM, Ian Wienand wrote:
> While I'm reserved about the
> idea of full platform functional tests, essentially having a
> wide-variety of up-to-date tox environments using some of the methods
> discussed there is, I think, a very practical way to be cow-catching
> some of the bigge
Hi,
Thanks. I just send patch [1] to add this new job to Neutron failure rate
Grafana dashboard.
[1] https://review.openstack.org/#/c/583870/
> Wiadomość napisana przez Ghanshyam Mann w dniu
> 19.07.2018, o godz. 06:55:
>
>> On Sun, May 13, 2018 at 1:20 PM, Ghanshyam Mann
>> wrote:
>>> On
25 matches
Mail list logo