----- Original Message -----
> From: "Robert Collins" <robe...@robertcollins.net>
> To: "OpenStack Development Mailing List" <openstack-dev@lists.openstack.org>
> Sent: Thursday, October 3, 2013 4:22:26 PM
> Subject: [openstack-dev] [TripleO] Continual deployment scripts
>
> This is a proposal: I think we should not use toci in the
> continually-deployed infrastructure: toci is aimed at testing, CD is
> production ready - key differences in intent: In CD doing a fresh
> start every time isn't really desirable :) and in toci we'll want to
> do massively parallel testing when/where possible, whereas CD wants
> staged deployments, graceful operations etc...
>
> So if there is anything that is in toci that will be useful for the CD
> overcloud / undercloud I think we should move it to
> tripleo-image-elements/elements/cd-tools or tripleo-incubator/cd-tools
> {I'm torn on which :)}, and then reuse that from toci.
>
> Thoughts?
Sounds reasonable to me. TripleO CI (TOCI) is certainly focused on testing
however many of us have found it to be really useful in setting up our daily
development environments as well. I don't always want/need to tear my entire
dev environment down however... I'd like to (sometimes) have the option just to
deploy a fresh overcloud. Tools/scripts to do just that sound wonderful.
I do see there as being some overlap here so reuse definitely makes since. My
vote would be to put things in tripleo-incubator/cd-tools for now and we can
see how it shakes out. We can always move them later.
Dan
>
> -Rob
>
> --
> Robert Collins <rbtcoll...@hp.com>
> Distinguished Technologist
> HP Converged Cloud
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
