<div dir="ltr"><p dir="ltr">Hi Marius,</p>
<p dir="ltr">In cisco switches I have to activate spt portfast on the provisioning network otherwise introspection doesnt work, I get dhcp timeouts. <span style="white-space:pre-wrap">interface FastEthernet0/3</span></p><pre style="white-space:pre-wrap"> <b>description F=I, E=MTQ-itcCTRL-01, P=Eth1, X=Management Openstack
switchport trunk native vlan 2210
switchport trunk allowed vlan 2210,2014,2015
switchport mode trunk
spanning-tree <span class="">portfast</span></b></pre><div><span class=""><p dir="ltr">I also have dell switches and didn't have this problem.</p><div>The metadata problem seems related with some timeout from all the interfaces that get ip from dhcp for the first time and not iptables or routing, because as soon as I run the curl command from command line works fine, so I force it deleting json file from deployed folder, running "os-refresh-config" and the installation resumes.<br></div></span></div>
<p dir="ltr">Regards<br></p>
<div class="gmail_quote"><br></div><div class="gmail_quote"><br></div><div class="gmail_quote">Em 06/06/2016 13:20, "Marius Cornea" <<a href="mailto:marius@remote-lab.net" target="_blank">marius@remote-lab.net</a>> escreveu:<br type="attribution"><blockquote 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"><div>On Mon, Jun 6, 2016 at 1:53 PM, Christopher Brown <<a href="mailto:cbrown2@ocf.co.uk" target="_blank">cbrown2@ocf.co.uk</a>> wrote:<br>
> On Mon, 2016-06-06 at 12:13 +0100, Marius Cornea wrote:<br>
>> On Mon, Jun 6, 2016 at 12:53 PM, Christopher Brown <<a href="mailto:cbrown2@ocf.co.uk" target="_blank">cbrown2@ocf.co.uk</a><br>
>> > wrote:<br>
><br>
</div>[...]<br>
<div>><br>
> Running this command you see something like:<br>
><br>
> [2016-06-04 10:57:09,195] (heat-config) [WARNING] Skipping config<br>
> b28e3adb-ed18-4e74-94cf-260c3c1eefec, already deployed<br>
> [2016-06-04 10:57:09,195] (heat-config) [WARNING] To force-deploy, rm<br>
> /var/lib/heat-config/deployed/b28e3adb-ed18-4e74-94cf-260c3c1eefec.json<br>
><br>
> Once we do this then the deployment continues.<br>
><br>
> Hoep this helps - thanks to Pedro for pointing me in the right<br>
> direction.<br>
<br>
</div>A couple of thoughts about this: if it is STP causing timeouts due to<br>
the transitioning states I'd expect the dhcp requests to time out<br>
earlier, during pxe boot. I think we should add this to the docs, that<br>
the switch ports where the provisioning nic is connected should be<br>
configured as portfast, otherwise you might see dhcp timeouts due to<br>
the convergence time.<br>
<br>
>From what I can see the nodes got stuck later in the deployment<br>
process, unable to reach the metadata server, which runs on the<br>
undercloud. When I hit such issue I usually try to see if I get any<br>
respone by 'curl <a href="http://169.254.169.254" rel="noreferrer" target="_blank">http://169.254.169.254</a>' and then proceed to debug if<br>
it doesn't work. In the past I've seen several causes for this such as<br>
incorrect routing tables set by the nic templates ( you can check it<br>
by 'ip r get 169.254.169.254' and see that the router corresponds to<br>
the underclud IP address) or iptables rules on the undercloud that<br>
blocked access to the metadata server. If it seems stuck without no<br>
actual reason it's also worth trying to restart os-collect-config by<br>
systemctl<br>
<div><br>
<br>
><br>
>> ><br>
>> > Happy to help out with documentation and keeping errata/workarounds<br>
>> > up<br>
>> > to date - I think we just need a "stable" section of the website<br>
>> > which<br>
>> > doesn't seem to exist at the moment.<br>
>> ><br>
>> > Regards<br>
>> ><br>
>> ><br>
>> > On Mon, 2016-06-06 at 00:37 +0100, Graeme Gillies wrote:<br>
>> > ><br>
>> > > Hi Everyone,<br>
>> > ><br>
>> > > I just wanted to say I have been following this thread quite<br>
>> > > closely<br>
>> > > and<br>
>> > > can sympathize with some of the pain people are going through to<br>
>> > > get<br>
>> > > tripleO to work.<br>
>> > ><br>
>> > > Currently it's quite difficult and a bit opaque on how to<br>
>> > > 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<br>
>> > > get a<br>
>> > > functional overcloud working with RDO Mitaka utilising the RDO<br>
>> > > stable<br>
>> > > release built by CentOS, and then I'll talk about some specific<br>
>> > > steps<br>
>> > > I<br>
>> > > think need to be undertaken by the RDO/TripleO team in order to<br>
>> > > provide<br>
>> > > a better experience in the future.<br>
>> > ><br>
>> > > To get a functional overcloud using RDO Mitaka, you need to do<br>
>> > > 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<br>
>> > > your<br>
>> > > undercloud<br>
>> > > 3) Following the normal steps to install your undercloud<br>
>> > > (modifying<br>
>> > > undercloud.conf, and running openstack undercloud install<br>
>> > > 4) You will now need to manually patch ironic on the undercloud<br>
>> > > in<br>
>> > > order<br>
>> > > to make sure repeated introspection works. This might not be<br>
>> > > needed<br>
>> > > if<br>
>> > > you don't do any introspection, but I find more often than not<br>
>> > > you<br>
>> > > end<br>
>> > > up having to do it, so it's worthwhile. The bug you need to patch<br>
>> > > is<br>
>> > > [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/abd50d8438" rel="noreferrer" target="_blank">https://review.openstack.org/changes/306421/revisions/abd50d8438</a><br>
>> > > e7d3<br>
>> > > 71ce24f97d8f8f67052b562007/patch?download'<br>
>> > > ><br>
>> > > ><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<br>
>> > > modifying<br>
>> > > the file<br>
>> > ><br>
>> > > /usr/lib/python2.7/site-<br>
>> > > packages/tripleoclient/v1/overcloud_image.py<br>
>> > ><br>
>> > > At around line 467 you will see a reference to epel, I add a new<br>
>> > > line<br>
>> > > after that to include the rdo_release DIB element to the build as<br>
>> > > 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<br>
>> > > build<br>
>> > > them specifying the mitaka version of rdo_release. I then upload<br>
>> > > 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<br>
>> > > ramdisk,<br>
>> > > we<br>
>> > > need to build a set of images utilising RDO Trunk for the mitaka<br>
>> > > 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/c" rel="noreferrer" target="_blank">http://trunk.rdoproject.org/centos7-mitaka/c</a><br>
>> > > urre<br>
>> > > nt/"<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<br>
>> > > normally<br>
>> > ><br>
>> > > Please note that obviously your mileage may vary, and this is by<br>
>> > > all<br>
>> > > means not an exclusive list of the problems. I have however used<br>
>> > > these<br>
>> > > steps to do multiple node deployments (10+ nodes) with HA over<br>
>> > > different<br>
>> > > hardware sets with different networking setups (single nic,<br>
>> > > multiple<br>
>> > > nic<br>
>> > > with bonding + vlans).<br>
>> > ><br>
>> > > With all the different repos floating around, all which change<br>
>> > > very<br>
>> > > rapidly, combined with the documentation defaults targeting<br>
>> > > developers<br>
>> > > and CI systems (not end users), it's hard to not only get a<br>
>> > > stable<br>
>> > > TripleO install up, but also communicate and discuss clearly with<br>
>> > > others<br>
>> > > what is working, what is broken, and how to compare two<br>
>> > > installations<br>
>> > > 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<br>
>> > > community<br>
>> > > that we undertake the following<br>
>> > ><br>
>> > > 1) Overhaul all the TripleO documentation so that all the steps<br>
>> > > default<br>
>> > > to utilising/deploying using RDO Stable (that is, the releases<br>
>> > > done<br>
>> > > by<br>
>> > > CBS). There should be colored boxes with alt steps for those who<br>
>> > > wish<br>
>> > > to<br>
>> > > use RDO Trunk on the stable branch, and RDO Trunk from master.<br>
>> > > This<br>
>> > > basically inverts the current pattern. I think anyone, Operator<br>
>> > > or<br>
>> > > developer, who is working through the documentation for the first<br>
>> > > time,<br>
>> > > should be given steps that maximise the chance of success, and<br>
>> > > thus<br>
>> > > the<br>
>> > > most stable release we have. Once a user has gone through the<br>
>> > > 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<br>
>> > > the<br>
>> > > rdo_release DIB element, and sets the RDO_RELEASE environment<br>
>> > > variable<br>
>> > > to be 'mitaka' or whenever the current stable release is (and we<br>
>> > > should<br>
>> > > endevour to update it with new releases). There should be no<br>
>> > > extra<br>
>> > > environment variables necessary to build images, and by default<br>
>> > > 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<br>
>> > > some<br>
>> > > sort of robust process for either backporting those patches to<br>
>> > > the<br>
>> > > builds in CBS (I understand we don't do this for various<br>
>> > > reasons), or<br>
>> > > we<br>
>> > > need some kind of tooling or solution that allows operators to<br>
>> > > apply<br>
>> > > only the fixes they need from RDO Trunk (delorean). We need to<br>
>> > > ensure<br>
>> > > that when an Operator utilises TripleO they have the greatest<br>
>> > > chance<br>
>> > > of<br>
>> > > success, and bugs such as these which severely impact the<br>
>> > > 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>
>> > > that<br>
>> > > does highlight the outstanding issues related to TripleO on the<br>
>> > > RDO<br>
>> > > Stable (CBS) releases. These should have links to relevant<br>
>> > > bugzillas,<br>
>> > > clean instructions on how to work around the issue, or cleanly<br>
>> > > apply<br>
>> > > a<br>
>> > > patch to avoid the issue, and as new releases make it out, we<br>
>> > > should<br>
>> > > update the page to drop off workarounds that are no longer<br>
>> > > needed.<br>
>> > ><br>
>> > > The goal is to push Operators/Users to working with our most<br>
>> > > stable<br>
>> > > code<br>
>> > > as much as possible, and track/curate issues around that. This<br>
>> > > way<br>
>> > > everyone should be on the same page, issues are easier to discuss<br>
>> > > and<br>
>> > > diagnose, and overall peoples experiences should be better.<br>
>> > ><br>
>> > > I'm interested in thoughts, feedback, and concerns, both from the<br>
>> > > 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>
>> > > ><br>
>> > > ><br>
>> > > > Thanks Marius,<br>
>> > > ><br>
>> > > > I can confirm that it installs fine with 3 controllers + 3<br>
>> > > > computes<br>
>> > > > after recreating the stack<br>
>> > > ><br>
>> > > > Regards<br>
>> > > ><br>
>> > > > On Sat, Jun 4, 2016 at 4:14 PM, Marius Cornea <marius@remote-la<br>
>> > > > <a href="http://b.ne" rel="noreferrer" target="_blank">b.ne</a><br>
>> > > > t<br>
>> > > > <mailto:<a href="mailto:marius@remote-lab.net" target="_blank">marius@remote-lab.net</a>>> wrote:<br>
>> > > ><br>
>> > > > Hi Pedro,<br>
>> > > ><br>
>> > > > Scaling out controller nodes is not supported at this<br>
>> > > > 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 <pgsousa@gmail.<br>
>> > > > com<br>
>> > > > <mailto:<a href="mailto:pgsousa@gmail.com" target="_blank">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<br>
>> > > > FAILS<br>
>> > > > ><br>
>> > > > > Problem: The new controller nodes are "stuck" in "pscd<br>
>> > > > start", so<br>
>> > > > it seems<br>
>> > > > > to be a problem joining the pacemaker cluster... Did<br>
>> > > > anyone<br>
>> > > > 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 <pgsousa@gmai<br>
>> > > > <a href="http://l.co" rel="noreferrer" target="_blank">l.co</a><br>
>> > > > m<br>
>> > > > <mailto:<a href="mailto:pgsousa@gmail.com" target="_blank">pgsousa@gmail.com</a>>> wrote:<br>
>> > > > >><br>
>> > > > >> Hi,<br>
>> > > > >><br>
>> > > > >> I finally managed to install a baremetal in mitaka with<br>
>> > > > 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_i" rel="noreferrer" target="_blank">http://buildlogs.centos.org/centos/7/cloud/x86_64/tripleo_i</a><br>
>> > > > mage<br>
>> > > > s/mitaka/delorean/<br>
>> > > > >><br>
>> > > > >> I do have an issue that forces me to delete a json file<br>
>> > > > and<br>
>> > > > run<br>
>> > > > >> os-refresh-config inside my overcloud nodes other than<br>
>> > > > that<br>
>> > > > it<br>
>> > > > installs<br>
>> > > > >> fine.<br>
>> > > > >><br>
>> > > > >> Now I'll test with more 2 controllers + 2 computes to<br>
>> > > > have a<br>
>> > > > full HA<br>
>> > > > >> deployment.<br>
>> > > > >><br>
>> > > > >> If anyone needs help to document this I'll be happy to<br>
>> > > > help.<br>
>> > > > >><br>
>> > > > >> Regards,<br>
>> > > > >> Pedro Sousa<br>
>> > > > >><br>
>> > > > >><br>
>> > > > >> On Fri, Jun 3, 2016 at 8:26 PM, Ronelle Landy <rlandy@re<br>
>> > > > dhat<br>
>> > > > .com<br>
>> > > > <mailto:<a href="mailto:rlandy@redhat.com" target="_blank">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<br>
>> > > > repositories?<br>
>> > > > >>><br>
>> > > > >>> Might also want to check your version of rabbitmq: I<br>
>> > > > 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" target="_blank">pgsousa@gmail.com</a> <mailto:<a href="mailto:pgsous" target="_blank">pgsous</a><br>
>> > > > a@gm<br>
>> > > > <a href="http://ail.com" rel="noreferrer" target="_blank">ail.com</a>>><br>
>> > > > >>> > To: "Ronelle Landy" <<a href="mailto:rlandy@redhat.com" target="_blank">rlandy@redhat.com</a> <mailto:<a href="mailto:rlandy" target="_blank">rlandy</a><br>
>> > > > @red<br>
>> > > > <a href="http://hat.com" rel="noreferrer" target="_blank">hat.com</a>>><br>
>> > > > >>> > Cc: "Christopher Brown" <<a href="mailto:cbrown2@ocf.co.uk" target="_blank">cbrown2@ocf.co.uk</a><br>
>> > > > <mailto:<a href="mailto:cbrown2@ocf.co.uk" target="_blank">cbrown2@ocf.co.uk</a>>>, "Ignacio Bravo"<br>
>> > > > >>> > <<a href="mailto:ibravo@ltgfederal.com" target="_blank">ibravo@ltgfederal.com</a> <mailto:<a href="mailto:ibravo@ltgfederal.com" target="_blank">ibravo@ltgfederal.com</a>><br>
>> > > > >,<br>
>> > > > "rdo-list"<br>
>> > > > >>> > <<a href="mailto:rdo-list@redhat.com" target="_blank">rdo-list@redhat.com</a> <mailto:<a href="mailto:rdo-list@redhat.com" target="_blank">rdo-list@redhat.com</a>>><br>
>> > > > >>> > Sent: Friday, June 3, 2016 1:20:43 PM<br>
>> > > > >>> > Subject: Re: [rdo-list] Baremetal Tripleo stable<br>
>> > > > 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" target="_blank">rlandy@redhat.com</a> <mailto:<a href="mailto:rlandy@redhat.com" target="_blank">rlandy@redhat.com</a>>><br>
>> > > > >>> > wrote:<br>
>> > > > >>> ><br>
>> > > > >>> > > I am not sure exactly where you installed from, and<br>
>> > > > 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" target="_blank">pgsousa@gmail.com</a><br>
>> > > > <mailto:<a href="mailto:pgsousa@gmail.com" target="_blank">pgsousa@gmail.com</a>>><br>
>> > > > >>> > > > To: "Ronelle Landy" <<a href="mailto:rlandy@redhat.com" target="_blank">rlandy@redhat.com</a><br>
>> > > > <mailto:<a href="mailto:rlandy@redhat.com" target="_blank">rlandy@redhat.com</a>>><br>
>> > > > >>> > > > Cc: "Christopher Brown" <<a href="mailto:cbrown2@ocf.co.uk" target="_blank">cbrown2@ocf.co.uk</a><br>
>> > > > <mailto:<a href="mailto:cbrown2@ocf.co.uk" target="_blank">cbrown2@ocf.co.uk</a>>>, "Ignacio Bravo" <<br>
>> > > > >>> > > <a href="mailto:ibravo@ltgfederal.com" target="_blank">ibravo@ltgfederal.com</a> <mailto:<a href="mailto:ibravo@ltgfederal.com" target="_blank">ibravo@ltgfederal.com</a><br>
>> > > > >>,<br>
>> > > > "rdo-list"<br>
>> > > > >>> > > > <<a href="mailto:rdo-list@redhat.com" target="_blank">rdo-list@redhat.com</a> <mailto:<a href="mailto:rdo-list@redhat.com" target="_blank">rdo-list@redhat.com</a>><br>
>> > > > ><br>
>> > > > >>> > > > Sent: Friday, June 3, 2016 12:26:58 PM<br>
>> > > > >>> > > > Subject: Re: [rdo-list] Baremetal Tripleo stable<br>
>> > > > version?<br>
>> > > > >>> > > ><br>
>> > > > >>> > > > Thanks Ronelle,<br>
>> > > > >>> > > ><br>
>> > > > >>> > > > do you think this kind of errors can be related<br>
>> > > > with<br>
>> > > > network<br>
>> > > > >>> > > > settings?<br>
>> > > > >>> > > ><br>
>> > > > >>> > > > "Could not retrieve fact='rabbitmq_nodename',<br>
>> > > > >>> > > > resolution='<anonymous>':<br>
>> > > > >>> > > > undefined method `[]' for nil:NilClass Could not<br>
>> > > > retrieve<br>
>> > > > >>> > > > fact='rabbitmq_nodename',<br>
>> > > > resolution='<anonymous>':<br>
>> > > > 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" target="_blank">rlandy@redhat.com</a> <mailto:<a href="mailto:rlandy@redhat.com" target="_blank">rlandy@redhat.com</a>>><br>
>> > > > >>> > > > 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<br>
>> > > > use<br>
>> > > > Tripleo<br>
>> > > > >>> > > > > Qucikstart<br>
>> > > > >>> > > with a<br>
>> > > > >>> > > > > few modifications.<br>
>> > > > >>> > > > > <a href="https://bugs.launchpad.net/tripleo-quickstart/+" rel="noreferrer" target="_blank">https://bugs.launchpad.net/tripleo-quickstart/+</a><br>
>> > > > bug/<br>
>> > > > 1571028.<br>
>> > > > >>> > > > ><br>
>> > > > >>> > > > > ----- Original Message -----<br>
>> > > > >>> > > > > > From: "Pedro Sousa" <<a href="mailto:pgsousa@gmail.com" target="_blank">pgsousa@gmail.com</a><br>
>> > > > <mailto:<a href="mailto:pgsousa@gmail.com" target="_blank">pgsousa@gmail.com</a>>><br>
>> > > > >>> > > > > > To: "Ronelle Landy" <<a href="mailto:rlandy@redhat.com" target="_blank">rlandy@redhat.com</a><br>
>> > > > <mailto:<a href="mailto:rlandy@redhat.com" target="_blank">rlandy@redhat.com</a>>><br>
>> > > > >>> > > > > > Cc: "Christopher Brown" <<a href="mailto:cbrown2@ocf.co.uk" target="_blank">cbrown2@ocf.co.uk</a><br>
>> > > > <mailto:<a href="mailto:cbrown2@ocf.co.uk" target="_blank">cbrown2@ocf.co.uk</a>>>, "Ignacio Bravo" <<br>
>> > > > >>> > > > > <a href="mailto:ibravo@ltgfederal.com" target="_blank">ibravo@ltgfederal.com</a> <mailto:<a href="mailto:ibravo@ltgfederal" target="_blank">ibravo@ltgfederal</a><br>
>> > > > .com<br>
>> > > > ><br>
>> > > > > ><br>
>> > > > > > ,<br>
>> > > > "rdo-list"<br>
>> > > > >>> > > > > > <<a href="mailto:rdo-list@redhat.com" target="_blank">rdo-list@redhat.com</a> <mailto:<a href="mailto:rdo-list@redhat" target="_blank">rdo-list@redhat</a>.<br>
>> > > > com><br>
>> > > > ><br>
>> > > > ><br>
>> > > > >>> > > > > > Sent: Friday, June 3, 2016 11:48:38 AM<br>
>> > > > >>> > > > > > Subject: Re: [rdo-list] Baremetal Tripleo<br>
>> > > > stable<br>
>> > > > version?<br>
>> > > > >>> > > > > ><br>
>> > > > >>> > > > > > Hi Ronelle,<br>
>> > > > >>> > > > > ><br>
>> > > > >>> > > > > > maybe I understand it wrong but I thought<br>
>> > > > that<br>
>> > > > 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/installati" rel="noreferrer" target="_blank">http://docs.openstack.org/developer/tripleo-docs/installati</a><br>
>> > > > on/i<br>
>> > > > nstallation.html<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" target="_blank">rlandy@redhat.com</a> <mailto:<a href="mailto:rlandy@redhat.com" target="_blank">rlandy@redhat.com</a>><br>
>> > > > ><br>
>> > > > >>> > > wrote:<br>
>> > > > >>> > > > > ><br>
>> > > > >>> > > > > > > Hello,<br>
>> > > > >>> > > > > > ><br>
>> > > > >>> > > > > > > We have had success deploying RDO (Mitaka)<br>
>> > > > on<br>
>> > > > baremetal<br>
>> > > > >>> > > > > > > systems -<br>
>> > > > >>> > > using<br>
>> > > > >>> > > > > > > Tripleo Quickstart with both single-nic-<br>
>> > > > vlans<br>
>> > > > and<br>
>> > > > >>> > > > > > > bond-with-vlans<br>
>> > > > >>> > > > > network<br>
>> > > > >>> > > > > > > isolation configurations.<br>
>> > > > >>> > > > > > ><br>
>> > > > >>> > > > > > > Baremetal can have some complicated<br>
>> > > > networking<br>
>> > > > issues but,<br>
>> > > > >>> > > > > > > from<br>
>> > > > >>> > > > > previous<br>
>> > > > >>> > > > > > > experiences, if a single-controller<br>
>> > > > deployment<br>
>> > > > worked but a<br>
>> > > > >>> > > > > > > HA<br>
>> > > > >>> > > > > deployment<br>
>> > > > >>> > > > > > > did not, I would check:<br>
>> > > > >>> > > > > > > - does the HA deployment command include:<br>
>> > > > -e<br>
>> > > > >>> > > > > > ><br>
>> > > > >>> > > > ><br>
>> > > > >>> > ><br>
>> > > > >>> > ><br>
>> > > > /usr/share/openstack-tripleo-heat-<br>
>> > > > 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" target="_blank">cbrown2@ocf.co</a><br>
>> > > > .uk<br>
>> > > > <mailto:<a href="mailto:cbrown2@ocf.co.uk" target="_blank">cbrown2@ocf.co.uk</a>>><br>
>> > > > >>> > > > > > > > To: <a href="mailto:pgsousa@gmail.com" target="_blank">pgsousa@gmail.com</a> <mailto:<a href="mailto:pgsousa@gma" target="_blank">pgsousa@gma</a><br>
>> > > > il.c<br>
>> > > > om>,<br>
>> > > > <a href="mailto:ibravo@ltgfederal.com" target="_blank">ibravo@ltgfederal.com</a> <mailto:<a href="mailto:ibravo@ltgfederal.com" target="_blank">ibravo@ltgfederal.com</a>><br>
>> > > > >>> > > > > > > > Cc: <a href="mailto:rdo-list@redhat.com" target="_blank">rdo-list@redhat.com</a> <mailto:<a href="mailto:rdo-list@" target="_blank">rdo-list@</a><br>
>> > > > redh<br>
>> > > > <a href="http://at.com" rel="noreferrer" target="_blank">at.com</a>><br>
>> > > > >>> > > > > > > > Sent: Friday, June 3, 2016 10:29:39 AM<br>
>> > > > >>> > > > > > > > Subject: Re: [rdo-list] Baremetal Tripleo<br>
>> > > > stable<br>
>> > > > version?<br>
>> > > > >>> > > > > > > ><br>
>> > > > >>> > > > > > > > Hello Ignacio,<br>
>> > > > >>> > > > > > > ><br>
>> > > > >>> > > > > > > > Thanks for your response and good to know<br>
>> > > > 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<br>
>> > > > 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<br>
>> > > > and<br>
>> > > > vlans.<br>
>> > > > >>> > > > > > > ><br>
>> > > > >>> > > > > > > > The RDO web page states:<br>
>> > > > >>> > > > > > > ><br>
>> > > > >>> > > > > > > > "If you want to create a production-ready<br>
>> > > > 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,<br>
>> > > > Ignacio<br>
>> > > > Bravo<br>
>> > > > wrote:<br>
>> > > > >>> > > > > > > > > Pedro / Christopher,<br>
>> > > > >>> > > > > > > > ><br>
>> > > > >>> > > > > > > > > Just wanted to share with you that I<br>
>> > > > also<br>
>> > > > had<br>
>> > > > plenty of<br>
>> > > > >>> > > > > > > > > issues<br>
>> > > > >>> > > > > > > > > deploying on bare metal HA servers, and<br>
>> > > > have<br>
>> > > > paused the<br>
>> > > > >>> > > deployment<br>
>> > > > >>> > > > > > > > > using TripleO until better winds start<br>
>> > > > to<br>
>> > > > flow<br>
>> > > > here. I<br>
>> > > > >>> > > > > > > > > was<br>
>> > > > >>> > > able to<br>
>> > > > >>> > > > > > > > > deploy the QuickStart, but on bare<br>
>> > > > metal<br>
>> > > > 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<br>
>> > > > go<br>
>> > > > through<br>
>> > > > a full<br>
>> > > > >>> > > > > > > > > install<br>
>> > > > >>> > > > > with<br>
>> > > > >>> > > > > > > > > us to better see where things fail. We<br>
>> > > > can<br>
>> > > > do this<br>
>> > > > >>> > > > > > > > > handholding<br>
>> > > > >>> > > > > > > > > deployment once every week/month based<br>
>> > > > on<br>
>> > > > developers time<br>
>> > > > >>> > > > > > > > > availability. That way we can get a<br>
>> > > > working<br>
>> > > > install, and<br>
>> > > > >>> > > > > > > > > we can<br>
>> > > > >>> > > > > > > > > troubleshoot real life environment<br>
>> > > > problems.<br>
>> > > > >>> > > > > > > > ><br>
>> > > > >>> > > > > > > > ><br>
>> > > > >>> > > > > > > > > IB<br>
>> > > > >>> > > > > > > > ><br>
>> > > > >>> > > > > > > > > On Jun 3, 2016, at 6:15 AM, Pedro Sousa<br>
>> > > > >>> > > > > > > > > <<a href="mailto:pgsousa@gmail.com" target="_blank">pgsousa@gmail.com</a> <mailto:<a href="mailto:pgsousa@gmai" target="_blank">pgsousa@gmai</a><br>
>> > > > <a href="http://l.co" rel="noreferrer" target="_blank">l.co</a><br>
>> > > > m>><br>
>> > > > >>> > > wrote:<br>
>> > > > >>> > > > > > > > ><br>
>> > > > >>> > > > > > > > > > Yes. I've used this, but I'll try<br>
>> > > > again<br>
>> > > > as there's<br>
>> > > > >>> > > > > > > > > > seems to<br>
>> > > > >>> > > be<br>
>> > > > >>> > > > > new<br>
>> > > > >>> > > > > > > > > > updates.<br>
>> > > > >>> > > > > > > > > ><br>
>> > > > >>> > > > > > > > > ><br>
>> > > > >>> > > > > > > > > ><br>
>> > > > >>> > > > > > > > > > Stable Branch Skip all repos<br>
>> > > > mentioned<br>
>> > > > above,<br>
>> > > > other<br>
>> > > > >>> > > > > > > > > > than<br>
>> > > > >>> > > epel-<br>
>> > > > >>> > > > > > > > > > release which is still required.<br>
>> > > > >>> > > > > > > > > > Enable latest RDO Stable Delorean<br>
>> > > > 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>
>> > > > ><br>
>> > > > >>> > > > > > > > > > Enable the Delorean Deps repository<br>
>> > > > >>> > > > > > > > > > sudo curl -o<br>
>> > > > >>> > > > > > > > > > /etc/yum.repos.d/delorean-deps-<br>
>> > > > 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.rep" rel="noreferrer" target="_blank">http://nk.rdoproject.org/centos7-liberty/delorean-deps.rep</a><br>
>> > > > o><br>
>> > > > >>> > > > > > > > > ><br>
>> > > > >>> > > > > > > > > > On Fri, Jun 3, 2016 at 11:10 AM,<br>
>> > > > Christopher<br>
>> > > > Brown <<br>
>> > > > >>> > > > > <a href="mailto:cbrown2@ocf.co" target="_blank">cbrown2@ocf.co</a> <mailto:<a href="mailto:cbrown2@ocf.co" target="_blank">cbrown2@ocf.co</a>>.<br>
>> > > > >>> > > > > > > > > > uk> wrote:<br>
>> > > > >>> > > > > > > > > > > No, Liberty deployed ok for us.<br>
>> > > > >>> > > > > > > > > > ><br>
>> > > > >>> > > > > > > > > > > It suggests to me a package<br>
>> > > > mismatch.<br>
>> > > > Have you<br>
>> > > > >>> > > > > > > > > > > completely<br>
>> > > > >>> > > > > rebuilt<br>
>> > > > >>> > > > > > > > > > > the<br>
>> > > > >>> > > > > > > > > > > undercloud and then the images<br>
>> > > > using<br>
>> > > > Liberty?<br>
>> > > > >>> > > > > > > > > > ><br>
>> > > > >>> > > > > > > > > > > On Fri, 2016-06-03 at 11:04 +0100,<br>
>> > > > Pedro<br>
>> > > > Sousa wrote:<br>
>> > > > >>> > > > > > > > > > > > AttributeError: 'module' object<br>
>> > > > has<br>
>> > > > 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" target="_blank">+44 (0)114 257 2200</a><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>
>> > > > <<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.o" rel="noreferrer" target="_blank">http://blog.o</a><br>
>> > > > cf.c<br>
>> > > > <a href="http://o.uk" rel="noreferrer" target="_blank">o.uk</a>><br>
>> > > > >>> > > > > > > > > > > Twitter: @ocfplc<br>
>> > > > >>> > > > > > > > > > ><br>
>> > > > >>> > > > > > > > > > > Please note, any emails relating to<br>
>> > > > an<br>
>> > > > OCF<br>
>> > > > Support<br>
>> > > > >>> > > > > > > > > > > request<br>
>> > > > >>> > > must<br>
>> > > > >>> > > > > > > > > > > always<br>
>> > > > >>> > > > > > > > > > > be sent to <a href="mailto:support@ocf.co.uk" target="_blank">support@ocf.co.uk</a><br>
>> > > > <mailto:<a href="mailto:support@ocf.co.uk" target="_blank">support@ocf.co.uk</a>> for a ticket number to<br>
>> > > > >>> > > > > > > > > > > be<br>
>> > > > >>> > > > > generated<br>
>> > > > >>> > > > > > > > > > > or<br>
>> > > > >>> > > > > > > > > > > existing support ticket to be<br>
>> > > > updated.<br>
>> > > > Should this<br>
>> > > > >>> > > > > > > > > > > not be<br>
>> > > > >>> > > done<br>
>> > > > >>> > > > > > > > > > > then OCF<br>
>> > > > >>> > > > > > > > > > ><br>
>> > > > >>> > > > > > > > > > > cannot be held responsible for<br>
>> > > > requests<br>
>> > > > not<br>
>> > > > dealt<br>
>> > > > >>> > > > > > > > > > > with in a<br>
>> > > > >>> > > > > > > > > > > timely<br>
>> > > > >>> > > > > > > > > > > manner.<br>
>> > > > >>> > > > > > > > > > ><br>
>> > > > >>> > > > > > > > > > > OCF plc is a company registered in<br>
>> > > > 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,<br>
>> > > > Thorncliffe<br>
>> > > > Park,<br>
>> > > > >>> > > > > > > > > > > Chapeltown,<br>
>> > > > >>> > > > > > > > > > > Sheffield S35<br>
>> > > > >>> > > > > > > > > > > 2PG.<br>
>> > > > >>> > > > > > > > > > ><br>
>> > > > >>> > > > > > > > > > > If you have received this message<br>
>> > > > 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" target="_blank">rdo-list@redhat.com</a> <mailto:<a href="mailto:rdo-list@re" target="_blank">rdo-list@re</a><br>
>> > > > dhat<br>
>> > > > .com><br>
>> > > > >>> > > > > > > > > <a href="https://www.redhat.com/mailman/listinfo" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo</a><br>
>> > > > /rdo<br>
>> > > > -list<br>
>> > > > >>> > > > > > > > ><br>
>> > > > >>> > > > > > > > > To unsubscribe: rdo-list-unsubscribe@re<br>
>> > > > dhat<br>
>> > > > .com<br>
>> > > > <mailto:<a href="mailto:rdo-list-unsubscribe@redhat.com" target="_blank">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" target="_blank">+44 (0)114 257 2200</a><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> <<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" rel="noreferrer" target="_blank">http://blog.ocf.co</a>.<br>
>> > > > uk><br>
>> > > > >>> > > > > > > > Twitter: @ocfplc<br>
>> > > > >>> > > > > > > ><br>
>> > > > >>> > > > > > > > Please note, any emails relating to an<br>
>> > > > OCF<br>
>> > > > Support<br>
>> > > > request<br>
>> > > > >>> > > > > > > > must<br>
>> > > > >>> > > > > always<br>
>> > > > >>> > > > > > > > be sent to <a href="mailto:support@ocf.co.uk" target="_blank">support@ocf.co.uk</a><br>
>> > > > <mailto:<a href="mailto:support@ocf.co.uk" target="_blank">support@ocf.co.uk</a>> for a ticket number to be<br>
>> > > > >>> > > generated or<br>
>> > > > >>> > > > > > > > existing support ticket to be updated.<br>
>> > > > Should<br>
>> > > > this<br>
>> > > > not be<br>
>> > > > >>> > > > > > > > done<br>
>> > > > >>> > > then<br>
>> > > > >>> > > > > OCF<br>
>> > > > >>> > > > > > > ><br>
>> > > > >>> > > > > > > > cannot be held responsible for requests<br>
>> > > > not<br>
>> > > > dealt<br>
>> > > > with in a<br>
>> > > > >>> > > timely<br>
>> > > > >>> > > > > > > > manner.<br>
>> > > > >>> > > > > > > ><br>
>> > > > >>> > > > > > > > OCF plc is a company registered in<br>
>> > > > 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<br>
>> > > > Park,<br>
>> > > > Chapeltown,<br>
>> > > > >>> > > Sheffield<br>
>> > > > >>> > > > > 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>
>> > > > >>> > > > > > > > rdo-list mailing list<br>
>> > > > >>> > > > > > > > <a href="mailto:rdo-list@redhat.com" target="_blank">rdo-list@redhat.com</a> <mailto:<a href="mailto:rdo-list@redh" target="_blank">rdo-list@redh</a><br>
>> > > > at.c<br>
>> > > > om><br>
>> > > > >>> > > > > > > > <a href="https://www.redhat.com/mailman/listinfo/r" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/r</a><br>
>> > > > do-l<br>
>> > > > ist<br>
>> > > > >>> > > > > > > ><br>
>> > > > >>> > > > > > > > To unsubscribe: rdo-list-unsubscribe@redh<br>
>> > > > at.c<br>
>> > > > om<br>
>> > > > <mailto:<a href="mailto:rdo-list-unsubscribe@redhat.com" target="_blank">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" target="_blank">rdo-list@redhat.com</a> <mailto:<a href="mailto:rdo-list@redhat.com" target="_blank">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" target="_blank">rdo-list-unsubscribe@redhat.com</a><br>
>> > > > <mailto:<a href="mailto:rdo-list-unsubscribe@redhat.com" target="_blank">rdo-list-unsubscribe@redhat.com</a>><br>
>> > > ><br>
>> > > ><br>
>> > > ><br>
>> > > ><br>
>> > > > _______________________________________________<br>
>> > > > rdo-list mailing list<br>
>> > > > <a href="mailto:rdo-list@redhat.com" target="_blank">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" target="_blank">rdo-list-unsubscribe@redhat.com</a><br>
>> > > ><br>
>> > > --<br>
>> > > Graeme Gillies<br>
>> > > Principal Systems Administrator<br>
>> > > Openstack Infrastructure<br>
>> > > Red Hat Australia<br>
>> > ><br>
>> > > _______________________________________________<br>
>> > > rdo-list mailing list<br>
>> > > <a href="mailto:rdo-list@redhat.com" target="_blank">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" target="_blank">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" target="_blank">+44 (0)114 257 2200</a><br>
>> > Web: <a href="http://www.ocf.co.uk" rel="noreferrer" target="_blank">www.ocf.co.uk</a><br>
>> > Blog: <a href="http://blog.ocf.co.uk" rel="noreferrer" target="_blank">blog.ocf.co.uk</a><br>
>> > Twitter: @ocfplc<br>
>> ><br>
>> > Please note, any emails relating to an OCF Support request must<br>
>> > always<br>
>> > be sent to <a href="mailto:support@ocf.co.uk" target="_blank">support@ocf.co.uk</a> for a ticket number to be generated or<br>
>> > existing support ticket to be updated. Should this not be done then<br>
>> > OCF<br>
>> ><br>
>> > cannot be held responsible for requests not dealt with in a timely<br>
>> > manner.<br>
>> ><br>
>> > OCF plc is a company registered in England and Wales. Registered<br>
>> > number<br>
>> ><br>
>> > 4132533, VAT number GB 780 6803 14. Registered office address: OCF<br>
>> > plc,<br>
>> ><br>
>> > 5 Rotunda Business Centre, Thorncliffe Park, Chapeltown, Sheffield<br>
>> > S35<br>
>> > 2PG.<br>
>> ><br>
>> > If you have received this message in error, please notify us<br>
>> > immediately and remove it from your system.<br>
>> ><br>
>> > _______________________________________________<br>
>> > rdo-list mailing list<br>
>> > <a href="mailto:rdo-list@redhat.com" target="_blank">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" target="_blank">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" target="_blank">+44 (0)114 257 2200</a><br>
> Web: <a href="http://www.ocf.co.uk" rel="noreferrer" target="_blank">www.ocf.co.uk</a><br>
> Blog: <a href="http://blog.ocf.co.uk" rel="noreferrer" target="_blank">blog.ocf.co.uk</a><br>
> Twitter: @ocfplc<br>
><br>
> Please note, any emails relating to an OCF Support request must always<br>
> be sent to <a href="mailto:support@ocf.co.uk" target="_blank">support@ocf.co.uk</a> for a ticket number to be generated or<br>
> existing support ticket to be updated. Should this not be done then OCF<br>
><br>
> cannot be held responsible for requests not dealt with in a timely<br>
> manner.<br>
><br>
> OCF plc is a company registered in England and Wales. Registered number<br>
><br>
> 4132533, VAT number GB 780 6803 14. Registered office address: OCF plc,<br>
><br>
> 5 Rotunda Business Centre, Thorncliffe Park, Chapeltown, Sheffield S35<br>
> 2PG.<br>
><br>
> If you have received this message in error, please notify us<br>
> immediately and remove it from your system.<br>
</div></blockquote></div>
</div>