[Openstack-operators] Tokyo Ops Design Summit Tracks - Agenda on Sched

Tom Fifield tom at openstack.org
Fri Oct 16 03:38:40 UTC 2015


On 15/10/15 07:12, Christopher Aedo wrote:
> On Mon, Oct 12, 2015 at 10:01 PM, Tom Fifield <tom at openstack.org> wrote:
>> Let's do it :)
>
> Excellent!  Do I need to do anything?  Or will something be magically
> added to the schedule?  Just let me know if I need to take any action
> here, thanks!

Automagic :)

Check out 2PM on Wednesday:

https://mitakadesignsummit.sched.org/overview/type/ops


> -Christopher
>
>> On 13/10/15 07:57, Fox, Kevin M wrote:
>>>
>>> +1 *
>>> *
>>> ------------------------------------------------------------------------
>>> *From:* Christopher Aedo
>>> *Sent:* Monday, October 12, 2015 3:51:23 PM
>>> *To:* openstack-operators at lists.openstack.org
>>> *Subject:* Re: [Openstack-operators] Tokyo Ops Design Summit Tracks -
>>>
>>> Agenda on Sched
>>>
>>> On Sun, Oct 11, 2015 at 8:55 PM, Tom Fifield <tom at openstack.org> wrote:
>>>>
>>>> Hi all,
>>>>
>>>> We are still lacking:
>>>>
>>>> * Moderator(s) for Quotas and Billing
>>>> * Content for about 3 slots.
>>>>
>>>> If you have interest for any of this, please speak now - time is running
>>>> out!
>>>
>>>
>>> I'm very interested in having an operator focused discussion about
>>> delivering apps to your users, and whether or not that matters to the
>>> cloud operators out there.  Apps on OpenStack is something near and
>>> dear to my heart (working on apps.openstack.org), is it important to
>>> the operators of clouds though?
>>>
>>> I know a few of the bigger public cloud providers have worked on their
>>> own approaches to this (using Heat templates, Murano apps, or some
>>> other PaaS layers).  I think there's a big benefit to a common catalog
>>> of apps that everyone can use, but maybe the big operators want to
>>> exert more control by keeping an independent catalog?  Or maybe there
>>> are other reasons?
>>>
>>> Please speak up if you're interested in this topic, I'd be very happy
>>> to moderate, and I think if we can get some operators talking together
>>> about this there would be a lot of value in the conversation!
>>>
>>> -Christopher
>>>
>>> _______________________________________________
>>> OpenStack-operators mailing list
>>> OpenStack-operators at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>
>>>
>>> _______________________________________________
>>> OpenStack-operators mailing list
>>> OpenStack-operators at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>
>>
>>
>> _______________________________________________
>> OpenStack-operators mailing list
>> OpenStack-operators at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators




More information about the OpenStack-operators mailing list