Open Stack

Hey,

I'll like to collaborate, please, just let me know what can I do to help
with this task.

Might be a good idea to have in the blueprint a list of tasks?

Also, I think this can be called Deployment/Upgrade guide for TripleO.

Cheers,
Carlos.



On Mon, Mar 20, 2017 at 3:26 PM, Sanjay Upadhyay <supadhya at redhat.com>
wrote:

>
>
> On Mon, Mar 20, 2017 at 5:31 PM, Emilien Macchi <emilien at redhat.com>
> wrote:
>
>> I proposed a blueprint to track the work done:
>>
>> https://blueprints.launchpad.net/tripleo/+spec/tripleo-deploy-guide
>> Target: pike-3
>>
>> Volunteers to work on it with me, please let me know.
>>
>
> Please add me (irc handle - saneax), I am interested on this.
>
> regards
> /sanjay
>
>
>> Thanks,
>>
>> On Tue, Mar 14, 2017 at 7:00 AM, Alexandra Settle <a.settle at outlook.com>
>> wrote:
>> > Hey Emilien,
>> >
>> > You pretty much covered it all! Docs team is happy to provide guidance,
>> but in reality, it should be a fairly straight forward process.
>> >
>> > The Kolla team just completed their deploy-guide patches and were able
>> to help refine the process a bit further. Hopefully this should help the
>> TripleO team :)
>> >
>> > Reach out if you have any questions at all :)
>> >
>> > Thanks,
>> >
>> > Alex
>> >
>> > On 3/13/17, 10:32 PM, "Emilien Macchi" <emilien at redhat.com> wrote:
>> >
>> >     Team,
>> >
>> >     [adding Alexandra, OpenStack Docs PTL]
>> >
>> >     It seems like there is a common interest in pushing deployment
>> guides
>> >     for different OpenStack Deployment projects: OSA, Kolla.
>> >     The landing page is here:
>> >     https://docs.openstack.org/project-deploy-guide/newton/
>> >
>> >     And one example:
>> >     https://docs.openstack.org/project-deploy-guide/openstack-
>> ansible/newton/
>> >
>> >     I think this is pretty awesome and it would bring more visibility
>> for
>> >     TripleO project, and help our community to find TripleO
>> documentation
>> >     from a consistent place.
>> >
>> >     The good news, is that openstack-docs team built a pretty solid
>> >     workflow to make that happen:
>> >     https://docs.openstack.org/contributor-guide/project-deploy
>> -guide.html
>> >     And we don't need to create new repos or do any crazy changes. It
>> >     would probably be some refactoring and sphinx things.
>> >
>> >     Alexandra, please add any words if I missed something obvious.
>> >
>> >     Feedback from the team would be welcome here before we engage any
>> work,
>> >
>> >     Thanks!
>> >     --
>> >     Emilien Macchi
>> >
>> >
>>
>>
>>
>> --
>> Emilien Macchi
>>
>> ____________________________________________________________
>> ______________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscrib
>> e
>> 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://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/20170320/41287908/attachment.html>