Showing headlines posted by dba477

Following bellow is set of instructions required to perform TripleoO QuickStart deployment for release "master". It differs a bit from testing default release "mitaka" . First on F24(23) workstation . . .

This post follows up "TripleO deployment of master branch via instack-virt-setup" Launchpad bug "Updating plans breaks deployment" has status "In Progress" so to be able redeploy "overcloud" heat stack the following bellow workaround would be appiled.

Due to Launchpad Bug "introspection hangs due to broken ipxe config" finally resolved on 09/01/2016 approach suggested in TripleO manual deployment of 'master' branch by Carlo Camacho has been retested. As appears things in meantime have been changed. Following bellow is the way how mentioned above post worked for me right now on 32 GB VIRTHOST (i7 4790)

Procedure bellow identify Controller which has RouterDSA in active state and shutdown/startup this Controller ( controller-1 in particular case). Then log into conntroller-1 and restart pcs cluster on particular Controller, afterwards runs `pacemaker resource cleanup` for several resources what results bringing back cluster nodes in proper status

Current update allows to automate procedure via /etc/rc.d/rc.local and exports is stack's shell variables which allow to start virt-manager right away , presuming that xhost+ was issued in root's shell. Thus, we intend to survive VIRTHOST cold reboot (downtime) and keep previous version of undercloud. VM been able to bring it up avoiding build via quickstart.sh.

Sshutle may be installed on Fedora 24 via straight forward `dnf -y install sshutle`

So, when F24 has been set up as WKS for TripleO QuickStart deployment to VIRTHOST , there is no need to install add-on FoxyProxy and tune it on firefox as well as connect from ansible wks to undergound via...

The following is a step by step self sufficient instruction performing Mitaka HA instack-virt-setup on CentOS 7.2 VIRTHOST based on current Mitaka delorean repos. It follows official guide lines and updates undercloud with OVSIntPort vlan10 for br-ctlplane OVS bridge making posible HA and/or Ceph overcloud deployments with "Network Isolation" enabled.

A final target of this post is to compare undercloud configuration been built by QuickStart and undercloud configuration been built per official documentation for Mitaka stable...

This post follows up http://lxer.com/module/newswire/view/230814/index.html and might work as timer saver. We intend to survive VIRTHOST cold reboot (downtime) and keep previous version of undercloud VM been able to bring it up avoiding build via quickstart.sh, then restart procedure from loging into undercloud and immediately run overcloud deployment.

This post follows up https://www.linux.com/blog/rdo-triple0-quickstart-ha-setup-i... In meantime undercloud-install,undercloud-post-install (openstack undercloud install, openstack overcloud image upload ) are supposed to be performed during original run `bash quickstart.sh --config ./ha.yml $VIRTHOST` . Neutron networks deployment on undercloud and HA Server's configuration has been significantly rebuilt during during the last weeks.

Nova-Docker driver is installed on Compute node which is supposed to run several Java EE Servers as light weight Nova-Docker Containers (instances) having floating IPs on external flat network (actually real office network 192.168.1.0/24) . General Setup RDO Mitaka ML2&OVS&VLAN 3 Nodes.

This posting follows up "Deploying OpenStack on just one hosted server" http://lxer.com/module/newswire/view/229554/index.html, but is focused on utilizing i7 4790/4770 CPUs with inexpensive boards like ASUS Z97-P having 32 GB RAM.

Set up Gnome Desktop && VirtTools on Virtualization Server ( VIRTHOST ) and make remote connection to Virt-manager running on VIRTHOST (192.168.1.75). Then create VM via virt-manager as follows using standard CentOS 7.2 ISO image.

I believe the post bellow will bring some more light on TripleO QuickStart procedure suggested on RDO QuickStart page. Size of memory on Server 32 GB is a must. During minimal configuration runtime 23 GB of RAM are required.

Posting bellow is written with intend to avoid waiting until "koji" build will appear in updates repo of stable RDO Mitaka release, what might take a couple of months or so. Actually, it doesn't require knowledge how to write properly source RH's rpm file.It just needs picking up raw content of git commits from upstream git repo converting them into patches and rebuild required src.rpm(s) with patch(es) needed

Nova-Docker driver is installed on Compute node which is supposed to run two Java EE Servers as light weight Nova-Docker Containers (instances) having floating IPs on two different external vlan enabled subnets (10.10.10.0/24; 10.10.50.0/24). General Setup RDO Mitaka ML2&OVS&VLAN 3 Nodes.

The RDO project recently re-bumped all their tools to both release and install OpenStack. TI was impressed by all the changes so I wanted to test it, and indeed, it works great now.

Post bellow is addressing the question when Controller/Network RDO Mitaka Node has to have external networks of VLAN type with predefined vlan tags. Straight forward packstack deployment doesn't allow to achieve desired network configuration. External network provider of vlan type appears to be required. In particular case, office networks 10.10.10.0/24 vlan tagged (157) ,10.10.50.0/24 vlan tagged (172) already exists when RDO install is running.

TripleO installer is a great tool to deploy an OpenStack cloud. It’s backed by a large user community and doesn’t invent any new tools to install OpenStack.On the other hand, I’m somewhat sceptical about Heat being the right tool to do software configuration. Funneling the configuration options through the Heat templates down to the Puppet scripts seems cumbersome to me.

The problem here is that REST API POST request creating ssh-keypair to access nova servers doesn't write to disk rsa private key and only upload public one to nova. Closing Chrome Client results loosing rsa private key. To prevent failure to write to disk private key , save response-export.json as shown bellow.