Blair,
Sure.
I’d also be happy for a second volunteer to share it with so that we get a
rounded perspective, it is important that we don’t get too influenced by one
organisation’s use cases.
Tim
From: Blair Bethwaite
Date: Thursday, 19 January 2017 at 20:24
To: Tim Bell
Cc: "m...@mattjarvis
Good day everyone,
As operators we would like to reboot the efforts started around OsOps.
Initial things that may make sense to work towards are starting back
meetings, standardizing the repos (like having a lib or common folder,
READMEs include release(s) tool works with, etc), increasing feedbac
> On Jan 18, 2017, at 5:20 PM, Matt Jarvis wrote:
>
> I think one of the problems we're seeing now is that a lot of operators have
> actually already scratched some of these missing functionality itches like
> quota management and project nesting by handling those scenarios in external
> man
--
Pieter C Kruithof Jr, MS, CPE
PTL, OpenStack UX project
http://www.linkedin.com/in/pkruithofjr
512 576-2844
This email message and any attachments hereto is intended for use only by
the addressee(s) named herein. If you have received this email in error,
please immediately notify the sender
I have some conflicts. Would team members be interested in a make up at the
same time next week?
Sent from my iPhone
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openst
On 19 January 2017 at 13:41, Bruno L wrote:
> Hi,
>
> November last year the Neutron team has announced that VPN as a Service
> will be no longer part of Neutron[1].
>
> We run a public cloud based in New Zealand called Catalyst Cloud[2]. Our
> customers find the VPN service extremely useful to i
Hi All,
We had a great meeting today. Following were the items that we discussed:
* Zainab presented her word frequency analysis of the Launchpad data and
high level review of the source code
* Michael provided some info on the types of data in Stackoverflow
* Nemat reviewed th
I wanted to let the group know that a study that was conducted by OpenStack
UX on behalf of the community. In fact, Tim was one of the participants.
https://docs.google.com/presentation/d/1J6-8MwUGGOwy6-A_w1EaQcZQ1Bq2YWeB-kw4vCFxbwM/edit?usp=sharing
Cheers,
Piet
On Thu, Jan 19, 2017 at 12:24
Hi Tim,
We did wonder in last week's meeting whether quota management and nested
project support (particularly which flows are most important) would be a
good session for the Boston Forum...? Would you be willing to lead such a
discussion?
Cheers,
On 19 January 2017 at 19:59, Tim Bell wrote:
>
Ruan,
Good question! I should clarify that there would be no *default* policy
file to maintain in the project source code, like in keystone currently
[0]. All policy defaults would be coded into the project. Nova has already
taken this approach with their policy file [1], which leaves them with
no
We opened the vote to deprecate/remove the Debian support in Kolla:
http://lists.openstack.org/pipermail/openstack-dev/2017-January/110466.html
Christian.
--
Christian Berendt
Chief Executive Officer (CEO)
Mail: bere...@betacloud-solutions.de
Web: https://www.betacloud-solutions.de
Betacloud
On 18 Jan 2017, at 23:20, Matt Jarvis
mailto:m...@mattjarvis.org.uk>> wrote:
I think one of the problems we're seeing now is that a lot of operators have
actually already scratched some of these missing functionality itches like
quota management and project nesting by handling those scenarios
12 matches
Mail list logo
