Open Stack

Hello Florian.

I'm not saying that submission about application deployment strategies are not fitting CAD track. 
Just saying that for next summits it is worth to consider splitting current CAD track into Cloud application deployment (less formal name: From Code to Clouds) and Cloud application development.
For example, how generic clouds impacts the way how solution architects are designing applications.

And i completely agree with Stefano. Current list of tracks and their definitions are becoming more and more complex (good example here: Networking and TELCO/NFV). So, it would be a good step forward (after this summit of course) is to start wider discussion about how developers are consuming OpenStack in their applications in order to understand if it is really necessary bring yet another level of complexity into how we define what we, as community, want to learn within OpenStack summit.

And yet one thing more, it seems to be that problem appears in understanding of what actually Cloud Application is.
>From developers perspective, cloud application is nothing else rather than regular application, but adjusted (micro-service architecture) according to deployment environment capabilities (distributed platform, etc.). Basically, word "cloud" means the where application would run. But we're missing key thing, how can we consume OpenStack services for building software that facing to a regular users (i've seen one talk like what i've described, it was about Zaqar and micro-service interactions in applications - this is what we should look and ask for).

Kind regards,
Denys Makogon

________________________________________
From: Florian Haas <florian at hastexo.com>
Sent: Saturday, February 6, 2016 8:09 PM
To: Nick Chase
Cc: openstack-track-chairs at lists.openstack.org
Subject: Re: [Openstack-track-chairs] Cloud Application Development Track future improvements

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
>

_______________________________________________
Openstack-track-chairs mailing list
Openstack-track-chairs at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs