Open Stack

As someone who submitted a talk to that track (which is indeed about
deploying a learning management in an automated fashion with Heat, but
obviously also discusses the architecture and design that underpins
said deployment), I primarily did so because I figured it was the best
fit of the options available, in the absence of a training/learning
track.

Cheers,
Florian


On Sat, Feb 6, 2016 at 5:53 PM, Nick Chase <nchase at mirantis.com> wrote:
> Also, I think people were concentrating on making their talks relevant
> specifically to OpenStack.
>
> When we create the track we can create a good continuum, I think, from
> designing to building to testing to deploying an app.
>
> ---- Nick
>
> On Feb 6, 2016 11:47 AM, "Stefano Maffulli" <stefano.maffulli at dreamhost.com>
> wrote:
>>
>> On 02/06/2016 01:36 PM, Denys Makogon wrote:
>>
>> And here's what i see - current track consists of mostly from talks about
>> how to deploy apps within OpenStack.
>>
>>
>> I tend to agree with you that deployment is only one option and that
>> architecture, design, microservices, frameworks, etc are an important part
>> of development, too.
>>
>> Before jumping to conclusions that require complicating the agenda even
>> more, I'd try to look at the root cause for this issue. Are we reaching out
>> to the wrong audience? do we have a confusing message? are there very few
>> developers using OpenStack?
>>
>> /stef
>>
>> _______________________________________________
>> Openstack-track-chairs mailing list
>> Openstack-track-chairs at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs
>>
>
> _______________________________________________
> Openstack-track-chairs mailing list
> Openstack-track-chairs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs
>