Open Stack

Hi Rico,

Great to meet you at the summit.


The version related templates I think would work as follows.

In each named directory we would have the same set of templates
e.g.
Single instance
Clustered instance
resource group
etc..

And so if you are on Pike you would go to the pike directory and you 
will find all th3e examples we have created for pike.

I am not sure that I properly understand how we want to take this 
forward as the current structure of the repository is confusing.

DO we just want to update all the examples there with the latest "Pike" 
way of creating these resources or do we want to have some backwards 
compatibility?
We will need to agree on that at first I think.

I will definitely join the meeting.

Regards

Lance


On 15.05.17 12:13, Rico Lin wrote:
> Hi Lance and all others who shows interest
>
> IMO, after some feedback from the summit. I think it will be greate to 
> have efforts on
>
>   * **bug/blueprint*: We needs more people doing fix/review/spec.
>     Since we still on the way to make heat more handy as Orchestration
>     tools*
>   * *template example*: Since we do have some new functions but didn't
>     actually give a proper update of it.
>   * *tutorial*: We got some reports about the lack of tutorials for
>     for for features like software config/ rolling upgrade, so I
>     definitely think we require some improvement here.
>   * *test*: Our integration test(tempest test) seems not cover
>     every scenario (like we just cover some snapshots test these few
>     weeks). Also, we do hope to get more reports on how people use
>     heat, and what's the test result.
>
> So yes from me, Lance, that will help:)
>
> Also, most of our functions can be directly called by future version, 
> so if we separate it into versions, how can Pike user find that 
> example? I like to idea to make all user aware of template version. 
> but not sure to make version specific directory will help. Maybe a 
> version info in template description will do? We can discussion this 
> at the meeting (Wednesdays at 1500 UTC in #openstack-meeting-5) :)
>
> 2017-05-15 15:21 GMT+08:00 Lance Haig <lnhaig at gmail.com 
> <mailto:lnhaig at gmail.com>>:
>
>     Good to know that there is interest.
>
>     I was thinking that we should perhaps create a directory for each
>     openstack version.
>
>     so we start say with a mitaka directory and then move the files
>     there and test them all so that they work with Liberty.
>     Then we can copy it over to Mitaka and do the same but add the
>     extra functionality.
>     and then Newton etc...
>
>     That way if someone is on a specific version they only have to go
>     to a specific directory to get the examples they need.
>
>     What do you think?
>
>     Lance
>
>
>     On 14 May 2017 at 23:14, Kaz Shinohara <ksnhr.tech at gmail.com
>     <mailto:ksnhr.tech at gmail.com>> wrote:
>
>         Hi Lance,
>
>         I like it too.
>         We should keep them updated according to the latest spec and
>         actual use cases.
>
>         Regards,
>         Kaz Shinohara
>
>
>         2017-05-13 13:00 GMT+09:00 Foss Geek <thefossgeek at gmail.com
>         <mailto:thefossgeek at gmail.com>>:
>
>             Hi Lance, I am also interested to assisting you on this.
>
>             Thanks
>             Mohan
>
>             On 11-May-2017 2:25 am, "Lance Haig" <lnhaig at gmail.com
>             <mailto:lnhaig at gmail.com>> wrote:
>
>                 Hi,
>
>                 I would like to introduce myself to the heat team.
>
>                 My name is Lance Haig I currently work for Mirantis
>                 doing workload onboarding to openstack.
>
>                 Part of my job is assisting customers with using the
>                 new Openstack cloud they have been given.
>
>                 I recently gave a talk with a colleague Florin
>                 Stingaciu on LCM with heat at the Boston Summit.
>
>                 I am interested in assisting the project.
>
>                 We have noticed that there are some outdated examples
>                 in the heat-examples repository and I am not sure that
>                 they all still function.
>
>                 I was wondering if it would be valuable for me to take
>                 a look at these and fix them or perhaps we can rethink
>                 how we present the examples.
>
>                 I am interested in what you guys think.
>
>                 Thanks
>
>                 Lance
>
>                 __________________________________________________________________________
>                 OpenStack Development Mailing List (not for usage
>                 questions)
>                 Unsubscribe:
>                 OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>                 <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
>                 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>                 <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
>
>
>             __________________________________________________________________________
>             OpenStack Development Mailing List (not for usage questions)
>             Unsubscribe:
>             OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>             <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
>             http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>             <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
>
>
>
>         __________________________________________________________________________
>         OpenStack Development Mailing List (not for usage questions)
>         Unsubscribe:
>         OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>         <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
>         http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>         <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
>
>
>
>     __________________________________________________________________________
>     OpenStack Development Mailing List (not for usage questions)
>     Unsubscribe:
>     OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>     <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>     <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
>
>
>
>
> -- 
> May The Force of OpenStack Be With You,
> */Rico Lin
> /*irc: ricolin
>
>
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170515/5cd5fd80/attachment.html>