Re: [openstack-dev] [openstack-docs] [tripleo] Creating official Deployment guide for TripleO

2017-04-25 Thread Alexandra Settle 


On 4/25/17, 3:40 AM, "Emilien Macchi"  wrote:

On Fri, Mar 24, 2017 at 11:35 AM, Emilien Macchi  wrote:
> On Wed, Mar 22, 2017 at 2:25 PM, Emilien Macchi  
wrote:
>> Thanks to these who volunteered, it's appreciated.
>>
>> I'm going to kick-off initial work here:
>>
>> 1. Create CI job that build deploy-guide on tripleo-docs repo (when
>> required) - https://review.openstack.org/448740
>
> Step 1 done.
>
>> 2. In tripleo-docs, modify tox.ini and create initial structure for
>> deployment guide (I'll kick it off once we have the CI job)
>
> Step 2, done and ready for review: 
https://review.openstack.org/#/c/449684/
>
>> 3. Start moving deployment related bits from doc/source/ to
>> deploy-guide/source/ (I'll need your help for this step). We also need
>> to include Alexendra and her team to make sure we're moving the right
>> bits.
>
> Keep posted, that will be the next step.

So this step is ready now, since we have the directory in place:
https://github.com/openstack/tripleo-docs/tree/master/deploy-guide/source

I would need some help and feedback on the bits that we're going to move:

* what chapters do we want to move? (related to Deployment)
* how do we handle redirection from old URLs (to keep web search valid
until it's indexed again)

Redirection can be handled in multiple ways. You can look at doing what the 
kolla team did and not move it at all, but rather, use ‘includes’. For example: 
https://github.com/openstack/kolla-ansible/blob/master/deploy-guide/source/quickstart.rst
 

However, I would personally not recommend this action. Simply because if you 
are planning to have a deployment guide, I would recommend you commit to this 
action so there is one source of truth when people are looking for the guide 
itself. The OpenStack-Ansible team ‘created’ a new deployment guide, and moved 
most of their install content across. The team then linked to the Deployment 
Guide on their docs.o.o/dev page. You can see that here: 
https://docs.openstack.org/developer/openstack-ansible/ 

It is entirely up to the TripleO team what they intend to do here. But there 
are options, basically. There will be broken links without, we recommend 
implementing this method: 
https://docs.openstack.org/contributor-guide/project-deploy-guide.html#deployment-guide-and-installation-guide-links
 

>> 4. Expose TripleO deployment guide to deployment guides front page and
>> drink a gin tonic.

I haven't figured yet how to expose the guide to the frontpage but
maybe Alexandra or someone from Docs team can help. It's unclear to me
how to handle that since we have a branchless doc repo, so we would
likely have a versionless documentation link (and handle
version-specific bits inline).

I don’t think the versioning should matter so much here. We will not version 
your guides, and if you do not, there is no problem. To ‘publish’ the guides, 
you need to add your deployment guide to our www/project-deploy-guide/draft 
file. See here: 
https://github.com/openstack/openstack-manuals/blob/master/www/project-deploy-guide/draft/index.html
 Also for Ocata: 
https://github.com/openstack/openstack-manuals/blob/master/www/project-deploy-guide/ocata/index.html
 

Again, any help is welcome. It would be great to achieve this goal in
Pike: having an official TripleO deployment guide among other
deployment tools guides.

Hopefully this helps a bit ( ping me if you have any questions/concerns.

Thanks,

>> I'll give an update when 2. is done so we can start working on the 
content.
>>
>> Thanks,
>>
>> On Wed, Mar 22, 2017 at 8:22 AM, Flavio Percoco  
wrote:
>>> On 20/03/17 08:01 -0400, Emilien Macchi 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.
>>>
>>>
>>> It'd be awesome to have some input from the containers squad on this 
effort
>>> too.
>>> Put me on the list for now while we find another volunteer in the 
containers
>>> DFG.
>>>
>>> Flavio
>>>
 Thanks,

 On Tue, Mar 14, 2017 at 7:00 AM, Alexandra Settle 

 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

Re: [openstack-dev] [openstack-docs] [tripleo] Creating official Deployment guide for TripleO

2017-04-24 Thread Emilien Macchi 
On Fri, Mar 24, 2017 at 11:35 AM, Emilien Macchi  wrote:
> On Wed, Mar 22, 2017 at 2:25 PM, Emilien Macchi  wrote:
>> Thanks to these who volunteered, it's appreciated.
>>
>> I'm going to kick-off initial work here:
>>
>> 1. Create CI job that build deploy-guide on tripleo-docs repo (when
>> required) - https://review.openstack.org/448740
>
> Step 1 done.
>
>> 2. In tripleo-docs, modify tox.ini and create initial structure for
>> deployment guide (I'll kick it off once we have the CI job)
>
> Step 2, done and ready for review: https://review.openstack.org/#/c/449684/
>
>> 3. Start moving deployment related bits from doc/source/ to
>> deploy-guide/source/ (I'll need your help for this step). We also need
>> to include Alexendra and her team to make sure we're moving the right
>> bits.
>
> Keep posted, that will be the next step.

So this step is ready now, since we have the directory in place:
https://github.com/openstack/tripleo-docs/tree/master/deploy-guide/source

I would need some help and feedback on the bits that we're going to move:

* what chapters do we want to move? (related to Deployment)
* how do we handle redirection from old URLs (to keep web search valid
until it's indexed again)

>> 4. Expose TripleO deployment guide to deployment guides front page and
>> drink a gin tonic.

I haven't figured yet how to expose the guide to the frontpage but
maybe Alexandra or someone from Docs team can help. It's unclear to me
how to handle that since we have a branchless doc repo, so we would
likely have a versionless documentation link (and handle
version-specific bits inline).


Again, any help is welcome. It would be great to achieve this goal in
Pike: having an official TripleO deployment guide among other
deployment tools guides.

Thanks,

>> I'll give an update when 2. is done so we can start working on the content.
>>
>> Thanks,
>>
>> On Wed, Mar 22, 2017 at 8:22 AM, Flavio Percoco  wrote:
>>> On 20/03/17 08:01 -0400, Emilien Macchi 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.
>>>
>>>
>>> It'd be awesome to have some input from the containers squad on this effort
>>> too.
>>> Put me on the list for now while we find another volunteer in the containers
>>> DFG.
>>>
>>> Flavio
>>>
 Thanks,

 On Tue, Mar 14, 2017 at 7:00 AM, Alexandra Settle 
 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"  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-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>> --
>>> @flaper87
>>> Flavio Percoco
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>>

Re: [openstack-dev] [openstack-docs] [tripleo] Creating official Deployment guide for TripleO

2017-03-24 Thread Emilien Macchi 
On Wed, Mar 22, 2017 at 2:25 PM, Emilien Macchi  wrote:
> Thanks to these who volunteered, it's appreciated.
>
> I'm going to kick-off initial work here:
>
> 1. Create CI job that build deploy-guide on tripleo-docs repo (when
> required) - https://review.openstack.org/448740

Step 1 done.

> 2. In tripleo-docs, modify tox.ini and create initial structure for
> deployment guide (I'll kick it off once we have the CI job)

Step 2, done and ready for review: https://review.openstack.org/#/c/449684/

> 3. Start moving deployment related bits from doc/source/ to
> deploy-guide/source/ (I'll need your help for this step). We also need
> to include Alexendra and her team to make sure we're moving the right
> bits.

Keep posted, that will be the next step.

> 4. Expose TripleO deployment guide to deployment guides front page and
> drink a gin tonic.
>
> I'll give an update when 2. is done so we can start working on the content.
>
> Thanks,
>
> On Wed, Mar 22, 2017 at 8:22 AM, Flavio Percoco  wrote:
>> On 20/03/17 08:01 -0400, Emilien Macchi 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.
>>
>>
>> It'd be awesome to have some input from the containers squad on this effort
>> too.
>> Put me on the list for now while we find another volunteer in the containers
>> DFG.
>>
>> Flavio
>>
>>> Thanks,
>>>
>>> On Tue, Mar 14, 2017 at 7:00 AM, Alexandra Settle 
>>> 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"  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-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>> --
>> @flaper87
>> Flavio Percoco
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
>
> --
> Emilien Macchi



-- 
Emilien Macchi

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [openstack-docs] [tripleo] Creating official Deployment guide for TripleO

2017-03-22 Thread Emilien Macchi 
Thanks to these who volunteered, it's appreciated.

I'm going to kick-off initial work here:

1. Create CI job that build deploy-guide on tripleo-docs repo (when
required) - https://review.openstack.org/448740
2. In tripleo-docs, modify tox.ini and create initial structure for
deployment guide (I'll kick it off once we have the CI job)
3. Start moving deployment related bits from doc/source/ to
deploy-guide/source/ (I'll need your help for this step). We also need
to include Alexendra and her team to make sure we're moving the right
bits.
4. Expose TripleO deployment guide to deployment guides front page and
drink a gin tonic.

I'll give an update when 2. is done so we can start working on the content.

Thanks,

On Wed, Mar 22, 2017 at 8:22 AM, Flavio Percoco  wrote:
> On 20/03/17 08:01 -0400, Emilien Macchi 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.
>
>
> It'd be awesome to have some input from the containers squad on this effort
> too.
> Put me on the list for now while we find another volunteer in the containers
> DFG.
>
> Flavio
>
>> Thanks,
>>
>> On Tue, Mar 14, 2017 at 7:00 AM, Alexandra Settle 
>> 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"  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-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> --
> @flaper87
> Flavio Percoco
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Emilien Macchi

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [openstack-docs] [tripleo] Creating official Deployment guide for TripleO

2017-03-22 Thread Flavio Percoco 

On 20/03/17 08:01 -0400, Emilien Macchi 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.


It'd be awesome to have some input from the containers squad on this effort too.
Put me on the list for now while we find another volunteer in the containers
DFG.

Flavio


Thanks,

On Tue, Mar 14, 2017 at 7:00 AM, Alexandra Settle  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"  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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


--
@flaper87
Flavio Percoco


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [openstack-docs] [tripleo] Creating official Deployment guide for TripleO

2017-03-21 Thread Alexandra Settle 
Thanks for volunteering everyone :)

Carlos – The Contributor Guide link that Emilien shared has a list of the tasks 
(step-by-step process) that need to be done. The only other thing you might 
need to elaborate on is potential for editing and ensuring your guide is 
up-to-date and fully deployable.

The other thing is, the project deployment guides tend to focus entirely on a 
full deployment (rather than an AIO, or upgrade content). Although I see no 
reason why this scope can’t expand – just letting you know what is currently 
added/being added to the section :)

Cheers,

Alex

From: Carlos Camacho Gonzalez <ccama...@redhat.com>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org>
Date: Monday, March 20, 2017 at 3:21 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [openstack-docs] [tripleo] Creating official 
Deployment guide for TripleO

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 
<supad...@redhat.com<mailto:supad...@redhat.com>> wrote:


On Mon, Mar 20, 2017 at 5:31 PM, Emilien Macchi 
<emil...@redhat.com<mailto:emil...@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.set...@outlook.com<mailto:a.set...@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" 
> <emil...@redhat.com<mailto:emil...@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-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [openstack-docs] [tripleo] Creating official Deployment guide for TripleO

2017-03-20 Thread Carlos Camacho Gonzalez 
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 
wrote:

>
>
> On Mon, Mar 20, 2017 at 5:31 PM, Emilien Macchi 
> 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 
>> 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"  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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [openstack-docs] [tripleo] Creating official Deployment guide for TripleO

2017-03-20 Thread Sanjay Upadhyay 
On Mon, Mar 20, 2017 at 5:31 PM, Emilien Macchi  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 
> 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"  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-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [openstack-docs] [tripleo] Creating official Deployment guide for TripleO

2017-03-20 Thread Emilien Macchi 
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.

Thanks,

On Tue, Mar 14, 2017 at 7:00 AM, Alexandra Settle  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"  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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [openstack-docs] [tripleo] Creating official Deployment guide for TripleO

2017-03-14 Thread Alexandra Settle 
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"  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


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [openstack-docs] [tripleo] Creating official Deployment guide for TripleO

2017-03-13 Thread Emilien Macchi 
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

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev