Hey Saverio!
That's great news:) We, Kolla community, would love to hear your
feedback and help you with any questions/issues you might have.
Please, join us in #openstack-kolla if you're not yet there.
Cheers,
Michal "inc0" Jastrzebski
On 3 February 2017 at 17:05, Saverio Proto
So far I am just learning. I wrote down some notes based on my
experience of this week.
https://github.com/zioproto/kolla-on-SWITCHengines/
I am looking forward to the Milano Ops Mid-cycle to chat face to face
with more operators interested in Kolla.
The key point is how to grow the Kolla
Hi Jay
It seems like I blinked and 10 more emails flew by since last night. ;-)
One of the difficulties for people like myself, and I think most of the LCOO
participants are like me, is that I have full-time internal commitments with my
employer that significantly limit the amount of time I
+1 from me as well.
I'd like to throw out this suggestion for some discussion.
Many of us on the "working group" side of things have full-time internal
commitments within our various companies. It's VERY difficult to be able to
take the time needed to peruse IRC logs, etherpads, email lists,
I believe this is one of the goal of Product WG, providing a common
platform for users/operators and WG to aggregrate requirements by creating
common "User Story Requirements" which can be implemented cross-project,
cross-releases.
https://wiki.openstack.org/wiki/ProductTeam#Objectives
Putting this out to the whole User and Operator Community. Jay and Edgar have
given us the opportunity to introduce and so we worked up the following.
Community feedback ideas and continued collaboration are welcome.
The LCOO is a group of Multi-cloud Operators who are also development
+1 for the WG summary and sharing priorities.
Equally, exploring how we can make use of common collaboration tools for all WG
would be beneficial.
There is much work to do to get the needs translated to code/doc/tools and it
would be a pity if we are not sharing to the full across WGs due to
On 02/03/2017 01:16 PM, Jonathan Proulx wrote:
On Fri, Feb 03, 2017 at 04:34:20PM +0100, lebre.adr...@free.fr wrote:
:Hi,
:
:I don't know whether there is already a concrete/effective way to identify
overlapping between WGs.
:But if not, one way can be to arrange one general session in each
On Fri, Feb 03, 2017 at 04:34:20PM +0100, lebre.adr...@free.fr wrote:
:Hi,
:
:I don't know whether there is already a concrete/effective way to identify
overlapping between WGs.
:But if not, one way can be to arrange one general session in each summit where
all WG chairs could come and discuss
Hi Andy, thanks very much for your response. I appreciate it. Comments
and questions inline.
On 02/02/2017 09:44 PM, UKASICK, ANDREW wrote:
Hi Jay.
It's already getting late here and I still have to do my farm chores
but I want to acknowledge your request. I think you've developed
quite a
Hi Andreas,
The way you're doing it at the end looks correct - the docs are not quite
right on that one.
The nfs_shares file will only get templated on the cinder_volumes hosts, as
will the nfs_shares_config option - so in essence it shouldn't matter that
the var isn't limited to volume hosts.
Hi,
I don't know whether there is already a concrete/effective way to identify
overlapping between WGs.
But if not, one way can be to arrange one general session in each summit where
all WG chairs could come and discuss about major actions that have been done
for the past cycle and what are
Jay and All,
I want to clarify and be very clear about one point that you raised: “My
questions seem to have been taken as an attack on the LCOO.”
Your questions and valid and good feedback for us as community. Nobody should
feel like “an attack” when somebody else ask those questions. Now, I
Leong, thanks so much for responding. Comments/followup questions inline.
On 02/02/2017 09:07 PM, Sun, Yih Leong wrote:
LCOO was initiated by a group of large telco who contributes/uses OpenStack, such
as AT, NTT, Reliance Jio, Orange, etc [1].
ack.
The co-chair has reached out to Product
Hi!
I need to ask how do you correctly configure nfs to be used with
openstack-ansible newton (14.0.6). I think it is great that there is an
production example file that uses nfs for glance and cinder
(openstack_user_config.yml.prod.example) but the cinder config is not
working for me.
I
15 matches
Mail list logo
