[Openstack-docs] Upgrading to Havana
Tom Fifield
tom at openstack.org
Thu Dec 19 03:24:17 UTC 2013
Upgrades are definitely operations, not a 'special case of an installation'.
This is for a few reasons, here's some examples:
* The audience of the installation guide and the operations guide is
very different. The manual installation guide is most likely to be read
by first-timers, who in many cases then use this to turn it into
something that gets managed by an automated configuration management
system such as puppet or chef.
* The steps involved in upgrading from one version to another and
installing a new version from scratch are completely different, be they
package management, or configuration file changes
* When you're upgrading, you have to keep all of your existing virtual
machines, networks, storage objects etc available and on-line. This
makes upgrades fundamentally different to installations.
Regards,
Tom
On 18/12/13 12:48, Diane Fleming wrote:
> I agree with that - it's related to install.
>
> Sent from my iPhone
>
> On Dec 17, 2013, at 10:41 PM, "Nick Chase" <nchase at mirantis.com
> <mailto:nchase at mirantis.com>> wrote:
>
>> Actually it sounds like an installation issue to me. Basically you
>> are installing the same version as the install guide, but with the
>> special case that you already have the previous version installed.
>>
>> On Dec 17, 2013 11:12 PM, "Anne Gentle" <annegentle at justwriteclick.com
>> <mailto:annegentle at justwriteclick.com>> wrote:
>>
>>
>>
>>
>> On Tue, Dec 17, 2013 at 10:03 PM, Summer Long <slong at redhat.com
>> <mailto:slong at redhat.com>> wrote:
>>
>> Hi all,
>> Am triaging for bug day, and have signed up to do the upgrade
>> notes (perhaps not on bug day, but you know what I mean).
>> However, er, where should they go?
>>
>> Currently, I'm only seeing the notes in the Ops manual, was
>> there a consensus to put them somewhere else?
>> A new Upgrading article for the Havana page? The Installation
>> Guide is already too bulky (would think).
>> Or have I missed them completely somewhere else?
>>
>> Should they also be pulled out of the Ops guide (since
>> upgrading is SO version-specific)?
>>
>>
>> I think the job of upgrading usually lands in an
>> operator/architects lap, so I think the Ops Guide is the location.
>> O'Reilly editor thinks so too. It shouldn't be written to be super
>> version specific, though, if it can be helped. Here's the current
>> section: http://docs.openstack.org/trunk/openstack-ops/content/maintenance.html#upgrades
>>
>> I hate to envision this, but I wonder if it could be its own
>> guide? Blah. I stand by my request to have it in the Ops Guide.
>>
>> Anne
>>
>>
>>
>> thanks, Summer
>>
>> --
>> Summer Long
>> OpenStack Documentation Lead
>> Engineering Content Services
>>
>> Red Hat Asia Pacific
>> Brisbane, Australia
>> slong at redhat.com <mailto:slong at redhat.com> | irc: slong
>>
>> _______________________________________________
>> Openstack-docs mailing list
>> Openstack-docs at lists.openstack.org
>> <mailto:Openstack-docs at lists.openstack.org>
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>
>>
>>
>>
>> --
>> Anne Gentle
>> annegentle at justwriteclick.com <mailto:annegentle at justwriteclick.com>
>>
>> _______________________________________________
>> Openstack-docs mailing list
>> Openstack-docs at lists.openstack.org
>> <mailto: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
>> <mailto: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
>
More information about the Openstack-docs
mailing list