Open Stack

Overall I think u just hit a weakspot in openstack. But lots of people are
here to help :-)

A lot of the upgrading depends on what your current [glance, nova, cinder,
quantum] configuration is, what database u are using, what the allowable
VM impact is, how your network is deployed, how your db is deployed, what
kind of API downtime is allowable, what your API deployment is (behind
load-balancers), what package management system you are using (where are u
getting the code), how is that code deployed (puppet, chef, other?), how
comfortable with upgrades have you been, are you just planning on doing a
python upgrade (or will things like the linux kernel or libvirt be
affected as well), how big of a team do u have to test the upgrade
process, what is your idea of a smooth upgrade (no downtime, some
downtime?), in what timeline do you want this upgrade done...

Lots of questions I know, but all of them (and likely more that I missed)
are relevant to how this upgrade process will work.

-Josh

On 12/5/13 4:35 PM, "Sumit Gaur" <sumitkgaur at gmail.com> wrote:

> Hi ,
> I am a openstack user and I had faced a lot of problems in upgrading
>my environment to newer versions of openstack releases. I need to know
>if Openstack dev team is working on *smooth upgrade* process of
>further release ? I know there are process doc available but process
>itself is very difficult.
>
>Can we start looking into this direction as it is a major pain point
>and show stopper for openstack users so far. *Please let me know any
>pointers in this directions*.
>
> Thanks
> sumit
>Cloud administrator
>
>_______________________________________________
>Mailing list: 
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>Post to     : openstack at lists.openstack.org
>Unsubscribe : 
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack