Hi everyone,
Due to most of us being at the OpenStack Summit, we're cancelling the
meeting tomorrow.
Thanks everyone and see you in Berlin.
Regards,
Mohammed
--
Mohammed Naser — vexxhost
-
D. 514-316-8872
D. 800-910-1726 ext. 200
E.
FYI: Thanks to Jesse, he has picked up this work and it's up here:
https://review.openstack.org/#/c/609329/6
On Wed, Oct 10, 2018 at 9:56 AM Jesse Pretorius
wrote:
>
> On 10/10/18, 5:54 AM, "Mohammed Naser" wrote:
>
> >So I’ve been thinking of dropping the Xenial jobs to reduce our overall
On 10/10/18, 5:54 AM, "Mohammed Naser" wrote:
>So I’ve been thinking of dropping the Xenial jobs to reduce our overall
> impact in terms of gate usage in master because we don’t support it.
I think we can start dropping it given our intended supported platform for
Stein is Bionic, not
On Wed, 2018-10-10 at 06:50 +0200, Mohammed Naser wrote:
> Hi everyone!
>
> So I’ve been thinking of dropping the Xenial jobs to reduce our
> overall impact in terms of gate usage in master because we don’t
> support it.
>
> However, I was a bit torn on this because i realize that it’s
>
Hi everyone!
So I’ve been thinking of dropping the Xenial jobs to reduce our overall impact
in terms of gate usage in master because we don’t support it.
However, I was a bit torn on this because i realize that it’s possible for us
to write things and backport them only to find out that
Hi everyone:
Our gates have unfortunately been blocked because of OpenSUSE failures
and Bionic timeouts, I have submitted a patch to set both to non
voting
Bionic: It seems to take a really long time for APT installs, I'm
investigating and thanks to fungi I hope to have an instance to get it
up
On 11.9.2018 18:53, Alex Schultz wrote:
Thanks everyone for coming and chatting. From the meeting we've had a
few items where we can collaborate together.
Here are some specific bullet points:
- TripleO folks should feel free to propose some minor structural
changes if they make the
Thanks everyone for coming and chatting. From the meeting we've had a
few items where we can collaborate together.
Here are some specific bullet points:
- TripleO folks should feel free to propose some minor structural
changes if they make the integration easier. TripleO is currently
I just realized I booked the room and put it in the etherpad but
forgot to email out the time.
Time: Tuesday 09:00-10:45
Room: Big Thompson
https://etherpad.openstack.org/p/ansible-collaboration-denver-ptg
Thanks,
-Alex
On Tue, Sep 4, 2018 at 1:03 PM, Alex Schultz wrote:
> On Thu, Aug 9, 2018
Hi team:
I've come up with a schedule which includes the general events
happening at the PTG which would be interesting for the OSA team and
contributors.
https://calendar.google.com/calendar?cid=dmV4eGhvc3QuY29tXzgwNmJyb2hpZnNoaGdmY2kzcWdqdDk3aTJzQGdyb3VwLmNhbGVuZGFyLmdvb2dsZS5jb20
Please let
Hi team:
We won't be conducting a meeting this week because of the PTG,
however, we'll be making an effort to try and allow/bring remote
access to those not at the PTG over this week.
Thanks everyone.
Regards,
Mohammed
__
Hi Andy:
I made a metal note of replying to this but I never got a chance to :(
It was great working with you, you're always welcome back anytime! :)
Thanks,
Mohammed
On Mon, Sep 3, 2018 at 3:32 AM Hugh Saunders wrote:
>
> Thanks for all your hard work on OSA Andy :)
>
> On Thu, 30 Aug 2018
On Thu, Aug 9, 2018 at 2:43 PM, Mohammed Naser wrote:
> Hi Alex,
>
> I am very much in favour of what you're bringing up. We do have
> multiple projects that leverage Ansible in different ways and we all
> end up doing the same thing at the end. The duplication of work is
> not really
Thanks for all your hard work on OSA Andy :)
On Thu, 30 Aug 2018 at 18:41 Andy McCrae wrote:
> Now that Rocky is all but ready it seems like a good time! Since changing
> roles I've not been able to keep up enough focus on reviews and other
> obligations - so I think it's time to step aside as
> From: Andy McCrae
> Now that Rocky is all but ready it seems like a good time! Since changing
> roles I've not been able to keep up enough focus on reviews and other
> obligations - so I think it's time to step aside as a core reviewer.
> I want to say thanks to everybody in the community,
Hey Andy,
I can only underline what Ian says. It was a pleasure to work with you,
many thanks for your kind support all the time. Keep your ears stiff,
what we say in Germany. And good luck :)
kind regards
Frank
Am 2018-08-30 20:05, schrieb Ian Y. Choi:
Hello Andy,
Thanks a lot for your
On 30/08/18 18:40, Andy McCrae wrote:
> Now that Rocky is all but ready it seems like a good time! Since
> changing roles I've not been able to keep up enough focus on reviews and
> other obligations - so I think it's time to step aside as a core reviewer.
>
> I want to say thanks to everybody in
Andy,
We’ll miss you! Thanks so much for all your hard work and leadership.
Don’t be a stranger!
Amy (spotz)
Sent from my iPhone
> On Aug 30, 2018, at 11:05 AM, Ian Y. Choi wrote:
>
> Hello Andy,
>
> Thanks a lot for your work on OpenStack-Ansible team.
>
> It was very happy to
Thanks for all you do and have done for the OpenStack Community, Andy :)
Andy McCrae wrote:
Now that Rocky is all but ready it seems like a good time! Since
changing roles I've not been able to keep up enough focus on reviews
and other obligations - so I think it's time to step aside as a core
Hello Andy,
Thanks a lot for your work on OpenStack-Ansible team.
It was very happy to collaborate with you as different teams (me: I18n
team) during Ocata and Pike release cycles,
and I think I18n team now has better insight on OpenStack-Ansible thanks
to the help from you and so many kind
Now that Rocky is all but ready it seems like a good time! Since changing
roles I've not been able to keep up enough focus on reviews and other
obligations - so I think it's time to step aside as a core reviewer.
I want to say thanks to everybody in the community, I'm really proud to see
the work
Dear community,
We are approaching the PTG in Denver, and I want to remind everybody to make
sure you are ready for it!
I've created the etherpad [1] where you can add any topic you want to discuss,
if you haven't done so already.
If you are not able to attend the PTG, please mention it on
Hi,
On Fri, Aug 10, 2018 at 5:00 AM, Wesley Hayutin wrote:
>
>
> On Thu, Aug 9, 2018 at 5:33 PM Alex Schultz wrote:
>
>> On Thu, Aug 9, 2018 at 2:56 PM, Doug Hellmann
>> wrote:
>> > Excerpts from Alex Schultz's message of 2018-08-09 14:31:34 -0600:
>> >> Ahoy folks,
>> >>
>> >> I think it's
> On 8/10/18, 3:20 AM, "Paul Belanger" wrote:
>
>This is basically what I do with roles i write, allow the user to decide
> to step
>over specific tasks. For example, I have created nodepool_task_manager
> variable
>with the following:
>
>
>
A couple of changes [1][2] that I proposed to kolla ansible recently as a
PoC could be related here. Kolla ansible is full of almost identical roles
for each service, with a lot of duplicated 'code' (YAML). The idea was to
try to factor some of that out into shared roles. This results in less code
Hello,
On Fri, Aug 10, 2018 at 7:47 AM Paul Belanger wrote:
>
> On Thu, Aug 09, 2018 at 08:00:13PM -0600, Wesley Hayutin wrote:
> > On Thu, Aug 9, 2018 at 5:33 PM Alex Schultz wrote:
> >
> > > On Thu, Aug 9, 2018 at 2:56 PM, Doug Hellmann
> > > wrote:
> > > > Excerpts from Alex Schultz's
On Thu, Aug 09, 2018 at 08:00:13PM -0600, Wesley Hayutin wrote:
> On Thu, Aug 9, 2018 at 5:33 PM Alex Schultz wrote:
>
> > On Thu, Aug 9, 2018 at 2:56 PM, Doug Hellmann
> > wrote:
> > > Excerpts from Alex Schultz's message of 2018-08-09 14:31:34 -0600:
> > >> Ahoy folks,
> > >>
> > >> I think
On Thu, Aug 9, 2018 at 5:33 PM Alex Schultz wrote:
> On Thu, Aug 9, 2018 at 2:56 PM, Doug Hellmann
> wrote:
> > Excerpts from Alex Schultz's message of 2018-08-09 14:31:34 -0600:
> >> Ahoy folks,
> >>
> >> I think it's time we come up with some basic rules/patterns on where
> >> code lands when
On Thu, Aug 9, 2018 at 2:56 PM, Doug Hellmann wrote:
> Excerpts from Alex Schultz's message of 2018-08-09 14:31:34 -0600:
>> Ahoy folks,
>>
>> I think it's time we come up with some basic rules/patterns on where
>> code lands when it comes to OpenStack related Ansible roles and as we
>>
Excerpts from Alex Schultz's message of 2018-08-09 14:31:34 -0600:
> Ahoy folks,
>
> I think it's time we come up with some basic rules/patterns on where
> code lands when it comes to OpenStack related Ansible roles and as we
> convert/export things. There was a recent proposal to create an
>
Hi Alex,
I am very much in favour of what you're bringing up. We do have
multiple projects that leverage Ansible in different ways and we all
end up doing the same thing at the end. The duplication of work is
not really beneficial for us as it takes away from our use-cases.
I believe that
Ahoy folks,
I think it's time we come up with some basic rules/patterns on where
code lands when it comes to OpenStack related Ansible roles and as we
convert/export things. There was a recent proposal to create an
ansible-role-tempest[0] that would take what we use in
+1
From: Markos Chandras
Sent: Monday, August 6, 2018 4:35:55 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [openstack-ansible] Proposing Jonathan Rosser as
core reviewer
On 07/30/2018 11:16 AM, jean-phili...@evrard.me wrote:
> He
On 07/30/2018 11:16 AM, jean-phili...@evrard.me wrote:
> Hello everyone,
>
> I'd like to propose Jonathan Rosser (jrosser) as core reviewer for
> OpenStack-Ansible.
> The BBC team [1] has been very active recently across the board, but worked
> heavily in our ops repo, making sure the
Maybe such change should be considered to be done globally on all OpenStack
channels?
> Wiadomość napisana przez jean-phili...@evrard.me w dniu 01.08.2018, o godz.
> 10:13:
>
> Hello everyone,
>
> Due to a continuously increasing spam [0] on our IRC channels, I have decided
> to make our
Hello everyone,
Due to a continuously increasing spam [0] on our IRC channels, I have decided
to make our channel (#openstack-ansible on freenode) only joinable by
Freenode's nickserv registered users.
I am sorry for the inconvenience, as it will now be harder to reach us (but
it's not that
+1 nice guy to be a core!
On Mon, Jul 30, 2018, 13:08 Mohammed Naser wrote:
> On Mon, Jul 30, 2018 at 11:59 AM, Jesse Pretorius
> wrote:
> >>On 7/30/18, 9:19 AM, "jean-phili...@evrard.me"
> wrote:
> >>
> >>I'd like to propose Jonathan Rosser (jrosser) as core reviewer for
>
On Mon, Jul 30, 2018 at 11:59 AM, Jesse Pretorius
wrote:
>>On 7/30/18, 9:19 AM, "jean-phili...@evrard.me"
>>wrote:
>>
>>I'd like to propose Jonathan Rosser (jrosser) as core reviewer for
>> OpenStack-Ansible.
>>The BBC team [1] has been very active recently across the board, but
>>
>On 7/30/18, 9:19 AM, "jean-phili...@evrard.me" wrote:
>
>I'd like to propose Jonathan Rosser (jrosser) as core reviewer for
> OpenStack-Ansible.
>The BBC team [1] has been very active recently across the board, but
> worked heavily in our ops repo, making sure the experience is
+2 from me!
Amy (spotz)
On Mon, Jul 30, 2018 at 3:16 AM, jean-phili...@evrard.me <
jean-phili...@evrard.me> wrote:
> Hello everyone,
>
> I'd like to propose Jonathan Rosser (jrosser) as core reviewer for
> OpenStack-Ansible.
> The BBC team [1] has been very active recently across the board, but
Hello everyone,
I'd like to propose Jonathan Rosser (jrosser) as core reviewer for
OpenStack-Ansible.
The BBC team [1] has been very active recently across the board, but worked
heavily in our ops repo, making sure the experience is complete for operators.
I value Jonathan's opinion (I
Hello,
According to the readability test here [1], contributors prefer reading a task
like the following:
- name: Fail if service was deployed using a different installation method
fail:
msg: "Switching installation methods for OpenStack services is not
supported"
when:
-
Hello everyone,
If you were not at the previous OpenStack-Ansible meeting*, I'd like to inform
you I will not be running for PTL of OSA.
It's been a pleasure being the PTL of OSA for the last 2 cycles.
We have improved in many ways: testing, stability, speed, features,
documentation, user
This title seems very scary. It was to be read as "... for source installs" : )
To be honest, I feel very sad about the lack of involvement in CentOS
in OSA over the years.
We didn't get many contributors over time for it.
This has always been a labour of love, and the honeymoon seems over for
Hi Paul:
On Thu, Jun 28, 2018 at 5:03 PM, Paul Belanger wrote:
> On Thu, Jun 28, 2018 at 12:56:22PM -0400, Mohammed Naser wrote:
>> Hi everyone:
>>
>> This email is to ask if there is anyone out there opposed to removing
>> SELinux bits from OpenStack ansible, it's blocking some of the gates
>>
On Thu, Jun 28, 2018 at 12:56:22PM -0400, Mohammed Naser wrote:
> Hi everyone:
>
> This email is to ask if there is anyone out there opposed to removing
> SELinux bits from OpenStack ansible, it's blocking some of the gates
> and the maintainers for them are no longer working on the project
>
Also, this is the change that drops it, so feel free to vote with your
opinion there too:
https://review.openstack.org/578887 Drop SELinux support from os_swift
On Thu, Jun 28, 2018 at 12:56 PM, Mohammed Naser wrote:
> Hi everyone:
>
> This email is to ask if there is anyone out there opposed
Hi everyone:
This email is to ask if there is anyone out there opposed to removing
SELinux bits from OpenStack ansible, it's blocking some of the gates
and the maintainers for them are no longer working on the project
unfortunately.
I'd like to propose removing any SELinux stuff from OSA based
Hello,
TL:DR; If you have spare cycles, join one of our interest groups!
In the Queens cycle, I have formalised the "liaisons" work, making
them an integral part of the Thursday's meeting agenda. Sadly, that
initiative didn't work, as almost no liaison worked/reported on those
meetings, and I
Hello,
*TL:DR;* If you are an openstack-ansible user, consuming our roles directly,
with tags, without using openstack-ansible plays or integrated repo,
then things will change for you. Start using git shas instead of tags.
All other openstack-ansible users should not see a difference, even if
On 03/05/18 09:13, Andy McCrae wrote:
>
>
> I will gladly pick up my well-used meeting chair hat.
> It's a great idea, I think it would help make our meetings more productive.
> Once you've been chair you have a different view of how the meetings work.
>
> Andy
I too think this is a great idea
I think Jesse sumarized things elegantly.
Here is an analogy for you, to complement the answer with more
background. Let me compare our state with a new company,
as this is a a notion people many people can relate to.
Initially we were a startup. Only a few people were working on OSA on
its
Mailing List (not for usage questions)"
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [openstack-ansible] Implement rotations for
meetings handling
* So my question is... what is the health status of OSA? Is there still a
core of committed contributors? I only c
Hi OSA peeps.
I apologise in advance for what may seem like an impertinent question. And
for those playing along at home, I was just getting the hang of
contributing to OSA when last year my employer decided that some of us were
no longer needed, and OpenStack lost quite a few full time employed
>
>
> Now that we are all part-time, I'd like to toy with a new idea,
> proposed in the past by Jesse, to rotate the duties with people who
> are involved in OSA, or want to get involved more (it's not restricted
> to core developers!).
>
> One of the first duties to be handled this way could be
Also +1.__
OpenStack 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
Excerpts from Jean-Philippe Evrard's message of 2018-05-02 17:14:07 +0200:
> Hello everyone,
>
> Now that we are all part-time, I'd like to toy with a new idea,
> proposed in the past by Jesse, to rotate the duties with people who
> are involved in OSA, or want to get involved more (it's not
+1 good idea
On Wed, May 2, 2018 at 9:09 AM, Amy Marrich wrote:
> +1, leading meetings is a great way to get folks involved in the Community
> and gives them some 'ownership' within the project.
>
> Amy (spotz)
>
> On Wed, May 2, 2018 at 10:14 AM, Jean-Philippe Evrard <
>
+1, leading meetings is a great way to get folks involved in the Community
and gives them some 'ownership' within the project.
Amy (spotz)
On Wed, May 2, 2018 at 10:14 AM, Jean-Philippe Evrard <
jean-phili...@evrard.me> wrote:
> Hello everyone,
>
> Now that we are all part-time, I'd like to toy
I am definitely +1 on this, I think it's a great idea.
Thanks,
Dave Wilde (d34dh0r53)
On Wed, May 2, 2018 at 10:27 AM Mohammed Naser wrote:
> On Wed, May 2, 2018 at 11:14 AM, Jean-Philippe Evrard
> wrote:
> > Hello everyone,
> >
> > Now that we
On Wed, May 2, 2018 at 11:14 AM, Jean-Philippe Evrard
wrote:
> Hello everyone,
>
> Now that we are all part-time, I'd like to toy with a new idea,
> proposed in the past by Jesse, to rotate the duties with people who
> are involved in OSA, or want to get involved more
Hello everyone,
Now that we are all part-time, I'd like to toy with a new idea,
proposed in the past by Jesse, to rotate the duties with people who
are involved in OSA, or want to get involved more (it's not restricted
to core developers!).
One of the first duties to be handled this way could be
+2!
On Thu, Apr 26, 2018 at 10:20 AM, Carter, Kevin wrote:
> +2 from me!
>
>
> --
>
> Kevin Carter
> IRC: Cloudnull
>
> On Wed, Apr 25, 2018 at 4:06 AM, Markos Chandras wrote:
>>
>> On 24/04/18 16:05, Jean-Philippe Evrard wrote:
>> > Hi everyone,
>> >
>>
+2 from me!
--
Kevin Carter
IRC: Cloudnull
On Wed, Apr 25, 2018 at 4:06 AM, Markos Chandras wrote:
> On 24/04/18 16:05, Jean-Philippe Evrard wrote:
> > Hi everyone,
> >
> > I’d like to propose Mohammed Naser [1] as a core reviewer for
> OpenStack-Ansible.
> >
>
> +2
>
> --
On 24/04/18 16:05, Jean-Philippe Evrard wrote:
> Hi everyone,
>
> I’d like to propose Mohammed Naser [1] as a core reviewer for
> OpenStack-Ansible.
>
+2
--
markos
SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
On 4/24/18, 4:08 PM, "Jean-Philippe Evrard" wrote:
>I’d like to propose Mohammed Naser [1] as a core reviewer for
> OpenStack-Ansible.
A happy +2 from me. (
Rackspace Limited is a company registered in England & Wales (company
+2 from me.
Marc Gariépy
On 2018-04-24 11:05 AM, Jean-Philippe Evrard wrote:
Hi everyone,
I’d like to propose Mohammed Naser [1] as a core reviewer for OpenStack-Ansible.
He has been working actively on fixing the telemetry stack, and is now
willing to step up to improve the CentOS platform
+2 from me!
Amy (spotz)
On Tue, Apr 24, 2018 at 10:05 AM, Jean-Philippe Evrard <
jean-phili...@evrard.me> wrote:
> Hi everyone,
>
> I’d like to propose Mohammed Naser [1] as a core reviewer for
> OpenStack-Ansible.
>
> He has been working actively on fixing the telemetry stack, and is now
>
Hi everyone,
I’d like to propose Mohammed Naser [1] as a core reviewer for OpenStack-Ansible.
He has been working actively on fixing the telemetry stack, and is now
willing to step up to improve the CentOS platform which is now in a
very degraded state.
I feel that it’s important that he’s able
Maybe worth posting on operators, but it looks like the scheduling of
the action fails, which let me think that nova is not running fine
somewhere.
Why is the restart in a random order? That can cause issues, and
that's the whole reason why we are orchestrating the deploys/upgrade
with ansible.
Hi,
I'm trying to migrate controller and compute VMs installed with
Openstack-Ansible across systems with following approach.
This is mainly to minimize the deployment time in the Jenkins CI environment.
Export steps:
1. Power off the VMs gracefully.
2. virsh dumpxml ${node} >
Dear community,
Starting at the end of this month, I won't be able to work full time
on OpenStack-Ansible anymore.
I want to highlight the following:
Our current way of working is not sustainable in the long run, as a lot
of work (and therefore pressure) is concentrated on a few individuals.
I
Hello,
Ahah, gate job breakages? You were the first to break them, but also
willing to step in to fix them as soon as you knew.
And that's the part I will remember the most.
You will be missed, Major. Your next team is lucky to have you!
It was a pleasure working with you. And the gifs, omagad!
Ah Major, we shall definitely miss your readiness to help, positive attitude
and deep care for setenforce 1. Oh, and then there're the gifs... so many
gifs...
While I am inclined to [1], I shall instead wish you well while you [2]. (
[1] https://media.giphy.com/media/1BXa2alBjrCXC/giphy.gif
All the best Major, thanks for all your work on OSA :)
On Mon, 26 Mar 2018 at 14:05 Major Hayden wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hey there,
>
> As promised, I am stepping down from being an OpenStack-Ansible core
> reviewer since I am unable to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey there,
As promised, I am stepping down from being an OpenStack-Ansible core reviewer
since I am unable to meet the obligations of the role with my new job. :(
Thanks to everyone who has mentored me along the way and put up with my gate
job
Dear OpenStack-Ansiblers,
We've got an etherpad here [1], to track all the things we want to
discuss at the forum.
if you're an OpenStack-Ansible user, don't hesitate to add your
session ideas, list what you liked or disliked in the last release,
and share your experience!
Thank you in advance.
Right, that's a little absurd, 1TB? :-) , I completely agree.
They could live with anything, but I'd try to estimate minimums across
distributions
for example, an RDO test deployment with containers looks like:
(undercloud) [stack@undercloud ~]$ ssh heat-admin@192.168.24.8 "sudo df -h
; sudo
Hello,
That's what it always was, but it was hidden in the pages. Now that I
refactored the pages to be more visible, you spotted it :)
Congratulations!
More seriously, I'd like to remove that requirement, showing people
can do whatever they like. It all depends on how/where they store
images,
Compute host disk requirements for Openstack Ansible seem high in the
documentation.
I think I have used smaller compute hosts in the past.
Did something change in Queens?
https://docs.openstack.org/project-deploy-guide/openstack-ansible/latest/overview-requirements.html
Compute hosts
Disk
Hello,
We discussed the problem of the miscommunication at the PTG, and we
agreed the focus of the week solved many things for clarity.
I am not sure we need to send a ML summary, if all is recorded in the
meeting each week: people can just browse meetings for this info.
I have no strong opinion
JP,
When the Community meeting was moved to once a month there was a lot of
resulting miscommunication as a result. If a weekly review is going to be
sent to the mailing list with channel discussions is going to be sent out,
I think that's a good alternative but the conversations still need to
Hello,
During the PTG, we've discussed about changing our meetings.
I'd like to have a written evidence in our mailing lists, showing what
we discussed, and what we proposed to change. I propose we validate
those changes if they get no opposition in the next 7 days (deadline:
13 March).
What we
Dear community,
We are everyday closer to the end of the cycle, and the following
roles seem not ready for integration into the next release, because
they are failing their own gates's functional testing for more than
two weeks:
- os_ceilometer
- os_aodh
- os_trove
- os_magnum
Following the
Hello everyone,
I would like to announce my candidacy for PTL of the
OpenStack-Ansible project for the Rocky cycle.
I will focus on a single theme this cycle, simplification.
After all the features introduced in Queens cycle, it's time
to simplify our work:
* Reduce the amount of variables in
I added my comment/opinion on the bug.
Thanks for reporting this, Major!
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
estions)
> > <openstack-dev@lists.openstack.org>
> > Subject: [openstack-dev] [openstack-ansible] Limiting pip wheel builds
> > for OpenStack clients
> >
> > Hey there,
> >
> > I was spelunking into the slow wheel build problems we've been seeing
> > in Cent
> -Original Message-
> From: Major Hayden [mailto:ma...@mhtx.net]
> Sent: Wednesday, January 24, 2018 8:03 PM
> To: OpenStack Development Mailing List (not for usage questions)
> <openstack-dev@lists.openstack.org>
> Subject: [openstack-dev] [openstack-ansible] L
Hey there,
I was spelunking into the slow wheel build problems we've been seeing in CentOS
and I found that our wheel build process was spending 4-6 minutes building
cassandra-driver. The wheel build process usually takes 8-12 minutes, so half
the time is being spent there.
More digging
Hello,
On 04/01/18 10:29, Periyasamy Palanisamy wrote:
> Hi OSA Experts,
>
>
>
> I’m trying to bring up openstack using openstack-ansible in AIO flavor
> by having neutron ml2 plugin set to ovs.
>
> OSA is being executed from OPNFV XCI deployer with attached
> openstack_user_config and
Hi OSA Experts,
I'm trying to bring up openstack using openstack-ansible in AIO flavor by
having neutron ml2 plugin set to ovs.
OSA is being executed from OPNFV XCI deployer with attached
openstack_user_config and user_variables*.yml files.
I can see installation [1] is being successful, but
Hi,
We are trying test environment deployment with OpenStack-ansible pike
release. After executing setup-hosts.yaml, the lxc-containers were created.
We have an issue while doing
*apt-get update *in infra-repo-container as it couldn't connect to the
proxy server.
The strange thing is that the
Hi,
We are trying test environment deployment with openstack-ansible pike
release. After executing setup-hosts.yaml, the lxc-containers were created.
We have an issue while doing apt-get update in infra-repo-container as it
couldn't connect to the proxy server.
The strange this is that the
Hello everyone,
A small delegation of our openstack-ansible team will be in Sydney,
and we are looking forward to meeting all of you!
We'll have an ops feedback session during the forum happening on
Monday 6th, 1:30 pm - 2:10 pm.
If you're willing to get started with openstack-ansible,
Hello everyone,
With our role maturity guidelines now in place [1], we can now start
the maturity downgrade procedure [2] for the following roles:
- monasca [3]
- monasca-agent [4]
- octavia [5]
- searchlight [6]
On top of that, the os_freezer role need more love [7], while still in
incubated
Hello everyone,
I'd be very happy if someone can take over the bug triage czar duty,
and report it in our community meeting end of each month.
It doesn't take too much time in itself (preparing a list of bugs
before the meeting, having an opinion on them, and attend the bug
triage meeting). IMO,
Hello everyone,
From this week on, openstack-ansible will meet in the
#openstack-ansible channel, every Tuesday, 16:00 UTC. No meeting will
happen on Thursdays anymore. The community meeting would happen the
last Tuesday of the month, the bug triages are kept the rest of the
time.
Keep also in
Hello everyone,
Some people on this planet are more aware of others of this fact:
we have too many meetings in our life.
I don't think OpenStack-Ansible should be so greedy to take 8 hours of
your life a month for meetings. I therefore propose the reduction to 4
meetings/month: 3 bug triages and
I use openstack-ansible for all of my OpenStack testing and deployment
needs currently so if there was an AIO that I could use as a reference that
would be awesome. I personally found that having scenarios available in the
AIO helps drive upgrades and adoptions of new features. As an example I
Well, there are ppl already running OpenVSwitch on openstack-ansible,
so I guess it's just a question of a few bug fixes and adding a
scenario to make sure this is working forever :p
On Fri, Sep 29, 2017 at 8:22 AM, Gyorgy Szombathelyi
wrote:
>
>>
>> Hello
1 - 100 of 513 matches
Mail list logo