Hi Ronelle,
maybe I understand it wrong but I thought that Tripleo Quickstart was for
deploying virtual environments?
And for baremetal we should use
?
Thanks
On Fri, Jun 3, 2016 at 4:43 PM, Ronelle Landy <rlandy(a)redhat.com> wrote:
 Hello,
 We have had success deploying RDO (Mitaka) on baremetal systems - using
 Tripleo Quickstart with both single-nic-vlans and bond-with-vlans network
 isolation configurations.
 Baremetal can have some complicated networking issues but, from previous
 experiences, if a single-controller deployment worked but a HA deployment
 did not, I would check:
  - does the HA deployment command include: -e
 /usr/share/openstack-tripleo-heat-templates/environments/puppet-pacemaker.yaml
  - are there possible MTU issues?
 ----- Original Message -----
 > From: "Christopher Brown" <cbrown2(a)ocf.co.uk>
 > To: pgsousa(a)gmail.com, ibravo(a)ltgfederal.com
 > Cc: rdo-list(a)redhat.com
 > Sent: Friday, June 3, 2016 10:29:39 AM
 > Subject: Re: [rdo-list] Baremetal Tripleo stable version?
 >
 > Hello Ignacio,
 >
 > Thanks for your response and good to know it isn't just me!
 >
 > I would be more than happy to provide developers with access to our
 > bare metal environments. I'll also file some bugzilla reports to see if
 > this generates any interest.
 >
 > Please do let me know if you make any progress - I am trying to deploy
 > HA with network isolation, multiple nics and vlans.
 >
 > The RDO web page states:
 >
 > "If you want to create a production-ready cloud, you'll want to use the
 > TripleO quickstart guide."
 >
 > which is a contradiction in terms really.
 >
 > Cheers
 >
 > On Fri, 2016-06-03 at 14:30 +0100, Ignacio Bravo wrote:
 > > Pedro / Christopher,
 > >
 > > Just wanted to share with you that I also had plenty of issues
 > > deploying on bare metal HA servers, and have paused the deployment
 > > using TripleO until better winds start to flow here. I was able to
 > > deploy the QuickStart, but on bare metal the history was different.
 > > Couldn't even deploy a two server configuration.
 > >
 > > I was thinking that it would be good to have the developers have
 > > access to one of our environments and go through a full install with
 > > us to better see where things fail. We can do this handholding
 > > deployment once every week/month based on developers time
 > > availability. That way we can get a working install, and we can
 > > troubleshoot real life environment problems.
 > >
 > >
 > > IB
 > >
 > > On Jun 3, 2016, at 6:15 AM, Pedro Sousa <pgsousa(a)gmail.com> wrote:
 > >
 > > > Yes. I've used this, but I'll try again as there's seems to be
new
 > > > updates.
 > > >
 > > >
 > > >
 > > > Stable Branch Skip all repos mentioned above, other than epel-
 > > > release which is still required.
 > > > Enable latest RDO Stable Delorean repository for all packages
 > > > sudo curl -o /etc/yum.repos.d/delorean-liberty.repo 
https://trunk.r
 > > > 
doproject.org/centos7-liberty/current/delorean.repo
 > > > Enable the Delorean Deps repository
 > > > sudo curl -o /etc/yum.repos.d/delorean-deps-liberty.repo 
http://tru
 > > > 
nk.rdoproject.org/centos7-liberty/delorean-deps.repo
 > > >
 > > > On Fri, Jun 3, 2016 at 11:10 AM, Christopher Brown <cbrown2(a)ocf.co.
 > > > uk> wrote:
 > > > > No, Liberty deployed ok for us.
 > > > >
 > > > > It suggests to me a package mismatch. Have you completely rebuilt
 > > > > the
 > > > > undercloud and then the images using Liberty?
 > > > >
 > > > > On Fri, 2016-06-03 at 11:04 +0100, Pedro Sousa wrote:
 > > > > > AttributeError: 'module' object has no attribute
'PortOpt'
 > > > > --
 > > > > Regards,
 > > > >
 > > > > Christopher Brown
 > > > > OpenStack Engineer
 > > > > OCF plc
 > > > >
 > > > > Tel: +44 (0)114 257 2200
 > > > > Web: 
www.ocf.co.uk
 > > > > Blog: blog.ocf.co.uk
 > > > > Twitter: @ocfplc
 > > > >
 > > > > Please note, any emails relating to an OCF Support request must
 > > > > always
 > > > > be sent to support(a)ocf.co.uk for a ticket number to be generated
 > > > > or
 > > > > existing support ticket to be updated. Should this not be done
 > > > > then OCF
 > > > >
 > > > > cannot be held responsible for requests not dealt with in a
 > > > > timely
 > > > > manner.
 > > > >
 > > > > OCF plc is a company registered in England and Wales. Registered
 > > > > number
 > > > >
 > > > > 4132533, VAT number GB 780 6803 14. Registered office address:
 > > > > OCF plc,
 > > > >
 > > > > 5 Rotunda Business Centre, Thorncliffe Park, Chapeltown,
 > > > > Sheffield S35
 > > > > 2PG.
 > > > >
 > > > > If you have received this message in error, please notify us
 > > > > immediately and remove it from your system.
 > > > >
 > >
 > > _______________________________________________
 > > rdo-list mailing list
 > > rdo-list(a)redhat.com
 > > 
https://www.redhat.com/mailman/listinfo/rdo-list
 > >
 > > To unsubscribe: rdo-list-unsubscribe(a)redhat.com
 > --
 > Regards,
 >
 > Christopher Brown
 > OpenStack Engineer
 > OCF plc
 >
 > Tel: +44 (0)114 257 2200
 > Web: 
www.ocf.co.uk
 > Blog: blog.ocf.co.uk
 > Twitter: @ocfplc
 >
 > Please note, any emails relating to an OCF Support request must always
 > be sent to support(a)ocf.co.uk for a ticket number to be generated or
 > existing support ticket to be updated. Should this not be done then OCF
 >
 > cannot be held responsible for requests not dealt with in a timely
 > manner.
 >
 > OCF plc is a company registered in England and Wales. Registered number
 >
 > 4132533, VAT number GB 780 6803 14. Registered office address: OCF plc,
 >
 > 5 Rotunda Business Centre, Thorncliffe Park, Chapeltown, Sheffield S35
 > 2PG.
 >
 > If you have received this message in error, please notify us
 > immediately and remove it from your system.
 >
 > _______________________________________________
 > rdo-list mailing list
 > rdo-list(a)redhat.com
 > 
https://www.redhat.com/mailman/listinfo/rdo-list
 >
 > To unsubscribe: rdo-list-unsubscribe(a)redhat.com
 >