<div dir="ltr">Hi Graeme,<div><br></div><div>I ran introspection several times and didn't have the problem you mentioned. Always worked fine.</div><div><br></div><div>However I did have problems with my generated overcloud images:</div><div><br></div><div>"Could not retrieve fact='rabbitmq_nodename',<br>resolution='<anonymous>':<br>undefined method `[]' for nil:NilClass Could not retrieve<br>fact='rabbitmq_nodename', resolution='<anonymous>': undefined<br>method `' for nil:NilClass"<br></div><div><br></div><div>After downloading the delorean generated images the problem was gone.</div><div><br></div><div>Regards,</div><div>Pedro Sousa</div><div><br></div><div><br></div><div><br></div><div>How</div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 6, 2016 at 1:51 AM, Graeme Gillies <span dir="ltr"><<a href="mailto:ggillies@redhat.com" target="_blank">ggillies@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="">On 06/06/16 10:26, Pedro Sousa wrote:<br>
> Hi Graeme,<br>
><br>
> my 2 cents here, my experience was different from yours.<br>
><br>
> I've managed to install tripleo with 3 controllers + 3 computes without<br>
> epel repos and without applying any patches, using mitaka repos from<br>
> cbs. I didn't have any issues with introspection, but I tested on the<br>
> same hw (Dell PowerEdge R430). Then I downloaded some prebuild overcloud<br>
> images from delorean<br>
> repos: <a href="http://buildlogs.centos.org/centos/7/cloud/x86_64/tripleo_images/mitaka/delorean/" rel="noreferrer" target="_blank">http://buildlogs.centos.org/centos/7/cloud/x86_64/tripleo_images/mitaka/delorean/</a><br>
><br>
> That being said, there's a lot to be done concerning install<br>
> documentation, and how to report bugs and issues, specifically for<br>
> baremetal environments, where a lot of people like me intend to use<br>
> tripleo for production.<br>
><br>
> Regards<br>
<br>
</span>The patch I note in step 4) is to work around an issue that only affects<br>
you if you introspect a node more than once. It will always work the<br>
first time, it's the second time that it will fail. So if you are only<br>
introspecting once then you don't need it.<br>
<br>
The patch I apply in step 5) is to work around an issue that is fixed in<br>
DLRN, and is only necessary if you want to build images yourself and not<br>
use prebuilt ones. By using prebuilt ones from DLRN, you are in effect<br>
getting the fix by nature of that (and thus don't need the patch).<br>
<br>
Note that if you are also sourcing your overcloud-full.qcow2 from DLRN<br>
repos, then you are no longer deploying an overcloud that uses CBS, you<br>
are deploying an overcloud from DLRN. You can confirm this by checking<br>
if the rdo-release rpm is installed on your overcloud, and check that in<br>
/etc/yum.repos.d there is no 'delorean.repo'<br>
<br>
Regards,<br>
<br>
Graeme<br>
<span class=""><br>
><br>
><br>
><br>
><br>
><br>
> On Mon, Jun 6, 2016 at 12:37 AM, Graeme Gillies <<a href="mailto:ggillies@redhat.com">ggillies@redhat.com</a><br>
</span><div><div class="h5">> <mailto:<a href="mailto:ggillies@redhat.com">ggillies@redhat.com</a>>> wrote:<br>
><br>
> Hi Everyone,<br>
><br>
> I just wanted to say I have been following this thread quite closely and<br>
> can sympathize with some of the pain people are going through to get<br>
> tripleO to work.<br>
><br>
> Currently it's quite difficult and a bit opaque on how to actually<br>
> utilise the stable mitaka repos in order to build a functional<br>
> undercloud and overcloud environment.<br>
><br>
> First I wanted to share the steps I have undergone in order to get a<br>
> functional overcloud working with RDO Mitaka utilising the RDO stable<br>
> release built by CentOS, and then I'll talk about some specific steps I<br>
> think need to be undertaken by the RDO/TripleO team in order to provide<br>
> a better experience in the future.<br>
><br>
> To get a functional overcloud using RDO Mitaka, you need to do the<br>
> following<br>
><br>
> 1) Install EPEL on your undercloud<br>
> 2) Install <a href="https://www.rdoproject.org/repos/rdo-release.rpm" rel="noreferrer" target="_blank">https://www.rdoproject.org/repos/rdo-release.rpm</a> on your<br>
> undercloud<br>
> 3) Following the normal steps to install your undercloud (modifying<br>
> undercloud.conf, and running openstack undercloud install<br>
> 4) You will now need to manually patch ironic on the undercloud in order<br>
> to make sure repeated introspection works. This might not be needed if<br>
> you don't do any introspection, but I find more often than not you end<br>
> up having to do it, so it's worthwhile. The bug you need to patch is [1]<br>
> and I typically run the following commands to apply the patch<br>
><br>
> # sudo su -<br>
> $ cd /usr/lib/python2.7/site-packages<br>
> $ curl<br>
> '<a href="https://review.openstack.org/changes/306421/revisions/abd50d8438e7d371ce24f97d8f8f67052b562007/patch?download" rel="noreferrer" target="_blank">https://review.openstack.org/changes/306421/revisions/abd50d8438e7d371ce24f97d8f8f67052b562007/patch?download</a>'<br>
> | base64 -d | patch -p1<br>
> $ systemctl restart openstack-ironic-inspector<br>
> $ systemctl restart openstack-ironic-inspector-dnsmasq<br>
> $ exit<br>
> #<br>
><br>
> 5) Manually patch the undercloud to build overcloud images using<br>
> rhos-release rpm only (which utilises the stable Mitaka repo from<br>
> CentOS, and nothing from RDO Trunk [delorean]). I do this by modifying<br>
> the file<br>
><br>
> /usr/lib/python2.7/site-packages/tripleoclient/v1/overcloud_image.py<br>
><br>
> At around line 467 you will see a reference to epel, I add a new line<br>
> after that to include the rdo_release DIB element to the build as well.<br>
> This typically makes the file look something like<br>
><br>
> <a href="http://paste.openstack.org/show/508196/" rel="noreferrer" target="_blank">http://paste.openstack.org/show/508196/</a><br>
><br>
> (note like 468). Then I create a directory to store my images and build<br>
> them specifying the mitaka version of rdo_release. I then upload these<br>
> images<br>
><br>
> # mkdir ~/images<br>
> # cd ~/images<br>
> # export RDO_RELEASE=mitaka<br>
> # openstack overcloud image build --all<br>
> # openstack overcloud image upload --update-existing<br>
><br>
> 6) Because of the bug at [2] which affects the ironic agent ramdisk, we<br>
> need to build a set of images utilising RDO Trunk for the mitaka branch<br>
> (where the fix is applied), and then upload *only* the new ironic<br>
> ramdisk. This is done with<br>
><br>
> # mkdir ~/images-mitaka-trunk<br>
> # cd ~/images-mitaka-trunk<br>
> # export USE_DELOREAN_TRUNK=1<br>
> # export<br>
> DELOREAN_TRUNK_REPO="<a href="http://trunk.rdoproject.org/centos7-mitaka/current/" rel="noreferrer" target="_blank">http://trunk.rdoproject.org/centos7-mitaka/current/</a>"<br>
> # export DELOREAN_REPO_FILE="delorean.repo"<br>
> # openstack overcloud image build --type agent-ramdisk<br>
> # sudo cp ironic-python-agent.initramfs /httpboot/agent.ramdisk<br>
><br>
> 7) Follow the rest of the documentation to deploy the overcloud normally<br>
><br>
> Please note that obviously your mileage may vary, and this is by all<br>
> means not an exclusive list of the problems. I have however used these<br>
> steps to do multiple node deployments (10+ nodes) with HA over different<br>
> hardware sets with different networking setups (single nic, multiple nic<br>
> with bonding + vlans).<br>
><br>
> With all the different repos floating around, all which change very<br>
> rapidly, combined with the documentation defaults targeting developers<br>
> and CI systems (not end users), it's hard to not only get a stable<br>
> TripleO install up, but also communicate and discuss clearly with others<br>
> what is working, what is broken, and how to compare two installations to<br>
> see if they are experiencing the same issues.<br>
><br>
> To this end I would like to suggest to the RDO and TripleO community<br>
> that we undertake the following<br>
><br>
> 1) Overhaul all the TripleO documentation so that all the steps default<br>
> to utilising/deploying using RDO Stable (that is, the releases done by<br>
> CBS). There should be colored boxes with alt steps for those who wish to<br>
> use RDO Trunk on the stable branch, and RDO Trunk from master. This<br>
> basically inverts the current pattern. I think anyone, Operator or<br>
> developer, who is working through the documentation for the first time,<br>
> should be given steps that maximise the chance of success, and thus the<br>
> most stable release we have. Once a user has gone through the process<br>
> once, they can look at the alternative steps for more aggressive<br>
> releases<br>
><br>
> 2) Patch python-tripleoclient so that by default, when you run<br>
> "openstack overcloud image build" it builds the images utilising the<br>
> rdo_release DIB element, and sets the RDO_RELEASE environment variable<br>
> to be 'mitaka' or whenever the current stable release is (and we should<br>
> endevour to update it with new releases). There should be no extra<br>
> environment variables necessary to build images, and by default it<br>
> should never touch anything RDO Trunk (delorean) related<br>
><br>
> 3) For bugs like the two I have mentioned above, we need to have some<br>
> sort of robust process for either backporting those patches to the<br>
> builds in CBS (I understand we don't do this for various reasons), or we<br>
> need some kind of tooling or solution that allows operators to apply<br>
> only the fixes they need from RDO Trunk (delorean). We need to ensure<br>
> that when an Operator utilises TripleO they have the greatest chance of<br>
> success, and bugs such as these which severely impact the deployment<br>
> process harm the adoption of TripleO and RDO.<br>
><br>
> 4) We should curate and keep an up to date page on <a href="http://rdoproject.org" rel="noreferrer" target="_blank">rdoproject.org</a><br>
</div></div>> <<a href="http://rdoproject.org" rel="noreferrer" target="_blank">http://rdoproject.org</a>> that<br>
<span class="">> does highlight the outstanding issues related to TripleO on the RDO<br>
> Stable (CBS) releases. These should have links to relevant bugzillas,<br>
> clean instructions on how to work around the issue, or cleanly apply a<br>
> patch to avoid the issue, and as new releases make it out, we should<br>
> update the page to drop off workarounds that are no longer needed.<br>
><br>
> The goal is to push Operators/Users to working with our most stable code<br>
> as much as possible, and track/curate issues around that. This way<br>
> everyone should be on the same page, issues are easier to discuss and<br>
> diagnose, and overall peoples experiences should be better.<br>
><br>
> I'm interested in thoughts, feedback, and concerns, both from the RDO<br>
> and TripleO community, and from the Operator/User community.<br>
><br>
> Regards,<br>
><br>
> Graeme<br>
><br>
> [1] <a href="https://bugs.launchpad.net/ironic-inspector/+bug/1570447" rel="noreferrer" target="_blank">https://bugs.launchpad.net/ironic-inspector/+bug/1570447</a><br>
> [2] <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1322892" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1322892</a><br>
><br>
> On 05/06/16 02:04, Pedro Sousa wrote:<br>
> > Thanks Marius,<br>
> ><br>
> > I can confirm that it installs fine with 3 controllers + 3 computes<br>
> > after recreating the stack<br>
> ><br>
> > Regards<br>
> ><br>
> > On Sat, Jun 4, 2016 at 4:14 PM, Marius Cornea <<a href="mailto:marius@remote-lab.net">marius@remote-lab.net</a> <mailto:<a href="mailto:marius@remote-lab.net">marius@remote-lab.net</a>><br>
</span><span class="">> > <mailto:<a href="mailto:marius@remote-lab.net">marius@remote-lab.net</a> <mailto:<a href="mailto:marius@remote-lab.net">marius@remote-lab.net</a>>>> wrote:<br>
> ><br>
> > Hi Pedro,<br>
> ><br>
> > Scaling out controller nodes is not supported at this moment:<br>
> > <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1243312" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1243312</a><br>
> ><br>
> > On Sat, Jun 4, 2016 at 5:05 PM, Pedro Sousa <<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a> <mailto:<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a>><br>
</span><span class="">> > <mailto:<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a> <mailto:<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a>>>> wrote:<br>
> > > Hi,<br>
> > ><br>
> > > some update on scaling the cloud:<br>
> > ><br>
> > > 1 controller + 1 compute -> 1 controller + 3 computes OK<br>
> > ><br>
> > > 1 controller + 3 computes -> 3 controllers + 3 compute FAILS<br>
> > ><br>
> > > Problem: The new controller nodes are "stuck" in "pscd start", so<br>
> > it seems<br>
> > > to be a problem joining the pacemaker cluster... Did anyone had this<br>
> > > problem?<br>
> > ><br>
> > > Regards<br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > > On Sat, Jun 4, 2016 at 1:50 AM, Pedro Sousa <<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a> <mailto:<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a>><br>
</span><span class="">> > <mailto:<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a> <mailto:<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a>>>> wrote:<br>
> > >><br>
> > >> Hi,<br>
> > >><br>
> > >> I finally managed to install a baremetal in mitaka with 1<br>
> > controller + 1<br>
> > >> compute with network isolation. Thank god :)<br>
> > >><br>
> > >> All I did was:<br>
> > >><br>
> > >> #yum install centos-release-openstack-mitaka<br>
> > >> #sudo yum install python-tripleoclient<br>
> > >><br>
> > >> without epel repos.<br>
> > >><br>
> > >> Then followed instructions from Redhat Site.<br>
> > >><br>
> > >> I downloaded the overcloud images from:<br>
> > >><br>
> > <a href="http://buildlogs.centos.org/centos/7/cloud/x86_64/tripleo_images/mitaka/delorean/" rel="noreferrer" target="_blank">http://buildlogs.centos.org/centos/7/cloud/x86_64/tripleo_images/mitaka/delorean/</a><br>
> > >><br>
> > >> I do have an issue that forces me to delete a json file and run<br>
> > >> os-refresh-config inside my overcloud nodes other than that it<br>
> > installs<br>
> > >> fine.<br>
> > >><br>
> > >> Now I'll test with more 2 controllers + 2 computes to have a full HA<br>
> > >> deployment.<br>
> > >><br>
> > >> If anyone needs help to document this I'll be happy to help.<br>
> > >><br>
> > >> Regards,<br>
> > >> Pedro Sousa<br>
> > >><br>
> > >><br>
> > >> On Fri, Jun 3, 2016 at 8:26 PM, Ronelle Landy <<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a> <mailto:<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a>><br>
</span><span class="">> > <mailto:<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a> <mailto:<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a>>>> wrote:<br>
> > >>><br>
> > >>> The report says: "Fix Released" as of 2016-05-24.<br>
> > >>> Are you installing on a clean system with the latest repositories?<br>
> > >>><br>
> > >>> Might also want to check your version of rabbitmq: I have<br>
> > >>> rabbitmq-server-3.6.2-3.el7.noarch on CentOS 7.<br>
> > >>><br>
> > >>> ----- Original Message -----<br>
> > >>> > From: "Pedro Sousa" <<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a> <mailto:<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a>><br>
</span><span class="">> <mailto:<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a> <mailto:<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a>>>><br>
> > >>> > To: "Ronelle Landy" <<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a> <mailto:<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a>><br>
</span><span class="">> <mailto:<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a> <mailto:<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a>>>><br>
> > >>> > Cc: "Christopher Brown" <<a href="mailto:cbrown2@ocf.co.uk">cbrown2@ocf.co.uk</a> <mailto:<a href="mailto:cbrown2@ocf.co.uk">cbrown2@ocf.co.uk</a>><br>
</span><span class="">> > <mailto:<a href="mailto:cbrown2@ocf.co.uk">cbrown2@ocf.co.uk</a> <mailto:<a href="mailto:cbrown2@ocf.co.uk">cbrown2@ocf.co.uk</a>>>>, "Ignacio Bravo"<br>
> > >>> > <<a href="mailto:ibravo@ltgfederal.com">ibravo@ltgfederal.com</a> <mailto:<a href="mailto:ibravo@ltgfederal.com">ibravo@ltgfederal.com</a>><br>
</span><span class="">> <mailto:<a href="mailto:ibravo@ltgfederal.com">ibravo@ltgfederal.com</a> <mailto:<a href="mailto:ibravo@ltgfederal.com">ibravo@ltgfederal.com</a>>>>,<br>
> "rdo-list"<br>
> > >>> > <<a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a> <mailto:<a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a>><br>
</span>> <mailto:<a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a> <mailto:<a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a>>>><br>
<span class="">> > >>> > Sent: Friday, June 3, 2016 1:20:43 PM<br>
> > >>> > Subject: Re: [rdo-list] Baremetal Tripleo stable version?<br>
> > >>> ><br>
> > >>> > Anyway to workaround this? Maybe downgrade hiera?<br>
> > >>> ><br>
> > >>> > On Fri, Jun 3, 2016 at 5:55 PM, Ronelle Landy<br>
> > <<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a> <mailto:<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a>><br>
</span>> <mailto:<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a> <mailto:<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a>>>><br>
<span class="">> > >>> > wrote:<br>
> > >>> ><br>
> > >>> > > I am not sure exactly where you installed from, and when you<br>
> > did your<br>
> > >>> > > installation, but any chance, you've hit:<br>
> > >>> > > <a href="https://bugs.launchpad.net/tripleo/+bug/1584892" rel="noreferrer" target="_blank">https://bugs.launchpad.net/tripleo/+bug/1584892</a>?<br>
> > >>> > > There is a link bugzilla record.<br>
> > >>> > ><br>
> > >>> > > ----- Original Message -----<br>
> > >>> > > > From: "Pedro Sousa" <<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a> <mailto:<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a>><br>
</span><span class="">> > <mailto:<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a> <mailto:<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a>>>><br>
> > >>> > > > To: "Ronelle Landy" <<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a> <mailto:<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a>><br>
</span><span class="">> > <mailto:<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a> <mailto:<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a>>>><br>
> > >>> > > > Cc: "Christopher Brown" <<a href="mailto:cbrown2@ocf.co.uk">cbrown2@ocf.co.uk</a> <mailto:<a href="mailto:cbrown2@ocf.co.uk">cbrown2@ocf.co.uk</a>><br>
</span><span class="">> > <mailto:<a href="mailto:cbrown2@ocf.co.uk">cbrown2@ocf.co.uk</a> <mailto:<a href="mailto:cbrown2@ocf.co.uk">cbrown2@ocf.co.uk</a>>>>, "Ignacio Bravo" <<br>
> > >>> > > <a href="mailto:ibravo@ltgfederal.com">ibravo@ltgfederal.com</a> <mailto:<a href="mailto:ibravo@ltgfederal.com">ibravo@ltgfederal.com</a>><br>
</span><span class="">> <mailto:<a href="mailto:ibravo@ltgfederal.com">ibravo@ltgfederal.com</a> <mailto:<a href="mailto:ibravo@ltgfederal.com">ibravo@ltgfederal.com</a>>>>,<br>
> > "rdo-list"<br>
> > >>> > > > <<a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a> <mailto:<a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a>><br>
</span>> <mailto:<a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a> <mailto:<a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a>>>><br>
<span class="">> > >>> > > > Sent: Friday, June 3, 2016 12:26:58 PM<br>
> > >>> > > > Subject: Re: [rdo-list] Baremetal Tripleo stable version?<br>
> > >>> > > ><br>
> > >>> > > > Thanks Ronelle,<br>
> > >>> > > ><br>
> > >>> > > > do you think this kind of errors can be related with network<br>
> > >>> > > > settings?<br>
> > >>> > > ><br>
> > >>> > > > "Could not retrieve fact='rabbitmq_nodename',<br>
> > >>> > > > resolution='<anonymous>':<br>
> > >>> > > > undefined method `[]' for nil:NilClass Could not retrieve<br>
> > >>> > > > fact='rabbitmq_nodename', resolution='<anonymous>': undefined<br>
> > >>> > > > method `[]'<br>
> > >>> > > > for nil:NilClass"<br>
> > >>> > > ><br>
> > >>> > > > On Fri, Jun 3, 2016 at 4:56 PM, Ronelle Landy<br>
> > <<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a> <mailto:<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a>><br>
</span>> <mailto:<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a> <mailto:<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a>>>><br>
<span class="">> > >>> > > > wrote:<br>
> > >>> > > ><br>
> > >>> > > > > Hi Pedro,<br>
> > >>> > > > ><br>
> > >>> > > > > You could use the docs you referred to.<br>
> > >>> > > > > Alternatively, if you want to use a vm for the<br>
> > undercloud and<br>
> > >>> > > > > baremetal<br>
> > >>> > > > > machines for the overcloud, it is possible to use Tripleo<br>
> > >>> > > > > Qucikstart<br>
> > >>> > > with a<br>
> > >>> > > > > few modifications.<br>
> > >>> > > > > <a href="https://bugs.launchpad.net/tripleo-quickstart/+bug/1571028" rel="noreferrer" target="_blank">https://bugs.launchpad.net/tripleo-quickstart/+bug/1571028</a>.<br>
> > >>> > > > ><br>
> > >>> > > > > ----- Original Message -----<br>
> > >>> > > > > > From: "Pedro Sousa" <<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a> <mailto:<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a>><br>
</span><span class="">> > <mailto:<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a> <mailto:<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a>>>><br>
> > >>> > > > > > To: "Ronelle Landy" <<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a> <mailto:<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a>><br>
</span><span class="">> > <mailto:<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a> <mailto:<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a>>>><br>
> > >>> > > > > > Cc: "Christopher Brown" <<a href="mailto:cbrown2@ocf.co.uk">cbrown2@ocf.co.uk</a> <mailto:<a href="mailto:cbrown2@ocf.co.uk">cbrown2@ocf.co.uk</a>><br>
</span><span class="">> > <mailto:<a href="mailto:cbrown2@ocf.co.uk">cbrown2@ocf.co.uk</a> <mailto:<a href="mailto:cbrown2@ocf.co.uk">cbrown2@ocf.co.uk</a>>>>, "Ignacio Bravo" <<br>
> > >>> > > > > <a href="mailto:ibravo@ltgfederal.com">ibravo@ltgfederal.com</a> <mailto:<a href="mailto:ibravo@ltgfederal.com">ibravo@ltgfederal.com</a>><br>
</span><span class="">> <mailto:<a href="mailto:ibravo@ltgfederal.com">ibravo@ltgfederal.com</a> <mailto:<a href="mailto:ibravo@ltgfederal.com">ibravo@ltgfederal.com</a>>>>,<br>
> > "rdo-list"<br>
> > >>> > > > > > <<a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a> <mailto:<a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a>><br>
</span>> <mailto:<a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a> <mailto:<a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a>>>><br>
<span class="">> > >>> > > > > > Sent: Friday, June 3, 2016 11:48:38 AM<br>
> > >>> > > > > > Subject: Re: [rdo-list] Baremetal Tripleo stable version?<br>
> > >>> > > > > ><br>
> > >>> > > > > > Hi Ronelle,<br>
> > >>> > > > > ><br>
> > >>> > > > > > maybe I understand it wrong but I thought that Tripleo<br>
> > >>> > > > > > Quickstart<br>
> > >>> > > was for<br>
> > >>> > > > > > deploying virtual environments?<br>
> > >>> > > > > ><br>
> > >>> > > > > > And for baremetal we should use<br>
> > >>> > > > > ><br>
> > >>> > > > ><br>
> > >>> > ><br>
> > >>> > ><br>
> > <a href="http://docs.openstack.org/developer/tripleo-docs/installation/installation.html" rel="noreferrer" target="_blank">http://docs.openstack.org/developer/tripleo-docs/installation/installation.html</a><br>
> > >>> > > > > > ?<br>
> > >>> > > > > ><br>
> > >>> > > > > > Thanks<br>
> > >>> > > > > ><br>
> > >>> > > > > ><br>
> > >>> > > > > ><br>
> > >>> > > > > ><br>
> > >>> > > > > ><br>
> > >>> > > > > > On Fri, Jun 3, 2016 at 4:43 PM, Ronelle Landy<br>
> > >>> > > > > > <<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a> <mailto:<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a>><br>
</span>> <mailto:<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a> <mailto:<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a>>>><br>
<span class="">> > >>> > > wrote:<br>
> > >>> > > > > ><br>
> > >>> > > > > > > Hello,<br>
> > >>> > > > > > ><br>
> > >>> > > > > > > We have had success deploying RDO (Mitaka) on baremetal<br>
> > >>> > > > > > > systems -<br>
> > >>> > > using<br>
> > >>> > > > > > > Tripleo Quickstart with both single-nic-vlans and<br>
> > >>> > > > > > > bond-with-vlans<br>
> > >>> > > > > network<br>
> > >>> > > > > > > isolation configurations.<br>
> > >>> > > > > > ><br>
> > >>> > > > > > > Baremetal can have some complicated networking<br>
> > issues but,<br>
> > >>> > > > > > > from<br>
> > >>> > > > > previous<br>
> > >>> > > > > > > experiences, if a single-controller deployment<br>
> > worked but a<br>
> > >>> > > > > > > HA<br>
> > >>> > > > > deployment<br>
> > >>> > > > > > > did not, I would check:<br>
> > >>> > > > > > > - does the HA deployment command include: -e<br>
> > >>> > > > > > ><br>
> > >>> > > > ><br>
> > >>> > ><br>
> > >>> > ><br>
> > /usr/share/openstack-tripleo-heat-templates/environments/puppet-pacemaker.yaml<br>
> > >>> > > > > > > - are there possible MTU issues?<br>
> > >>> > > > > > ><br>
> > >>> > > > > > ><br>
> > >>> > > > > > > ----- Original Message -----<br>
> > >>> > > > > > > > From: "Christopher Brown" <<a href="mailto:cbrown2@ocf.co.uk">cbrown2@ocf.co.uk</a> <mailto:<a href="mailto:cbrown2@ocf.co.uk">cbrown2@ocf.co.uk</a>><br>
</span><span class="">> > <mailto:<a href="mailto:cbrown2@ocf.co.uk">cbrown2@ocf.co.uk</a> <mailto:<a href="mailto:cbrown2@ocf.co.uk">cbrown2@ocf.co.uk</a>>>><br>
> > >>> > > > > > > > To: <a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a><br>
</span><span class="">> <mailto:<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a>> <mailto:<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a><br>
> <mailto:<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a>>>,<br>
> > <a href="mailto:ibravo@ltgfederal.com">ibravo@ltgfederal.com</a> <mailto:<a href="mailto:ibravo@ltgfederal.com">ibravo@ltgfederal.com</a>><br>
</span><span class="">> <mailto:<a href="mailto:ibravo@ltgfederal.com">ibravo@ltgfederal.com</a> <mailto:<a href="mailto:ibravo@ltgfederal.com">ibravo@ltgfederal.com</a>>><br>
> > >>> > > > > > > > Cc: <a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a><br>
</span><div><div class="h5">> <mailto:<a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a>> <mailto:<a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a><br>
> <mailto:<a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a>>><br>
> > >>> > > > > > > > Sent: Friday, June 3, 2016 10:29:39 AM<br>
> > >>> > > > > > > > Subject: Re: [rdo-list] Baremetal Tripleo stable<br>
> > version?<br>
> > >>> > > > > > > ><br>
> > >>> > > > > > > > Hello Ignacio,<br>
> > >>> > > > > > > ><br>
> > >>> > > > > > > > Thanks for your response and good to know it<br>
> isn't<br>
> > just me!<br>
> > >>> > > > > > > ><br>
> > >>> > > > > > > > I would be more than happy to provide<br>
> developers with<br>
> > >>> > > > > > > > access to<br>
> > >>> > > our<br>
> > >>> > > > > > > > bare metal environments. I'll also file some<br>
> bugzilla<br>
> > >>> > > > > > > > reports to<br>
> > >>> > > see<br>
> > >>> > > > > if<br>
> > >>> > > > > > > > this generates any interest.<br>
> > >>> > > > > > > ><br>
> > >>> > > > > > > > Please do let me know if you make any<br>
> progress - I am<br>
> > >>> > > > > > > > trying to<br>
> > >>> > > > > deploy<br>
> > >>> > > > > > > > HA with network isolation, multiple nics and<br>
> vlans.<br>
> > >>> > > > > > > ><br>
> > >>> > > > > > > > The RDO web page states:<br>
> > >>> > > > > > > ><br>
> > >>> > > > > > > > "If you want to create a production-ready cloud,<br>
> > you'll<br>
> > >>> > > > > > > > want to<br>
> > >>> > > use<br>
> > >>> > > > > the<br>
> > >>> > > > > > > > TripleO quickstart guide."<br>
> > >>> > > > > > > ><br>
> > >>> > > > > > > > which is a contradiction in terms really.<br>
> > >>> > > > > > > ><br>
> > >>> > > > > > > > Cheers<br>
> > >>> > > > > > > ><br>
> > >>> > > > > > > > On Fri, 2016-06-03 at 14:30 +0100, Ignacio Bravo<br>
> > wrote:<br>
> > >>> > > > > > > > > Pedro / Christopher,<br>
> > >>> > > > > > > > ><br>
> > >>> > > > > > > > > Just wanted to share with you that I also had<br>
> > plenty of<br>
> > >>> > > > > > > > > issues<br>
> > >>> > > > > > > > > deploying on bare metal HA servers, and have<br>
> > paused the<br>
> > >>> > > deployment<br>
> > >>> > > > > > > > > using TripleO until better winds start to flow<br>
> > here. I<br>
> > >>> > > > > > > > > was<br>
> > >>> > > able to<br>
> > >>> > > > > > > > > deploy the QuickStart, but on bare metal the<br>
> > history was<br>
> > >>> > > different.<br>
> > >>> > > > > > > > > Couldn't even deploy a two server<br>
> configuration.<br>
> > >>> > > > > > > > ><br>
> > >>> > > > > > > > > I was thinking that it would be good to<br>
> have the<br>
> > >>> > > > > > > > > developers<br>
> > >>> > > have<br>
> > >>> > > > > > > > > access to one of our environments and go<br>
> through<br>
> > a full<br>
> > >>> > > > > > > > > install<br>
> > >>> > > > > with<br>
> > >>> > > > > > > > > us to better see where things fail. We can<br>
> do this<br>
> > >>> > > > > > > > > handholding<br>
> > >>> > > > > > > > > deployment once every week/month based on<br>
> > developers time<br>
> > >>> > > > > > > > > availability. That way we can get a working<br>
> > install, and<br>
> > >>> > > > > > > > > we can<br>
> > >>> > > > > > > > > troubleshoot real life environment problems.<br>
> > >>> > > > > > > > ><br>
> > >>> > > > > > > > ><br>
> > >>> > > > > > > > > IB<br>
> > >>> > > > > > > > ><br>
> > >>> > > > > > > > > On Jun 3, 2016, at 6:15 AM, Pedro Sousa<br>
> > >>> > > > > > > > > <<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a><br>
</div></div>> <mailto:<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a>> <mailto:<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a><br>
<div><div class="h5">> <mailto:<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a>>>><br>
> > >>> > > wrote:<br>
> > >>> > > > > > > > ><br>
> > >>> > > > > > > > > > Yes. I've used this, but I'll try again as there's<br>
> > >>> > > > > > > > > > seems to<br>
> > >>> > > be<br>
> > >>> > > > > new<br>
> > >>> > > > > > > > > > updates.<br>
> > >>> > > > > > > > > ><br>
> > >>> > > > > > > > > ><br>
> > >>> > > > > > > > > ><br>
> > >>> > > > > > > > > > Stable Branch Skip all repos mentioned above,<br>
> > other<br>
> > >>> > > > > > > > > > than<br>
> > >>> > > epel-<br>
> > >>> > > > > > > > > > release which is still required.<br>
> > >>> > > > > > > > > > Enable latest RDO Stable Delorean repository<br>
> > for all<br>
> > >>> > > > > > > > > > packages<br>
> > >>> > > > > > > > > > sudo curl -o<br>
> > /etc/yum.repos.d/delorean-liberty.repo<br>
> > >>> > > > > <a href="https://trunk.r" rel="noreferrer" target="_blank">https://trunk.r</a><br>
> > >>> > > > > > > > > ><br>
> > <a href="http://doproject.org/centos7-liberty/current/delorean.repo" rel="noreferrer" target="_blank">doproject.org/centos7-liberty/current/delorean.repo</a><br>
> <<a href="http://doproject.org/centos7-liberty/current/delorean.repo" rel="noreferrer" target="_blank">http://doproject.org/centos7-liberty/current/delorean.repo</a>><br>
> > <<a href="http://doproject.org/centos7-liberty/current/delorean.repo" rel="noreferrer" target="_blank">http://doproject.org/centos7-liberty/current/delorean.repo</a>><br>
> > >>> > > > > > > > > > Enable the Delorean Deps repository<br>
> > >>> > > > > > > > > > sudo curl -o<br>
> > >>> > > > > > > > > > /etc/yum.repos.d/delorean-deps-liberty.repo<br>
> > >>> > > > > <a href="http://tru" rel="noreferrer" target="_blank">http://tru</a><br>
> > >>> > > > > > > > > ><br>
> > <a href="http://nk.rdoproject.org/centos7-liberty/delorean-deps.repo" rel="noreferrer" target="_blank">nk.rdoproject.org/centos7-liberty/delorean-deps.repo</a><br>
> <<a href="http://nk.rdoproject.org/centos7-liberty/delorean-deps.repo" rel="noreferrer" target="_blank">http://nk.rdoproject.org/centos7-liberty/delorean-deps.repo</a>><br>
> > <<a href="http://nk.rdoproject.org/centos7-liberty/delorean-deps.repo" rel="noreferrer" target="_blank">http://nk.rdoproject.org/centos7-liberty/delorean-deps.repo</a>><br>
> > >>> > > > > > > > > ><br>
> > >>> > > > > > > > > > On Fri, Jun 3, 2016 at 11:10 AM, Christopher<br>
> > Brown <<br>
> > >>> > > > > <a href="mailto:cbrown2@ocf.co">cbrown2@ocf.co</a> <mailto:<a href="mailto:cbrown2@ocf.co">cbrown2@ocf.co</a>><br>
</div></div>> <mailto:<a href="mailto:cbrown2@ocf.co">cbrown2@ocf.co</a> <mailto:<a href="mailto:cbrown2@ocf.co">cbrown2@ocf.co</a>>>.<br>
<span class="">> > >>> > > > > > > > > > uk> wrote:<br>
> > >>> > > > > > > > > > > No, Liberty deployed ok for us.<br>
> > >>> > > > > > > > > > ><br>
> > >>> > > > > > > > > > > It suggests to me a package mismatch. Have you<br>
> > >>> > > > > > > > > > > completely<br>
> > >>> > > > > rebuilt<br>
> > >>> > > > > > > > > > > the<br>
> > >>> > > > > > > > > > > undercloud and then the images using Liberty?<br>
> > >>> > > > > > > > > > ><br>
> > >>> > > > > > > > > > > On Fri, 2016-06-03 at 11:04 +0100, Pedro<br>
> > Sousa wrote:<br>
> > >>> > > > > > > > > > > > AttributeError: 'module' object has no<br>
> > attribute<br>
> > >>> > > 'PortOpt'<br>
> > >>> > > > > > > > > > > --<br>
> > >>> > > > > > > > > > > Regards,<br>
> > >>> > > > > > > > > > ><br>
> > >>> > > > > > > > > > > Christopher Brown<br>
> > >>> > > > > > > > > > > OpenStack Engineer<br>
> > >>> > > > > > > > > > > OCF plc<br>
> > >>> > > > > > > > > > ><br>
> > >>> > > > > > > > > > > Tel: <a href="tel:%2B44%20%280%29114%20257%202200" value="+441142572200">+44 (0)114 257 2200</a> <tel:%2B44%20%280%29114%20257%202200><br>
> > <tel:%2B44%20%280%29114%20257%202200><br>
> > >>> > > > > > > > > > > Web: <a href="http://www.ocf.co.uk" rel="noreferrer" target="_blank">www.ocf.co.uk</a><br>
</span>> <<a href="http://www.ocf.co.uk" rel="noreferrer" target="_blank">http://www.ocf.co.uk</a>> <<a href="http://www.ocf.co.uk" rel="noreferrer" target="_blank">http://www.ocf.co.uk</a>><br>
> > >>> > > > > > > > > > > Blog: <a href="http://blog.ocf.co.uk" rel="noreferrer" target="_blank">blog.ocf.co.uk</a><br>
> <<a href="http://blog.ocf.co.uk" rel="noreferrer" target="_blank">http://blog.ocf.co.uk</a>> <<a href="http://blog.ocf.co.uk" rel="noreferrer" target="_blank">http://blog.ocf.co.uk</a>><br>
<span class="">> > >>> > > > > > > > > > > Twitter: @ocfplc<br>
> > >>> > > > > > > > > > ><br>
> > >>> > > > > > > > > > > Please note, any emails relating to an OCF<br>
> > Support<br>
> > >>> > > > > > > > > > > request<br>
> > >>> > > must<br>
> > >>> > > > > > > > > > > always<br>
> > >>> > > > > > > > > > > be sent to <a href="mailto:support@ocf.co.uk">support@ocf.co.uk</a> <mailto:<a href="mailto:support@ocf.co.uk">support@ocf.co.uk</a>><br>
</span>> > <mailto:<a href="mailto:support@ocf.co.uk">support@ocf.co.uk</a> <mailto:<a href="mailto:support@ocf.co.uk">support@ocf.co.uk</a>>> for a<br>
<div><div class="h5">> ticket number to<br>
> > >>> > > > > > > > > > > be<br>
> > >>> > > > > generated<br>
> > >>> > > > > > > > > > > or<br>
> > >>> > > > > > > > > > > existing support ticket to be updated.<br>
> > Should this<br>
> > >>> > > > > > > > > > > not be<br>
> > >>> > > done<br>
> > >>> > > > > > > > > > > then OCF<br>
> > >>> > > > > > > > > > ><br>
> > >>> > > > > > > > > > > cannot be held responsible for<br>
> requests not<br>
> > dealt<br>
> > >>> > > > > > > > > > > with in a<br>
> > >>> > > > > > > > > > > timely<br>
> > >>> > > > > > > > > > > manner.<br>
> > >>> > > > > > > > > > ><br>
> > >>> > > > > > > > > > > OCF plc is a company registered in England<br>
> > and Wales.<br>
> > >>> > > > > Registered<br>
> > >>> > > > > > > > > > > number<br>
> > >>> > > > > > > > > > ><br>
> > >>> > > > > > > > > > > 4132533, VAT number GB 780 6803 14.<br>
> > Registered office<br>
> > >>> > > address:<br>
> > >>> > > > > > > > > > > OCF plc,<br>
> > >>> > > > > > > > > > ><br>
> > >>> > > > > > > > > > > 5 Rotunda Business Centre, Thorncliffe<br>
> Park,<br>
> > >>> > > > > > > > > > > Chapeltown,<br>
> > >>> > > > > > > > > > > Sheffield S35<br>
> > >>> > > > > > > > > > > 2PG.<br>
> > >>> > > > > > > > > > ><br>
> > >>> > > > > > > > > > > If you have received this message in<br>
> error,<br>
> > please<br>
> > >>> > > > > > > > > > > notify<br>
> > >>> > > us<br>
> > >>> > > > > > > > > > > immediately and remove it from your<br>
> system.<br>
> > >>> > > > > > > > > > ><br>
> > >>> > > > > > > > ><br>
> > >>> > > > > > > > ><br>
> _______________________________________________<br>
> > >>> > > > > > > > > rdo-list mailing list<br>
> > >>> > > > > > > > > <a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a><br>
</div></div>> <mailto:<a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a>> <mailto:<a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a><br>
<span class="">> <mailto:<a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a>>><br>
> > >>> > > > > > > > > <a href="https://www.redhat.com/mailman/listinfo/rdo-list" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/rdo-list</a><br>
> > >>> > > > > > > > ><br>
> > >>> > > > > > > > > To unsubscribe: <a href="mailto:rdo-list-unsubscribe@redhat.com">rdo-list-unsubscribe@redhat.com</a> <mailto:<a href="mailto:rdo-list-unsubscribe@redhat.com">rdo-list-unsubscribe@redhat.com</a>><br>
</span>> > <mailto:<a href="mailto:rdo-list-unsubscribe@redhat.com">rdo-list-unsubscribe@redhat.com</a><br>
<span class="">> <mailto:<a href="mailto:rdo-list-unsubscribe@redhat.com">rdo-list-unsubscribe@redhat.com</a>>><br>
> > >>> > > > > > > > --<br>
> > >>> > > > > > > > Regards,<br>
> > >>> > > > > > > ><br>
> > >>> > > > > > > > Christopher Brown<br>
> > >>> > > > > > > > OpenStack Engineer<br>
> > >>> > > > > > > > OCF plc<br>
> > >>> > > > > > > ><br>
> > >>> > > > > > > > Tel: <a href="tel:%2B44%20%280%29114%20257%202200" value="+441142572200">+44 (0)114 257 2200</a> <tel:%2B44%20%280%29114%20257%202200><br>
</span><span class="">> > <tel:%2B44%20%280%29114%20257%202200><br>
> > >>> > > > > > > > Web: <a href="http://www.ocf.co.uk" rel="noreferrer" target="_blank">www.ocf.co.uk</a> <<a href="http://www.ocf.co.uk" rel="noreferrer" target="_blank">http://www.ocf.co.uk</a>><br>
> <<a href="http://www.ocf.co.uk" rel="noreferrer" target="_blank">http://www.ocf.co.uk</a>><br>
> > >>> > > > > > > > Blog: <a href="http://blog.ocf.co.uk" rel="noreferrer" target="_blank">blog.ocf.co.uk</a> <<a href="http://blog.ocf.co.uk" rel="noreferrer" target="_blank">http://blog.ocf.co.uk</a>><br>
> <<a href="http://blog.ocf.co.uk" rel="noreferrer" target="_blank">http://blog.ocf.co.uk</a>><br>
> > >>> > > > > > > > Twitter: @ocfplc<br>
> > >>> > > > > > > ><br>
> > >>> > > > > > > > Please note, any emails relating to an OCF Support<br>
> > request<br>
> > >>> > > > > > > > must<br>
> > >>> > > > > always<br>
> > >>> > > > > > > > be sent to <a href="mailto:support@ocf.co.uk">support@ocf.co.uk</a> <mailto:<a href="mailto:support@ocf.co.uk">support@ocf.co.uk</a>><br>
</span>> > <mailto:<a href="mailto:support@ocf.co.uk">support@ocf.co.uk</a> <mailto:<a href="mailto:support@ocf.co.uk">support@ocf.co.uk</a>>> for a<br>
<div><div class="h5">> ticket number to be<br>
> > >>> > > generated or<br>
> > >>> > > > > > > > existing support ticket to be updated.<br>
> Should this<br>
> > not be<br>
> > >>> > > > > > > > done<br>
> > >>> > > then<br>
> > >>> > > > > OCF<br>
> > >>> > > > > > > ><br>
> > >>> > > > > > > > cannot be held responsible for requests not<br>
> dealt<br>
> > with in a<br>
> > >>> > > timely<br>
> > >>> > > > > > > > manner.<br>
> > >>> > > > > > > ><br>
> > >>> > > > > > > > OCF plc is a company registered in England<br>
> and Wales.<br>
> > >>> > > > > > > > Registered<br>
> > >>> > > > > number<br>
> > >>> > > > > > > ><br>
> > >>> > > > > > > > 4132533, VAT number GB 780 6803 14.<br>
> Registered office<br>
> > >>> > > > > > > > address:<br>
> > >>> > > OCF<br>
> > >>> > > > > plc,<br>
> > >>> > > > > > > ><br>
> > >>> > > > > > > > 5 Rotunda Business Centre, Thorncliffe Park,<br>
> > Chapeltown,<br>
> > >>> > > Sheffield<br>
> > >>> > > > > S35<br>
> > >>> > > > > > > > 2PG.<br>
> > >>> > > > > > > ><br>
> > >>> > > > > > > > If you have received this message in error,<br>
> please<br>
> > notify<br>
> > >>> > > > > > > > us<br>
> > >>> > > > > > > > immediately and remove it from your system.<br>
> > >>> > > > > > > ><br>
> > >>> > > > > > > > _______________________________________________<br>
> > >>> > > > > > > > rdo-list mailing list<br>
> > >>> > > > > > > > <a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a><br>
</div></div>> <mailto:<a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a>> <mailto:<a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a><br>
<span class="">> <mailto:<a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a>>><br>
> > >>> > > > > > > > <a href="https://www.redhat.com/mailman/listinfo/rdo-list" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/rdo-list</a><br>
> > >>> > > > > > > ><br>
> > >>> > > > > > > > To unsubscribe: <a href="mailto:rdo-list-unsubscribe@redhat.com">rdo-list-unsubscribe@redhat.com</a> <mailto:<a href="mailto:rdo-list-unsubscribe@redhat.com">rdo-list-unsubscribe@redhat.com</a>><br>
</span>> > <mailto:<a href="mailto:rdo-list-unsubscribe@redhat.com">rdo-list-unsubscribe@redhat.com</a><br>
<span class="">> <mailto:<a href="mailto:rdo-list-unsubscribe@redhat.com">rdo-list-unsubscribe@redhat.com</a>>><br>
> > >>> > > > > > > ><br>
> > >>> > > > > > ><br>
> > >>> > > > > ><br>
> > >>> > > > ><br>
> > >>> > > ><br>
> > >>> > ><br>
> > >>> ><br>
> > >><br>
> > >><br>
> > ><br>
> > ><br>
> > > _______________________________________________<br>
> > > rdo-list mailing list<br>
> > > <a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a> <mailto:<a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a>><br>
</span>> <mailto:<a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a> <mailto:<a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a>>><br>
<span class="">> > > <a href="https://www.redhat.com/mailman/listinfo/rdo-list" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/rdo-list</a><br>
> > ><br>
> > > To unsubscribe: <a href="mailto:rdo-list-unsubscribe@redhat.com">rdo-list-unsubscribe@redhat.com</a> <mailto:<a href="mailto:rdo-list-unsubscribe@redhat.com">rdo-list-unsubscribe@redhat.com</a>><br>
</span>> > <mailto:<a href="mailto:rdo-list-unsubscribe@redhat.com">rdo-list-unsubscribe@redhat.com</a><br>
<span class="im">> <mailto:<a href="mailto:rdo-list-unsubscribe@redhat.com">rdo-list-unsubscribe@redhat.com</a>>><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > rdo-list mailing list<br>
> > <a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a> <mailto:<a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a>><br>
> > <a href="https://www.redhat.com/mailman/listinfo/rdo-list" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/rdo-list</a><br>
> ><br>
> > To unsubscribe: <a href="mailto:rdo-list-unsubscribe@redhat.com">rdo-list-unsubscribe@redhat.com</a> <mailto:<a href="mailto:rdo-list-unsubscribe@redhat.com">rdo-list-unsubscribe@redhat.com</a>><br>
> ><br>
><br>
><br>
</span><span class="im">> --<br>
> Graeme Gillies<br>
> Principal Systems Administrator<br>
> Openstack Infrastructure<br>
> Red Hat Australia<br>
><br>
> _______________________________________________<br>
> rdo-list mailing list<br>
</span><span class="im">> <a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a> <mailto:<a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a>><br>
> <a href="https://www.redhat.com/mailman/listinfo/rdo-list" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/rdo-list</a><br>
><br>
> To unsubscribe: <a href="mailto:rdo-list-unsubscribe@redhat.com">rdo-list-unsubscribe@redhat.com</a><br>
> <mailto:<a href="mailto:rdo-list-unsubscribe@redhat.com">rdo-list-unsubscribe@redhat.com</a>><br>
><br>
><br>
<br>
<br>
--<br>
</span><div class=""><div class="h5">Graeme Gillies<br>
Principal Systems Administrator<br>
Openstack Infrastructure<br>
Red Hat Australia<br>
</div></div></blockquote></div><br></div></div>