Open Stack

This is definitely a place where we'll need to be some what distro
specific.  If it's close enough we can just run apt&rpm flavored
instructions in parallel keeping the same steps but two sets of
example commands where needed that would be ideal, well to me anyway.

Tom and I (well mostly Tom) went through a test upgrade to verify the
Ubuntu steps starting from a clean Grizzly Install (using the havana
install guide but with grizzly packages ). This should be done on RHEL
instructions as well, if Matt can do this that's great, if not once
it's written up I could give it a go.

-Jon

On Sat, Jan 25, 2014 at 12:17 PM, Anne Gentle <anne at openstack.org> wrote:
>
>
>
> On Sat, Jan 25, 2014 at 10:23 AM, Matt Kassawara <mkassawara at gmail.com>
> wrote:
>>
>> Oops... I didn't know about the lack of conditional markup.  In that case,
>> just leave room for a second section in the markup and I'll try to match the
>> Ubuntu flow.  Do we want to include any other distributions?
>>
>
> You can include other distributions, we are working on a RHEL architecture
> inclusion. I think that a second section would be warranted with a change to
> the title and xml:id.
>
> My changes are done for markup and editing, and I was able to update a patch
> marked WIP. I didn't mark it WIP again, but did amend the commit message to
> indicate this shouldn't merge until testing is done.
>
> Thanks,
> Anne
>
>
>>
>>
>> On Sat, Jan 25, 2014 at 9:09 AM, Anne Gentle <anne at openstack.org> wrote:
>>>
>>> Hi Matt,
>>>
>>> Great idea! Just be aware we can't do conditional markup in this book as
>>> there's only one output. Not sure if that's what you were thinking of
>>> (conditions) or just a second section, but it's a good idea.
>>>
>>> Anne
>>>
>>>
>>> On Sat, Jan 25, 2014 at 10:05 AM, Matt Kassawara <mkassawara at gmail.com>
>>> wrote:
>>>>
>>>> I'm curious about this too since I'm planning to add the RHEL-style
>>>> instructions for the migration process.  I was mostly planning to record the
>>>> instructions locally, wait for markup of the Ubuntu instructions, and then
>>>> upload a patch to add the RHEL-style instructions before any final markup
>>>> and approval.  Alternatively, I can wait until someone merges the complete
>>>> Ubuntu instructions and then upload a patch to add the RHEL-style
>>>> instructions.  I'm still a noob here. :)
>>>>
>>>>
>>>> On Sat, Jan 25, 2014 at 8:52 AM, Jeremy Stanley <fungi at yuggoth.org>
>>>> wrote:
>>>>>
>>>>> On Sat, Jan 25, 2014 at 10:27 AM, Anne Gentle <anne at openstack.org>
>>>>> wrote:
>>>>> [...]
>>>>> > The thing about setting something to "WIP" is that another author
>>>>> > actually
>>>>> > can't work on it while it's in WIP state (someone correct me if
>>>>> > that's
>>>>> > wrong). Only the original author can set it to "ready for work"
>>>>> > again.
>>>>>
>>>>> Having the current patchset of a change set to work in progress
>>>>> should not prevent other contributors from uploading a new patchset.
>>>>> If it seems to, I'd be curious to see the resulting error message.
>>>>> --
>>>>> Jeremy Stanley
>>>>>
>>>>> _______________________________________________
>>>>> Openstack-docs mailing list
>>>>> Openstack-docs at lists.openstack.org
>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Openstack-docs mailing list
>>>> Openstack-docs at lists.openstack.org
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>>>
>>>
>>
>
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>