As most of you are aware, my mother was diagnosed with stage 2 non-Hodgkins Lymphoma in December 2016, It was a lengthy treatment of Chemotherapy, and I would never wish anything like this for anyone.
It’s been a while since I last posted on my blog (almost 4 years, WOW!!!)
A lot of things have changed at work and personal life, and there’s a lot to talk about. The key things in this post is about catching up where I have been
Hopefully, you’ll see more from me, over the next few weeks and months, especially rounding up the new technology I have been working on, and also something, I have taken up in my personal life too.
For those people following my blogs, you would’ve had an all-in-one install all up and running by now; but now we are going to start afresh. We are going to have a fresh system as explained in my first post, with all the relevant RDO packages installed, and we have all the repositories enabled. Now this installation will be for the foreseeable future, so we won’t need to re-install our OpenStack machine.
This post is going to be quite intensive, such that we are going to try and get to the same stage that we finished in the previous post, but with extra compute nodes in mind.
Welcome to the third part of the series of the blog, today we are going to look at installing and configuring OpenStack networking which will allow us to assign a floating IP to the VM created a in the previous post, and then we should be able to ping and SSH to the instance.
You will need to have your system up to the stage where all the RPMs, repositories, and base config of the system is configured, with one instance up, and available. If in doubt, follow Parts 1 and 2 of the series.
Welcome to the second part of the series of the blog, today we are going to look at installing and configuring OpenStack using packstack, which is provided by the RDO openstack-packstack RPM.
You will need to have your system up to the stage where all the RPMs, repositories, and base config of the system is up to follow this blog. See Part 1 of this topic for more information
Before I start, the contents of all files mentioned in this blog are available at (https://gitlab.arif-ali.co.uk/arif/openstack-lab). Also my assumption is that you would have some knowledge of most of the components in OpenStack. Finally, this will be in a few parts so that there’s not as much to take on
Over the past few months, I have been evaluating OpenStack, and trying a few things in a Proof of Concept(PoC) environment, to see how we can use this in the future. I came through many challenges and hurdles, but finally I got the core components working recently.
There are many times in a datacenter, where we can log into the machines remotely, but we are unable to get external access directly from the machine itself.
I have wanted to use wget to download files, but fortunately, I found a new way to do it
We have a host that we want to get to, through a gateway machine; i.e. we have a hop to get to the machine that we need to work on
Then from that machine, we log onto another machine
We would like to just run one command from the command line, to get directly onto mgmt01
At work, I was trying to get a node installed remotely through kickstart such that I can create the partition table in a specific order. Unfortunately anaconda does not allow us to do that, and you could get disks partitioned not necessarily in the same order. i.e. I wanted the below
- partition 1 == 10M
- partition 2 ~ 50M with raid 2 across all 8 disks, with 6 Hot Spares
- Partition 3 ~ 50G with raid 5 across all 8 disks, with 1 Hot Spare
- Partition 4 everything else
This is probably my first proper blog post, so here goes.
Over the last few years, I have accumulated many git and svn repositories for work and personal projects, and have always looked for a web GUI, and source code management, that all fitted nicely. In this time I have used SVN with webdav, and websvn which worked really well, but unfortunately died to death, as multi-user integration wasn’t there, and therefore colleagues in my team could not effectively contribute to the projects.