Open Stack

----- Original Message -----
> From: "Steve Gordon" <sgordon at redhat.com>
> To: "Matt Kassawara" <mkassawara at gmail.com>
> 
> ----- Original Message -----
> > From: "Matt Kassawara" <mkassawara at gmail.com>
> > To: "Steve Gordon" <sgordon at redhat.com>
> > 
> > While OpenStack RC code often sufficiently tests services, packaging
> > concerns such as dependencies and default configuration options tend to lag
> > by one or more milestone/RC cycles. The RDO repository only contained
> > milestone 3 packages until just prior to the official release of Juno when
> > RC2 packages appeared in it.
> 
> RC2 tarballs themselves only became available just prior to the official
> release (e.g. Oct 9th for Cinder, Oct 10th for Neutron) and were put into
> the repo on the 13th. The gap between RC1 tarballs being available and being
> put in the repo was similar.
> 
> > Testing packages (even just the core services), writing patches, reviewing
> > patches, and general time allocation
> > issues can delay a functional installation guide by a week or more beyond
> > the package release date. Furthermore, the RDO packages require testing on
> > RHEL/CentOS and Fedora plus the neutron and nova-network variations. I
> > would like to provide users with a mostly functional installation guide on
> > the official release date which would require availability of at least RC
> > packages at least one week prior to the official release date.
> > release packages becoming available yesterday afternoon and the plan to cut
> > juno/stable for openstack-manuals tomorrow gives us about one day to
> > install the packages on two distributions each with two variants, determine
> > the issues, write patches, test them, and run them through the review
> > process before all changes involve backports.
> 
> As a result of user feedback from previous test days we stage and test the
> RDO packages to ensure basic sanity before putting them into the repo, this
> takes time but ensures that we have at least some level of confidence in the
> packages being deployed and avoids user frustration caused by basic issues
> that can be easily prevented. If you wish to access the staged packages in
> future while they are still undergoing testing, just ask (they are public,
> just not in the main repo).

Going back through the repo [1] we pushed builds based on the final release into the repo on the 22nd/23rd and held off formally announcing while we fixed a few more bugs over the weekend.

Thanks,

Steve

[1] https://repos.fedorapeople.org/repos/openstack/openstack-juno/epel-7/?C=M;O=A
> > On Tue, Oct 28, 2014 at 4:23 PM, Steve Gordon <sgordon at redhat.com> wrote:
> > 
> > > ----- Original Message -----
> > > > From: "Matt Kassawara" <mkassawara at gmail.com>
> > > > To: "Anne Gentle" <anne at openstack.org>
> > > >
> > > > If other reasons (outside of the installation guide) exist to move it
> > > > on
> > > > the 29th rather than wait until after the summit, I can deal... but
> > > > backporting patches for RHEL/CentOS/Fedora will take more time and
> > > effort.
> > > > Not our fault RDO can't push release packages out in a reasonable
> > > > amount
> > > of
> > > > time.
> > >
> > > Can you elaborate on what's reasonable so we can endeavour to accommodate
> > > in future? Our aim this time around was for +2 weeks on upstream release
> > > to
> > > allow some level of smoke testing to occur, despite that M-3 and RC
> > > packages that could have been used were available leading up to this.
> > >
> > > We've been communicating this to users @
> > > https://www.redhat.com/archives/rdo-list/
> > >
> > > Thanks,
> > >
> > > Steve
> > >
> > > > On Mon, Oct 27, 2014 at 9:45 PM, Anne Gentle <anne at openstack.org>
> > > > wrote:
> > > >
> > > > >
> > > > > On Mon, Oct 27, 2014 at 9:34 PM, Matt Kassawara
> > > > > <mkassawara at gmail.com>
> > > > > wrote:
> > > > >
> > > > >> The RDO Juno release packages for RHEL/CentOS/Fedora only became
> > > > >> available today [1] which leaves very little time for testing and
> > > patching
> > > > >> the installation guide prior to cutting juno/stable for
> > > openstack-manuals
> > > > >> on the 29th. Can we push it out a day or two?
> > > > >>
> > > > >
> > > > > I think if we don't do the 29th it'll be after Nov 7th due to
> > > > > Andreas's
> > > > > and my travel schedules, is that an okay solution?
> > > > >
> > > > >
> > > > >>
> > > > >> [1]
> > > > >>
> > > https://openstack.redhat.com/forum/discussion/992/rdo-juno-packages-available
> > > > >>
> > > > >> _______________________________________________
> > > > >> 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
> > > >
> > >
> > > --
> > > Steve Gordon, RHCE
> > > Sr. Technical Product Manager,
> > > Red Hat Enterprise Linux OpenStack Platform
> > >
> > 
> 
> _______________________________________________
> OpenStack-docs mailing list
> OpenStack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
> 

-- 
Steve Gordon, RHCE
Sr. Technical Product Manager,
Red Hat Enterprise Linux OpenStack Platform