<div dir="ltr">Cool trick. :) I think I got it all but please do double-check:<br><a href="https://review.openstack.org/121426">https://review.openstack.org/121426</a><br><br>The upstream this will pull from is <a href="https://github.com/annegentle/ha-guide">https://github.com/annegentle/ha-guide</a><br><br>Thanks,<br><br>Anne<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Sep 14, 2014 at 3:19 PM, Andreas Jaeger <span dir="ltr"><<a href="mailto:aj@suse.com" target="_blank">aj@suse.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 09/14/2014 09:25 PM, Andreas Jaeger wrote:<br>
> On 09/14/2014 08:16 PM, Anne Gentle wrote:<br>
>><br>
>><br>
>> On Mon, Sep 8, 2014 at 11:20 AM, Edgar Magana <<a href="mailto:edgar.magana@workday.com">edgar.magana@workday.com</a><br>
>> <mailto:<a href="mailto:edgar.magana@workday.com">edgar.magana@workday.com</a>>> wrote:<br>
>><br>
>> Can you guys include me in any further discussions?<br>
>> I want to help..<br>
>><br>
>> Thanks,<br>
>><br>
>> Edgar<br>
>><br>
>> From: Adam Lawson <<a href="mailto:alawson@aqorn.com">alawson@aqorn.com</a> <mailto:<a href="mailto:alawson@aqorn.com">alawson@aqorn.com</a>>><br>
>> Date: Tuesday, August 26, 2014 at 11:48 AM<br>
>> To: Anne Gentle <<a href="mailto:anne@openstack.org">anne@openstack.org</a> <mailto:<a href="mailto:anne@openstack.org">anne@openstack.org</a>>><br>
>> Cc: David Medberry <<a href="mailto:david.medberry@canonical.com">david.medberry@canonical.com</a><br>
>> <mailto:<a href="mailto:david.medberry@canonical.com">david.medberry@canonical.com</a>>>, Sriram Subramanian<br>
>> <<a href="mailto:sriram@sriramhere.com">sriram@sriramhere.com</a> <mailto:<a href="mailto:sriram@sriramhere.com">sriram@sriramhere.com</a>>>,<br>
>> "<a href="mailto:openstack-docs@lists.openstack.org">openstack-docs@lists.openstack.org</a><br>
>> <mailto:<a href="mailto:openstack-docs@lists.openstack.org">openstack-docs@lists.openstack.org</a>>"<br>
>> <<a href="mailto:openstack-docs@lists.openstack.org">openstack-docs@lists.openstack.org</a><br>
>> <mailto:<a href="mailto:openstack-docs@lists.openstack.org">openstack-docs@lists.openstack.org</a>>>,<br>
>> "<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a><br>
>> <mailto:<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>>"<br>
>> <<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a><br>
>> <mailto:<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>>><br>
>> Subject: Re: [Openstack-operators] High Availability Guide team<br>
>><br>
>> I'd be happy to participate as needed Anne.<br>
>><br>
>> On Aug 26, 2014 11:10 AM, "Anne Gentle" <<a href="mailto:anne@openstack.org">anne@openstack.org</a><br>
>> <mailto:<a href="mailto:anne@openstack.org">anne@openstack.org</a>>> wrote:<br>
>><br>
>> Hi all,<br>
>> Cross-posting to -docs and -operators.<br>
>><br>
>> At the Ops mid-cycle meetup this week, Matt Griffin, David<br>
>> Medberry, and Sriram Subramanian offered to start a review team<br>
>> for the High Availability Guide. It needs some updates and it's<br>
>> best if the review team works similar to the Security Guide --<br>
>> subject matter experts working with core docs team members for<br>
>> reviews. So I'm proposing we pull it into its own repo just like<br>
>> the Security Guide. Any reasons not to? I think the next steps are:<br>
>><br>
>> 1. Propose a patch to openstack/governance to show the repo is<br>
>> governed by the Docs program.<br>
>> 2. Propose a patch that sets up a separate review team starting<br>
>> with Matt, David, and Sriram. We think Emilien would be<br>
>> interested too, sound good? Any others? We can have members of<br>
>> openstack-docs-core as well, similar to the Security Guide.<br>
>> 3. Propose a patch that gets that guide building separately in a<br>
>> different repo.<br>
>> 4. Start working on the four bugs already logged [1] and logged<br>
>> more as needed.<br>
>><br>
>><br>
>> Hi all,<br>
>> Sounds like we still need the tasks above to happen.<br>
>><br>
>> Sriram and Andreas, I've got a branch with the HA Guide separated out<br>
>> at <a href="https://github.com/annegentle/ha-guide" target="_blank">https://github.com/annegentle/ha-guide</a> -- can you take a look and see<br>
>> if we can use it for the starting point? If it's good-to-go, I can take<br>
>> tasks 1 and 3. (Sriram, I hope you didn't get too far with the separate<br>
>> repo, holler if you want to divvy up either of those.)<br>
><br>
> That is as simple import without all the history and seems to have one<br>
> level too much.<br>
><br>
> I propose to do use git filter-branch to keep the history intact,<br>
<br>
</div></div>Have a look at:<br>
<br>
<a href="https://github.com/ajaeger/ha-guide/tree/master/doc" target="_blank">https://github.com/ajaeger/ha-guide/tree/master/doc</a><br>
<br>
This one misses the top-level files that were in your directory but I<br>
can add them back later on.<br>
<br>
Sriram, do you have the perfect solution? ;)<br>
<div class="HOEnZb"><div class="h5"><br>
Andreas<br>
--<br>
Andreas Jaeger aj@{<a href="http://suse.com" target="_blank">suse.com</a>,<a href="http://opensuse.org" target="_blank">opensuse.org</a>} Twitter/Identica: jaegerandi<br>
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany<br>
GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)<br>
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126<br>
</div></div></blockquote></div><br></div>